hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.8.3 Synchronized notify and delete connection | • It must accept a notification request that is tied to and executed simultaneously with the deletion of the connection. • The notify and the delete request must be synchronized, which means that they are both either accepted or refused. 7.2.9 Requirements from Delete Connection (from MG) message and parameters |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.9.1 Delete connection forced by MG | • The MG must support the forced termination of the connection by using a variant of the DeleteConnection command. • The endpoint identifier, must be fully qualified; wildcard conventions must not be used. • It must return a reason code for the termination. ETSI ETSI TR 102 019 V1.1.1 (2002-02) 59 |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.9.2 Delete multiple or all connections | • Deletion of multiple connections, initiated from the MGC, command must be supported: - The endpoint identity must not use the "any of" wildcard. - All connections for the endpoint(s) with the CallId specified must be deleted. The command does not return any individual statistics or call parameters. • Deletion of all ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.9.3 Auditing | • It must increase system availability, by periodically "pinging" subscribers to minimize time needed to detect an outage. • It must support auditing of endpoints. • It must support auditing of connections. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.10 Requirements from audit endpoint message and parameters | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.10.1 Audit endpoint | • It must increase system availability, by periodically "pinging" subscribers to minimize time needed to detect an outage. • It must support auditing of connections. • It must support auditing of endpoints. • The "any of" wildcard convention must not be used for endpoint identity. The "all of" wildcard convention may b... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.11 Requirements from audit connection message and parameters | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.11.1 Auditing connections | • It must support auditing of individual endpoints. • Wildcards must not be used to in the endpoint identity. • If no information was requested, and the endpoint refers to a valid endpoint, the gateway must check that the connection specified exists and, if so, returns a positive response. • It must return all relevant... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.12 Requirements from restart in progress message and parameters | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.12.1 Restart in progress | • The MG must notify the MGC that an endpoint or a group of endpoints is taken out of service or is being placed back in service. • It must identify the endpoints that are taken in or out of service. The "all of" wildcard convention may be used to apply the command to a group of endpoints, for example, all endpoints th... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.12.2 Restart method types | • It must support a "graceful" restart, and ensure that the specified endpoint(s) will be taken out of service after the specified "restart delay". • It must support a "cancel-graceful", to ensure that a gateway is cancelling a previously issued "graceful" restart method for the same endpoints. • It must support a "for... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.12.3 MG restart in progress response | • The MG should send a "graceful" or "forced" restart in progress message as a courtesy to the MGC when they are taken out of service, e.g. by being shutdown, or taken out of service by a network management system, although the MGC cannot rely on always receiving such messages. • The MG must send a "restart" restart in... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13 J.tgcp: API recovery requirements | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.1 Autonomous fault detection and recovery | • In order to implement proper call signalling, the MGC must keep track of the state of the endpoint. • The MG must make sure that events are properly notified to the MGC. • Hand-over conflict resolution between separate MGC's is not provided; the MGCs must communicate with each other, and may use the auditing capabili... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.2 Endpoint/MGC recovery model | • An MGC must be identified by its domain name, not network address, for normal call handling. • Each endpoint must have only one MGC associated with it: the notified entity. • The notified entity (MGC) must be pre-provisioned; if empty, the last handling source address must be used. • Responses to commands must always... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.3 Detection of lost association | • TGCP messages run over UDP, and hence are not guaranteed and subject to loss. In the absence of a timely response commands must be repeated. • The MG must keep in memory a list of the responses that they sent to recent transactions, and a list of the transactions that are currently being executed. Recent is here defi... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.4 Repetition mechanism | • Repetition mechanism must be used to protect against: - Transmission errors. - Components failure. - MGC failure. - Fail-over (new MGC takes over seamlessly). • A repetition algorithm must detect which of the four failure occur. It needs to into account the differences between the "suspicion threshold" (Max1), and th... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.5 Repeat transmission algorithm | • The MG must always check for the presence of a new MGC. • If a new MGC is detected, the MG must direct retransmissions of any outstanding commands. • Prior to any retransmission, it must check the time elapsed since the sending of the initial datagram. • If the number of retransmissions to this MGC equals a suspicion... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.6 Repeat algorithm timers | • The MG must support exponentially increasing timers for detecting transmission, failure over, and MGC takeovers and restarts. • The MG must prevent retransmitted commands from being executed more than once using preset timer values; the sender and receiver must agree on these time values. • The default value for the ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.7 Race conditions | • It must assume the possibility of race conditions, and must support a quarantine list that buffers events for later processing and explicit detection of "desynchronization" the mismatched seizure-state due to glare for an endpoint. • It must assume the order of commands and responses may not be maintained by the tran... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.8 Quarantine list accumulation and sending | • A quarantine list must accumulate and buffer events occurring while waiting in transient notification states. • It must detect events that occur and store them in the quarantine buffer for later processing. • When the response to the notify command is received, or when a notification request is received and executed ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.9 Explicit detection and transactional semantics | • The MG must check the condition of the endpoint before responding to a notification request to avoid race condition, and return an error if the gateway is requested to notify a "seizure" transition while the circuit is already seized, or if the gateway is requested to notify an "unseize" condition while the circuit i... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.10 Ordering of commands, and treatment of disorder | • It must not assume that the underlying transport protocol guarantees the sequencing of commands sent to a gateway or an endpoint. • It may want to provide consistent operation of the endpoints using these rules: - Commands pertaining to the different endpoints or connections may be sent in parallel. - Commands may be... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.11 Restart time shifting | • In order to prevent an "avalanches" of messages after a restart, the following behaviour must be followed: - When a gateway is powered on, it must initiate restart timer to a random value, uniformly distributed between 0 and a provisional maximum waiting delay (MWD), e.g. 360 seconds. Care must be taken to avoid sync... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.12 Restart execution | • Each endpoint must send a restart in progress command to the MGC before sending any other message. • A MG must have a provisional default MGC to direct the initial restart message to. • When the collection of endpoints in a MG is managed by more than one MGC, the above procedure must take full advantage of wild-cardi... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.13 Disconnected endpoints management | • Endpoints can become disconnected when they fail to communicate with the MGC, and must follow a disconnect procedure as follows: - A "disconnected" timer is initialized to a random value between 0 and a provisionable "disconnected" initial waiting delay (Tdinit), Care must be taken to avoid synchronicity of the rando... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.13.14 Consistent return and reason codes | • All MGCP commands receive a response, and must carry a consistent return code as defined in this specification that indicates the status of the command, with a ranged based categories for response acknowledgement, provisional response, successful completion, transient error, and permanent error. • Reason-codes must b... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.1 Consistent command structure | • All commands must have a consistent structure with a Command header, which for some commands may be followed by a session description. • All responses must have a Response header, which for some commands may be followed by a session description. • Headers and session descriptions must be encoded as a set of text line... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.2 Command Header | • The command header must be composed of: - a command line identifying the requested action or verb; - the transaction identifier; - the endpoint towards which the action is requested; - the MGCP protocol version; - a set of parameter lines composed of a parameter name followed by a parameter value. • Unless otherwise ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.3 Command line | • The command line is composed of: - the name of the requested verb; - the identification of the transaction; - the name of the endpoint(s) that should execute the command (in notifications or restarts, the name of the endpoint(s) that is issuing the command); - the protocol version. ETSI ETSI TR 102 019 V1.1.1 (2002-0... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.4 Requested verb naming | • Requested verbs are encoded as four letter upper- and/or lower-case ASCII codes, and must support as a minimum the following: - CreateConnection CRCX. - ModifyConnection MDCX. - DeleteConnection DLCX. - NotificationRequest RQNT. - Notify NTFY. - AuditEndpoint AUEP. - AuditConnection AUCX. - RestartInProgress RSIP. • ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.5 Transition identity handling | • A MG must support two separate transaction identifier name spaces, one for sending and one for receiving transactions. • At a minimum, transaction identifiers for commands sent to a given trunking gateway must be unique for the maximum lifetime of the transactions within the collection of MGCs that control that MG. •... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.6 Name and protocol version coding | • The endpoint names and MGC names must be encoded as e-mail addresses, as defined in IETF RFC 821 [12]. In these addresses, the domain name identifies the system where the endpoint is attached, while the left side identifies a specific endpoint on that system. Both components must be case insensitive. • The name of no... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.7 Parameter lines | • Parameter lines must be composed of a case insensitive parameter name, which in most cases is composed of a single upper-case character, followed by a colon, a white space, and the parameter value. • Parameter names must adhere to the name code space defined in this specification. • MGs and MGCs should always provide... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.8 Requirements on parameters in parameter line | • The following parameters should adhere to the name space definitions and conventions of the present document: Response Acknowledgement, RequestIdentifier, Local Connection Options, Capabilities, Connection Parameters, Reason Codes, Connection Mode, Event/Signal Name Coding, Requested events, SignalRequests, Observed ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.9 Response header | • All responses must have a consistent structure with a responses header. • The response line must start with the response code, which is a three-digit numeric value. • The responses must follow the mandatory vs. optional vs. forbidden requirements. • Final responses must be identified. • Response parameters must adher... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.10 Retry at the protocol levels | • The retransmission timers should estimate the timer by measuring the time spent between sending a command and the return of a response. MGs must at a minimum implement a retransmission strategy using exponential back-off with configurable initial and maximum retransmission timer values. • MGs gateways should use the ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.11 Post-retry at the protocol level | • After any retransmission, the MGCP entity should do the following: - it should double the estimated value of the average delay, AAD. - it should compute a random value, uniformly distributed between 0,5 AAD and AAD. - it should set the retransmission timer (RTO) to the minimum of: the sum of that random value and N... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.12 Piggy-backing protocol | • There are cases when an MGC will want to send several messages at the same time to one or more endpoints in a gateway and vice versa. in the same UDP packets; they must be separated by a line of text that contains a single dot. • The piggy-backed messages must be processed as if they had been received in separate dat... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.13 Transaction identifier sharing | • Transaction identifiers are integer numbers in the range from 1 to 999,999,999. MGCs may decide to use a specific number space for each of the gateways that they manage, or to use the same number space for all gateways that belong to some arbitrary group. • MGC's may decide to share the load of managing a large gatew... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.14 Response acknowledgement of confirmed transactions: 3 way handshake | • A response acknowledgement parameter must be found in any command. It carries a set of "confirmed transaction-id ranges" for final responses received - provisional responses must not be confirmed. • MGCP gateways may choose to delete the copies of the responses to transactions whose id is included in "confirmed trans... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.15 Transaction confirmation algorithm | • Let termnew and termold be the endpoint-name in respectively a new command, cmdnew, and some old command. cmdold. The transaction-ids to be confirmed in cmdnew should then be determined as follows: 1) If termnew does not contain any wildcards: Unconfirmed responses to old commands where termold equals termnew. Op... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.16 Provisional response | • In some cases, transaction completion times could be significantly longer than otherwise in a network based UDP over IP. A provisional response must therefore be issued. • If a duplicate create connection or modify connection command is received, and the transaction has not yet finished executing, a provisional respo... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.14.17 Security | • If unauthorized entities could use the TGCP, they would be able to set up unauthorized calls or interfere with authorized calls. Security is not provided as an integral part of TGCP. Instead TGCP must assume the existence of a lower layer providing the actual security. • Security requirements and solutions for TGCP a... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.15 J.tgcp: Requirements from annex A, event packages | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.15.1 Event package overall | • Each package defines a package name for the package and event codes and definitions for each of the events in the package must adhere to the encoding and convention of the document. • Unless otherwise stated, all of the events/signals are detected/applied on endpoints and audio generated by them must not be forwarded... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.15.2 Continuity tone (COT) and fax tone | • Two types of COT must be supported per ITU-T Recommendation Q.724 [14]: - Continuity Tone 1 (co1): A tone at 2 010 Hz m. To conform with current continuity testing practice, the event should not be generated until the tone has been removed. The tone is of type TO - the continuity test will only be applied for the spe... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.15.3 Call tones | Events must be generated for: • Fax tone: whenever a fax communication is detected - see e.g. ITU-T Recommendation T.30 [15], or V.21 [16]. • Modem tones: whenever a modem communication is detected - see e.g. ITU-T Recommendation V.8 [17]. • Reorder tone: Reorder tone, a.k.a congestion tone, as specified in ITU-T Recom... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.15.4 Operation failure | • The operation failure event may be generated when the endpoint was asked to apply one or several signals of type TO on the endpoint, and one or more of those signals failed prior to timing out. The completion report may carry as a parameter the name of the signal that failed. • When the operation failure event is req... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.15.5 Long duration and media start events | • A long duration event must be generated when a connection has been established for more than a certain period of time. The default value is 1 hour, however this may be changed by the provisioning process; the event may be detected on a connection. When no connection is specified, the event applies to all connections ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.16 J.tgcp: Requirements from MF operator services | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.16.1 Introduction | • "MF Operator service trunk support" is a requirement in some countries (NA), not necessarily as a replacement to SS7, but as a back up to connect emergency services to the operator if there is a catastrophic failure of the link to the SS7 network; with it you still can have emergency services in the event you are cut... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.16.2 Outgoing operator service package events/signals | It may support one-way outgoing MF "Feature Group D" (FGD) Operator Services as a Package, including adhering to the naming convention of the present document and handling the following events and signals: • Call answer (ans): Call Answer occurs at the time of the OSS ANI request, i.e. the call may not necessarily have... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.16.3 MF terminating protocol package | • It may support for busy-line verification (BLV) and operator interrupt (OI) on one-way incoming MF terminating trunks dedicated to BLV and OI as a package. • When Operator Services are provided by an off-net provider, the OSS may not have access to subscriber databases to determine whether BLV and OI should be allowe... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.17 Future work | • The package construct is used to identify different types of trunks and IP connection: if operators require it, other trunk types can be added by creating new packages within the framework, including ISDN, R1, R2, etc. At the current time, this is not expected. ETSI ETSI TR 102 019 V1.1.1 (2002-02) 74 Annex A: Biblio... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 1 Scope | The present document provides the User Requirement Specifications for the Critical Communications Application needed to support Broadband Mission Critical Communications over IP communications networks such as LTE. The present document describes the functionalities which are most needed by users and the requirements th... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 2 References | |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 2.1 Normative references | Normative references are not applicable in the present document. |
a0ed040843b40578482556eee92460f5 | 102 022-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... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 3 Definitions and abbreviations | |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Base Station (BS): set of equipment on a single site (which may be more than just a radio function) mission critical broadband communications: work programme within ETSI Technical Committee TETRA and Critical Communications Evolution t... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AL Ambience Listening ASSI Alias Short Subscriber Identity AVL Automatic Vehicle Location BS Base Station CA Conventional Access CCA Critical Communications Application CCBG Critical Communications Broadband Group CCS Critical Communication Sy... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4 Critical Communications Application Requirements | |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.1 General | |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.1.0 Introduction | In order to ensure that IP communications networks such as LTE are able to meet the requirements of critical communications some changes to the 3GPP™ standards are needed. The most critical have been proposed first and are called Group Communication System Enablers (GCSE) [i.1] and Proximity Based Services (ProSE) [i.2... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.1.1 Description of Interfaces in Figures 1 to 3 | Interface 1 LTE Core Network - UE This interface is specified according to the network protocols of the underlying IP network. Where the underlying network is LTE, it consists of the 3GPP specified standardized LTE UE to EPC interfaces. ETSI ETSI TR 102 022-2 V1.2.1 (2018-01) 13 Interface 2 Infra CCA - LTE Core Network... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.2 Group Addressed Services | |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.2.0 General | This is the classic public safety and PMR situation whereby one addresses many in a voice or data call and it has the following detailed requirements: • The group call application should be able to allow or bar MU access to each group. • When the user selects a group, the MU should request access to the group and the M... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.2.1 Emergency communication | This is where in an emergency situation a user needs to send an emergency message for assistance. This is normally an alarm which is a predefined change of status tagged with location but conceivably can be voice text or video. The derived requirements are: • The MU should send an Emergency Alarm with pre-emption when ... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.2.2 Dispatcher Override | This is where a dispatcher decides to override communications to a group to share information. The derived requirements are: • The system should manage a priority level within a group associated with each member of the group for floor control in an active communication. • There should be four (4) different priority lev... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.2.3 Local Fall Back | When through accident or intent an MU cannot connect to any base station that is connected to the network it should be able to temporarily fall back into operating on the local base station or isolated group of base stations only in a fall back mode with restricted services. The requirements of this are: • If disconnec... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.3 Priority and Pre-Emption Services | In order to gain priority of access over other users or to pre-empt existing users on the system there has to be a protocol to access and use the system that allows this to occur. The following requirements apply to the 3GPP layer and to the Application layer: • The system should support at least eight different priori... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.4 Off Network Services | |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.4.0 General | Where it is not possible or desirable to connect to the network public safety users need the ability to operate terminal to terminal in "walkie-talkie" mode for voice and data. This facility is called Direct Mode Operation in PMR parlance. It is proposed that in LTE proximity services (ProSe) is used. Terminals operati... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.4.1 Public Safety Specific Requirements for Off Network Services | Whatever technology is used authorized public safety terminals should be able to exchange voice and data directly with others without use of the network. This may even be required if there is network coverage. Requirements were proposed by TCCA CCBG SA as part of their use case development and input into 3GPP the respo... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.4.2 Local network Extension | There are times when extra capacity needs to be provided locally at an incident. The requirements are: • A nomadic relay node (that might for example be mounted on a vehicle) that can be moved to an incident area, connect there to a wide area network and provide local coverage and capacity extension. • Systems support ... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.5 Calling/Talking Party Identity Restriction | • Talking Party Identity restriction, i.e. suppression of the talking party identity to provide anonymity, is occasionally required for individual and group calls within the CCA, or in 'ISI-equivalent' calls between CCAs in order to, for example, protect covert users. • Similarly it can be anticipated that Calling Part... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.6 Interoperability with Legacy Systems | The System should be able to interwork with narrow-band systems such that: • An MU should be able to communicate by a gateway between systems with devices used in the narrow-band systems. • An MU should be able to send and receive data (e.g. status messages, text, location, IP data) to/from devices used in the narrowba... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.8 Dispatching - a Video Case | Included as a line in group addressed calls plus. Based on the separation between the 3GPP domain and the Application layer, the following requirements apply to the Application layer: • The system should be capable of managing different types of media for the same group. • The system should be capable of managing indep... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.9 Video Briefing | This is where video/multi-media is pushed to a group to brief them. Covered above. |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.10 Net Preference | Requirement is on 3GPP only. |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 4.11 Dual Watch | There is a need when in ProSe to monitor for GCSE and be able to switch over. Furthermore: • The MU should be able to switch between GCSE_LTE and ProSE modes via user interaction with the radio. • The MU should be able to listen simultaneously to a set of GCSE_LTE and ProSE communications. • All MU should be able to de... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 5 Voice Requirements | |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 5.0 General | Covered in group addressed calls to a large extent. The need is for clear, high quality audio in a variety of environments both with an earpiece and without. The audio has to be capable of being sufficiently loud that communications can be understood in noisy environments and when the MU is worn on the waist. At the sa... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 5.1 Intelligibility in Noisy Environments | There is a need to be able to make and receive clear communications on an MU when standing adjacent to vehicles with sirens operating and/or helicopters and aircraft with their engines running. For TETRA this was assisted by the use of a specific CODEC and something similar is needed here. There is also a need to be ab... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 5.2 Call Set up Time | Covered under group addressed calls. |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 6 Security | The CCA has to address the facilitation of end to end encryption between MUs so that coupled with the air interface encryption of LTE a similar level of encryption to that already available on mission critical communications can be achieved. The algorithms used for encryption should be capable of being upgraded over ti... |
a0ed040843b40578482556eee92460f5 | 102 022-2 | 7 Priorities for Functionality | At the TCCA CCBG meeting in Amsterdam in June 2013 attendees were asked what their priorities for functionality were given that there would probably be a phased release. The questions posed are summarized in figures 5 and 6. Figure 5: Questions for Users (slide 1 of 2) (extract of slides with the consent of TCCA) ETSI ... |
20cc200c31fe90200983950f4b7826ca | 102 015 | 1 Scope | The present document gives the results of a review of the current TC-HF deliverables on Supplementary Services and makes recommendations for improvement. |
20cc200c31fe90200983950f4b7826ca | 102 015 | 2 References | For the purposes of this Technical Report (TR), the following references apply: [1] ETSI TR 102 083: "Human Factors (HF); Supplementary service codes for use in public network services". [2] ETSI ES 201 382: "Human Factors (HF); Procedure for registering a supplementary service code". [3] ETSI ETR 261-1: "Human Factors... |
20cc200c31fe90200983950f4b7826ca | 102 015 | 3 Definitions and abbreviations | |
20cc200c31fe90200983950f4b7826ca | 102 015 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: centrex: centralized PBX service provided by a local exchange for private (business) customers service code: two or three digit string used within a user command dialogue to identify a Supplementary Service supplementary service: addit... |
20cc200c31fe90200983950f4b7826ca | 102 015 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CEPT European Conference of Postal and Telecommunications Administrations GSM Global System for Mobile communication ISDN Integrated Services Digital Network MMI Man-Machine Interface PBX Private Branch eXchange PSTN Public Switched Telephone ... |
20cc200c31fe90200983950f4b7826ca | 102 015 | 4 Current HF deliverables | |
20cc200c31fe90200983950f4b7826ca | 102 015 | 4.1 TR 102 083 | TR 102 083 [1], Supplementary service codes for use in public network services, is a report that describes the use of those service codes for supplementary services used in public networks that were identified in the answers to a questionnaire sent out to the ETSI membership. The document provides categorized listing o... |
20cc200c31fe90200983950f4b7826ca | 102 015 | 4.2 ES 201 382 | ES 201 382 [2], "Procedure for registering a supplementary service code", is a short document that provides a brief description of the use of supplementary service codes and sets out the procedures to be followed when applying for a code for use in a public network. It provides the necessary application form for regist... |
20cc200c31fe90200983950f4b7826ca | 102 015 | 4.3 TC HF Web site | Under the link "Supplementary Service Codes", the ETSI TC HF web site provides a brief definition and description of the use of supplementary service codes. It provides a link to a pdf document described as a report that provides an alphabetical listing of the supplementary services that require codes. Another link is ... |
20cc200c31fe90200983950f4b7826ca | 102 015 | 4.4 Other TC HF documents | ETR 261-1, Assessment and definition of a harmonized minimum man-machine interface (MMI) for accessing and controlling public network based supplementary services; Part 1: "General approach and summary of findings" [3], presents the results of research to develop a harmonized MMI particularly for supplementary services... |
20cc200c31fe90200983950f4b7826ca | 102 015 | 5 Proposals for improvement | |
20cc200c31fe90200983950f4b7826ca | 102 015 | 5.1 TR 102 083 | Although the listing of supplementary service codes in TR 102 083 [1] is currently slightly out of date, as the document is a historical record of the results of a questionnaire it should not be changed. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.