Method for discovery and selection of server authenticating and transmitting user subscription data and apparatus thereof

Abstract

The present disclosure relates to a communication technique and a system for integrating a 5G communication system with IoT technology to support higher data transmission rates than those of 4G systems. The present disclosure can be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. A method for selecting a server of a first stand-alone non-public network (SNPN) that a terminal is onboarding in a wireless communication system according to an embodiment of the present invention comprises the steps of receiving a Network Access Identifier set as a unique identifier of the terminal from the terminal, selecting a Default Credential Server based on address information of a Default Credential Server included in the Network Access Identifier, and receiving address information of a provisioning server selected from the Default Credential Server from the Default Credential Server.

Description

Technology Field

[0001] The present invention relates to a communication system, and more particularly to a method for a terminal to search for and select a server for terminal authentication and subscriber information data transmission in order to receive subscriber information in a non-public network (NPN). Background Technology

[0002] Efforts are being made to develop improved 5G (5th generation) communication systems or pre-5G communication systems to meet the increasing demand for wireless data traffic following the commercialization of 4G (4th generation) communication systems. For this reason, 5G communication systems or pre-5G communication systems are referred to as Beyond 4G Network communication systems or Post-LTE systems.

[0003] To achieve high data transmission rates, 5G communication systems are being considered for implementation in the mmWave band (e.g., the 60 GHz band). To mitigate path loss and increase the transmission distance of radio waves in the mmWave band, beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna technologies are being discussed for 5G communication systems.

[0004] In addition, to improve the network of the system, technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation are being developed in 5G communication systems.

[0005] In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (Non Orthogonal Multiple Access), and SCMA (Sparse Code Multiple Access) are being developed in 5G systems.

[0006] 5G systems are considering support for a wider variety of services compared to existing 4G systems. For example, the most representative services may include enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), massive machine-type communication (mMTC), and evolved multimedia broadcast / multicast service (eMBMS). Furthermore, a system providing the aforementioned URLLC service may be referred to as a URLLC system, and a system providing eMBB service may be referred to as an eMBB system. Additionally, the terms "service" and "system" may be used interchangeably.

[0007] Among these, URLLC services are being newly considered in 5G systems, unlike existing 4G systems, and require the satisfaction of ultra-high reliability (e.g., packet error rate of about 10⁻⁵) and low latency (e.g., about 0.5 msec) conditions compared to other services. To satisfy these strict requirements, URLLC services may require the application of a transmission time interval (TTI) shorter than that of eMBB services, and various operational methods utilizing this are being considered.

[0008] Meanwhile, the Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; recently, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) are being researched for connecting objects.

[0009] In an IoT environment, intelligent IT (Internet Technology) services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT (Information Technology) and various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0010] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, Machine to Machine (M2M), and Machine Type Communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud RAN as a big data processing technology, as previously described, can also be considered an example of the convergence of 5G and IoT technologies.

[0011] As described above and with the advancement of mobile communication systems, it has become possible to provide various services; consequently, there is a need for measures to efficiently utilize Non-Public Networks (NPNs) to provide these diverse services using private networks in places such as factories, schools, and companies. The problem to be solved

[0012] The present invention aims to provide a method and apparatus for searching for and selecting a server for terminal authentication and subscriber information data transmission in a non-public network (NPN). means of solving the problem

[0013] A method for a first stand-alone non-public network (SNPN) that is onboarding a terminal in a wireless communication system according to an embodiment of the present invention to select a server comprises the steps of receiving a Network Access Identifier set as a unique identifier of the terminal from the terminal, selecting a Default Credential Server based on address information of a Default Credential Server included in the Network Access Identifier, and receiving address information of a provisioning server selected from the Default Credential Server from the Default Credential Server.

[0014] The server selection method of the first SNPN above may further include the step of selecting a session management function (SMF) and a user plane function (UPF) corresponding to the provisioning server selected from the basic credential server.

[0015] The server selection method of the first SNPN above may further include the step of transmitting an authentication request containing authentication information for the terminal to the basic credential server, and the step of receiving a response regarding the successful authentication of the terminal from the basic credential server.

[0016] The method for selecting a server of the first SNPN above may further include the step of receiving identification information of the second SNPN to serve the terminal from the basic credential server.

[0017] A method of operation for a terminal to select a server for a first SNPN (stand-alone non-public network) that the terminal is onboarding in a wireless communication system according to an embodiment of the present invention includes the steps of transmitting a Network Access Identifier set as a unique identifier of the terminal to the first SNPN, and performing a terminal authentication procedure with a provisioning server selected by a Default Credential Server corresponding to address information included in the Network Access Identifier.

[0018] The method of operation of the above terminal may further include the step of receiving information regarding a second SNPN to serve the terminal from the provisioning server.

[0019] According to an embodiment, a session management function (SMF) and a user plane function (UPF) corresponding to the provisioning server selected from the basic credential server may be selected.

[0020] A stand-alone non-public network (SNPN) in a wireless communication system according to an embodiment of the present invention, in which a terminal is onboarding and selecting a server, comprises a transceiver and a control unit that controls receiving a Network Access Identifier set as a unique identifier of the terminal from the terminal, selects the Default Credential Server based on address information of the Default Credential Server included in the Network Access Identifier, and controls receiving address information of a provisioning server selected from the Default Credential Server from the Default Credential Server.

[0021] A method of operation of a terminal onboarding to a stand-alone non-public network (SNPN) that selects a server in a wireless communication system according to an embodiment of the present invention includes a transceiver and a control unit that controls the transmission of a Network Access Identifier, which is set as a unique identifier of the terminal, to the first SNPN, and performs a terminal authentication procedure with a provisioning server selected by a Default Credential Server corresponding to address information included in the Network Access Identifier. Effects of the invention

[0022] The method and apparatus according to an embodiment of the present invention can effectively select a server for terminal authentication and subscriber data transmission in a wireless communication system. Brief explanation of the drawing

[0023] FIG. 1 illustrates the structure of a 5G network according to an embodiment of the present invention. FIG. 2 is a diagram showing entities for transmitting a user subscription to a terminal according to an embodiment of the present invention. FIGS. 3a and 3b illustrate a procedure for a terminal according to an embodiment of the present invention to perform UE Onboarding in order to receive user subscriber information. FIG. 4 is a diagram illustrating the structure of a network entity or server according to an embodiment of the present invention. FIG. 5 is a drawing for explaining the structure of a terminal according to an embodiment of the present invention. Specific details for implementing the invention

[0024] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. In this regard, it should be noted that identical components in the attached drawings are indicated by the same reference numerals whenever possible. Furthermore, detailed descriptions of known functions and configurations that may obscure the essence of the present invention will be omitted.

[0025] In describing the embodiments in this specification, technical details that are well known in the technical field to which the present invention belongs and are not directly related to the present invention are omitted. This is intended to convey the essence of the present invention more clearly without obscuring it by omitting unnecessary explanations.

[0026] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0027] The advantages and features of the present invention and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below but can be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components.

[0028] At this time, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0029] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For instance, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order according to their corresponding functions.

[0030] In this embodiment, the term "part" refers to a software or hardware component, such as an FPGA or ASIC, and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to operate one or more processors. Accordingly, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." Furthermore, the components and "parts" may be implemented to operate one or more CPUs within a device or secure multimedia card.

[0031] Hereinafter, the base station is an entity that performs resource allocation of terminals and may be at least one of Node B, BS (Base Station), eNB (eNode B), gNB (gNode B), wireless access unit, base station controller, or a node on the network.

[0032] The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In addition, embodiments of the present disclosure may be applied to other communication systems having a technical background or channel type similar to the embodiments of the present disclosure described below. Furthermore, embodiments of the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0033] Terms used in the following description to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0034] For the convenience of the following explanation, some terms and names defined in the 3GPP (3rd generation partnership project) LTE (long term evolution) standards and / or 3GPP NR (new radio) standards may be used. However, the present invention is not limited by the above terms and names and can be applied in the same way to systems conforming to other standards.

[0035] Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.

[0036] FIG. 1 illustrates the structure of a 5G network according to an embodiment of the present invention. The description of network entities or network nodes constituting the 5G network is as follows.

[0037] Referring to FIG. 1, a wireless communication system constituting a 5G network may include a UE (User Equipment, 100) and a plurality of network entities (101 to 125).

[0038] (R)AN ((Radio) Access Network, 101) is an entity that performs wireless resource allocation for terminals (100), and may be at least one of eNode B, gNode B, Node B, BS (Base Station), NG-RAN (Next Generation Radio Access Network), 5G-AN, wireless access unit, base station controller, or a node on the network.

[0039] The terminal (100) may be at least one of a UE (User Equipment), NG UE (Next Generation UE), MS (Mobile Station), cellular phone, smartphone, or computer. Additionally, the terminal (100) may include a multimedia system capable of performing communication functions.

[0040] Although embodiments of the present disclosure are described below using a 5G system as an example, embodiments of the present disclosure may be applied to other communication systems having a similar technical background. Furthermore, embodiments of the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0041] As wireless communication systems evolve from 4G systems to 5G systems, they define a new core network called NextGen Core (NG Core) or 5GC (5G Core Network). The new Core Network virtualizes all existing network entities (NE) to create network functions (NF). According to one embodiment of the present disclosure, a network function may refer to a network entity, a network component, or a network resource.

[0042] According to one embodiment of the present disclosure, 5GC may include NFs illustrated in FIG. 1. Of course, it is not limited to the example of FIG. 1, and 5GC may include a greater number of NFs than the NFs illustrated in FIG. 1 or a smaller number of NFs.

[0043] According to one embodiment of the present disclosure, the Access and Mobility Management Function (AMF, 109) may be a network function that manages the mobility of a terminal.

[0044] According to one embodiment of the present disclosure, a Session Management Function (SMF, 111) may be a network function that manages a Packet Data Network (PDN) connection provided to a terminal. Here, the PDN connection may be referred to as a Protocol Data Unit (PDU) Session.

[0045] According to one embodiment of the present disclosure, the PCF (Policy Control Function, 121) may be a network function that applies a mobile carrier's service policy, billing policy, and policy for a PDU Session to a terminal.

[0046] According to one embodiment of the present disclosure, Unified Data Management (UDM, 123) may be a network function that stores information about a subscriber.

[0047] According to one embodiment of the present disclosure, an Application Function (AF) may be an application function operated by a terminal manufacturer, a Service Provider, or a PLMN operator. However, even if the AF is not an application function operated by a terminal manufacturer, it may refer to another application function that manages the wireless capability and wireless capability ID of the terminal.

[0048] According to one embodiment of the present disclosure, a Service Communication Proxy (SCP, 113) can act as a proxy server during the delivery of 5G core services and relay communication with appropriate NFs to NFs.

[0049] According to one embodiment of the present disclosure, the Network Exposure Function (117) may be a function that provides information about a terminal to a server outside the 5G network. Additionally, the NEF (117) may provide information necessary for service to the 5G network and store it in the Unified Data Repository (UDR).

[0050] According to one embodiment of the present disclosure, a User Plane Function (UPF, 103) may be a function that performs the role of a gateway for transmitting user data (PDU) to a Data Network (DN, 105).

[0051] According to one embodiment of the present disclosure, a Network Repository Function (NRF, 119) can perform the function of discovering Network Functions (NF).

[0052] According to one embodiment of the present disclosure, an AUSF (Authentication Server Function, 107) can perform terminal authentication in a 3GPP access network and a non-3GPP access network.

[0053] According to one embodiment of the present disclosure, the Network Slice Selection Function (NSSF, 115) can perform the function of selecting a Network Slice Instance provided to a terminal.

[0054] According to one embodiment of the present disclosure, the DN (Data Network, 105) may be a data network in which a terminal (100) transmits and receives data in order to use the services of a network operator or a third party service.

[0055] FIG. 2 is a diagram showing entities for transmitting a user subscription to a terminal according to an embodiment of the present invention.

[0056] Referring to FIG. 2, a wireless communication system for transmitting a user subscription to a terminal may include a UE (200), an O-SNPN (Onboarding Stand-alone Non-Public Network, 210), a DCS (Default Credential Server, 220), a PS (Provisioning Server, 230), and an SNPN network (240) that holds user subscriber information.

[0057] First, it is assumed that the terminal (UE, 200) does not have subscriber information (User Subscription Data) and that the terminal (200) has default UE credentials assigned by the DCS (220). In addition, the DCS (220) may assign a unique UE identifier to the terminal that can uniquely identify the terminal (200).

[0058] O-SNPN (210) can provide User Plane (UP)-based IP Connectivity (UE Onboarding) or Control Plane (CP)-based NAS (Non-Access Stratum) Connectivity (UE Onboarding) to a terminal (200) that does not have subscriber information (User Subscription Data) so that the terminal (200) can download subscriber information. In order to determine whether to provide Onboarding services to the terminal (200), the DCS (220) may receive a request for terminal authentication.

[0059] The DCS (220) can pre-configure a default UE credential and a unique UE identifier for the terminal (200) and store this information. When performing UE Registration for Onboarding from the O-SNPN (210), the DCS (220) may receive a request for authentication for the terminal (200). Here, authentication for the terminal (200) is performed using the default UE credential.

[0060] Additionally, when PS (230) transmits subscriber information to the terminal (200), DCS (220) may receive a request for Authentication / Authorization for the terminal (200) from PS (230) to determine whether the terminal (200) is a terminal that has the authority to receive subscriber information. DCS (220) may be the manufacturer of the terminal (200) or a third party linked to the manufacturer or SNPN network operator.

[0061] PS (230) can receive user subscriber information, such as network credentials and user configuration information, from a network operator and transmit it to a terminal (200).

[0062] PS (230) may exist as a single server with DCS (220), and like DCS (220), it may be a server owned by a third party connected to the manufacturer of the terminal or the SNPN network operator. PS (230) may communicate with DCS (220) for the authentication / authorization of the terminal (200).

[0063] An SNPN network (240) that possesses user subscriber information can transmit user subscriber information to a terminal (200) through a PS (230). At this time, the network operator may have UE identifier information of the terminals to which user subscriber information will be provided.

[0064] FIGS. 3a and 3b illustrate a procedure for a terminal according to an embodiment of the present invention to perform UE Onboarding in order to receive user subscriber information.

[0065] Referring to FIG. 3a, a wireless communication system performing a UE Onboarding procedure may include a UE (300), a 5G-AN (5G Access Network, 310), a 5GC (5G Core Network, 320), a PS (Provisioning Server, 330), a DCS (Default Credential Server, 340), and a serving network (350).

[0066] Here, the 5G-AN (310) performs wireless resource allocation for the UE (300) and transmits system information to the UE (300). Additionally, the 5GC (320) can be implemented as a Stand-alone Non-Public Network (SNPN), and the serving network (350) can be implemented as a network (NPN or PLMN) that holds user subscriber information (network credential and configuration information).

[0067] In step S301, the terminal (300) pre-configures the default UE credential and unique UE identity assigned from the DCS (340). At this time, the default UE credential is set to the terminal (300), but the network credential is not set, and the network credential may be provided to the terminal (300) as part of the onboarding procedure.

[0068] According to an embodiment, if there is an agreement between the terminal manufacturer and the SNPN network, the terminal (300) may have an initial default configuration (e.g., PLMN ID and NIF of the SNPN, S-NSSAI, DNN, etc.).

[0069] The terminal ID assigned by the DCS (340) must uniquely identify the terminal (300). The DCS (340) is likely to be handled by a third party associated with a manufacturer that primarily manufactures IoT devices or a few manufacturers.

[0070] To assign a unique ID to a terminal without a specific standard organization, the terminal ID may include information from the DCS (340). In the present invention, to assign a unique ID to a terminal (300), it is proposed to use a UE ID in the form of a Network Access Identifier (NAI) that includes information from the DCS (340).

[0071] The form of the NAI is “user@realm”, and by including information about the DCS (340) in the realm, the Onboarding Network can determine which of the various DCS servers to select for authentication of the terminal. In particular, since the address of the DCS server can be included in the realm information, the DCS Discovery / Addressing problem can be solved at once.

[0072] In step S303, upon initial access, the terminal (300) can search for and select an O-SNPN (Onboarding SNPN) based on the received Broadcast System Information. At this time, the O-SNPN (Onboarding SNPN) does not necessarily have to be the same as the SNPN having network credentials.

[0073] Since the terminal (300) does not have subscriber information for the corresponding SNPN (320), it can transmit the terminal (300)'s unique UE identity and default UE credential to the SNPN (320) upon Initial Access. The terminal (300) may also transmit additional information, such as an application identifier or a Service Provider Identifier, to the SNPN (320).

[0074] In the present invention, the terminal (300) may use a Network Access Identifier (NAI) containing information of the DCS (340) as the unique UE identity of the terminal (300). The terminal (300) may transmit the NAI containing information of the DCS (340) to the SNPN (320).

[0075] In step S305, the SNPN (320) receives a unique UE identifier in the form of an NAI of the terminal (300) and can search for and select a DCS (340) using realm information included in the NAI. In particular, since the realm information may include URL information of the DCS (340), the SNPN (320) can send a UE Authentication message for terminal authentication to the corresponding DCS (340).

[0076] In addition, since DCS (340) may enter into a contract with a specific SNPN network for the onboarding service of its terminal, SNPN (320) may determine whether to provide connectivity for onboarding to the terminal through realm information included in NAI information.

[0077] In step S307, the SNPN (320) may request authentication regarding whether the terminal (300) can access the network for onboarding purposes by transmitting the terminal's unique UE identity and default UE credential to the DCS (340) managing the terminal (300). The authentication may be performed by selecting either primary authentication or Network Slice Specific Authentication and Authorisation (NSSAA).

[0078] In step S309, the DCS (340) performs authentication of the terminal (300), and if the authentication is successful, it can select a Provisioning Server (330) to receive subscriber information from an SNPN (350) that has subscriber information to be received by the terminal (300) and transmit it to the terminal (300). This involves having a list of SNPN networks that the terminal manufacturer has contracted with and pre-subscribed to, and selecting the most appropriate network among the contracted SNPN networks by considering the type of terminal and the current location, and selecting a PS (330) that can support it. The PS (330) can also select a PS (300) that can support the selected SNPN network from a list of PS servers that have contracted with the manufacturer, just like the SNPN network. According to the embodiment, when there are multiple selected serving networks, priority information may also be included.

[0079] In step S311, the DCS (340) can transmit a Response to the terminal's authentication success, the address information of the selected PS (300), and the ID of the selected serving network (350) (PLMN ID or PLMN ID + NID) to the onboarding network (320).

[0080] In step S313, the onboarding network (320) must select an SMF and a UPF to create a PDU Session that provides the terminal (300) with a restricted data connection accessible only to the selected PS (330). To do this, the onboarding network (320) uses the address of the selected PS received from the DCS (340).

[0081] Referring to FIG. 3b, in step S315, the onboarding network (320) can transmit the address of the selected PS received from the DCS (340) and S-NSSAI / DNN information for creating a PDU Session to the terminal (300). The terminal (300) can create a PDU Session using the received S-NSSAI / DNN information and transmit data to the PS (330) using the address information of the PS (330). Information related to the PS can be updated within the terminal if it differs from the information stored during pre-configuration.

[0082] In step S317, the terminal (300) can create a Configuration PDU Session. The PDU Session is created using S-NSSAI / DNN information received from a well-known or pre-configured S-NSSAI / DNN or DCS (340).

[0083] In steps S319 to S323, subscriber information can be requested from the PS (330) using information pre-configured in the terminal (300) at the application level, or subscriber information can be requested using selected PS address information received from the DCS (340). The PS (330) can request terminal authentication by looking at the realm part of the terminal (300)'s unique UE identifier information and sending the terminal (300)'s default UE credential to the DSC (340). At this time, the terminal (300) can also transmit the serving network ID (PLMN ID or PLMN ID + NID) and serving network priority information received from the DCS (340).

[0084] In step S325, PS (330) can request and receive network credentials for the future SNPN owning the subscription as well as other UE configuration parameters (e.g., PDU session parameters, such as SNSSAI, DNN, URSPs, QoS rules, and other required parameters to access the SNPN and establish a regular PDU session) from the serving network (350).

[0085] In step S327, PS (330) can transmit the data received from the serving network (350) in step S325 to the terminal (300).

[0086] If data is successfully received in step S327, in step S329, the terminal (300) disconnects the configuration PDU Session of the onboarding network (320) and performs deregistration for the onboarding network (320).

[0087] In step S331, the terminal (300) can receive network services by registering with the serving network (350) using the received subscriber information. At this time, the onboarding network (320) and the serving network (350) may be the same or different.

[0088] FIG. 4 is a diagram illustrating the structure of a network entity or server according to an embodiment of the present invention.

[0089] Each of the network entities or servers described with reference to FIGS. 1 to 3 may include the configuration of FIG. 4. For example, structures such as SMF, NEF, AF, etc. may correspond to the structure described in FIG. 4. For example, structures such as PS (Provisioning Server), DCS (Default Credential Server), etc. may correspond to the structure described in FIG. 4.

[0090] Referring to FIG. 4, a network entity or server according to an embodiment of the present disclosure may be composed of a transmitting / receiving unit (410), a memory (420), and a processor (430). According to the communication method of the network entity or server described above, the transmitting / receiving unit (410), the processor (430), and the memory (420) of the network entity or server may operate.

[0091] However, the components of the network entity or server are not limited to the examples described above. For example, the network entity or server may include more or fewer components than those described above. In addition, the transceiver (410), processor (430), and memory (420) may be implemented in the form of a single chip. Furthermore, the processor (430) may include one or more processors.

[0092] The transceiver unit (410) is a collective term for the receiver and the transmitter, and can transmit and receive signals with a base station, a terminal, a network entity, or a server. The signals transmitted and received with the base station, a terminal, a network entity, or a server may include control information and data. To this end, the transceiver unit (410) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver unit (410), and the components of the transceiver unit (410) are not limited to an RF transmitter and an RF receiver.

[0093] Additionally, the transceiver (410) can receive a signal through a wireless channel and output it to a processor (430), and transmit the signal output from the processor (430) through a wireless channel.

[0094] The memory (420) can store programs and data necessary for the operation of a network entity or server. Additionally, the memory (420) can store control information or data included in signals obtained from a network entity or server. The memory (420) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, the memory (420) may not exist separately but may be configured to be included in the processor (430).

[0095] The processor (430) can control a series of processes to enable a network entity or server to operate according to the embodiments of the present disclosure described above. For example, the processor (430) can receive control signals and data signals through the transmitting and receiving unit (410) and process the received control signals and data signals. Additionally, the processor (430) can transmit the processed control signals and data signals through the transmitting and receiving unit (410). There may be multiple processors (430), and the processor (430) can perform component control operations of the network entity or server by executing a program stored in memory (420).

[0096] FIG. 5 is a diagram illustrating the structure of a terminal according to an embodiment of the present invention.

[0097] The terminal described with reference to FIGS. 1 to 3 may correspond to the terminal of FIG. 5. Referring to FIG. 5, the terminal may be composed of a transceiver (510), a memory (520), and a processor (530). The transceiver (510), the processor (530), and the memory (520) of the terminal may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. In addition, the transceiver (510), the processor (530), and the memory (520) may be implemented in the form of a single chip. Furthermore, the processor (530) may include one or more processors.

[0098] The transceiver (510) is a collective term for the receiver and the transmitter of a terminal, and can transmit and receive signals with a base station, NF, server, or other terminal. The signals transmitted and received with a base station, NF, server, or other terminal may include control information and data. To this end, the transceiver (510) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (510), and the components of the transceiver (510) are not limited to an RF transmitter and an RF receiver.

[0099] Additionally, the transceiver (510) can receive a signal through a wireless channel and output it to a processor (530), and transmit the signal output from the processor (530) through a wireless channel.

[0100] The memory (520) can store programs and data necessary for the operation of the terminal. Additionally, the memory (520) can store control information or data included in signals obtained from the terminal. The memory (520) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, the memory (520) may not exist separately but may be configured to be included in the processor (530).

[0101] The processor (530) can control a series of processes to enable the terminal to operate according to the embodiments of the present disclosure described above. For example, the processor (530) can receive a control signal and a data signal through the transceiver (510) and process the received control signal and data signal. Additionally, the processor (530) can transmit the processed control signal and data signal through the transceiver (510). There may be multiple processors (530), and the processor (530) can perform component control operations of the terminal by executing a program stored in the memory (520).

[0102] Methods according to the claims or embodiments described in the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0103] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.

[0104] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), magnetic disc storage devices, CD-ROM (Compact Disc-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0105] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0106] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0107] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, parts of one embodiment of the present disclosure and another embodiment may be combined to operate a base station and a terminal. Additionally, the embodiments of the present disclosure are applicable to other communication systems, and other variations based on the technical concept of the embodiments may also be implemented.

Claims

Claim 1 A method for operating a stand-alone non-public network (SNPN) in a wireless communication system in which a terminal is onboarding, comprising: receiving a terminal unique identifier configured in the form of a network access identifier from the terminal; selecting a default credential server based on information included in the realm portion of the terminal unique identifier; and receiving address information of a provisioning server from the default credential server during the authentication procedure of the terminal. Claim 2 A method according to claim 1, further comprising the step of selecting a session management function (SMF) and a user plane function (UPF) corresponding to the provisioning server selected from the basic credential server. Claim 3 A method according to claim 1, further comprising: a step of transmitting an authentication request including authentication information for the terminal to the basic credential server; and a step of receiving a response regarding the successful authentication of the terminal from the basic credential server. Claim 4 A method according to claim 1, characterized in that the information included in the realm portion of the terminal unique identifier corresponds to the address of the basic credential server. Claim 5 A method according to claim 1, characterized in that when the authentication procedure of the terminal is successful, the provisioning server is selected by the basic credential server. Claim 6 A method for operating a terminal that is onboarding to a stand-alone non-public network (SNPN) in a wireless communication system, characterized by comprising: a step of transmitting a terminal unique identifier configured in the form of a network access identifier to the SNPN; and a step of performing a terminal authentication procedure with a provisioning server selected by a default credential server corresponding to information included in the realm portion of the terminal unique identifier. Claim 7 A method according to claim 6, characterized in that the information included in the realm portion of the terminal unique identifier corresponds to the address of the basic credential server. Claim 8 A method according to claim 6, characterized in that when the authentication procedure of the terminal is successful, the provisioning server is selected by the basic credential server. Claim 9 A stand-alone non-public network (SNPN) in a wireless communication system in which a terminal is onboarding comprises: a transceiver; and a control unit connected to the transceiver and controlling the transceiver, wherein the control unit controls the reception of a terminal unique identifier configured in the form of a network access identifier from the terminal, selects a default credential server based on information included in the realm portion of the terminal unique identifier, and controls the reception of address information of a provisioning server from the default credential server during the authentication procedure of the terminal. Claim 10 SNPN according to claim 9, wherein the control unit selects a session management function (SMF) and a user plane function (UPF) corresponding to the provisioning server selected from the basic credential server. Claim 11 SNPN according to claim 9, wherein the control unit controls the transmission of an authentication request including authentication information for the terminal to the basic credential server, and controls the reception of a response regarding the successful authentication of the terminal from the basic credential server. Claim 12 SNPN according to claim 9, characterized in that the information included in the realm portion of the terminal unique identifier corresponds to the address of the basic credential server. Claim 13 SNPN according to claim 9, characterized in that when the authentication procedure of the terminal is successful, the provisioning server is selected by the basic credential server. Claim 14 A terminal that is onboarding to a stand-alone non-public network (SNPN) in a wireless communication system, comprising: a transceiver; and a control unit connected to the transceiver and controlling the transceiver, wherein the control unit controls the transmission of a terminal unique identifier configured in the form of a network access identifier to the SNPN and performs a terminal authentication procedure with a provisioning server selected by a default credential server corresponding to information included in the realm portion of the terminal unique identifier. Claim 15 A terminal according to claim 14, characterized in that the information included in the realm portion of the terminal unique identifier corresponds to the address of the basic credential server. Claim 16 A terminal according to claim 14, characterized in that when the authentication procedure of the terminal is successful, the provisioning server is selected by the basic credential server.

Images