hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.2.1 Aim | An ST may reach a destination through one or more STs attached to the Internet. The "cost" of routing to ST3 or ST4 may change over time depending on the air interface status between the satellite and the STs, the congestion on-board or the congestion in the egress STs. Thus the forwarding table in ST1 (and/or the OBP/... |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.2.2 Requirements | Define how often the cost metrics need to be refreshed in order to allocate the computation of the routing table between OBC, BRS and ST. Definition of a BSMS cost-based routing matrix based on conventional IP routing tables and on "Link State" methods. A set of primitives (e.g. at the SI-C-SAP interface) will be defin... |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.3 TS3.3: Route discovery interface and primitives | |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.3.1 Aim | In OSPF and similar protocols. (i.e. EGP, BGP, etc.) it is essential that every router on a common network enables 2-way communications and keeps its database synchronized (see clause 7.2.2.3). Over a BSMS the Hello packet from an upstream router will reach the ST as a UDP packet. This packet is sent as high priority b... |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.3.2 Requirements | 1) Definition of suitable timer values for the BSMS. 2) Definition of primitives to support route discovery. |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.4 TS3.4: Dedicated BSMS signalling channels for routing, etc. | |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.4.1 Aim | Two of the main problems in a BSMS as regards route discovery and related topics (address resolution, labelling paths in MPLS, RSVP reservation etc.) are the potential limitations in bandwidth at the BSMS ingress terminal and the end-to-end delay (see clause 7.2.2.4). Due to these factors signalling messages may time o... |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.4.2 Requirements | Definition of signalling class function and SI-C-SAP primitives. The signalling class should allow IP signalling messages (usually short) to be transmitted a soon as they reach the ingress of the BSMS. As soon as an "important" message is identified it pre-empts any existing queue and leave in the next available frame ... |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.5 TS4: Strategies for IPv6 service transition from IPv4 | This TS is intended to extend and expand on routing and networking architectures addressed in TS1. |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.5.1 Aim | The BSMS may be chosen to be either IPv4 or IPv6 based, which has implications on the interworking mechanisms to be included in the BSMS. An IPv4-based BSMS is a natural short-term solution which could be adapted with interworking units at a few specific interfaces to allow for the IPv6 network interconnection scenario... |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.5.2 Requirements | Definition of BSMS functional architecture to support addressing and routing transition scenarios. Two main aspects may be considered of most immediate importance for strategic and fast adoption of IPv6 (Transition Mechanisms for IPv6 Hosts and Routers - IETF RFC 2893): 1) Interconnection of IPv6 islands through an IPv... |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.6 TS5: Label-based IP-oriented link layer | |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.6.1 Aim | A satellite-oriented solution to the underlying protocol to the IP layer in the BSMS is to employ "label paths" acting as logical broadcast networks. This is a simpler scheme compared to MPLS, and better adapted to satellites by taking advantage of their multicast attributes (see clause 7.4.2.2). Such logical satellite... |
78bf1d9f7e8dbb05426ae0561f9a50be | 102 155 | 9.3.6.2 Requirements | Definition of IP-oriented link layer: • Labelling concepts and label structure. • Satellite ARP for dynamic resolution. • Mapping of labels onto standardized satellite access layer identifiers (PID, VPI/VCI). • Segmentation and re-assembly functions (when a shared label is used to filter traffic at reception, a functio... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 1 Scope | The study was intended to include: • Investigation on the major sources of incompatibility. • Review of existing certificate configurations in the public domain, i.e. for open user communities. • Review of proposed profiles. • Conclusion whether a normative task is feasible and meaningful. Since the conclusion reached ... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 2 References | For the purposes of this Technical Report (TR), the following references apply: [1] Directive 1999/93/EC of the European Parliament and of the Council of 13 December 1999 on a Community framework for electronic signatures. [2] IETF RFC 3279: "Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure C... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 3 Definitions and abbreviations | |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: authentication certificate: Public Key Certificate (PKC) intended to be used in an electronic signature which serves as a method of authentication, as specified in Directive [1], article 2.1. Certification Authority: authority trusted ... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CA Certification Authority CRL Certificate Revocation List CSP Certificate Service Provider EESSI European Electronic Signature Standardization Initiative EIC Electronic Identity Certificates EID Electronic Identity Document IETF Internet Engi... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 4 Implications from the requirements of the Directive | Directive [1] whereas (5) provides a clear hint to interoperability: "The interoperability of electronic-signature products should be promoted; in accordance with Article 14 of the Treaty, the internal market comprises an area without internal frontiers in which the free movement of goods is ensured; essential requirem... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 5 Documents scrutinized | The following profiles and documents have been analysed by the task components. Document name Organization Country A-Trust - Certificate and CRL Specification A-Trust Gesellschaft für Sicherheitssysteme im elektronischen Zahlungsverkehr GmbH. Austria FINEID S4-1 - Implementation profile 1 of the FINEID - S1 specificati... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 6 Analysis outcomes | |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 6.1 Profile comparison | The following table gives a synoptic view of the main characteristics (i.e.: extensions and fields) of the examined profiles. Given the limited study purpose the profile examination has not been done in depth: the task members' goal was to ascertain if the existent certificates assure a satisfactory interoperability or... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 6.2 Profiles inconsistencies | A few inconsistencies stem out of the previous table. Their severity has been classified as follows: Severity 1. The inconsistency gives way to outright incompatibility since what is permitted or mandatory for one or more profile is unacceptable for other ones. Severity 2. The inconsistency requires the signature verif... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 6.2.1 Inconsistencies list | # Inconsistency Severity Comment 1 CertificateSerialNumer field length S3 The acceptable field length spans between 8 bytes and 20 bytes. It can be easily handled by suitable application programs, but a uniform length it would be preferable. 2 Allowed Signature Algorithms S1 All provide for SHA1 with RSA encryption, bu... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 6.2.2 Comments on the findings | Major concerns arise from the previous table: 1) non full interoperability among certificates; 2) questionable choices, mostly in the authentication certificate profile. Both concerns may lead to major problems in exchanging signed electronic documents across frontiers and in mutually recognizing Member States electron... |
bc39af42a5d9eabce8b47d1caa9ca1cf | 102 153 | 7 Proposed strategy and implementation phases | It has already been pointed out that an actual interoperability is indispensable to achieve the Directive purposes, as specified in clause 4. It is a common belief of those who took part in the study that a task force is to be charged of working out certificate profiles that meet the following requirements: 1) achieve ... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 1 Scope | The present document gives a preliminary analysis of technical requirements for the support of EMTEL and location services for emergency and priority services within the PSTN/ISDN/IP signalling transport services in Europe, to progress toward the enhancement signalling transport protocol standards documentation. |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 2 References | For the purposes of this Technical Report (TR), the following references apply: [1] CGALIES: CGALIES Final Report V1.0. [2] LOCUS: Final Report D6. [3] ETSI TS 102 164: "Services and Protocols for Advanced Networks (SPAN); Emergency Location Protocols". [4] WERT FINAL REPORT for the September 11, 2001 New York City Wor... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project ATM Asynchronous Transfer Mode CGALIES Co-ordination Group on Access to Location Information for Emergency Services CLI Calling Line Identity CPC Calling Party Category DECT Digital Enhanced Cordless Tel... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 4 Enhanced emergency call for assistance | The need for and means of improved telecommunication services for disaster relief communications and emergency call handling was debated in ITU and ETSI workshops [7], [8]. The requirements for the Enhanced 112 (E112) service are contained in the CGALIES report [1] and in the LOCUS reports [2] which outline the regulat... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 4.1 Protocol interfaces | Figure 1 indicates how the location information of the caller is passed to the appropriate emergency service. The caller has been categorized into four basic types, a mobile user, a fixed line user, a data packet user, and an automatic alarm user. These protocol interfaces are marked . Dispatcher ... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 4.1.1 Fixed line user | This user includes the normal telephony user that dials for emergency assistance using the pan European emergency number 112, or national specific emergency number. As well as the voice telephony service other data services such as SMS or telemetry, may be used to alert the PSAP (or are configured such that an alert ca... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 4.1.2 Mobile user | Radio Access Network SMLC GMLC Core N’twk PSAP Figure 2: Mobile users with location information functional architecture Figure 2 shows how for a GSM customer that dials for emergency assistance, using the pan European emergency number 112 or national specific emergency number, location information is made availab... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 4.1.3 Data network user | |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 4.1.3.1 Data based users | Included in this clause, is a description how location information could be obtained and verified. At present this cannot be done in the present IP protocol set of standards. How is this information then interworked so that the information is available in the location database? PSAP LAN Administrator WAN LAN PSTN ... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 4.1.3.2 Message data based users | Data, fixed and mobile networks are also capable of delivering data as well as voice to the PSAP, in the form of email and SMS messages respectively. This form of contact suffers from the problem that the location cannot be confirmed in real time by the caller as is done by voice communication, provided the caller is c... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 4.1.4 Alarm data users | This has been investigated by this STF and it is believed that there are no problems for ETSI SPAN as alarm devices are fixed in the network therefore location information rarely changes. ETSI ETSI TR 102 197 V1.1.1 (2003-10) 11 |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 4.2 Multiple PSAP and cross border protocol interfaces | Dispatcher ? A B Figure 5: Functional architecture of multiple PSAP and a cross border EMTEL call Figure 5 shows a possible fully integrated PSAP platform. Not shown here is the possibility of a similar architecture showing multiple databases that are fully integrated to allow for redundancy.... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5 Disaster communications | This clause outlines the actions that may be put into place and extrapolates the requirements that may be put into place to deal with a disaster. It should be noted that this clause of the present document has only considered a disaster that occurs within the European sphere and does not consider disasters that occur e... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.1 Pre-disaster requirements | |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.1.1 Unknown disasters | Most networks cooperate with any disaster plans put in place by the respective governments; they also have disaster recovery programmes in place to deal with telecommunication disasters like exchange failure. As far as signalling is concerned there is no special further requirements needed so there is no work for ETSI ... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.1.2 Known disasters | If there is a disaster about to happen e.g. flooding then there may be a need for the emergency authorities to broadcast to a large number of people in the disaster zone. For the fixed line networks there may be many alternatives to achieve this requirement, e.g. from automatic dialling devices on each exchange to usin... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.2 Immediate requirements | |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.2.1 Citizen to authority | When the disaster first strikes then there may be no communication in any form from the effected area, but from the outside of this area there may be a very large number of calls from good Samaritans dialling 112. When the news of this disaster reaches the population a very large number of calls will be generated to th... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.2.2 Authority to authority | It should also be self evident that for a disaster for which no warning is possible then there would be no immediate emergency command structure in place but this should have been planned for and any disaster plans initiated. It may be that the PSAP will have to act as the initial command centre and would need to commu... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.2.3 Authority to citizen | Technically this is not any different from the previous clause (5.1.2) for the broadcasting of warnings etc. prior to an emergency occurring. In the initial phase of the disaster it could be very difficult to establish the exact nature of the emergency, but there may be a need to issue a standard warning to evacuate or... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.3 Long term requirements | The long-term requirements are based upon the assumption that after the disaster has occurred then a disaster HQ has been set-up to coordinate the emergency services. This could be a mobile centre within the area itself or it has been set-up outside the area and communicated to emergency services within the area. As it... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.3.1 Citizen to authority | In the worst-case scenario no communication is possible from the disaster area, but there is a need to for the general population to be able to communicate both with friends and family and the emergency authorities. This could be achieved by the disaster recover programmes that most network operators have in place whic... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.3.2 Authority to authority | It has been highlighted in various presentations to workshops that there is a need for cross emergency service communication, and each emergency service has its own equipment. Common communication equipment needs to be defined. This could be TETRA as one of the options as outlined in the MESA report [5]. Each emergency... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 5.3.3 Authority to citizen | The same requirements for claue 5.2.3 should also be applied to this clause. The WERT [4] report indicates a need to communicate with trapped survivors via voice and text including email. |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 6 Requirements on NGN/IP networks | From the workshops and discussions held in various standards fora there seems to be a common set of requirements emerging for the NGN/IP networks. These can be categorized as follows: • There is a need to specify EMTEL capability now, not retrofit later. • Solutions need to be reliable, affordable, backward capable, in... |
83e1e650710a372e5ff221c7006d5084 | 102 197 | 7 Recommendations | 1) From the above clause 4 it can be seen that work may need to be done to extend the service on the PSAP to accept a call for emergency assistance from non real time communications. These are principally SMS and email text messages. The problems outlined in the present document are: - These are not real time services,... |
b492d77f39260eed1f6412f6289fe484 | 102 140 | 1 Scope | The present document describes the status of the documents worked on by Special Task Force (STF) 226. |
b492d77f39260eed1f6412f6289fe484 | 102 140 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ETSI TS 102 141: "Services and Protocols for Advanced Networks (SPAN); MTP/SCCP/SSCOP and SIGTRAN (Transport of SS7 over IP); Message transfer part 2 User Adaptation layer (M2UA) [Endorsement of RFC 3331 (2002), modified]". [2] ETSI TS 1... |
b492d77f39260eed1f6412f6289fe484 | 102 140 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: M2PA Message transfer part 2-User Peer-to-peer Adaptation layer M2UA Message transfer part 2 User Adaptation layer M3UA Message transfer part 3 User Adaptation layer SUA Signalling connection control part User Adaptation layer SCTP Stream Cont... |
b492d77f39260eed1f6412f6289fe484 | 102 140 | 4 Report | |
b492d77f39260eed1f6412f6289fe484 | 102 140 | 4.1 Final list of TSs | Initially STF 226 worked on four adaptation layers developed in the SIGTRAN working group of the Internet Engineering Task Force (IETF): M2PA, M2UA, M3UA and SUA. The analysis of M2PA showed that there are no protocol elements which need to be adopted by ETSI networks. Furthermore the discussion on the SIGTRAN mailing ... |
b492d77f39260eed1f6412f6289fe484 | 102 140 | 4.2 SCTP | TS 102 144 [4] focusses on the requirements for an SCTP implementation used for signalling transport. All SCTP implementations are required to use the same checksum algorithm to ensure interoperability. For providing network fault tolerance the support of multihoming is required and the heartbeat mechanism shall be use... |
b492d77f39260eed1f6412f6289fe484 | 102 140 | 4.3 M2UA, M3UA and SUA | All three adaptation layers are handled the same way. In the common clause 4 of TS 102 141 [1], TS 102 142 [2], TS 102 143 [3] and TS 102 144 [4], considerations are given which make sure the different implementations are interoperable. Therefore it is required that SCTP is the transport protocol. Furthermore no nation... |
b492d77f39260eed1f6412f6289fe484 | 102 140 | 4.4 Further work | During the work of STF 226 some topics were found which need further work. These topics were out of the scope of STF 226. These topics are: • it should be analyzed and documented which protocol should be used in particular situations; • it should be analyzed and documented how the protocols should be used and are inter... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 1 Scope | The present document describes the use of service codes for supplementary services used in public network services. It was based upon the analysis of the answers to a questionnaire sent out to the whole ETSI members. In October 1997, it was supplemented by follow up questioning and the consideration of relevant ETSI, G... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 3 Definitions, symbols and abbreviations | |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 3.1 Definitions | For the purposes of the present document, the following definitions apply: Service Code: A two or three digit string used within a user command dialogue to identify a Supplementary Service. Supplementary Service: An additional service provided by a network which modifies or supplements a basic telecommunications servic... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: * The Star on the standard telephone keypad array # The Square on the standard telephone keypad array |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CAC Commercial Action Committee (within CEPT) CEPT Conférence des Administrations Européennes des Postes et Télécommunications ETNO Association of Public Telecommunications Network Operators GSM Global System for Mobile communications IMEI Int... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 4 Basis of the work | |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 4.1 Terms of reference of ETSI STF 117 | The original terms of reference required the STF to: • collate and analyse the data from the questionnaires; • categorize and rationalize the existing service code listings (to free up non-used codes and open up new service code groupings); • create the draft register and prepare the documentation for approval by TC-HF... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 4.2 Supplementary Service (SS) code | |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 4.2.1 Use of a SS code | A supplementary service code is a two or three digit string used within a user command dialogue used to gain access to and control of a supplementary service. Its use is specified in ETS 300 738 [11] and should contain the following fields: • prefix (PX), a mandatory element; • service code (SC), a mandatory element; •... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 4.2.2 Switching orders | A switching order is an instruction sent by the user to the exchange during a condition different from the normal call set up conditions in order to perform a call control function relating to particular SSs. The syntax is typically (R) SO. Where "R" is the Register recall signal and SO is the Switching Order, although... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 4.3 Questionnaire | The questionnaire, which had been created previously by TC-HF, was sent out to the whole ETSI membership asking for a reply before the 31st December 1997. It asked for the name and address of a contact point in the responding organization and listed 25 common SSs for PSTN, ISDN, analogue and digital mobile networks inv... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 5 Analysis of questionnaire | |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 5.1 Number of responses | When the work of analysis commenced there were 14 replies available from BT (UK), Belgacom, Cyprus Telecommunications Authority, France Telecom, Mannesman Mobilfunk, Mobiltel, Netia Telecom SA, Polska Telefonia Cyfrowa, Portugal Telecom, Telecel, Telecommunications Administration Centre Finland, Telia, TMN (Portugal) a... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 5.2 Anomalies | A number of replies were somewhat anomalous. Some respondents claimed that SSs were to be introduced shortly but gave no Code. Others gave titles that were not clear (e.g. Call Pick-up without barge-in), with or without a Code. One Country claimed it currently or would soon offer all possible SSs on ISDN but reserved t... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 5.3 Data entry | A database has been created in Microsoft Access© (Version 2) which allows the information contained in the responses to the questionnaire to be input into four Access© forms: • the first contains the name and address information supplied in the answers to the questionnaire; • the second the Network Type; • the third th... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 5.4 Definitions | In order to be able to clarify anomalies in the answers to the questionnaire it was necessary to have a clear understanding of the SS referred to; i.e. the service had to be defined. This definition needed to be unambiguous, and worded in user related terms. For this reason it was decided that each such service in the ... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 6 Categorization and rationalization | |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 6.1 Naming variations | Categorization of SSs was complicated by variations in the names given to the services and their categories in the documents referenced during the study. One of the areas in which the greatest variation of naming exists in the reference documents is that of services that result in a call intended for delivery to one te... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 6.2 Existing categorizations | A comprehensive categorization of SSs is provided in Section II of the SF Handbook [4]. The large number of categories (14) and the even larger number of sub-categories within the SF Handbook [4] means that each sub-category is likely to have few if any members. The resulting (semi-) redundant categories are a potentia... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 6.3 Adopted categorization | The adopted categorization has been based upon those categories shared between ITU-T Recommendation I.250 [26] and the ETSI GSM listed above. The "Call Restriction" category identified in ETSI's GSM standards has been included as its members have unique characteristics and it has a large number of members. "Call Deflec... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 6.4 Categorized listing | The SSs that have been identified in the analysis of the questionnaires obtained so far or in ETSI standards and reports have been fitted into the categorization defined in subclause 6.2 and are listed in table 1. The naming used in the table uses where possible the standard name for the service, modified slightly to b... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 6.5 Rationalization of SSs | As the data was collected and analysed it became clear that were some conflicts and difficulties. Part of the objective of the work was to "rationalize" the SS coding. The analysis of the questionnaire replies showed that one potential form of rationalization that proved to be impossible was to reassign a few unused co... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 7 ETSI register for SS codes | |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 7.1 Need for a register | The original ETSI STF 117 terms of reference pointed out that, with agreement from CEPT and ETNO, ETSI has a requirement to create an official register of service codes for public network based SSs. They required the analysis of the data from the questionnaires, the creation of a draft register and the preparation of t... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 7.2 CEPT register | The old CEPT register was a listing of SS titles and codes of which the latest version appears to be contained in CEPT Recommendation T/CAC 02 [5]. This was supported by and dependent upon the CEPT Handbook [4] together with Recommendations T/CAC S 10 E [6], T/SF 31 [34], T/SF 53 [35], T/SF 55 [36] and T/SF 66 [37]. Th... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 7.3 ETSI register | Having noted the format and content of the CEPT documentation it was necessary to consider what should be the content of the ETSI register. It was agreed by TC-HF that the register itself need be nothing more than a simple listing of the SS titles together with the allocated service code and/or switching order. This wo... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 7.4 Construction of the register | The current ETSI register of SS codes is given in annex A. It contains a listing of SSs, identified by their titles and associated with their allocated service code and/or switching order(s). Each service is defined in a manner which is intended to be unambiguous and worded in user related terms. Where possible the def... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 7.5 Use of the register | It is intended that the ETSI register of SS codes will provide the primary source of reference to available SSs. It will provide a standard listing of service names in English together with the recommended SS codes and switching orders. The provision of a set of clear, network independent definitions in one place shoul... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 8 Legislation and the ETSI register | The ONP framework Directive, 90/387/EEC [1] is a Directive intended to harmonize "the conditions for open and efficient access to and use of public telecommunications networks and, where applicable, public telecommunications services". It provided the basis for the Council Recommendation of the provision of harmonized ... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 9 Database | |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 9.1 Structure of the database | The database was generated using Microsoft Access© (Version 2) so as to be backwards compatible with as many users as possible. It is constructed in the form of four tables, each of the four tables being linked to the others in the form of a relational database containing: 1) a listing of service providers together wit... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 9.2 Use of the database | As the information is contained in one large relational database it may be used to extract information in many ways. Suitably filtered queries permit the listing, for example, of all of the SS names, listed in alphabetical order, together with the names of service providers offering them and the codes used. Alternative... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 10 Application procedures | |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 10.1 Procedure | The rules for the allocation of Service Codes set out in ES 201 382 [9] state that a code can only be allocated when the SS to which the code is to be assigned had been fully described. The allocation of a code can be proposed and a code can be reserved as proposed for one year. If sufficient description of the service... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 10.2 Responsibilities of applicant | A service provider who considers that he has available a new SS should first consult the ETSI register for SS codes with particular attention to the list of titles and definitions to see if such a SS has been described before. If his "new" SS is not described in the register he may then provide a definition of his serv... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 10.3 Responsibilities of the ETSI Secretariat | Upon receipt of a completed application form the ETSI Secretariat shall check it for correctness and refer back to the applicant if necessary. When a correctly completed form is received the ETSI Secretariat will check the code list for conflicts, and, if none are found, will confirm the allocation to the applicant and... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 10.4 Responsibilities of TC-HF chairman | The TC-HF Chairman will act as a central co-ordination point for the consultation process with e.g. the NA, SMG and TETRA Chairmen. The Chairman will receive from the ETSI Secretariat details of a new provisional entry. If the description provided is considered insufficient, the Chairman of TC-HF will inform the ETSI S... |
4b7e58afde7792131e1129e71f860c1b | 102 083 | 11 Conclusions and recommendations | There were disappointingly few answers to the questionnaire, so few as to cast some doubt on the validity of some of the conclusions that might be drawn from them. Although, during the activity of the task, 175 services were investigated and well over 100 defined, subsequent analysis and refinement of the information h... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.