Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 24.811  Word version:  17.0.0

Top   Top   None   None   Next
1…   5…

 

1  ScopeWord‑p. 11

The present document is to study the stage 2 and the stage 3 aspects for service requirements defined by SA WG1 under SA1 work item MINT (Minimization of Service Interruption), as specified in TS 22.011 and TS 22.261.

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.
  • 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.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.011: "Service accessibility".
[3]
TS 22.261: "Service requirements for the 5G system; Stage 1".
[4]
TS 23.501: "System architecture for the 5G System (5GS); Stage 2".
[5]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[6]
TS 28.533: "Management and orchestration; Architecture framework".
[7]
TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
[8]
TS 23.502: "Procedures for the 5G System (5GS)".
[9]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
Up

3  Definitions of terms, symbols and abbreviations

3.1  Terms

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.
PLMN with Disaster Condition:
A PLMN to which a Disaster Condition applies.
PLMN without Disaster Condition:
A PLMN to which no Disaster Condition applies.
For the purposes of the present document, the following terms and definitions given in TS 22.261 apply:
Disaster Condition
Disaster Inbound Roamer
Disaster Roaming
For the purposes of the present document, the following terms and definitions given in TS 23.122 apply:
Allowable PLMN
Up

3.2  SymbolsWord‑p. 12

Void

3.3  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 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.

4  Architectural Assumptions and Requirements

4.1  Architectural Assumptions

The following architectural assumptions apply:
  • The PDU sessions of the UE can be transferred when a UE moves from a PLMN with Disaster Condition to a PLMN providing Disaster Roaming.
  • In principle, the Disaster Inbound Roamers can receive the same services in a PLMN without Disaster Condition as non-disaster inbound roamers can receive in the PLMN without Disaster Condition, subject to agreement between HPLMN of the UE and the PLMN without Disaster Condition, regulations of the country, and constraints of the PLMN without Disaster Condition.
  • The network functions except one or more RAN nodes of the PLMN with Disaster Condition can be assumed to be still operational. One or more RAN nodes of the PLMN with Disaster Condition are non-operational.
  • Architecture defined in TS 23.501 is used as basis architecture for supporting minimization of service interruption.
Up

4.2  Architectural Requirements

The system shall satisfy the stage-1 requirements in TS 22.261, clause 6.31 and TS 22.011, clause 3.2.2.
The solution shall enable a UE of a selected PLMN (HPLMN or VPLMN) with Disaster Condition, to select and register on another PLMN without Disaster Condition in UE's forbidden PLMN list when no other PLMN is available except for PLMNs in UE's forbidden PLMN list and the PLMN without Disaster Condition is able to accept Disaster Inbound Roamers from the PLMN with Disaster Condition.
If the UE, with HPLMN subscription, was informed by the HPLMN that it should apply Disaster Roaming when a Disaster Condition arises (in the HPLMN or a VPLMN), the solution shall enable a UE to detect that a Disaster Condition applies to PLMN D, where PLMN D is the UE's HPLMN or a PLMN not in the UE's forbidden PLMNs list, regardless of whether the UE is registered in PLMN D or not. When the UE detects that a Disaster Condition applies to PLMN D, the solution shall enable the UE to select and to register on another PLMN without Disaster Condition in the UE's forbidden PLMNs list when no other PLMN is available except for PLMNs in the UE's forbidden PLMNs list and the PLMN without Disaster Condition is able to accept Disaster Inbound Roamers from the PLMN with Disaster Condition.
Up

Up   Top   ToC