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 22.944  Word version:  18.0.1

Top   Top   Up   Prev   Next
0…   5…   A   B… 
5 Requirements  5.1 General  5.2 Security  5.3 Functionality split  5.3.1 MT Functions  5.3.2 TE Functions  5.4 TE-MT Reference Point 
...

 

5  Requirements  p. 8

Requirements are identified for only the single active subscription for each TE-MT combination case. Requirements for the other more general cases may be added in later releases.

5.1  General  p. 8

  1. The functionality split proposed applies to Circuit Switched (CS) domain.
  2. The functionality split proposed applies to the Packet Switched (PS) domain.
  3. The user should be able to control which MTs and TEs are part of their user equipment combination.
  4. A standardized API for access to capabilities provided by an MT (TE) towards a TE (MT) across Operating Systems must be provided.
  5. It must be possible to develop applications in the TE that use 3GPP services independently of the specific 3GPP defined radio module being used. For example the application developer should not need to write different applications for 3GPP defined radio modules made by different companies.
  6. Control over those radio aspects as currently available with AT commands should be provided to the TE by the MT. Access to additional functions is not required.
  7. Call control signalling (e.g. IMS SIP signalling) must not be run transparently through the MT by the TE in this Release. [Note: This requirement is FFS currently under review.].
Up

5.2  Security  p. 9

  1. IMEI must be collocated with Mobility Management functions.
  2. The USIM/SIM and if relevant the ISIM application must be a part of the MT.
  3. The architecture for UE Functionality Split must provide a solution with equivalent or better security than the integrated (non-split) UE architecture. Particular attention should be paid to the origination point of call control signalling to ensure that the TE does not insert false information without detection in the MT or the network.
  4. Access to any parts of the network must not be given to unauthorised entities.
Up

5.3  Functionality split  p. 9

5.3.1  MT Functions  p. 9

  1. Radio attachment to the 3GPP network.
  2. Authenticating subscription(s) (including IMS subscription).
  3. Communicating with the application(s) resident on the UICC on behalf of the TE.
  4. Creation/activation/deactivation of additional PDP contexts on demand from a TE.
  5. Transceiving PS data across the appropriate Radio Access Bearers with the RAN
  6. Security
  7. Call control (including call control for IMS) [Note: This requirement is FFS.]
  8. Mobility Management function. Given this requirement, all relevant security-related identities (IMEI, IMSI, TMSI, etc.) must be located on the MT or UICC.
Up

5.3.2  TE Functions  p. 9

  1. Control of hardware in the TE (speaker, microphones, video cameras, displays, etc.)
  2. Access to services and capabilities provided by the MT. [Note: The services and capabilities provided by the MT which can be accessed by the TE are FFS].
  3. Call control [Note: This requirement is FFS.]

5.4  TE-MT Reference Point  p. 10

  1. The interface between a TE and an MT uses the TS 27.007 and TS 27.005 AT command set.

Up   Top   ToC