hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.8.1.1 Field descriptions
| The specifications only use comments to delineate blocks of ASN.1, e.g., -- TAG-RRCREESTABLISHMENT-START/STOP and ASN1-START/STOP, and to assign need codes, e.g., -- Need R, and conditional presence, e.g., -- Cond L2RemoteUE, to fields. Therefore, it is feasible to write field descriptions in the line immediately prece... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.8.1.2 Conditional presence definitions
| Conditional presence definitions could be defined inline to the ASN.1, but not inside of the IE definitions since the conditional presence can apply to multiple ASN.1 IEs. To differentiate conditional presence definitions from other types of comments, a simple syntax like that described in section 5.8.1.1 could be used... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.8.1.3 Rendering the ASN.1
| The audience of 3GPP specifications is broad, including mobile network operators (MNO), UE vendors, UE chipset vendors, NW vendors, governmental bodies, researchers, delegates, standards defining organizations (SDO), and the interested public. Therefore, it is reasonable to produce a professionally rendered specificati... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.8.1.4 Editing the ASN.1
| Integrated development environments (IDEs), which are essentially text editors that at least support syntax highlighting and indentation and commonly support integration with Git and source code syntax checkers and compilers, can be useful in displaying source files such as ASN.1 files in a more human-friendly way. An ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.8.1.5 Storing the ASN.1
| RAN4 stores their band combination tables in the JSON file format in the 3GPP Forge, and SA5 store YAML files in the 3GPP Forge (https://forge.3gpp.org/rep/sa5/CH/-/tree/Rel-19/OpenAPI). Similarly, it would be feasible to store ASN.1 in asn files in the 3GPP Forge.
Further, we can draw from the example of TS 32.291, a... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6 Proposals for Tools and Ways of Working
| Editor's note: corresponds to objective 3.
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.1 Proposal #1: tools and ways of working for OpenDocument
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.1.1 Description
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.1.1.1 Description of tools
| For editing ODT documents, LibreOffice is a natural choice, however it is by no means the only option. Here is a short and not exhaustive list of such tools with short summaries of their strengths:
- LibreOffice Writer: This is arguably the most popular and comprehensive ODT editor. It's free, open-source, and cross-p... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2 Proposal #2 Git for Version Control
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1 Description
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.0 Overview
| Git (https://git-scm.org) is an open-source distributed version control system, which tracks changes to files and enables collaboration.
Distributed means that every user can download and update a full copy of the repository, including files and their history locally (not just the current files, but also the full chan... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.1 Description of tools
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.1.0 Overview
| The following are basic git commands for creating and saving changes (see Figure 6.2.1.0-1):
- git clone - Create a full local copy of a remote repository, it contains both file and changes history. Cloning a repository is the action of downloading the repository from the remote server.
- git fetch - Download changes... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.1.1 Git commit
| The Git commit command records a snapshot of the project’s staged changes, capturing the state of the codebase at a particular point of time. Each commit consists of following elements:
- Metadata - Includes author, committer, message, timestamps, and a unique identifier called a SHA hash.
- Commit Message - Describe... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.1.2 Git branching
| Git branching is essential for managing projects efficiently in collaborative and feature-driven development workflows. Key aspects of branching include:
- Creating independent lines of development
- Isolate changes and work on new features, bug fixes, or experiments without affecting the main codebase
- Enable coll... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.1.3 Git history
| Git history provides detailed information about every single change introduced by commits, including:
- Commit Details: Includes commit hashes, messages, authors, dates, and timestamps.
- Changes to Files: Tracks what changes were made to specific files over time.
- Branch Contributions: Identifies changes introduce... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.1.4 Git GUI tools
| Git itself is a CLI (Command Line Interface) based tool, but it is also integrated in many existing GUI (Graphical User Interface) tools. Because Git repositories are decentralized, it can be completely up to user preference which tools to use. Some examples of Git tools include:
- Built-in GUIs:
- git-gui — Simple o... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.2 Description of repository structure and branching
| This section describes the physical structure of the repository and the branches required to track releases, the effect of Git operations on the repository structure, and how CRs become part of the specification.
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.2.1 Structure
| A repository would be created for each specification, e.g., TS 38.300 and TS 38.331 would be kept in distinct repositories. The reason for maintaining separate repositories is to cleanly associate CRs with a specification as is done today and to enable the individual tracking of versions of releases. When exploring a s... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.2.2 Branching
| As discussed in the previous section, each release would have its own branch, which when checked out would point to the latest version of that release. Creating a branch is the first step to making a modification to the specification. When creating a CR, the latest version of the affected release must first be checked ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.2.3 Merging
| After the final revisions of CR1 and CR3 were ready they were marked as agreed, awaiting merging in plenary. During plenary, CR1 and CR3 were approved and merged into the Release 21 branch. Once all merging was complete, the latest commit (the last merge) was tagged with the next version, v21.1.0, for easy retrieval. S... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.2.4 Merging Running CRs, Baseline CRs
| During the creation of a new release, the latest version of the active release is used as a baseline for a running CR (or baseline CR) to begin implementing the agreements made during the work item. The current procedure for baseline CR handling is described in Annex C.
The first running CR for 38.331 toward Release 1... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.2.5 Example of branching and merging during a release cycle
| Figure 6.2.1.2.5-1 is an example of how the mechanisms described in previous sections (branching, merging) can be applied during a release cycle. We take the example of Rel-22 work item phase and assume Rel-21 specifications are available in the Git repository. In this phase, Rel-21 specification maintenance will happe... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.2.6 Directory Contents
| The use of Git is agnostic to the format or formats of the files within, and can store any type of file, with the caveat that binary files are not well supported due to the difficulty in generating a difference between two versions of a binary file wherein a single change could affect multiple parts of the file. A sing... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.3 Description of procedures
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.3.1 Mapping Git procedures to Change Request processes
| We can compare the typical current CR procedure (Figure 6.2.1.3.1-1) to a potential future CR procedure with Git (Figure 6.2.1.3.1-2), relating each current step to the Git equivalent in the new procedure. The mapping provided is not meant to imply a solution, but rather to relate the Git flow to our current 3GPP flow.... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.3.2 Creating a CR - workflow description
| This section describes the workflow for creating a CR. The table, Table 6.2.1.3.2-1, describes the steps required to create and upload a CR to the Git repository. Note that details related to TDoc reservation, and downloading an automatically generated TDoc will not be discussed in this section.
Table 6.2.1.3.2-1: Cre... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.3.3 Updating a CR – workflow description
| After the first version of a CR has been pushed to the remote repository, it can be further modified by the original author or by other contributors. The CR branch can be worked on directly or one or more branches can be created to make changes. In this example, the focus will be on an author applying further changes t... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.4 Intermediate form CR
| The time constraints and the large number of contributors to the revision of a CR could necessitate the use of an intermediate document format for use in collaboration. Today it is common for working groups to collaborate as follows.
1. Rapporteur uploads the initial version of a document, e.g., a CR.
2. A delegate d... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.2 Evaluation against requirements of section 4.3
| Editor's Note: Evaluation is FFS.
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.3 Proposal #3: Ways of Working on CRs during meetings when using Gitlab for preparation of CRs
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.3.1 Description
| Gitlab on 3GPP Forge is used as a repository of identical copies of certain (parts of the) specifications that are written in text-based formats separately from the rest of the specifications written in Word. The primary normative reference of specifications remains stored on FTP.
Gitlab on 3GPP Forge is used for prep... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.3.1.1 Description of tools
| The tools used in these Ways of Working are the following:
- 3GU for CR submission
- Word for CR cover sheet.
- Gitlab on 3GPP Forge for storage of text-based parts of specifications that are not written in Word, and at least for preparation of CRs or draft CRs
- Schema files for ensuring consistent use of styles ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.3.1.2 Description of procedures
| The following Ways of Working (WoW) are studied for collaborative work on drafting CRs.
In this clause, changes to the CR cover sheet data fields must be controlled through access to Gitlab, in order to maintain a one-to-one correspondence between commits and a CR referencing these commits.
It is also assumed that ei... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.3.2 Evaluation against requirements of section 4.3
| Editor's note: The evaluation is FFS
6.4 Proposal #4 OneM2M workflow
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1 Description
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.1 Description of tools
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2 Description of procedures
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2.1 Introduction
| Below is described a candidate workflow for using the 3GPP's GitLab environment (i.e. the 3GPP Forge) for handling CRs, TSs and TRs. This workflow is similar to the workflow used by the OneM2M (https://www.onem2m.org/) for handling of CRs, TSs and TRs with adaptations to the current 3GPP ways of working.
It should be ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2.2 Overview
| Below is a diagram showing the workflow used for CRs in OneM2M. You might need to zoom in to see the details, but the diagram is also available in a higher resolution version here: https://forge.etsi.org/rep/cti/md-specs-dev/contribution-procedure/-/blob/master/simplified-process.md.
More details are also found here: ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2.3 Git repository settings
| In this model each TS or TR has its own associated repository in the 3GPP Forge with a protected "main" branch (containing the latest version of the specification) with the following characteristics:
- The main branch is protected:
- Only MCC can merge into main branch
- Only TSG and WG officials can approve Merge R... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2.4 Workflow for a WG meeting
| The following would happen for a WG meeting:
- Following the WG's pre-meeting schedule, delegates request for Tdoc numbers.
- With the Tdoc numbers allocated for the CRs, delegates should create "CR" branches which have in the name of the branch a reference to the tdoc number, e.g., CR/WG-YYMCXI_CR_Name. The CR branc... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2.5 Workflow for a TSG meeting
| During the TSG meeting, the CRs agreed in the preceding WG meetings have to be approved by the TSG. In GitLabs terms this means that the Merge Requests tagged as agreed during the WG meetings have to be now approved and merged in the main branch. This could be done following the steps below:
- In the TSG meeting, the ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2.6 Maintenance for frozen specification releases
| To handle corrections CRs for frozen releases the current model proposes the following workflow:
- At the freeze of each release MCC creates a protected branch for the release to be frozen:
- release-xx-main branch created from the main branch
For the correction CRs to a frozen release, the protected branch will act... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2.7 Publishing the specifications
| Currently OneM2Ms approach is that they have an automated portal where all their specifications are found: https://specifications.onem2m.org/
Whenever a new version of their specification is ready, i.e. after CR implementation has completed, the latest specification is published and can be accessed on the portal. The ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2.8 Potential variant of the OneM2M workflow: GitFlow-like workflow
| One variant of the OneM2M workflow described above is the GitFlow work flow. In the GitFlow workflow a develop branch is used as an intermediate step when implementing Merge Requests onto the main branch based on these principles as follows:
- Protected main branch:
- Only MCC can merge into main branch
- Only TSG o... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.4.1.2.9 Handling CR cover page information
| In this model, the CR cover page information is converted from tabular format to JSON format as presented in the example below. Note that approach could be in both the OneM2M workflow or the alternative (GitFlow-like workflow described in clause 6.4.1.2.8).
CR-Form-v12.3
CHANGE REQUEST
<Spec#>
CR
<CR#>
rev
<... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 7 Overall evaluation
| Editor's note: Overall evaluation of combined proposals from sections 5 and 6, including trials.
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 8 Recommendations
| Editor's note: Final recommendations
Annex A:
3GPP Stakeholder Survey on CR Tools
As part of the effort to develop tools ''New Working Methods'' during the years 2015-2022, a 3GPP stakeholder survey was performed in 2022 [3]. The goal of this survey was to provide clear input on requirements and expectations wit... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 25.4 I need to identify all abbreviations in a CR that are neither defined in the specification, nor in 21.905, nor in the cited 3GPP specifications in the reference section.
| Some secretaries found this useful, but most found the feature unimportant:
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 25.5 I need to search change marked documents for all changes after a given date, e.g. after CEST yesterday.
| While most rapporteurs agreed this was important, there was disagreement with secretaries. One even commented: "don't do this!"
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 27.6 I need to create an interim version of the target specification that reflects the specification status after the first of more than one working group meeting in a single quarter.
| NOTE 1: Though interim versions of specifications have no official status since CRs are only sent to TSG for approval at the end of a quarter, some delegates may benefit from the ability to view the cumulative result of all agreed CRs (and even postponed CRs) to a given specification
While some rapporteurs found this... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 27.4 I need to be able to use the CR and specification tool to apply pseudo-CRs as changes to a source specification.
| NOTE 2: Pseudo-CRs (pCRs) are currently informally structured documents. Please take into account in answering this question that in order support implementation of pseudo-CRs in a tool, it may be necessary that pseudo-CRs documents become more formal in their structure. For example, it may be necessary to define and f... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.2.4 Rebasing Merging Running CRs, Baseline CRs
| Editor’s note: This section will be reconsidered and is left here for the purpose of describing the concept of porting changes from the current release into running CRs as to keep the CRs up to date. A different approach will be studied whereby changes from the current release would be merged into the running CRs inste... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.2.1.2.5 Example of branching, and merging and rebasing during a release cycle
| Figure 6.2.1.2.5-1 is an example of how the mechanisms described in previous sections (branching, merging, rebasing) can be applied during a release cycle. We take the example of Rel-22 work item phase and assume Rel-21 specifications are available in the Git repository. In this phase, Rel-21 specification maintenance ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 6.3 Proposal #3: Ways of Working on CRs during meetings when using Gitlab for collaborative draftingpreparation of CRs
| |
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 1 Scope
| The present document studies and assesses enhancements to the management aspects of management data, focusing on data discovery, data collection, data storage, data access etc., for 5G-Advanced. The study aims to identify the new functionalities, or enhancement to the data management capabilities and propose potential ... |
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 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.
-... |
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 3 Definitions of terms, symbols and abbreviations
| |
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 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.
|
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 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].
<ABBREVIATION> <Expansion>
|
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 4 Use Cases
| 4.1 Request and Report of External Management Data
|
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 4.1.1 Use Case#1-1: Time Issue of External Management Data
| 4.1.1.1 Description
External management data are modelled in TS 28.622[X] by ExternalDataType IOC (clause 4.3.73). This IOC defines attributes to indicate the type of external management data and related meta data.
Specified meta data are
- mediaLocation: “address from which the described external management d... |
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 4.3.1 Use Case#3-1: Access control for performance metrics
| 4.3.1.1 Description
When an MnS consumer requests the collection of performance metrics using the PerfMetricJob IOC (see clause 4.3.31 of TS 28.622 [2]), the MnS producer needs to be able to determine whether the MnS consumer is authorized to collect such data or not.
4.3.1.2 Problem Statement
Clause 7.3 o... |
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 4.4.1 Use Case#4-1: Enhancement of Management data collection
| 4.4.1.1 Description
The ManagementDataCollection IOC defined in TS 28.622 [2] represents a management data collection request job for trace metrics and performance metrics. The ManagementDataCollection IOC includes attributes “managementData”, “targetNodeFilter”, “collectionTimeWindow”, “reportingCtrl”, “dataScop... |
be084ca539ec241ad52e3fcedfa78679 | 28.887 | 5 Conclusion and Recommendations
| Editor’s Note: This clause is to summarize the identified key items and to discuss recommendations for a potential Work Item.
5.1 Request and Report of External Management Data
5.2 UE Data Collection
5.3 Enhancement of Management Services Access Control (MSAC)
5.4 Clarification of Mechanisms to Discover, Reques... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 1 Scope
| The present document …
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 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.
-... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 3 Definitions of terms, symbols and abbreviations
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 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.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 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].
OTT Over the top
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 4 Concepts and overview
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5 Management capabilities for AI/ML lifecycle
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1 ML model training
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1 Use cases
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.1 Management support to training for UE-side model
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.1.1 Management support to AI/ML-based beam management
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.1.1.1 Description
| To support AI/ML-based beam management defined in TS 38.300 [2], for beam prediction management, UE can send the data of beam prediction management to UE-side training entity (e.g. a server inside MNO or an OTT server) via gNB and 3GPP management system for UE-side model training (see NOTE 1). 3GPP management system ne... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.1.1.2 Potential requirements
| REQ-ML_UESIDE-01: The 3GPP management system should have a capability allowing the authorized UE-side training entity to request the UE-side training data for the UE-side model training.
REQ-ML_UESIDE-02: The 3GPP management system should have a capability to request and get the UE-side training data from gNB(s) for t... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.1.1.3 Possible solutions
| TBD
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.1.1.4 Possible solutions evaluation
| TBD
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.2 Management support to OAM-centric training for NG-RAN NW-side model
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.2.1 Management support to AI/ML-based beam management
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.2.1.1 Description
| To support AI/ML-based beam management defined in TS 38.300 [2], UE can provide data of beam management to 3GPP management system via gNB (see NOTE 1). 3GPP management system needs to collect data from gNB for OAM-centric training for NG-RAN NW-side model.
Figure 5.1.1.2.1.1-1: Management of NW-side data collection ... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.2.1.2 Potential requirements
| REQ-ML_NWSIDE-01: The 3GPP management system should have a capability to configure the NW-side training data collection for OAM-centric NW-side model training.
REQ-ML_NWSIDE-02: The 3GPP management system should have a capability to obtain the NW-side training data for OAM-centric NW-side model training.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.2.1.3 Possible solutions
| TBD
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.2.1.4 Possible solutions evaluation
| TBD
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.3 Management of Vertical Federated Learning
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.3.1 Description
| In Rel-19, Vertical Federated Learning (VFL) is introduced in core network for NWDAF(s) and AF(s).There may be one NWDAF or one AF acting as a VFL server and one or multiple NWDAF(s) and/or one or multiple AF(s) acting as VFL Client(s). Vertical Federated Learning is available among NWDAFs or between NWDAF(s) and AF(s)... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.3.2 Potential requirements
| REQ-VFL_MGMT-01: The ML training MnS producer should have a capability allowing an authorized consumer to get the VFL role (VFL server or VFL client) of an ML Training Function in VFL process.
REQ-VFL_MGMT-02: The ML training MnS producer should have a capability allowing an authorized consumer to specify requirements... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.3.3 Possible solutions
| To support VFL in 3GPP management system, the following enhancements are proposed:
- Enhancements Aspects #1, extending the MLTrainingFunction IOC with the following aspects:
1) Extend learningTechnologyName by changing the allowed value “FL” to “VFL” and “HFL” to differentiate different FL training types supported b... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.3.4 Possible solutions evaluation
| 5.1.1.4 Management support to data collection for two-sided model training
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.4.1 Management support to CSI compression
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.4.1.1 Description
| To support CSI compression defined in TR 38.843 [3], the operator can deliver relevant data for two-sided model training (see NOTE 1) to a UE-side model training entity (e.g. a server deployed by an MNO or by an OTT service provider). The UE-side model training entity uses the received data to perform UE-part model tra... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.4.1.2 Potential requirements
| REQ-ML_TWOSIDE-01: The 3GPP management system should have a capability allowing a UE-side training entity to subscribe for receiving relevant data for CSI compression.
REQ-ML_TWOSIDE-02: The 3GPP management system should have a capability to configure one or more gNBs to produce and report relevant data for CSI compre... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.5 Enhancement on LCM of Federated Learning
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.5.1 Description
| Federated learning (FL) is a distributed machine learning approach that allows multiple FL clients to collaboratively train an ML model on local datasets contained in each FL Client without explicitly exchanging data samples.
When receiving an FL training request, the ML training MnS Producer acting as FL server needs... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.