hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.37 Simultaneous network or system access | Any applicable specifications and standards that are written to meet the requirements of the Project MESA SoR should also provide for simultaneous access to multiple networks or host computers by a single MESA user device, as well as simultaneous access from multiple MESA user devices to a single host. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.38 Network pre-emption | Any specifications and standards that are created to meet the requirements of the Project MESA SoR should support prioritization of access and routing, and allow for pre-emption as applicable. It is noted that pre-emption (dynamic, forced or ruthless) of non-public safety users on shared commercial/government systems i... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.39 First-In, first-Out | Any specifications and standards written to meet the requirements of the Project MESA SoR should ensure a system design that allows for access on a "first-in - first-out" basis within each priority class. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.40 System and/or network transaction audit trail | Any specifications and standards written to meet the requirements of the Project MESA SoR should allow network managers the option of creating an audit trail of all transactions that take place over their site, network or system. Access to this information has to be protected. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.41 Ability to provide statistical reports | Any specifications and standards written to meet the requirements of the Project MESA SoR should include all necessary systems or network management software to allow for the users to easily access operational and performance management information. This information should be formatted to allow for the creation of stat... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.42 Agency-by-agency reports | Any specifications and standards written to meet the requirements of the Project MESA SoR should include a management system that allows for usage, traffic patterns and performance reports to be generated on an agency-by-agency basis. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.43 MESA network component identification | Any specifications and standards written to meet the requirements of the Project MESA SoR should include the capability to automatically identify all appropriate MESA components and MESA user devices for each transmission within a network or a group of networks. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.44 Security requirements | Any specifications and standards written to meet the requirements of the Project MESA SoR should permit effective, efficient, reliable and, as may be required, secure (authenticated and/or encrypted) intra- and interagency communications (interoperability). The basic security platforms should be capable of being expand... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.45 Automated information requirements | Any specifications and standards written to meet the requirements of the Project MESA SoR should accommodate access to each nation's specific automated security requirements. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.46 Blocking unauthorized access | Any specifications and standards written to meet the requirements of the Project MESA SoR should include the ability to block access by unauthorized users, authenticate authorized users and to stun and kill equipment, as applicable. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.47 Over-the-air-rekeying (OTAR) | Any specifications and standards written to meet the requirements of the Project MESA SoR should enable over the air rekeying. ETSI ETSI TS 170 001 V3.3.1 (2008-03) 25 |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.48 High-speed, error-free service | Any specifications and standards written to meet the requirements of the Project MESA SoR should be predicated on a network design that is capable of the rapid transmission of all potential data applications, through very harsh operating environments, with a minimum of data or transmission errors. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.49 End-to-end transmit time | The proposed Project MESA wireless network(s) end-to-end transit time shall be less than 400 milliseconds. For voice communications, the end-to-end delay shall not exceed 150 ms for duplex systems and 250 ms for half-duplex systems. For links involving a non-terrestrial node, the delay shall not exceed 400 ms. NOTE: 40... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.50 Transparent transfer | Any specifications and standards written to meet the Project MESA SoR should allow for the seamless transfer of MESA user devices moving between MESA capable cells, and/or predefined system architecture, regardless of the MESA network services being utilized, as infrastructure and authorization permits. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.51 Degradation and redundancy | Any specifications and standards that are written to meet the requirements of the Project MESA SoR should include the capability of providing "graceful system or network degradation" and/or complete redundancy when required. • The specifications and standards written to comply with the Project MESA SoR should include t... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.52 Duty cycle requirements | Any specifications and standards written to meet the requirements of the Project MESA SoR should include all the technology requirements that ensure the equipment used in the system or network are capable of, and rated for, a 100 % duty cycle. Panic Button • The specifications and standards that are compliant with Proj... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.53 Data to be transported | The Project MESA specifications and standards should comply with the SoR's basic requirement for immediate, error- free transfer and display of all forms of data, including but not limited to, text, voice, video, infrared video, photos, detailed graphical information, such as maps, engineering plans or drawings, and fi... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.54 Network and data base interconnectivity | Any specifications and standards written to meet the Project MESA SoR should embody the concept of supporting the connection to, or interconnecting with, all known or specified local, regional, national and/or international public safety databases, applications, files, or related electronic technology services that all... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.55 Network transmission requirements | The technology selected and the specifications and standards written to meet the requirements of the Project MESA SoR should be capable of supporting information transfer rate-intensive applications, such as the rapid transmission of digital photos taken at the scene of a public safety incident. This transmission of pu... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.56 Location Determination | Any specifications and standards written to meet the requirements of the Project MESA SoR should support geographical position-locating capability. NOTE: A number of the services covered by the MESA effort share the common denominator of having to deploy their personnel into situations, which are potentially life threa... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.57 Delayed transmission and remote stops | Any specifications and standards written to meet the requirements of the Project MESA SoR should be capable of supporting delayed transmission and/or remote store and forward when required and authorized. ETSI ETSI TS 170 001 V3.3.1 (2008-03) 27 |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.58 Dynamic updating of data fields | Any specifications and standards written to meet the requirements of the Project MESA SoR should support two-way operation to accommodate the implementation of "smart" systems that automatically update data fields being transmitted from authorized and authenticated MESA user devices, including: • Data terminals. • Subs... |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 1 Scope | .............................................................................................................................................. 22 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 2 References | ...................................................................................................................................... 22 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 3 Definitions, symbols and abbreviations | ......................................................................................... 23 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 3.1 Definitions | ............................................................................................................................................... 23 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 3.2 Symbols | ................................................................................................................................................... 24 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 3.3 Abbreviations | .......................................................................................................................................... 26 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 4 General | ........................................................................................................................................... 28 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 4.1 Relationship between minimum requirements and test requirements | ..................................................... 28 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 4.2 Applicability of minimum requirements | ................................................................................................. 29 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 4.3 Specification suffix information | .............................................................................................................. 29 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 4.4 Test points analysis | ................................................................................................................................. 30 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 4.5 Applicability and test coverage rules | ....................................................................................................... 30 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 4.6 Pass fail decision rule of test case | ........................................................................................................... 30 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5 Operating bands and Channel arrangement | .................................................................................... 31 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.1 General | .................................................................................................................................................... 31 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2 Operating bands | ....................................................................................................................................... 31 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2A Operating bands for CA | .......................................................................................................................... 33 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2A.1 Intra-band CA | .................................................................................................................................... 33 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2A.2 Inter-band CA | .................................................................................................................................... 33 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2A.2.1 Inter-band CA (two bands) | ........................................................................................................... 34 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2A.2.2 Inter-band CA (three bands) | ......................................................................................................... 36 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2A.2.3 Inter-band CA (four bands) | .......................................................................................................... 37 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2B Operating bands for DC | .......................................................................................................................... 37 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2C Operating band combination for SUL | ..................................................................................................... 37 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2D Operating bands for UL MIMO | .............................................................................................................. 38 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2E Operating band for V2X | .......................................................................................................................... 39 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2E.1 V2X operating bands | ......................................................................................................................... 39 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2E.2 V2X operating bands for concurrent operation | .................................................................................. 39 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2J Operating band for ATG | ......................................................................................................................... 39 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.2K Operating bands for Aerial UE | ................................................................................................................ 40 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3 UE channel bandwidth | ............................................................................................................................ 40 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3.1 General | ............................................................................................................................................... 40 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3.2 Maximum transmission bandwidth configuration | ............................................................................. 40 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3.3 Minimum guard band and transmission bandwidth configuration | ..................................................... 41 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3.4 RB alignment | ..................................................................................................................................... 43 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3.5 UE channel bandwidth per operating band | ........................................................................................ 43 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3.6 Asymmetric channel bandwidths | ....................................................................................................... 46 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3A UE channel bandwidth for CA | ................................................................................................................ 48 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3A.1 General | ............................................................................................................................................... 48 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3A.2 Maximum transmission bandwidth configuration for CA | ................................................................. 48 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3A.3 Minimum guard band and transmission bandwidth configuration for CA | ......................................... 48 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3A.4 Void | ................................................................................................................................................... 50 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3A.5 UE channel bandwidth per operating band for CA | ............................................................................ 50 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3E Channel bandwidth for V2X | ................................................................................................................... 51 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3E.1 General | ............................................................................................................................................... 51 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3E.2 Channel bandwidth for V2X concurrent operation | ............................................................................ 51 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.3I Channel bandwidth for (e)RedCap | .......................................................................................................... 51 3GPP TS 38.521-1 version 19.2.0 Release 19 4 ETSI TS 138 521-1 V19.2.0 (2025-11) ETSI |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4 Channel arrangement | ............................................................................................................................... 51 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.1 Channel spacing | ................................................................................................................................. 51 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.1.1 Channel spacing for adjacent NR carriers | .................................................................................... 51 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.2 Channel raster | .................................................................................................................................... 52 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.2.1 NR-ARFCN and channel raster | .................................................................................................... 52 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.2.2 Channel raster to resource element mapping | ................................................................................ 52 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.2.3 Channel raster entries for each operating band | ............................................................................ 53 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.3 Synchronization raster | ....................................................................................................................... 55 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.3.1 Synchronization raster and numbering | ......................................................................................... 55 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.3.2 Synchronization raster to synchronization block resource element mapping | ............................... 56 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4.3.3 Synchronization raster entries for each operating band | ................................................................ 56 5.4.4 TX–RX frequency separation ............................................................................................................ 58 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4A Channel arrangement for CA | ................................................................................................................... 59 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4A.1 Channel spacing for CA | ..................................................................................................................... 59 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4A.2 Channel raster for CA | ........................................................................................................................ 59 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4A.3 Synchronization raster for CA | ........................................................................................................... 59 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4A.4 Tx-Rx frequency separation for CA | ................................................................................................... 59 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4E Channel arrangement for V2X | ................................................................................................................ 59 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4E.1 Channel spacing | ................................................................................................................................. 59 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4E.2 Channel raster | .................................................................................................................................... 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4E.2.1 NR-ARFCN and channel raster | .................................................................................................... 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4E.2.2 Channel raster to resource element mapping | ................................................................................ 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4E.2.3 Channel raster entries for each operating band | ............................................................................ 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4E.3 Synchronization raster for V2X | ......................................................................................................... 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4F | 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4G | 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4H | 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4I Channel arrangement for (e)RedCap | ....................................................................................................... 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4I.1 Channel spacing for (e)RedCap | ......................................................................................................... 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4I.2 Channel raster for (e)RedCap | ............................................................................................................ 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4I.2.1 NR-ARFCN and channel raster | .................................................................................................... 60 |
47427c363b8cb3a33a525cec081286b5 | 138 521-1 | 5.4I.2.2 Channel raster to resource element mapping | ................................................................................ 60 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.