Content for TR 23.700-61 Word version: 18.0.0
1 Scope
2 References
3 Definitions of terms and abbreviations
3.1 Terms
3.2 Abbreviations
4 Architectural Assumptions and Requirements
5 Key Issues
5.1 Key Issue #1: Determination of unavailability period in 5GS for a specific UE
...
...
1 Scope p. 7
This study will focus on the mechanism to determine the "unavailability period" in the 5G system for the UE.
2 References p. 7
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
3 Definitions of terms and abbreviations p. 7
3.1 Terms p. 7
For the purposes of the present document, the terms given in TR 21.905 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.
3.2 Abbreviations p. 7
4 Architectural Assumptions and Requirements p. 7
- The "unavailability period" may be made available on the user interface. Whether and how "unavailability period" is used on the user interface (if any) of the UE is outside the scope of this study.
-
The "unavailability period" for the UE is expected to be sufficiently long for the UE to execute required events such as:
- Silent reset at Modem;
- Security patch updates;
- OS upgrade;
- Modem SW updates; and
- Device reboot upon Modem setting changes via OMA-DM.
5 Key Issues p. 8
5.1 Key Issue #1: Determination of unavailability period in 5GS for a specific UE p. 8
5.1.1 Description p. 8
To execute certain events, for example OS upgrade, silent reset at modem or modem software updates (also commonly called as binary updates) there are 3 parties involved: the device, the operator and the application function. Once the UE has downloaded the binary, the time when the UE performs the upgrade is left for the UE implementation, with possibly UE implementations seeking user input. If UEs cannot execute the event (e.g. the storage capacity or the battery level are insufficient), they may delay execution of the event. These UEs become unavailable (i.e. cannot interact with the 5G System) in the order of minutes whenever such operations are performed. As UEs become unavailable without prior knowledge from the core network and/or application function, it can impact critical operations of an application server if it depends on availability of the UE during the unavailability period (i.e. a period of time during which the UE is not available).
The present key issue shall study:
- Whether and how an unavailability period is determined in 5GS for a specific UE.
- Study the expected UE and/or network actions (if any) based on determined unavailability period.
