hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.1.3 Potential solutions
| This solution includes defining a new IOC for Network Maintenance CCL, which can be represented by CCLPurpose <<ProxyClass>> as specified in 3GPP TS 28.567 [2], clause 6.3.12. This IOC includes attributes for the following information:
- The type of network maintenance that Network Maintenance CCL needs to deliver, e.... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.1.3.1 Potential solution #1
| This solution includes defining a new IOC for Network Maintenance CCL, which can be represented by CCLPurpose <<ProxyClass>> as specified in 3GPP TS 28.567 [2], clause 6.3.12. This IOC includes attributes for the following information:
- The type of network maintenance that Network Maintenance CCL needs to deliver, e.... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.1.4 Evaluation of potential solutions
| Only one potential solution provided in clause 4.1.3.1 is identified. This potential solution proposes a new IOC for Network Maintenance CCL, which can be represented by CCLPurpose <<ProxyClass>>. It also proposes a new dataType for Network Maintenance CCL result to be supported by CCLReport. The implementation of this... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.2 CCL for network capacity optimization
| |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.2.1 Description
| Cellular networks have multiple managed objects (existing in RAN, CN and OAM) running together to fulfil the required services. This group of managed objects (MO) need to be monitored to check if the existing capacity of the object is enough for the current or near future demands. Network monitoring mechanisms are used... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.2.2 Potential requirements
| REQ-NET-CAP-1: The 3GPP management system should support a capability allowing an authorized MnS Consumer to instantiate a CCL for network capacity optimization and request for optimization of available network capacity.
REQ-NET-CAP-2: The 3GPP management system should support a capability enabling the MnS consumer to... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.2.3 Possible solutions
| This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support a capacity optimization closed control loop, the following can be introduced:
- An IOC for capacity optimization CCL as a new CCL purpose, say called CapacityOptimizationCCL that inherits from a closed cont... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.2.4 Evaluation of solution
| The solution fulfils all the requirements and recommended to be considered for the normative work.
|
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.3 CCL for Automated status monitoring
| |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.3.1 Description
| This use case describes a scenario in which an MnS consumer may request a CCL for continuous monitoring of network status and resolution of any detected issues, such as performance outliers. The MnS consumer may request to monitor the status of a complete network or a specific subset of the network.
Based on the reque... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.3.2 Potential requirements
| REQ-Monitor-CCL -1: The 3GPP management system should have the capability to allow MnS consumer to instantiate a closed control loop for Automated status monitoring
REQ- Monitor-CCL -2: The 3GPP management system should have the capability to enable the MnS consumer to instantiate a closed control loop with the scope ... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.3.3 Potential solutions
| This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support the management of a status monitoring closed control loop, it is proposed to:
- introduce an IOC for status monitoring CCL, say called StatusMonitoringCCL. It is a CCL purpose that inherits the capabilities... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.3.4 Evaluation of solutions
| Only one potential solution is provided in clause 4.3.3 which enables instantiating a closed control loop for Automated status monitoring including the scope to be monitored. It is a feasible solution to address requirements REQ-Monitor-CCL-1 and REQ-Monitor-CCL-2. It is recommended to proceed to normative phase.
N... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.4 CCL for Multi-domain ES Optimization
| |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.4.1 Description
| TS28.310 [5] and 28.541 [6] have specified capabilities for energy saving management where a distributed or centralized Energy Saving Function (DESF, CESF) decide whether to activate a cell (send a cell into energy saving state) or to deactivate a cell (wake up a cell from an energy saving state). The DESF and CESF are... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.4.2 Potential requirements
| REQ- CCL-ES-1: The management system should enable the MnS consumer to compose or instantiate the energy savings closed control loop for multi-domain energy saving optimization.
|
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.4.3 Possible solutions
| This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support compose or instantiate the energy savings closed control loop for multi-domain energy saving optimization, the following can be introduced:
- an IOC for multi-domain energy savings optimization CCL purpose ... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.5 Dynamic CCL for resource optimization
| |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.5.1 Description
| A CCL may require different kinds of input to address its requirements. 3GPP TS 28.104 [4], specified MDA with reports on different kinds of analysis of network issues, predictions of potential issues and corresponding relevant causes and recommended actions for preventions, and/or prediction of network and/or service ... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.5.3 Possible solutions
| This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support the composition of a CCL on network slicing resource optimization, it is proposed:
- to introduce an IOC for network slice resource optimization closed control loop.
- The network slice resource optimizat... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.5.2 Potential requirements
| REQ- CCL-RO-1: The management system should enable the MnS consumer to compose a network slice resource optimization closed control loop that uses MDA capabilities as analytics components of the CCL
|
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.6 Closed Control Loop traceability
| |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.6.1 Description
| CCLs may be instantiated or execution configured by several MnS consumers, some by other network management entities in an automated manner. E.g.,, during fulfilment of an intent, the intent handling function may need to instantiate control loops to fulfil tasks derived from the received intent. On the other hand, a C... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.6.2 Potential requirements
| REQ-CCL_Trace-1: The 3GPPP management system should provide information on the CCL to identify the management entity that instantiated CCL and the task which the CCL is required to accomplish for that entity.
REQ-CCL_Trace-2: The 3GPPP management system should provide a capability allowing the MnS consumer to indicat... |
4f0bf3de05c8f2635add4d0daab5ffd7 | 28.889 | 4.6.3 Potential solutions
| This solution proposes add three attributes in the CCL model definitions, i.e.:
• the identity of the entity (e.g., each intent handling function) which instantiated the CCL or triggered the specific task on the CCL. This is only used by the CCL to match tasks for traceability.
• the task for the closed loop,... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 1 Scope
| The present document studies on how Coverged Charging support CAPIF enhancements and new Charging scenarios brought by the CAPIF framework, as defined in 3GPP TS 23.222 [2].
The following items are studied:
• possible charging scenarios and requirements related to service API/AEF Instantiation and Multiple Provid... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 3 Definitions of terms, symbols and abbreviations
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
3GPP 3rd Generation Partnership Project
5GS 5g System
AEF API Exposing ... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 4 Concepts and background
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 4.1 General Description
|
The CAPIF core function provides the centralized CAPIF APIs that enable onboarding, discovery, security, and monitoring of exposed APIs. API invokers connect to the CAPIF core via CAPIF-1 and CAPIF-2 interfaces for onboarding and discovery of APIs, while CAPIF-1e extend these capabilities by enabling the authorizatio... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 4.2 Background
| The Common API Framework defined, in 3GPP TS 23.222 [2], offers a uniform approach for securely exposing and utilizing network APIs. It incorporates shared functional components and reference points to facilitate API invoker verification, permission control, oversight and administration. This setup allows developers an... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1 Topic #1 CAPIF Converged Charging support for service API/AEF
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.1 General description and assumptions
| The reference points used for the API invoker within and outside the PLMN trust domain and to discover service APIs are the CAPIF-1 and CAPIF-1e reference points (TS 23.222 [2] clauses 6.4.2 and 6.4.3), which exists between the API invoker and the CAPIF core function.
|
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.2 Use Cases
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.2.1 Use Case #1.1: API Invokers Service Charging
| An operator provides CAPIF Core Functions and CAPIF-1 and CAPIF-1e reference points towards API Invokers and wants to be able to charge the API Invokers for services it provides.
|
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.2.2 Use Case #1.2: Converged Charging for API Invoker Onboarding and Discovery in Non-Trusted Domain
| The API Invokers outside the PLMN trust domain reach CAPIF Core function through CAPIF-1e reference point. The API Invoker performs onboarding to authenticate and authorize access, followed by service API discovery queries. Charging is applied based on the success of the onboarding attempt and discovery operations.
Th... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.3 Potential charging requirements
| REQ-CH_CAPIF_RP-01: Charging for services provided via the CAPIF-1 and CAPIF-1e reference points shall be supported.
REQ-CH_CAPIF_RP-02: Charging for services provided via the CAPIF-1 and CAPIF-1e reference points shall be supported.
REQ-CH_CAPIF_RP-03: Charging for onboarding and discovery events via CAPIF-1e.
REQ-... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.4 Key Issues
|
Key issue #1.1: Identify the chargeable events for reference point CAPIF-1 and CAPIF-1e.
Key issue #1.2: Identify the placement of the charging trigger function for reference point CAPIF-1 and CAPIF-1e.
Key issue #1.3: Identify the chargeable events and information for onboarding/discovery in non-trusted domains vi... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.5 Possible Solutions
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.5.1 Solution #1.1: CTF in CCF for CAPIF-1 and CAPIF-1e
| A possible solution for key issue #1.2 covering requirement REQ-CH_CAPIF_RP-01.
The CAPIF-1 and CAPIF-1e reference points (TS 23.222 [2] clauses 6.4.2 and 6.4.3), which exists between the API invoker and the CAPIF core function, is used for the API invoker within and outside the PLMN trust domain and to discover servi... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.5.2 Solution #1.2: Chargeable services for CAPIF-1 and CAPIF-1e
| A possible solution for key issue #1.1 covering requirement REQ-CH_CAPIF_RP-01.
The CAPIF-1 and CAPIF-1e reference points (TS 23.222 [2] clauses 6.4.2 and 6.4.3), which exists between the API invoker and the CAPIF core function, is used for the API invoker within and outside the PLMN trust domain and to discover servi... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.5.3 Solution #1.3: CTF in CCF for CAPIF-4 and CAPIF-4e
| A possible solution for key issue #1.2 covering requirement REQ-CH_CAPIF_RP-01.
The CAPIF-4 and CAPIF-4e reference points (TS 23.222 [2] clauses 6.4.7 and 6.4.10), which exists between the API publishing function within the PLMN trust domain or 3rd party trust domain and the CAPIF core function within the PLMN trust d... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.5.4 Solution #1.4: Chargeable services for CAPIF-4 and CAPIF-4e
| A possible solution for key issue #1.2 covering requirement REQ-CH_CAPIF_RP-01.
The CAPIF-4 and CAPIF-4e reference points (TS 23.222 [1] clauses 6.4.7 and 6.4.10), which exists between the API publishing function within the PLMN trust domain or 3rd party trust domain and the CAPIF core function within the PLMN trust d... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.6 Evaluation
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.1.7 Conclusion
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2 Topic #2 CAPIF Converged Charging of multiple API Providers
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.1 General description and assumptions
| Clause 6.2.2 of 3GPP TS 23.222 [2] describes on how CAPIF Interconnection is supported.
The reference points used for publishing the service API information are the CAPIF-4 and CAPIF-4e reference points (TS 23.222 [2] clauses 6.4.7 and 6.4.10), which exists between the API publishing function within the PLMN trust dom... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.2 Use Cases
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.2.1 Use Case #2.1: API Invoker accessing Service APIs across Interconnected CAPIF Provider Domains
| An API Invoker onboarded in CAPIF Provider A discovers and invokes service APIs published by CAPIF Provider B via inter-domain reference points (CAPIF-6e) as defined in TS 23.222 [2] Clause 6.2.2.
The same API Invoker subscription may be charged for:
• Service API invocations in Provider B
There is the possibil... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.2.2 Use Case #2.2 API publishing in CAPIF core function by API Provider
| An operator provides CAPIF Core Functions and CAPIF-4 and CAPIF-4e reference points towards API Providers and wants to be able to charge the API Providers for services it provides.
Charging party: CAPIF Provider
Charged party: API Provider
|
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.2.3 Use Case #2.3: Converged Charging for API Updates and Management Across Interconnected CAPIF Provider Domains
| An API Provider B (in a non-trusted domain) publishes service APIs via CAPIF-4e to CAPIF Provider A's for discovery. Subsequently, the API Provider performs updates, unpublishes, or retrieves API information across domains. Charging is triggered for these management operations, with potential fees for cross-domain sync... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.3 Potential charging requirements
| The following are potential high-level charging requirements, derived from the requirements in TS 23.222 [2].
REQ-CH_CAPIF_IC-01: The CAPIF should support converged charging for APIs service management either per CAPIF provider A or B.
REQ-CH_CAPIF_IC-02: Charging for services provided via the CAPIF-4 and CAPIF-4e re... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.4 Key issues#2: Charging events and charging information required
|
Key issue #2.1: Identification of the charging information and chargeable event for API Invoker accessing Service APIs of a CAPIF Provider in an inter-connection CAPIF scenario;
Key issue #2.2: Identify the chargeable events for reference point CAPIF-4 and CAPIF-4e.
Key issue #2.3: Identify the placement of the cha... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.5 Possible Solutions
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.6 Evaluation
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.2.7 Conclusion
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3 Topic #3 CAPIF Converged Charging of API Invoker Authorization and Authentication Impact
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.1 General description and assumptions
| Clause 6.3.7 describes on CAPIF Authentication is supported and Clause 8.25.2.17 of 3GPP TS 23.222 [2] describes on how CAPIF Interconnections Authentication and Authorization is supported.
The reference points used for the API invoker to authentication and authorization are the CAPIF-2 and CAPIF-2e reference points (... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.2 Use Cases
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.2.1 Use Case #3.1: Converged Charging for API Invoker Authentication and Authorization Events Impact
| An API Invoker is onboarded in a single CAPIF Core Function (CCF) and performs authentication (e.g., OAuth 2.0 token request) and authorization (scope validation, policy enforcement) prior to service API invocation via CAPIF-1, CAPIF-2, CAPIF-3 reference points.
The following events may be considered:
• Authoriz... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.2.2 Use Case #3.2 Authorization in CAPIF core function
| An operator provides CAPIF Core Functions and CAPIF-3 and CAPIF-3e reference points towards API Provider and wants to be able to charge the API Provider for services it provides.
Charging party: CAPIF Provider
Charged party: API Provider
|
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.2.3 Use Case #3.3: Authorization and authentication in application exposure function
| An operator provides Application Exposure Function and CAPIF-2 and CAPIF-2e reference points towards API Invokers and wants to be able to charge the API Invokers for services it provides.
Charging party: CAPIF Provider
Charged party: API Provider
|
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.3 Potential charging requirements
| The following are potential high-level charging requirements, derived from the requirements in TS 23.222 [2].
REQ-CH_CAPIF_AA-01: The Charging Function may trigger charging for authorization events: scope granted/revoked, service API overlimit usage.
REQ-CH_CAPIF_AA-02: The generated CDRs would be possible to correla... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.4 Key issues#3: Charging events and charging information required
|
Key issue #3.1: Identification of the charging information and chargeable events for APIs service Operation and Management Authorization;
Key issue #3.2: Identify the chargeable events for reference point CAPIF-3 and CAPIF-3e.
Key issue #3.3: Identify the placement of the charging trigger function for reference poi... |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.5 Possible Solutions
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.6 Evaluation
| |
01c2a1b881b9a58736bc921e2a1cbda5 | 28.891 | 5.3.7 Conclusion
|
6 Evaluation
7 Conclusion
Annex A (informative):
PlantUML
A.1 Flows
A.1.1 Figure 5.1.5.1-1
@startuml
<style>
element {
BackGroundColor: white;
}
</style>
hide footbox
participant APP as "API\nInvoker"
participant CCF as "CCF\n(CTF)"
participant CHF as "CHF"
APP -> CCF : 1. ... |
70172d647bd0430cf55959218f45740d | 25.902 | 1 Scope
| The present document is part of the Release 6 work item "FDD Enhanced Uplink".
The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing Iub/Iur specifications, needed for the introduction of "Iub/Iur Congestion Control" measures for Release 6.
This work task belongs t... |
70172d647bd0430cf55959218f45740d | 25.902 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not a... |
70172d647bd0430cf55959218f45740d | 25.902 | 3 Definitions, symbols and abbreviations
| |
70172d647bd0430cf55959218f45740d | 25.902 | 3.1 Definitions
| For the purposes of the present document, the following terms and definitions apply:
E-DCH: Enhanced DCH, a new dedicated transport channel type or enhancements to an existing dedicated transport channel type.
|
70172d647bd0430cf55959218f45740d | 25.902 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
void
|
70172d647bd0430cf55959218f45740d | 25.902 | 3.3 Abbreviations
| For the purposes of the present document, the following abbreviations apply:
CFN Connection Frame Number
DRT Delay Reference Time
FSN Frame Sequence Number
HSDPA High Speed Downlink Packet Access
RFN RNC Frame Number
RNL Radio Network Layer
SFN System Frame Number
TNL Transport Network Layer
|
70172d647bd0430cf55959218f45740d | 25.902 | 4 Background and introduction
| In RAN Plenary Meeting #27, it was agreed to create a Technical Report on the subject of "Iub/Iur congestion control (Rel-6)".
The technical objective of this TR is to improve the Congestion Handling performance of the UTRAN over the Iub and the Iur interfaces.
Any solution should take into account backwards compat... |
70172d647bd0430cf55959218f45740d | 25.902 | 5 Requirements
| For Iub/Iur Congestion Controlled, the following requirements were agreed in RAN3:
• RNC shall have a means for detecting congestion.
• Receiving node shall have a means for notifying the source of congestion i.e. sending node, that congestion has occurred.
• Iub/Iur Congestion control for both HSDPA and... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.1 Background information
| |
70172d647bd0430cf55959218f45740d | 25.902 | 6.1.1 Introduction
| There are many types of congestion control mechanisms, the main groups are window based, rate based or combination of both. The method often used for congestion detection is the method based on the loss of packets. Other methods appropriate for congestion detection are: packet delay, average queue and rate difference. ... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.1.2 Example 1: TFRC
| Congestion Factor depends on the congestion control algorithm, and on the congestion detection method. By detecting the loss of packets and using some method to derive RTT, transmit rate could be prepared according to transmit rate formula X = f(s, RTT, p) where s is the packet size in bytes/second, RTT – the round tri... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.1.3 Example 2: "ABR like" congestion control
| "ABR like" congestion control has "additive increase, exponential decrease" type of algorithms. Different formulas exist for computing ACR (Allowed Cell Rate) for increase and for decrease. ACR i.e. current transmission rate in cell/s, should be computed in octets or in number of MAC-d PDUs. Then from the computed ACR... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.2 Functional description
| |
70172d647bd0430cf55959218f45740d | 25.902 | 6.2.1 Iub/Iur congestion detection
| The Node B scheduler decides on when and with which bit rate each and every UE is allowed to transmit in the cell. Each received MAC-es PDU is placed in a frame protocol data frame and sent to the SRNC (in some cases several PDUs are bundled into the same data frame). For each data frame, the Node B attach the followin... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.2.2 Iub/Iur congestion reduction
| When the RNC has detected that there is a congestion situation in the transport network, it needs to inform the Node B that this is the case. This is done by means of a frame protocol control frame, in which the Node B is informed about the congestion situation. This control frame will be called Congestion Indication. ... |
70172d647bd0430cf55959218f45740d | 25.902 | 1 The purpose of the congestion control, is not to act as a flow control but rather as an "emergency break" in order to keep the system at a stable state.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 2 The output bit rate from the node B depends on many things, for example radio interference, distance from mobile to Node B, available hardware resources etc. The Node B scheduler will need to take all that into consideration when assigning the bit rate to each mobile.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 3 Performance wise, to specify very detailed behaviour when the control frame is received is not possible due to the reasons in bullet 2.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 6.2.3 A similar solution for HSDPA
| It has been acknowledged that similar functionality shall also be introduced for HSDPA. Further it was expressed that such a solution should be as similar as possible to any solution for Enhanced Uplink. In this clause such functionality is proposed and analysed.
From a conceptual point of view, the reuse of the conc... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.2.4 Handling of the Iur
| Two philosophies can be distinguished for the handling of the Iub traffic, referred to as the "Iub pipe" and the "Iub cloud".
|
70172d647bd0430cf55959218f45740d | 25.902 | 6.2.4.1 Iub pipe philosophy
|
Figure 3: "Iub pipe" philosophy
With the "Iub pipe", logic the CRNC enforces the traffic limit injected on the Iub interface in the DL, so it is able to instantaneously detect any congestion situation. The advantage of this approach is that there is no need for using any new congestion mechanisms in the Node B, beca... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.2.4.2 Iub Cloud philosophy
|
Figure 5: "Iub cloud" philosophy
With the "Iub cloud" logic, the traffic injected by the RNC is less tightly controlled i.e. the RNC is likely to inject too much traffic in the network, thus yielding a congestion situation. This approach should allow for statistical multiplexing in some scenarios without complex con... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.2.4.3 Co-existence of the two philosophies
| In the situation where the HS-DSCH connection extends across the Iur interface it is important to note that – should it be employed – the HS-DSCH flow control may be terminated in the DRNC.
In this scenario, two separate flow control loops would then be employed on both Iub and Iur.
If, in the "Iub pipe" logic, a DR... |
70172d647bd0430cf55959218f45740d | 25.902 | 1 The DRNC makes the decision to use Congestion Control and indicates to the Node B – via Control Plane - not to perform Congestion Control (e.g. using the Physical Shared Channel Reconfiguration procedure).
| |
70172d647bd0430cf55959218f45740d | 25.902 | 2 The DRNC makes the decision and indicates to the SRNC that it shall include the user plane protocol extensions that are used by the Node B to detect congestion (namely the timestamp and the Frame Sequence Number) by introducing a new User Plane Congestion Field Inclusion IE in the HS-DSCH FDD/TDD Information Response... | This would allow the DRNC to indicate to the SRNC if User Plane fields destined to be used for Congestion detection by the Node B are to be included or not in the HS-DSCH Data Frames. If not included, Congestion detection and Congestion Control will not be employed by the Node B.
This second approach is preferred as ... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.3 Impacts on Iub/Iur control plane protocols
| TS 25.423
• a new User Plane Congestion Field Inclusion IE in the HS-DSCH FDD/TDD Information Response IEs.
|
70172d647bd0430cf55959218f45740d | 25.902 | 6.4 Impacts on Iub/Iur user plane protocols
| TS 25.427
• EDCH data frame: Introduction of a 4 bit Frame Sequence Number (FSN) field.
• EDCH data frame: Clarification that CFN and SFN can be used for dynamic delay measurements.
• Introduction of a Congestion Status control frame.
• Specification of desired behaviour when Node B receives the Con... |
70172d647bd0430cf55959218f45740d | 25.902 | 6.5 Open issues
| • Thus far Iub/Iur Congestion Control has been considered for HSDPA and Enhanced Uplink only. Could any final solution be applicable for UL and DL DCH?
|
70172d647bd0430cf55959218f45740d | 25.902 | 6.6 Backwards compatibility
| void
|
70172d647bd0430cf55959218f45740d | 25.902 | 7 Agreements and associated contributions
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.