TIA - Telecommunications Industry Association

TIA EIA-411-A

Wed, 01 Jan 1986 00:00:00 GMT

TIA EIA-411-A; Electrical and Mechanical Characteristics of Earth Station Antennas for Satellite Communications TIA - Telecommunications Industry Association PREFACE
The objectives of EIA-411-A, Electrical and Mechanical Characteristics of Earth Station Antennas for Satellite Communications," are the following:
(a) to provide standard terms, definitions, and concepts for the mechanical and RF design of earth station antennas, and
(b) to offer a standard methodology for the verification of RF performance compatible with current technology and test equipment.
The standards are not intended to replace or supersede applicable codes. The information contained in these standards was obtained from information and data as referenced and noted herein and represents, in the judgment of the subcommittee, the accepted industry practices for definition and standards for the design and testing of satellite communications antennas.
Specific values for parameters such as gain, sidelobe level, safe wind loading etc., are not given because the acceptable values depend on the application and the system configuration.
This industry standard does provide users as well as manufacturers with a common language for the preparation of specifications, proposals, and test routines.

TIA TIA-136-750

Tue, 01 Jan 2013 00:00:00 GMT

TIA TIA-136-750; TDMA Cellular/PCS General UDP Transport Service (GUTS) TIA - Telecommunications Industry Association Purpose and Scope
The General UDP Transport Service, GUTS, is a general-purpose application data delivery service. The General UDP Transport Service increases flexibility of adding new value-added features, and creates an open platform for the creation of both consumer and corporate information services via wireless Internet and intranet access. GUTS utilizes the Internet Standard User Datagram Protocol (UDP) to specify the intended application, or port. The General UDP Transport Service provides a new teleservice specially designed to require minimum protocol overhead allowing more room for the data payload (i.e., GUTS is not based on the Short Messaging Service). The General UDP Transport Service supports both mobile-terminated (point-to-point and broadcast), as well as mobile-originated services. The General UDP Transport Service assumes no specific encoding of the application datagrams, and transparently passes the data to the application specified by the destination port. GUTS may also be used to integrate many current TIAEIA-136 features into the common user interface of a browser. For example, GUTS may be used to support one-way and mobile-originated "Cellular Messaging Teleservice (CMT)"-like messaging and other services associated with the traditional CMT service (e.g., bulk messaging), or "broadcast" services. In effect, GUTS combined with a browser application can provide a common and consistent user interface for both enhanced and existing TIAEIA-136 services.
The General UDP Transport Service can carry essentially any higher layer application protocol. For mobile-terminated services, the messages defined in the General UDP Transport Service carry UDP datagrams from an application in the network (in this architecture, the Application Server or Gateway), to the appropriate application in the mobile station (for example, an HDML Browser). Similarly, for mobile-originated services, the messages defined in the General UDP Transport Service carry UDP datagrams from an application in the mobile station (for example, the HDML Browser), to an application in the network (the Application Server or Gateway). These applications are defined by appropriate UDP ports. Port assignments are necessary for the UDP portion of the protocol. These port assignments may be outside of the UDP Well-Known port assignments, as it can be envisioned that existing applications defined in the Well-Known port assignments may be used in the General UDP Transport Service. The port assignments inform the receiving end of the UDP datagram which application the data should be delivered to. On a mobile-terminated GUTS Data message, the mobile station delivers the datagram to the GUTS application. The Destination Port specifies the particular application within GUTS for which the UDP Data should be delivered. For example, if the Destination Port specifies the port for the HDML/WAP Browser, then the GUTS shall deliver the data to the HDML/WAP Browser, as shown below:

TIA TSB-87-2018

Tue, 01 Jan 2002 00:00:00 GMT

TIA TSB-87-2018; Cellular Digital Packet Data System Specification - Part 2018 M-ES EID Assignment TIA - Telecommunications Industry Association Introduction
This Part presents a tutorial on the usage of the Equipment IDentifier (EID) for manufacturers of M-ESs. This Part also provides a template application form to be used in acquiring a manufacturer identifier from the Institute of Electrical and Electronic Engineers (IEEE).
The IEEE Registration Authority assigned manufacturer identifier comprises the high-order 24 bits of the EID defined in IS-732. In the EID, the manufacturer identifier is followed by a 24-bit unique CDPD M-ES number assigned by the manufacturer. The EID is used to guarantee that Temporary Equipment Identifier (TEI) requests sent by any two M-ESs are different. It appears in the following messages:
• IDENTITY REQUEST Message [IS-732-403]
• IDENTITY ASSIGN Message [IS-732-403]
• IDENTITY CHECK Response Message [IS-732-403].
The EID is further optionally used in the following Mobile Network Registration Protocol (MNRP) Messages:
• END SYSTEM HELLO [IS-732-507]
• END SYSTEM BYE [IS-732-507].
The EID is further optionally used in the following Mobile Network Location Protocol (MNLP) Messages:
• REDIRECT REQUEST [IS-732-501]
• REDIRECT FLUSH [IS-732-501]
• REDIRECT EXPIRY [IS-732-501].

TIA J-STD-102

Sat, 01 Jan 2011 00:00:00 GMT

TIA J-STD-102; JOINT ATIS/TIA CMAS FEDERAL ALERT GATEWAY TO CMSP GATEWAY INTERFACE TEST SPECIFICATION TIA - Telecommunications Industry Association This Standard defines operational testing procedures for the communications between the Federal Alert Gateway and the Commercial Mobile Service Provider (CMSP) Gateway over the C-Interface. This includes operational testing of all processing functionality within the FEMA-administered Commercial Mobile Alert Service (CMAS) entities and the CMSP-administered CMAS entities that directly impacts communications over the C-Interface. Operational testing of all other processing within the FEMA and CMSP entities including the CMSP infrastructure is beyond the scope of this Standard.
Purpose
The purpose of interface testing is to evaluate whether systems or components transmit data and control information correctly to each other. In addition, the tests defined in this Standard may be used during regression testing when updates are made to either the Federal Alert Gateway or the CMSP Gateway.
Specifically, the Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Testing Specification defines a set of tests to verify the following minimal set of functionality during interface and regression testing:
• Ability to complete the C-Interface startup procedures:
• Ability to bring up the IPSec tunnel.
• Ability to bring up the TCP/IP connection.
• Ability to receive, process, and acknowledge valid CMAS Alert, Update, Cancel, and Required Monthly Test (RMT) messages.
• Ability to handle transmission control cease and resume messages.
• Ability to handle link test messages.
• Ability to perform CAP retrieval.
This Standard is not intended to define test cases for the complete development lifecycle, nor is it intended to provide complete requirements verification or complete compliance testing. Requirements verification testing is typically performed during the unit, integration, and system testing phases and is beyond the scope of this Standard.