Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 23.700-36  Word version:  18.1.0

Top   Top   Up   Prev   None
0…   4…   5…   5.3.3…   6…   6.2…   6.2.1.2…   6.3…   6.4…   6.5…   6.6…   6.7…   6.8…   6.9…   6.10…   7…   8…   9…

 

9  Conclusionsp. 54

9.1  General conclusionsp. 54

This technical report fulfills the objectives of the study on application architecture for enabling application data analytics. The report includes the following:
  1. Definition of terms and abbreviations used in the study (clause 3);
  2. Key issues identified by the study (clause 4);
  3. Architectural requirements and detailed application architecture for enabling Application Data Analytics (clause 5);
  4. Individual solutions addressing the key issues (clause 6);
  5. Deployment scenarios (clause 7); and
  6. Overall evaluations of all the solutions (clause 8);
Up

9.2  General conclusions for normative workp. 54

For normative work in 3GPP Rel-18, it is recommended to define:
  1. Terms and abbreviations, the definition of terms and abbreviations captured in clause 3 will be reused.
  2. Requirements on ADAE, the architectural requirements identified in clause 4 will be used as baseline architectural requirements; such requirements include also per functionality-imposed requirements as well as requirements for the internal ADAE architecture.
  3. Application architecture for enabling Application Data Analytics Enablement, the architectures as specified in clause 5.3 will be used as baseline architecture.
  4. Deployment scenarios will be considered as captured in clause. Additional deployment models and their implications on the solutions will be considered.
  5. The definition of ADAE analytics services, data sources and corresponding APIs as captured in clause 8.2.2 based on the concluded solutions (see clause 9.3).
Up

9.3  Conclusions of solutionsp. 55

The study concludes with ADAE functionality, following solution considerations for the normative work:
  1. Following individual solutions, corresponding to the key issues, will be considered as candidate solutions:
    1. for Key issue #1 (Support for application performance analytics):
      1. Solution #1 (Support for application performance analytics)
      2. Solution #2 (Data Analytics Enablement)
      3. Solution #4 (Support for performance analytics for UE-to-UE sessions)
      4. Solution #5 (Service experience to support application performance analytics)
    2. for Key issue #2 (Support for edge analytics enablement):
      1. Solution #2 (Data Analytics Enablement)
      2. Solution #3 (Support for edge load analytics)
    3. for Key issue #3 (Support for data collection for application layer analytics):
      1. Solution #2 (Data Analytics Enablement)
    4. for Key issue #4 (Key Issue on interactions with SEAL services):
      1. Solution #2 (Data Analytics Enablement)
    5. for Key issue #5 (Support for slice-related application data analytics):
      1. Solution #6 (Support for slice related application data analytics)
    6. for Key issue #6 (Support for slice configuration recommendation enablement):
      1. Solution #7 (Slice configuration recommendation)
    7. for Key issue #7 (Support for location accuracy analytics):
      1. Solution #8 (Location accuracy analytics)
    8. for Key issue #8 (Support for service API capability analytics):
      1. Solution #9 (Service API analytics)
Up

$  Change historyp. 56


Up   Top