Access control processing method considering service area-based network slicing and apparatus therefor

Abstract

The present document relates to a method for performing access control considering service area-based network slicing, especially partially allowed network slice selection assistance information (PANSSAI). The method therefor comprises: when mobile oriented (MO) partially allowed network slice selection assistance information (PANSSAI)-related data is generated, determining a specific access category for an access attempt corresponding to the MO PANSSAI in a non access stratum (NAS) layer of a terminal; providing access identification information and information on the specific access category from the NAS layer of the terminal to a radio resource control (RRC) layer; and performing, in the RRC layer of the terminal, an access control procedure on the basis of the access identification information and the information on the specific access category.

Description

Access control processing method considering service area-based network slicing and device therefor

[0001] This specification relates to a 3GPP wireless communication system, and more particularly, to a method for processing access control considering service area-based network slicing, and in particular, Partially Allowed NSSAI (Network Slice Selection Assistance Information), and a device therefor.

[0002] Standardization for 3GPP is being discussed for 6G after 5G.

[0003] In 5G networks or future next-generation networks, the concept of network slicing will be introduced to provide more flexible and optimized services to users.

[0004] Specifically, network slicing involves dividing a single physical network into multiple virtual networks. Each network segment can be customized and optimized for specific application services or subscriber types.

[0005] Based on cloud computing and virtualization technologies, shared physical network resources can be dynamically and effectively scheduled into logical network slices in response to changing user demands.

[0006] Networks segmented in this way can be distinguished by Network Slice Selection Assistance Information (NSSAI). There are several types of NSSAI. If a terminal fails to detect changes in NSSAI at the network level and access control is performed, communication processing can be inefficiently delayed.

[0007] In order to solve the above-described problem, one aspect of the present invention proposes an access control processing method and a device therefor that considers service area-based network slicing.

[0008] Specifically, we propose a method and a device for performing access control procedures when PANSSAI (Partially Allowed Network Slice Selection Assistance Information) is supported and applied.

[0009] In addition, when PANSSAI is supported and applied, we propose a method for setting the Cause field of an RRC connection message and a device for doing so.

[0010] The problems to be solved by the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0011] In one aspect of the present invention for solving the above-described problem, a method for operating a terminal in a wireless communication system is proposed, the method including: when data related to MO (Mobile Oriented) PANSSAI (partially allowed network slice selection assistance information) is generated, determining a specific access category for a connection attempt corresponding to the MO PANSSAI in a NAS (Non Access Stratum) layer of the terminal; providing connection identification information and information about the specific access category from the NAS layer of the terminal to an RRC (Radio Resource Control) layer; and performing a connection control procedure in the RRC layer of the terminal based on the connection identification information and information about the specific access category.

[0012] Meanwhile, in another aspect of the present invention for solving the above-described problem, a terminal in a wireless communication system is proposed, comprising: a transceiver; at least one processor; and at least one memory storing instructions and being operably electrically connectable to the at least one processor, wherein an operation performed based on the instructions being executed by the at least one processor includes: when data related to MO (Mobile Oriented) PANSSAI (partially allowed network slice selection assistance information) is generated, determining a specific access category for a connection attempt corresponding to the MO PANSSAI in a NAS (Non Access Stratum) layer of the terminal, providing connection identification information and information about the specific access category from the NAS layer of the terminal to an RRC (Radio Resource Control) layer, and performing a connection control procedure in the RRC layer of the terminal based on the connection identification information and the information about the specific access category.

[0013] Preferably, the RRC layer of the terminal further includes transmitting an RRC connection setup message including an RRC connection establishment reason (cause) to the network, wherein the RRC connection establishment reason may correspond to a specific connection category for the MO PANSSAI responsive connection attempt.

[0014] Preferably, the method may further include receiving information for performing the PANSSAI-related access control procedure from the network via SIB1 (System Information Block Type1).

[0015] Preferably, performing the access control procedure may include performing a Unified Access Control (UAC) check based on the access identification information, information regarding the specific access category, and PANSSAI-related information. In particular, the PANSSAI-related information may include information regarding a specific NSSAI and information regarding a Tracking Area (TA) identifier corresponding to the specific NSSAI.

[0016] According to the embodiments of the present invention as described above, an access control processing method considering service area-based network slicing can be implemented.

[0017] Specifically, by distinguishing between partially permitted NSSAI traffic-related signaling and the associated QoS and application service requirements, access control can be efficiently handled in the event of congestion in the wireless section. This efficient access control can improve congestion situations and minimize battery and resource waste for both terminals and the network by reducing the overhead of unnecessary signaling.

[0018] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention belongs from the description below.

[0019] Figure 1 is a diagram illustrating a 3GPP wireless communication system.

[0020] Figure 2 is an example diagram showing the structure of a wireless communication system from a node perspective.

[0021] Figure 3 is another example diagram showing the structure of a wireless communication system from a node perspective.

[0022] Figure 4 is an example diagram showing the structure of a radio interface protocol between a terminal and a network.

[0023] Figure 5 is an example diagram to explain the concept of network slicing.

[0024] FIG. 6 is a drawing for explaining a method for performing an access control procedure according to one embodiment of the present invention.

[0025] Figure 7 shows a block diagram of a processor in which the disclosure of this specification is implemented.

[0026] Figure 8 illustrates a device according to one embodiment of the present specification.

[0027] FIG. 9 illustrates a block diagram of a network node according to one embodiment of the present specification.

[0028] Fig. 10 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0029] FIG. 11 is a block diagram showing in detail the transmitter / receiver of the first device illustrated in FIG. 8 or the transmitter / receiver unit of the device illustrated in FIG. 10.

[0030] FIG. 12 illustrates another wireless communication system applicable to the disclosure of this specification.

[0031] It should be noted that the technical terms used in this specification are used merely to describe specific embodiments and are not intended to limit the contents of this specification. In addition, unless specifically defined otherwise herein, the technical terms used in this specification should be interpreted as having a meaning generally understood by those skilled in the art to which this specification pertains, and should not be interpreted in an excessively broad or narrow sense. In addition, if a technical term used in this specification is an incorrect technical term that does not accurately express the contents and ideas of this specification, it should be replaced with a technical term that can be correctly understood by a person skilled in the art. In addition, general terms used in this specification should be interpreted according to their dictionary definitions or according to the preceding and following context, and should not be interpreted in an excessively narrow sense.

[0032] Additionally, the singular expressions used herein include plural expressions unless the context clearly dictates otherwise. In this application, terms such as "consist of" or "have" should not be construed to necessarily include all of the components or steps described in the specification, and should be construed to mean that some of the components or steps may not be included, or that additional components or steps may be included.

[0033] Additionally, terms including ordinal numbers, such as "first," "second," etc., used herein may be used to describe various components, but these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present invention, a first component could be referred to as a second component, and similarly, a second component could also be referred to as a first component.

[0034] When a component is referred to as being connected or connected to another component, it may be directly connected or connected to that other component, but there may also be other components intervening. Conversely, when a component is referred to as being directly connected or connected to another component, it should be understood that there are no other components intervening.

[0035] Hereinafter, embodiments will be described in detail with reference to the attached drawings. Regardless of the drawing reference numerals, identical or similar components will be given the same reference numerals, and redundant descriptions thereof will be omitted. In addition, when describing the contents of this specification, if a detailed description of a related known technology is judged to obscure the gist of this specification, the detailed description thereof will be omitted. In addition, it should be noted that the attached drawings are only intended to make the contents and ideas of this specification easily understandable, and should not be construed as limiting the contents and ideas of this specification by the attached drawings. The contents and ideas of this specification should be construed to extend to all changes, equivalents, and substitutes other than the attached drawings.

[0036] In this specification, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”

[0037] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0038] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0039] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0040] Additionally, parentheses used in this specification may mean “for example.” Specifically, when “control information (PDCCH)” is indicated, “PDCCH” may be suggested as an example of “control information.” In other words, “control information” in this specification is not limited to “PDCCH,” and “PDDCH” may be suggested as an example of “control information.” Furthermore, even when indicated as “control information (i.e., PDCCH),” “PDCCH” may be suggested as an example of “control information.”

[0041] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0042] Although the attached drawing illustrates a UE (User Equipment) as an example, the illustrated UE may also be referred to as a UE (100) (Terminal), ME (Mobile Equipment), etc. In addition, the UE may be a portable device such as a laptop, mobile phone, PDA, smart phone, multimedia device, etc., or a non-portable device such as a PC or vehicle-mounted device.

[0043]

[0044] As described above, this specification assumes a method applicable to a 3GPP wireless communication system. To this end, the following describes a specific network configuration of a 3GPP wireless communication system to specifically illustrate embodiments of the present invention.

[0045]

[0046] 3GPP wireless communication system configuration

[0047] Figure 1 is a diagram illustrating a 3GPP wireless communication system.

[0048] The 5GC (5G Core) network may include various components, and in FIG. 1, some of them include AMF (Access and Mobility Management Function) (41), SMF (Session Management Function) (42), PCF (Policy Control Function) (43), UPF (User Plane Function) (44), AF (Application Function) (45), UDM (Unified Data Management) (46), and N3IWF (Non-3GPP InterWorking Function) (49).

[0049] The UE (User Equipment) (10) is connected to the data network via the UPF (44) through the NG-RAN (Next Generation Radio Access Network).

[0050] The UE (10) can also receive data services via untrusted non-3GPP (non-3rd Generation Partnership Project) access, such as a Wireless Local Area Network (WLAN). To connect the non-3GPP access to the core network, an N3IWF (49) may be deployed.

[0051] Figure 2 is an example diagram showing the structure of a wireless communication system from a node perspective.

[0052] As can be seen from FIG. 2, the UE is connected to a data network (DN) via a radio access network (RAN).

[0053] The illustrated Control Plane Function (CPF) node performs all or part of the functions of the Mobility Management Entity (MME) of 4th generation mobile communication, and all or part of the control plane functions of the Serving Gateway (S-GW) and the PDN Gateway (P-GW). The CPF node includes the Access and Mobility Management Function (AMF) and the Session Management Function (SMF).

[0054] The illustrated User Plane Function (UPF) node is a type of gateway through which user data is transmitted and received. The UPF node can perform all or part of the user plane functions of the S-GW and P-GW of 4G mobile communications.

[0055] The illustrated PCF (Policy Control Function) is a node that controls the business operator's policy.

[0056] The illustrated application function (AF) is a server for providing various services to the UE.

[0057] The Unified Data Management (UDM) depicted is a type of server that manages subscriber information, similar to the Home Subscriber Server (HSS) of 4G mobile communications. The UDM stores and manages the subscriber information in a Unified Data Repository (UDR).

[0058] The illustrated Authentication Server Function (AUSF) authenticates and manages the UE.

[0059] The illustrated Network Slice Selection Function (NSSF) is a node for network slicing, as described below.

[0060] A UE can connect to two data networks simultaneously using multiple PDU (protocol data unit or packet data unit) sessions.

[0061] Figure 3 is another example diagram showing the structure of a wireless communication system from a node perspective.

[0062] Figure 3 shows an architecture for a UE to access two data networks simultaneously using one PDU session.

[0063] Matters related to the reference points shown in FIGS. 2 and 3 are as follows.

[0064] N1 represents the reference point between the UE and AMF.

[0065] N2 represents the reference point between (R)AN and AMF.

[0066] N3 represents the reference point between (R)AN and UPF.

[0067] N4 represents the reference point between SMF and UPF.

[0068] N5 represents the reference point between PCF and AF.

[0069] N6 represents the reference point between UPF and DN.

[0070] N7 represents the reference point between SMF and PCF.

[0071] N8 represents the reference point between UDM and AMF.

[0072] N9 represents a reference point between UPFs.

[0073] N10 represents the reference point between UDM and SMF.

[0074] N11 represents the reference point between AMF and SMF.

[0075] N12 represents the reference point between AMF and AUSF.

[0076] N13 represents the reference point between UDM and AUSF.

[0077] N14 represents a reference point between AMFs.

[0078] N15 represents the reference point between PCF and AMF.

[0079] N16 represents a reference point between SMFs.

[0080] N22 represents the reference point between AMF and NSSF.

[0081] N33 represents the reference point between NEF (Network Exposure Function) and AF.

[0082] Figure 4 is an example diagram showing the structure of a radio interface protocol between a terminal and a network.

[0083] The above wireless interface protocol is based on the 3GPP wireless access network standard. The above wireless interface protocol is horizontally divided into the physical layer, data link layer, and network layer, and vertically divided into the user plane for data information transmission and the control plane for control signal transmission.

[0084] The above protocol layers can be divided into L1 (first layer), L2 (second layer), and L3 (third layer) based on the three lower layers of the Open System Interconnection (OSI) reference model, which is widely known in communication systems.

[0085] Below, each layer of the wireless interface protocol is described.

[0086] The first layer, the Physical layer, provides information transfer services using physical channels. The Physical layer is connected to the upper layer, the Medium Access Control (MAC) layer, via a Transport Channel, through which data is transferred between the MAC layer and the Physical layer. Furthermore, data is transferred between different Physical layers, i.e., between the physical layers of the transmitter and receiver, via the Physical Channel.

[0087] Layer 2 includes the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer.

[0088] The third layer includes the Radio Resource Control (RRC) layer. The RRC layer is defined solely in the control plane and is responsible for controlling logical, transport, and physical channels, related to the configuration, reconfiguration, and release of radio bearers (RBs). Here, RBs represent the services provided by the second layer for data transmission between the terminal and the RAN.

[0089] The above NAS (Non-Access Stratum) layer performs functions such as session management and mobility management.

[0090] The NAS layer is divided into NAS entities for MM (Mobility Management) and NAS entities for SM (Session Management).

[0091] 1) NAS entities for MM provide the following general functions:

[0092] As NAS procedures related to AMF, including:

[0093] Registration management and access management procedures. AMF supports the following functions:

[0094] - Secure NAS signal connection between UE and AMF (integrity protection, encryption)

[0095] 2) The NAS entity for SM performs session management between the UE and SMF.

[0096] SM signaling messages are processed, i.e., generated and processed, at the NAS-SM layer of the UE and SMF. The content of SM signaling messages is not interpreted by the AMF.

[0097] - In case of SM signaling transmission,

[0098] - The NAS entity for MM generates a NAS-MM message that induces how and where to deliver the SM signaling message, with a security header indicating the NAS transmission of the SM signaling, and additional information for the receiving NAS-MM.

[0099] - Upon receiving SM signaling, the NAS entity for SM performs an integrity check of the NAS-MM message and interprets additional information to derive how and where to derive the SM signaling message.

[0100] Meanwhile, the RRC layer, RLC layer, MAC layer, and PHY layer located below the NAS layer in FIG. 4 are collectively called the Access Stratum (AS).

[0101] The network system for 5G (i.e., 5GC) also supports non-3GPP access. A representative example of non-3GPP access is WLAN access. This WLAN access may include both trusted and untrusted WLANs.

[0102] In a system for 5G, AMF performs registration management (RM) and connection management (CM) for 3GPP access as well as non-3GPP access.

[0103]

[0104] Network Slicing

[0105] Figure 5 is an example diagram to explain the concept of network slicing.

[0106] Network slicing refers to dividing a single physical network into multiple virtual networks. Each network segment can be customized and optimized for specific application services or subscriber types. Using cloud computing and virtualization technologies, shared physical network resources can be dynamically and effectively scheduled across logical network slices to meet changing user demands.

[0107] A 5G network slice is a collection of network functions and settings for a specific use case or business model. Referring to Figure 5, Network Slice 1 represents an example of 5G network slicing with enhanced Mobile Broadband (eMBB), Network Slice 2 represents V2X (Vehicle to Everything), and Network Slice 3 represents MIoT (Massive IoT).

[0108] A single network slice can span several domains, including distributed cloud infrastructure, radio access networks operating transport networks, and core networks. The fundamental principle of 5G network slice design is to provide only the customized functions required to handle traffic for specific use cases. Network slices are equipped with the necessary customization capabilities and the ability to adapt to changing requirements.

[0109] Meanwhile, according to the Next Generation Mobile Networks (NGMN) definition, network slicing consists of three layers: the Service Instance Layer, the Network Slice Instance Layer, and the Resource Layer. The Service Instance Layer represents end-user services, and each service is represented by a Service Instance. The Network Slice Service Instance Layer includes the provided Network Slice Instances, which provide the network characteristics required for the Service Instances. The Resource Layer provides all virtual or physical resources and network functions required to create a Network Slice Instance.

[0110] In the 3GPP 5G mobile communication network being developed by the IETF (Internet Engineering Task Force) DetNet (Deterministic Networking) WG (Working Group), network slicing is operated based on the Core Network (CN), and basically operates based on Network Slice Instance information. A network slice instance refers to a set of resources and network function instances required to form a network slice. A network slice can be used in the entire PLMN (Public Land Mobile Network) or in one or more TAs (Tracking Areas). A network slice instance can be associated with one or more S-NSSAI (Single-Network Slice Selection Assistance Information), and conversely, one S-NSSAI can be associated with one or more network slice instances.

[0111] In 3GPP 5G mobile networks, a network slice is identified by a single S-NSSAI. S-NSSAI consists of a Slice / Service type (SST) and a Slice Differentiator (SD). While the SST must be included in S-NSSAI, the SD may or may not be included. Currently, six SST types and values ​​are defined as standards in the 3GPP technical specifications, as shown in Table 1.

[0112] Slice / Service TypeSST valueMBB(enhanced Mobile Broadband)1URLLC(Ultra-Reliable Low Latency Communications)2MIoT(massive IoT)3V2X(Vehicle to Everything)4HMTC*(High-performance Machine-Type Communications)(*since Rel-17 onwards)5HDLLC**(High Data rate and Low Latency Communications)(**since Rel-18 onwards)6

[0113] Meanwhile, a set of one or more S-NSSAIs is called NSSAI (Network Slice Selection Assistance Information). During the registration process of the 5G mobile communication network, the terminal uses NSSAI to request a network slice connection of the core network, and the core network is responsible for authenticating and authorizing the terminal's request for a network slice connection. The terminal may receive and configure or store various types of NSSAI information from the 5G core network. Configured NSSAI is NSSAI provided and configured by the serving PLMN, Default Configured NSSAI is NSSAI provided and configured by the home PLMN, and Requested NSSAI is NSSAI used when the terminal requests a connection to the core network for a specific network slice. Allowed NSSAI is NSSAI that means the core network allows the terminal to connect to a specific network slice. Additionally, Subscribed S-NSSAI refers to the S-NSSAI included in the subscriber information.

[0114] The terminal may have a default NSSAI that is pre-configured and stored, or may be provided or updated from the core network. Each S-NSSAI in the default NSSAI corresponds to an S-NSSAI in the subscriber's NSSAI. The S-NSSAI in the terminal's requested NSSAI refers to an S-NSSAI in the NSSAI that has been previously configured or permitted by the network. Consequently, the NSSAI or S-NSSAI that the terminal generally uses refers to the NSSAI or S-NSSAI that has been previously configured or permitted by the network.

[0115] Meanwhile, terminals and 5G mobile networks basically receive or use NSSAI information during the registration process to support and manage network slice connections. First, terminals generally have a preset NSSAI that is set and stored in advance and an authorized NSSAI that has been previously authorized by the network and can be used. If there is no previously authorized NSSAI from the network, there may not be an authorized NSSAI. When a terminal requests connection to a specific network slice, it sends a Registration Request message containing the requested NSSAI information to the network during the registration process. At this time, the requested NSSAI information means the use of the default configured NSSAI information if the terminal does not have a configured NSSAI or an authorized NSSAI stored, i.e., if there is no available configured NSSAI information. If the authorized NSSAI is not stored and an available configured NSSAI is stored, the configured NSSAI is used as the requested NSSAI information. Finally, if an available permission NSSAI is stored, the permission NSSAI is used as the request NSSAI information. The core network verifies the request NSSAI included in the registration request message transmitted by the terminal and responds to the terminal by including the configuration NSSAI, permission NSSAI, and rejected NSSAI information in the Registration Accept message. The terminal stores the configuration NSSAI, permission NSSAI, and rejection NSSAI information provided through the registration accept message transmitted from the network and uses them when requesting a network slice connection in the future. However, in principle, the terminal does not use the rejected NSSAI because it is NSSAI information that the network has rejected for use.Through this registration request procedure, the terminal and the network mutually provide NSSAI information for network slice connection support and management, and manage the settings.

[0116] In addition, when a terminal transmits a PDU session setup request message to the network for data transmission, it transmits to the network S-NSSAI information about the network slice to which the application related to data transmission is trying to connect from the stored permission NSSAI, and the network checks the S-NSSAI information included in the PDU session setup request message transmitted by the terminal, and if there is no problem, it responds with acceptance.

[0117] In addition, when network slicing-related information including NSSAI is changed due to changes in subscriber information or mobile network policy, the network can notify the terminal of the changed NSSAI information. In this case, the network can provide the changed NSSAI information to the terminal through a generic UE configuration update procedure. To this end, the AMF transmits a configuration update command message to the terminal including configured NSSAI, allowed NSSAI, and rejected NSSAI information, and the terminal updates and stores the received configured NSSAI, allowed NSSAI, and rejected NSSAI information. Thereafter, the terminal performs a network slice connection request using the changed NSSAI information.

[0118] Meanwhile, the 3GPP Release 18 standard defines Partially Allowed NSSAI. A comparison of the existing Allowed NSSAI and the Partially Allowed NSSAI is as follows:

[0119] The existing Allowed NSSAI refers to an NSSAI that notifies the network (AMF and / or SMF) that the network slicing service related to the NSSAI information is permitted for the NSSAI requested by the terminal in the registration area in which the terminal is registered. In this case, the Allowed NSSAI is applied on the PLMN or all TA lists of the area in which the terminal is registered (Registration Area).

[0120] On the other hand, the partial allowed NSSAI is applied on the PLMN or some TA lists of the registration area where the terminal is registered. Therefore, the network slicing service associated with the partial allowed NSSAI (e.g., partial allowed NSSAI#1) is allowed in some TAs in the registered area, but the network slicing service associated with the partial allowed NSSAI (e.g., partial allowed NSSAI#1) is not allowed in other TAs. The partial allowed NSSAI#1 can be represented by a specific S-NSSAI#1. This partial allowed NSSAI information is provided and updated through the registration procedure or the generic UE configuration update procedure. In a mobile communication network, an operator can operate a service area differently according to the partial allowed NSSAI, and this service area differentiation according to the partial allowed NSSAI is essential for supporting QoS differentiation, i.e., differentiated resource allocation and traffic processing.

[0121] Currently, in 3GPP 5GS (5G System), access control is performed by taking into account network congestion in the terminal and wireless sections, as shown in Table 2 and Table 3 below.

[0122] Rule #Type of access attemptRequirements to be metAccess Category1Response to paging or NOTIFICATION over non-3GPP access;5GMM connection management procedure initiated for the purpose of transporting an LPP message without an ongoing 5GC-MO-LR procedure;Access attempt to handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access; orAccess attempt upon receipt of "call-pull-initiated" indication from the upper layers (see 3GPP TS 24.174 [13D])Access attempt is for MT access, or handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access; orAccess attempt is made upon receipt of "call-pull-initiated" (3GPP TS 24.174 [13D])0 (= MT_acc)2EmergencyUE is attempting access for an emergency session (NOTE 1, NOTE 2)2 (= emergency)3Access attempt for operator-defined access categoryUE stores operator-defined access category definitions valid in the current PLMN as specified in subclause 4.5.3, and access attempt is matching criteria of an operator-defined access category definition32-63(= based on operator classification)3.1Access attempt for MO exception dataUE is in NB-N1 mode and allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368

[0017] or the USIM file EF. NASCONFIGin 3GPP TS 31.102

[0022] ), and access attempt is for MO data or for MO signalling initiated upon receiving a request from upper layers to transmit user data related to an exceptional event.10 (= MO exception data)4Access attempt for delay tolerant service(a) UE is configured for NAS signalling low priority or UE supporting S1 mode is configured for EAB (see the "ExtendedAccessBarring" leaf of NAS configuration MO in 3GPP TS 24.368

[0017] or 3GPP TS 31.102

[0022] ) where "EAB override" does not apply, and(b): the UE received one of the categories a, b or c as part of the parameters for unified access control in the broadcast system information, and the UE is a member of the broadcasted category in the selected PLMN or RPLMN / equivalent PLMN(NOTE 3, NOTE 5, NOTE 6, NOTE 7, NOTE 8)1 (= delay tolerant)5MO MMTel voice call; orMT MMTel voice callAccess attempt is for MO MMTel voice call or MT MMTel voice callor for NAS signalling connection recovery during ongoing MO MMTel voice call or ongoing MT MMTel voice call (NOTE 2)4 (= MO MMTel voice).

[0123] Rule #Type of access attemptRequirements to be metAccess Category6MO MMTel video call; orMT MMTel video callAccess attempt is for MO MMTel video call or MT MMTel video callor for NAS signalling connection recovery during ongoing MO MMTel video call or ongoing MT MMTel video call (NOTE 2)5 (= MO MMTel video)7MO SMS over NAS or MO SMSoIP; orMT SMSoIPAccess attempt is for MO SMS over NAS (NOTE 4) or MO SMS over SMSoIP transfer or MT SMS over SMSoIPor for NAS signalling connection recovery during ongoing MO SMS or SMSoIP transfer or ongoing MT MMTel video call (NOTE 2)6 (= MO SMS and SMSoIP)7.1MO IMS registration related signallingAccess attempt is for MO IMS registration related signalling (e.g.IMS initial registration, re-registration, subscription refresh)or for NAS signalling connection recovery during ongoing procedure for MO IMS registration related signalling (NOTE 2a)9 (= MO IMS registration related signalling)8UE NAS initiated 5GMM specific proceduresAccess attempt is for MO signalling3 (= MO_sig)8.1Mobile originated location requestAccess attempt is for mobile originated location request (NOTE 9)3 (= MO_sig)8.2Mobile originated signalling transaction towards the PCFAccess attempt is for mobile originated signalling transaction towards the PCF (NOTE 10)3 (= MO_sig)8.3Access attempt for RAN timing synchronizationAccess attempt is for mobile originated signaling for the reconnection to the network due to RAN timing synchronization status change3 (= MO_sig)9UE NAS initiated 5GMM connection management procedure or 5GMM NAS transport procedureAccess attempt is for MO data7 (= MO_data)10An uplink user data packet is to be sent for a PDU session with suspended user-plane resourcesNo further requirement is to be met7 (= MO_data).

[0124] In addition, the current 3GPP standard defines the mapping relationship between the access category (Access Category) defined in Tables 2 and 3 and the RRC establishment reason as shown in Table 4 below.

[0125] Access categoriesRRC establishment (resume) cause is set toAny categorymps-PriorityAccessAny categorymcs-PriorityAccessAny categoryhighPriorityAccessAny categoryhighPriorityAccess0 (= MT_acc)mt-Access1 (= delay tolerant)Not applicable (NOTE 1)2 (= emergency)emergency3 (= MO_sig)mo-Signalling4 (= MO MMTel voice)mo-VoiceCall5 (= MO MMTel video)mo-VideoCall6 (= MO SMS and SMSoIP)mo-SMS7 (= MO_data)mo-Data9 (= MO IMS registration related signaling)mo-Data

[0126] However, the current 3GPP standard does not provide a way to distinguish between partially allowed NSSAIs and process access control according to the relevant traffic QoS and application service requirements. More specifically, the existing technology only allows service differentiation by NSSAI (S-NSSAI). For example, if a carrier wants to differentiate factory automation services by region or sector, or more specifically, differentiate home appliance factory automation services from battery manufacturing factory automation services, the current 3GPP standard does not provide such service differentiation.

[0127] In conclusion, there is a need for a method to perform access control by distinguishing signaling for traffic based on these partially permissive NSSAIs.

[0128]

[0129] Access control method considering partial allowable NSSAI

[0130] First, the present invention proposes adding a new access control category y, such as Table 5 below, to Table 2 or Table 3 described above for signaling and / or data related to Partially Allowed NSSAI (PANSSAI).

[0131] Rule #Type of access attemptRequirements to be metAccess CategoryxMO Partially Allowed NSSAI service requestAccess attempt is for mobile originated Partially allowed NSSAI related signaling and / or datay (= MO PANSSAI)

[0132] In addition, the present invention proposes adding an RRC connection establishment reason or an RRC connection resume reason as shown in Table 6 below in Table 4 described above for signaling and / or data related to Partially Allowed NSSAI (PANSSAI).

[0133] Access categoriesRRC connection establishment (resume) cause is set toy (=MO PANSSAI)mo-PANSSAI

[0134] The access control method of the present invention based on the suggestions in Tables 5 and 6 above can be performed as follows. Step 1) When a congestion situation occurs in the wireless section between a terminal and a base station, the base station (e.g., gNB, eNB, etc.) provides access control information (e.g., information such as UAC (Unified Access Control) category, barring time, barring factor, barring Identity, etc.) for signaling and / or data related to PANSSAI (Partially Allowed NSSAI) to the terminal in SIB1 (system information block 1) information.

[0135] Step 2) When MO (Mobile Oriented) PANSSAI signaling or data is generated in the application layer of the terminal, it can notify the NAS layer of the terminal. Thereafter, the NAS layer of the terminal determines the Access Category for the MO PANSSAI-related signaling and / or data, i.e., Access Category #y of Table 5 above, and transmits this together with Access Identity information to the RRC layer of the terminal. At this time, PANSSAI-related information can be transmitted to the RRC layer of the terminal along with the Access Identity information.

[0136] Step 3) The terminal RRC layer performs a UAC (Unified Access Control) check procedure based on i) connection identification information and ii) connection category #y for MO PANSSAI-related signaling and / or data (or i) connection identification information, ii) connection category #y for MO PANSSAI-related signaling and / or data and iii) PANSSAI-related information) provided from the NAS layer.

[0137] At this time, information about PANSSAI may be specific S-NSSAI information (e.g., S-NSSAI#1), specific S-NSSAI + Partial tracking area Identity information (e.g., Partial TAU list#1), or cell identity information (e.g., cellID#1).

[0138] Step 4) The terminal RRC layer sets "mo-PANSSAI", which is the RRC connection establishment reason or RRC connection resumption reason mapped to connection category #y as shown in Table 6, in the RRCSetupRequest message and transmits it to the base station. The base station performs QoS control / resource control / access control, etc. based on this.

[0139]

[0140] According to the present invention, when congestion occurs in a wireless section, signaling related to partially permitted NSSAI traffic can be distinguished, enabling efficient access control processing tailored to the QoS and application service requirements associated with partially permitted NSSAI traffic. This efficient access control processing can improve congestion situations and minimize battery and resource waste for both terminals and the network by reducing the overhead of unnecessary signaling.

[0141]

[0142] FIG. 6 is a diagram illustrating a method for performing an access control procedure according to one embodiment of the present invention. In particular, FIG. 6 assumes that the terminal supports PANSSAI (Partially allowed NSSAI) and has received relevant information from the network.

[0143] Referring to FIG. 6, the terminal recognizes that MO (Mobile Oriented) PANSSAI signaling or data has occurred (A05). Specifically, when MO PANSSAI signaling or data occurs in the application layer of the terminal, it can notify the NAS layer of the terminal.

[0144] Thereafter, the NAS layer of the terminal determines the access category for MO PANSSAI signaling or data as the access category #y of Table 5 (A10), and provides the determined access category #y together with access identity information to the RRC layer of the terminal (A15). As described above, PANSSAI-related information may also be provided to the terminal RRC layer. At this time, the information about PANSSAI may be specific S-NSSAI information (e.g., S-NSSAI#1), specific S-NSSAI + Partial tracking area Identity information (e.g., Partial TAU list#1), or cell identity information (e.g., cellID#1).

[0145] Next, the terminal RRC layer performs an access control procedure (A20) based on i) access identification information and ii) access category #y for MO PANSSAI-related signaling and / or data (or i) access identification information, ii) access category #y for MO PANSSAI-related signaling and / or data and iii) PANSSAI-related information) provided from the NAS layer.

[0146] Additionally, the terminal RRC layer sets "mo-PANSSAI", which is an RRC connection establishment reason or RRC connection resume reason mapped to access category #y, in the RRCSetupRequest message and transmits it to the base station (A25).

[0147]

[0148] Figure 7 shows a block diagram of a processor in which the disclosure of this specification is implemented.

[0149] As can be seen from FIG. 7, the processor (1020) implementing the disclosure of the present specification may include multiple circuits to implement the proposed functions, procedures, and / or methods described herein. For example, the processor (1020) may include a first circuit (1020-1), a second circuit (1020-2), and a third circuit (1020-3). Furthermore, although not shown, the processor (1020) may include more circuits. Each circuit may include multiple transistors.

[0150] The above processor (1020) may be called an ASIC (application-specific integrated circuit) or AP (application processor) and may include at least one of a DSP (digital signal processor), a CPU (central processing unit), and a GPU (graphics processing unit).

[0151] The above processor can be mounted on a UE.

[0152] Figure 8 illustrates a device according to one embodiment of the present specification.

[0153] Referring to FIG. 8, the wireless communication system may include a first device (100a) and a second device (100b).

[0154] The first device (100a) may be a UE described in the disclosure of this specification. Alternatively, the first device (100a) may be a base station, a network node, a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), an AI (Artificial Intelligence) module, a robot, an AR (Augmented Reality) device, a VR (Virtual Reality) device, an MR (Mixed Reality) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, a device related to 5G services, or any other device related to the field of the 4th Industrial Revolution.

[0155] The second device (100b) may be a network node (e.g., AMF or MME) described in the disclosure of this specification. Alternatively, the second device (100b) may be a base station, a network node, a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), an AI (Artificial Intelligence) module, a robot, an AR (Augmented Reality) device, a VR (Virtual Reality) device, an MR (Mixed Reality) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, a device related to 5G services, or any other device related to the field of the 4th Industrial Revolution.

[0156] For example, the UE (100) may include a mobile phone, a smart phone, a laptop computer, a digital broadcasting UE, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation device, a slate PC, a tablet PC, an ultrabook, a wearable device (e.g., a smartwatch, a smart glass, a head mounted display (HMD)), etc. For example, the HMD may be a display device worn on the head. For example, the HMD may be used to implement VR, AR, or MR.

[0157] For example, a drone may be an unmanned aircraft that flies by wireless control signals. For example, a VR device may include a device that implements virtual world objects or backgrounds. For example, an AR device may include a device that implements virtual world objects or backgrounds by connecting them to real world objects or backgrounds. For example, an MR device may include a device that implements virtual world objects or backgrounds by merging them with real world objects or backgrounds. For example, a holographic device may include a device that utilizes holography, a light interference phenomenon that occurs when two laser beams meet, to record and reproduce three-dimensional information to implement a 360-degree stereoscopic image. For example, a public safety device may include a video relay device or a wearable imaging device on the user's body. For example, MTC devices and IoT devices may be devices that do not require direct human intervention or operation. For example, MTC devices and IoT devices may include smart meters, bending machines, thermometers, smart light bulbs, door locks, or various sensors. For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, managing, or preventing a disease. For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, or correcting an injury or disability. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device may be a device used for the purpose of regulating pregnancy. For example, a medical device may include a diagnostic device, a surgical device, an (in vitro) diagnostic device, a hearing aid, or a device for a procedure. For example, a security device may be a device installed to prevent potential risks and maintain safety. For example, a security device may be a camera, CCTV, a recorder, or a black box.For example, a fintech device may be a device capable of providing financial services, such as mobile payments. For example, a fintech device may include a payment device or a point of sale (POS). For example, a climate / environmental device may include a device that monitors or predicts the climate / environment.

[0158] The first device (100a) may include at least one processor, such as a processor (1020a), at least one memory, such as a memory (1010a), and at least one transceiver, such as a transceiver (1031a). The processor (1020a) may perform the functions, procedures, and / or methods described above. The processor (1020a) may perform one or more protocols. For example, the processor (1020a) may perform one or more layers of a wireless interface protocol. The memory (1010a) may be connected to the processor (1020a) and may store various types of information and / or commands. The transceiver (1031a) may be connected to the processor (1020a) and may be controlled to transmit and receive wireless signals.

[0159] The second device (100b) may include at least one processor, such as a processor (1020b), at least one memory device, such as a memory (1010b), and at least one transceiver, such as a transceiver (1031b). The processor (1020b) may perform the functions, procedures, and / or methods described above. The processor (1020b) may implement one or more protocols. For example, the processor (1020b) may implement one or more layers of a wireless interface protocol. The memory (1010b) may be connected to the processor (1020b) and may store various types of information and / or commands. The transceiver (1031b) may be connected to the processor (1020b) and may be controlled to transmit and receive wireless signals.

[0160] The memory (1010a) and / or the memory (1010b) may be connected internally or externally to the processor (1020a) and / or the processor (1020b), or may be connected to another processor via various technologies such as a wired or wireless connection.

[0161] The first device (100a) and / or the second device (100b) may have one or more antennas. For example, the antenna (1036a) and / or the antenna (1036b) may be configured to transmit and receive wireless signals.

[0162] FIG. 9 illustrates a block diagram of a network node according to one embodiment of the present specification.

[0163] In particular, FIG. 9 is a drawing that illustrates in detail a case where a base station is divided into a central unit (CU) and a distributed unit (DU).

[0164] Referring to FIG. 9, the base stations (W20, W30) may be connected to the core network (W10), and the base station (W30) may be connected to the neighboring base station (W20). For example, the interface between the base stations (W20, W30) and the core network (W10) may be referred to as NG, and the interface between the base station (W30) and the neighboring base station (W20) may be referred to as Xn.

[0165] The base station (W30) can be divided into a CU (W32) and DUs (W34, W36). That is, the base station (W30) can be operated hierarchically separated. The CU (W32) can be connected to one or more DUs (W34, W36), and for example, the interface between the CU (W32) and the DUs (W34, W36) can be referred to as F1. The CU (W32) can perform functions of upper layers of the base station, and the DUs (W34, W36) can perform functions of lower layers of the base station. For example, the CU (W32) may be a logical node hosting radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layers of a base station (e.g., gNB), and the DUs (W34, W36) may be logical nodes hosting radio link control (RLC), media access control (MAC), and physical (PHY) layers of the base station. Alternatively, the CU (W32) may be a logical node hosting RRC and PDCP layers of a base station (e.g., en-gNB).

[0166] The operation of DU (W34, W36) can be partially controlled by CU (W32). One DU (W34, W36) can support more than one cell. One cell can be supported by only one DU (W34, W36). One DU (W34, W36) can be connected to one CU (W32), and by suitable implementation, one DU (W34, W36) can also be connected to multiple CUs.

[0167] Fig. 10 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0168] In particular, the terminal, i.e., UE (100) illustrated in FIG. 10 is a drawing that exemplifies the first device of FIG. 8 in more detail.

[0169] The UE (100) includes a memory (1010), a processor (1020), a transceiver (1031), a power management module (1091), a battery (1092), a display (1041), an input unit (1053), a speaker (1042), a microphone (1052), a subscriber identification module (SIM) card, and one or more antennas.

[0170] The processor (1020) may be configured to implement the proposed functions, procedures and / or methods described herein. Layers of a wireless interface protocol may be implemented in the processor (1020). The processor (1020) may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. The processor (1020) may be an application processor (AP). The processor (1020) may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of the processor (1020) may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO™ series processor manufactured by MediaTek®, an ATOM™ series processor manufactured by INTEL®, or a corresponding next-generation processor.

[0171] The power management module (1091) manages power to the processor (1020) and / or the transceiver (1031). The battery (1092) supplies power to the power management module (1091). The display (1041) outputs the results processed by the processor (1020). The input unit (1053) receives input to be used by the processor (1020). The input unit (1053) can be displayed on the display (1041). A SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and its associated keys, which are used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Contact information can also be stored on many SIM cards.

[0172] The memory (1010) is operably coupled to the processor (1020) and stores various information for operating the processor (610). The memory (1010) may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. When the embodiment is implemented in software, the techniques described herein may be implemented as modules (e.g., procedures, functions, etc.) that perform the functions described herein. The modules may be stored in the memory (1010) and executed by the processor (1020). The memory (1010) may be implemented within the processor (1020). Alternatively, the memory (1010) may be implemented external to the processor (1020) and communicatively connected to the processor (1020) via various means known in the art.

[0173] The transceiver (1031) is operably coupled to the processor (1020) and transmits and / or receives a radio signal. The transceiver (1031) includes a transmitter and a receiver. The transceiver (1031) may include a baseband circuit for processing a radio frequency signal. The transceiver controls one or more antennas to transmit and / or receive a radio signal. The processor (1020) transmits command information to the transceiver (1031) to initiate communication, for example, to transmit a radio signal constituting voice communication data. The antenna functions to transmit and receive radio signals. Upon receiving a radio signal, the transceiver (1031) may transmit the signal for processing by the processor (1020) and convert the signal to baseband. The processed signal may be converted into audible or readable information output through the speaker (1042).

[0174] The speaker (1042) outputs sound-related results processed by the processor (1020). The microphone (1052) receives sound-related input to be used by the processor (1020).

[0175] A user inputs command information, such as a phone number, for example, by pressing (or touching) a button on an input unit (1053) or by voice activation using a microphone (1052). The processor (1020) receives this command information and processes it to perform an appropriate function, such as dialing a phone number. Operational data can be extracted from a SIM card or memory (1010). In addition, the processor (1020) can display command information or operation information on a display (1041) for the user's recognition and convenience.

[0176] FIG. 11 is a block diagram showing in detail the transmitter / receiver of the first device illustrated in FIG. 8 or the transmitter / receiver unit of the device illustrated in FIG. 10.

[0177] Referring to FIG. 11, the transceiver (1031) includes a transmitter (1031-1) and a receiver (1031-2). The transmitter (1031-1) includes a Discrete Fourier Transform (DFT) unit (1031-11), a subcarrier mapper (1031-12), an IFFT unit (1031-13), a CP insertion unit (1031-14), and a wireless transmitter (1031-15). The transmitter (1031-1) may further include a modulator. In addition, for example, the transmitter may further include a scramble unit (not shown), a modulation mapper (not shown), a layer mapper (not shown), and a layer permutator (not shown), which may be arranged before the DFT unit (1031-11). That is, in order to prevent an increase in PAPR (peak-to-average power ratio), the transmitter (1031-1) first passes the information through a DFT (1031-11) before mapping the signal to a subcarrier. The signal spread (or precoded in the same sense) by the DFT unit (1031-11) is mapped to a subcarrier through a subcarrier mapper (1031-12) and then passes through an IFFT (Inverse Fast Fourier Transform) unit (1031-13) to be converted into a signal on the time axis.

[0178] The DFT unit (1031-11) performs DFT on the input symbols and outputs complex-valued symbols. For example, when Ntx symbols are input (where Ntx is a natural number), the DFT size is Ntx. The DFT unit (1031-11) may be called a transform precoder. The subcarrier mapper (1031-12) maps the complex symbols to each subcarrier in the frequency domain. The complex symbols may be mapped to resource elements corresponding to resource blocks allocated for data transmission. The subcarrier mapper (1031-12) may be called a resource element mapper. The IFFT unit (1031-13) performs IFFT on the input symbols and outputs a baseband signal for data, which is a time-domain signal. The CP insertion unit (1031-14) copies a portion of the rear portion of the baseband signal for data and inserts it into the front portion of the baseband signal for data. CP insertion prevents ISI (Inter-Symbol Interference) and ICI (Inter-Carrier Interference), thereby maintaining orthogonality even in multipath channels.

[0179] On the other hand, the receiver (1031-2) includes a wireless reception unit (1031-21), a CP removal unit (1031-22), an FFT unit (1031-23), and an equalization unit (1031-24). The wireless reception unit (1031-21), the CP removal unit (1031-22), and the FFT unit (1031-23) of the receiver (1031-2) perform the inverse functions of the wireless transmission unit (1031-15), the CP insertion unit (1031-14), and the IFF unit (1031-13) of the transmitter (1031-1). The receiver (1031-2) may further include a demodulator.

[0180] FIG. 12 illustrates another wireless communication system applicable to the disclosure of this specification.

[0181] The various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the disclosure of this specification can be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0182] Referring to FIG. 12, a communication system (1) applicable to the disclosure of the present specification includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0183] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0184] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the disclosure of the present specification.

[0185] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to such specific embodiments, and may be modified, changed, or improved in various forms within the scope described in the spirit and claims of this specification.

[0186] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0187] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In a method for operating a terminal in a wireless communication system, When data related to MO (Mobile Oriented) PANSSAI (partially allowed network slice selection assistance information) is generated, a specific connection category for the MO PANSSAI responsive connection attempt is determined in the NAS (Non Access Stratum) layer of the terminal, Provides connection identification information and information about the specific connection category from the NAS layer of the terminal to the RRC (Radio Resource Control) layer, In the RRC layer of the terminal, performing a connection control procedure based on the connection identification information and information about the specific connection category, How the terminal operates.

2. In paragraph 1, In the RRC layer of the terminal, further comprising transmitting an RRC connection setup message including an RRC connection establishment reason (cause) to the network, The reason for establishing the above RRC connection is: Corresponding to a specific connection category for the above MO PANSSAI response connection attempt, How the terminal operates.

3. In paragraph 1, Further comprising receiving information for performing the above PANSSAI related access control procedure from the network through SIB1 (System Information Block Type1). How the terminal operates.

4. In paragraph 1, Performing the above access control procedure is as follows: Including performing a Unified Access Control (UAC) check based on the above connection identification information, information about the specific connection category, and PANSSAI-related information. How the terminal operates.

5. In paragraph 4, The above PANSSAI related information is: Containing information of a specific NSSAI and TA (Tracking Area) identifier information corresponding to the specific NSSAI, How the terminal operates.

6. In a terminal in a wireless communication system, Transmitter and receiver; at least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, Based on the above instruction being executed by the at least one processor, the operations performed are: When data related to MO (Mobile Oriented) PANSSAI (partially allowed network slice selection assistance information) is generated, a specific connection category for the MO PANSSAI responsive connection attempt is determined in the NAS (Non Access Stratum) layer of the terminal, Provides connection identification information and information about the specific connection category from the NAS layer of the terminal to the RRC (Radio Resource Control) layer, In the RRC layer of the terminal, performing a connection control procedure based on the connection identification information and information about the specific connection category, Terminal.

7. In paragraph 6, In the RRC layer of the terminal, further comprising transmitting an RRC connection setup message including an RRC connection establishment reason (cause) to the network, The reason for establishing the above RRC connection is: Corresponding to a specific connection category for the above MO PANSSAI response connection attempt, Terminal.

8. In paragraph 6, Further comprising receiving information for performing the above PANSSAI related access control procedure from the network through SIB1 (System Information Block Type1). Terminal.

9. In paragraph 6, Performing the above access control procedure is as follows: Including performing a Unified Access Control (UAC) check based on the above connection identification information, information about the specific connection category, and PANSSAI-related information. Terminal.

10. In paragraph 9, The above PANSSAI related information is: Containing information of a specific NSSAI and TA (Tracking Area) identifier information corresponding to the specific NSSAI, Terminal.

Images