METHOD AND DEVICE FOR CONTROL PLANE-BASED REGISTRATION AND REMOTE PROVISIONING IN COMMUNICATION SYSTEM

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. An operation method of an access and mobility management function (AMF) in a wireless communication network according to the disclosure includes: receiving, from a base station, a registration request message including a parameter indicating that a terminal supports control plane-based remote provisioning; determining the control plane-based remote provisioning, based on the parameter; and determining an authentication server function (AUSF) for onboarding of the terminal, based on the control plane-based remote provisioning.

Claims

1. A method of an access and mobility management function (AMF) in a communication network, the method comprising: receiving, from a base station, a registration request message comprising a parameter indicating that a terminal supports a control plane-based remote provisioning; determining, based on the parameter, the control plane-based remote provisioning; and determining, based on the control plane-based remote provisioning, an authentication server function (AUSF) for onboarding of the terminal.

2. A method of a security anchor function (SEAF) in a communication network, the method comprising: receiving, from a terminal, a message comprising a subscription concealed identifier (SUCI); generating, based on the message, a terminal authentication request message comprising the SUCI, a serving network (SN) name, and a control plane-based remote provisioning indicator; transmitting, to an authentication server function (AUSF), the terminal authentication request message to; and receiving a terminal authentication response message comprising a subscription permanent identifier (SUPI) in response to transmitting the terminal authentication request message.

3. The method of claim 2, wherein the terminal authentication response message further comprises a terminal authentication result.

4. The method of claim 2, further comprising: generating, based on the terminal authentication response message, a terminal remote provisioning request message comprising the SUPI, the SN name, and the control plane-based remote provisioning indicator; and transmitting, to a provisioning server (PVS), the terminal remote provisioning request message.

5. The method of claim 4, wherein an authentication procedure for the terminal is performed, based on the terminal remote provisioning request message, between the PVS and a default credentials server (DCS).

6. A method of an authentication server function (AUSF) in a communication network, the method comprising: receiving a first authentication request message comprising a subscription concealed identifier (SUCI), a serving network (SN) name, and a control plane-based remote provisioning indicator from a security anchor function (SEAF); transmitting, to a unified data management (UDM), a terminal authentication acquisition request message comprising the SUCI, the SN name, and the control plane-based remote provisioning indicator, based on the first authentication request message; and receiving a terminal authentication acquisition response message comprising a subscription permanent identifier (SUPI) from the UDM in response to transmitting the terminal authentication acquisition request message.

7. The method of claim 6, wherein the SUPI is generated by the UDM based on the SUCI.

8. The method of claim 6, further comprising transmitting, to a default credentials server (DCS), a second authentication request message comprising the SUPI, the SN name, and the control plane-based remote provisioning indicator based on the terminal authentication acquisition response message.

9. The method of claim 8, wherein the SUPI, the SN name, and the control plane-based remote provisioning indicator are transmitted to a a provisioning server (PVS) via a remote provisioning request message generated by the DCS.

10. The method of claim 9, further comprising receiving, from the DCS, a first authentication response message comprising the SUPI and a terminal authentication result in response to transmitting the second authentication request message.

11. The method of claim 10, further comprising transmitting, to the SEAF, a second authentication response message comprising the SUPI and the terminal authentication result based on the first authentication response message.

12. The method of claim 6, further comprising transmitting, to the SEAF, a first authentication response message comprising the SUPI based on the terminal authentication acquisition response message.

13. The method of claim 12, wherein the SUPI, the SN name, and the control plane-based remote provisioning indicator are transmitted to a PVS via a terminal remote provisioning request message generated by the SEAF.

14. A method of a provisioning server (PVS) in a communication network, the method comprising: receiving, from a default credentials server (DCS), a terminal remote provisioning request message comprising a subscription permanent identifier (SUPI), a serving network (SN) name, and a control plane-based remote provisioning indicator based on an authentication procedure for a terminal; receiving, based on the terminal remote provisioning request message, remote provisioning information from a subscription owner (SO)-standalone non-public network (NPN) (SNPN); and transmitting, to a unified data management (UDM), a terminal remote provisioning response message comprising the SUPI, an SNPN credential, and information for accessing the SO-SNPN based on the remote provisioning information.

15. The method of claim 14, wherein: a terminal parameter is updated by the UDM based on the terminal remote provisioning response message; the terminal parameter is transmitted to the terminal; and the terminal is configured to terminate, based on the terminal parameter, access to onboarding (ON)-SNPN and initialize a registration operation for the SO-SPNP.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0016] FIG. 1 illustrates a structure of a 5G network 10 according to embodiments of the present disclosure;

[0017] FIG. 2 illustrates a structure of a 5G network 10 according to embodiments of the present disclosure;

[0018] FIG. 3 illustrates a flowchart of a procedure in which a terminal 100 registers with an SNPN 20 in a wireless communication system 10 according to embodiments of the present disclosure;

[0019] FIG. 4 illustrates a flowchart of g an authentication procedure when a terminal 100 makes onboarding to an SNPN 20 in a wireless communication system according to embodiments of the present disclosure;

[0020] FIG. 5 illustrates a flowchart of an authentication procedure when a terminal 100 makes onboarding to an SNPN 20 in a wireless communication system according to embodiments of the present disclosure;

[0021] FIG. 6 illustrates a flowchart of a procedure for performing control plane-based remote provisioning from a PVS 1200 in a wireless communication system according to embodiments of the present disclosure;

[0022] FIG. 7 illustrates a configuration of a terminal 100 according to embodiments of the present disclosure;

[0023] FIG. 8 illustrates a configuration of a base station 200 according to embodiments of the present disclosure;

[0024] FIG. 9 illustrates a configuration of an AMF 500 according to embodiments of the present disclosure;

[0025] FIG. 10 illustrates a configuration of an SEAF 550 according to embodiments of the present disclosure;

[0026] FIG. 11 illustrates a configuration of an AUSF 900 according to embodiments of the present disclosure;

[0027] FIG. 12 illustrates a configuration of a UDM 1000 according to embodiments of the present disclosure;

[0028] FIG. 13 illustrates a configuration of a DCS 1100 according to embodiments of the present disclosure; and

[0029] FIG. 14 illustrates a configuration of a PVS 1200 according to embodiments of the present disclosure.

DETAILED DESCRIPTION

[0030] FIGS. 1 through 14, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0031] FIG. 1 illustrates a structure of a 5G network 10 according to embodiments of the present disclosure.

[0032] Referring to FIG. 1, the description of network entities or network nodes configuring the 5G network 10 is as follows.

[0033] A (radio) access network ((R)AN) 200, as a subject which performs radio resource allocation of a terminal 100, may be at least one of an eNode B, a Node B, a base station (BS), a next generation radio access network (NG-RAN), a 5G-AN, a radio access unit, a base station controller, or a node on the network. The terminal 100 may include a user equipment (UE), a next generation UE (NG UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, although an embodiment of the disclosure is described below using a 5G system as an example, the embodiment of the disclosure may be applied to other communication systems having a similar technical background. In addition, an embodiment of the disclosure may be applied to other communication systems via some modifications within a range which does not significantly deviate from the scope of the disclosure, as determined by a person having skilled technical knowledge.

[0034] As a wireless communication system evolves from a 4G system to a 5G system, the wireless communication system defines a next generation core (NG core) or 5G core network (5GC) which is a new core network. The new core network has virtualized all existing network entities (NEs) into network functions (NFs). According to an embodiment of the disclosure, a network function may refer to a network entity, a network component, or a network resource.

[0035] According to an embodiment of the disclosure, the 5GC may include NFs 300, 400, 500, 600, 700, 800, 900, 1000, 1500, 1600, 1700, and 1800 shown in FIG. 1. The disclosure is not limited to the example of FIG. 1, and the 5GC may include a larger number of NFs or a smaller number of NFs than the NFs shown in FIG. 1.

[0036] According to an embodiment of the disclosure, an access and mobility management function (AMF) 500 may be a network function of managing the mobility of the UE 100.

[0037] According to an embodiment of the disclosure, a session management function (SMF) 600 may be a network function of managing a packet data network (PDN) connection provided to the UE 100. The PDN connection may be referred to as a packet data unit (PDU) session.

[0038] According to an embodiment of the disclosure, a policy control function (PCF) 700 may be a network function of applying a service policy, a charging policy, and a PDU session policy of a mobile communication service provider with respect to the UE 100.

[0039] According to an embodiment of the disclosure, a unified data management (UDM) 1000 may be a network function of storing information on a subscriber.

[0040] According to an embodiment of the disclosure, a network exposure function (NEF) 1500 may be a function of providing information on the UE 100 to a server outside the 5G network. In addition, the NEF 1500 may provide a function of providing information necessary for a service to the 5G network and storing the information in a UDR (not shown).

[0041] According to an embodiment of the disclosure, a user plane function (UPF) 300 may be a function which serves as a gateway for transferring user data (PDU) to a data network (DN) 400.

[0042] According to an embodiment of the disclosure, a network repository function (NRF) 1600 may perform a function of discovering an NF.

[0043] According to an embodiment of the disclosure, an authentication server function (AUSF) 900 may perform UE authentication in a 3GPP access network and a non-3GPP access network.

[0044] According to an embodiment of the disclosure, a network slice selection function (NSSF) 800 may perform a function of selecting a network slice instance provided to the UE 100.

[0045] According to an embodiment of the disclosure, the data network (DN) 400 may be a data network through which the UE 100 transmits or receives data in order to use a service of a network service provider or a third party service.

[0046] FIG. 2 illustrates a structure of the 5G network 10 according to embodiments of the present disclosure.

[0047] Referring to FIG. 2, the wireless communication system 10 for transmitting, to the UE 100, standalone NPN (SNPN) credentials and subscriber information for accessing an SNPN 20 may include the UE 100, the onboarding SNPN (ON-SNPN) 20, a default credentials server (DCS) 1100, a provisioning server (PVS) 1200, and a subscription owner SNPN (SO-SNPN) 30 possessing SNPN credentials and subscriber information. This figure is a conceptual diagram illustrating control plane-based remote provisioning.

[0048] First, it is assumed that the terminal (UE) 100 does not have SNPN credentials and subscriber information (user subscription data), and the UE 100 has default UE credentials allocated by the DCS 1100. In addition, the DCS 1100 may allocate a subscription permanent identifier (SUPI) capable of uniquely identifying the UE 100 to the UE 100.

[0049] The ON-SNPN 20 may provide, to the UE 100, UP-based IP connectivity (UE onboarding) or CP-based non-access stratum (NAS) connectivity (UE onboarding) such that the UE 100 without SNPN credentials and subscriber information can receive the SNPN credentials and the subscriber information. The ON-SNPN may request authentication and authorization for the UE 100 from the DCS 1100 in order to determine whether to provide a UE onboarding service to the UE 100. FIG. 2 illustrates UP-based UE onboarding.

[0050] The DCS 1100 may pre-configure default UE credentials and an SUPI with respect to the UE 100 and then store the same. The DCS 1100 may receive, from the ON-SNPN, a request for authentication for the UE 100 when performing registration for UE onboarding. The authentication and authorization for the UE 100 is performed based on the default UE credentials and SUPI.

[0051] In addition, when the PVS 1200 transmits SNPN credentials and subscriber information to the UE 100, in order to determine whether the UE 100 is a UE having the right to receive the SNPN credentials and the subscriber information, the DCS 1100 may receive a request for UE authentication for the UE 100 from the PVS 1200. The DCS 1100 may be a manufacturer of the UE 100 or a third party associated with the manufacturer or an SNPN network service provider.

[0052] The PVS 1200 may receive user subscriber information such as user configuration information and SNPN credentials from the SO-SNPN 30 and transmit the same to the UE.

[0053] The PVS 1200 may exist as one server with the DCS 1100, and like the DCS 1100, the PVS 1200 may be a server owned by the manufacturer of the UE 100 or the third party associated with the SNPN network service provider. The PVS 1200 may communicate with the DCS 1100 for the authentication and authorization of the UE 100.

[0054] The SO-SNPN 30 possessing the SNPN credentials and the user subscriber information may transmit the SNPN credentials and the user subscriber information to the UE 100 via the PVS 1200.

[0055] FIG. 3 illustrates a flowchart of a procedure in which the UE 100 registers with the SNPN 20 in the wireless communication system 10 according to embodiments of the present disclosure.

[0056] Referring to FIG. 3, in operation S401, the UE 100 may transmit a registration request message to the (R)AN 200 in order to make onboarding to the ON-SNPN 20. The registration request message may include information indicating that the UE 100 performs CP-based remote provisioning. For example, the registration request message may include a 5GS mobility management (5GMM) core network capability parameter. For example, the 5GMM core network capability parameter may include an information element (IE) called a parameter of a network operation for supporting remote provisioning (parameter in supported network behavior for remote provisioning). For example, the information element may indicate a remote provisioning scheme requested by the UE 100. For example, the information element may indicate control plane-based remote provisioning. The RAN 200 may receive the registration request message from the UE 100.

[0057] In operation S402, the RAN 200 may select the AMF 500 supporting onboarding, based on the registration request message received from the UE 100.

[0058] In operation S403, the RAN 200 may transmit the registration request message received from the UE 100 to the selected AMF 500. The AMF 500 may receive the registration request message from the RAN 200.

[0059] In operation S404, the AMF 500 may determine a remote provisioning scheme for the UE 100, based on the registration request message. For example, the AMF 500 may determine a remote provisioning scheme for the UE 100, based on the 5GMM core network capability parameter included in the registration request message. For example, the AMF 500 may determine the remote provisioning scheme for the UE 100 as a control plane-based (CP-based) remote provisioning, based on the 5GMM core network capability parameter.

[0060] In operation S405, the AMF 500 may transmit an identifier request message for requesting an identifier of the UE 100 to the UE 100. For example, the identifier of the UE 100 may be an international mobile equipment identity (IMEI). The UE 100 may receive the identifier request message from the AMF 500.

[0061] In operation S406, the UE 100 may transmit an identifier response message including the identifier of the UE 100 to the AMF 500, based on the identifier request message received from the AMF 500. The AMF 500 may receive the identifier response message from the UE 100. Operations S405 and S406 may be selectively performed.

[0062] In operation S407, the AMF 500 may select the AUSF 900 which performs authentication for the UE 100. For example, when operations S405 and S406 are performed, the AMF 500 may select the AUSF 900, based on the registration request message and the identifier response message. For example, when operations S405 and S406 are not performed, the AMF 500 may select the AUSF 900, based on the registration request message.

[0063] FIG. 4 illustrates a flowchart of an authentication procedure when the UE 100 makes onboarding to the SNPN 20 in a wireless communication system according to embodiments of the present disclosure.

[0064] Referring to FIG. 4, an authentication procedure when the UE 100 makes onboarding to the SNPN 20 may be performed simultaneously with a registration procedure of the UE 100 of FIG. 3. For example, operations S501 to S504 may be performed during the SNPN registration procedure of FIG. 3.

[0065] In operation S501, the UE 100 may transmit an N1 message to a security anchor function (SEAF) 550. For example, the N1 message may include a subscription concealed identifier (SUCI). The SEAF 900 may receive the N1 message from the UE 100.

[0066] In operation S502, the SEAF 550 may transmit a UE authentication request message (Nausf_UEAuthentication_Authenticate Request) to the AUSF 900. The SEAF 550 may generate the UE authentication request message, based on the N1 message. For example, the UE authentication request message may include an SUCI (or subscription permanent identifier (SUPI)), a serving network (SN)-name, and a control plane-based remote provisioning indicator. The AUSF 900 may receive the UE authentication request message from the SEAF 550.

[0067] In operation S503, the AUSF 900 may generate a UE authentication acquisition request message (Nudm_UEAuthenticationGet Request), based on the UE authentication request message received from the SEAF 550. The AUSF 900 may transmit the UE authentication acquisition request message to the UDM 1000. For example, the UE authentication acquisition request message may include an SUCI (or SUPI), an SN-name, and a control plane-based remote provisioning indicator. The UDM 1000 may receive the UE authentication acquisition request message from the AUSF 900.

[0068] In operation S503-1, the UDM 1000 may de-conceal the SUCI, based on the UE authentication acquisition request message received from the AUSF 900 to convert the SUCI into the SUPI.

[0069] In operation S503-2, the UDM 1000 may select an authentication method, based on the UE authentication request message. In operation S503-3, the UDM 1000 may prepare to perform control plane-based remote provisioning, based on the UE authentication request message. For example, the UDM 1000 may prepare to receive remote provisioning information from the PVS 1200, based on the UE authentication request message.

[0070] In operation S504, the UDM 1000 may transmit a UE authentication acquisition response message (Nudm_UEAuthenticationGet Response) to the AUSF 900. The UE authentication acquisition response message may include an SUPI. The AUSF 900 may receive the UE authentication acquisition response message from the UDM 1000.

[0071] In operation S505, the AUSF 900 may select the DCS 1100, based on the SUPI included in the UE authentication acquisition response message received from the UDM 1000. The AUSF 900 may generate a UE authentication request message (Ndcs_UEAuthentication Request), based on the UE authentication acquisition response message. For example, the UE authentication request message may include an SUPI, an SN-name, and a control plane-based remote provisioning indicator. The AUSF 900 may transmit the UE authentication request message to the DCS 1100. The DCS 1100 may receive the UE authentication request message from the AUSF 900.

[0072] In operation S506, the DCS 1100 may perform authentication for the UE 100, based on the UE authentication request message received from the AUSF 900. The DCS 1100 may generate a UE remote provisioning request message (Npvs_UERemoteProvisioning Request), based on the UE authentication request message. For example, the UE remote provisioning request message may include an SUPI, an SN-name, and a control plane-based remote provisioning indicator. The DCS 1100 may transmit the UE remote provisioning request message to the PVS 1200 after performing the authentication for the UE 100. The PVS 1200 may receive the UE remote provisioning request message from the DCS 1100. The PVS 1200 may perform control plane-based remote provisioning with respect to the UE 100, based on the UE remote provisioning request message.

[0073] In operation S507, the DCS 1100 may generate a UE authentication response message (Ndcs_UEAuthentication Response), based on a result of performing the authentication for the UE 100. For example, the UE authentication response message may include an SUPI and a UE authentication result. The DCS 1100 may transmit the UE authentication response message to the AUSF 900. The AUSF 900 may receive the UE authentication response message from the DCS 1100.

[0074] In operation S508, the AUSF 900 may generate a UE authentication response message (Nausf_UEAuthentication_Authenticate Response), based on the UE authentication response message received from the DCS 1100. For example, the UE authentication response message may include an SUPI and a UE authentication result. The AUSF 900 may transmit the UE authentication response message to the SEAF 550. The SEAF 550 may receive the UE authentication response message from the AUSF 900.

[0075] FIG. 5 illustrates a flowchart of an authentication procedure when the UE 100 makes onboarding to the SNPN 20 in a wireless communication system according to embodiments of the present disclosure.

[0076] Referring to FIG. 5, FIG. 5 may be another embodiment of FIG. 4. For example, operations S601 to S604 may be the same as operations S501 to S504 of FIG. 4. In FIG. 5, it is assumed that UE authentication by the DCS 1100 has already been performed.

[0077] In operation S605, the AUSF 900 may generate a UE authentication response message, based on a UE authentication acquisition response message received from the UDM 1000. For example, the UE authentication response message may include an SUPI. The AUSF 900 may transmit the UE authentication response message to the SEAF 550. The SEAF 550 may receive a UE authentication request message from the AUSF 900.

[0078] In operation S606, the SEAF 550 may generate a UE remote provisioning request message (Npvs_UERemoteProvisioning Request), based on the UE authentication request message received from the AUSF 900. For example, the UE remote provisioning request message may include an SUPI, an SN-name, and a control plane-based remote provisioning indicator. The SEAF 550 may transmit the UE remote provisioning request message to the PVS 1200. The PVS 1200 may receive the UE remote provisioning request message from the SEAF 550.

[0079] In operation S607, the PVS 1200 may perform control plane-based remote provisioning with respect to the UE 100, based on the UE remote provisioning request message received from the SEAF 550. The PVS 1200 may perform UE authentication with the DCS 1100, based on the UE remote provisioning request message received from the SEAF 550. For example, the PVS 1200 may generate a UE authentication request message, based on the UE remote provisioning request message. The UE authentication request message may include an SUPI. The PVS 1200 may transmit the UE authentication request message to the DCS 1100. The DCS 1100 may receive the UE authentication request message from the PVS 1200. In response to the UE authentication request message, the DCS 1100 may transmit, to the PVS 1200, the authentication result for the UE 100 which has already been performed.

[0080] FIG. 6 illustrates a flowchart of a procedure for performing control plane-based remote provisioning from the PVS 1200 in a wireless communication system according to embodiments of the present disclosure.

[0081] Referring to FIG. 6, the UE 100, the AMF 500, the UDM 1000, the DCS 1100, and the PVS 1200 may perform an operation for UE authentication/security. For example, the DCS 1100 may authenticate the UE 100 via the operation for UE authentication/security.

[0082] In operation S701, after authenticating the UE 100, the DCS 1100 may generate a UE remote provisioning request message (Npvs_UERemoteProvisioning Request). For example, the UE remote provisioning request message may include an SUPI, an SN-name, and a control plane-based remote provisioning indicator. The DCS 1100 may transmit the UE remote provisioning request message to the PVS 1200. The PVS 1200 may receive the UE remote provisioning request message from the DCS 1100.

[0083] The PVS 1200 may transmit a request message for requesting remote provisioning information to the SO-SNPN 30, based on the UE remote provisioning request message. The PVS 1200 may receive the remote provisioning information from the SO-SNPN 30 in response to the request message. For example, the remote provisioning information may include SNPN credential information and access information for accessing the SO-SNPN 30.

[0084] In operation S702, the PVS 1200 may generate a UE remote provisioning response message (Npvs_UERemoteProvisioning Response), based on the remote provisioning information. For example, the UE remote provisioning response message may include an SUPI, SNPN credential information, and access information for accessing the SO-SNPN 30. The PVS 1200 may transmit the UE remote provisioning response message to the UDM 1000. The UDM 1000 may receive the UE remote provisioning response message from the PVS 1200.

[0085] In operation S703, the UDM 1000 may determine to perform a UE parameters update (UPU) procedure. The UDM 1000 may update a parameter for the UE 100, based on the UE remote provisioning response message received from the PVS 1200.

[0086] In operation S704, the UDM 1000 may generate a subscriber data management (SDM) notification message (Nudm_SDM_Notification), based on the updated parameter. The UDM 1000 may transmit the SDM_notification message to the AMF 500. The AMF 500 may receive the SDM notification message from the UDM 1000.

[0087] In operation S705, the AMF 500 may transmit an SDM information message (Nudm_SDM_Info) to the UDM 1000 in response to the SDM notification message. The UDM 1000 may receive the SDM information message from the AMF 500.

[0088] In operation S706, the AMF 500 may generate a downlink (DL) NAS transport message including a UPU container. The AMF 500 may transmit the DL NAS transport message to the UE 100. The UE 100 may receive the DL NAS transport message from the AMF 500.

[0089] In operation S707, the UE 100 may generate a uplink (UL) NAS message including an UP acknowledgment (ACK), based on the DL NAS transport message. The UE 100 may transmit the UL NAS message to the AMF 500. The AMF 500 may receive the UL NAS message from the UE 100.

[0090] In operation S708, the AMF 500 may generate an SDM information message, based on the UL NAS message. The AMF 500 may transmit the SDM information message to the UDM 1000.

[0091] In operation S709, the UE 100 may terminate access to the ON-SNPN 20 in order to access the SO-SNPN 30. For example, the UE 100 may determine whether a request for re-registration has been generated from the UDM 1000, based on the DL NAS transport message. When the request for re-registration is generated from the UDM 1000, the UE 100 may initialize the re-registration. For example, the UE 100 may initialize registration to access the SO-SNPN 30.

[0092] FIG. 7 illustrates a configuration of the UE 100 according to embodiments of the present disclosure.

[0093] The UE 100 according to the disclosure may include a controller 102 configured to control the overall operation of the UE 100, a transceiver 101 including a transmitter and a receiver, and a memory 103. The disclosure is not limited to the above example, and the UE may include more or fewer configurations than the configurations shown in FIG. 7.

[0094] According to the disclosure, the transceiver 101 may transmit or receive a signal to or from network entities 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1400, 1500, 1600, and 1700 or another UE. A signal transmitted to or received from the network entities 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1400, 1500, 1600, and 1700 may include control information and data. In addition, the transceiver 101 may receive a signal via a wireless channel to output the signal to the controller 102, and transmit the signal output from the controller 102 via the wireless channel.

[0095] According to the disclosure, the controller 102 may control the UE 100 to perform the operations of FIGS. 3 to 6 described above. The controller 102, the memory 103, and the transceiver 101 are not required to be necessarily implemented as separate modules, and may be implemented as one component in the form of a single chip. In addition, the controller 102 and the transceiver 101 may be electrically connected to each other. In addition, the controller 102 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0096] According to an embodiment of the disclosure, the memory 103 may store data, such as a basic program, an application program, and configuration information, for the operation of the UE 100. In particular, the memory 103 provides the stored data according to a request of the controller 102. The memory 103 may be configured by a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage mediums. In addition, the UE may include a plurality of memories 103. In addition, the controller 102 may perform the above-described embodiments, based on a program for performing the above-described embodiments of the disclosure, the program being stored in the memory 103.

[0097] FIG. 8 illustrates a configuration of the base station 200 according to embodiments of the present disclosure.

[0098] The base station 200 according to the disclosure may include a controller 202 configured to control the overall operation of the base station 200, a transceiver 201 including a transmitter and a receiver, and a memory 203. The disclosure is not limited to the above example, and the base station 200 may include more or fewer configurations than the configurations shown in FIG. 8.

[0099] According to the disclosure, the transceiver 201 may transmit or receive a signal to or from at least one of other network entities 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100. A signal transmitted to or received from at least one of the other network entities 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100 may include control information and data.

[0100] According to the disclosure, the controller 202 may control the base station 200 to perform the operations of FIGS. 3 to 6 described above. The controller 202, the memory 203, and the transceiver 201 are not required to be necessarily implemented as separate modules, and may be implemented as one component in the form of a single chip. In addition, the controller 202 and the transceiver 201 may be electrically connected to each other. In addition, the controller 202 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0101] According to the disclosure, the memory 203 may store data, such as a basic program, an application program, and configuration information, for the operation of the base station 200. In particular, the memory 203 provides the stored data according to a request of the controller 202. The memory 203 may be configured by a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage mediums. In addition, there may be a plurality of memories 203. In addition, the controller 202 may perform the above-described embodiments, based on a program for performing the above-described embodiments of the disclosure, the program being stored in the memory 203.

[0102] FIG. 9 illustrates a configuration of the AMF 500 according to embodiments of the present disclosure.

[0103] The AMF 500 according to the disclosure may include a controller 502 configured to control the overall operation of the AMF 500, a network interface 501 including a transmitter and a receiver, and a memory 503. The disclosure is not limited to the above example, and the AMF 500 may include more or fewer configurations than the configurations shown in FIG. 9.

[0104] According to the disclosure, the network interface 501 may transmit or receive a signal to or from at least one of other network entities 200, 300, 400, 600, 700, 800, 900, 1000, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100. A signal transmitted to or received from at least one of the other network entities 200, 300, 400, 600, 700, 800, 900, 1000, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100 may include control information and data.

[0105] According to the disclosure, the controller 502 may control the AMF 500 to perform the operations of FIGS. 3 to 6 described above. The controller 502, the memory 503, and the network interface 501 are not required to be necessarily implemented as separate modules, and may be implemented as one component in the form of a single chip. In addition, the controller 502 and the network interface 501 may be electrically connected to each other. In addition, the controller 502 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0106] According to the disclosure, the memory 503 may store data, such as a basic program, an application program, and configuration information, for the operation of the AMF 500. In particular, the memory 503 provides the stored data according to a request of the controller 502. The memory 503 may be configured by a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage mediums. In addition, there may be a plurality of memories 503. In addition, the controller 502 may perform the above-described embodiments, based on a program for performing the above-described embodiments of the disclosure, the program being stored in the memory 503.

[0107] FIG. 10 illustrates a configuration of the SEAF 550 according to embodiments of the present disclosure.

[0108] The SEAF 550 according to the disclosure may include a controller 552 configured to control the overall operation of the SEAF 550, a network interface 551 including a transmitter and a receiver, and a memory 553. The disclosure is not limited to the above example, and the SEAF 550 may include more or fewer configurations than the configurations shown in FIG. 10.

[0109] According to the disclosure, the network interface 551 may transmit or receive a signal to or from at least one of other network entities 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100. A signal transmitted to or received from at least one of the other network entities 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100 may include control information and data.

[0110] According to the disclosure, the controller 552 may control the SEAF 550 to perform the operations of FIGS. 3 to 6 described above. The controller 552, the memory 553, and the network interface 551 are not required to be necessarily implemented as separate modules, and may be implemented as one component in the form of a single chip. In addition, the controller 552 and the network interface 551 may be electrically connected to each other. In addition, the controller 552 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0111] According to the disclosure, the memory 553 may store data, such as a basic program, an application program, and configuration information, for the operation of the SEAF 550. In particular, the memory 553 provides the stored data according to a request of the controller 552. The memory 553 may be configured by a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage mediums. In addition, there may be a plurality of memories 553. In addition, the controller 552 may perform the above-described embodiments, based on a program for performing the above-described embodiments of the disclosure, the program being stored in the memory 553.

[0112] FIG. 11 illustrates a configuration of the AUSF 900 according to embodiments of the present disclosure.

[0113] The AUSF 900 according to the disclosure may include a controller 902 configured to control the overall operation of the AUSF 900, a network interface 901 including a transmitter and a receiver, and a memory 903. The disclosure is not limited to the above example, and the AUSF 900 may include more or fewer configurations than the configurations shown in FIG. 11.

[0114] According to the disclosure, the network interface 901 may transmit or receive a signal to or from at least one of other network entities 200, 300, 400, 500, 550, 600, 700, 800, 900, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100. A signal transmitted to or received from at least one of the other network entities 200, 300, 400, 500, 550, 600, 700, 800, 900, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100 may include control information and data.

[0115] According to the disclosure, the controller 902 may control the AUSF 900 to perform the operations of FIGS. 3 to 6 described above. The controller 902, the memory 903, and the network interface 901 are not required to be necessarily implemented as separate modules, and may be implemented as one component in the form of a single chip. In addition, the controller 902 and the network interface 901 may be electrically connected to each other. In addition, the controller 902 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0116] According to the disclosure, the memory 903 may store data, such as a basic program, an application program, and configuration information, for the operation of the AUSF 900. In particular, the memory 1003 provides the stored data according to a request of the controller 902. The memory 903 may be configured by a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, or a DVD, or a combination of storage mediums. In addition, there may be a plurality of memories 903. In addition, the controller 902 may perform the above-described embodiments, based on a program for performing the above-described embodiments of the disclosure, the program being stored in the memory 903.

[0117] FIG. 12 illustrates a configuration of the UDM 1000 according to embodiments of the present disclosure.

[0118] The UDM 1000 according to the disclosure may include a controller 1002 configured to control the overall operation of the UDM 1000, a network interface 1001 including a transmitter and a receiver, and a memory 1003. The disclosure is not limited to the above example, and the UDM 1000 may include more or fewer configurations than the configurations shown in FIG. 12.

[0119] According to the disclosure, the network interface 1001 may transmit or receive a signal to or from at least one of other network entities 200, 300, 400, 500, 550, 600, 700, 800, 900, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100. A signal transmitted to or received from at least one of the other network entities 200, 300, 400, 500, 550, 600, 700, 800, 900, 1100, 1200, 1400, 1500, 1600, and 1700 or the UE 100 may include control information and data.

[0120] According to the disclosure, the controller 1002 may control the UDM 1000 to perform the operations of FIGS. 3 to 6 described above. The controller 1002, the memory 1003, and the network interface 1001 are not required to be necessarily implemented as separate modules, and may be implemented as one component in the form of a single chip. In addition, the controller 1002 and the network interface 1001 may be electrically connected to each other. In addition, the controller 1002 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0121] According to the disclosure, the memory 1003 may store data, such as a basic program, an application program, and configuration information, for the operation of the UDM 1000. In particular, the memory 1003 provides the stored data according to a request of the controller 1002. The memory 1003 may be configured by a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, or a DVD, or a combination of storage mediums. In addition, there may be a plurality of memories 1003. In addition, the controller 1002 may perform the above-described embodiments, based on a program for performing the above-described embodiments of the disclosure, the program being stored in the memory 1003.

[0122] FIG. 13 illustrates a configuration of the DCS 1100 according to embodiments of the present disclosure.

[0123] The DCS 1100 according to the disclosure may include a controller 1202 configured to control the overall operation of the DCS 1100, a network interface 1101 including a transmitter and a receiver, and a memory 1103. The disclosure is not limited to the above example, and the DCS 1100 may include more or fewer configurations than the configurations shown in FIG. 13.

[0124] According to the disclosure, the network interface 1101 may transmit or receive a signal to or from at least one of other network entities 200, 300, 400, 500, 550, 600, 700, 800, 900, 1000, 1200, 1400, 1500, 1600, and 1700 or the UE 100. A signal transmitted to or received from at least one of the other network entities 200, 300, 400, 500, 550, 600, 700, 800, 900, 1000, 1200, 1400, 1500, 1600, and 1700 or the UE 100 may include control information and data.

[0125] According to the disclosure, the controller 1102 may control the DCS 1100 to perform the operations of FIGS. 3 to 6 described above. The controller 1102, the memory 1103, and the network interface 1101 are not required to be necessarily implemented as separate modules, and may be implemented as one component in the form of a single chip. In addition, the controller 1102 and the network interface 1101 may be electrically connected to each other. In addition, the controller 1102 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0126] According to the disclosure, the memory 1103 may store data, such as a basic program, an application program, and configuration information, for the operation of the DCS 1100. In particular, the memory 1103 provides the stored data according to a request of the controller 1102. The memory 1103 may be configured by a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage mediums. In addition, there may be a plurality of memories 1103. In addition, the controller 1102 may perform the above-described embodiments, based on a program for performing the above-described embodiments of the disclosure, the program being stored in the memory 1103.

[0127] FIG. 14 illustrates a configuration of the PVS 1200 according to embodiments of the present disclosure.

[0128] The PVS 1200 according to the disclosure may include a controller 1202 configured to control the overall operation of the PVS 1200, a network interface 1201 including a transmitter and a receiver, and a memory 1203. The disclosure is not limited to the above example, and the PVS 1200 may include more or fewer configurations than the configurations shown in FIG. 14.

[0129] According to the disclosure, the network interface 1201 may transmit or receive a signal to or from at least one of other network entities 200, 300, 400, 500, 550, 600, 700, 800, 900, 1000, 1100, 1300, 1400, 1500, 1600, and 1700 or the UE 100. A signal transmitted to or received from at least one of the other network entities 200, 300, 400, 500, 550, 600, 700, 800, 900, 1000, 1100, 1300, 1400, 1500, 1600, and 1700 or the UE 100 may include control information and data.

[0130] According to the disclosure, the controller 1202 may control the PVS 1200 to perform the operations of FIGS. 3 to 6 described above. The controller 1202, the memory 1203, and the network interface 1201 are not required to be necessarily implemented as separate modules, and may be implemented as one component in the form of a single chip. In addition, the controller 1202 and the network interface 1201 may be electrically connected to each other. In addition, the controller 1202 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0131] According to the disclosure, the memory 1203 may store data, such as a basic program, an application program, and configuration information, for the operation of an EIR server 1400. In particular, the memory 1203 provides the stored data according to a request of the controller 1202. The memory 1203 may be configured by a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage mediums. In addition, there may be a plurality of memories 1203. In addition, the controller 1202 may perform the above-described embodiments, based on a program for performing the above-described embodiments of the disclosure, the program being stored in the memory 1203.

[0132] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.