Method and apparatus for operating a terminal in a wireless communication system

Abstract

The present disclosure may provide a method for operating a terminal in a wireless communication system, the method including the steps of: a terminal supporting an SNPN connection making a connection to a second SNPN based on a qualification of a first SNPN as a qualification holder; recognizing a failure of the connection to the second SNPN; and setting the validity of the second SNPN in a subscription data list to an invalid state based on the connection failure.

Description

[Technical field]

[0001] The present invention relates to a method and apparatus for operating a terminal in a wireless communication system, and more particularly, to a method for storing and processing SNPN configuration information in a list of subscribe data when a terminal supporting enhanced non public network (eNPN) authenticates via a standalone NPN (SNPN) for which it does not have credentials. [Background technology]

[0002] Wireless access systems have been widely deployed to provide various communication services such as voice and data. In general, wireless access systems are multiple access systems that can support communication with multiple users by sharing available system resources (such as bandwidth and transmission power). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency division multiple access (SC-FDMA) systems.

[0003] In particular, as many communication devices require large communication capacity, enhanced mobile broadband (eMBB) communication technology, which is improved over existing radio access technology (RAT), has been proposed. In addition, not only massive machine type communications (mMTC) that provides various services anytime and anywhere by connecting multiple devices and things, but also communication systems that consider reliability and latency sensitive services / user equipment (UE) have been proposed. Various technical configurations have been proposed for this purpose. Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure may provide a method and apparatus for operating a terminal in a wireless communication system.

[0005] The present disclosure may provide a method and apparatus for a terminal supporting an SNPN in a wireless communication system to connect to the SNPN via a credential holder (CH).

[0006] The present disclosure may provide a method and apparatus for storing and processing SNPN setting information in a subscription data list upon authentication failure for an SNPN connection based on a credential holder's credential in a wireless communication system.

[0007] The present disclosure can provide a method and apparatus that uses a separate counter when connecting to an SNPN based on a license holder's license in a wireless communication system.

[0008] The technical problems to be solved by the present disclosure are not limited to those described above, and other technical problems not described above can be considered by a person having ordinary skill in the art to which the technical configuration of the present disclosure is applied from the embodiments of the present disclosure described below. [Means for solving the problem]

[0009] As an example of the present disclosure, a terminal operation method in a wireless communication system may include a step in which a terminal supporting a standalone non public network (SNPN) connection, as a credential holder, connects to a second SNPN based on credentials of a first SNPN, a step of recognizing a failure of connection to the second SNPN, and a step of setting the validity of the first SNPN in a list of subscribe data to an invalid state based on the connection failure.

[0010] As an example of the present disclosure, a terminal operating in a wireless communication system includes at least one transceiver, at least one processor, and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform a specific operation, wherein the specific operation includes a terminal supporting a standalone non public network (SNPN) connection connecting to a second SNPN based on credentials of a first SNPN as a credential holder, recognizing a failure of connection to the second SNPN, and setting the validity of the first SNPN in a list of subscribe data to an invalid state based on the connection failure.

[0011] As an example of the present disclosure, a method for operating a network in a wireless communication system, comprising:

[0012] The method includes steps of receiving a registration request message from a terminal and transmitting a registration rejection message to the terminal, wherein the terminal is a terminal that supports a standalone non public network (SNPN) connection, and the terminal, as a credential holder, connects to a second SNPN, which is a network, based on the credentials of a first SNPN, recognizes a failure to connect to the second SNPN based on the registration rejection message, and sets the validity of the first SNPN in a list of subscribe data to an invalid state based on the connection failure.

[0013] As an example of the present disclosure, a network operating in a wireless communication system includes at least one transceiver, at least one processor, and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform a specific operation, the specific operation controlling the transceiver to receive a registration request message from a terminal and controlling the transceiver to transmit a registration rejection message to the terminal, the terminal being a terminal supporting a standalone non public network (SNPN) connection, the terminal being a credential holder and connecting to a second SNPN, which is a network, based on credentials of a first SNPN, recognizing a failure to connect to the second SNPN based on the registration rejection message, and setting the validity of the first SNPN in a list of subscribe dates to an invalid state based on the connection failure.

[0014] Also, as an example of the present disclosure, in an apparatus including at least one memory and at least one processor functionally coupled to the at least one memory, the at least one processor can support a connection to the SNPN, while the apparatus, as a credential holder, connects to a second SNPN based on credentials of a first SNPN, recognizes a failure to connect to the second SNPN, and sets the validity of the first SNPN in a list of subscribe dates to an invalid state based on the connection failure.

[0015] Also, as an example of the present disclosure, a non-transitory computer-readable medium storing at least one instruction includes at least one instruction executable by a processor, the at least one instruction being capable of connecting to a second SNPN based on credentials of a first SNPN as a credential holder, recognizing a failure to connect to the second SNPN, and setting the validity of the first SNPN in a list of subscribe dates to an invalid state based on the connection failure.

[0016] In addition, the following items are commonly applicable:

[0017] Also, as an example of the present disclosure, the method may further include a step of checking whether the terminal supports an SNPN connection using the qualification of the qualification holder.

[0018] Also, as an example of the present disclosure, if the terminal supports an SNPN connection using a credential of a credential holder, the terminal may connect to a second SNPN based on the credential of a first SNPN.

[0019] Also, as an example of the present disclosure, if the terminal does not support an SNPN connection using the credentials of a credential holder, the terminal may perform an SNPN connection based on the credentials that the terminal has.

[0020] Also, as an example of the present disclosure, when a terminal connects to a third SNPN based on the qualifications for the third SNPN that the terminal has and recognizes that the connection to the third SNPN has failed, the terminal can set the validity of the third SNPN in the subscription data list to an invalid state.

[0021] Also, as an example of the present disclosure, when the terminal receives a first authentication rejection message based on a connection to a second SNPN, a first counter is incremented, and when the first counter reaches a first value, the terminal can recognize a failure to connect to the second SNPN.

[0022] Also, as an example of the present disclosure, when the terminal receives a second authentication rejection message based on a connection to a third SNPN, a second counter is incremented, and when the second counter reaches a second value, the terminal can recognize a failure to connect to the third SNPN.

[0023] Also, as an example of the present disclosure, the first counter and the second counter can be set to different counters.

[0024] Also, as an example of the present disclosure, the validity of the first SNPN may be maintained until the power is turned on again or before the subscription data list is updated. Effect of the Invention

[0025] Advantageously, the present disclosure provides a method and apparatus for operating a terminal in a wireless communication system.

[0026] The present disclosure has an effect of providing a method in which a terminal supporting an SNPN in a wireless communication system connects to the SNPN by using the credentials of a credential holder (CH).

[0027] The present disclosure has an advantage of recognizing the SNPN for which authentication failure has occurred by storing and processing SNPN setting information in a subscription data list when authentication for an SNPN connection fails based on the qualification of a qualification holder in a wireless communication system.

[0028] The present disclosure has an advantage of preventing unnecessary signaling from occurring by a method for storing and processing SNPN setting information in a subscription data list when authentication for an SNPN connection fails based on the entitlement of a license holder in a wireless communication system.

[0029] The present disclosure has an advantage of providing a method for using a separate counter when connecting to an SNPN based on a license holder's license in a wireless communication system.

[0030] The effects obtained in the embodiments of the present disclosure are not limited to the effects described above, and other effects not described above can be clearly derived and understood by a person having ordinary skill in the art to which the technical configuration of the present disclosure is applied from the following description of the embodiments of the present disclosure. In other words, unintended effects by implementing the configuration described in the present disclosure can also be derived from the embodiments of the present disclosure by a person having ordinary skill in the art. [Brief description of the drawings]

[0031] The drawings attached below are for aiding understanding of the present disclosure, and together with the detailed description, can provide examples of the present disclosure. However, the technical features of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing can be combined with each other to form a new embodiment. Reference numerals in each drawing can refer to structural elements.

[0032] [Figure 1] FIG. 2 is a diagram showing various reference points. [Diagram 2]FIG. 1 is a diagram illustrating an example of a network structure of an evolved universal terrestrial radio access network (E-UTRAN) applicable to the present disclosure. [Diagram 3] FIG. 1 is a diagram illustrating an example of a general E-UTRAN and EPC (evolved packet core) architecture. [Figure 4] FIG. 1 is a diagram illustrating an example of a radio interface protocol structure in a control plane between a user equipment (UE) and an evolved node B (eNB). [Diagram 5] A diagram showing an example of the structure of a radio interface protocol in the user plane between a UE and an eNB. [Figure 6] FIG. 1 is a diagram illustrating an example of a typical NR (new radio)-RAN (radio access network) architecture. [Figure 7] This is a diagram showing an example of functional separation between a general NG-RAN and a 5GC (5th generation core). [Figure 8] FIG. 1 is a diagram illustrating an example of a general architecture of a 5G (5th generation) system. [Figure 9] FIG. 1 is a diagram illustrating an example of a wireless device to which the present disclosure can be applied. [Figure 10] FIG. 13 is a diagram showing another example of a wireless device to which the present disclosure can be applied. [Figure 11] FIG. 1 is a diagram showing an example of a portable device to which the present disclosure is applied; [Figure 12] FIG. 13 is a diagram showing a method in which a terminal applied to the present disclosure connects to an SNPN. [Figure 13] FIG. 13 is a diagram showing a method in which a terminal applied to the present disclosure connects to an SNPN. [Figure 14] A diagram showing a method in which a terminal applied to the present disclosure performs credential verification based on an external entity. [Figure 15]FIG. 1 illustrates a method for performing authentication for SNPN connections based on a credential holder that is applicable to the present disclosure. [Figure 16] FIG. 13 is a diagram illustrating a method in which a terminal applicable to the present disclosure connects to an SNPN. [Figure 17] FIG. 13 is a diagram illustrating a method in which a terminal applicable to the present disclosure connects to an SNPN. [Figure 18] FIG. 2 illustrates a terminal operation method applied to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] The following examples combine the components and features of the present disclosure in a specific form. Each component or feature is considered to be optional unless otherwise specified. Each component or feature may be implemented in a form not combined with other components or features. Also, some components and / or features may be combined to configure an embodiment of the present invention. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment.

[0034] In the description of the drawings, procedures or steps that may make the gist of the present disclosure unclear are not described, and procedures or steps that can be understood by those skilled in the art are not described.

[0035] Throughout the specification, when a part "comprising" or "including" a certain element, this means that the part may further include other elements, not excluding other elements, unless otherwise specified to the contrary. In addition, the terms "part," "unit," "module," and the like described in the specification mean a unit that processes at least one function or operation, which can be realized by hardware, software, or a combination of hardware and software. In addition, the words "a" or "an," "one," "the," and similar related words can be used in the context of describing this disclosure (particularly in the context of the claims below) to include both the singular and the plural, unless otherwise indicated in the specification or clearly refuted by the context.

[0036] In this specification, the embodiment of the present invention has been described with a focus on the data transmission / reception relationship between the base station and the mobile station. Here, the base station is meant as a terminal node of the network that directly communicates with the mobile station. Certain operations described in this document as being performed by the base station may also be performed by an upper node of the base station in some cases.

[0037] That is, various operations performed for communication with a mobile station in a network consisting of a number of network nodes including a base station may be performed by the base station or other network nodes other than the base station. Here, the term "base station" may be replaced with other terms such as fixed station, Node B, eNB (eNode B), gNB (gNode B), ng-eNB, advanced base station (ABS), or access point.

[0038] In addition, in the embodiments of the present disclosure, the term "terminal" may be replaced with terms such as user equipment (UE), mobile station (MS), subscriber station (SS), mobile subscriber station (MSS), mobile terminal, or advanced mobile station (AMS).

[0039] Also, the transmitting end refers to a fixed and / or mobile node that provides a data service or a voice service, and the receiving end refers to a fixed and / or mobile node that receives the data service or the voice service. Thus, in the case of an uplink, a mobile station can be the transmitting end and a base station can be the receiving end. Similarly, in the case of a downlink, a mobile station can be the receiving end and a base station can be the transmitting end.

[0040] An embodiment of the present disclosure may be supported by standard documents disclosed in at least one of wireless access systems, such as an IEEE 802.xx system, a 3GPP (registered trademark) (3rd Generation Partnership Project) system, a 3GPP LTE (Long Term Evolution) system, a 3GPP 5G (5th generation) NR (New Radio) system, and a 3GPP2 system. In particular, an embodiment of the present disclosure may be supported by 3GPP TS (technical specification) 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.321, and 3GPP TS 38.331 documents.

[0041] In addition, the embodiments of the present disclosure may be applied to other wireless access systems and are not limited to the above-mentioned systems. For example, the embodiments of the present disclosure may be applied to systems applied after the 3GPP 5G NR system and are not limited to a specific system.

[0042] That is, steps or parts of the embodiments of the present invention that are obvious but not described may be described with reference to the above documents. Also, all terms disclosed in this document may be explained by the above standard documents.

[0043] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, and is not intended to represent the only embodiments in which the technical configuration of the present disclosure can be implemented.

[0044] Furthermore, specific terms used in the embodiments of the present disclosure are provided to aid in understanding the present disclosure, and the use of such specific terms may be modified in different forms without departing from the technical spirit of the present disclosure.

[0045] The following techniques can be applied to various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA).

[0046] For clarity of explanation, the following description will be based on 3GPP communication systems (e.g., LTE, NR, etc.), but the technical idea of ​​the present invention is not limited thereto. LTE may refer to technology after 3GPP TS 36.xxx Release 8. In particular, LTE technology after 3GPP TS 36.xxx Release 10 may be called LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 may be called LTE-A pro. 3GPP NR may refer to technology after TS 38.xxx Release 15. 3GPP 6G may refer to technology after TS Release 17 and / or Release 18. "xxx" refers to the detailed number of a standard document. LTE / NR / 6G may be collectively referred to as a 3GPP system.

[0047] For background art, terms, abbreviations, etc. used in this disclosure, reference may be made to matters described in standard documents published prior to the present invention. For example, reference may be made to 36.xxx and 38.xxx standard documents.

[0048] The terms used in this document are defined as follows:

[0049] IMS (IP Multimedia Subsystem or IP Multimedia Core Network Subsystem): An architectural framework for providing standardization for delivering voice or other multimedia services over IP.

[0050] -UMTS (Universal Mobile Telecommunications System): A third generation mobile communication technology developed by 3GPP and based on GSM (Global System for Mobile Communication).

[0051] - EPS (Evolved Packet System): A network system consisting of EPC (Evolved Packet Core), an IP (Internet Protocol) based packet switched core network, and access networks such as LTE and UTRAN. It is an evolved form of UMTS.

[0052] -NodeB: A base station in a UMTS network. It is installed outdoors and has a coverage area on a macro cell scale.

[0053] -eNodeB: The base station of the EPS network. It is installed outdoors and has a macro cell-scale coverage.

[0054] -Home NodeB: A base station of a UMTS network, installed indoors, with a coverage of microcell scale

[0055] -Home eNode: A base station of the EPS network, installed indoors, with coverage on a microcell scale.

[0056] -User Equipment: User equipment. The terminal may be referred to as a terminal, ME (Mobile Equipment), MS (Mobile Station), etc. Also, the terminal may be a portable device such as a notebook computer, a mobile phone, a PDA (Personal Digital Assistant), a smartphone, a multimedia device, etc., or a non-portable device such as a PC (Personal Computer) or a vehicle-mounted device. In MTC-related content, the term terminal or terminal may refer to an MTC terminal.

[0057] -MTC (Machine Type Communication): Communication conducted by machines without human intervention. It is also called M2M (Machine to Machine) communication.

[0058] -MTC terminal (MTC UE or MTC device or MTC equipment): A terminal (e.g., a vending machine, a meter reader, etc.) having a function of communicating via a mobile communication network (e.g., communicating with an MTC server via a PLMN) and performing an MTC function

[0059] -RAN (Radio Access Network): A unit in a 3GPP network that includes Node B, RNC (Radio Network Controller) that controls it, and eNodeB. It exists at the end of the terminal and provides a connection to the core network.

[0060] -HLR (Home Location Register) / HSS (Home Subscriber Server): A database that contains subscriber information in a 3GPP network. The HSS can perform functions such as configuration storage, identity management, and user state storage.

[0061] - PLMN (Public Land Mobile Network): A network configured for the purpose of providing mobile communication services to individuals. It can be configured by operator.

[0062] - NAS (Non-Access Stratum): A functional layer for transmitting and receiving signaling and traffic messages between a terminal and a core network in the UMTS and EPS protocol stack. Its main function is to support terminal mobility and to support session management procedures that establish and maintain IP connections between the terminal and the PDN GW.

[0063] -SCEF (Service Capability Exposure Function): An entity within the 3GPP architecture for service capability exposure that provides a means for securely exposing services and capabilities provided by a 3GPP network interface.

[0064] -MME (Mobility Management Entity): A network node of an EPS network that performs mobility management and session management functions.

[0065] - PDN-GW (Packet Data Network Gateway): A network node of the EPS network that performs UE IP address allocation, packet screening and filtering, and charging data collection functions.

[0066] -Serving GW (Serving Gateway): A network node of an EPS network that performs functions such as mobility anchor, packet routing, idle mode packet buffering, and triggering paging for UEs of MME

[0067] - PCRF (Policy and Charging Rule Function): An EPS network node that makes policy decisions to dynamically apply differentiated QoS and charging policies for each service flow.

[0068] -OMA DM (Open Mobile Alliance Device Management): A protocol designed for managing mobile devices such as mobile phones, PDAs, and portable computers, and performs functions such as device configuration, firmware upgrades, and error reports.

[0069] -OAM (Operation, Administration and Maintenance): A set of network management functions that provide network fault indication, performance information, and data and diagnostic functions.

[0070] -PDN (Packet Data Network): A network in which servers (e.g., MMS Server, WAP Server, etc.) that support specific services are located.

[0071] -PDN connection: Connection from a terminal to a PDN, i.e., the association (connection) between a terminal represented by an IP address and a PDN represented by an APN

[0072] -EMM (EPS Mobility Management): A sub-layer of the NAS layer, EMM can be in an "EMM-Registered" or "EMM-Deregistered" state depending on whether the UE is network attached or detached.

[0073] - EMM Connection Management (ECM) connection: A signaling connection established between a UE and an MME for exchanging NAS messages. An ECM connection is a logical connection consisting of an RRC connection between a UE and an eNB and an S1 signaling connection between the eNB and an MME. When an ECM connection is established / terminated, the RRC connection and the S1 signaling connection are similarly established / terminated. An established ECM connection means that the UE has an RRC connection established with an eNB, and that the MME has an S1 signaling connection established with the eNB. Depending on whether a NAS signaling connection, i.e., an ECM connection, is established, the ECM may have an "ECM-Connected" or "ECM-Idle" state.

[0074] -AS (Access-Stratum): Includes a protocol stack between the UE and the wireless (or access) network, and is responsible for transmitting data and network control signals.

[0075] -NAS configuration MO (Management Object): MO (Management Object) used in the process of setting parameters related to NAS functionality in the UE.

[0076] -PDN (Packet Data Network): A network in which servers that support specific services (e.g., MMS (Multimedia Messaging Service) servers, WAP (Wireless Application Protocol) servers, etc.) are located.

[0077] -PDN connection: A logical connection between a UE and a PDN, represented by one IP address (one IPv4 address and / or one IPv6 prefix).

[0078] -APN (Access Point Name): A string that indicates or distinguishes a PDN. To connect to a requested service or network, a specific P-GW must be passed through, and this P-GW is a name (string) predefined in the network to be able to find it (for example, internet.mmc012.mcc345.gprs).

[0079] -ANDSF (Access Network Discovery and Selection Function): Provides a policy that allows a UE to discover and select available connections (access) on a per-user basis as a network entity.

[0080] -EPC path (or infrastructure data path): User plane communication path via EPC

[0081] -E-RAB (E-UTRAN Radio Access Bearer): refers to the concatenation of an S1 bearer and a corresponding data radio bearer. If an E-RAB exists, there is a one-to-one mapping between the E-RAB and the EPS bearer of the NAS.

[0082] -GTP (GPRS Tunneling Protocol): A group of IP-based communication protocols used to carry general packet radio service (GPRS) in GSM, UMTS and LTE networks. Within the 3GPP architecture, GTP and proxy mobile IPv6-based interfaces are specified on various interface points. GTP can be decomposed into several protocols (e.g., GTP-C, GTP-U and GTP'). GTP-C is used within the GPRS core network for signaling between the Gateway GPRS Support Node (GGSN) and the Serving GPRS Support Node (SGSN). GTP-C allows the SGSN to activate a session for a user (e.g., PDN context activation), deactivate the same session, adjust the quality of service parameters, or update a session for a subscriber that has just been activated from another SGSN. GTP-U is used to carry user data within the GPRS core network and between radio access networks and core networks.

[0083] Hereinafter, the present specification will be described based on the terms defined above.

[0084] The three main requirement areas for 5G include (1) the Enhanced Mobile Broadband (eMBB) area, (2) the massive Machine Type Communication (mMTC) area, and (3) the Ultra-reliable and Low Latency Communications (URLLC) area.

[0085] Some use cases may require multiple areas for optimization, while others may only focus on one key performance indicator (KPI). 5G is here to support these diverse use cases in a reliable and flexible way.

[0086] 5G System Architecture Applicable to This Disclosure

[0087] The 5G system is an advanced technology from the 4th generation LTE mobile communication technology, and is an extension technology of LTE (Long Term Evolution) and supports eLTE (extended LTE), non-3GPP (e.g., WLAN) access, etc., based on the evolution or clean state structure of the existing mobile communication network.

[0088] The 5G system is defined as a service platform, and the interaction between network functions (NFs) in the architecture for the 5G system can be expressed in the following two ways:

[0089] Reference point representation: Indicates interoperation between NF services within an NF described by a point-to-point reference point (e.g., N11) between two NFs (e.g., AMF and SMF).

[0090] Service-based Representation: A network function (e.g., AMF) in the control plane (CP) allows other authorized network functions to access its services. This representation also includes point-to-point reference points, if necessary.

[0091] 3GPP system in general

[0092] FIG. 1 shows various reference points.

[0093] Although the example network structure in FIG. 1 shows that the SGW and the PDN GW are configured as separate gateways, the two gateways may also be realized by a single gateway configuration option.

[0094] The MME is an element that performs signaling and control functions to support UE access to network connection, network resource allocation, tracking, paging, roaming, handover, etc. The MME controls control plane functions related to subscriber and session management. The MME manages a number of eNBs and performs signaling for selection of a conventional gateway for handover to another 2G / 3G network. The MME also performs functions such as security procedures, terminal-to-network session handling, and idle terminal location management.

[0095] The SGSN handles all packet data such as user mobility management and authentication to other 3GPP networks (eg, GPRS networks).

[0096] The ePDG acts as a security node for untrusted non-3GPP networks (eg, I-WLAN, WiFi hotspots, etc.).

[0097] As described with reference to FIG. 1, a UE having IP capability can access an IP service network (e.g., IMS) provided by a carrier (i.e., operator) via various elements in the EPC, not only in 3GPP access but also in non-3GPP access infrastructures.

[0098] Also, for example, a reference point such as S1-U or S1-MME can connect two functions existing in different functional entities. In the 3GPP system, a reference point is defined as a conceptual link connecting two functions existing in different functional entities of E-UTRAN and EPC. Table 1 below summarizes the reference points shown in FIG. 1. In addition to the examples in Table 1, various reference points may exist depending on the network structure.

[0099] [Table 1]

[0100] Among the reference points shown in Figure 1, S2a and S2b correspond to non-3GPP interfaces. S2a is a reference point that provides the user plane with related control and mobility support between trusted non-3GPP access and PDN GW. S2b is a reference point that provides the user plane with related control and mobility support between ePDG and PDN GW.

[0101] FIG. 2 is a diagram illustrating an example of a network structure of an evolved universal terrestrial radio access network (E-UTRAN) applicable to the present disclosure.

[0102] The E-UTRAN system is an evolved system from the existing UTRAN system, and may be, for example, a 3GPP LTE / LTE-A system. Communication networks are widely deployed to provide various communication services, such as voice (e.g., Voice over Internet Protocol (VoIP)) over IMS and packet data.

[0103] 2, the E-UMTS network includes an E-UTRAN, an EPC, and one or more UEs. The E-UTRAN is composed of eNBs that provide control plane and user plane protocols to the UEs, and the eNBs are connected via an X2 interface.

[0104] The X2 user plane interface (X2-U) is defined between eNBs. The X2-U interface provides non-guaranteed delivery of user plane packet data units (PDUs). The X2 control plane interface (X2-CP) is defined between two adjacent eNBs. The X2-CP performs functions such as context transfer between eNBs, control of user plane tunnels between source and target eNBs, transfer of handover-related messages, and uplink load management.

[0105] The eNB is connected to a terminal via a radio interface and is connected to an evolved packet core (EPC) via an S1 interface.

[0106] The S1 user plane interface (S1-U) is defined between the eNB and the serving gateway (S-GW). The S1 control plane interface (S1-MME) is defined between the eNB and the mobility management entity (MME). The S1 interface performs evolved packet system (EPS) bearer service management functions, non-access stratum (NAS) signaling transport functions, network sharing, MME load balancing functions, etc. The S1 interface supports many-to-many-relation between the eNB and the MME / S-GW.

[0107] The MME can perform various functions such as NAS signaling security, Access Stratum (AS) security control, signaling between Core Network (CN) nodes (Inter-CN) to support mobility between 3GPP access networks, IDLE mode UE reachability (including execution and control of paging retransmission), Tracking Area Identity (TAI) management (for idle and active mode terminals), PDN GW and SGW selection, MME selection for handover where the MME is changed, SGSN selection for handover to a 2G or 3G 3GPP access network, roaming, authentication, bearer management functions including dedicated bearer establishment, and support for Public Warning System (PWS) (including Earthquake Vision and Tsunami Warning System (ETWS) and Commercial Mobile Alert System (CMAS)) message transmission.

[0108] FIG. 3 is a diagram illustrating an example of a general E-UTRAN and evolved packet core (EPC) architecture.

[0109] As shown in Fig. 3, while a Radio Resource Control (RRC) connection is active, the eNB can perform functions such as routing to a gateway, scheduling and transmission of paging messages, scheduling and transmission of a broadcast channel (BCH), dynamic allocation of resources to UEs in uplink and downlink, configuration and provisioning for eNB measurements, radio bearer control, radio admission control, and connected mobility control. In the EPC, functions such as paging status, LTE_IDLE state management, user plane encryption, SAE bearer control, NAS signaling encryption, and integrity protection can be performed.

[0110] Annex J of 3GPP TR 23.799 shows various architectures combining 5G and 4G, and 3GPP TS 23.501 shows architectures using NR and NGC.

[0111] FIG. 4 is a diagram showing an example of a radio interface protocol structure in a control plane between a UE (User equipment) and an eNB (Evolved Node B), and FIG. 5 is a diagram showing an example of a radio interface protocol structure in a user plane between the UE and an eNB.

[0112] The radio interface protocol is based on the 3GPP radio access network standard, and is horizontally composed of a physical layer, a data link layer, and a network layer, and vertically divided into a user plane for transmitting data information and a control plane for transmitting signaling.

[0113] The protocol layers can be divided into L1 (Layer 1, 1st layer), L2 (Layer 2, 2nd layer), and L3 (Layer 3, 3rd layer) based on the lower three layers of the Open System Interconnection (OSI) reference model widely known in communication systems.

[0114] The following describes each layer of the radio protocol in the control plane shown in FIG. 4 and the radio protocol in the user plane shown in FIG.

[0115] The first layer, the physical layer, provides an information transfer service using a physical channel. The physical layer is connected to the higher medium access control layer via a transport channel, and data is transferred between the medium access control layer and the physical layer via the transport channel. Data is transferred between different physical layers, i.e., between the physical layers of the transmitting side and the receiving side, via the physical channel.

[0116] A physical channel is composed of multiple subframes on the time axis and multiple subcarriers on the frequency axis. Here, one subframe is composed of multiple OFDM symbols and multiple subcarriers on the time axis. One subframe is composed of multiple resource blocks, and one resource block is composed of multiple OFDM symbols and multiple subcarriers. A transmission time interval (TTI), which is a unit time for transmitting data, is 1 ms, which corresponds to one subframe.

[0117] According to 3GPP LTE, the physical channels existing in the physical layers of the transmitting side and the receiving side can be divided into data channels PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), and control channels PDCCH (Physical Downlink Control Channel), PCFICH (Physical Control Format Indicator Channel), PHICH (Physical Hybrid-ARQ Indicator Channel), and PUCCH (Physical Uplink Control Channel), etc.

[0118] There are various layers in the second layer. First, the Medium Access Control (MAC) layer in the second layer maps various logical channels to various transmission channels and also maps various logical channels to one transmission channel, performing logical channel multiplexing. The MAC layer is connected to the upper layer, the RLC layer, through logical channels, and the logical channels are largely divided into control channels that transmit information on the control plane and traffic channels that transmit information on the user plane according to the type of information being transmitted.

[0119] The Radio Link Control (RLC) layer of the second layer performs segmentation and concatenation of data received from a higher layer and adjusts the data size so that the lower layer is suitable for transmitting the data over the radio section.

[0120] The Packet Data Convergence Protocol (PDCP) layer in the second layer performs a header compression function to reduce the size of IP packet headers, which are relatively large and contain unnecessary control information, in order to efficiently transmit IP packets such as IPv4 and IPv6 in wireless sections with small bandwidth. In addition, in the LTE system, the PDCP layer also performs a security function, which consists of ciphering to prevent third parties from eavesdropping on data and integrity protection to prevent third parties from manipulating data.

[0121] The Radio Resource Control (RRC) layer, located at the top of Layer 3, is defined only in the control plane and is responsible for controlling logical channels, transport channels, and physical channels in relation to the configuration, reconfiguration, and release of Radio Bearers (RBs). Here, RB refers to the service provided by Layer 2 for data transmission between UE and E-UTRAN.

[0122] When an RRC connection is established between the RRC of the UE and the RRC layer of the radio network, the UE is in an RRC connected mode; otherwise, the UE is in an RRC idle mode.

[0123] The RRC state of the UE and the RRC connection method will be described below. The RRC state means whether the RRC of the UE is logically connected to the RRC of the E-UTRAN. If it is connected, it is called the RRC_CONNECTED state, and if it is not connected, it is called the RRC_IDLE state. Since the UE in the RRC_CONNECTED state has an RRC connection, the E-UTRAN can grasp the existence of the UE in cell units. Therefore, the UE can be effectively controlled. On the other hand, the E-UTRAN cannot grasp the existence of the UE in the RRC_IDLE state, and the core network manages it in TA (Tracking Area) units, which are larger area units than cells. That is, the UE in the RRC_IDLE state is only grasped in area units larger than cells, and the UE must transition to the RRC_CONNECTED state to receive normal mobile communication services such as voice and data. Each TA is distinguished by a Tracking Area Identity (TAI). The UE can configure the TAI via a tracking area code (TAC), which is information broadcast in a cell.

[0124] When a user first turns on the UE, the UE first searches for a suitable cell, then establishes an RRC connection with the cell and registers the UE information in the core network. After that, the UE remains in the RRC_IDLE state. A UE that remains in the RRC_IDLE state (re)selects a cell as necessary and considers system information and paging information. This is called camping on a cell. When a UE that has remained in the RRC_IDLE state needs to establish an RRC connection, it first establishes an RRC connection with the RRC of the E-UTRAN through the RRC connection procedure and transitions to the RRC_CONNECTED state. There are various cases in which a UE that was in the RRC_IDLE state needs to establish an RRC connection, such as when a user needs to make a call or data transmission attempt, or when a paging message is received from the E-UTRAN and a response message is transmitted.

[0125] A Non-Access Stratum (NAS) layer, which is located above the RRC layer, performs functions such as session management and mobility management.

[0126] The NAS hierarchy shown in FIG. 4 will now be described in detail.

[0127] Evolved Session Management (ESM) belonging to the NAS layer is responsible for controlling the UE to use PS services from the network by performing functions such as default bearer management and dedicated bearer management. A default bearer resource is characterized in that it is allocated from the network when the UE is connected to a specific packet data network (PDN) for the first time. At this time, the network allocates an IP address that the UE can use so that the UE can use data services, and allocates the QoS of the default bearer. LTE supports two types of bearers: a bearer with a guaranteed bit rate (GBR) QoS characteristic that guarantees a specific bandwidth for data transmission / reception, and a non-GBR bearer with a best effort QoS characteristic without bandwidth guarantee. In the case of a default bearer, a non-GBR bearer is allocated. In the case of a dedicated bearer, a bearer with a QoS characteristic of GBR or Non-GBR can be allocated.

[0128] A bearer allocated from a network to a UE is called an evolved packet service (EPS) bearer. When an EPS bearer is allocated, the network assigns an ID to the bearer, which is called an EPS bearer ID. An EPS bearer has QoS characteristics of MBR (maximum bit rate) and / or GBR (guaranteed bit rate).

[0129] 6 is a diagram illustrating an example of a general new radio (NR)-radio access network (RAN) architecture. Referring to FIG. 6, an NG-RAN node may be one of the following:

[0130] -A gNB providing NR user plane and control plane protocols towards the UE; or

[0131] -ng-eNB providing E-UTRATM user plane and control plane protocols towards the UE.

[0132] The gNB and the ng-eNB are connected to each other via the Xn interface. The gNB and the ng-eNB are also connected to the Access and Mobility Management Function (AMF) via the NG interface for 5GC, more specifically, to the NG-C interface and to the User Plane Function (UPF) via the NG-U interface (see 3GPP TS 23.501 [3]).

[0133] Incidentally, the architecture and F1 interface for functional separation are defined in 3GPP TS 38.401[4].

[0134] Figure 7 is a diagram showing an example of functional separation between a general NG-RAN and a 5GC (5th generation core). Referring to Figure 7, the yellow boxes indicate logical nodes and the white boxes indicate main functions.

[0135] The gNB and ng-eNB host the following functions:

[0136] -Radio resource management functions: radio bearer control, radio admission control, connection mobility control, dynamic resource allocation for UEs in both uplink and downlink (scheduling)

[0137] -IP header compression, encryption and data integrity protection;

[0138] -If the routing for the AMF cannot be determined from the information provided by the UE, select the AMF from the IMT-2000 3GPP-UE attachment;

[0139] - Routing of user plane data to the UPF;

[0140] -Conveying control plane information to the AMF;

[0141] - Connection setup and termination;

[0142] - Paging message scheduling and transmission

[0143] - System broadcast information scheduling and transmission (provided by AMF or OAM)

[0144] - Measurement and measurement reporting configuration for mobility and scheduling

[0145] -Uplink transmission level packet display

[0146] -Session management;

[0147] -Network slicing support;

[0148] QoS flow management and mapping for data radio bearers

[0149] -Support for UE in RRC_INACTIVE state

[0150] -NAS message distribution function;

[0151] -Radio access network sharing;

[0152] -double connection;

[0153] - Close interoperability between NR and E-UTRA

[0154] The AMF hosts the following main functions (see 3GPP TS 23.501[3]):

[0155] - NAS signal end;

[0156] -NAS signal security;

[0157] -AS security control;

[0158] - Signaling between CN nodes for mobility between 3GPP access networks;

[0159] Idle mode UE connectivity (including paging retransmission control and execution)

[0160] -Registration area management;

[0161] - Supports mobility within and between systems

[0162] -Access authentication;

[0163] - Granting access permissions, including checking roaming privileges;

[0164] -Mobility management controls (subscriptions and policies)

[0165] -Network slicing support;

[0166] -SMF selection

[0167] The UPF hosts the following main functions (see 3GPP TS 23.501[3]):

[0168] -Anchor points for Intra- / Inter-RAT mobility (if applicable)

[0169] - Session points for external PDUs interconnected to a data network

[0170] -Packet routing and forwarding;

[0171] - Packet inspection and user plane part of policy rule trials

[0172] -Traffic usage reporting;

[0173] -Uplink classifier that helps direct traffic to the data network

[0174] - Branching for multi-homed PDU session support;

[0175] - QoS handling for user plane (e.g. packet filtering, gating, UL / DL rate retry)

[0176] -Uplink traffic verification (SDF and QoS flow mapping)

[0177] -Downlink packet buffering and downlink data notification triggering

[0178] The Session Management Function (SMF) hosts the following main functions (see 3GPP TS 23.501 [3]):

[0179] -Session management;

[0180] - UE IP address allocation and management

[0181] -UP function selection and control;

[0182] -Traffic steering configuration to route traffic to the appropriate targets in UPF

[0183] - Policy enforcement and partial control of QoS

[0184] -Downlink Data Notification

[0185] 8 is a diagram showing an example of a general architecture of a 5G (5th generation) system. The following is a description of each reference interface and node in FIG. 8.

[0186] The Access and Mobility Management Function (AMF) supports functions such as signaling between CN nodes for mobility between 3GPP access networks, termination of the Radio Access Network (RAN) CP interface (N2), termination of NAS signaling (N1), registration management (Registration Area management), idle mode UE reachability, support for network slicing, and SMF selection.

[0187] Some or all of the functionality of the AMF can be supported within a single instance of an AMF.

[0188] A data network (DN) may refer to, for example, an operator service, an Internet connection, or a third party service, etc. The DN transmits downlink protocol data units (PDUs) to the UPF, or receives PDUs transmitted from the UE from the UPF.

[0189] A policy control function (PCF) receives information on the flow of packets from an application server and provides a function for determining policies such as mobility management and session management.

[0190] A Session Management Function (SMF) provides a session management function, and when a UE has multiple sessions, each session can be managed by a different SMF.

[0191] Some or all of the functionality of an SMF can be supported within a single instance of an SMF.

[0192] Unified Data Management (UDM) stores user subscription data, policy data, etc.

[0193] The User Plane Function (UPE) transfers downlink PDUs received from the DN to the UE via the (R)AN, and transfers uplink PDUs received from the UE via the (R)AN to the DN.

[0194] The Application Function (AF) interacts with the 3GPP core network to provide services (e.g., support functions such as application impact on traffic routing, network capability exposure access, and interaction with a policy framework for policy control).

[0195] (Radio) Access Network ((R)AN) is a collective term for new radio access networks that support evolved versions of 4G radio access technologies, evolved E-UTRA, and new radio access technologies (NR) (e.g., gNB).

[0196] The gNB supports functions such as functions for radio support management (i.e., Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources (i.e., scheduling) to UEs in uplink / downlink).

[0197] User equipment (UE) refers to user equipment.

[0198] In the 3GPP system, a conceptual link connecting NFs in a 5G system is defined as a reference point.

[0199] N1 is a reference point between the UE and the AMF, N2 is a reference point between the (R)AN and the AMF, N3 is a reference point between the (R)AN and the UPF, N4 is a reference point between the SMF and the UPF, N6 is a reference point between the UPF and the data network, N9 is a reference point between the two core UPFs, N5 is a reference point between the PCF and the AF, N7 is a reference point between the SMF and the PCF, N24 is a reference point between the PCF in the visited network and the PCF in the home network, N8 is a reference point between the UDM and the AMF, N10 is a reference point between the UDM and the SMF, N11 is a reference point between the AMF and the SMF, N12 is a reference point between the AMF and the Authentication Server Function (AUSF), N13 is a reference point between the UDM and the AUSF, N14 is a reference point between the two AMFs, N15 is a reference point between the PCF and the AMF in case of a non-roaming scenario and between the visited network in case of a roaming scenario. N16 is a reference point between two SMFs (in a roaming scenario, the reference point is between the SMF in the visited network and the SMF in the home network), N17 is a reference point between the AMF and the 5G-EIR (Equipment Identity Register), N18 is a reference point between the AMF and the UDSF (Unstructured Data Storage Function), N22 is a reference point between the AMF and the NSSF (Network Slice Selection Function), N23 is a reference point between the PCF and the NWDAF (Network Data Analytics Function), N24 is a reference point between the NSSF and the NWDAF, N27 is a reference point between the NRF (Network Repository Function) in the visited network and the NRF in the home network, N31 is a reference point between the NSSF in the visited network and the NSSF in the home network, N32 is a reference point between the SEPP (security protection proxy) in the visited network and the SEPP in the home network, N33 is a reference point between the NEF (Network Repository Function) in the visited network and the NSSF in the home network.N40 is the reference point between the SMF and the CHF (charging function), and N50 is the reference point between the AMF and the CBCF (Circuit Bearer Control Function).

[0200] Meanwhile, for convenience of explanation, FIG. 8 illustrates a reference model in which a UE accesses one DN using one PDU session, but is not limited thereto.

[0201] In the above, for convenience of explanation, the EPS system using the eNB has been described as a reference. However, the eNB may be a gNB, and the MM (mobility management) function of the MME may be replaced with the AMF, the SM function of the S / P-GW with the SMF, and the user plane-related functions of the S / P-GW with the UPF, etc., and may be replaced with the 5G system.

[0202] In the above, this specification has been described based on EPS, but the content can be supported in a 5G system through similar operations via processes / messages / information for similar purposes.

[0203] Communication system applicable to the present disclosure

[0204] Without being limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams of the present disclosure disclosed in this document may be applicable to a variety of fields requiring wireless communication / connection (e.g., 5G) between devices.

[0205] Hereinafter, the present invention will be described in more detail with reference to the drawings. In the following drawings / description, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks, unless otherwise stated.

[0206] Wireless Devices Applicable to the Present Disclosure

[0207] FIG. 9 is a diagram illustrating an example of a wireless device to which the present disclosure can be applied.

[0208] 9, a first wireless device 900a and a second wireless device 900b may transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR), where {first wireless device 900a, second wireless device 900b} may correspond to {wireless device 100x, base station 120} and / or {wireless device 100x, wireless device 100x} in FIG.

[0209] The first wireless device 900a includes one or more processors 902a and one or more memories 904a, and may further include one or more transceivers 906a and / or one or more antennas 908a. The processor 902a may be configured to control the memory 904a and / or the transceiver 906a to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. For example, the processor 902a may process information in the memory 904a to generate a first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver 906a. The processor 902a may also receive a wireless signal including a second information / signal via the transceiver 906a, and then store information obtained from signal processing of the second information / signal in the memory 904a. The memory 904a may be coupled to the processor 902a and may store various information related to the operation of the processor 902a.

[0210] The second wireless device 900b includes one or more processors 902b and one or more memories 904b, and may further include one or more transceivers 906b and / or one or more antennas 908b. The processor 902b may be configured to control the memory 904b and / or the transceiver 906b to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. For example, the processor 902b may process information in the memory 904b to generate a third information / signal, and then transmit a wireless signal including the third information / signal via the transceiver 906b. The processor 902b may also receive a wireless signal including a fourth information / signal via the transceiver 906b, and then store information obtained from signal processing of the fourth information / signal in the memory 904b. The memory 904b may be coupled to the processor 902b and may store various information related to the operation of the processor 902b. For example, the memory 904b may store software code including instructions for performing some or all of the processes controlled by the processor 902b or performing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in this document. Here, the processor 902b and the memory 904b may be part of a communication modem / circuit / chip designed to realize a wireless communication technology (e.g., LTE, NR). The transceiver 906b may be coupled to the processor 902b and may transmit and / or receive wireless signals via one or more antennas 908b. The transceiver 906b may include a transmitter and / or a receiver. The transceiver 906b may be mixed with an RF unit. In this disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0211] Structure of wireless device applicable to the present disclosure

[0212] FIG. 10 is a diagram showing another example of a wireless device to which the present disclosure is applied.

[0213] 10, a wireless device 1300 corresponds to the wireless devices 900a, 900b of FIG. 9 and may be configured with various elements, components, units, and / or modules. For example, the wireless device 1000 may include a communication unit 1010, a control unit 1020, a memory unit 1030, and additional elements 1040. The communication unit may include a communication circuit 1012 and a transceiver 1014. For example, the communication circuit 1012 may include one or more processors 902a, 902b and / or one or more memories 904a, 904b of FIG. 9. For example, the transceiver 1014 may include one or more transceivers 906a, 906b and / or one or more antennas 908a, 908b of FIG. 9. The controller 1020 is electrically connected to the communication unit 1010, the memory unit 1030, and the additional element 1040, and controls various operations of the wireless device. For example, the controller 1020 may control electrical / mechanical operations of the wireless device based on a program / code / command / information stored in the memory unit 1030. In addition, the controller 1020 may transmit information stored in the memory unit 1030 to an external device (e.g., another communication device) via a wireless / wired interface via the communication unit 1010, or may store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit 1030.

[0214] The additional element 1040 may be configured in various ways depending on the type of wireless device. For example, the additional element 1040 may include at least one of a power unit / battery, an input / output unit, a driving unit, and a computing unit. Without being limited thereto, the wireless device 1000 may be realized in the form of a robot, a vehicle, an XR device, a mobile device, a home appliance, an IoT device, a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environment device, an AI server / device, a base station, a network node, etc. The wireless device may be mobile or may be used at a fixed location depending on the use case / service.

[0215] In FIG. 10, various elements, components, units / parts, and / or modules in the wireless device 1000 may be interconnected entirely via a wired interface, or at least some of them may be connected wirelessly via a communication unit 1010. For example, in the wireless device 1000, the control unit 1020 and the communication unit 1010 may be connected by wire, and the control unit 1020 and other components may be connected wirelessly via the communication unit 1010. Also, each element, component, unit / part, and / or module in the wireless device 1000 may further include one or more elements. For example, the control unit 1020 may be configured with a set of one or more processors. For example, the control unit 1020 may be configured with a set of a communication control processor, an application processor, an ECU (electronic control unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 1030 may be composed of a RAM, a dynamic RAM (DRAM), a ROM, a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0216] Mobile devices to which the present disclosure can be applied

[0217] FIG. 11 is a diagram showing an example of a mobile device to which the present disclosure is applied.

[0218] 11 illustrates a mobile device to which the present disclosure is applied. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, a smart glasses), a mobile computer (e.g., a notebook computer, etc.). The mobile device may be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS base), an advanced mobile station (AMS), or a wireless terminal (WT).

[0219] 11, a portable device 1100 may include an antenna unit 1108, a communication unit 1110, a control unit 1120, a memory unit 1130, a power supply unit 1140a, an interface unit 1140b, and an input / output unit 1140c. The antenna unit 1108 may be configured as a part of the communication unit 1110. Blocks 1110 to 1130 / 1140a to 1140c correspond to blocks 1010 to 1030 / 1040 in FIG. 10, respectively.

[0220] The communication unit 1110 can transmit and receive signals (e.g., data, control signals, etc.) between other wireless devices and base stations. The control unit 1120 can control components of the portable device 1100 to perform various operations. The control unit 1120 can include an AP (application processor). The memory unit 1130 can store data / parameters / programs / codes / commands required for operating the portable device 1100. The memory unit 1130 can also store input / output data / information, etc. The power supply unit 1140a supplies power to the portable device 1100 and can include wired / wireless charging circuits, batteries, etc. The interface unit 1140b can support connection between the portable device 1100 and other external devices. The interface unit 1140b can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit 1140c may receive or output image information / signals, audio information / signals, data, and / or information input by a user, and may include a camera, a microphone, a user input unit, a display unit 1140d, a speaker, and / or a haptic module.

[0221] For example, in the case of data communication, the input / output unit 1140c may acquire information / signals (e.g., touch, text, voice, image, video) input by a user, and the acquired information / signals may be stored in the memory unit 1130. The communication unit 1110 may convert the information / signals stored in the memory into wireless signals, and transmit the converted wireless signals directly to another wireless device or to a base station. In addition, the communication unit 1110 may receive wireless signals from another wireless device or a base station, and then restore the received wireless signals to the original information / signals. The restored information / signals may be stored in the memory unit 1130 and then output in various forms (e.g., text, voice, image, video, haptic) via the input / output unit 1140c.

[0222] The following describes a method for a terminal to store and process a list of subscriber data as SNPN terminal configuration information when performing an authentication procedure via a stand-alone non-public network (SNPN) that does not have credentials.

[0223] As an example, the NPN may be a private network that is distinguished from the public network. The SNPN may be a network that does not depend on the public network and operates independently. Thus, the SNPN may not support interworking with an evolved packet system (EPS) and may not support emergency services. As another example, the SNPN may not support roaming services and is not limited to a specific embodiment. That is, the SNPN may be a private network that operates independently of the public network.

[0224] As an example, when a terminal attempts to connect to an SNPN, the terminal may connect to the SNPN via a PLMN or may connect directly to the SNPN, but is not limited to a specific embodiment. For convenience of explanation, the following description will be given on the basis of a case where the terminal connects directly to the SNPN, but is not limited thereto.

[0225] As an example, FIGS. 12 and 13 are diagrams illustrating a method in which a terminal applied to the present disclosure connects to an SNPN.

[0226] Referring to FIG. 12, a terminal 1 (1210) and a terminal 2 (1220) can connect to the SNPN 1230. Here, an AAA (authentication, authorization, and accounting) server for the connection qualification of the SNPN 1230 can be located outside the SNPN 1230. The AAA server can be a server that manages authentication based on a terminal verification process, authorization based on terminal verification, and terminal accounts. As a specific example, the terminal 1 (1210) can subscribe to the PLMN 1240 and certify qualifications for the SNPN 1230 connection based on the PLMN 1240 to connect to the SNPN 1230. In contrast, the terminal 2 (1220) can be a terminal that subscribes to the SNPN 1230 and directly holds the qualifications of the SNPN 1230, and can connect to the SNPN 1230 using the held qualifications.

[0227] Also, as an example, referring to FIG. 13, the terminal 2 (1320) may be a terminal that subscribes to the SNPN 1330 and directly holds the qualification of the SNPN modem 1330, as in FIG. 12, and can connect to the SNPN 1330 by using the held qualification. In contrast, the terminal 1 (1310) can connect to the SNPN 1330 by proving the qualification for connecting to the SNPN 1330 based on a third party 1340 and obtaining the authority. That is, an entity 1340 separated from the SNPN 1330 can hold the qualification of the SNPN 1330, and the terminal 1 (1310) can obtain the authority to connect to the SNPN 1330 by performing authentication based on the entity that holds the qualification of the SNPN 1330. As an example, the entity of the third party 1340 may be a credential holder (CH), which will be described later.

[0228] Also, as an example, FIG. 14 is a diagram illustrating a method in which a terminal applied to the present disclosure performs credential verification based on an external entity. Referring to FIG. 14, a terminal 1410 may transmit a registration request message including a subscription concealed identifier (SUCI) to a security anchor function (SEAF) 1420. At this time, the SUCI may be generated based on the SUPI of the terminal. Next, the SEAF anchor 1420 may transmit an authentication request message (e.g., Nausf_UEAuthentication_Authenticate Request message) for terminal authentication to an AUSF 1430. As an example, the authentication request message may include, but is not limited to, the above-mentioned SUCI and information on the serving network name.

[0229] Next, the AUSF 1430 may transmit an authentication securing request (e.g., Nudm_UEAuthentication_Get Request) including the SUCI and the serving network name to the UDM 1440. At this time, the UDM 1440 may obtain the SUPI by de-concealing the SUCI, and may transmit an authentication securing response (e.g., Nudm_UEAuthentication_Get Response) including the SUPI information and the AAA server information to the AUSF 1430. Then, the AUSF 1430 may transmit an authentication and access request message (e.g., authentication_request / access request) including the SUPI and the serving network name to the AAA-P (proxy AAA) 1450, and the AAA-P 1450 may transmit the SUPI information and the serving network name information to the AAA-E 1460 via an access request message (e.g., access request). The AAA-E 1460 may perform authentication on the terminal based on the SUPI and the serving network name information. When authentication is complete, the AAA-E1460 returns EAP success. SEAF and a response message (e.g., access accept) including the SUIP to the AAA-P 1450, which then transmits an EAP success, SEAF An authentication and access response message (e.g., authentication_response / access accept) including the SUIP can be delivered to the AUSF 1430. At this time, the AUSF 1430 sends EAP success, K SEAFand SUIP to the SEAF 1420. The SEAF 1420 then transmits a response message (e.g., authentication result) including EAP success, ngKSI, and ABBA to the terminal 1410 to complete the authentication. That is, the terminal 1410 can obtain authority by performing authentication for SNPN connection based on the credential holder, which is an SNPN external entity, based on the above-mentioned procedure.

[0230] Also, as an example, configuration information for an SNPN connection may be broadcast via an NG-RAN node providing an SNPN connection. As an example, the broadcasted information may include at least one of at least one PLMN ID and NID list information identifying an NPN accessible via an NG-RAN per PLMN ID. Also, as an example, the broadcasted information may further include at least one of an indicator indicating whether connection support is possible using the qualifications of an external qualification holder for each SNPN, a GNI list supported per SNPN, and indicator information indicating whether to permit a registration attempt for a terminal that is not explicitly instructed to select an SNPN for each SNPN, and is not limited to a specific embodiment.

[0231] When the terminal obtains the SNPN-related configuration and subscription information based on the above, the terminal may obtain at least one of a PLMN ID and an SNPN network identifier (NID) for each SNPN to which the terminal subscribes. In addition, the terminal capable of SNPN connection may obtain at least one of a subscriber identifier (SUPI) and credentials. In addition, the terminal capable of SNPN connection may further obtain at least one of an N3IWF FQDN (fully qualified domain name) and identifier information of a country where the N3IWF is located as non-3GPP interworking function (N3IWF)-related information for non-3GPP access network connection, but is not limited thereto.

[0232] In addition, when the terminal supports an SNPN connection using the qualification of the qualification holder for each subscribed SNPN, the terminal may further acquire at least one of preferred SNPN list information controlled by the terminal, preferred SNPN list information controlled by the qualification holder, and GIN list information controlled by the qualification holder, but is not limited thereto. In this case, as an example, the preferred SNPN list information controlled by the qualification holder and the GIN list information controlled by the qualification holder may be updated by the qualification holder. In this case, as an example, the above information acquired by the terminal may be broadcast by the NG-RAN, as described above.

[0233] Also, a method for a terminal to select an SNPN can be considered based on the above. As an example, a terminal capable of SNPN access can select an SNPN based on an SNPN access mode.

[0234] If the SNPN access mode is not permitted, even if the terminal is capable of connecting to the SNPN, it cannot connect to the SNPN and can perform the PLMN selection procedure. Also, in the case of a terminal capable of connecting to the SNPN and the PLMN simultaneously, if the SNPN access mode is set, the terminal can only connect to the SNPN, but is not limited to this.

[0235] In contrast, a terminal in which the SNPN access mode is set can connect to the SNPN. Here, for example, the terminal can select a network based on whether or not it supports an SNPN connection using the qualification of a qualification holder.

[0236] As an example, in the automatic network selection mode, the terminal may preferentially connect to the last connected SNPN, or if preferential connection to the last connected SNPN is not possible, the terminal may connect to an SNPN identified by the terminal's SUPI and a qualified PLMN ID or NID.

[0237] In addition, when automatic network selection is not possible based on the above, and the terminal supports an SNPN connection using the qualification of the credential holder, the terminal may perform a connection via an available SNPN. In this case, the available SNPN may be determined based on at least one of preferred SNPN list information controlled by the terminal, preferred SNPN list information controlled by the credential holder, and GIN list information controlled by the credential holder. As another example, the available SNPN may be determined based on an SNPN that is not included in the preferred SNPN list information controlled by the credential holder and the GIN list information controlled by the credential holder and is not explicitly instructed by the network but is available as a credential holder in the terminal, and is not limited to a specific embodiment.

[0238] At this time, as an example, in the past, one qualification could correspond to one SNPN ID, but as described above, one SNPN ID can have multiple qualifications, and one qualification can have multiple SNPN IDs, and is not limited to a specific form.Then, the terminal can select one SNPN based on the available SNPNs and perform a connection.

[0239] Also, as an example, in a manual network selection mode where an SNPN connection is supported using the qualifications of a qualification holder, the terminal may check the SNPN list that supports the connection using the qualifications of the qualification holder and set it as an available SNPN, and is not limited to a specific form.

[0240] The terminal may select an SNPN based on an available SNPN. In this case, the terminal may configure a list of subscriber data and select an SNPN based on the list of subscription data. For example, the subscription data list may include at least one of a subscriber ID in the form of a SUPI, qualification information, and an SNPN identifier. For example, the subscription data list may include setting information for each SNPN based on the terminal, and validity information for each SNPN may be recorded. For example, the terminal may not connect to an SNPN whose validity is set as invalid in the subscription data list. In this case, the terminal may not connect to an SNPN whose validity is set as invalid until a new USIM is inserted or the power is turned on again.

[0241] As an example, as described above, a terminal capable of an SNPN connection can support an SNPN connection by using the credentials of a credential holder (CH), where the credential holder can provide connection authority by authenticating the terminal for an SNPN connection as an entity separate from the SNPN.

[0242] As a specific example, Fig. 15 is a diagram illustrating a method for performing authentication for an SNPN connection based on a credential holder applied in the present disclosure. Referring to Fig. 15, a credential holder 1510 can authenticate and authorize the SNPN connection of a terminal through an AAA (authentication, authorization, and accounting) server. Here, the AAA server may be a server that manages authentication based on a terminal verification process, authorization based on terminal verification, and an account of the terminal.

[0243] For example, referring to FIG. 15, an authentication server function (AUSF) of the SNPN 1520 may authenticate and authorize a terminal based on the credentials provided by the AAA server in the credential holder 1510. At this time, when a user data management (UDM) of the SNPN 1520 instructs the AUSF of the SNPN 1520 that authentication is required based on the AAA server of the credential holder 1510, the AUSF may search and select an AAA server and transmit an EAP (extensible authentication protocol) message to the AAA server acting as an EAP server that preferentially authenticates. At this time, when authentication and authorization are granted based on the AAA server, the SUPI may be used as information for identifying the terminal. When authentication is completed based on the AAA server, the AMF and SMF of the SNPN 1520 may read terminal subscription information from the UDM based on the above-mentioned SUPI. As described above, the terminal may perform authentication using the credentials of the credential holder 1510 to obtain authority for an SNPN connection, thereby making an SNPN connection.

[0244] As an example, when the terminal connects to the SNPN based on the above, the terminal may store configuration information of a list of subscribe data for managing the SNPN. At this time, if an authentication failure occurs in the SNPN selected by the terminal, the terminal may store a subscription corresponding to an ID selected from the SNPN IDs in the subscription data list as configuration information as an invalid subscription. The terminal stores configuration information based on the subscription data list, and may prevent data transmission to the corresponding SNPN, which is an invalid subscription, until a USIN is newly inserted or the power is newly turned on. That is, the terminal may store configuration information based on the subscription data list as described above so that unnecessary signaling transmission is not issued to the SNPN for which authentication has already failed, and another SNPN may be selected to efficiently select the SNPN.

[0245] In this case, for example, in the past, when a terminal supported an SNPN connection, the terminal included a credential for each SNPN ID and could connect to the SNPN for which the credential exists. In contrast, as described above, it is necessary to consider the case where the terminal connects to the SNPN with the credential holder as an entity separated from the SNPN.

[0246] That is, when the terminal supports an SNPN, the terminal can select an SNPN for which it does not have qualifications and perform an authentication procedure through the selected SNPN according to the qualifications held by the terminal. As a specific example, when the terminal supports an SNPN, the first SNPN may be unavailable. In this case, the terminal can authenticate the second SNPN using the qualifications of the first SNPN. That is, the terminal can connect to the second SNPN using the qualifications of the first SNPN, which is an SNPN selected by the terminal, even though the terminal does not have qualifications for the second SNPN.

[0247] As an example, if the terminal stores the setting information of the subscription data list as in the past, the terminal may store the SNPN for which authentication has failed as an invalid SNPN in the subscription data list as setting information. As a specific example, as described above, when the terminal attempts to connect to the second SNPN selected based on the qualification of the first SNPN, the terminal may not be able to set up a connection to the SNPN based on the authentication failure. In this case, if the terminal stores the SNPN for which authentication has failed as setting information in the subscription data list as in the past, the terminal may set the second SNPN as invalid, which may cause a problem that a connection to the selected second SNPN is prohibited instead of the first SNPN that is actually qualified.

[0248] As a more specific example, a case can be considered in which a terminal has subscription #1 and subscription #2. In this case, as an example, subscription #1 may be entitled to SNPN ID #1. That is, the terminal can be entitled to SNPN #1 based on subscription #1. Also, as an example, subscription #2 may be entitled to SNPN ID #2. That is, the terminal can be entitled to SNPN #2 based on subscription #2.

[0249] Here, as an example, a case can be considered in which the terminal is a credential holder in SNPN#3 and uses the credential of SNPN#1 to connect, or a case can be considered in which the terminal is a credential holder in SNPN#3 and uses the credential of SNPN#2 to connect.

[0250] At this time, when the terminal selects an SNPN and SNPN#1 and SNPN#2 are unavailable, the terminal may perform an authentication procedure using the qualifications of SNPN#1 at SNPN#3. Therefore, if the authentication procedure fails, the SNPN at which the authentication procedure failed may be SNPN#1, not SNPN#3. The terminal must store the setting information of SNPN#1 as an invalid SNPN in the subscription data list, but as described above, SNPN#3 may be stored in the subscription data list as an invalid SNPN where authentication failed. Also, as an example, if the terminal performs an authentication procedure using the qualifications of SNPN#2 at SNPN#3 and authentication failure occurs, SNPN#3 may be stored in the subscription data list as an invalid SNPN where authentication failed.

[0251] That is, the terminal can record an authentication failure in an SNPN that can be authenticated by storing an incorrect SNPN ID in the SNPN setting storage information. Therefore, the terminal cannot connect to the SNPN (i.e., SNPN#3) until the terminal inserts a new USIM or turns on the power again, and therefore the SNPN that can be connected cannot be used.

[0252] In addition, since the terminal did not record the SNPNs for which authentication failed (i.e., SNPN#1, SNPN#2) as configuration information in the subscription data list, the terminal may select the SNPNs for which authentication failed again to perform the authentication procedure. As a result, the terminal may perform unnecessary authentication procedures with the SNPNs for which authentication failure is expected, which may result in unnecessary signaling, thereby wasting network resources. Therefore, although the terminal may be able to select another transmittable SNPN and operate normally, there is a risk of a problem in that the terminal may connect to the SNPN for which authentication failed and perform unnecessary operations.

[0253] In view of the above, if a terminal supports SNPN, a method for the terminal to store and process changed terminal configuration information may be required.

[0254] As a specific example, consider a case where a terminal has a first SNPN entitlement based on a first subscription, in which the terminal, as an entitlement holder, can connect to a second SNPN using the entitlement of the first SNPN.

[0255] That is, the terminal may support eNPN and connect to the second SNPN using the qualification of a qualification holder (e.g., a first SNPN). In this case, the terminal may receive an authentication reject message. That is, a connection failure may occur to the terminal.

[0256] At this time, as described above, in order to record the SNPN where authentication failure occurred in the subscription data list, the terminal can check whether the selected SNPN (or current SNPN, i.e., the second SNPN) is the same as the SNPN (i.e., the first SNPN) that is eligible to perform authentication.

[0257] Here, if the selected SNPN (or current SNPN) and the qualified SNPN are different from each other, the terminal may select a qualified SNPN associated with the selected SNPN and set the validity of the corresponding SNPN ID in a list of subscribe data, which is SNPN setting information, to invalid. That is, the terminal may recognize that the first SNPN and the second SNPN are different from each other and set the validity of the qualified first SNPN in the subscription data list to invalid.

[0258] As a specific example, when a terminal selects an SNPN, the terminal may check whether a connection to the SNPN is supported using the qualification of an entity (qualification holder) separated from the SNPN. Here, if the terminal does not support an SNPN connection using the qualification of an entity (qualification holder) separated from the SNPN, the terminal cannot connect to another SNPN using the qualification of the qualification holder. That is, the terminal can connect only to an SNPN that is qualified as a subscribed SNPN. Here, the subscription data list may record the validity of an SNPN that has failed authentication as invalid, as in the conventional case, and may maintain the setting information of the subscription data list until a new USIM is inserted or the power is turned on again.

[0259] On the other hand, when the terminal supports an SNPN connection using the qualification of an entity (qualification holder) separated from the SNPN, the terminal can connect to another SNPN using the qualification of the qualification holder. Therefore, if an authentication failure occurs in the terminal, the terminal can record the validity of the entity (i.e., the qualification holder) selected from the subscription data list as invalid, and can maintain the setting information of the subscription data list until a new USIM is inserted or the power is turned on again.

[0260] In other words, when a terminal supports an SNPN connection using the qualifications of an entity (qualification holder) separated from the SNPN, the validity of the qualification holder can be recorded as invalid, thereby recording the SNPN where the actual authentication failure occurred as invalid, thereby preventing unnecessary signaling in a subsequent authentication procedure, as shown in Table 2 below.

[0261] [Table 2]

[0262] Also, as an example, when a terminal supports a connection to an SNPN using a credential holder's credential, a method of selecting an SNPN having an associated credential by the terminal may be considered. As an example, the terminal may store an SNPN ID corresponding to a subscription used by the terminal as a requested SNPN ID. As another example, an SNPN having an associated credential may be selected based on an SNPN in an SNPN list preferred by the terminal.

[0263] As another example, the network may indicate to the terminal the SNPN ID of the entitlement used by the terminal. In this case, the base station may indicate the SNPN ID of the entitlement used by the terminal via a terminal configuration update message. As an example, the SNPN may be indicated to the terminal as an SNPN having an associated entitlement based on an SNPN in an SNPN list preferred by the entitlement holder. Also, as an example, an available SNPN may be determined based on an SNPN that is not included in the preferred SNPN list information controlled by the entitlement holder and the GIN list information controlled by the entitlement holder and is not explicitly indicated by the network but is usable by the terminal as the entitlement holder, and is not limited to a specific embodiment.

[0264] In this case, for example, if the SNPN selected by the terminal (or the current SNPN) is the same as the SNPN for which the terminal is qualified, the terminal may set the validity of the selected SNPN ID in the subscription data list, which is the SNPN setting information, to invalid. Here, the validity of the SNPN ID may be maintained until the power is turned on again or before the subscription data list is updated.

[0265] As another example, a case may be considered in which a terminal attempts a connection and registration procedure to a second SNPN using the qualifications of a first SNPN, but the authentication procedure fails. Alternatively, a case may be considered in which a terminal attempts a connection and registration procedure to a second SNPN using the qualifications of a first SNPN, but the registration procedure fails. In this case, the terminal may check whether the first SNPN with which the qualifications are linked is the same as the actually selected SNPN (or the current SNPN, i.e., the second SNPN). In this case, if the SNPNs are different from each other, the terminal may manage the first SNPN using a second list of the terminal. As an example, the second list may be distinguished from the subscription data list, which is the first list. In the second list, information on the first SNPN and information on the second SNPN that was attempted to be registered using the first SNPN may be stored together. Thereafter, when the terminal attempts to connect to the second SNPN, the terminal may not use the qualifications of the first SNPN stored in the second list. However, if the terminal is permitted to connect using the qualifications of a qualification holder in an SNPN other than the second SNPN, the terminal may use the qualifications of the first SNPN, and is not limited to a specific form.

[0266] Also, as an example, based on the above, when an SNPN connection is made using the qualifications of another qualification holder rather than the qualifications held by the terminal, the terminal can set a new counter for the connected SNPN using the qualifications of the qualification holder.

[0267] More specifically, when the terminal receives the NAS message, the terminal can check the integrity protection of the received NAS message. As an example, the NAS message may be at least one of an authentication reject, a registration reject, and a service reject message, but other NAS messages may also exist and are not limited to the above embodiment.

[0268] Here, the terminal can use a message for which integrity protection of the NAS message has been confirmed, but cannot use a message for which integrity protection has not been confirmed since it cannot be trusted, and can increment a counter (hereinafter, a first counter). As an example, the first counter may be a counter for determining that the SIM / USIM is not valid. In this case, if the terminal continuously receives a message for which integrity protection has not been confirmed, the terminal can increment the first counter, and if the first counter is incremented by a preset value, the terminal can determine that the set value is an invalid state. That is, the terminal can attempt to receive a message based on integrity protection a preset number of times, and if the reception fails, can set the message to an invalid state.

[0269] In this case, as an example, a counter for an SNPN connected using the qualification of a qualification holder (hereinafter, referred to as the second counter) may be different from the above-mentioned first counter. As an example, the second counter may be a counter corresponding to a case where an SNPN is connected using the qualification of another qualification holder, rather than the qualification of the terminal. As an example, when the terminal receives a NAS message for which integrity protection has not been confirmed (e.g., an authentication reject message), the terminal may attempt to receive the NAS message a preset number of times based on the second counter, and when the preset number of times is exceeded, the terminal may set the SNPN ID for which the authentication has failed to be in an invalid state.

[0270] That is, the second counter for checking whether authentication has failed due to an SNPN for which the terminal is not qualified may be different from the first counter for checking whether authentication has failed due to an SNPN for which the terminal is actually qualified. Here, the second counter may be set to a value larger than or smaller than the first counter. Also, as an example, the second counter and the first counter may be set to the same value, and are not limited to a specific form.

[0271] Based on the above, the terminal can solve the problem that an SNPN that can be successfully authenticated cannot be connected by storing an incorrect SNPN ID in the SNPN setting storage information. In addition, the terminal does not need to recognize an SNPN that has failed authentication and perform unnecessary signaling, thereby ensuring normal operation of the terminal.

[0272] FIG. 16 is a diagram showing a method in which a terminal applied to the present disclosure connects to an SNPN.

[0273] 16, the terminal can check whether or not the terminal supports the SNPN (S160'). At this time, if the terminal does not support the SNPN, the terminal can connect to the PLMN, as described above (S1602). As another example, if the terminal is capable of simultaneous connection to the SNPN and the PLMN but does not support the SNPN connection, the terminal may not connect to the SNPN, as described above.

[0274] Meanwhile, when the terminal supports the SNPN connection, the terminal may check whether to support the SNPN connection using the qualification of the qualification holder (S1603). At this time, when the terminal supports the SNPN connection using the qualification of the qualification holder, the terminal may connect to the second SNPN using the qualification of the first SNPN as the qualification holder (S1604). At this time, as an example, a method of selecting an SNPN with which the terminal has associated qualifications may store an SNPN corresponding to a subscription used by the terminal as a requested SNPN ID. As another example, the terminal may receive an indication of the SNPN ID of the qualification used by the terminal from the network. At this time, the SNPN ID of the qualification used by the terminal may be indicated to the terminal through a UE configuration update message and is not limited to a specific form. Based on the above, when the terminal connects to the second SNPN using the qualification of the first SNPN, the terminal may receive an authentication failure message (S1605). At this time, the terminal may recognize a failure in connection to the second SNPN based on the authentication failure message, and may record the validity of the SNPN corresponding to the connection failure in the subscription data list as invalid. At this time, as an example, since the terminal has connected to the second SNPN using the qualification of the first SNPN, the validity of the first SNPN in the subscription data list may be recorded as invalid (S1606). That is, when the terminal fails to connect to the SNPN based on the qualification of the qualification holder, the validity of the qualification holder may be recorded as invalid.

[0275] On the other hand, if the terminal does not support connection to the SNPN with the qualification of the qualification holder (S1603), the terminal can connect to the SNPN using the qualification held by the terminal. As an example, the terminal holds a qualification for a third SNPN and can connect to the third SNPN based on the qualification held (S1607). At this time, the terminal can recognize a failure in connection to the third SNPN based on the authentication failure message, and can record the validity of the corresponding SNPN in the subscription data list as invalid for the SNPN corresponding to the connection failure. Here, since the terminal has connected to the third SNPN using the qualification of the third SNPN, the validity of the third SNPN in the subscription data list can be recorded as invalid (S1609). In other words, since the terminal has connected to the corresponding SNPN through the qualification held by the terminal, the validity of the corresponding SNPN can be recorded in the SNPN as invalid.

[0276] FIG. 17 is a diagram showing a method in which a terminal applied to the present disclosure connects to an SNPN. As an example, referring to FIG. 17, a case in which a terminal connects to an SNPN as shown in FIG. 16 can be considered (S1701). In this case, when a terminal connects to a second SNPN using a qualification of a first SNPN as a qualification holder, if the connection fails, the terminal can record the validity of the first SNPN in an invalid state in the subscription data list, as described above. In this case, as an example, in order for the terminal to determine the connection failure, the terminal can check the reception of an authentication rejection message. In this case, when the terminal receives the authentication rejection message, the terminal can increment a first counter (S1702). Here, when the terminal continuously receives the authentication rejection message and the first counter reaches a first value, the terminal can recognize the connection failure (S1703). Thereafter, the terminal can record the validity of the first SNPN in an invalid state in the subscription data list (S1704).

[0277] Also, as an example, the terminal may connect to the third SNPN based on the qualifications held by the terminal. That is, the terminal may connect to the SNPN using the qualifications of the SNPN, without using the qualifications of the qualification holder, as described above. In this case, as an example, the terminal may check the reception of an authentication rejection message in order to determine the connection failure. In this case, when the terminal receives the authentication rejection message, the terminal may increment a second counter (S1705). Here, when the terminal continuously receives the authentication rejection message and the second counter reaches a second value, the terminal may recognize the connection failure (S1706). Thereafter, the terminal may record the validity of the third SNPN as invalid in the subscription data list (S1707).

[0278] In this case, as an example, the first counter and the second counter described above may be set to different values ​​from each other. That is, the counter for determining authentication failure when connecting to an SNPN using the qualification of a qualification holder and the counter for determining authentication failure when connecting directly to an SNPN using the qualification of the SNPN may be set to different values ​​from each other, as described above.

[0279] FIG. 18 is a diagram illustrating a terminal operation method applied to the present disclosure.

[0280] 18, a terminal supporting an SNPN connection can connect to a second SNPN based on the credentials of a first SNPN as a credential holder (S1810). In this case, if the terminal recognizes a failure in connection to the second SNPN (S1820), the terminal can set the validity of the first SNPN in a list of subscribe data to an invalid state based on the connection failure (S1830). That is, the credential holder can be recorded as invalid.

[0281] At this time, as an example, the terminal may further check whether or not to support an SNPN connection using the credentials of a credential holder. If the terminal supports an SNPN connection using the credentials of a credential holder, the terminal may connect to a second SNPN based on the credentials of the first SNPN as described above. In contrast, if the terminal does not support an SNPN connection using the credentials of a credential holder, the terminal may connect to an SNPN based on the credentials held by the terminal. As an example, when the terminal connects to a third SNPN based on the credentials of a third SNPN held by the terminal and recognizes a failure in the connection to the third SNPN, the terminal may set the validity of the third SNPN in the subscription data list to an invalid state. That is, the validity of the target SNPN may be set to an invalid state.

[0282] Also, as an example, when the terminal receives a first authentication rejection message based on a connection to a second SNPN using the qualification of a first SNPN, the terminal increments a first counter, and when the first counter reaches a first value, the terminal may recognize a failure to connect to the second SNPN. Also, when the terminal receives a second authentication rejection message based on a connection to a third SNPN using the qualification of the terminal, the terminal increments a second counter, and when the second counter reaches a second value, the terminal may recognize a failure to connect to the third SNPN. In this case, as an example, the first counter and the second counter may be set to different counters, as described above.

[0283] Also, for example, the validity of the subscription data list can be maintained until the power is turned on again or before the subscription data list is updated, as described above.

[0284] It is obvious that the above-mentioned example of the proposed method can be included as one of the implementation methods of the present disclosure and can be regarded as a kind of proposed method. Also, the above-mentioned proposed methods may be implemented independently, or may be implemented in a combined (or merged) form of some of the proposed methods. Rules can be defined so that the base station notifies the terminal of the applicability information of the proposed method (or information on the rules of the proposed method) via a predefined signal (e.g., a physical layer signal or a higher layer signal).

[0285] The present disclosure may be embodied in other specific forms without departing from the technical ideas and essential features described in the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in all respects, but should be considered as illustrative. The scope of the present disclosure must be determined by a reasonable analysis of the attached claims, and all modifications within the scope of the equivalents of the present disclosure are included in the scope of the present disclosure. In addition, claims that do not have an explicit reference relationship in the claims may be combined to form an embodiment, or may be included as a new claim by amendment after filing. [Industrial Applicability]

[0286] The embodiments of the present disclosure may be applied to various wireless access systems, such as 3GPP (3rd Generation Partnership Project) or 3GPP2 systems.

[0287] The embodiments of the present disclosure are applicable not only to the various wireless access systems but also to all technical fields to which the various wireless access systems are applied. Furthermore, the proposed method is also applicable to mmWave and Thz communication systems using ultra-high frequency bands.

[0288] Furthermore, embodiments of the present disclosure may be applied to a variety of applications, such as autonomous vehicles and drones.

Claims

1. 1. A method for operating a terminal in a wireless communication system, comprising: A terminal supporting a standalone non public network (SNPN) access accesses a second SNPN based on a credential of the first SNPN as a credential holder; identifying a failure to access the second SNPN; setting an entry contained in a list of subscription data having a SNPN identifier as not valid until the terminal is switched off or the entry is updated, the list includes at least one entry containing validity information for each SNPN; The entry is associated with the first SNPN based on the terminal supporting access to the SNPN by utilizing a credential of a credential holder; The entry is associated with the second SNPN based on the terminal not supporting the SNPN access by utilizing the credential of the credential holder.

2. The method of claim 1 , wherein the terminal accesses the second SNPN based on the credential of the first SNPN based on the terminal supporting the SNPN access by utilizing the credential of the credential holder.

3. The method of claim 1 , wherein the terminal performs the SNPN access based on a credential that the terminal possesses based on the terminal not supporting the SNPN access by utilizing the credential of the credential holder.

4. The method of claim 3, wherein the terminal accesses the third SNPN based on credentials for the third SNPN held by the terminal, and based on recognizing failure of the access to the third SNPN, the terminal sets the validity of the third SNPN in the list of subscription data to an invalid state.

5. based on the terminal receiving a first authentication rejection message based on the access to the second SNPN, the terminal increments a first counter; The method of claim 4 , wherein the terminal recognizes a failure in the access to the second SNPN based on the first counter reaching a first value.

6. based on the terminal receiving a second authentication rejection message based on the access to the third SNPN, the terminal increments a second counter; The method of claim 5 , wherein the terminal recognizes the failure of the access to the third SNPN based on the second counter reaching a second value.

7. The method of claim 6 , wherein the first counter and the second counter are configured as different counters.

8. The method of claim 1 , wherein the validity of the first SNPN is maintained until the power is switched on again or until the list of subscription data is updated.

9. A terminal operating in a wireless communication system, comprising: At least one transceiver; At least one processor; at least one memory operatively coupled to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform certain operations; The specific operation is: A terminal supporting a standalone non public network (SNPN) access accesses a second SNPN based on a credential of the first SNPN as a credential holder; Identifying a failure to access the second SNPN; configured to set an entry included in a list of subscription data having an SNPN identifier as not valid until the terminal is switched off or the entry is updated, the list includes at least one entry containing validity information for each SNPN; The entry is associated with the first SNPN based on the terminal supporting access to the SNPN by utilizing a credential of a credential holder; A terminal, the entry being associated with the second SNPN based on the terminal not supporting the SNPN access by utilizing the credential of the credential holder.

10. 1. A network operating in a wireless communication system, comprising: At least one transceiver; At least one processor; at least one memory operatively coupled to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform certain operations; The specific operation includes causing the transceiver to: receiving a registration request message from a terminal; Controlling the terminal to transmit a registration rejection message; The terminal is a terminal that supports standalone non public network (SNPN) access, The terminal includes: accessing the network, a second SNPN, based on a credential of the first SNPN as a credential holder; Identifying the failure to access the second SNPN based on the registration rejection message; configured to set an entry included in a list of subscription data having an SNPN identifier as not valid until the terminal is switched off or the entry is updated, the list includes at least one entry containing validity information for each SNPN; The entry is associated with the first SNPN based on the terminal supporting access to the SNPN by utilizing a credential of a credential holder; The entry is associated with the second SNPN based on the terminal not supporting the SNPN access by utilizing the credential of the credential holder.

Images