Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 23.761  Word version:  17.0.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions and abbreviations  4 Architectural Requirements and Assumptions 
...

 

1  Scope  p. 10

With the growing usage of Multi-USIM devices in the market 3GPP is considering system enhancements that would allow better support of such devices.
This study item will address the objectives listed in the WID (SP-190248).

2  References  p. 10

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 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[3]
TS 38.304: "NR; User Equipment (UE) procedures in idle mode".
[4]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[5]
TS 22.101: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Service aspects; Service principles".
[6]
TS 23.502: "Procedures for the 5G System (5GS)".
[7]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[8]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[9]
TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[10]
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[11]
TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2".
[12]
TS 33.501: "Security architecture and procedures for 5G System".
[13]
RFC 5626:  " Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)".
[14]
TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
[15]
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[16]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[17]
TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
Up

3  Definitions and abbreviations  p. 11

3.1  Definitions  p. 11

For the purposes of the present document, the terms and definitions given in TR 21.905 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

3.3  Abbreviations  p. 11

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

4.1  Architectural Requirements  p. 11

The following architectural requirements apply:
  • The 3GPP system shall treat each registration from the USIMs of a Multi-USIM devices independently.
  • Each registered USIM in a Multi-USIM device shall be associated with a dedicated IMEI/PEI.
  • GSM, UMTS are out of scope.
  • End-user's determination on whether to have on-going service and/or incoming service is controlled by user.
  • An Emergency call related to one USIM for a multi-USIM device shall not be interrupted by the system autonomously without the calling or called party initiating the interruption, i.e. emergency calls related to one USIM shall not be interrupted autonomously by the system due to services for another USIM.
  • Solutions shall build on the 5G System architectural principles as in TS 23.501, including flexibility and modularity for newly introduced functionalities.
Up

4.2  Architectural Assumptions  p. 11

The following architectural assumptions apply:
  • The study shall focus on Dual-USIM devices, the expectation being that the enablers for Dual-USIM devices will also apply to Multi-USIM devices.
  • The study shall consider all of the following cases:
    • UE connected over 3GPP Access with EPS on one USIM and 5GS on the other USIM.
    • UE connected over 3GPP Access with EPS on both USIMs.
    • UE connected over 3GPP Access with 5GS on both USIMs.
  • Specific to Dual-USIM devices the study shall focus on Single Rx / Single Tx UEs and Dual Rx / Single Tx UEs.
  • The Multi-USIM device shall handle Emergency calls using clause 10.9 of TS 22.101 as a basis.
  • The problem statement is common to 5GS and EPS, but the solutions for 5GS and EPS need not be the same.
  • The system enablers for Multi-USIM devices are expected to apply for the cases where the multiple USIMs are owned by the same or by different MNOs.
  • The solutions shall not require network coordination for the case where the multiple USIMs in the Multi-USIM device are served by different serving networks.
  • A multi-USIM device with different USIMs may be camping with all USIMs on the same serving network RAN node, or it may be camping on different serving networks RAN nodes.
  • For a multi-USIM device, the solutions may require in-device co-ordination between the UEs represented by each USIM within the multi-USIM device. The mechanism for in-device co-ordination shall be left for the multi-USIM device implementation.
  • MUSIM features requiring new UE-network interactions are optional, hence the UE may use MUSIM features requiring new UE-network interactions in one PLMN when it has learnt that this PLMN supports these MUSIM features.
Up

Up   Top   ToC