name: ECUR
full_form: Event Charging with Unit Reservation
context: 6.1.2.2.1.1 ECUR - Reserve Units and Debit Units Operations Figure 6.2 shows the transactions that are required on the Ro interface in order to perform ECUR with Reserve Units and Debit Units operations. Multiple replications of both of these operations are possible. Figure 6.2: ECUR - Reserve Units and Debit Units Operations 1. The AS/MRFC receives a SIP related service request from S-CSCF. The service request may be initiated by either the user or an AS/MRFC. The Reserve Units Operation is performed as described in TS 32.200 [2]. 2. In order to perform Reserve Units operation for a number of units (monetary or non-monetary units), the AS/MRFC sends an CCR with CC-Request-Type AVP set to INITIAL-REQUEST to the ECF. If known, the AS/MRFC may include Requested-Service-Unit (RSU) AVP (monetary or non monetary units) and Acc-Interim-Interval (AII) AVP in the request message. 3. If the service cost information is not received by the ECF, the ECF determines the price of the desired service
description: Event Charging with Unit Reservation (ECUR) is a procedure for reserving and debiting units in the context of event-based charging. It involves a series of transactions between network functions, including the Application Server/Media Resource Function Controller (AS/MRFC), the Service-CSCF (S-CSCF), and the Event Charging Function (ECF). The procedure includes steps such as sending a SIP-related service request, performing Reserve Units Operation, and determining the price of the desired service.
explanation: The context describes ECUR as a series of transactions and operations between network functions to manage event-based charging. This indicates that ECUR is a specific sequence of actions or steps taken by the network to achieve a particular goal, which aligns with the definition of a Procedure.
section_title: 6.1.2.2.1Message Flows - Successful Cases and Scenarios
biotag_Context: O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,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-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,I-Procedure,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-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O