hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
5f53d3479ff0f89c2731a65731bf0951 | 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.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.5 Possible Solutions
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.6 Evaluation
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.7 Conclusion
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2 Topic #2 CAPIF Converged Charging of multiple API Providers
| |
5f53d3479ff0f89c2731a65731bf0951 | 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... |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.2 Use Cases
| |
5f53d3479ff0f89c2731a65731bf0951 | 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... |
5f53d3479ff0f89c2731a65731bf0951 | 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
|
5f53d3479ff0f89c2731a65731bf0951 | 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... |
5f53d3479ff0f89c2731a65731bf0951 | 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... |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.5 Possible Solutions
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.6 Evaluation
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.7 Conclusion
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3 Topic #3 CAPIF Converged Charging of API Invoker Authorization and Authentication Impact
| |
5f53d3479ff0f89c2731a65731bf0951 | 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 (... |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3.2 Use Cases
| |
5f53d3479ff0f89c2731a65731bf0951 | 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... |
5f53d3479ff0f89c2731a65731bf0951 | 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
|
5f53d3479ff0f89c2731a65731bf0951 | 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
|
5f53d3479ff0f89c2731a65731bf0951 | 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... |
5f53d3479ff0f89c2731a65731bf0951 | 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... |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3.5 Possible Solutions
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3.6 Evaluation
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3.7 Conclusion
|
6 Evaluation
7 Conclusion
Annex <A> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-8
SA5#162
S5-253360
Initial Skeleton
0.0.0
2025-10
SA5#163
S5-254806
S5-254807
S5-254808
S5-254809
S5-254810
Document Structure ... |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.4.1 Key issues#1.1: Charging events and charging information required
| Identify the chargeable services and events for CAPIF-1 and CAPIF-1e.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.4.2 Key issues#1.2: Charging events and charging information required
| Identify the placement of the charging trigger function for CAPIF-1 and CAPIF-1e.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.23 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... |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.34 Key issues#12.1: 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... |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.45 Possible Solutions
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.56 Evaluation
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.67 Conclusion
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3.23 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... |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3.34 Key issues#13.1: 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... |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3.45 Possible Solutions
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3.56 Evaluation
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.3.67 Conclusion
|
6 Evaluation
7 Conclusion
Annex <A> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-8
SA5#162
S5-253360
Initial Skeleton
0.0.0
2025-10
SA5#163
S5-254806
S5-254807
S5-254808
S5-254809
S5-254810
Document Structure ... |
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
| |
70172d647bd0430cf55959218f45740d | 25.902 | 1 The development of an Iub/Iur Congestion control solution should bear in mind both the E-DCH and HSDPA features.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 2 Iub/Iur Congestion control for both HSDPA and Enhanced Uplink should – if possible – employ similar solutions.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 3 The RNC remains the entity in charge of the Congestion Control function.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 4 NodeB behaviour when receiving the congestion indication shall be specified.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 5 The detection algorithm will not be specified in the TR. (However example algorithms may be given in an annex.)
| |
70172d647bd0430cf55959218f45740d | 25.902 | 6 Congestion indication should be signalled via the user plane.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 7 Signalling of Congestion via the user plane will also include varying levels of congestion severity.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 8 Congestion Detection will be performed on a per flow basis.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 9 Within the E-DCH data frame (user plane), congestion detection will be based upon a time reference or a sequence number.
| 10 For the handling of Iub/Iur Congestion due to HSDPA, the CRNC decides whether all or none of the HS-DSCH MAC-d Flows of a context are subject to Congestion Control.
|
70172d647bd0430cf55959218f45740d | 25.902 | 11 A "counter" field be attached to EVERY E-DCH data frame.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 12 The "counter" field within the E-DCH frame will take the form of a "frame sequence number" (FSN).
| |
70172d647bd0430cf55959218f45740d | 25.902 | 13 Different levels of congestion shall be indicated by "No congestion", "TNL Congestion – detected by delay build-up", "TNL Congestion – detected by frame loss".
| |
70172d647bd0430cf55959218f45740d | 25.902 | 14 The resulting behaviour following the signalling of Congestion Indication will not be defined – this is an implementation matter.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 15 For impacts upon RNL xxxAP Signalling protocols, please refer to CR 1080 against TS 25.423. This CR allows a CRNC to decide whether a particular E-DCH flow is subject to congestion control at flow setup.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 16 Regarding the possibility of an Iub/Iur Congestion Control solution incorporating Rate Adaptation, this functionality was discussed, but a solution was not found, nor foreseen as possible at this time.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 17 With respect to Softhandover, no issues have been found concerning the relationship/interaction with E-DCH Congestion Control.
| 8 Specification impact and associated Change Requests
This clause is intended to list the affected specifications and the related agreed Change Requests. It also lists the possible new specifications that may be needed for the completion of the Work Task.
CR Title
Impacted Specification
CR implemented against vers... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 1 Scope
| This present document is for the 3GPP Release 6 Work Item "Network Assisted Cell Change – Network Side Aspects.".
The purpose of the present document is to aid TSG RAN WG3 to standardise the signalling of relevant GERAN information during cell re-selection across the relevant UTRAN interfaces.
This document is inten... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 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... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 3 Definitions, symbols and abbreviations
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 3.1 Definitions
| For the purposes of the present document, the following terms and definitions apply.
Local RNC: the local RNC(s) to a given cell or BSS is/are the RNC(s) with cells which are neighbouring to the GERAN cell or BSC.
Remote RNC: an RNC is remote to a given GERAN cell or BSS if none of its cells are neighbours of the GER... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Gb Interface between the BSS and the 2G SGSN
Gn Interface between two GSNs in the same PLMN
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 3.3 Abbreviations
| Applicable abbreviations can be found in [3]. For the purposes of the present document, the following abbreviations apply:
BSSGP Base Station Subsystem GPRS Protocol
DRNC Drift RNC
GERAN Gsm/Edge Radio Access Network
NACC Network Assisted Cell Change
PSI Packet System Information
RAN Radio Access Network
RIM ... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 4 Introduction
| At the 3GPP TSG RAN #19 meeting, the Work Item Description on "Network Assisted Cell Change from UTRAN to GERAN – Network Aspects" was approved.
In today's GPRS networks (without NACC), cell re-selection can causes a service interruption in the region of 4 – 8 seconds, which obviously has an impact on the user experie... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 5 Requirements
| The standardisation of NACC from UTRAN to GERAN shall meet the following requirements:
1) The impact to the Gb and Gn interfaces shall be minimised.
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 6 Study Areas
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1 UTRAN NACC signalling architecture
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.1 General
| Three possible mechanisms have been identified to gain access to the GERAN SI/PSI at the SRNC, whilst minimising the impacts on the existing Gb/Gn procedures:
1) The (P)SI is stored by the SRNC.
2) The (P)SI is stored by the local RNC
3) O&M-based distribution of (P)SI.
These solutions are explained in the followi... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.2 Solution 1: (P)SI stored by the SRNC
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.2.1 General description
| This solution is based on the serving RNC directly requesting and receiving the SI/PSI from the target BSS and it is depicted in figure 1.
1) The SRNC receives a measurement report from the UE and decides to move the UE to GERAN.
NOTE: The SRNC could request the info earlier on receiving GERAN n_cell info from DRNC.... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.2.2 Analysis of the solution
| Pros:
1) No additional Iur load generated.
2) No additional Iur implementation required.
3) Synchronised update of SI/PSI is possible using "on-modification" measurement reporting.
Cons:
1) Generally more SI/PSI stored in each RNC than in other solutions.
2) Additional load on the SGSN due to... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.3 Solution 2: (P)SI stored by the local RNC
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.3.1 General description
| This solution is based on the local RNC requesting SI/PSI from the BSS, and receiving it on an "on-modification" basis. This procedure is depicted in figure 2.
1) After installation and configuration of the GERAN neighbouring cell lists in the local RNC, a REQUEST message is sent to the SGSN requesting GERAN SI/PSI fo... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.3.2 Analysis of the solution
| Pros:
1) Generally less SI/PSI stored in each RNC than in other solutions.
2) Synchronised update of SI/PSI is possible using "on-modification" measurement reporting.
3) Impact on SGSN load is minimised.
Cons:
1) More Iur signalling than SRNC terminated solution.
2) Additional load on the DRNC... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.