LKT-BMAX-2-OR-25BreezeMAX 4Motion Broadband Wireless Access System

4Motion ® System Manual Release 2.5M2 April 2010 P/N 215637 Document History 4Motionii System Manual Document History TopicDescriptionDate Issued Preliminary Release for Early Field Trials New System ManualJanuary 2008 Preliminary Release for BetaMay 2008 Release for GAJuly 2008 SDR Section 1.3.1.3 RemovedAugust 2008 TemplateChangedSeptember 2008 Power Feeder Section 1.3.4 Supported in release 2.5December 2008 7 MHz Channel Bandwidth Table 1-4, relevant sections in Chapter 4. Supported in release 2.5December 2008 Installing 4x2 ODU Section 2.1.4 Updated (including new installation options)December 2008 Installation recommendation Section 2.3.9.1 Recommendation on installing AUs in a 3-sector configuration December 2008 Trap Manager Section 2.1.5 Modified instructions for initial configurationDecember 2008 Operation and Administration Using the CLI Chapter 4 Updated to reflect NPU SW Version 2_5_1_8December 2008 Rate Limiting for the NPU Section 3.3.7.2 Rate limits are configurable only by the vendor. May 2009 Configuring ACLs Section 3.3.10 Updated default ACLs.May 2009 Configuring Performance Data Collection Section 3.3.13 Added support for new counters groups, updated names. May 2009 Configuring the Power Control Required C/N Level Parameters Section 3.8.6.2.2 Updated Defaults for cqi, cdma, qam64-1by2, qam64-2by3, qam64-3by4, qam64-5by6. May 2009 Managing the BS Keep-Alive Functionality Section 3.8.26 Updated commands’ syntax.May 2009 Managing the BS Idle Mode Parameters Section 3.8.28 New featureMay 2009 Document History 4Motioniii System Manual Managing BS Services Section 3.8.4 Added new parameters: paging-cycle, paging-offset, lm-traffic-idle-period, dl-def-rate. Updated range and default value for max-subburst. May 2009 Managing Ranging Parameters Section 3.8.23 The following tables were removed from operator CLI: Bandwidth Request, Handover Ranging, Initial Ranging, Periodic Ranging, Timing Correction. contbased-rsrvtimeout was removed from Ranging General table. May 2009 Airframe General Parameters Sections 3.8.16.2.1, 3.8.16.3.1, 3.8.16.5.1 Updated parameters: Removed: enable-ul-scrotation. Added: auto-diversity, auto-rx-enable. Corrected name: ul-duration. May 2009 Airframe Cyclic Delay Parameters Section 3.8.16.2.4 Updated descriptions.May 2009 Airframe Linear Delay Parameters Previousely Section 4.8.16.2.5 Updated descriptions.May 2009 Airframe Mapping Parameters Previousely Section 4.8.16.2.6 Updated descriptions.May 2009 Airframe Receive Parameters Previousely Section 4.8.16.2.7 Updated descriptions.May 2009 Airframe Downlink Diversity Parameters Section 3.8.16.2.3 Changed value range and default for the mimo parameter. May 2009 Airframe MIMO Parameters Sections 3.8.16.2.8, 3.8.16.3.5, 3.8.16.5.8 New Airframe parameters table.May 2009 Neighbor BS General Parameters Sections 3.8.13.2.1, 3.8.13.3.1, 3.8.13.7.1 Updated parameters: Removed: restartcount ucd-configchangecount and dcd-configchangecount must be set to 0. Added: paging-grp-id, nbr-strt-rng-codes. Updated range and description: preamble-idx May 2009 TopicDescriptionDate Issued Document History 4Motioniv System Manual Service Mapping Rule R1 Profile Parameters Sections 3.8.5.2.3, 3.8.5.6.3 Removed: sdu-length, sdu-size. All possible values of datadeliverytype are supported (including rTVR and nRTVR). Updated descriptions of cir, mir, latency. Updated range for cir, mir. May 2009 Service Mapping Rule R6 Profile Parameters Section 3.8.5.2.4, Updated range for cir, mir.May 2009 Feedback Allocation Parameters Section 3.8.7 Removed: pr-cdma, ert-poll-enable. Default value of ir-cdma changed from 20 to 2. Updated description of max-cqi. May 2009 Trigger Setup Parameters Section 3.8.10 Removed: hysteresismargin, timetotrigger Updated description of avgduration-rssi. May 2009 Neighbor BS Trigger Setup Parameters Sections 3.8.13.2.3, 3.8.13.3.3, 3.8.13.7.3 Removed: hysteresismargin, timetotriggerMay 2009 Rate Adaptation Parameters (was previously Section 4.8.20) All Rate Adaptation parameters were removed. May 2009 Scan Negotiation Parameters Section 3.8.11 Removed: all parameters except enable-modify. May 2009 Handover Negotiation at SBS (was previously 4.8.12) All Handover Negotiation at SBS parameters were removed. May 2009 UCD Parameters (was previously 4.8.15) All UCD parameters were removed.May 2009 DCD Parameters (was previously 4.8.16) All DCD parameters were removed.May 2009 Authentication Relay Parameters Section 3.8.18 Removed: nonauth-macctrlratethrshld, nonauth-pduratethrshld Updated the default value of maxeaproundsthrshld to 100. Updated the default value of suspendedeapprocthrshld to 10000. Updated the description. Updated the default value of activemsthrshld to 1024. May 2009 TopicDescriptionDate Issued Document History 4Motionv System Manual Handover Control Parameters Section 3.8.23 All configurable (read-write) parameters were removed. A new read-only parameter added: CINRReuse. May 2009 BS Management Alarm Thresholds (was previously 4.8.26) All BS Management Alarm Thresholds parameters were removed. May 2009 BS Alarm Threshold Parameters Section 3.8.24 Removed: dl-droppedpackets, unalloc-slots, dl-retransmissions, ul-retransmissions, dl-subburstdrop, ul-subburstdrop. Updated description, range and default for ul-mednoise, ul-99prcntnoise. Added: Be-exc-dl-drop-thr, rt-exc-dl-drop-thr, nrt-exc-dl-drop-thr, ugs-exc-dl-drop-thr, ert-exc-dl-drop-thr. May 2009 Managing the Site General Information Section 3.3.15.7 Added section on displaying the site general information. Address parameter value was changed to up to 70 characters. Removed: AsnName, Region. May 2009 Managing the Unique Identifier Section 3.3.15.8 Added section on displaying the site ID.May 2009 Displaying the Vendor Identifier Section 3.3.15.9 New feature.May 2009 AU Connectivity Parameters Sections 3.5.2.3, 3.5.3.3, 3.5.6.3 Added new parameters: service-ip, service-mask, service-next-hop. Updatated possible values of bearervlanid and the read…

Text truncated - open the document above for the full version.

Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion159 System Manual 3.3.8.2Managing QoS Classification Rules QoS classification rules classify packets into flows, based on the following parameters: „IP address of the host originating the traffic (the IP address assigned to the bearer, internal-management or external-management interface) „Layer 3 protocol indicating either TCP or UDP „Layer 4-source port for the application that needs to be marked (for example, FTP, Telnet, SNMP, MIP, or RADIUS) A class-map can be associated with each flow to define separate DSCP and/or VLAN priority bits for QoS handling of each flow. 1Enable the ACL configuration mode for ACL 199 (refer to Section 3.3.8.2.1). Syntax Description ParameterDescriptionPresenceDefault Value Possible Values [<class-map- num(1-65535) >] Indicates the identifier of the class-map for which configuration information is to be displayed. Do not specify a value for this parameter if you want to view the configuration information for all class-maps. OptionalN/A1-65535 Display Format (for each class-map if requested for all class-maps) Class map <class map number> ---------------------------------------------- CoS Value : <value> DSCP Value : <value> Command Modes Global command mode To configure a QoS classification rule: Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion160 System Manual 2You can now: »Configure one or more QoS classification rules (refer to Section 3.3.8.2.2) »Delete one or more QoS classification rules (refer to Section 3.3.8.2.3) »Terminate the ACL configuration mode (refer to Section 3.3.8.2.4) You can, at any time, enable/disable QoS marking (refer to Section 3.3.8.3) or view the configuration information for ACL 199 (refer to Section 3.3.8.4). 3.3.8.2.1Enabling the ACL Configuration Mode for ACL 199 To configure QoS classification rules for host-originating traffic, first enable the extended ACL 199 configuration mode. Run the following command to enable the extended ACL configuration mode for ACL 199. npu(config)# ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>} [name<string>] After you enable the ACL 199 configuration mode, you can configure one or several QoS classification rules, and associate them with the appropriate class-maps. IMPORTANT QoS classification rules can be associated only with ACL 199. IMPORTANT QoS classification rules can be added only to extended ACL 199 Command Syntax npu(config)# ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>} [ name <string>] Privilege Level 10 Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion161 System Manual 3.3.8.2.2Configuring a QoS Classification Rule You can configure the QoS classification rules for the ACL with respect the following parameters: „Source IP address for the host-originating application traffic „Application protocol (TCP or UDP) „L4 source port of the application traffic „QoS class-map identifier By default, there are 8 pre-configured QoS classification rules associated with the 8 pre-configured QoS class-maps: Syntax Description ParameterDescriptionPresenceDefault Value Possible Values extended <access-list-n umber (100-199)> Indicates the identifier of the extended ACL for which the ACL configuration mode is to be enabled. You must specify 199 to enable configuration of QoS classification rules. MandatoryN/A199 [ name <string>] Indicates the name of the ACL for which the ACL configuration mode is to be enabled. Note: If you do not specify the ACL name, the ACL number is used as the default ACL name. OptionalN/AString (upto 20 characters) Command Modes Global configuration mode Table 3-15: Pre-Configured QoS Classification Rules and Class-Maps IP InterfaceType of TrafficProtocolSource Port Class Map DSCP802.1p BearerRADIUSUDP1812177 Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion162 System Manual After configuring QoS classification rules for this ACL, enable QoS marking for this ACL. By default, QoS marking is disabled. For details, refer to Section 3.3.8.3. Run the following command to configure a QoS classification rule for this ACL: npu(config-ext-nacl)# qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>} When you execute this command, a new QoS classification rule is added to the ACL for which the configuration mode is enabled. BearerMobileIP-AgentUDP434277 BearerWiMAX ASN Control Plane Protocol UDP2231377 Internal-ManagementOBSAI message exchange between NPU and AU UDP10009400 Internal-ManagementTrivial File Transfer Protocol UDP69500 External-ManagementTelnetTCP23600 External-ManagementSSH Remote Login Protocol TCP22700 External-ManagementSNMPUDP161800 IMPORTANT An error may occur if: „You have specified a source port that is not within the range, 1-65535. „The host IP address or class-map identifier that you have specified do not exist. Command Syntax npu(config-ext-nacl)# qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>} Privilege Level 10 Table 3-15: Pre-Configured QoS Classification Rules and Class-Maps IP InterfaceType of TrafficProtocolSource Port Class Map DSCP802.1p Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion163 System Manual 3.3.8.2.3Deleting a QoS Classification Rule To delete a QoS classification rule for an ACL, run the following command: npu(config-ext-nacl)# no qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>} Syntax Description ParameterDescriptionPresenceDefault Value Possible Values {host <src-ip-addres s>} Indicates the IP address of the host interface that generates the traffic for which this classification rule is to be configured. Specify the IP address that you have assigned to the internal-management, ex…

Text truncated - open the document above for the full version.

Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion359 System Manual „NPU Counters Groups (per-NPU counters): »NPU DATA port »NPU MGMT port »NPU CASCADE port »AU ports »NPU internal-management interface »NPU external-management interface »NPU local-management interface »NPU bearer interface »Service Flow Authorization functionality »Data path functionality »AAA client functionality »Authenticator function »Context function »DHCP proxy functionality »DHCP relay functionality »DHCP server functionality »MS state change functionality Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion360 System Manual „AU Counters Groups (per-BS counters) »De-Registration »Integrity »Mobility »Network Entry (NE) »Traffic »Utilization »“Idle Mode” »“Fast Feedback CQI Handling” »“Ack/Nack Channel Handling” »“End Transaction Update” »“DL Frame Data Zone Histograms” »“TxR1 Net Traffic” »“RxR1 Net Traffic” »“TxR1 Total Traffic” »“RxR1 Total Traffic” »“DL HARQ Sub-Bursts Drops” »“DL HARQ Transmissions” »General »All MS Basic Mode »Specific MS Advanced Mode For details on the performance data counters collected for each group refer to the relevant 4Motion Performance Management document. You can specify the group for which performance data is to be stored and collected. Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion361 System Manual The data is stored in an XML file called, prf_<SiteID>_yyyymmddhhmm.xml.gz in the path,/tftpboot/management/performance. The system maintains this data for a maximum of 24 hours after which it is deleted. It is recommended that you periodically make a backup of these files on an external server. You can enable/disable collection of performance data for each group separately. This section describes: „“Enabling Collection and Storage of Historical Performance Data” on page 361 „“Disabling Collection and Storage of Performance Data” on page 366 „“Displaying the Status of Performance Data Collection” on page 368 3.3.13.1Enabling Collection and Storage of Historical Performance Data 4Motion collects and stores performance data for the a number of system groups (refer to Section 3.3.13). To enable collection and storage of performance data for a group, run the following command: To enable collection and storage of performance data for an NPU counters group: npu(config)# pm-group enable npu {BckhlPort | MgmtPort | CascPort | AuPortTable | IntMgmtIf | ExtMgmtIf | LclMgmtIf | BearerIf | Sfa | DatapathFn | AaaClient | Authenticator | ContextFn | ProxyDhcp | RelayDhcp | ServerDhcp | MsStateChangeFn} To enable collection and storage of performance data for an AU counters group: npu(config)# pm-group enable au { BsDeRegistrationTable | BsIntegrity | BsMobilityTable | BsNetworkEntryTable | BsTrafficTable | BsUtilizationTable | BsIdleModeTable | BsFastFeedbackCQIHandlingTable | BsAckNackChannelHandlingTable | BsEndTransactionUpdateTable | BsDlDataZoneFrameHistogramsTable | BsTxR1NetTrafficTable | BsRxR1NetTrafficTable | BsTxR1TotalTrafficTable | BsRxR1TotalTrafficTable | BsDLHARQSbDropsTable | BsDLHARQTransmissionTable | BsGeneral | Bsallmsbasicmode | Bsspecificmsadvancedmode} Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion362 System Manual You can display whether performance data collection is currently enabled or disabled for a particular group. For details, refer Section 3.3.13.3. The parameters in this command correspond to the groups listed in the following tables: NOTE Using this command, you can enable collection of performance data for only one group at a time. For example, run the following command if you want to enable performance data collection and storage for the data path function: npu(config)# pm-group enable npu DatapathFn Table 3-25: NPU Counters Groups for which Performance Data can be Collected Parameter NameRefers to... BckhlPortNPU DATA port MgmtPortNPU MGMT port CascPortNPU CASCADE port AuPortTableAU ports IntMgmtIfNPU internal-management interface ExtMgmtIfNPU external-management interface LclMgmtIfNPU local-management interface BearerIfNPU bearer interface SfaService flow authorization DatapathFnData path functionality AaaClientAAA client functionality AuthenticatorAuthenticator function ContextFnContext function ProxyDhcpDHCP proxy functionality RelayDhcpDHCP relay functionality ServerDhcpDHCP server functionality MsStateChangeFnMS state change functionality Table 3-26: AU Counters Groups for which Performance Data can be Collected Parameter NameRefers to... BsDeRegistrationTable De-Registration BsIntegrity Integrity Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion363 System Manual For example, run the following command if you want to enable performance data collection for the NPU DATA port: npu(config)# pm-group enable npu BckhlPort When you run this command, collection and storage of performance data is enabled for the DATA port counters. After you have enabled collection and storage of performance data is fetched every quarter of an hour. BsMobilityTable Mobility BsNetworkEntryTable Network Entry BsTrafficTable Traffic BsUtilizationTable Utilization BsIdleModeTable Idle Mode BsFastFeedbackCQIHandlingTable Fast Feedback CQI Handling BsAckNackChannelHandlingTable Ack/Nack Channel Handling BsEndTransactionUpdateTable End Transaction Update BsDlDataZoneFrameHistogramsTable DL Frame Data Zone Histograms BsTxR1NetTrafficTable TxR1 Net Traffic BsRxR1NetTrafficTable RxR1 Net Traffic BsTxR1TotalTrafficTable TxR1 Total Traffic BsRxR1TotalTrafficTable RxR1 Total Traffic BsDLHARQSbDropsTable DL HARQ Sub-Bursts Drop BsDLHARQTransmissionTable DL HARQ Transmissions BsGeneral General Bsallmsbasicmode All MS Basic Modec Bsspecificmsadvancedmode Specific MS Advanced Mode NOTE When you enable collection of performance data collection, the data is stored in a file called, prf_<SiteID>_yyyymmddhhmm.xml.gz in the path, /tftpboot/management/perfo…

Text truncated - open the document above for the full version.

August 09, 2010 Declaration – Using Licensee Globalstar I declare that we (Alvarion) are using Globalstar Licensee for our product like FCC ID: LKT-BMAX-2-OR-25. Our Customer ORC (Open Range) is using Globalstar frequency for WIMAX. Globalstar owns the 2490MHz frequency. Sincerely, AVNER RUTA

Federal Communications Commission FCC 08-254 Before the Federal Communications Commission Washington, D.C. 20554 In the Matter of ) ) Globalstar Licensee LLC ) File No. SAT-MOD-20080516-00106 ) Call Sign: S2115 Application for Modification of License ) for Operation of Ancillary Terrestrial ) Component Facilities ) ORDER AND AUTHORIZATION Adopted: October 31, 2008 Released: October 31, 2008 By the Commission: Commissioners Copps, Adelstein, and Tate issuing separate statements; Chairman Martin and Commissioner McDowell dissenting and issuing separate statements. I. INTRODUCTION 1. In this order, we grant in part a request by Globalstar Licensee LLC (“Globalstar”) to modify its authority for an ancillary terrestrial component (“ATC”) to be operated in conjunction with the Globalstar™ Mobile Satellite Service (“MSS”) system. Specifically, we modify Globalstar’s license to permit use of the WiMAX air interface protocol. In doing so, we find that an interim waiver of certain of our ATC “gating criteria” and technical rules will serve the public interest by permitting Globalstar and its spectrum lessee, Open Range Communications, Inc. (“Open Range”), to commence deployment of a broadband service consistent with a $267 million loan commitment from the Department of Agriculture’s Rural Development Utilities Program. II. BACKGROUND A. The Globalstar ATC Authorization 2. Globalstar holds a space station license for the Globalstar 1.6/2.4 GHz MSS system, which has been in continuous commercial operation for more than eight years providing voice and data services in the United States and abroad via non-geostationary-orbit satellites. 1 In March 2005, Globalstar’s predecessor-in-interest applied for authority to operate ATC base stations and dual-mode MSS/ATC mobile terminals with the cdma2000 air interface protocol. The International Bureau granted the application in January 2006, subject to conditions, 2 assigning the 1610-1615.5 MHz frequency band for Globalstar ATC mobile terminal transmission and the 2487.5-2493 MHz band for Globalstar ATC 1 An affiliated company, GUSA Licensee LLC, holds licenses for the Globalstar MSS system’s gateway earth stations in the United States and holds a blanket license for operation of Globalstar MSS terminals in the United States. 2 Globalstar LLC Request for authority to implement an ancillary terrestrial component for the Globalstar Big LEO Mobile Satellite Service system, Order and Authorization, DA 06-121, 21 FCC Rcd 398 (2006) (“Globalstar ATC Order”). Federal Communications Commission FCC 08-254 2 base station transmission. These ATC frequency assignments were consistent with a rule provision, Section 25.149(a)(2)(iii), which stated that ATC operations in the 1.6/2.4 MHz MSS bands would be limited to the 1610-1615.5 MHz, 1621.35-1626.5 MHz, and 2487.5-2493 MHz bands and to the frequencies assigned for the licensee’s MSS operation. In a Notice of Proposed Rulemaking released in November 2007, the Commission proposed to amend Section 25.149(a)(2)(iii) to expand the available spectrum for ATC operation in the 1.6/2.4 MHz MSS bands. 3 In a Report and Order released in April 2008, the Commission adopted the proposed rule change and accordingly proposed to modify Globalstar’s ATC license to expand the spectrum assigned for ATC operation to extend from 1610 to 1617.775 MHz band and from 2483.5 to 2495 MHz, for a total ATC spectrum bandwidth of 19.275 MHz. 4 Globalstar’s ATC authorization was subsequently modified to allow operation in those wider frequency bands. 5 B. Application for Modification of ATC Authority and Related Filings 3. In the above-captioned application, Globalstar requests that its license be modified to authorize ATC operation with air interface protocols other than the previously authorized cdma2000. Specifically, Globalstar requests authority to use four additional protocols: Wideband CDMA (“WCDMA”), Time Division CDMA (“TD-CDMA”), Long Term Evolution with Frequency Division Duplex (“LTE-FDD”), and WiMAX with Time Division Duplex (“WiMAX-TDD”). 4. Globalstar states in the application that when it originally sought authority to deploy ATC services it planned to offer a variety of MSS/ATC services using cdma2000 or IS-95 protocols but that technology choices have evolved dramatically since then, driven by the rapid rate of innovation in the wireless marketplace. After considering various technical options and financial models, Globalstar concluded that there is a strong and currently unmet market demand for broadband wireless data technologies employing WiMAX-TDD, WCDMA, TD-CDMA, and/or LTE protocols. 5. Globalstar plans to collaborate with one or more “terrestrial partners” to offer MSS bundled together with ATC broadband service. To that end, Globalstar has entered into a spectrum lease agreement with Open Range. Under the terms of the agreement, Open Range would construct and operate an ATC network using S-band spectrum leased from Globalstar. The two companies would provide MSS/ATC service to customers equipped with dual-mode handheld terminals, Open Range providing the ATC service and Globalstar providing the MSS component. 6. The first-generation mobile device for the Globalstar/Open Range rural broadband service offering would be a MSS/ATC handheld unit based on the same architecture as Globalstar’s SPOT Satellite Personal Tracker™. The SPOT device provides one-way, transmit-only communications 3 Spectrum and Service Rules for Ancillary Terrestrial Components in the 1.6/2.4 GHz Big LEO Bands; Review of the Spectrum Sharing Plan Among Non-Geostationary Satellite Orbit Mobile Satellite Service Systems in the 1.6/2.4 GHz Bands, Second Order on Reconsideration, Second Report and Order, and Notice of Proposed Rulemaking, 22 FCC Rcd 19733 (2007). 4 Spectrum and Service Rules for Ancillary Terrestrial Components in the 1.6/2.4 GHz Big LEO Bands/Globalstar Licensee LLC, Authority to Implement an Ancillary Terrestrial Component, Report and Order a…

Text truncated - open the document above for the full version.

APPLICANT INFORMATION Enter a description of this application to identify it on the main menu: Application for Modification of ATC Authority Approved by OMB 3060−0678 Date & Time Filed: May 16 2008 5:33:26:260PM File Number: SAT−MOD−20080516−00106 FCC APPLICATION FOR SPACE AND EARTH STATION:MOD OR AMD − MAIN FORM FCC 312 MAIN FORM FOR OFFICIAL USE ONLY FCC Use Only 1−8. Legal Name of Applicant Name: Globalstar Licensee LLC Phone Number: 408−933−4525 DBA Name: Fax Number: 408−933−4960 Street: 461 S. Milpitas Boulevard E−Mail:[email protected] City: Milpitas State: CA Country: USA Zipcode: 95035 − Attention: Mr Anthony J Navarra 1 CLASSIFICATION OF FILING 9−16. Name of Contact Representative Name: Mike Kozlowski Phone Number: 408−933−4456 Company: Globalstar, Inc. Fax Number: 408−933−4957 Street: 461 S. Milpitas Boulevard E−Mail: [email protected] City: Milpitas State: CA Country: USA Zipcode: 95035− Attention: Mike Kozlowski Relationship: Engineer 2 17. Choose the button next to the classification that applies to this filing for both questions a. and b. Choose only one for 17a and only one for 17b. a1. Earth Station a2. Space Station (N/A) b1. Application for License of New Station (N/A) b2. Application for Registration of New Domestic Receive−Only Station b3. Amendment to a Pending Application b4. Modification of License or Registration b5. Assignment of License or Registration b6. Transfer of Control of License or Registration b7. Notification of Minor Modification (N/A) b8. Application for License of New Receive−Only Station Using Non−U.S. Licensed Satellite (N/A) b9. Letter of Intent to Use Non−U.S. Licensed Satellite to Provide Service in the United States (N/A) b10. Other (Please specify) (N/A) b11. Application for Earth Station to Access a Non−U.S.satellite Not Currently Authorized to Provide the Proposed Service in the Proposed Frequencies in the United States (N/A) b12. Application for Database Entry b13. Amendment to a Pending Database Entry Application b14. Modification of Database Entry 17c. Is a fee submitted with this application? If Yes, complete and attach FCC Form 159. If No, indicate reason for fee exemption (see 47 C.F.R.Section 1.1114). Governmental Entity Noncommercial educational licensee Other(please explain): 17d. Fee Classification CGW − Space Station Modification(Non− Geostationary) 3 TYPE OF SERVICE 18. If this filing is in reference to an existing station, enter: (a) Call sign of station: S2115 19. If this filing is an amendment to a pending application enter both fields, if this filing is a modification please enter only the file number: (a) Date pending application was filed: (b) File number: SATMOD2005030100054 20. NATURE OF SERVICE: This filing is for an authorization to provide or use the following type(s) of service(s): Select all that apply: a. Fixed Satellite b. Mobile Satellite c. Radiodetermination Satellite d. Earth Exploration Satellite e. Direct to Home Fixed Satellite f. Digital Audio Radio Service g. Other (please specify) 21. STATUS: Choose the button next to the applicable status. Choose only one. Common Carrier Non−Common Carrier 22. If earth station applicant, check all that apply. Using U.S. licensed satellites Using Non−U.S. licensed satellites 23. If applicant is providng INTERNATIONAL COMMON CARRIER service, see instructions regarding Sec. 214 filings. Choose one. Are these facilities: Connected to a Public Switched Network Not connected to a Public Switched Network N/A 4 TYPE OF STATION 24. FREQUENCY BAND(S): Place an ’X’ in the box(es) next to all applicable frequency band(s). a. C−Band (4/6 GHz) b. Ku−Band (12/14 GHz) c.Other (Please specify upper and lower frequencies in MHz.) Frequency Lower: 1610 Frequency Upper: 2500 (Please specify additional frequencies in an attachment) 25. CLASS OF STATION: Choose the button next to the class of station that applies. Choose only one. a. Fixed Earth Station b. Temporary−Fixed Earth Station c. 12/14 GHz VSAT Network d. Mobile Earth Station e. Geostationary Space Station f. Non−Geostationary Space Station g. Other (please specify) 26. TYPE OF EARTH STATION FACILITY: Transmit/Receive Transmit−Only Receive−Only N/A "For Space Station applications, select N/A." 5 PURPOSE OF MODIFICATION 27. The purpose of this proposed modification is to: (Place an ’X’ in the box(es) next to all that apply.) a −− authorization to add new emission designator and related service b −− authorization to change emission designator and related service c −− authorization to increase EIRP and EIRP density d −− authorization to replace antenna e −− authorization to add antenna f −− authorization to relocate fixed station g −− authorization to change frequency(ies) h −− authorization to add frequency i −− authorization to add Points of Communication (satellites &amp; countries) j −− authorization to change Points of Communication (satellites &amp; countries) k −− authorization for facilities for which environmental assessment and radiation hazard reporting is required l −− authorization to change orbit location m −− authorization to perform fleet management n −− authorization to extend milestones o −− Other (Please specify) 6 ENVIRONMENTAL POLICY ALIEN OWNERSHIP Earth station applicants not proposing to provide broadcast, common carrier, aeronautical en route or aeronautical fixed radio station services are not required to respond to Items 30−34. 28. Would a Commission grant of any proposal in this application or amendment have a significant environmental impact as defined by 47 CFR 1.1307? If YES, submit the statement as required by Sections 1.1308 and 1.1311 of the Commission’s rules, 47 C.F.R. 1.1308 and 1.1311, as …

Text truncated - open the document above for the full version.