Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 28.104  Word version:  18.3.0

Top   Top   Up   Prev   Next
1…   5…   6…   7…   7.2.2…   7.2.3…   7.2.4…   7.2.5…   7.2.6…   7.2.7…   7.2.8…   7.3…   8…   9…   10…   A…

 

7.2.6  MDA assisted critical maintenance managementp. 34

7.2.6.1  RAN Node Software Upgradep. 34

7.2.6.1.1  Descriptionp. 34
This MDA capability is for network critical maintenance during RAN node software upgrade process.
7.2.6.1.2  Use casep. 34
As per the current mechanism of software upgrade at RAN node results in service disruption or huge operational cost. Consider a scenario, when a RAN Node is required to shut down manually to undergo critical maintenance for a very short duration of time. Software upgrade can be one such critical maintenance scenario. In such cases, all the resources (bearer, security functions, mobility management) that are managed by this RAN Node need to be purged and reconfigured at another RAN Node (standby RAN Node) or if another RAN Node is not available then resources will be reconfigured again when former RAN Node comes up after software upgrade. Both the situations lead to additional operational expenses and data loss. Operational expense in terms of all the resources to be released/attached again and data loss for all GBR sessions/bearer.
It is expected to use MDAS to optimize the procedure of software upgrade at RAN Node by providing the right time to execute the required upgrade. The software upgrade should be automatically initiated by the OAM system, once configured, during the time frame when the expected impacts are minimum i.e. at the optimal time when there would be minimum expected operational cost and data loss. The Optimal Time (current or futuristic) can be derived by collecting and analysing the data related to DRBs including GBR/non-GBR, state, modification count, ongoing handover etc. MDAS can utilize historical data and AI/ML (e.g. time series based) algorithm to derive the future optimal time frame for software upgrade.
Up
7.2.6.1.3  Requirementsp. 35
Requirement label Description Related use case(s)
REQ-SWA_MDA-01MDA capability for RAN Node software upgrade shall include providing the DRB info analytics output describing the DRBs info at a particular RAN Node(s).RAN Node software upgrade.
REQ-SWA_MDA-02MDA capability for RAN Node software upgrade shall include providing the DRB info analytics output describing the DRB info based on the following DRB characteristics; type (GBR/non-GBR), state (idle/active), modification count (indicating number of times, this bearer has gone for modification since its creation), handover in-progress (indicates whether the bearer is undergoing handover or not).RAN Node software upgrade.
REQ-SWA_MDA-03MDA capability for RAN Node software upgrade shall include providing output describing the DRB info that contain the following information:
  • Time frame/duration at which the output is generated.
  • Whether RAN Node is optimal for upgrade at present.
  • Whether RAN Node will be optimal for upgrade during a future time frame. This will also provide a future frame.
  • Total number of GBR and non-GBR DRBs at future point of time frame. This will also provide a future frame.
RAN Node software upgrade.
Up

Up   Top   ToC