hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.1.1 Boolean | The IDL boolean type is mapped to the interface org.etsi.ttcn.tri.TriBoolean, so that objects implementing this interface can act as holder objects. The following interface is defined for org.etsi.ttcn.tri.TriBoolean: // TriBoolean package org.etsi.ttcn.tri; public interface TriBoolean { public void setBooleanValue(boo... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.1.2 String | The IDL string type is mapped to the java.lang.String class without range checking or bounds for characters in the string. All possible strings defined in TTCN-3 can be converted to java.lang.String. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2 Structured Type Mapping | The TRI IDL description defines user defined types as native types. In the Java language mapping these types are mapped to Java interfaces. The interfaces define methods and attributes being available for objects implementing this interface. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.1 TriPortIdType | TriPortIdType is mapped to the following interface: // TRI IDL TriPortIdType package org.etsi.ttcn.tri; public interface TriPortId { public String getPortName(); public TriComponentId getComponent(); public boolean isArray(); public int getPortIndex(); } Methods - getPortName() Returns the port name as defined in the T... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.2 TriPortIdListType | TriPortIdListType is mapped to the following interface: // TRI IDL TriPortIdListType package org.etsi.ttcn.tri; public interface TriPortIdList { public int size(); public boolean isEmpty(); public java.util.Enumeration getPortIds(); public TriPortId get(int index); } Methods - size() Returns the number of ports in this... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.3 TriComponentIdType | TriComponentIdType is mapped to the following interface: // TRI IDL TriComponentIdType package org.etsi.ttcn.tri; public interface TriComponentId { public String getComponentId(); public String getComponentTypeName(); public TriPortIdList getPortList(); public boolean equals(TriComponentId port); } Methods - getCompone... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.4 TriMessageType | TriMessageType is mapped to the following interface: // TRI IDL TriMessageType package org.etsi.ttcn.tri; public interface TriMessage { public byte[] getEncodedMessage(); public void setEncodedMessage(byte[] message); public boolean equals(TriMessage message); } Methods - getEncodedMessage() Returns the message encoded... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.5 TriAddressType | TriAddressType is mapped to the following interface: // TRI IDL TriAddressType package org.etsi.ttcn.tri; public interface TriAddress { public byte[] getEncodedAddress(); public void setEncodedAddress(byte[] address); public boolean equals(TriAddress address); } Methods - getEncodedAddress() Returns the encoded address... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.6 TriSignatureIdType | TriSignatureIdType is mapped to the following interface: // TRI IDL TriSignatureIdType package org.etsi.ttcn.tri; public interface TriSignatureId { public String getSignatureName(); public void setSignatureName(String sigName); public boolean equals(TriSignatureId sig); } ETSI ETSI TR 102 043 V1.1.1 (2002-04) 29 Method... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.7 TriParameterType | TriParameterType is mapped to the following interface: // TRI IDL TriParameterType package org.etsi.ttcn.tri; public interface TriParameter { public String getParameterName(); public void setParameterName(String name); public int getParameterPassingMode(); public void setParameterPassingMode(in mode); public byte[] get... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.8 Methods | - getParameterName() Returns the parameter name as defined in the TTCN-3 specification. - setParameterName(String name) Sets the name of this TriParameter parameter to name. - getParameterPassingMode() Returns the parameter passing mode of this parameter. - setParameterPassingMode(int mode) Sets the parameter mode of t... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.9 TriParameterPassingModeType | TriParameterPassingModeType is mapped to the following interface: // TRI IDL TriParameterPassingModeType package org.etsi.ttcn.tri; public interface TriParameterPassingMode { public final static int TRI_IN = 0; public final static int TRI_INOUT = 1; public final static int TRI_OUT = 2; } Constants - TRI_IN Will be used... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.10 TriParameterListType | TriParameterListType is mapped to the following interface: // TRI IDL TriParameterListType package org.etsi.ttcn.tri; public interface TriParameterList { public int size(); public boolean isEmpty(); public java.util.Enumeration getParameters(); public TriParameter get(int index); public void clear(); public void add(Tr... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.11 TriExceptionType | TriExceptionType is mapped to the following interface: // TRI IDL TriExceptionType package org.etsi.ttcn.tri; public interface TriException { public byte[] getEncodedException(); public void setEncodedException(byte[] message); public boolean equals(TriException exc); } Methods - getEncodedException() Returns the excep... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.12 TriTimerIdType | TriTimerIdType is mapped to the following interface: // TRI IDL TriTimerIdType package org.etsi.ttcn.tri; public interface TriTimerId { public String getTimerName(); public boolean equals(TriTimerId timer); } Methods - getTimerName() Returns the name of this timer identifier as defined in the TTCN-3 specification. In c... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.13 TriTimerDurationType | TriTimerDurationType is mapped to the following interface: // TRI IDL TriTimerDurationType package org.etsi.ttcn.tri; public interface TriTimerDuration { public double getDuration(); public void setDuration(double duration); public boolean equals(TriTimerDuration duration); } Methods - getDuration() Returns the duratio... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.14 TriFunctionIdType | TriFunctionIdType is mapped to the following interface: // TRI IDL TriFunctionIdType package org.etsi.ttcn.tri; public interface TriFunctionId { public String toString(); public String getFunctionName(); public boolean equals(TriFunctionId fun); } |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.15 Methods | - toString() Returns the string representation of the function as defined in TTCN-3 specification. - getFunctionName() Returns the function identifier as defined in the TTCN-3 specification. - equals(TriFunctionId fun) Compares fun with this TriFunctionId for equality. Returns true if and only if both functions have th... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.16 TriTestCaseIdType | TriTestCaseIdType is mapped to the following interface: // TRI IDL TriTestCaseIdType package org.etsi.ttcn.tri; public interface TriTestCaseId { public String toString(); public String getTestCaseName(); public boolean equals(TriTestCaseId tc); } Methods - toString() Returns the string representation of the test case a... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.17 TriActionTemplateType | TriActionTemplateType is mapped to the following interface: // TRI IDL TriActionTemplateType package org.etsi.ttcn.tri; public interface TriActionTemplate { public String toString(); public byte[] getEncodedTemplate(); public boolean equals(TriActionTemplate actionTemplate); } Methods - toString() Returns the string re... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.2.18 TriStatusType | TriStatusType is mapped to the following interface: // TriStatusType package org.etsi.ttcn.tri; public interface TriStatus { public final static int TRI_OK = 0; public final static int TRI_ERROR = -1; public String toString(); public int getStatus(); public void setStatus(int status); public boolean equals(TriStatus st... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.4 Constants | Within this Java language mapping constants have been specified. All constants are defined public final static and are accessible from every object from every package. The constants defined within this clause are not defined with the IDL section. Instead they result from the specification of the TRI IDL types marked as... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.5 Mapping of Interfaces | The TRI IDL definition defines two interfaces, the triCommunication and the triPlatform interface. As the operations are defined for different directions within this interface, i.e. some operations can only be called by the TTCN-3 Executable (TE) on the System Adapter (SA) while others can only be called by the SA on t... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.5.1 Out and InOut Parameter Passing Mode | The following IDL types are used in out or inout parameter passing mode: • TriParameter • TriParameterList • TriBoolean • TriTimerDuration In case they are used in out or inout parameter passing mode objects of the respective class will be passed with the method call. The called entity can then access methods to set th... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.5.2 triCommunication - Interface | The triCommunication interface is divided into two sub interfaces, the triCommunicationSA interface, defining calls from the TE to the SA and the triCommunicationTE interface, defining calls from the SA to the TE. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.5.2.1 triCommunicationSA | The triCommunicationSA interface is mapped to the following interface: // TriCommunication // TE -> SA package org.etsi.ttcn.tri; public interface TriCommunicationSA { // Reset Operation // Ref: TRI-Definition 7.5.1 TriStatus triSAReset(); // Connection handling operations // Ref: TRI-Definition 7.5.2 public TriStatus ... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.5.2.2 triCommunicationTE | The triCommunicationTE interface is mapped to the following interface: // TriCommunication // SA -> TE package org.etsi.ttcn.tri; public interface TriCommunicationTE { // Message based communication operations // Ref: TRI-Definition 7.5.6 public void triEnqueueMsg(TriPortId tsiPortId, TriAddress sutAddress, TriComponen... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.5.3 triPlatform - Interface | The triPlatform interface is divided in two sub interfaces, the triPlatformPA interface, defining calls from the TE to the PA and the triPlatformTE interface, defining calls from the PA to the TE. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.5.3.1 TriPlatformPA | The triPlatformPA interface is mapped to the following interface: // TriPlatform // TE -> PA package org.etsi.ttcn.tri; public interface TriPlatformPA { // Ref: TRI-Definition 7.6.1 public TriStatus triPAReset(); // Timer handling operations // Ref: TRI-Definition 7.6.2 public TriStatus triStartTimer(TriTimerId timerId... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.5.3.2 TriPlatformTE | The triPlatformTE interface is mapped to the following Java interface: // TriPlatform // PA -> TE package org.etsi.ttcn.tri; public interface TriPlatformTE { // Ref: TRI-Definition 7.6.6 public void triTimeout(TriTimerId timerId); } |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.6 Optional Parameters | Clause 7.4 defines that a reserved value shall be used to indicate the absence of an optional parameter. For the Java language mapping the Java null value shall be used to indicate the absence of an optional value. For example if in the triSend operation the address parameter shall be omitted the operation invocation s... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.7 TRI Initialization | All methods are non-static, i.e. operations can only be called on objects. As the present document does not define concrete implementation strategies of TE, SA, and PA the mechanism how the TE, the SA, or the PA get to know the handles on the respective objects is out of scope of the present document. Tool vendors shal... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.8 Error Handling | Beside the error handling as defined in clause 7.2 no additional error handling is defined within this Java language mapping. In particular no exception handling mechanisms are defined. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 9 ANSI C Language Mapping | |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 9.1 Introduction | This clause defines the TRI ANSI-C language mapping for the abstract data types specified in clause 7.3. For basic IDL types, the mapping conforms to OMG recommendations. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 9.2 Names and scopes | • C parameter identifiers shall start with a lower case letter, and subsequent part building the parameter identifier start with a capital letter. For example the IDL parameter SUTaddress maps to sutAddress in C. • Abstract data type identifiers in C are omitting the trailing Type used in the IDL definition. For exampl... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 9.2.1 Abstract Type Mapping | TRI ADT ANSI C Representation Notes and comments TriActionTemplate BinaryString TriAddress BinaryString TriComponentId typedef struct TriComponentId { BinaryString compInst; QualifiedName compType; } TriComponentId; compInst is for component instance. TriException BinaryString TriFunctionId QualifiedName TriMessage Bin... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 9.2.2 ANSI C Type Definitions | C ADT Type definition Notes and comments BinaryString typedef struct BinaryString { unsigned char* data; long int bits; void* aux; } BinaryString; data is a non-null-terminated string. bits is the number of bits used in data. bits value -1 is used to denote omitted value. The aux field is for future extensibility of TR... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 9.2.3 IDL Type Mapping | IDL type ANSI C Representation Notes and comments Boolean unsigned char From OMG IDL to C++ mapping String char* From OMG IDL to C++ mapping |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 9.2.4 TRI Operation Mapping | IDL Representation ANSI C Representation TriStatusType triSAReset() TriStatus triSAReset() TriStatusType triExecute (in TriTestCaseIdType testCaseId, in TriPortIdListType tsiPortList) TriStatus triExecute (const TriTestCaseId* testCaseId, const TriPortIdList* tsiPortList) TriStatusType triMap (in TriPortIdType compPort... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 9.3 Memory Management | The called party is responsible for saving any data in its own scope if the data is to be used after function termination. In other words, the calling party does not guarantee that a pointer is valid after the function call. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 9.4 Error handling | No error handling has been defined for this mapping. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10 Use Scenarios | This clause contains use scenarios that should help users of the TRI and tool vendors providing the TRI understand the semantics of the operations defined within the present document. Three scenarios are defined in terms of Message Sequence Charts (MSC). A scenario consists of a TTCN-3 code fragment that uses TTCN-3 co... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10.1 First Scenario | The first scenario shows some TTCN-3 timer operations, i.e. start and timer running, message based communication operations, i.e. send and receive, as well as connection handling operations, i.e. map and unmap. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10.1.1 TTCN-3 Fragment | module triScenario1 { external function MyFunction(); type port PortTypeMsg message { inout integer } type component MyComponent { port PortTypeMsg MyPort; timer MyTimer } type component MyTSI { port PortTypeMsg PCO1; } testcase scenario1() runs on MyComponent system MyTSI { MyPort.clear; MyPort.start; MyTimer.start(2)... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10.1.1.1 Message Sequence Chart | Figure 4: Use Scenario 1 ETSI ETSI TR 102 043 V1.1.1 (2002-04) 45 |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10.2 Second Scenario | The second example shows a similar scenario which also uses timed procedure based communication operations which are initiated by the test component MyComponent. In this example MyComponent is assumed to run as the MTC. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10.2.1 TTCN-3 Fragment | module triScenario2 { signature MyProc ( in float par1, inout float par2) exception(MyExceptionType); type record MyExceptionType { FieldType1 par1, FieldType2 par2 } type port PortTypeProc procedure { out MyProc } type component MyComponent { port PortTypeProc MyPort; timer MyTimer = 7 } testcase scenario2() runs on M... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10.2.1.1 Message Sequence Chart | Figure 5: Use Scenario 2 ETSI ETSI TR 102 043 V1.1.1 (2002-04) 47 |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10.3 Third Scenario | Use scenario 3 shows the reception of a procedure call as well as a reply and raising of an exception based on this received call. Again MyComponent is assumed to run as the MTC. FieldType1, FieldType2, p1, and p2 are assumed to be defined elsewhere. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10.3.1 TTCN-3 Fragment | module triScenario3 { signature MyProc ( in float par1, inout float par2) exception(MyExceptionType); type record MyExceptionType { FieldType1 par1, FieldType2 par2 } type port PortTypeProc procedure { in MyProc } type component MyComponent { port PortTypeProc MyPort; timer MyTimer = 3 } testcase scenario3(integer x) r... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 10.3.1.1 Message Sequence Chart | Figure 6: Use Scenario 3 ETSI ETSI TR 102 043 V1.1.1 (2002-04) 49 Annex A: IDL Summary This clause summarizes the IDL definition of TRI operations as defined in clause 7. // ************************************************************************* // Interface definition for the TTCN-3 Runtime Interface // ************... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 1 Scope | The present document presents the results of ongoing work to harmonize existing ETSI Technical Specification (TS) on policy requirements for certification authorities (TS 101 456 [1] and TS 102 042 [2]) with other internationally recognized standards and related activities. The aim of the present document is to identif... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ETSI TS 101 456: "Policy requirements for certification authorities issuing qualified certificates". [2] ETSI TS 102 042: "Policy requirements for certification authorities issuing public key certificates". [3] IETF RFC 2527: "Internet X... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 3 Definitions and abbreviations | |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: certificate: public key of a user, together with some other information, rendered un-forgeable by encipherment with the private key of the certification authority which issued it NOTE: See ITU-T Recommendation X.509 | ISO/IEC 9594-8 [1... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABA American Bar Association AICPA American Institute of Certified Public Accountants ANSI American National Standards Institute APEC Asia-Pacific Economic Community CA Certification Authority CEN Comité Européen de Normalisation CICA Canadian... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 4 Objective | The major objective of the present document on international certificate policy harmonization is achieving harmonization between other internationally recognized policies and other policy requirements which are not constrained by the European legal framework, on the one side with, on the other side, CA policy requireme... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 5 Relevant activities | |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 5.1 Introduction | There are a wide range of activities relating to certificate policies and practices which have some international relevance. This clause does not aim to provide a comprehensive list of relevant activities; rather it identifies those which are most closely related to TS 101 456 [1] (referred to in the present document a... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 5.2 IETF PKIX policy and practices framework | The Internet Engineering Task Force (IETF) Public Key Infrastructure X.509 (PKIX) working group published in March 1999 a Certificate Policies and Certification Practices Framework - RFC 2527 [3]. This provides a structure for the specification of certificate policies and certification practice statements. RFC 2527 [3]... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 5.3 ABA PKI assessment guidelines | The American Bar Association (ABA) Information Security Committee (ISC) has produced guidelines for the assessment of a public key infrastructure called the PKI Assessment Guidelines (PAG) [7]. The PAG provides general guidance particularly from the legal perspective. However, as a general guide the PAG does not identi... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 5.4 US Federal PKI | The United States federal government has established PKI infrastructure to support inter-departmental and inter-governmental security called the Federal PKI (FPKI). This is based around a Bridge CA which supports mapping between approved PKI domains. The approval is based around a "Federal Bridge CA Certificate Policy"... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 5.5 APEC TEL eSTG | The eSecurity Task Group (eSTG) is a task group of the Business Facilitation Steering Group of the APEC Telecommunications and Information Working Group (APEC TEL) - APEC is the Asia-Pacific Economic Community. eSTG does not have a formal charter but has two basic functions: • the security of information infrastructure... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 5.6 ANSI X9.79 - PKI policy and practices framework | ANSI developed a framework for PKI policies and practices aimed at the financial services around the time of the development of TS 101 456 [1]. An annex to this ANSI document (ANSI X9.79 [8], annex B) includes specific requirements for PKI policies and practices, which have similar objectives to TS 101 456 [1]. An earl... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 5.7 ISO TC68 - PKI policy and practices framework | ANSI proposed a new work item to ISO TC68 (standards for the financial services sector) for a Public Key Infrastructure for Financial Services - Practices and Policy Framework [9] based on ANSI X9.79 [8]. TC68 members agreed to this work item in the latter part of 2001 but with a number of European members requesting t... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 5.8 OECD | The OECD Working Party on Information Security and Privacy (WPISP) is looking at issues of authentication around cross border electronic transactions. As part of this work ETSI provided a note on the need for harmonized approval criteria for Trust Service Providers, as yet it is not clear whether there will be any acti... |
d762ee98c1d43f3d871a42240af88192 | 102 040 | 6 Recommendations | Members of ETSI technical committee on Electronic Signatures and Infrastructures have been active in working with other international activities relating the certificate policy requirements in other parts of the world, and have been successful in influencing these activities to maximize the harmonization with the ETSI ... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 1 Scope | The present document provides the user requirements for a TETRA-based AGA service. The present document is applicable to the specification of TETRA Release 2 equipment. The AGA User Requirements Specification contained in the present document are based on a study by EPT WG1 which reviewed previous user requirements doc... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ETSI TR 102 021-1: "Terrestrial Trunked Radio (TETRA); User Requirement Specification TETRA Release 2; Part 1: General Overview". [2] ETSI TR 102 021-2: "Terrestrial Trunked Radio (TETRA); User Requirement Specification TETRA Release 2; ... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 3 Definitions and abbreviations | |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: aircraft: fixed wing aeroplane or helicopter air MS: TETRA mobile station certified for use in aircraft TETRA Release 2: work Programme with new terms of reference within ETSI Project TETRA to enhance the services and facilities of TET... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 3.2 Abbreviations | For the purposes of the present document the following abbreviations apply: AGA Air - Ground - Air BS Base Station DMO Direct Mode Operation HLA Home Location Area LA Location Area MAC Medium Access Control MS Mobile Station PAMR Public Access Mobile Radio PEI Peripheral Equipment Interface PDU Protocol Data Unit RF Ra... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4 User Requirement Specification | |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.1 General Requirements | The requirements for an Air to Ground service can be summarized as: 1) Air terminals should have the same TETRA services (Mobility Management, voice and data) as terrestrial terminals. 2) The air terminal may need to be approved by the local Aviation Authority. 3) There is a need for RF co-ordination on networks in the... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.2 Air to Ground Implementation | The implementation of an air service must use standard TETRA V+D air interface, base stations and terminals with only slight modifications to take account of the special needs. This approach will mean that all the services that are available to terrestrial users are also available to air users. It is also a practical a... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3 Signalling | |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3.1 General | In general, the air interface signalling will be identical to that of a terrestrial TETRA terminal. The only difference will be the need for some cell reselection modifications and to take account of the low propagation losses in free air. |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3.2 Cell Reselection | To employ a cellular infrastructure for the air service, the consideration of cell reselection signalling has lead to suggested modifications in air interface operation. The changes are made in the TIPs rather than the air interface itself. The TETRA air interface standard was optimized for terrestrial operation where ... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3.3 Moving from terrestrial cell to air cell | |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3.3.1 General | The air MS must register on the air cells as soon as possible after take-off to guard against the air MS producing co-channel interference on the rest of the terrestrial network. The Air to Ground TIP [11] includes this requirement. To this end there are two proposals to encourage air MSs to look for air cells in prefe... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3.3.2 Preferred location area | In this approach the MS is programmed with a list of air cell location areas representing "preferred Location Areas" or Home Location Areas (HLA). During operation the MS continually looks at the neighbour cell information broadcast looking for cells that are members of this list. When a MS sees a cell, which is a memb... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3.3.3 Highly preferred subscriber class | In this approach there are two provisioning items. The MS is programmed with a subscriber class representing air cell terminals and the air cells are programmed to broadcast support of the same subscriber class. The standard allows for MS provisioning of subscriber class to be temporarily modified over the air interfac... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3.4 Moving from air cell to air cell | This mode of handover is the one most likely to be subject to limitations of a cellular structure used in the terrestrial network. Such a structure relies on the RSSI reducing significantly as the MS moves away from a BS and behind obstructions. Due to line of sight free-space propagation characteristics, it is unlikel... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3.5 Moving from air cell to terrestrial cell | In this case the air MS must hold on to the air cell as long as possible. To effect satisfactory handover performance the air cell must have some terrestrial cells in its neighbour cell list. These will need optimization otherwise the list will be too long. It is suggested that a list of important terrestrial cells (e.... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.3.6 Neighbour cell monitoring | The air MS has a particular interest in rapid neighbour monitoring when it is registered on a terrestrial cell as the MS is searching for an air cell (when it takes off). The air MS could be defined to scan the air cell more often than the terrestrial cell. This is not a standards change but the users consider that thi... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.4 Wide band noise | The use of a different air to ground frequency sub-band is expected to eliminate co-channel interference with the terrestrial network. In considering wide band interference the effects on the terrestrial network of air MSs and the inverse effect of terrestrial BSs on air MSs should be considered. It was concluded that ... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.5 Large radius cells | |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.5.1 General | The current range of a TETRA cell is limited at 58 km by the size of the gap between adjacent slots (see EN 300 392-2 [9] clauses 6.4.5 and 9.4.4). The extension of range in an air to ground network has benefits in two areas: 1) The handover performance will improve; 2) There are benefits in RF planning. The improvemen... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.5.2 Reduced ramp up and ramp down timing | It is concluded that the only practical option is to increase the guard time by reducing the ramp up and ramp down timing of the MS. An increase of 6 bits in the guard time would give a total range up to 83 (58 + 25) km. It is worth noting that an MS with faster ramp timings would still be within the standard as there ... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.5.3 Radio frequency planning | The improvement in RF planning to be gained from an increase in cell radius from 58 km to 83 km could give a maximum reduction in cells by a factor of 2 (83/58 squared). The resultant distance between BSs (144 km) gives rise to the possibility of a frequency reuse pattern of 7. This is especially important for those op... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.5.4 Border cell configuration | To help co-ordination and cross border interference reduction there are some techniques that would help to reduce the power of the MS near the borders. This does not use new signalling but rather a configuration of existing signalling. The BS broadcast could be used to reduce the maximum power that can be transmitted b... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.5.5 Other impacts | There would be other impacts from an increase in the maximum cell radius.They are not new requirements but rather derived from the main requirements. 1) The BS must be able to detect the training sequence from the "later" bursts from the distant MS. That is the training sequence may appear starting at bits 254 - 274 fr... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.6 DMO | Direct Mode will not be used as a general AGA solution. An example of when DMO may be used could be communication from a helicopter to emergency services on the ground prior to landing at an incident in an area where there is no terrestrial coverage or for special operations which do not wish to use the TMO network. Th... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 4.7 Failure modes | The failure of an MS in an aircraft would be the same as the failure of a terrestrial MS. The situation is different if a BS from the air to ground overlay network fails. In these conditions, it is likely that air MSs registered on the failed cell will choose a terrestrial BS and register to that cell. This is because ... |
a34f959374329abfb729f6d7c24dfaff | 102 021-8 | 5 Conclusions on options | A cell extension to 83 km will meet the requirements for AGA operation. The reduction in MS ramp up and ramp down times is seen as a technically possible way to achieve such an increase in cell radius. It is suggested that the "highly preferred subscriber class" is the better way to indicate an air cell and to encourag... |
0558300fed6e8df498d6967774046a9c | 102 021-7 | 1 Scope | The present document contains the User Requirements Specifications (URS) which are described in non-technical terms. Although high level requirements are proposed by the present document, it is considered restrictive to mandate particular security implementations at this point, until a revised threat analysis has been ... |
0558300fed6e8df498d6967774046a9c | 102 021-7 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
0558300fed6e8df498d6967774046a9c | 102 021-7 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
0558300fed6e8df498d6967774046a9c | 102 021-7 | 2.2 Informative references | 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] ETSI ES 202 109: "Terrestrial Trunked Radio (TETRA); Security; Synchronization mechanism for end-to-end encryption". |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.