hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4131cd5fefdadf4075e3ec0993ed8fe4 | 34.901 | 10.4.3 Composite criteria | The results of the simulation stated above show that almost all the devices are picked out at relatively early stages, and only few reach later stages. This observation would lead to the idea that the test time could be reduced if stricter criteria at the later stages. Suppose that each threshold in a criterion, Rth-fi... |
4131cd5fefdadf4075e3ec0993ed8fe4 | 34.901 | 11 Accuracy of Continuous Distributions | As stated in clause 9.2, the negative binomial distributions can be approximated by m-Erlang distribution. In this Appendix, we will discuss about how good this approximation is.
For continuous distributions, Equation (1’) and (2’) determine early Pass/Fail thresholds, and these can be transformed to more specific form... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 1 Scope | The present document provides an overview and overall description of the LTE-based 5G terrestrial broadcast comprising:
- a service delivering Free To Air content [2];
- a radio network comprising only MBMS-dedicated cells or FeMBMS/Unicast-mixed cells [3] as transmitters; and
- Receive Only Mode (ROM) devices and UEs ... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 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.
- Fo... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 3 Definitions, symbols and abbreviations | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1]. |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
DRX Discontinuous reception
eMBMS Evolved MBMS
FeMBMS Further enh... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 4 Introduction | <Definition of LTE-based 5G broadcast: Dedicated network, ROM devices>
<Motivation>
<Use cases>
<Quick overview of the Rel.14 and Rel.16 work>
<Network scenarios: LPLT, MPMT, HPHT>
<Receiver types: rooftop, car-mounted,…> |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 4.1 General | The main aspects of the LTE-based 5G terrestrial broadcast described in this specification are:
- radio network comprising only MBMS-dedicated cells or FeMBMS/Unicast-mixed cells [3] as transmitters; and
- ROM devices and UEs supporting FeMBMS [4] as receivers.
NOTE: ROM devices support only ROM service [5]. ROM servic... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 4.2 Use cases and requirements | In Release 14, the use cases and scenarios for eMBMS services based on LTE have been expanded to include terrestrial broadcasting (the feature also referred to as "EnTV"). This included new requirements:
- network dedicated to TV broadcast via eMBMS;
- SFN deployments with ISD significantly larger than a typical ISD as... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 4.3 Enhancements targeting LTE terrestrial broadcast | In Release 14, the following key RAN enhancements were made to the specifications to enable LTE terrestrial broadcast:
- MBMS-dedicated cell [3];
- MBSFN subframes using f = 1.25 kHz [8];
- New information blocks on PBCH and PDSCH of CAS [3], [6]:
- MIB-MBMS is transmitted with a 40ms periodicity and updated every 160... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 5 Architecture | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 5.1 General | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 5.2 Network elements | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 5.3 Interfaces | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 5.4 Protocol stack | The network architecture for LTE-based 5G terrestrial broadcast is described in 3GPP TS 36.300 [3] subclause 15.1.1, with the exception that only:
- ROM reception via MBMS-dedicated cell; or
- MBMS reception via FeMBMS/Unicast-mixed cell
is supported.
RAN interfaces for LTE-based 5G terrestrial broadcast are described... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 6 Protocol aspects | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 6.1 Physical layerFrame structure and numerologies | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 6.1.1 Frame structure and numerologies | 6.1.2 Channels and signalsOnly frame structure type 1 is supported. All numerologies specified in 3GPP TS 36.211 [8] are supported. For subframes using f other than 0.370 kHz, the frame structure is according to Figure 6.1-1. For transmissions using f = 0.370 kHz, the frame structure is shown in Figure 6.1-2.
Figure ... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 6.2 MBMS Transmission | MBMS transmission is performed according to 3GPP TS 36.300 [3] subclause 15.3.3.
MCCH configuration and scheduling is performed according to 3GPP TS 36.300 [3] subclause 15.3.5 and 3GPP TS 36.331 [6] subclause 5.8.1. In case of a MBMS-dedicated cell, the MBMS counting configuration is not supported.
MCCH information ac... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 6.1.3 Physical layer procedures | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 6.32 MAC Layer | <BCH and MCH aspects only>MAC layer supports only:
- BCH reception for BCCH;
- DL-SCH reception for BCCH; and
- MCH reception for MCCH/MTCH.
BCH reception and DL-SCH reception in the MAC layer use transparent MAC [16], i.e. single MAC PDU per TTI with no headers. HARQ entity uses the dedicated broadcast HARQ process, d... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 6.43 RLC layer | BCCH uses the RLC-TM mode.
MTCH and MCCH use the RLC-UM mode. RLC operation for MTCH and MCCH is described in 3GPP TS 36.300 [3] subclause 15.3.3. |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 6.54 RRC layer | RRC layer supports only:
- System information reception (see 3GPP TS 36.331 [6] subclause 5.2) in MBMS-dedicated cell; and
- MBMS reception (see 3GPP TS 36.331 [6] subclause 5.8) in MBMS-dedicated cell and in FeMBMS/Unicast-mixed cell.
For system information reception, the following applies:
- only BCCH-BCH-Message-MBM... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 6.5 Idle mode | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 7 ROM aspects | |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 7.1 General | Since a ROM device does not support uplink transmission or two-way signalling procedures, and does not comprise USIM, it cannot support all the physical layer procedures of the conventional UE. By the same token, only a subset of idle mode procedures and RRM requirements applicable to a conventional UE will be supporte... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 7.2 Physical layer procedures | ROM device only supports the following physical layer procedures specified in 3GPP TS 36.213 [13]:
- Cell search;
- Timing synchronization;
- PDSCH procedures;
- PDCCH assignment procedure;
- PMCH procedures; and
- Assumptions independent on physical channels (clause 12) related to MBMS-dedicated cell. |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 7.3 Idle mode procedures | ROM device only supports the following idle mode procedures specified in 3GPP TS 36.304 [14]:
- Cell selection; and
- Cell reselection.
PLMN prioritization for cell reselection is specified in 3GPP TS 36.304 [14] subclause 5.2.4.1.
NOTE: NAS layer PLMN selection does not apply to ROM device. PLMN selection for ROM dev... |
d832899f12f9cb7303ee0f37d0629dd2 | 36.276 | 7.4 RRM requirements | ROM device only supports the following requirements specified in 3GPP TS 36.133 [15]:
- Cell selection; and
- Cell reselection, except for:
- IRAT reselection;
- paging-related requirements; and
- CSG cell-related requirements.
Appendix Upper layer aspects
Pointers only
<Transparent mode>
<Service and session configura... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 1 Scope | The present document describes new use cases and potential requirements applicable to Public Warning Services for
- UEs with diverse form-factors whose user interface is different from the conventional mobile phones; and
- UEs that are defined by applying 3GPP system to non-ICT industry businesses (e.g. vehicles or mac... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 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.
- Fo... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 3 Definitions, symbols and abbreviations | Delete from the above heading those words which are not applicable.
Clause numbering depends on applicability and should be renumbered accordingly. |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
Definition format (Normal)
<defined term>: <definition>.
example: text use... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation> |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
Abbreviation format (EW)
<ACRONYM> <Explanation> |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 4 Overview | This clause provides a high-level overview of the feature that includes:
- description of feature
- benefit(s) the feature provide to the operator, end user, etc
- any other (background) information that helps the reader understand the feature |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5 Use cases for UEs with different or no user interface or with different UE roles | |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.1 Use case: UEs with no user interface over direct network connection | |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.1.1 Description | This use case describes a scenario where UEs with no user interface that are not intended for human type communication are connected to a 3GPP network and receive a PWS message when a disaster occurs. Those UEs with no user interface take pre-defined actions (e.g. shutting down air condition when an earthquake occurs t... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.1.2 Pre-conditions | UEs with no user interface are subscribed to operator’s 3GPP network.
UEs with no user interface are connected to the 3GPP network.
UEs with no user interface monitor the 3GPP network for public warning alarms.
Pre-defined actions or procedures are stored on the UEs with no user interface and can be executed based upon... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.1.3 Service Flows | UEs with no user interface are deployed to manage home appliances such as powering them on and off .
An earthquake suddenly occurs in the area where UEs with no user interface are located and because of the earthquake, a PWS message is broadcast to UEs with no user interface.
UEs with no user interface take pre-defined... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.1.4 Post-conditions | UEs with no user interface take pre-defined actions (e.g. power off) in time that made home appliances less damaged from the earthquake. |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.1.5 Potential Impacts or Interactions with Existing Services/Features | None identified |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.1.6 Potential Requirements | The 3GPP system shall enable the content of a PWS message to include information that can be mapped to an event or a disaster and is identifiable by the UEs with no user interface per event or disaster.
NOTE: The information included in the content of a PWS message may be an identifier of an event or a disaster.
UEs wi... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.2 Use case: Remote UEs with no user interface over indirect network connection | |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.2.1 Description | This use case describes a scenario where remote UEs with no user interface that are not intended for human type communication are connected to 3GPP network via relay UE in coverage of 3GPP network and receive a PWS message via relay UE when a disaster occurs. Those remote UEs with no user interface take pre-defined act... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.2.2 Pre-conditions | A relay UE is connected to the 3GPP network and remote UEs with no user interface are in indirect network connection.
Pre-defined actions or procedures are stored on the remote UEs with no user interface and can be executed based upon the information in the content of the PWS message which is transmitted by the relay U... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.2.3 Service Flows | Remote UEs with no user interface are deployed to control machines in a factory and are connected to 3GPP network via a relay UE.
An earthquake suddenly occurs close to the factory and the relay UE receives a PWS message.
The relay UE receives a PWS message, and unconditionally forwards the PWS message to the remote UE... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.2.4 Post-conditions | Remote UEs with no user interface take pre-defined actions (e.g. shut off the power) in time that made machines in the factory less damaged from the earthquake. |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.2.5 Potential Impacts or Interactions with Existing Services/Features | None identified |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.2.6 Potential Requirements | The remoteUE with no user interface shall be able to support the reception of the information that is related to an event or a disaster notified by PWS message and is transmitted from the relay UE.
NOTE: Subject to regional regulatory requirements and the intended function of the UE (e.g. IoT) which does not have a use... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.3 Use case: relay UE for indirect network connection of remote UEs | |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.3.1 Description | This use case describes a scenario where a relay UE that provides an indirect network connection to remote UEs transmits a PWS message to the remote UEs as they are located in an area where the PWS message is broadcast from the 3GPP network. |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.3.2 Pre-conditions | Bob and Mary go out to the sea by taking their yacht where there is a relay UE on the deck of the yacht to provide indirect network connection to remote UEs inside the steel cabin of the yacht. |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.3.3 Service Flows | The PWS message is broadcast and the relay UE receives the PWS message notifying that a storm is coming to the area where the yacht is located while Bob and Mary sleep in the steel cabin of the yacht.
The UEs that Bob and Mary have with them could not receive the PWS message directly because the UEs are located inside ... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.3.4 Post-conditions | Bob and Mary woke up due to the warning alarm from the UEs that they have with them inside the cabin and come back to the port before the storm arrives at the area where they are. |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.3.5 Potential Impacts or Interactions with Existing Services/Features | None identified |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.3.6 Potential Requirements | The relay UE shall have the capability of forwarding an incoming PWS message to remote UEs.
A remote UE shall be able to support monitoring PWS messages which are received both directly from the 3GPP network and indirectly via the relay UE.
When a remote UE receives a PWS message transmitted via a relay UE, the remote ... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.4 Use case: UE with different user interface | |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.4.1 Description | This use case describes a scenario where the user interface of the mobile device is different from the conventional user interface of the mobile phone, e.g. augmented reality based user interface or hologram based user interface.
Because the network functionalities to broadcast a PWS message need to be kept as unchange... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.4.2 Pre-conditions | The UE with different user interface (e.g. augmented reality based or hologram based user interface) are connected to 3GPP system.
A warning event or disaster is identifiable from information that can be extracted from the PWS message.
Pre-defined content or procedure is mapped in the UE with different user interface t... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.4.3 Service Flows | Sally is on holidays in Seoul and her device, a UE with user interface that is different from the conventional user interface of a mobile device (e.g. augmented based or hologram based user interface), helps her find a good restaurant at Gangnam area.
Suddenly an earthquake occurs near Seoul so a PWS message is broadca... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.4.4 Post-conditions | Sally recognized in time about the earthquake occurred thanks to the notification of the device and not by the text-based public warning message itself. |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.4.5 Potential Impacts or Interactions with Existing Services/Features | None identified |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 5.4.6 Potential Requirements | The UE with a different user interface (i.e. a user interface that is not capable of displaying a text-based content) shall be able to support the reception of a PWS message broadcast from the 3GPP network.
The UE with a different user interface shall be able to support the extraction of the information on the type of ... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 6 Considerations | |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 6.1 Considerations on the improvement of the understandability of the PWS message | |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 6.1.1 Constraints inherent in the language-based and text-based PWS message | 3GPP specified the requirements for Public Warning System in 3GPP TS 22.268 from 3GPP Release 8 onwards in order to let mobile users receive text-based PWS messages. Language-related requirements described in 3GPP TS 22.268 are as follows.
NOTE 1: Requirements described in the section 5 (Earthquake and Tsunami Warning... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 6.1.2 Potential requirements proposed for the improvement of the understandability of the PWS message | For mobile users with disabilities, the user interface of UEs that are used by them is extended by UE accessibility functions. The most effective presentation of the warning indication may be different from what is normally defined for mobile users without disabilities. Considering such difference, following potential ... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 6.2 Considerations on existing PWS requirements for UEs with different or no user interface or with different UE roles | |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 6.2.1 Applicability review of existing PWS requirements | UEs with different or no user interface or with different UE roles didn’t exist when existing PWS requirements were specified in 3GPP TS 22.268 [2] so some of existing PWS requirements might not be applicable and need to be revised or to add some additional requirements for UEs with different or no user interface or wi... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 6.2.2 Proposals on existing PWS requirements | Proposed texts are given in Table 4 in order to make existing PWS requirements with proposed texts applicable for UEs with different or no user interface or with different role as well as for legacy UEs with the conventional user interface that 3GPP assumed when these existing PWS requirements were specified in 3GPP TS... |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 7 Potential Requirements | Text to be provided. |
2e4def7229d8545d814f4132a20a55ee | 22.969 | 8 Conclusion and Recommendations | Text to be provided.
Annex <A>:
<Annex title>
Annexes are only to be used where appropriate:
Annexes are labelled A, B, C, etc. and are "informative"(3GPP TRs are informative documents by nature).
Annex <X>:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2016-11
SA1#76
S1-163232
... |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 1 Scope | The present document specifies the Information Model definitions and Solution Set definitions for 5G Core Network (5GC) network resource model, to fulfil the requirements identified in 3GPP TS 28.542 [2].
The Information Model definitions define the semantics and behaviour of information object class attributes and rel... |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 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.
- Fo... |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 3 Definitions and abbreviations | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. For terms and definitions not found here, please refer to 3GPP TS 28.542 [2]. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [... |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1] and 3GPP TS 28.542 [2].
JSON JavaScript Object Notation
4 Informa... |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.2.1 Class diagram of 5GC NFs | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.2.1.1 Relationships | This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for NRM of 5GC NFs definitions. This clause provides the overview of the relationships of relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes.
The Figure 4.2.1.1-... |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.2.1.2 Inheritance | This clause depicts the inheritance relationships that exist between IOCs.
Figure 4.2.1.2-1 shows the inheritance hierarchy from IOC ManagedFunction related to the 5GC NF NRM.
Figure 4.2.1.2-1: Inheritance hierarchy from IOC ManagedFunction related to the 5GC NF NRM
Figure 4.2.1.2-2 shows the inheritance hierarchy from... |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.2.2 Class diagram of AMF Region/AMF Set | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.2.2.1 Relationships | This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for NRM of AMF Region/AMF Set definitions. This clause provides the overview of the relationships of relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes.
The Figu... |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.2.2.2 Inheritance | This clause depicts the inheritance relationships that exist between IOCs.
Figure 4.2.2.2-1 shows the inheritance hierarchy from IOC ManagedFunction related to the AMF Region/AMF Set NRM.
Figure 4.2.2.2-1: AMF Region/AMF Set Inheritance |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3 Class definitions | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.1 AMFFunction | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.1.1 Definition | This IOC represents the AMF functionality in 5GC. For more information about the AMF, see 3GPP TS 23.501 [3]. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.1.2 Attributes | Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
pLMNIdList
M
M
M
-
M
aMFIdentifier
M
M
M
-
M
sBIFQDN
M
M
M
-
M
sBIServiceList
M
M
-
-
M
weightFactor
M
M
M
-
M
nSSAI
CM
M
-
-
M |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.1.3 Attribute constraints | Name
Definition
nSSAI CM Support Qualifier
The condition is “network slicing feature is supported”. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.2 SMFFunction | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.2.1 Definition | This IOC represents the SMF function in 5GC. For more information about the SMF, see 3GPP TS 23.501 [3]. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.2.2 Attributes | Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
pLMNIdList
M
M
M
-
M
tAClist
M
M
M
-
M
sBIFQDN
M
M
M
-
M
sBIServiceList
M
M
-
-
M
nSSAI
CM
M
M
-
M |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.2.3 Attribute constraints | Name
Definition
nSSAI CM Support Qualifier
The condition is “network slicing feature is supported”. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.3 UPFFunction | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.3.1 Definition | This IOC represents the UPF function in 5GC. For more information about the UPF, see 3GPP TS 23.501 [3]. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.3.2 Attributes | Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
pLMNIdList
M
M
M
-
M
tAClist
M
M
M
-
M
nSSAI
CM
M
M
-
M |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.3.3 Attribute constraints | Name
Definition
nSSAI CM Support Qualifier
The condition is “network slicing feature is supported”. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.