name: BSSGP
full_form: Base Station Subsystem GPRS Protocol
context: NRACHi is the number of PRACHs associated to the ith FPACH. NE-RUCCHi is the number of E-RUCCHs associated to the ith FPACH and NE-RUCCHi equals to . When SF of PRACH code equals to 16, LiE will be 2, otherwise LiE will be 1ã When SF of PRACH code equals to 4, SF of E-RUCCHwill be 8, otherwise E-RUCCHs has the same SF with PRACH. When nE-RUCCHi equals to nRACHi, E-RUCCH will share the same code resource with PRACH. And when SF of PRACH code equals to 4, the code resource assigned to PRACH including two codes (code i and code i+1) of SF 8, E-RUCCH can use the ith code of SF 8. If FPACHi sent an acknowledgement for E-RUCCH information, the sub-frames on which an acknowledgement is sent on FPACHi is fulfilling the following relation: (SFNâ mod LiE)=nE-RUCCHi ; nE-RUCCHi=0,â¦, NE-RUCCHi-1, Where, SFNâ is the sub-frame number of the acknowledgement on FPACH Accordingly, the code resource assigned to PRACH may be used by PRACH or E-RUCCH, we should make two prescript avoiding the collision
description: The Base Station Subsystem GPRS Protocol (BSSGP) is used for communication between the Base Station Subsystem (BSS) and the Serving GPRS Support Node (SGSN) in a GSM or UMTS network. It manages packet data transmission and reception, and supports General Packet Radio Service (GPRS). In this context, BSSGP carries RIM Information between the RNC and the RIM application part.
explanation: BSSGP is classified as a Protocol because it defines rules for carrying specific information (RIM Information) between network components (RNC and RIM application part), which aligns with the definition of a protocol.
section_title: 9.2.3.31	RIM Information
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Parameter,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Connection,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Parameter,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-Connection,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,B-Network,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Technology,I-Technology,I-Technology,I-Technology,O,O,O,O,B-Protocol,O,B-Procedure,O,O,O,B-Network Function,O,O,B-Procedure,O,O