name: BC
full_form: Broadcast
context: Here, two new concepts are introduced: First: Service Application PLMN Code (SAPC) and, second: Addition of new services in ENUM under the control of the operators who have reached a roaming agreement for a set of subscribers. Service Application PLMN Code (SAPC): Service Application PLMN Code (SAPC) is a unique E.164 number assigned to a PLMN providing a set of services. Table 1 gives examples of SAPC codes for different PLMNs. It should be noted that the use of wild card to denote an exchange code would work equally well and is covered by the SAPC concept introduced in this draft paper. However, the wild card use in DNS can cause unpredictable results. It is also recommended that it should not be used in DNS/ENUM. SAPC code assignment will undoubtedly work to associate a set of services uniquely with a PLMN. SAPC concept applies to other services as well as potential future services such as Instant Messaging, Dispatch etc. which may not be based on or associated with E.164 numbering
description: The Broadcast (BC) Bearer Context Setup procedure involves the exchange of messages between the gNB-CU-CP and gNB-CU-UP to establish or modify broadcast bearer resources. The BC BEARER CONTEXT SETUP REQUEST message is sent by the gNB-CU-CP to initiate the procedure, while the BC BEARER CONTEXT SETUP RESPONSE message is sent by the gNB-CU-UP in response, containing information about successfully established and failed broadcast bearer resources.
explanation: The context describes a specific communication exchange between network components (gNB-CU-CP and gNB-CU-UP) for setting up broadcast bearer resources. The mention of 'BC BEARER CONTEXT SETUP REQUEST' and 'BC BEARER CONTEXT SETUP RESPONSE' messages indicates that BC is related to the content being exchanged, which aligns with the definition of a Message entity type.
section_title: 8.6.1.1.2	Successful Operation
biotag_Context: O,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,I-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,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,B-Network,O,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,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,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,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
biotag_Description: O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O