name: ARIB
full_form: Association of Radio Industries and Business
context: Almanac data: Sig GNSS NAVIC 2020_9_17 Almanac.txt Ephemeris data: Ephemeris data: Sig GNSS GPS 2020_9_17 Rinex.rnx, Sig GNSS GLONASS 2020_9_17 Rinex.rnx, Sig GNSS GALILEO 2020_9_17 Rinex.rnx, Sig GNSS BDS 2020_9_17 Rinex.rnx, Sig GNSS NAVIC 2020_9_17 Rinex.rnx UE location: the UE location is calculated as a random offset from the reference location using the method described in subclause 6.2.1.2.6. The reference location is: latitude: 10 degrees 44 minutes 0 seconds north, longitude: 79 degrees 40 minutes 0 seconds east, (Sigar India), height:= 300m. Nominal start time: as for GNSS scenario #1. Viable running time to maintain specified requirements: as for GNSS scenario #1. Satellite meeting specified requirements to be used for simulation and for which Assistance Data (other than Almanac) shall be generated: Navic: PRN: 4, 6, 9. GPS: PRN: 2, 19, 28 Galileo: tbd Glonass: tbd Beidou: tbd Scenario 3B has the following subtest and is intended to serve NAVIC and GAGAN: Subtest 15
description: The Association of Radio Industries and Business (ARIB) is a Japanese organization that develops and standardizes radio communication technologies. It transposes 3GPP technical specifications into its own standards, such as ARIB STD-T63-25.104 and ARIB STD-T63-36.104, which are referenced by ITU-R Recommendations. These standards cover transmission and reception specifications for single RAT cases, including UTRA BS (FDD) and E-UTRA BS requirements.
explanation: The text explicitly states that ARIB is a Japanese organization involved in developing and standardizing radio communication technologies. It mentions specific standards developed by ARIB, further solidifying its classification as an organization.
section_title: 12.3	Regulatory references in ARIB
biotag_Context: O,O,O,B-Technology,O,O,O,O,O,O,O,O,B-Technology,B-Technology,O,O,O,B-Technology,B-Technology,O,O,O,B-Technology,O,O,O,O,B-Technology,B-Network Function,O,O,O,B-Technology,O,O,O,B-Device,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Organization,I-Organization,I-Organization,I-Organization,I-Organization,I-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,B-Organization,O,O,B-Organization,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,B-Network,B-Network Function,O,O,B-Technology,B-Network Function,O