MFA TR MF.100 V1.0.

1 (2017-04)
Technical Specification

MulteFire Alliance

Guidelines for MulteFire Specifications

(Release 1)

The present document has been developed within MulteFire Alliance and may be further elaborated for the purposes of the MulteFire Alliance.
The MulteFire Alliance accepts no liability for any use of this Specification.

1
 Keywords
multefire, neutral host network, stage 2, NHN

MulteFire Alliance

Postal address

5177 Brandin Court

Fremont, CA 94538 USA

Internet
http://www.multefire.org

Copyright Notification

No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.

© 2017, MulteFire Alliance

All rights reserved.

UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association

2
1 Scope
This document provides general guidelines on the use of MulteFire Alliance (MFA) specifications and the interpretation
of references in the context of MulteFire.

2 References
[1] Third Generation Partnership Project (3GPP). Vocabulary for 3GPP Specifications. 3GPP TR 21.905.

3 Definitions, symbols and abbreviations

3.1 Definitions
For the purposes of the present document, the terms and definitions described in 3GPP TR 21.905 [1] apply. A term
defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].

3.2 Symbols

3.3 Abbreviations
Abbreviation Definition
3GPP Third Generation Partnership Project
MF MulteFire
MFA MulteFire Alliance
TS Technical Specification
TR Technical Report

4 Guidelines for MulteFire Specifications

4.1 Specification Numbering
There are two types of MulteFire Alliance specifications:

1. Specifications fully created by MulteFire Alliance.

2. Specifications based on specifications originally published by 3GPP, but contain changes provided by MFA
that are MulteFire specific. The cover page of these specifications is identical to the title page of the 3GPP
specification (i.e., the baseline). Any changes or modifications that MFA provides over the 3GPP baseline are
indicated with track changes. The modifications indicated with track changes in the MFA specifications also
include the modifications due to approved 3GPP CRs that are not part of the baseline 3GPP specification (E.g.
if the baseline 3GPP version is 13.5 and there is a 3GPP CR implemented only in version 13.6 and MFA
would like to apply that CR for MF then it should be indicated with track changes as it is change over the
baseline 3GPP version.). Note that these 3GPP CRs shall also go via the normal MFA change approval process
(see Annex A), they are not introduced automatically. In order to distinguish the modifications coming from
3GPP CRs form other modifications, different author is used for this type of modifications when the
specification with track changes is created. Therefore, a MFA specification may contain modifications from
two authors: one author for modifications introduced due to approved 3GPP CRs and one author for other
MFA modifications.

MFA documentation uses a standard documentation ID system. Each document ID begins with the three-letter
designation MFA. This is followed by a two-letter abbreviation to indicate whether the document is a technical
specification (TS) or technical report (TR).

3
The final segment of the ID contains a two-character abbreviation followed by a three-digit number to indicate the type
of specification/report.

The first digit of the three-digit specification number of the MulteFire specification refers to the type of the
specification.

• 1XY: General MulteFire documents and documentation of requirements.

• 2XY: Architecture (Stage 2) level specifications.
• 3XY: Protocol (Stage 3) level specifications.

The standalone MulteFire Alliance specifications (specifications fully created by MulteFire Alliance) include a two-
letter “MF” prefix, that precedes the 3-digit number at the end of the document ID (e.g., this specification uses the
following number: “MF.100”, and is referred in other specifications as “MFA TR MF.100”).

MulteFire Alliance specifications based on a 3GPP specification retain the numbers used in the baseline 3GPP
specification (e.g., MFA TS 12.345).

Figure 4.1-1 illustrates the document IDs for MFA specifications.

Indicates whether the document was

Indicates whether the document is
designed entirely by MulteFire (MF), or
a technical specification (TS) or a
is based on content initially edited by
technical report (TR)
3GPP (NN)

Indicates that the specification is Indicates the type of specification:

edited and published by MulteFire general requirements, architecture, or
Alliance (MFA) protocol

MFA TS XX.NNN
Example of a document ID for content
created entirely by MFA, per §4.1. MFA TR MF.100

Example of a document ID for content

modified by MFA, based on a 3GPP MFA TS 36.300
source specification, per §4.1.

Figure 4.1-1: Document Identification system for MulteFire Alliance

4.2 Specification Versioning

MulteFire Alliance specifications use an “A.B.C” numbering where

• A.B refers to the MulteFire Alliance Release of the specification, and

• the last digit (“C”) is the version of the specification within that release.

E.g., specifications for MulteFire Release 1 are identified with a version number starting with “1.0”.

When the first version of a MFA specification for a release is issued the last digit is “0” independently of the last digit
used in the previous release for the same specification. When an MFA specification is updated within the same release,
the last digit is increased by 1. An update of a specification is never issued without changing the version of the
specification.

4.2a Specifications in ARO system

Official MFA specifications can be found under the ARO Specifications menu. In that menu, there is a separate folder
of each MF Release. Within the Release folder specifications are uploaded with their document identifier (see section
4.1). The different versions of a specification can be found under their document identifier. As specifications are
updated independently it may happen that the latest versions of the specifications have different version numbers. The
structure is illustrated in Figure 4.2a-1.

4
 MulteFire Alliance Release 1.0 Specifications MFA-TR-MF.100 MFA-TR-MF.100-v1.0.1.docx
MFA-TR-MF.100-v1.0.0.docx

MFA-TS-36.300 MFA-TS-36.300-v1.0.2.docx
MFA-TS-36.300-v1.0.1.docx
MFA-TS-36.300-v1.0.0.docx

MulteFire Alliance Release 1.1 Specifications

Figure 4.2a-1: Specification menu structure in ARO

4.3 Specification Cross-Referencing

In general, cross-references in MFA specifications will contain the Document ID, and the corresponding reference
listing in Section 2 (where users may obtain the full document title and publication version if necessary).

When a MulteFire Alliance specification cross-references another MulteFire Alliance specification, then the cross-
reference describes the latest published version of that MFA specification from the same MulteFire release.

When a MulteFire Alliance specification cross-references a 3GPP specification and the version of the specification is
explicitly included in the cross-reference, then the referred version of the 3GPP specification shall be used.

When a MulteFire Alliance Rel-1 specification cross-references a 3GPP specification, and the version of the
specification is not explicitly included in the cross-reference, then the cross-reference describes the latest published
version of that 3GPP specification from 3GPP Release 13.

When a 3GPP specification is used in the context of MulteFire and the 3GPP specification contains a cross-reference to
another 3GPP specification that has MulteFire Alliance specific version, then the cross-reference shall be interpreted as
a cross-reference to the latest published version of the MulteFire Alliance-specific version of the 3GPP specification
(e.g., when a 3GPP specification is used in the context of MulteFire and it contains a reference to 3GPP TS 24.301 then
it shall be interpreted as a cross-reference to MFA TS 24.301).

5 List of MulteFire Specifications

5.1 MulteFire Alliance Release 1 specifications
Table 5.1-1 lists Release 1 specifications created and designed entirely by MulteFire Alliance. Table 5.1-2 lists
Release 1 specifications edited and modified by MulteFire Alliance, using a 3GPP specification as a baseline.

Table 5.1-1: MulteFire standalone specifications

Document ID Title Responsible Group

MFA TR MF.100 Guidelines for MulteFire Specifications TSG
(this document)
MFA TR MF.101 MulteFire Deployment Scenarios and Requirements E2E Architecture WG
MFA TS MF.201 Architecture for PLMN Access Mode Stage 2 (Release 1) E2E Architecture WG
MFA TS MF.202 Architecture for Neutral Host Network Access Mode Stage 2 E2E Architecture WG
(Release 1)
MFA TS MF.301 MulteFire Subscription Management Stage 3 (Release 1) E2E Architecture WG

5
Table 5.1-2: MulteFire-edited specifications using a 3GPP specification as a baseline

3GPP baseline Responsible Group

Document ID Title release
MFA TS 24.301 Non-Access Stratum (NAS) protocol for Evolved Release 13 E2E Architecture WG
Packet System (EPS) Stage 3 (Release 1)
MFA TS 26.213 Evolved Universal Terrestrial Radio Access (E- Release 14 Radio WG
UTRA) Physical Layer Procedures (Release 1)
MFA TS 33.401 Security Architecture (Release 1) Release 13 E2E Architecture WG
MFA TS 36.201 Evolved Universal Terrestrial Radio Access (E- Release 14 Radio WG
UTRA) MF physical layer; General description
(Release 1)
MFA TS 36.211 Evolved Universal Terrestrial Radio Access (E- Release 14 Radio WG
UTRA) Physical Channels and Modulation (Release
1)
MFA TS 36.212 Evolved Universal Terrestrial Radio Access (E- Release 14 Radio WG
UTRA) MF physical layer; Multiplexing and Channel
Coding (Release 1)
MFA TS 36.300 Evolved Universal Terrestrial Radio Access (E- Release 14 Radio WG
UTRA) and Evolved Universal Terrestrial Radio
Access Network (E-UTRAN) and MulteFire (MF)
Overall description Stage 2 (Release 1)
MFA TS 36.302 Evolved Universal Terrestrial Radio Access (E- Release 14 Radio WG
UTRA) Services provided by the physical layer
(Release 1)
MFA TS 36.304 Technical Specification Group Radio Access Release 14 Radio WG
Network Evolved Universal Terrestrial Radio Access
(E-UTRA); User Equipment (UE) procedures in idle
mode
MFA TS 36.306 MulteFire Alliance Evolved Universal Terrestrial Release 14 Radio WG
Radio Access (E-UTRA) User Equipment (UE) radio
access capabilities (Release 1)
MFA TS 36.321 Evolved Universal Terrestrial Radio Access (E- Release 14 Radio WG
UTRA) Medium Access Control (MAC) protocol
specification (Release 1)
MFA TS 36.331 Technical Specification Group Radio Access Release 13 Radio WG
Network Evolved Universal Terrestrial Radio Access
(E-UTRA); Radio Resource Control (RRC); Protocol
Specification (Release 1)
MFA TS 36.413 S1 Application Protocol (S1AP) (Release 1) Release 13 E2E Architecture WG

6
Annex A: Updating MulteFire Specifications
Member companies can submit proposals (change requests) to modify specifications in the group that is responsible for
the given specification. All modification proposals shall be uploaded as working documents using ARO Document
menu.

The submitted proposals are reviewed by the responsible group. The chair of the group selects how the group reviews
the proposed changes. The review can happen during TSG meetings, during teleconferences or via emails. During the
review process the document may be revised and new version(s) of the document may be uploaded. At the end of the
review the chair of the group announces whether the proposal was approved by the group and indicates the approved
version of the document.

A group may decide at any time to create a draft version of a specification to facilitate the work of the group (e.g. to
enable cross-checking of different changes or specifications). These draft versions may indicate the changes over the
previous version of the specification with track changes from different authors. Such a draft may be uploaded as an
ARO Document, but shall never be considered as an official version of the specification.

The specifications are updated according to the approved changes after TSG meetings. A new version of a specification
is issued after all approved change requests are implemented in the specification.