name: SHO
full_form: Selected Home Operator
context: 13. The PVA sends the validation results back to the SHO, according to the SHO requirements. 14. The SHO encrypt the MCIM by using the PfC and generate the management object for M (e.g MCIMobj). 15. The SHO delivers the encrypted MCIM (e.g. within MCIMobj) to the RO (DPF) and authorizes provisioning of the MCIM application to the M2ME. 16. The RO (DPF) downloads a MCIM object to the M2ME. 17. The M2ME provisions the downloaded MCIM into the TRE. The TRE decrypts MCIMobj by using the TRE Platform Key to obtain the MCIM. 18. The M2ME reports the success/failure status of the provisioning to the RO (DPF). 19. The RO (DPF) reports the success/failure status of the provisioning back to the SHO The step 11 to 19 describes the phase of MCIM application provision. Thus the M2ME can attach to the network of the SHO by using the MCIM. Then the SHO provides the M2ME with operational service. The procedure of how to initially provision the MCIM to the M2ME is executed as depicted in figure
description: The Selected Home Operator (SHO) is a network function responsible for managing and provisioning Mobile Communication Identity Module (MCIM) applications to devices. It handles encryption, validation, and authorization processes. The SHO interacts with other network functions such as the PVA, RO (DPF), and M2ME to ensure secure and successful MCIM application provisioning.
explanation: The text describes the SHO's role in managing applications, interacting with other network components, and performing security-related tasks like encryption and authorization. These characteristics are typical of a Network Function within telecommunications.
section_title: 5.1.3.6.3	Network Interactions for MCIM Provisioning in case of 3GPP Access
biotag_Context: O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Procedure,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Network Function,O,O,O,O,O,B-Interface,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Interface,O,O,O,B-Network Function,O,O,O,O,O,O,B-Device,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Interface,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,B-Procedure,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Interface,O,O,B-Device,O,O,O,O,O,B-Network Function,O,O