Access control mechanism for signaling or data for industrial traffic

Abstract

One disclosure of the present specification proposes an operation method at a terminal. The method may comprise: a step of receiving, from a base station, system information including access control-related information on industrial signaling and / or data; a step of sending industrial signaling or data and determining an access type according to the access identifier; a step of performing a check for access control (Unified Access Control) on the basis of the access type and the access control related information; a step for determining a radio resource control (RRC) establishment cause or an RRC recovery cause on the basis of the access type when the access type has passed from the check, and a step for determining a radio resource control (RRC) establishment cause or an RRC recovery cause on the basis of the access type; and a step of transmitting, to the base station, an RRC message including the determined RRC establishment cause or RRC recovery cause.

Description

Technical Field

[0001] This specification relates to mobile communications. Background Art

[0002] Based on the success of the fourth generation of mobile communications, long term evolution (LTE) / LTE-Advanced (LTE-A), interest in the next generation, the fifth generation (so-called 5G) mobile communications is increasing, and research work is progressing.

[0003] The fifth generation of mobile communications defined by the International Telecommunication Union (ITU) is to provide data transmission speeds of up to 20Gbps and experience transmission speeds of at least 100Mbps anywhere. The official name is "IMT-2020" and the goal is to achieve commercialization worldwide in 2020.

[0004] The fifth generation of mobile communications supports multiple numerologies or subcarrier spacing (SCS) to support various services. For example, if the SCS is 15kHz, it supports wide area of ​​traditional cellular bands, if the SCS is 30kHz / 60kHz, it supports dense-urban, lower latency and wider carrier bandwidth, and when the SCS is above 60kHz, it supports bandwidth greater than 24.25GHz in order to overcome phase noise.

[0005] The NR frequency band is defined as two types of frequency ranges (FR1 and FR2). FR1 is 410MHz–7125MHz, and FR2 is 24250MHz–52600MHz, which can mean millimeter wave (mmW).

[0006] For the sake of convenience, in the frequency range used in the NR system, FR1 can represent "range below 6 GHz", FR2 can represent "range above 6 GHz", and can be called millimeter wave (millimeter wave, mmW).

[0007] [Table 1]

[0008]

[0009]

[0010] As described above, the value of the frequency range of the NR system can be changed. For example, FR1 may include a frequency band from 410 MHz to 7125 MHz, as shown in Table A7 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included in FR1 may include unlicensed bands. Unlicensed bands can be used for a variety of purposes, for example, for vehicle communications (e.g., autonomous driving).

[0011] [Table 2]

[0012] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz–7125MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0013] The ITU suggests three major usage scenarios: for example, eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication) and URLLC (Ultra Reliable and Low Latency Communications).

[0014] First, URLLC involves usage scenarios that require high reliability and low latency. For example, services such as autonomous driving, factory automation, and augmented reality require high reliability and low latency (e.g., latency below 1ms). The current 4G (LTE) latency is statistically 21-43ms (best 10%) and 33-75ms (middle). This is not enough to support services that require latency below 1ms.

[0015] Next, eMBB use cases involve use cases that require mobile ultra-wideband.

[0016] This ultra-wideband high-speed service seems difficult to be accommodated by the existing LTE / LTE-A designed core network.

[0017] Therefore, in the so-called fifth generation of mobile communications, there is an urgent need to redesign the core network.

[0018] Figure 1 is a diagram showing the structure of a next generation mobile communication network.

[0019] 5GC (5G Core) can include various components. Figure 1Including the Access and Mobility Management Function (AMF) 41, Session Management Function (SMF) 42, Policy Control Function (PCF) 43, User Plane Function (UPF) 44, Application Function (AF) 45, Unified Data Management (UDM) 46, and Non-3GPP InterWorking Function (Non-3GPP InterWorking Function) 49, which are part of it.

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

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

[0022] Figure 2 is an example showing the expected structure of the next generation mobile communication from the perspective of nodes.

[0023] refer to Figure 2 It can be seen that the UE is connected to the data network (DN) through the next generation Radio Access Network (RAN).

[0024] The control plane function (CPF) node shown performs all or part of the mobility management entity (MME) functions of the fourth generation mobile communication, as well as all or part of the control plane functions of the serving gateway (S-GW) and the PDN gateway (P-GW). The CPF node includes an access and mobility management function (AMF) and a session management function (SMF).

[0025] The user plane function (UPF) node shown is a type of gateway for sending and receiving user data. The UF node can perform all or part of the user plane functions of the S-GW and P-GW of the fourth generation mobile communication.

[0026] The Policy Control Function (PCF) shown is a node that controls operator policies.

[0027] The application function (AF) shown is a server that provides various services to UE.

[0028] The Unified Data Management (UDM) shown is a server that manages subscriber information, such as the Home Subscriber Server (HSS) of the fourth generation mobile communication. The UDM stores the subscriber information in a Unified Data Repository (UDR) and manages it.

[0029] The Authentication Server Function (AUSF) shown authenticates and manages the UE.

[0030] The Network Slice Selection Function (NSSF) shown is a node for network slicing as described later.

[0031] exist Figure 2In the present invention, the UE uses multiple protocol data units or packet data units (PDU) sessions to access two data networks simultaneously.

[0032] Figure 3 is a diagram showing an example of an architecture that supports simultaneous access to two data networks.

[0033] exist Figure 3 It shows the architecture where the UE uses one PDU session to access two data networks simultaneously.

[0034] Figure 2 and Figure 3 The reference points shown are as follows.

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

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

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

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

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

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

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

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

[0043] N9 represents the reference point between UPFs.

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

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

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

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

[0048] N14 represents the reference point between AMFs.

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

[0050] N16 represents the reference point between SMFs.

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

[0052] Figure 4 is another example diagram showing the structure of the Radio Interface Protocol between UE and gNB.

[0053] The wireless interface protocol is based on the 3GPP wireless access network standard. The wireless interface protocol consists of the physical layer, data link layer and network layer horizontally, and is divided into the user plane (User Plane) for data information transmission and the control plane (Control Plane) for control signal transmission vertically.

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

[0055] Each layer of the wireless protocol is described below.

[0056] The first layer, the physical layer, uses a physical channel to provide information transfer services. The physical layer is connected to the upper media access control layer through a transport channel, and data between the media access control layer and the physical layer is transferred through the transport channel. In addition, data is transmitted between different physical layers, that is, between the physical layers on the sending side and the receiving side, through the physical channel.

[0057] The second layer includes the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer and the Packet Data Convergence Protocol (PDCP) layer.

[0058] The third layer includes Radio Resource Control (RRC). The RRC layer is defined only in the control plane and is related to the establishment (setting), reset (Resetting) and release (Release) of Radio Bearers (RBs), and is responsible for the control of logical channels, transport channels, and physical channels. At this time, RB means the service provided by the second layer for data transmission between the terminal and E-UTRAN.

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

[0060] The NAS layer is divided into a NAS entity for mobility management (MM) and a NAS entity for session management (SM).

[0061] 1) The NAS entity for MM generally provides the following functions.

[0062] As NAS processes related to AMF, they include:

[0063] -Registration management and access management process, AMF supports the following functions:

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

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

[0066] The SM signaling message is processed at the NAS-SM layer between the UE and the SMF, i.e. created and processed. The content of the SM signaling message is not interpreted by the AMF.

[0067] -When sending SM signaling,

[0068] - The NAS entity for MM creates a NAS-MM message indicating the security header for NAS transmission of SM signaling, and derives the method and location of delivering SM signaling messages through the received additional information for NAS-MM.

[0069] - When receiving SM signaling, the NAS entity for SM performs an integrity check of the NAS-MM message and interprets the additional information to deduce the method and location of the SM signaling message.

[0070] At the same time, Figure 4 In the wireless communication network, the RRC layer, RLC layer, MAC layer and PHY layer located below the NAS layer are collectively referred to as the access stratum (AS).

[0071] The network system (ie, 5GC) for the next generation mobile communication (ie, 5G) also supports non-3GPP access. A representative example of non-3GPP access is WLAN access. WLAN access can include trusted WLAN and untrusted WLAN.

[0072] In the system used for 5G, AMF not only performs 3GPP access, but also performs registration management (RM) and connection management (CM) for non-3GPP access.

[0073] At the same time, in the future ultra-connected intelligent information society of the Fourth Industrial Revolution and 5G mobile communications, ultra-low latency (Ultra Reliable Low Latency Communications, URLLC) network technology, which is used to organically connect and exchange and process information between people and objects, online and offline, is becoming a necessary technology based on network infrastructure.

[0074] As part of URLLC network technologies such as Time Sensitive Networking (TSN) are being introduced for industrial use.

[0075] However, there is a problem that there is no method for distinguishing industrial traffic-related signaling and processing access control according to industrial traffic-related QoS and application service requirements. Summary of the invention

[0076] Technical issues

[0077] Therefore, the purpose of the present specification is to propose a method for solving the above problems.

[0078] Technical Solution

[0079] In order to solve the above problem, an operation method in a terminal is provided. The method may include: a step of receiving system information containing access control related information for industrial signaling and / or data from a base station; a step of determining an access category according to an access identifier when sending industrial signaling or data; a step of performing a check for access control (Unified Access Control) based on the access category and the access control related information; a step of determining a radio resource control (RRC) establishment cause or a radio resource control recovery cause based on the access category in the case of passing the check; and a step of sending a radio resource control message including the determined radio resource control establishment cause or radio resource control recovery cause to the base station.

[0080] In order to solve the above problem, a chipset installed in a terminal is provided. The chipset includes: at least one processor; and at least one memory storing instructions and being operably electrically connected to the at least one processor, and being executed by the at least one processor based on the instructions, and the operations performed include: receiving system information containing access control related information for industrial signaling and / or data from a base station; determining an access category according to an access identifier when sending industrial signaling or data; performing a check for access control (Unified Access Control) based on the access category and the access control related information; determining a Radio Resource Control (RRC) establishment cause or an RRC recovery cause based on the access category in the case of passing the check; and sending an RRC message including the determined RRC establishment cause or RRC recovery cause to the base station.

[0081] In order to solve the above problem, a device for a terminal is provided. The device may include: a transceiver unit; at least one processor; and at least one memory, which stores instructions and is operably electrically connected to the at least one processor, and is executed by the at least one processor based on the instructions, and the operations performed include: a step of receiving system information containing access control related information for industrial signaling and / or data from a base station; a step of determining an access category according to an access identifier when sending industrial signaling or data; a step of performing a check for access control (Unified Access Control) based on the access category and the access control related information; a step of determining a Radio Resource Control (RRC) establishment cause or an RRC recovery cause based on the access category if the check passes; and a step of sending an RRC message including the determined RRC establishment cause or RRC recovery cause to the base station.

[0082] Effects of the Invention

[0083] By distinguishing the signaling related to industrial traffic (e.g., TSN traffic, TSC traffic, DetNet traffic, URLLC traffic, or IIoT traffic) and in the case of congestion in the wireless section, access control can be effectively processed according to the QoS and application service requirements related to industrial traffic (e.g., TSN traffic, TSC traffic, DetNet traffic, URLLC traffic, or IIoT traffic). Such efficient access control processing can improve congestion conditions and reduce unnecessary signaling overhead to minimize battery and resource waste of terminals and networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] Figure 1 is a diagram showing the structure of a next generation mobile communication network.

[0085] Figure 2 is an example showing the expected structure of the next generation mobile communication from the perspective of nodes.

[0086] Figure 3 is a diagram showing an example of an architecture that supports simultaneous access to two data networks.

[0087] Figure 4 is another example diagram showing the structure of the Radio Interface Protocol between UE and gNB.

[0088] Figure 5a and 5b is a signal flow diagram illustrating an exemplary PDU session establishment process.

[0089] Figure 6a and Figure 6b It shows the modification process of the PDU session.

[0090] Figure 7 is a diagram showing an example of a network architecture that interoperates with a TSN network.

[0091] Figure 8 is an example diagram illustrating an architecture that supports time-sensitive communications and time synchronization services.

[0092] Fig. 9 FIG. 1 is a diagram showing an example of a disclosure according to the present specification.

[0093] Fig.10 is a block diagram showing the configuration of a processor that implements the disclosure of this specification.

[0094] Fig.11 FIG. 2 is a diagram showing a wireless communication system according to an embodiment.

[0095] Fig.12 is a block diagram illustrating a network node according to an embodiment.

[0096] Fig.13 is a block diagram showing the configuration of UE 100 according to an embodiment.

[0097] Fig.14 It is shown in Fig.11 The transceiver unit of the first device shown in FIG. Fig.13 A block diagram of the transceiver unit of the device shown.

[0098] Fig.15 1 is a diagram showing a communication system 1 applicable to the disclosure of this specification. DETAILED DESCRIPTION

[0099] It should be noted that the technical terms used in this specification are only used to describe specific embodiments and are not intended to limit the contents of this specification. In addition, unless specifically defined in different ways in this specification, the technical terms used in this specification should be interpreted as the meanings commonly understood by technicians in the technical field to which the disclosure of this specification belongs, and should not be interpreted as over-generalized meanings or over-reduced meanings. In addition, if the technical terms used in this specification are incorrect technical terms that cannot accurately express the contents and ideas of this specification, they should be replaced with technical terms that can be correctly understood by those skilled in the art. In addition, the general terms used in this specification should be interpreted as defined in the dictionary or according to the context, and should not be interpreted as over-reduced meanings.

[0100] In addition, singular expressions as used in this specification include plural expressions unless the context clearly indicates otherwise. In this application, terms such as "consisting of" or "having" should not be interpreted as necessarily including all the various constituent elements or steps described in the specification, and may not include some constituent elements or steps, or should be interpreted as also including additional constituent elements or steps.

[0101] In addition, the terms including ordinal numbers such as first, second, etc. used in this specification can be used to describe various constituent elements, but the constituent elements should not be limited by the terms. The terms are only used to distinguish one constituent element from another constituent element. For example, without departing from the scope of the rights, the first constituent element can be named as the second constituent element, and similarly, the second constituent element can also be named as the first constituent element.

[0102] When a component is mentioned as being connected or accessed to another component, it can be directly connected or accessed to another component, but other components may also exist in between. On the other hand, when it is mentioned that a component is directly connected or directly accessed to another component, it should be understood that there are no other components in between.

[0103] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings, but the same or similar constituent elements will be given the same figure marks regardless of the drawing symbols, and repeated descriptions thereof will be omitted. In addition, when interpreting the contents of this specification, if it is determined that the detailed description of the relevant known technology may obscure the gist of this specification, its detailed description will be omitted. In addition, it should be noted that the drawings are only for the purpose of facilitating the understanding of the contents and ideas of this specification, and should not be understood as limiting the contents and ideas of this specification by the drawings. The contents and ideas of this specification should be interpreted as extending to all changes, equivalents or substitutes other than the drawings.

[0104] In the present specification, "A or B" may mean "only A", "only B", or "both A and B". In other words, in the present specification, "A or B" may be interpreted as "A and / or B". For example, in the present specification, "A, B or C" may mean "only A", "only B", "only C", or "any combination of A, B and C".

[0105] A slash ( / ) or a comma used in this specification may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0106] In the present specification, "at least one of A and B" may mean "only A", "only B", or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present specification may be interpreted the same as "at least one of A and B".

[0107] In addition, in the present specification, "at least one of A, B, and C" may mean "only A", "only B", "only C", or "any combination of A, B, and C". In addition, "at least one of A, B, or C" or "at least one of A, B and / or C" may mean "at least one of A, B, and C".

[0108] In addition, brackets used in this specification may indicate "for example". Specifically, when expressed as "control information (PDCCH)", "PDCCH" is suggested as an example of "control information". In other words, the "control information" of this specification is not limited to "PDCCH", and "PDDCH" may be suggested as an example of "control information". In addition, when expressed as "control information (ie, PDCCH)", "PDCCH" may also be suggested as an example of "control information".

[0109] The technical features described separately in one of the drawings of this specification can be implemented individually or simultaneously.

[0110] In the drawings, a user equipment (UE) is shown by way of example, but the UE shown can also be referred to by terms such as UE 100 (terminal), mobile equipment, etc. In addition, the UE can be a portable device such as a laptop computer, mobile phone, PDA, smart phone or multimedia device, or can be a non-portable device such as a PC or in-vehicle device.

[0111] <PDU Session Establishment Procedure>

[0112] There can be the following two types of PDU session establishment procedures for the protocol data unit (PDU) session establishment procedure.

[0113] - PDU session establishment procedure initiated by the UE

[0114] - PDU session establishment procedure initiated by the network. For this, the network can send a device trigger message to the application of the UE.

[0115] Figure 5a and 5b are signal flow diagrams showing exemplary PDU session establishment procedures.

[0116] Figure 5a and Figure 5b The procedures shown are based on the registration procedure shown in Figure 5, assuming that the UE has already registered with the AMF. Therefore, it is assumed that the AMF has obtained the user subscription data from the UDM.

[0117] 1) The UE sends a NAS message to the AMF. The message packet can include single network slice selection assistance information (S-NSSAI), data network name (DNN), PDU session ID, request type, and N1 SM information, etc.

[0118] Specifically, the UE includes S-NSSAI from the NSSAI allowed by the current access category. If the information about the mapped NSSAI has been provided to the UE, the UE may provide all S-NSSAI based on the allowed NSSAI and corresponding S-NSSAI based on the information of the mapped NSSAI. The mapped NSSAI information is information that maps each S-NSSAI in the allowed NSSAI to the S-NSSAI of the NSSAI set for the Home Public Land Mobile Network (HPLMN).

[0119] More specifically, the UE may extract and store the information of the S-NSSAI and the mapped S-NSSAI in the registration process of FIG. 5 including the registration acceptance message received from the network (ie, AMF). Therefore, the UE includes the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on the information of the mapped NSSAI in the PDU session establishment request message and sends it.

[0120] To establish a new PDU session, the UE may create a new PDU session ID.

[0121] The UE may send a NAS message including a PDU Session Establishment Request message in the N1 SM information to start the PDU Session Establishment procedure initiated by the UE. The PDU Session Establishment Request message may include a request type, SSC mode, and protocol configuration options.

[0122] If the PDU session establishment is for setting up a new PDU session, the request type indicates "initial request". However, if there is an existing PDU session between the 3GPP access and the non-3GPP access, the request type may indicate "existing PDU session".

[0123] The NAS message sent by the UE is encapsulated in an N2 message by the AN. The N2 message is transmitted to the AMF and may include user location information and access technology type information.

[0124] -N1 SM information may include a SM PDU DN request container, which contains information for PDU session authentication by an external DN.

[0125] 2) If the message indicates that the request type is "initial request" and the PDU Session ID does not have an existing PDU Session for the UE, the AMF may determine that it is a request for a new PDU Session.

[0126] If the NAS message does not contain S-NSSAI, the AMF may determine the requested default S-NSSAI for the PDU session based on the UE joining. The AMF may correlate the PDU session ID and the SMF ID and store them.

[0127] AMF can select SMF.

[0128] 3)AMF may send a Nsmf_PDUSession_CreateSMContext request message or a Nsmf_PDUSession_UpdateSMContext request message to the selected SMF.

[0129] The Nsmf_PDUSession_CreateSMContext request message may include SUPI, DNN, S-NSSAI(s), PDU session ID, AMF ID, request type, PCF ID, priority access, N1 SM container, user location information, access category, PEI, GPSI, UE presence in LADN service area, join PDU session state notification, DNN selection mode and tracking requirements. The SM container may include the PDU session establishment request message.

[0130] The Nsmf_PDUSession_UpdateSMContext request message may include SUPI, DNN, S-NSSAI, SMContext ID, AMFID, request type, N1 SM container, user location information, access category, RAT type, and PEI. The N1 SM container may include a PDU session establishment request message.

[0131] The AMF ID is used to identify the AMF serving the UE. The N1 SM information may include a PDU session establishment request message received from the UE.

[0132] 4) SMF sends a user data request message to UDM. The joiner data request message may include the joiner permanent ID and DNN. UDM may send a join data response message to SMF.

[0133] In the above process 3, if the request type indicates "existing PDU session", the SMF determines that the request is due to the transition between 3GPP access and non-3GPP access. The SMF can identify the existing PDU session based on the PDU session ID.

[0134] If the SMF has not retrieved the SM-related joining data for the UE related to the DNN, the SMF can request the joining data.

[0135] The joining data may include information about the authenticated request type, authenticated SSC mode, and basic QoS profile.

[0136] SMF can confirm whether the UE request complies with the user joining and local policies. Alternatively, SMF rejects the UE request through NAS SM signaling (including the relevant SM rejection reason) sent by AMF, and SMF notifies AMF that the PDU session ID should be considered to be released.

[0137] 5)SMF sends Nsmf_PDUSession_CreateSMContextResponse message or Nsmf_PDUSession_UpdateSMContextResponse message to AMF.

[0138] The Nsmf_PDUSession_CreateSMContextResponse message may include Cause, SM ContextID or N1 SM container. The N1 SM container may include PDU Session Reject.

[0139] In the above process 3, SMF receives the Nsmf_PDUSession_CreateSMContext request message. If SMF can process the PDU session establishment request message, it creates the SMF SM Context and passes the SM Context ID to AMF.

[0140] 6) Optionally perform secondary authentication / authorization.

[0141] 7a) If operating PCC is used for the PDU session, the SMF selects PCF.

[0142] 7b) In order to establish an SM policy association with the PCF, the SMF executes the SM policy association establishment process.

[0143] 8) If the request type in process 3 indicates "initial request", the SMF selects the SSC mode for the PDU session. If process 5 is not performed, the SMF may also select the UPF. For request type IPv4 or IPv6, the SMF may allocate an IP address / prefix for the PDU session.

[0144] 9)SMF executes the SM policy association modification program and provides information on the triggering conditions for the policy control request.

[0145] 10) The request type indicates "initial request" and the SMF uses the selected UPF to initiate the N4 session establishment process. If not, the SMF can use the selected UPF to initiate the N4 session modification process.

[0146] 10a) SMF sends N4 Session Establishment / Modification Request message to UPF. Also, SMF can provide packet detection, enforcement and reporting rules to be installed in UPF for PDU session. When SMF allocates CN tunnel information, CN tunnel information can be provided to UPF.

[0147] 10b) UPF sends N4 Session Establishment / Modification Response message so that it can respond. If CN tunnel information is allocated by UPF, CN tunnel information can be provided to SMF.

[0148] 11)SMF sends Namf_Communication_N1N2MessageTransfer message to AMF. The Namf_Communication_N1N2MessageTransfer message may include PDU session ID, N2SM information and N1 SM container.

[0149] The N2 SM information may include PDU session ID, QFI (QoS flow ID), QoS profile, CN tunnel information, S-NSSAI from allowed NSSAI, session AMBR, PDU session type, user plane security enforcement information, UE integrity protection maximum data rate.

[0150] The N1 SM container may include a PDU Session Establishment Accept message.

[0151] The PDU Session Establishment Accept message may include allowed QoS rules, SSC mode, S-NSSAI, and allocated IPv4 address.

[0152] 12)AMF sends an N2 PDU Session Request message to RAN. The message may include N2 SM information and NAS message. The NAS message may include PDU Session ID and PDU Session Establishment Accept message.

[0153] AMF may send a NAS message including PDU Session ID and PDU Session Establishment Accept message. In addition, AMF includes the received N2 SM information from SMF in the N2 PDU Session Request message and sends it to RAN.

[0154] 13) The RAN may perform specific signaling exchanges with the UE related to the information received from the SMF.

[0155] The RA also allocates RAN N3 tunnel information for the PDU session.

[0156] The RAN delivers the NAS message provided in process 10 to the UE. The NAS message may include the PDU session ID and N1 SM information. The N1 SM information may include a PDU session establishment accept message.

[0157] The RAN sends a NAS message to the UE only when the necessary RAN resources are set up and the allocation of the RAN tunnel information is successful.

[0158] 14) RAN sends an N2 PDU Session Response message to AMF. The message may include PDU Session ID, cause and N2 SM information. N2 SM information may include PDU Session ID, (AN) tunnel information and a list of allowed / rejected QoS profiles.

[0159] -RAN tunnel information may belong to the access network address of the N3 tunnel corresponding to the PDU session.

[0160] 15) AMF may send a Nsmf_PDUSession_UpdateSMContext request message to SMF. The Nsmf_PDUSession_UpdateSMContext request message may include N2 SM information. AMF may send the N2 SM information received from RAN to SMF.

[0161] 16a) If the N4 session for the PDU session has not been established, the SMF can initiate the N4 session establishment process with the UPF. Otherwise, the SMF can initiate the N4 session modification process with the UPF. The SMF can provide the AN tunnel information and the CN tunnel information. The CN tunnel information needs to be provided only when the SMF selects the CN tunnel information in process 8.

[0162] 16b) UPF may send an N4 session modification response message to SMF.

[0163] 17)SMF sends Nsmf_PDUSession_UpdateSMContextResponse message to AMF.

[0164] After the process is completed, AMF can pass related events to SMF.

[0165] 18)SMF sends Nsmf_PDUSession_SMContextStatusNotify message.

[0166] 19) SMF sends information to UE via UPF. Specifically, for PDU type IPv6, SMF can create IPv6 router advertisement and transmit it to UE via N4 and UPF.

[0167] 20) If the PDU session establishment is not successful during this process, the SMF notifies the AMF.

[0168] <PDU Session Modification Procedure>

[0169] Figure 6a and Figure 6b shows the modification procedure of the PDU session.

[0170] The PDU session is established / managed based on the PDU session modification procedure.

[0171] The PDU session modification procedure can be initiated by the UE or can be initiated by the network.

[0172] 1a) If initiated by the UE: The UE can initiate the PDU session modification procedure by sending a NAS message. The NAS message can include an N1 SM container. The N1 SM container can include a PDU session modification request message, a PDU session ID, and information about the UE's maximum data rate for integrity protection. The PDU session modification request message can include a PDU session ID, packet filters, requested QoS, 5GSM core network functions, and the number of packet filters. The UE's maximum data rate for integrity protection indicates the maximum data rate that the UE can support for UP integrity protection. The number of packet filters represents the number of packet filters supported for QoS rules.

[0173] The NAS message is sent through the RAN and to the appropriate AMF according to the UE's location information. Then, the AMF sends an Nsmf_PDUSession_UpdateSMContext message to the SMF. This message can include a session management (SM) Context ID and an N1 SM container. The N1 SM container can include a PDU session modification request message.

[0174] 1b) When initiated by the PCF in the network node, the PCF initiates an SM policy association modification procedure to notify the SMF of the policy change.

[0175] 1c) When initiated by the UDM between network nodes, the UDM updates the SMF's subscription data by sending an Nudm_SDM_Notification message. The SMF can update the session management subscriber data and send an ACK message to the UDM.

[0176] 1d) When initiated by the SMF in the network node, the SMF can trigger a QoS update.

[0177] When 1a to 1d above are triggered, SMF can perform the PDU session modification process.

[0178] 1e) When the AN resource to which the QoS flow is mapped is released when it is initiated by the AN in the network node, the AN may notify the SMF. The AN may send an N2 message to the AMF. The N2 message may include a PDU session ID and N2 SM information. The N2 SM information may include QFI (QoS flow ID), user location information, and an indication that the QoS flow is released. The AMF may send an Nsmf_PDUSession_UpdateSMContext message. The message may include an SM Context ID and N2 SM information.

[0179] 2) The above SMF sends a report on the join event by executing the SM Policy Partnership Modification procedure. This step can be skipped if the PDU Session Modification procedure is triggered by 1b or 1d. If dynamic PCC is not configured to the network, the SMF applies internal policies to determine changes to the QoS profile.

[0180] Processes 3 to 7 described later may not be performed when the PDU session modification only requires the operation of the UPF.

[0181] 3a) When initiated by the UE or AN, the SMF may respond to the AMF by sending a Nsmf_PDUSession_UpdateSMContext message. The message may include N2SM information and N2 SM container. N2 SM information may include PDU session ID, QFI, QoS profile and session-AMBR. N1 SM container may include PDU session modification command. PDU session modification command may include PDU session ID, QoS rule, QuS rule operation, QoS flow unit QoS parameters and session-AMBR.

[0182] The N2 SM information may include information to be sent by the AMF to the AN. The N2 SM information may include a QFI and a QoS profile to inform the AN that one or more QoS flows are added or modified. If a PDU session modification is requested by a UE that is not configured with user plane resources, the N2 SM information to be delivered to the AN may include information for the establishment of user plane resources.

[0183] The N1 SM container may include a PDU session modification command to be delivered by the AMF through the UE. The PDU session modification command may include QoS rules and QoS flow unit (level) QoS parameters.

[0184] 3b) When initiated by SMF, SMF may send Namf_Communication_N1N2MessageTransfer message. The message may include N2 SM information and N1 SM container. N2 SM information may include PDU session ID, QFI, QoS profile, session-AMBR. N1 SM container may include PDU session modification command. PDU session modification command may include PDU session ID, QoS rules and QoS flow unit (level) QoS parameters.

[0185] If the UE is in the CM-IDLE state and ATC is activated, after the AMF updates and stores the UE context based on the Namf_Communication_N1N2MessageTransfer message, processes 3 to 7 described later can be skipped. When the UE enters a reachable state, that is, when the UE enters the CM-CONNECTED state, the AMF can send an N1 message to synchronize the UE and the UE context.

[0186] 4) AMF may send an N2 PDU Session Request message to AN. The N2 PDU Session Request message may include the N2 SM information and NAS message received from SMF. The NAS message may include the PDU Session ID and N1 SM container. The N1 SM container may include a PDU Session Modification Command.

[0187] 5) AN performs AN signaling exchanges with the UE related to the information received from the SMF. For example, in the case of NG-RAN, in order to modify the required AN resources related to the PDU session, an RRC connection reconfiguration procedure (ConnectionReconfiguration) can be performed with the UE.

[0188] 6) The AN sends an N2 PDU Session ACK message in response to the received N2 PDU Session Request. The N2 PDU Session ACK message may include N2 SM information and user location information. The N2 SM information may include a list of accepted / rejected QFIs, AN tunnel information, and PDU Session ID.

[0189] 7)AMF sends the N2 SM information and user location information received from AN to SMF via Nsmf_PDUSession_UpdateSMContext message. Then, SMF sends Nsmf_PDUSession_UpdateSMContext message to AMF.

[0190] 8) SMF sends an N4 session modification request message to UPF to update the N4 session of UPF included in the PDU session modification.

[0191] When a new QoS flow is created, the SMF works with the UPF to update the UL packet detection rules for the new QoS flow.

[0192] 9) The UE sends a NAS message in response to the received PDU session modification command. The NAS message may include a PDU session ID and an N1 SM container. The N1 SM container may include a PDU session modification command ACK.

[0193] 10) AN sends the NAS message to AMF.

[0194] 11)AMF may send the N1 SM container and user location information received from AN to SMF via Nsmf_PDUSession_UpdateSMContext message. N1 SM container may include PDU session modification command ACK. SMF may send Nsmf_PDUSession_UpdateSMContext response message to AMF.

[0195] 12) In order to update the N4 session of the UPF included in the PDU session modification, the SMF sends an N4 session modification request message to the UPF. The message may include the N4 session ID.

[0196] 13) When the SMF interacts with the PCF in the above process 1b or 2, the SMF can inform the PCF whether to execute the PCC decision through the SM policy association modification process.

[0197] The SMF may notify the requesting entity of user location information associated with the PDU session change. ()))()()))))()))()()()()())))()()()()()()()()()()()()()()()())))()()()()()()()())))()()

[0199] <Time-Sensitive Networking (TSN)>

[0200] On the other hand, the time-sensitive network TSN will be described.

[0201] In the future ultra-connected intelligent information society of the fourth industrial revolution and 5G mobile communications, ultra-low latency (URLLC; Ultra Reliable Low Latency Communications) network technology, which is used to organically connect people and objects, online and offline, etc. to exchange and process information, is becoming a necessary technology based on network infrastructure. As a result, 3GPP is also actively accommodating the challenging requirements of vertical industry fields, and is developing research on the Industrial Internet of Things (IioT) centered on automation to maximize the productivity and profitability of industry through changes in communication infrastructure. In particular, task-oriented industries such as smart factories, smart grids, and smart traffic systems require ultra-reliable and low-latency communication performance at the wired infrastructure level, so new technologies to support them are reflected in the standards.

[0202] IEEE TSN technology has emerged to realize the industrial Internet of Things (IIoT) of multiple devices and systems to be connected by networks in these industrial sites. IEEE TSN technology is considered to be the next-generation industrial network standard that can accommodate most network application examples of Ethernet by combining multiple existing IEEE standards into one packet technology. In 3GPP, 5G-TSN technology is vigorously promoted for standardization after Rel-16 for the vertical field diffusion of 5G technology. 5G-TSN technology is a technology that basically integrates IEEE TSN technology into 5G system (5GS; 5G system), and is a time-sensitive communication technology (Time-Sensitive Communications, TSC) that defines and supports various IIoT service requirements. In TSC, 5GS and TSN basically go through the time synchronization process. After that, TSC QoS Flow based on TSC assistance information is supported.

[0203] Figure 7 is a diagram showing an example of a network architecture that interoperates with a TSN network.

[0204] Reference Figure 7, the 5G system can communicate with the TSN bridge through the external network. The logical TSN bridge may include TSN translation functionality for the user plane and control plane to interoperate between the 5GS system and the TSN system. The 5GS TSN translation function may include a device-side TSN translator (DS-TT) and a network-side TSN translator (NW-TT). TSNAF is part of 5GC and can provide control plane translation functions that integrate 5GS and TSN. In 5GC and RAN, processes, wireless communication links, etc. that are characteristics of the 5G system may not be visible in the TSN network. 5GS provides TSN input (ingress) ports and output (egress) ports through DS-TT and NW-TT.

[0205] In order to discover the Ethernet device connected to the DS-TT, the DS-TT may support the link layer connection retrieval and reporting. In order to discover the Ethernet device connected to the NW-TT, the NW-TT may also support the link layer connection retrieval and reporting. If the DS-TT does not support the link layer connection retrieval and reporting, the NW-TT performs the link layer connection retrieval and reporting instead of the DS-TT, so that the Ethernet device connected to the DS-TT can be retrieved.

[0206] Figure 8 is an example diagram illustrating an architecture that supports time-sensitive communications and time synchronization services.

[0207] Reference Figure 8 , in order to support time synchronization services for Ethernet or IP type sessions, DS-TT, NW-TT and Time Sensitive Communication and Time Synchronization Function (TSCTSF) are shown. NEF provides 5GS capability information to support time synchronization services. TSCTSF controls DS-TT and NW-TT.

[0208] UPF / NW-TT transmits (g)PTP messages.

[0209] When the UPF supports more than one NW-TT, there can be a one-to-one association between the NW-TT and the network instance or a one-to-one association between the NW-TT and the network instance together with the DNN / S-NSSAI in the UPF. When there are multiple network instances in the UPF, each network instance can be considered to be logically separated.

[0210] <Deterministic Networking (Det Net)

[0211] The deterministic network DetNet technology being developed by the IETF DetNet WG is a technology that expands the application scope of Ethernet TSN technology (Layer 2 technology) and integrates with IP and MPLS basic networks (Layer 3 technology). Ultimately, DetNet technology refers to the technology that supports the extension of Ethernet TSN technology (Layer 2 technology) to IP technology (Layer 3 technology). In 3GPP, in order to support IETF DetNet technology from Rel-18 to 5GS, the TSC framework extension technology is reflected in the standard. ()()()()()()

[0213] <Unified access control>

[0214] Methods for controlling access to the network

[0215] A large number of user equipment (UE) can access the communication system, and various services can exist in the UE. If a large number of UEs and a large number of services have data communication requests, but the network cannot accept data communication requests from all UEs and services, it is necessary for the network to increase the stability of the system by controlling the access requests from the UE. Otherwise, there may be a problem that communication access requests such as emergency calls cannot be properly processed.

[0216] This access control method is generally called access control, and 5G uses the "unified access control" technology.

[0217] Hereinafter, unified access control will be described in detail.

[0218] Depending on operator policy, deployment scenarios, joiner profiles, and available services, different criteria are used to determine which access attempts are allowed or restricted when congestion occurs in the 5G system. The different criteria for access control are associated with access identifiers and access categories. The 5G system provides operators with a single unified access control that controls access based on these two aspects.

[0219] In unified access control, each access attempt is classified into one or more access identifiers and access categories. The UE tests whether the actual access attempt can be performed based on the access control information applicable to the access identifier and access category associated / matched with the access attempt.

[0220] Unified access control supports extensibility to allow additional standardized access identifiers and access categories, and supports flexibility to allow operator-defined access identifiers and access categories, leveraging the operator's own standards (access identifiers, joining information, access categories, such as network slicing, applications and application servers).

[0221] Additionally, the use of legacy Access Classes 11-15 is expanded while potentially allowing the success of access attempts that might otherwise be restricted based on user type.

[0222] According to the operator policy, the 5G system must be able to restrict UE access to the network using barring parameters based on access identifiers and access categories. As shown in Table 1 below, the access identifier is set on the UE. The access category is defined by combining the conditions of the UE and the access attempt type listed in Table 2 below. Select more than one access identifier and one access category and test the access attempt.

[0223] The 5G network may send barring control information (i.e., a list of barring parameters associated with an access identifier and access category) in more than one zone in the RAN.

[0224] The UE may determine whether a new specific access attempt may be allowed based on the barring parameters received from the barring control information and the UE's settings.

[0225] In the case of multiple core networks sharing the same RAN, the RAN may apply access control individually to different core networks.

[0226] The unified access control framework can be applied to UEs using E-UTRA to access the 5G core network (CN) and all UEs using new radio (NR) to access the 5G CN.

[0227] When starting a new access attempt (ie, a new session request), the unified access control framework may be applicable to UEs in RRC Idle, RRC Inactive, or RRC Connected states.

[0228] The 5G system supports operator-defined access categories that can be defined mutually exclusively by operators.

[0229] The unified access control framework may be applicable to roamers entering the PLMN.The serving PLMN may provide the UE with the definition of operator-defined access categories.

[0230] The following Table 3 shows the access identifier.

[0231] [Table 3]

[0232]

[0233] Access identifiers may be restricted at any time.

[0234] [Table 4]

[0235]

[0236]

[0237] The 5G network may broadcast barring control information in one or more areas of the RAN. The barring control information may be, for example, a list of barring parameters associated with an access ID and an access category. The UE may determine whether to allow a specific new access attempt based on the barring parameters (which the UE receives from the broadcast barring control information) and the UE's settings.

[0238] In the case of multiple core networks sharing the same RAN, the RAN may apply access control to other core networks individually.

[0239] The unified access control framework can be applied to both UEs using E-UTRA to access the 5G core network (CN) and UEs using NR to access the 5G CN.

[0240] When a UE initiates a new access attempt (eg, a new session request), the unified access control framework may be applicable to UEs in Radio Resource Control (RRC) Idle state, RRC Inactive state, and RRC Connected state.

[0241] For reference, "new session request" in the RRC connected state may mean an event. For example, an event may be a new MMTEL voice session, an MMTEL video session, sending SMS (SMS over IP or SMS over NAS), a new PDU session establishment, an existing PDU session modification, and a service request for re-establishing the user plane of an existing PDU session.

[0242] The 5G system may support a means for operators to define operator-defined access categories as mutually exclusive. For example, standard examples of operator-defined access categories may be network slices, applications, and application servers.

[0243] A unified access control framework may be applicable to inbound roamers of a PLMN.

[0244] The serving PLMN may provide the UE with the definition of the operator-defined access class.

[0245] If the UE needs to access the 5G system, the UE may first perform an access control check to determine whether access is allowed. The access control check may be performed on access attempts defined by the following event list.

[0246] a) When the UE is in 5GS Mobility Management (5GMM)-IDLE mode via 3GPP access and an event occurs that requires transition to 5GMM-CONNECTED mode; and

[0247] b) When the UE is in 5G MM-CONNECTED mode via 3GPP access, or in 5G MM-CONNECTED mode with RRC inactivity indication, and one of the following events occurs:

[0248] b-1) when the NAS layer (e.g., 5GMM) of the terminal receives MO-MMTEL-voice-call-started information / indication, MO-MMTEL-video-call-started information / indication, or MO-SMSoIP-attempt-started information / indication from an upper layer (e.g., application layer);

[0249] b-2) when a request is received from an upper layer (e.g., application layer) that is mobile originated by the NAS layer (e.g., 5GMM) of the terminal through NAS, and the request does not trigger a service request to transition the UE from 5GMM-IDLE mode to 5GMM-CONNECTED mode;

[0250] b-3) when the NAS layer (e.g., 5GMM) of the terminal receives a request from an upper layer (e.g., application layer) to send a ULNASTRANASPORT message for the purpose of PDU session establishment, and the request does not trigger a service request to transition the UE from 5GMM-IDLE mode to 5GMM-CONNECTED mode;

[0251] b-4) when the NAS layer (e.g. 5GMM) of the terminal receives a request from an upper layer (e.g., application layer) to send a ULNASTRANASPORT message for the purpose of PDU session modification, and the request does not trigger a service request to transition the UE from 5GMM-IDLE mode to 5GMM-CONNECTED mode;

[0252] b-5) when the NAS layer (e.g., 5GMM) of the terminal receives a request to re-establish user-plane resources for an existing PDU session; and

[0253] b-6) When the NAS layer (e.g. 5GMM) of the terminal is notified to send uplink user data packets for a PDU session with user-plane resources.

[0254] If the NAS layer of the terminal detects one of the above events, the NAS layer of the terminal may perform an operation of mapping the request kind to more than one access ID and access category. In addition, the lower layer (e.g., RRC layer) of the terminal may perform an access barring check on the request based on the determined access ID and access category. For reference, the NAS layer of the terminal may recognize the above events through information / indication provided from an upper layer and / or when determining that a normal NAS operation needs to be started.

[0255] In order to determine the requested access ID and access category, the NAS layer of the terminal may check the access reason for the set of access IDs and the set of access categories, the requested service type, and the user profile of the UE including the UE settings. Examples of the set of access IDs and the set of access categories are as follows:

[0256] - A set of standardized access IDs;

[0257] - a set of standardized access categories; and

[0258] - Where feasible, the operator-defines a set of access categories.

[0259] When a terminal (e.g., UE) needs to initiate an access attempt for one of the events such as the examples a) to b-6) above, the terminal determines one or more access IDs associated with the access attempt from a set of standardized access IDs, and can determine an access category associated with the access attempt from a set of standardized access categories and a set of operator-defined access categories.

[0260] For example, the set of access IDs applicable for a request related to an access attempt may be determined by a terminal (e.g., UE) as follows:

[0261] i) In the example of Table 3, for each of access IDs 1, 2, 11, 12, 13, 14 and 15, when selecting a new PLMN, the UE may check whether the access ID is available in the selected PLMN. Alternatively, the UE may check whether the access ID is applicable to the RPLMN or an equivalent PLMN; and

[0262] ii) If there is no available access ID among access IDs 1, 2, 11, 12, 13, 14, and 15, access ID0 may be used.

[0263] To determine the available access categories for the access attempt, the NAS layer of the terminal may check rules such as the example in Table 5 below, and use the matching access category for a barring check.

[0264] Table 5 below is an example of rules used by the NAS layer of the terminal when determining an available access category for an access attempt.

[0265] [Table 5]

[0266]

[0267]

[0268]

[0269]

[0270] If the access attempt matches more than one rule, the access class with the lowest rule number among the more than one rule may be selected. If the access attempt matches more than one operator-defined access class definition, the UE may select the operator-defined access class definition with the lowest precedence value. The situation where an access attempt matches more than one rule may include the situation where multiple events trigger an access attempt simultaneously.

[0271] 1. Access control check in 5GMM-IDLE mode and 5GMM-IDLE mode indicated by suspend

[0272] When the terminal is in the 5GMM-IDLE mode indicated by the 5GMM-IDLE mode and the suspend mode, the NAS layer in the terminal receives a request from an upper layer for an access attempt, and classifies the access attempt into access identifiers and access categories as shown below.

[0273] a) when the UE is not operating in SNPN access mode; or

[0274] b) When the UE operates in SNPN access mode.

[0275] The NAS layer of the terminal sends the applicable access identifier and access category to the lower layer for the purpose of access control checking. Based on the request to the lower layer, the NAS layer also provides the RRC establishment cause to the lower layer.

[0276] That is, when the UE is in 5GMM-IDLE mode, the NAS layer of the terminal receives a request for an access attempt from the upper layer of the terminal, and the NAS layer of the terminal can classify the access attempt into an access ID and an access category according to the examples in Tables 4 and 5 above.

[0277] For access control checking, the NAS layer of the terminal may communicate a request including an available access ID and an available access category to a lower layer (e.g., an RRC layer). The lower layer may perform an access restriction check. The NAS layer of the terminal may provide an RRC establishment cause in a request to the lower layer. According to implementation options, the NAS layer of the terminal may provide an RRC establishment cause to the lower layer after receiving a notification from the lower layer that an access attempt is allowed.

[0278] If the lower layer informs the NAS layer that the access attempt is allowed, the NAS layer may initiate a procedure for sending an initial NAS message regarding the access attempt.

[0279] If the lower layer notifies the NAS layer that the access attempt is barred, the NAS layer may not initiate a process for sending an initial NAS message about the access attempt. In addition, if the event that triggered the access attempt was once MO-MMTEL-voice-call-started information / indication, MO-MMTEL-video-call-started information / indication, or MO-SMSoIP-attempt-started information / indication, the NAS layer may notify the upper layer (e.g., application layer) that the access attempt is barred. In this case, when the NAS layer receives information / indication from the lower layer (e.g., RRC layer) that the restriction on the access category related to the access attempt has been relieved, the NAS layer notifies the upper layer that the restriction on the access category has been relieved. Also, if still necessary, the NAS layer may initiate a process for sending an initial NAS message. For reference, a barring timer for each access category may be driven (run by) in the lower layer. When the barring timer expires, the lower layer may notify the NAS layer of the information / indication that the access restriction has been relieved through the access category.

[0280] 2. Access control check in 5G MM-CONNECTED mode and 5G MM-CONNECTED mode indicated by RRC inactivation

[0281] When the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication, the upper layer of the terminal detects one of the above events b-1) to b-6), then the NAS layer of the terminal receives a request for an access attempt from the upper layer of the terminal. The NAS layer of the terminal can then classify the access attempt into access IDs and access categories according to the examples in Tables 4 and 5 above. For access control checking, the NAS layer of the terminal can communicate a request containing an available access ID and an available access category to a lower layer (e.g., an RRC layer).

[0282] The lower layer may perform an access restriction check. The NAS layer of the terminal may provide the RRC establishment cause in the request to the lower layer. According to implementation options, the NAS layer of the terminal may provide the RRC establishment cause to the lower layer after receiving a notification from the lower layer that the access attempt is allowed.

[0283] When the UE builds a REGISTRATION REQUEST message or a SERVICE REQUEST message for an access attempt, if the UE has pending uplink user data for more than one PDU Session, then the UE may display each PDU Session in the uplink data status IE (information element) regardless of the access class for which the access restriction check is performed. The UE may display pending user data for each PDU Session even if a restriction timer is being driven for some of the access classes to which it belongs.

[0284] When the lower layer notifies the NAS layer that the access attempt is allowed, the NAS layer can perform the following operations based on the event that triggered the access attempt:

[0285] a) If the event triggering the access attempt is MO-MMTEL-voice-call-started information / indication, MO-MMTEL-video-call-started information / indication, or MO-SMSoIP-attempt-started information / indication, the NAS layer may notify the upper layer (e.g., the application layer) that the access attempt is restricted;

[0286] b) If the event triggering the access attempt is a request from an upper layer to send a mobile originated SMS via NAS, the NAS layer (e.g., 5GMM layer) may initiate a NAS transport procedure in order to send the SMS in a UL NAS TRANSPORT message;

[0287] c) if the event triggering the access attempt is a request from an upper layer to establish a new PDU session, the NAS layer (e.g., 5GMM layer) may initiate a NAS transmission process in order to send a PDU session establishment request message;

[0288] d) If the event triggering the access attempt is a request from an upper layer to modify an existing PDU session, the NAS layer (e.g., 5GMM layer) may initiate a NAS transmission process in order to send a PDU session modification request message;

[0289] e) if the event triggering the access attempt is a request to re-establish user-plane resources associated with an existing PDU session, the NAS layer (e.g., 5GMM layer) may initiate a service request procedure; and

[0290] f) If the event triggering the access attempt is an uplink user data packet to be transmitted for a PDU session with delayed user-plane resources, the NAS layer (e.g., 5GMM layer) may consider that the uplink user data packet can be transmitted.

[0291] If the lower layers inform the NAS layer that the access attempt is restricted, then depending on the event that triggered the access attempt, the NAS layer may perform the following operations:

[0292] a) If the event triggering the access attempt is MO-MMTEL-voice-call-started information / indication, MO-MMTEL-video-call-started information / indication, or MO-SMSoIP-attempt-started information / indication, the NAS layer may notify the upper layer that the access attempt is restricted. The upper layer may prohibit the initiation of an MMTELvoice session, an MMTEL video session, or the sending of SMS over IP. In this case, when the NAS layer receives information / indication from the lower layer (e.g., the RRC layer) that the restriction on the access category related to the access attempt is relieved, the NAS layer may notify the upper layer that the restriction on the access category is relieved;

[0293] b) If the event triggering the access attempt is a request from an upper layer to send a mobile originated SMS through NAS, the NAS layer (e.g., 5GMM layer) may not initiate a NAS transmission procedure to send the SMS to the UL NAS TRANSPORT message. When the NAS layer receives information / indication from a lower layer (e.g., RRC layer) that restrictions on the access category related to the access attempt are relieved, the NAS layer may initiate a NAS transmission procedure if the NAS transmission procedure is still required.

[0294] c) If the event that triggers the access attempt is a request from an upper layer to establish a new PDU session, the NAS layer (e.g., 5GMM layer) may not initiate a NAS transmission process in order to send a PDU session establishment request message. When the NAS layer receives information / indication from a lower layer (e.g., RRC layer) that restrictions on access categories related to the access attempt are relieved, the NAS layer may initiate a NAS transmission process if a NAS transmission process is still required.

[0295] d) If the event that triggers the access attempt is a request from an upper layer to modify an existing PDU session, the NAS layer (e.g., 5GMM layer) may not initiate a NAS transmission process in order to send a PDU session modification request message. When the NAS layer receives information / indication from a lower layer (e.g., RRC layer) that restrictions on access categories related to the access attempt are relieved, the NAS layer may initiate a NAS transmission process if a NAS transmission process is still required.

[0296] e) If the event triggering the access attempt is a request for re-establishing user-plane resources associated with an existing PDU session, the NAS layer (e.g., 5GMM layer) may not initiate a service request procedure. When the NAS layer receives information / indication from a lower layer (e.g., RRC layer) that restrictions on an access category associated with the access attempt are relieved, the NAS layer may initiate a NAS transfer procedure if a NAS transfer procedure is still required; and

[0297] f) If the event triggering the access attempt is an uplink user data packet to be transmitted for a PDU session with delayed user-plane resources, the NAS layer (e.g., 5GMM layer) may not consider that the uplink user data packet can be transmitted. When the NAS layer receives information / indication from the lower layer (e.g., RRC layer) that the restriction of the access category related to the access attempt is relieved, the NAS layer may initiate the NAS transmission process if the NAS transmission process is still required.

[0298] 3. Mapping between access category / access identifier and RRC establishment cause

[0299] When 5GMM requests to establish a NAS signaling connection, the RRC establishment cause used by the terminal can be selected by one or more access identifiers and access categories. If the access attempt matches more than one rule, the RRC establishment cause with the lowest rule number can be used. If the determined access category is an operator-defined access category, the RRC establishment cause used by the terminal can be selected based on more than one access identifier and a standardized access category.

[0300] The following Table 6 shows the mapping between access identifier / access category and RRC establishment cause when establishing an N1 NAS signaling connection over NR connected in 5GCN.

[0301] [Table 6]

[0302]

[0303]

[0304] The following Table 7 shows the mapping between access identifier / access category and RRC establishment cause when establishing an N1 NAS signaling connection through E-UTRA connected to 5GCN.

[0305] [Table 7]

[0306]

[0307]

[0308] <Problems to be Solved by the Disclosure of This Specification>

[0309] TSN traffic has very strict QoS requirements for latency. In particular, in the case of certain TSN traffic, it is necessary to ensure a very deterministic transmission latency, and resource allocation and traffic processing solutions are required for this.

[0310] At present, in 3GPP 5GS (5G system), access control (Access Control) that takes into account network congestion conditions between terminals and radio intervals is performed, but a distinction is made between 1) Access attempt for MT access, or handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access; 2) Access attempt for Emergency; 3) Access attempt for MO exception data; 4) Access attempt for delay tolerant; 5) Access attempt for MO (Mobile originated) IMS related signaling; 6) Access attempt for MO MMTEL voice; 7) Access attempt for MO MMTEL video; 8) Access attempt for MO SMS or SMSoIP. SMS or SMSoIP); 9) Access attempt for MO signaling; 10) Access attempt for MO data; 11) Access attempt for operator-defined access category (ODAC) and perform access control.

[0311] However, there is no method that can distinguish signaling related to industrial traffic and handle access control according to QoS and application service requirements related to industrial traffic.

[0312] In summary, a method is needed to distinguish the signaling of these industrial traffic and perform access control (Access control for Industrial traffic (signalling and / or data)).

[0313] <Disclosure of this specification>

[0314] Therefore, a disclosure of this specification proposes a method for performing access control by distinguishing signaling for industrial traffic.

[0315] General traffic and other industrial traffic may refer to time-sensitive / deterministic or ultra-reliable low latency communication (URLLC) or Industrial IoT (Internet of Things), IIoT or time-sensitive communication (TSC) traffic or traffic of related sessions.

[0316] To this end, according to a disclosure of this specification, a new access category for sending industrial signaling and / or data is proposed.

[0317] [Table 8]

[0318]

[0319] According to a disclosure of this specification, in order to distinguish the signaling for TSN traffic, the following new RRC establishment cause and / or RRC recovery cause are proposed.

[0320] [Table 9]

[0321]

[0322] The following Table 10 is an example of a rule used when the NAS layer of the terminal determines an access class available for an access attempt. The following Table 10 shows a newly added access class according to a disclosure of the present specification.

[0323] [Table 10]

[0324]

[0325]

[0326] The following Table 11 shows the mapping between the access identifier / access category and the RRC establishment cause when establishing an N1 NAS signaling connection through the NR connected to the 5GCN. The following Table 11 shows the newly added access category and RRC establishment cause according to a disclosure of this specification.

[0327] [Table 11]

[0328]

[0329] The following Table 12 shows the mapping between the access identifier / access category and the RRC establishment cause when establishing an N1 NAS signaling connection through E-UTRA connected to 5GCN. The following Table 12 shows the newly added access category and RRC establishment cause according to one disclosure of this specification.

[0330] [Table 12]

[0331]

[0332] Fig. 9 FIG. 1 is a diagram showing an example of a disclosure according to the present specification.

[0333] See also Fig. 9 If congestion occurs in the wireless interval between the UE (i.e., terminal) and the base station, the base station (e.g., gNB, eNB, etc.) sends the first system information block (e.g., SIB1) containing TSN (or TSC, DetNet, IIoT, URLLC) signaling and / or information related to data access control (e.g., UAC category, restriction time, restriction factor, restriction identifier, etc.) to the UE (i.e., terminal).

[0334] If initiate (MO) TSN (or TSC, DetNet, IIoT, URLLC) signaling or data occurs at the application layer of the UE (ie, terminal), the application layer notifies the NAS layer through information / indication.

[0335] Afterwards, the NAS layer of the UE (i.e., terminal) determines to initiate (MO) TSN (or TSC, DetNet, IIoT, URLLC) signaling and / or the access category (e.g., access category #y) for the data, and sends it to the RRC layer of the UE (i.e., terminal) together with the access identifier (Access Identity) information.

[0336] The RRC layer of the UE (i.e., terminal) performs checks for access control (Unified Access Control) based on the access control related information (i.e., UAC category, restriction time, restriction factor, restriction identifier, etc.) contained in SI B1 in the base station (gNB, eNB, etc.) and based on the access identifier and access category information received from the NAS layer.

[0337] In addition, the RRC layer of the UE (i.e., the terminal) determines the RRC establishment cause / recovery cause based on the access category (e.g., #y) for initiating (MO) TSN (or TSC, DetNet, IIoT, URLLC) received from the NAS layer. For example, the RRC layer of the UE (i.e., the terminal) confirms the RRC establishment cause / recovery cause (e.g., "mo-TSN (or TSC, DetNet, IIoT, URLLC)") mapped to the access category (e.g., #y) for initiating (MO) TSN (or TSC, DetNet, IIoT, URLLC) received from the NAS layer. And, the RRC layer of the UE (i.e., the terminal) sets the RRC establishment cause / recovery cause in the RRC message and sends it to the base station. The RRC message can be a RRCSetupRequest message.

[0338] The base station then performs QoS / resource / access control etc. based on this.

[0339] If the base station receives an RRC message, for example, an RRC setup request message, the base station sends an RRC setup message to the UE (ie, terminal). Then, the UE (ie, terminal) sends an RRC setup completion message to the base station.

[0340] However, when the base station rejects the RRC message, for example, the RRC setup request message, the base station sends an RRC reject message.

[0341] The corresponding industrial signaling and / or data means TSN (or DetNet), time-sensitive / deterministic, ultra-reliable low latency communication (URLLC), Industrial IoT (Internet of Things), IIoT or time-sensitive communication (TSC) signaling and / or data.

[0342] <Abstract of this specification>

[0343] In order to solve the above problem, an operation method in a terminal is proposed. The operation method of the terminal may include: a step of receiving system information containing access control related information for industrial signaling and / or data from a base station; a step of determining an access category according to an access identifier when sending industrial signaling or data; a step of performing a check for access control (Unified Access Control) based on the access category and the access control related information; a step of determining a Radio Resource Control (RRC) establishment cause or an RRC recovery cause based on the access category in the case of passing the check; and a step of sending an RRC message including the determined RRC establishment cause or RRC recovery cause to the base station.

[0344] In order to solve the above problems, a chipset installed in a terminal is proposed. The chipset includes: at least one processor; and at least one memory storing instructions and electrically connected to the at least one processor operably. The at least one processor is executed based on the instructions, and the operations performed include: receiving system information containing access control related information for industrial signaling and / or data from a base station; determining an access category according to an access identifier when sending industrial signaling or data; performing a check for access control (Unified Access Control) based on the access category and the access control related information; determining a Radio Resource Control (RRC) establishment cause or an RRC recovery cause based on the access category in the case of passing the check; and sending an RRC message including the determined RRC establishment cause or RRC recovery cause to the base station.

[0345] In order to solve the above problems, a device for a terminal is proposed. The device may include: a transceiver unit; at least one processor; and at least one memory storing instructions and operably electrically connected to the at least one processor. The at least one processor is executed based on the instructions, and the operations performed include: a step of receiving system information containing access control related information for industrial signaling and / or data from a base station; a step of determining an access category according to an access identifier when sending industrial signaling or data; a step of performing a check for access control (Unified Access Control) based on the access category and the access control related information; a step of determining a Radio Resource Control (RRC) establishment cause or an RRC recovery cause based on the access category if the check passes; and a step of sending an RRC message including the determined RRC establishment cause or RRC recovery cause to the base station.

[0346] Industrial signaling and / or data may be traffic for time-sensitive networking (TSN), time-sensitive communications (TSC), deterministic networking (DetNet), ultra-reliable low latency communication (URLLC), or Industrial IoT (Internet of Things) (IIoT).

[0347] The determined RRC establishment cause or RRC resumption cause may be used to identify industrial signaling and / or data.

[0348] For industrial signaling and / or data, an access category may be determined in order to pass access control inspection.

[0349] The determined access class may have a high priority in order to pass the check for the access control for the industrial signaling and / or data.

[0350] Even when congestion occurs in the wireless section with the base station, the radio resource control message is transmitted after the check for access control is performed for the industrial signaling and / or data.

[0351] The terminal may include an application layer, a non-access stratum (NAS) and an RRC layer.

[0352] The determining step may include: receiving a notification from the application layer that the industrial signaling and / or data has occurred, the non-access layer determining the access category for the industrial signaling and / or data; and the non-access layer conveying the determined access category and the access identifier to the wireless resource control layer.

[0353] The RRC layer performs a check for the access control based on the access class, the access identifier, and the received access control related information received from the non-access stratum.

[0354] Hereinafter, a device to which the disclosure of this specification as described above can be applied will be described.

[0355] Fig.10 is a block diagram showing the configuration of a processor that implements the disclosure of this specification.

[0356] refer to Fig.10 It can be seen that the processor 1020 implementing the disclosure of this specification may include multiple circuits to implement the functions, processes and / or methods described and proposed in this specification. For example, the processor 1020 may include a first circuit 1020-1, a second circuit 1020-2, and a third circuit 1020-3. In addition, although not shown, the processor 1020 may also include more circuits. Each circuit may include multiple transistors.

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

[0358] The processor may be installed in the UE.

[0359] Fig.11 FIG. 2 is a diagram showing a wireless communication system according to an embodiment.

[0360] Reference Fig.11 , a wireless communication system may include a first device 100a and a second device 100b.

[0361] 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 sending UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, an unmanned aerial vehicle (UAV), an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, a mixed reality (MR) device, a holographic 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 other devices related to the field of the fourth industrial revolution.

[0362] 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 sending UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, an unmanned aerial vehicle (UAV), an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, a mixed reality (MR) device, a holographic 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 other devices related to the field of the fourth industrial revolution.

[0363] For example, UE 100 may be a mobile phone, a smart phone, a laptop computer, a digital broadcast UE device, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation, a slate PC, a tablet PC, an ultrabook, a wearable device (e.g., a watch-type UE device (smartwatch), a glasses-type UE device (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.

[0364] For example, a drone may be a flying object that flies by radio control signals without human piloting. For example, a VR device may include a device that realizes an object or background in a virtual world, etc. For example, an AR device may include a device that connects an object or background in a virtual world to an object or background in a real world, etc. and realizes it. For example, an MR device may include a device that merges an object or background in a virtual world into an object or background in a real world, etc. and realizes it. For example, a holographic device may include a device that uses holography, which is an interference phenomenon of light that occurs when two lasers meet, to record and reproduce three-dimensional information to realize a 360-degree stereoscopic image. For example, a public safety device may include a live video device or a video device that can be worn on a user, etc. For example, an MTC device and an IoT device may be a device that does not require direct human intervention or manipulation. For example, an MTC device and an IoT device may include a smart meter, a bending machine, a thermometer, a smart light bulb, a door lock, or various sensors, etc. For example, a medical device may be a device that is intended to diagnose, treat, alleviate, treat, or prevent a disease. For example, a medical device may be a device that is intended to diagnose, treat, alleviate, or correct an injury or disability. For example, a medical device may be a device that is intended to inspect, replace, or deform a structure or function. For example, a medical device may be a device intended to regulate pregnancy. For example, a medical device may include a diagnostic device, a surgical device, an (in vitro) diagnostic device, a hearing aid or a surgical device. For example, a security device may be a device installed to prevent possible 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 that can provide financial services such as mobile payments. For example, a fintech device may include a payment device or a point of sales (POS). For example, a climate / environmental device may include a device that monitors or predicts the climate / environment.

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

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

[0367] The memory 1010a and / or the memory 1010b may be connected to each other inside or outside the processor 1020a and / or the processor 1020b, and may also be connected to other processors through various technologies such as a wired or wireless connection.

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

[0369] Fig.12 is a block diagram illustrating a network node according to an embodiment.

[0370] Specifically, Fig.12 The diagram shows in detail a case where a base station is divided into a central unit (CU) and a distributed unit (DU).

[0371] Reference Fig.12 , base stations W20, W30 can be connected to the core network W10, and base station W30 can be connected to the adjacent base station W20. For example, the interface between base stations W20, W30 and the core network W10 can be called NG, and the interface between base station W30 and the adjacent base station W20 can be called Xn.

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

[0373] 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 only be supported by one DU W34, W36. One DU W34, W36 can be connected to one CU W32, and through appropriate implementation one DU W34, W36 can be connected to multiple CUs.

[0374] Fig.13 is a block diagram showing the configuration of UE 100 according to an embodiment.

[0375] especially, Fig.13 The UE 100 shown in FIG. 1 is a more detailed view of the above Fig.12 Figure 1 of the first device.

[0376] UE 100 includes a memory 1010, a processor 1020, a transceiver unit 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.

[0377] The processor 1020 may be configured to implement the functions, processes and / or methods described and suggested in this specification. The layers of the 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, Modem). An example of the processor 1020 may be a processor composed of MANUFACTURED BY SNAPDRAGON TM Series processors, EXYNOSTM series processors manufactured by A series processors manufactured by Made by HELIO TM Series processors, ATOM manufactured TM series processors or corresponding next-generation processors.

[0378] The power management module 1091 manages the power of the processor 1020 and / or the transceiver unit 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. The SIM card is an integrated circuit for identifying the international mobile subscriber identity (IMSI) and securely storing the keys associated with it in mobile devices such as mobile phones and computers to identify subscribers and perform authentication. Contact information can also be stored in multiple SIM cards.

[0379] The memory 1010 is operably coupled to the processor 1020 and stores various information for operating the processor 610. The memory 1010 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage devices. When the embodiment is implemented by software, the technology described in this specification may be implemented by a module (e.g., a process, a function, etc.) that performs the functions described in this specification. The module 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 outside the processor 1020 and may be communicatively connected to the processor 1020 by various means known in the art.

[0380] The transceiver unit 1031 is operably coupled to the processor 1020 and sends and / or receives wireless signals. The transceiver unit 1031 includes a transmitter and a receiver. The transceiver unit 1031 may include a baseband circuit for processing radio frequency signals. The transceiver unit controls one or more antennas to send and / or receive wireless signals. The processor 1020 communicates command information to the transceiver unit 1031 in order to initiate communication, for example, to send a wireless signal constituting voice communication data. The function of the antenna is to send and receive wireless signals. When receiving a wireless signal, the transceiver unit 1031 can transmit the signal and convert the signal to baseband in order to be processed by the processor 1020. The processed signal can be converted into audible or readable information output through the speaker 1042.

[0381] Speaker 1042 outputs sound related results processed by processor 1020. Microphone 1052 receives sound related input to be used by processor 1020.

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

[0383] Fig.14 It is shown in Fig.11 The transceiver unit of the first device shown in FIG. Fig.13 A block diagram of the transceiver unit of the device shown.

[0384] Reference Fig.14 , the transceiver unit 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 transmission unit 1031-15. The transmitter 1031-1 may also include a modulator. In addition, for example, a scramble unit (scramble unit, not shown), a modulation mapper (modulation mapper, not shown), a layer mapper (layer mapper, not shown), and a layer permutator (layer permutator, not shown) may also be included, which may be arranged before the DFT unit 1031-11. That is, in order to prevent the increase of the peak-to-average power ratio (PAPR), the transmitter 1031-1 first passes the signal through the DFT 1031-11 before mapping the signal to the subcarrier. The signal spread (or precoded in the same sense) by the DFT unit 1031 - 11 is mapped to subcarriers by the subcarrier mapper 1031 - 12 , and then passes through the Inverse Fast Fourier Transform (IFFT) unit 1031 - 12 again to create a signal on the time axis.

[0385] The DFT unit 1031-11 performs DFT on the input symbol and outputs a complex-valued symbol. For example, if Ntx symbols (where Ntx is a natural number) are input, the DFT size is Ntx. The DFT unit 1031-11 may be referred to as a transform precoder. The subcarrier mapper 1031-12 maps the complex-valued symbols to each subcarrier in the frequency domain. The complex-valued symbols may be mapped to resource elements corresponding to resource blocks allocated for data transmission. The subcarrier mapper 1031-12 may be referred to as a resource element mapper. The IFFT unit 1031-13 performs IFFT on the input symbol and outputs a baseband signal of the data as 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. By inserting CP, inter-symbol interference (ISI) and inter-carrier interference (ICI) can be prevented, thereby maintaining orthogonality even in a multipath channel.

[0386] On the other hand, the receiver 1031-2 includes a wireless receiving unit 1031-21, a CP removal unit 1031-22, an FFT unit 1031-23, an equalization unit 1031-24, etc. The wireless receiving 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 transmitting unit 1031-15, the CP insertion unit 1031-14, and the IFF unit 1031-13 in the transmitting end 1031-1. The receiver 1031-2 may also include a demodulator.

[0387] <Scenarios to which this specification is applicable>

[0388] Although not limited to this, the various descriptions, functions, processes, suggestions, methods and / or operational flowcharts disclosed in this specification disclosed herein may be applicable to a variety of fields requiring wireless communication / connection (e.g., 5G) between devices.

[0389] In the following, more detailed examples will be provided with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise specified, the same reference numerals represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0390] Fig.15 1 is a diagram showing a communication system 1 applicable to the disclosure of this specification.

[0391] Reference Fig.15 , the disclosed communication system 1 applicable to the present specification includes a wireless device, a base station and a network. Among them, the wireless device refers to a device that performs communication using a wireless access technology (such as 5GNR (new RAT), Long Term Evolution (Long Term Evolution, LTE)), and is referred to as a communication / wireless / 5G device. Although not limited to this, the wireless device may include a robot 100a, a vehicle 100b-1, 100b-2, an extended reality (eXtended Reality, XR) device 100c, a handheld device (Hand-held device) 100d, a home appliance 100e, an Internet of Things (Internet of Things, IoT) device 100f and an AI device / server 400. For example, a vehicle may include a vehicle equipped with a wireless communication function, an autonomous driving vehicle, a vehicle capable of inter-vehicle communication, etc. Among them, a vehicle may include an unmanned aerial vehicle (Unmanned Aerial Vehicle, UAV) (e.g., a drone). XR devices include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and can be embodied in the form of head-mounted devices (HMD), head-up displays (HUD) equipped in vehicles, televisions, smart phones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Mobile devices may include smart phones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptops, etc.), etc. Home appliances may include televisions, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, base stations and networks may also be implemented through wireless devices. A specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0392] The wireless devices 100a to 100f can be connected to the network 300 through the 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 the AI ​​server 400 through the network 300. The network 300 can be formed using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other through the base station 200 / network 300, but can also communicate directly (e.g., sidelink communication) without passing through the base station / network. For example, vehicles 100b-1, 100b-2 can communicate directly (e.g., vehicle to vehicle (V2V) / vehicle to everything (V2X) 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.

[0393] Wireless communication / connection 150a, 150b, 150c can be established between wireless devices 100a~100f / base station 200, and base station 200 / base station 200. Among them, wireless communication / connection can be established through various wireless access technologies (for example, 5GNR) such as uplink / downlink communication 150a and side link communication 150b (or, D2D communication), communication between base stations 150c (for example, relay, Integrated Access Backhaul (IAB)), etc. Through wireless communication / connection 150a, 150b, 150c, wireless devices and base stations / wireless devices, and base stations and base stations can send / receive wireless signals to each other. For example, wireless communication / connection 150a, 150b, 150c can send / receive signals through various physical channels. To this end, based on the various suggestions disclosed in this specification, at least a part of various configuration information setting processes for sending / receiving wireless signals, various signal processing processes (for example, channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.) and resource allocation processes can be performed.

[0394] The above is an exemplary description through preferred embodiments, but the disclosure of this specification is not limited to such specific embodiments. Therefore, it can be modified, changed or improved in various forms within the scope of the concept of this specification and the scope of the claims.

[0395] In the above exemplary system, the method is described as a series of steps or boxes based on the process diagram, but the order of the steps described is not limited, and as described above, some steps can occur in other orders or at the same time as other steps. In addition, those skilled in the art will understand that the steps shown in the process diagram are not exclusive, and other steps may be included or one or more steps in the process diagram may be deleted without affecting the scope of the rights.

[0396] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement an apparatus, and the technical features of the device claims of this specification may be combined to implement a method. In addition, the technical features of the method claims of this specification and the technical features of the device claims may be combined to implement an apparatus, and the technical features of the method claims of this specification and the technical features of the device claims may be combined to implement a method.

Claims

1. An operation method at a terminal, the method comprising: The step of receiving system information including access control related information for industrial signaling and / or data from a base station; The step of sending industrial signaling or data and determining the access category according to the access identifier occurs; Based on the access category and the access control related information, a step of performing a check for access control is performed; In case of passing from said checking, the step of determining a radio resource control establishment cause or a radio resource control resumption cause based on said access category; as well as The step of sending a radio resource control message including the determined radio resource control establishment cause or radio resource control resumption cause to the base station.

2. The method according to claim 1, wherein: The industrial signaling and / or data is traffic used for time-sensitive networking, time-sensitive communication, deterministic networking, ultra-reliable and low-latency communication, or industrial Internet of Things.

3. The method according to claim 1, wherein: The determined radio resource control establishment cause or radio resource control resumption cause is used to identify the industrial signaling and / or data.

4. The method according to claim 1, wherein: The access class is determined for the industrial signaling and / or data in order to pass the check for the access control.

5. The method according to claim 1, wherein: The determined access class has a high priority in order to allow the industrial signaling and / or data to pass the check for the access control.

6. The method according to claim 1, wherein: Even when congestion occurs in the wireless section with the base station, the industrial signaling and / or data passes the check for access control and the radio resource control message is transmitted.

7. The method according to claim 1, wherein: The terminal includes an application layer, a non-access layer and a radio resource control layer.

8. The method according to claim 7, wherein: The determining step comprises: A process in which the non-access layer determines the access category for the industrial signaling and / or data by receiving a notification from the application layer that the industrial signaling and / or data has occurred; and The non-access layer conveys the determined access category and access identifier to the radio resource control layer.

9. The method according to claim 8, wherein: The radio resource control layer performs a check for the access control based on the access class, the access identifier, and the received access control related information received from the non-access stratum layer.

10. A chipset installed in a terminal, the chipset comprising: at least one processor; as well as at least one memory storing instructions and being operably electrically connected to the at least one processor, and Based on the instruction being executed by the at least one processor, the operations performed include: The step of receiving system information including access control related information for industrial signaling and / or data from a base station; The step of sending industrial signaling or data and determining the access category according to the access identifier occurs; Based on the access category and the access control related information, a step of performing a check for access control is performed; In case of passing from the check, the step of determining a radio resource control establishment cause or a radio resource control resumption cause based on the access category; and The step of sending a radio resource control message including the determined radio resource control establishment cause or radio resource control resumption cause to the base station.

11. The chipset according to claim 10, wherein: The industrial signaling and / or data is traffic used for time-sensitive networking, time-sensitive communication, deterministic networking, ultra-reliable and low-latency communication, or industrial Internet of Things.

12. The chipset according to claim 10, wherein: The determined radio resource control establishment cause or radio resource control resumption cause is used to identify the industrial signaling and / or data.

13. The chipset according to claim 10, wherein: The access class is determined for the industrial signaling and / or data in order to pass the check for the access control.

14. The chipset according to claim 10, wherein: The determined access class has a high priority in order to allow the industrial signaling and / or data to pass the check for the access control.

15. The chipset according to claim 10, wherein: Even when congestion occurs in the wireless section with the base station, the industrial signaling and / or data passes the check for access control and the radio resource control message is transmitted.

16. A device for a terminal, the device comprising: Transceiver unit; at least one processor; as well as at least one memory storing instructions and being operably electrically connected to the at least one processor, and Based on the instruction being executed by the at least one processor, the operations performed include: The step of receiving system information including access control related information for industrial signaling and / or data from a base station; The step of sending industrial signaling or data and determining the access category according to the access identifier occurs; Based on the access category and the access control related information, a step of performing a check for access control is performed; In the case where the check passes, a step of determining a radio resource control establishment cause or a radio resource control recovery cause based on the access category; and The step of sending a radio resource control message including the determined radio resource control establishment cause or radio resource control resumption cause to the base station.

17. The device according to claim 16, wherein: The industrial signaling and / or data is traffic used for time-sensitive networking, time-sensitive communication, deterministic networking, ultra-reliable and low-latency communication, or industrial Internet of Things.

18. The device according to claim 16, wherein: The determined radio resource control establishment cause or radio resource control resumption cause is used to identify the industrial signaling and / or data.

19. The device according to claim 16, wherein: The access class is determined for the industrial signaling and / or data in order to pass the check for the access control.

20. The device according to claim 16, wherein: Even when congestion occurs in the wireless section with the base station, the industrial signaling and / or data passes the check for access control and the radio resource control message is transmitted.

Images