name: RNS
full_form: Radio Network Subsystem
context: 4b: UTRAN and GERAN Iu mode connection with Iur-g Figure 4c: UTRAN and GERAN A/Gb mode connection with Iur-g for 1.28Mcps TDD Each RNS is responsible for the resources of its set of cells. For each connection between User Equipment and the UTRAN, One RNS is the Serving RNS. When required, Drift RNSs support the Serving RNS by providing radio resources as shown in figure 5. The role of an RNS (Serving or Drift) is on a per connection basis between a UE and the UTRAN. Figure 5: Serving and Drift RNS To support UE mobility between UTRAN and GERAN Iu mode, the Serving RNS may be connected to the DBSS and vice versa as illustrated in figures 5a and 5b. For 1.28Mcps TDD, to support UE mobility between UTRAN and GERAN A/Gb mode, the Serving RNS may be connected to the TBSS as illustrated in figure 5c. The role of an RNS or BSS (Serving or Drift) is on a per connection basis between a UE and the UTRAN/GERAN Iu mode, or between a UE and the UTRAN /GERAN A/Gb mode for 1.28Mcp TDD. Figure 5a:
description: The Radio Network Subsystem (RNS) is a component of the Universal Terrestrial Radio Access Network (UTRAN) that manages radio resources for a set of cells. Each RNS can act as either a Serving RNS or a Drift RNS, with the role determined on a per-connection basis between User Equipment (UE) and the UTRAN. The Serving RNS is responsible for providing radio resources to support UE mobility, while the Drift RNS may assist by providing additional radio resources when needed.
explanation: The context describes the RNS as a component within the UTRAN architecture responsible for managing radio resources and supporting UE mobility. This aligns with the definition of a Network Function, which encompasses components that perform specific tasks within a telecommunications network.
section_title: 6	UTRAN Architecture
biotag_Context: O,B-Network,O,B-Mode,I-Mode,I-Mode,O,O,O,O,O,B-Network,O,B-Network,B-Mode,I-Mode,O,O,O,O,O,B-Technology,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network,I-Network,O,O,B-Device,O,O,B-Network,O,B-Network,B-Interface,O,O,B-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Network,O,B-Network,O,O,O,B-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Interface,O,O,O,O,B-Device,O,O,B-Network,O,B-Mode,I-Mode,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,B-Network,I-Network,I-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,B-Procedure,I-Procedure,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Network,I-Network,O,O,O,O,O,O,O,O,O