KR102128950B1 - Methods for controlling access control in next generation wireless network AND Apparatuses thereof - Google Patents

Abstract

The present disclosure is a technique for access control operation of a terminal in a next-generation mobile communication network. More specifically, the present disclosure relates to a method of performing integrated access control of a terminal and a method of performing specific access control for a service having low delay sensitivity. According to an embodiment of the present invention, in a method for a terminal to perform an access control operation, when an operator-defined access category information is received through a Non-Access Stratum (NAS) signaling and an access attempt of the terminal is triggered, a Non-Access Stratum (NAS) is triggered. ) Determining an access category for an access attempt at a layer or an access stratum (AS) layer, selecting RRC setting cause information associated with the access category, and using the access barring parameter associated with the access category AS ( It provides a method and apparatus comprising the step of performing an access barring (Access Barring) check operation in the Access Stratum (layer).

Description

Methods and controlling access control in next generation wireless network AND Apparatuses thereof

The present disclosure is a technique for access control operation of a terminal in a next-generation mobile communication network. More specifically, the present disclosure relates to a method of performing integrated access control of a terminal and a method of performing specific access control for a service having low delay sensitivity.

The terminal and the network perform communication using limited radio resources. In addition, each entity in the network utilizes limited resources for data processing. Therefore, when the terminal performs communication with the network, it may be determined whether or not access is possible due to various reasons.

For example, an access control function that performs congestion control of a conventional network is defined and performed in different protocol layers. This is because it is necessary to control overload according to a situation related to each layer. Depending on the access control function, the terminal may be restricted from accessing the base station or the RRC connection may be restricted. Through these limitations, the network performs congestion control to maintain the overall network data processing speed.

Meanwhile, next-generation mobile communication technologies are being researched in response to demands for large-capacity data processing and high-speed data processing. For example, in the current 3GPP series of mobile communication systems such as LTE (Long Term Evolution), LTE-Advanced, 5G, etc., a high-speed, large-capacity communication system capable of transmitting and receiving various data such as video and wireless data beyond voice-oriented services. This is required.

In such an environment, according to a conventional access barring (connection prohibition) mechanism defined by reflecting individual requirements, individual access prohibition functions using different solutions have to be implemented in the network and the terminal, and individual signaling for this must be defined and used. did. Accordingly, there is a problem in that complexity and signaling increase in network and terminal implementation.

Therefore, there is a need to solve this problem in the next generation mobile communication technology. In addition, there is a need to develop a technology for an integrated access control operation that allows a terminal to perform an integrated access control operation to provide a variety of services and to be flexibly applied to various situations that may occur in the next generation mobile communication.

In the above-mentioned background, the present disclosure intends to propose a method and apparatus for reducing complexity of a terminal and network implementation by integrating access control operations set in a separate mechanism according to each requirement.

In addition, the present disclosure intends to propose a method and apparatus for reducing signaling for access control by integrally controlling operations for access control.

In addition, the present disclosure intends to propose a specific access control method for a service that is relatively insensitive to delay in an integrated access control operation.

One embodiment devised to solve the above-described problems is a method in which a terminal performs an access control operation, the method comprising: receiving operator-defined access category information through non-access stratum (NAS) signaling and access attempt of the terminal When triggered, determining a single access category for an access attempt at a non-access stratum (NAS) layer or an access stratum (AS) layer, and selecting RRC setting cause information associated with the access category and associating with the access category It provides a method comprising the step of performing an access barring (Access Barring) check operation in the AS (Access Stratum) layer using the access barring parameters.

Further, according to an embodiment of the present invention, in a terminal performing an access control operation, when an access attempt of a receiving unit and a terminal receiving operator-defined access category information through NAS (Non-Access Stratum) signaling is triggered, a Non-Access Stratum (NAS) ) At the layer or the access stratum (AS) layer, one access category for an access attempt is determined, RRC setting cause information associated with the access category is selected, and an access stratum (AS) is used using an access barring parameter associated with the access category. It provides a terminal device including a control unit for performing an access barring (Access Barring) check operation in the layer.

The present disclosure provides an effect of preventing the waste of radio resources by reducing the implementation complexity of the terminal and reducing unnecessary signaling by providing an integrated access control operation in the next generation mobile communication technology.

In addition, the present disclosure provides an effect of increasing flexibility and efficiency by utilizing a service that is not sensitive to delay and an access category individually defined by an operator.

1 is a flowchart illustrating a terminal operation according to an embodiment.
2 is a diagram exemplarily showing a mapping table to which an access category is mapped according to an access attempt according to an embodiment.
FIG. 3 is a diagram exemplarily showing a table for explaining a mapping between an RRC setting cause and an access category according to an embodiment.
4 is a diagram exemplarily showing a mapping table to which access categories are mapped according to access attempts according to another embodiment.
5 is a view for explaining a message processing procedure in the conventional LTE technology.
6 is a diagram illustrating an example of a configuration of access access prohibition parameters for each access category according to an embodiment.
7 is a diagram exemplarily showing a mapping table to which an access category is mapped according to an access attempt according to another embodiment.
8 is a block diagram showing the configuration of a user terminal according to an embodiment.

Hereinafter, some embodiments of the present invention will be described in detail through exemplary drawings. It should be noted that in adding reference numerals to the components of each drawing, the same components have the same reference numerals as possible even though they are displayed on different drawings. In addition, in describing the present invention, when it is determined that detailed descriptions of related well-known structures or functions may obscure the subject matter of the present invention, detailed descriptions thereof will be omitted.

In the present specification, a wireless communication system means a system for providing various communication services such as voice and packet data. The wireless communication system includes a user equipment (UE) and a base station (BS).

The user terminal is a comprehensive concept that refers to a terminal in wireless communication, user equipment (UE) in WCDMA, LTE, HSPA and IMT-2020 (5G or New Radio), as well as MS (Mobile Station) in GSM, UT It should be interpreted as a concept including (User Terminal), SS (Subscriber Station), and wireless devices.

Base station or cell (Cell) generally refers to a station (station) to communicate with the user terminal, Node-B (Node-B), eNB (evolved Node-B), gNB (gNode-B), LPN (Low Power Node) ), Sector, Site, Antennas of various types, Base Transceiver System (BTS), Access Point, Point (e.g., transmit point, receive point, transmit/receive point), relay node ( Relay Node), mega cell, macro cell, micro cell, pico cell, femto cell, remote radio head (RRH), radio unit (RU), small cell (small cell).

Since the various cells listed above have a base station that controls each cell, the base station can be interpreted in two ways. 1) a device that provides a mega cell, a macro cell, a micro cell, a pico cell, a femto cell, or a small cell in relation to the radio area, or 2) the radio area itself. In 1), all devices that provide a predetermined wireless area are controlled by the same entity or interact to configure the wireless area in a collaborative manner. Points, transmission/reception points, transmission points, reception points, and the like, according to a configuration method of a wireless area, are examples of a base station. In 2), the radio area itself, which receives or transmits a signal from the viewpoint of the user terminal or the neighboring base station, may indicate to the base station itself.

In this specification, a cell is a component carrier having a coverage of a signal transmitted from a transmission/reception point or a signal transmitted from a transmission/reception point, or a transmission/reception point itself. Can.

In the present specification, the user terminal and the base station are two (Uplink or Downlink) transmitting and receiving subjects used to implement the technology or technical idea described in the present invention, which are used in a comprehensive sense and are not limited by specific terms or words. Does not.

Here, uplink (Uplink, UL, or uplink) refers to a method of transmitting and receiving data to the base station by the user terminal, downlink (Downlink, DL, or downlink) transmits and receives data to the user terminal by the base station Means the way.

For uplink transmission and downlink transmission, a time division duplex (TDD) method transmitted using different times may be used, and a frequency division duplex (FDD) method, TDD method, and FDD method transmitted using different frequencies may be used. Mixing methods can be used.

In addition, in a wireless communication system, an uplink and a downlink are configured based on one carrier or a pair of carriers to configure a standard.

Uplink and downlink transmit control information through control channels such as PDCCH (Physical Downlink Control CHannel), PUCCH (Physical Uplink Control CHannel), and PDSCH (Physical Downlink Shared CHannel), PUSCH (Physical Uplink Shared CHannel), etc. It consists of the same data channel and transmits data.

Downlink (downlink) may mean a communication or communication path from a multiple transmit and receive points to a terminal, and uplink (uplink) may mean a communication or communication path from a terminal to multiple transmit and receive points. At this time, in the downlink, the transmitter may be a part of multiple transmission/reception points, and the receiver may be a part of the terminal. In addition, in the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of the multiple transmission/reception points.

Hereinafter, a situation in which signals are transmitted/received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is also described in the form of'transmit and receive PUCCH, PUSCH, PDCCH and PDSCH'.

Meanwhile, High Layer Signaling described below includes RRC signaling for transmitting RRC information including RRC parameters.

The base station performs downlink transmission to the terminals. The base station transmits downlink control information such as scheduling required for reception of a downlink data channel, which is a main physical channel for unicast transmission, and physical downlink for transmitting scheduling approval information for transmission in an uplink data channel. The control channel can be transmitted. Hereinafter, the transmission and reception of signals through each channel will be described as a form in which the corresponding channel is transmitted and received.

There are no restrictions on the multiple access technique applied in a wireless communication system. Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Non-Orthogonal Multiple Access (NOMA), OFDM-TDMA, OFDM-FDMA, Various multiple access techniques such as OFDM-CDMA can be used. Here, NOMA includes SCMA (Sparse Code Multiple Access) and LDS (Low Density Spreading).

One embodiment of the present invention is to allocate resources such as asynchronous wireless communication evolving to LTE/LTE-Advanced, IMT-2020 through GSM, WCDMA, HSPA, and synchronous wireless communication evolving to CDMA, CDMA-2000 and UMB. Can be applied.

In this specification, a Machine Type Communication (MTC) terminal may mean a terminal supporting low cost (or low complexity) or a terminal supporting coverage enhancement. Alternatively, in this specification, the MTC terminal may mean a terminal defined as a specific category for supporting low cost (or low complexity) and/or coverage enhancement.

In other words, in this specification, the MTC terminal may mean a newly defined 3GPP Release-13 low cost (or low complexity) UE category/type that performs LTE-based MTC-related operations. Or, in this specification, the MTC terminal supports enhanced coverage compared to the existing LTE coverage, or UE category/type defined under the existing 3GPP Release-12 or lower supporting low power consumption, or the newly defined Release-13 low cost (or low complexity) UE category/type. Or, it may mean a further enhanced MTC terminal defined in Release-14.

In this specification, a NB-IoT (NarrowBand Internet of Things) terminal means a terminal supporting wireless access for cellular IoT. The objectives of the NB-IoT technology include improved indoor coverage, support for large-scale low-speed terminals, delay sensitivity, ultra-low-cost terminal costs, low power consumption, and optimized network architecture.

As a representative usage scenario in New Radio (NR), which is currently being discussed in 3GPP, enhanced Mobile BroadBand (eMBB), Massive Machine Type Communication (mMTC), and Ultra Reliable and Low Latency Communication (URLLC) have been proposed.

In this specification, frequency, frame, subframe, resource, resource block, region, band, subband, control channel, data channel, synchronization signal, various reference signals, various signals, various messages related to NR (New Radio) Can be interpreted as meaning used in the past or present or various meanings used in the future.

For example, LTE and NR in this specification refer to different radio access technologies, and the new radio access technologies under discussion in Release-15 of 3GPP are described as NR. NR may include various differences such as LTE and other frame structures, channels, and core network technologies, and various functions for wireless transmission in a high band, ultra high speed, and large data transmission may be added.

The embodiments described below may be applied to terminals, base stations, and core network entities (eg, MME, AMF, etc.) using next-generation mobile communication (5G mobile communication, New-RAT, NR). If necessary, the base station is a base station (CU, DU, or CU and DU) in a 5G wireless network in which a central unit (CU) and a distributed unit (DU) are separated. Individual), gNB, and the like.

In addition, for convenience of understanding, the conventional wireless access technology is described as LTE, and the new wireless access technology discussed in 3GPP is described as NR. In addition, the base station may be an eNB using LTE technology, or a gNB using NR technology, and will be described separately according to need.

NR (New Radio)

3GPP recently approved "Study on New Radio Access Technology", a study item for research on next-generation/5G radio access technology, based on which frame structure, channel coding and modulation for NR (New Radio), waveform and Discussion of the frame structure, channel coding & modulation, waveform & multiple access scheme, etc. has begun.

NR is required to be designed to satisfy various requirements required for each segmented and specific usage scenario as well as an improved data rate compared to LTE/LTE-Advanced. In particular, as a representative usage scenario of NR, enhancement mobile BroadBand (eMBB), massive MTC (mMTC), and Ultra Reliable and Low Latency Communications (URLLC) have been raised, and requirements for each usage scenario are presented. As a method for satisfying, a flexible frame structure design compared to LTE/LTE-Advanced is required.

Specifically, eMBB, mMTC, and URLLC are considered as representative usage scenarios of NR under discussion in 3GPP. Since each usage scenario has different requirements for data rates, latency, and coverage, each usage scenario is used through a frequency band constituting an arbitrary NR system. Efficient multiplexing of radio resource units based on different numerology (eg subcarrier spacing, subframe, TTI, etc.) as a method for efficiently satisfying the requirements for each scenario There is a need for a way to (multiplexing).

As one method for this, multiplexing is supported based on TDM, FDM or TDM/FDM through one NR carrier for numerology having different subcarrier spacing (SCS) values. Discussion has been made of a method and a method of supporting one or more time units in configuring a scheduling unit in a time domain. In this regard, in NR, a subframe is defined as a type of time domain structure, and a reference numerology for defining a corresponding subframe duration. As, it was decided to define a single subframe duration composed of 14 OFDM symbols of normal CP overhead based on 15 kHz SCS (Sub-Carrier Spacing), which is the same as LTE. Accordingly, the subframe in NR has a duration of 1 ms. However, unlike LTE, the subframe of NR is an absolute reference time duration, a slot and a mini-slot as a time unit based on actual uplink/downlink data scheduling. ) Can be defined. In this case, the number of OFDM symbols constituting the slot and the y value are determined to have a value of y=14 regardless of the neuromerology.

Accordingly, an arbitrary slot may be composed of 14 symbols, and all symbols may be used for DL transmission or all symbols may be uplink transmitted according to a transmission direction of the corresponding slot. UL transmission), or may be used in the form of a DL portion + (gap) + UL portion.

In addition, a mini-slot consisting of fewer symbols than the corresponding slot is defined in any numerology (or SCS), and based on this, a short-length time domain scheduling interval for transmitting/receiving uplink/downlink data (time-domain The scheduling interval may be set, or a long-time time-domain scheduling interval for transmitting/receiving uplink/downlink data through slot aggregation may be configured.

In particular, in case of transmitting/receiving for latency critical data such as URLLC, a slot based on 0.5ms (7 symbols) or 1ms (14 symbols) defined in a pneumatic structure based on a small SCS value such as 15kHz. When scheduling is performed in units, it may be difficult to satisfy the latency requirement, so for this, a mini-slot consisting of fewer OFDM symbols than the corresponding slot is defined and based on the URLLC. It can be defined such that scheduling is performed for delay critical data.

As described above, by defining different SCS or different TTI lengths in NR, technologies satisfying the requirements of URLLC and eMBB are being developed, and new technical elements are being developed from various viewpoints such as LTE, transport unit structure, and scheduling method. .

The access barring in the present specification should be interpreted as meaning including an access barring check operation for checking whether access is prohibited as a kind of access control operation performed by the terminal for the purpose of network congestion control and the like. Accordingly, access barring may be modified in various terms such as congestion control, access control, access prohibition, access check, barring check, access restriction, access barring, etc., and should be construed as being included in the present disclosure.

Hereinafter, the connection control operation in the conventional LTE mobile communication technology and the problems thereof and the purpose of the present disclosure will be briefly described.

Access barring technology in LTE

In the conventional LTE technology, an access control function providing congestion control of a network is defined in different protocol layers. Accordingly, it was possible to control overload according to a situation related to each layer. The LTE access control function is a RACH backoff function used when a base station experiences an overload during a random access procedure, a function of a base station rejecting an RRC connection according to radio resource conditions and load for an RRC connection request or releasing a connected RRC connection, In addition, there is an access barring function that prevents a terminal from sending signaling for an access request to a network by a base station.

The access barring mechanism enables efficient load reduction by preventing the terminal from sending signaling for an access request to the network with terminal-based access control.

In the conventional LTE (E-UTRAN), various access prohibition mechanisms have been defined and used. This is because various mechanisms have been defined to reflect various service requirements that have gradually occurred according to the commercialization and construction process of LTE technology. Each mechanism uses a different solution. For example, an access class barring (ACB) that provides access barring for a specific access class terminal is executed in an access stratum (AS) layer. On the other hand, SSAC (Service Specific Access Control) is implemented in the application layer because it provides additional control for MMTEL (Multimedia Telephony) voice calls applied to the IP Multimedia Subsystem (IMS) layer. Application specific congestion control for data communication (ACDC) is executed at the AS layer, but it is necessary to use definitions outside 3GPP, such as application ID. For this reason, standardization outside 3GPP is required, and otherwise, it may be a factor that may make application in the terminal and the network difficult. In addition, various access prohibition mechanisms such as ACB skipping ACB for voice, skipped ACB, and extended access barring (EAB) for access control to MTC terminals control access from different services, thereby preventing individual access prohibition. And implemented in the terminal. In addition, it is necessary to define and apply individual signaling for this.

3GPP is currently conducting a study on next-generation/5G radio access technology (for convenience of description, NR will be described below). A function for satisfying various requirements not provided by LTE may be added to the NR. Among these functions, it is necessary to include a unified access control/barring mechanism that satisfies various use cases and scenarios defined in LTE. However, no specific method has been proposed for this.

Hereinafter, for convenience of description, the integrated access control/prohibition mechanism will be described as integrated access control. In this specification, a method of performing integrated access control by a terminal is described, and various embodiments in individual operations are divided into detailed embodiments and described. In addition, an embodiment of performing access control for a service that is not sensitive to delay will be described separately below, and one or more embodiments disclosed in this specification may be applied to a terminal individually or through a mutual combination. In addition, the present disclosure can be applied to any mobile communication/fixed communication/wireless communication network including LTE as well as the next generation mobile communication (5G mobile communication) network.

First, the integrated access control operation of the terminal will be described first.

In the integrated access control operation, the NAS of the terminal may provide access category information to the RRC (AS) of the terminal for at least the RRC IDLE terminal or the RRC INACTIVE terminal. And when the terminal sends an RRC connection request message for establishing an RRC connection to the base station, the base station may determine whether to reject the connection request. To this end, the terminal may include establishment cause information in the transmission message for establishing the RRC connection to the base station.

In the conventional LTE technology, a 3-bit field is used for setting cause information. If the access category is included in the message 3 (MSG3) as a setting cause for integrated access control, more bits may be required, which may cause insufficient MSG3 resource consumption. Therefore, there is a need for a method that can effectively provide this.

The present disclosure, which was devised to solve these problems, aims to provide a method and apparatus for providing efficient integrated access control that satisfies various use cases and scenarios in a next-generation mobile communication network. Explain.

1 is a flowchart illustrating a terminal operation according to an embodiment.

Referring to FIG. 1, a method for a terminal to perform an access control operation may include receiving operator-defined access category information through non-access stratum (NAS) signaling (S110).

For example, the terminal may perform a connection control operation using a reference access category received from the base station or operator-defined access category information received from the base station through NAS signaling.

For example, the reference access category may be configured with a mapping table that is mapped to determine the access category according to the type of access attempt of the terminal.

As another example, the operator-defined access category may include at least one of an access category number, a 5G QoS Identifier (5QI), an application identifier that triggers an access attempt, and specific PDU session information associated with the slice.

Meanwhile, the reference access category and the operator-defined access category are, for example, terms for explanation, and are not limited to the terms. That is, the reference access category means category information that is applied equally regardless of the operator, and the operator-defined access category means category information set and used by an operator operating each base station. The reference access category and the operator-defined access category may each include a plurality of category information, and the terminal may select one or more access categories to be described below from a set of categories in which the corresponding categories are collected.

On the other hand, the method for the terminal to perform the access control operation, when the access attempt of the terminal is triggered, determining a single access category for the access attempt in the Non-Access Stratum (NAS) layer or the Access Stratum (AS) layer It can be done (S120).

For example, the terminal may store operator-defined access category information in the terminal, and detect whether the access attempt of the terminal is triggered. In the case of an access attempt, it may occur when a terminal establishes an RRC connection with a base station. Or, an access attempt may be generated in order for the terminal to communicate with the base station.

For example, the UE may determine that an access attempt of the UE is triggered when a state transition occurs from the RRC idle state to the RRC connected state or when the UE initiates a PDU session in the RRC connected state.

As another example, when an emergency signal is required to be transmitted, the terminal may determine that an access attempt is triggered when a response to a paging signal, an access attempt for a low-latency service, or a terminal transmission of voice data is triggered.

In addition to this, the terminal may determine that an access attempt is triggered in various situations according to the setting of the terminal, which may be variously set according to the type of the access attempt as shown in FIGS. 2, 4, and 7.

When the access attempt is triggered, the terminal may select any one of the access category information stored/configured in the terminal. For example, one access category selected by the terminal means category information selected from a set of access categories including a reference access category and operator-defined access category information.

As described above, the terminal may select an access category that is divided and set for each access attempt. For example, the terminal may determine the access category indicated by the access attempt by checking the rules according to the rule number order of the mapping table in which one or more access categories are assigned for each access attempt. To this end, the terminal uses a mapping table to which access attempts and access categories are mapped.

2 is a diagram exemplarily showing a mapping table to which an access category is mapped according to an access attempt according to an embodiment.

Referring to FIG. 2, the mapping table may be configured such that the rule number (Rule #) and the type of access attempt and the access category are mapped. Further, the mapping table may be configured using the reference access category described above, or may be configured using an operator-defined access category. Alternatively, the mapping table may be configured using both a reference access category and an operator-defined access category. That is, as configured in FIG. 2, rule numbers 1, 2, and 4 to 9 of the mapping table are configured to indicate a mapping of a reference access category and an access attempt, and rule number 3 can be configured to be mapped to an operator-defined access category. . To this end, access categories 32-63 may be configured such that operator-defined access categories and access attempts are mapped.

Accordingly, the terminal may check each access attempt according to the rule number using the mapping table configured as shown in FIG. 2 and select an access category mapped to the access attempt when a triggered access attempt exists.

Meanwhile, when the terminal checks a rule according to the mapping table and there is more than one access category mapped to the access attempt, the terminal may determine the access category with the lowest rule number as the access category. For example, although an access attempt for a delay immunity service (a service having low delay sensitivity) has been triggered, there may be a case where the specific access attempt is included in an operator-defined access category. That is, access attempts can be mapped to both the reference access category and the operator-defined access category. In this case, since the rule number associated with the operator-defined access category is 3 and the rule number for the delay immunity service is 4, the terminal can select 3 operator-defined access categories with a relatively low rule number.

Or, by checking the access attempt from the lower rule number of the mapping table, the terminal may stop checking the further rule number if an access attempt matching the triggered access attempt exists and select an access category mapped to the access attempt. . That is, it is possible to select an access category mapped to an access attempt by checking the lower rule number, rather than checking all rule numbers.

To this end, the rule number of the mapping table may be set to check for a specific access attempt from a low number. For example, the rule number of the access attempt mapped to the operator-defined access category may be set smaller than the rule number of the access attempt for the delay immunity service. Since the delay immunity service is a service that is not sensitive to delay, the rule number can be placed higher than an emergency service attempt or an operator-defined access attempt.

Meanwhile, the method for the terminal to perform the access control operation may include selecting RRC setting cause information associated with the access category (S130). The terminal may select an access category according to the access attempt using a mapping table, and select RRC setting cause information associated with the selected access category. Also, as shown in FIG. 2, one or more reference access categories may be set in association with an operator-defined access category.

FIG. 3 is a diagram exemplarily showing a table for explaining a mapping between an RRC setting cause and an access category according to an embodiment.

Referring to FIG. 3, the terminal selects an access category associated with an access attempt from one or more reference access categories, and selects an RRC setting cause mapped to the access category. The reason for setting the access category and the RRC may be linked through a separate mapping table. That is, the access category and the cause of RRC establishment may be mapped according to a one-to-one mapping relationship. The access category in FIG. 3 may be the access category selected in FIG. 2, and FFS refers to a portion that can be determined according to the terminal or operator selection. Alternatively, FFS indicates a portion that has not been determined yet. That is, various setting causes may be assigned to the FFS portion.

Also, the method for the terminal to perform the access control operation may include performing an access barring check operation in the access stratum (AS) layer using the access barring parameter associated with the access category (S140). . The terminal may perform an access barring check operation using the access barring parameters stored in association with the selected access category. The access barring parameter may be received from the base station or may be stored in advance in the terminal, and the value may be set differently for each access category. Accordingly, the terminal checks the access barring parameter configured in association with the determined access category, and applies the corresponding parameter to perform the access barring check operation.

As described above, the terminal configures a mapping table using a reference access category and an operator-defined access category, and selects an access category for each access attempt according to the configured mapping table. Further, the terminal may perform an access barring check operation by applying an access barring parameter configured for each access category. That is, the terminal can perform an integrated access barring operation, and even when the operator changes, the access barring check operation can be performed through the same procedure by changing the corresponding mapping table. Therefore, it is possible to satisfy various services and requirements required by the NR, and it is possible to prevent a duplicate access barring check operation.

Hereinafter, another embodiment of the above-described integrated access control operation of the terminal will be described. Each embodiment described below may be applied individually to the embodiment of FIG. 1 or may be applied to a terminal through some combinations. In addition, some configurations of the embodiment of FIG. 1 may be changed or combined to the configurations of each embodiment described below to be applied to the terminal. Alternatively, each embodiment described below may be applied as a detailed embodiment of each step of FIG. 1.

4 is a diagram exemplarily showing a mapping table to which access categories are mapped according to access attempts according to another embodiment.

Referring to Figure 4, the access category may have a number from 0 to 63. For an RRC IDLE terminal or an RRC INACTIVE terminal, when the corresponding terminal intends to establish an RRC connection, the NAS of the terminal may provide access category information to the RRC (AS) of the terminal. The NAS of the terminal may additionally provide access attempt type information to the RRC of the terminal in addition to the access category information.

The RRC of the terminal may establish an RRC connection or resume the RRC connection by using the following methods individually or in combination. That is, an RRC connection request message or an RRC connection resume message can be transmitted.

How to instruct information to be included in the cause or resumption of RRC connection through system information

When the terminal transmits an RRC connection request message for establishing an RRC connection to the base station, the terminal may include information for use in determining whether the connection request is rejected. For example, the terminal may include information about the cause of establishment (establishment cause) in the corresponding RRC connection request message.

Similarly, when the UE sends an RRC connection resume request message for resuming the RRC connection to the base station, the terminal may include information for use in determining whether to reject the connection resume request. For example, the UE may include resume cause information in the RRC connection resume request message. In the present specification, for convenience of explanation, information for reference in determining whether a request is rejected by a base station is described based on a set cause, but the present disclosure may be applied to a reopener. That is, in the case of the setting cause, it is included in the RRC connection request message, and in the case of the resumption cause, it is included in the RRC connection resumption request message, and the operation of the terminal and the characteristics of the information are equally applied. Meanwhile, the standardized access category information below means the reference access category information described above, and the access category designated by the operator may mean the operator-defined access category information described above.

If the operator classifies and uses the access categories 0 to 63, if the terminal classifies and includes the access category as a setting cause in the RRC connection establishment request, a value of at least 6 bits may be required. If the RRC INACTIVE terminal, such as RAN location area update (RLAU), includes initiating RRC connection setup/resume triggered by the AS as a set cause/resume cause, an additional 1 bit value may be required. That is, a 7-bit value may be required.

As described above, the resource for the RRC connection request or RRC connection resume request message provided through the CCCH channel is the number of bits because the terminals in the cell must use the resource by sharing the resource or have priority over other RRC messages provided through the DCCH channel. It is desirable to minimize.

To this end, the base station may broadcast information including information for indicating the number of bits to be provided as a setting cause in the RRC connection establishment request through the system information.

For example, the base station may broadcast by including information for indicating the number of bits to be provided as a setting cause in 4 bits (0 to 15). In this case, as an example, the terminal may use access category numbers 0 to 8 as values of 0 to 8 as a setting source. Seven values remain as the remaining setting source values of 9 to 15. Some of these 7 values can be used by mapping them to access category numbers 9-31 reserved as standardized access categories (reference access categories). And the rest of these 7 values can be used by mapping to the access category number (operator-defined access category) number 32-63 that can be specified by the operator.

For another example, the base station may broadcast including information for indicating the number of bits to be provided as a setting cause with 5 bits (0 to 31). In this case, as an example, the terminal may use the access category number from 0 to 8 as a value of 0 to 8 as a setting source. 23 values remain as the values of the setting cause 9~31. Some of these 23 values can be mapped to access category numbers 9-31 reserved for standardized access categories. And the rest of these 23 values can be used by mapping to access category numbers 32-63 that can be specified by the operator.

For another example, the base station may broadcast information including information for indicating 3 bits (0 to 7) of the number of bits to be provided as a setting cause.

As another example, the base station may broadcast including information to indicate that the operator does not use the assigned/delimited access category 32-63.

For another example, the base station may broadcast including information to indicate that it does not use the reserved access category (9-31).

As another example, the base station may broadcast including information to indicate that the reserved access category 9-31 and the operator do not use the assigned/delimited access category 32-63.

If the network does not use reserved access categories (9-31) or operator-defined access categories (32-63), only the access categories 0 to 9 are included. Therefore, by grouping access categories that can be processed with similar priority among the access categories 0 to 9, a value to be used as a setting cause value of the RRC connection request message can be further reduced. This will be described later separately.

Meanwhile, information for indicating the number of bits to be provided as the above-described setting cause may be provided through Minimum SI. Alternatively, information for indicating the number of bits to be provided as the above-described setting cause may be provided through other SI/general SIB.

Alternatively, the information for indicating the number of bits to be provided as the setting cause may include mapping rule information between the corresponding access category and the setting cause.

Alternatively, in order to prevent the use of additional bits, a setting cause/resume cause triggered in the AS, such as RAN location area update (RLAU), may be designated and used as one of access category values. For example, it is possible to use a value of one of 9-31 reserved for a standardized access category. For another example, the setting cause/resume cause triggered in the AS, such as RAN location area update (RLAU), can be set to use one of 32-63 that can be specified by the operator.

Alternatively, the information described in the above-described embodiments may be included in the RRC connection release message and indicated to the terminal. Alternatively, the base station may indicate by including the value mapping/rule/relation information that is a setting cause for each access category in the access barring configuration information. Alternatively, the base station may indicate a value mapped to a setting cause of an RRC connection request for each access category. Alternatively, the information described in the above-described embodiments may be stored by being instructed to the terminal through NAS signaling by a core network entity (control plane core network entity).

Alternatively, the information described in the above-described embodiments may be pre-configured in a storage device (for example, USIM/SIM) in the terminal or the information may be indicated and stored by an operator (via a related server such as a core network object or OTA). have. For example, the base station may indicate a value/rule/relationship mapped to a setting cause of an RRC connection request for each access category.

How to use the same set cause value for similar access categories to use fewer bits

As described above, the resource for the RRC connection request or RRC connection resume request message provided through the CCCH channel is the number of bits because the terminals in the cell must use the resource by sharing the resource or have priority over other RRC messages provided through the DCCH channel. It is desirable to minimize.

In order to reduce the number of bits of a setting cause or resumption of the terminal, the RRC of the terminal may use the same setting cause value for similar access categories or for specific types of access categories.

The NAS of the terminal may provide access category information to the RRC (AS) of the terminal. The NAS of the terminal may additionally provide access attempt type information to the RRC of the terminal in addition to the access category information.

For example, an access category having a higher priority than the normal priority may be used as a set cause value. For example, MO signaling resulting from paging, such as access category 0, is an access category that is initiated for processing incoming data by the base station and must be prioritized so that terminal prohibition is not required. The access category 0 can be classified into an access category to be prioritized compared to the general priority, and mapped and used to have a setting cause value to be prioritized. A terminal that maintains a specific AC number (AC11~15) such as access category 1 requires specific priority processing such as PLMN staff, emergency service, public utilities, security service, PLMN use, etc., and has priority over general priority. It can be an access category that should be. The access category 1 may be classified into an access category to be prioritized compared to the general priority, and mapped and used to have a setting cause value to be prioritized. Emergency calls such as access category 3 are also access categories that should be prioritized. The access categories 5 (voice), 6 (video), and 7 (SMS) may be included in the basic communication service, and one or more access categories among the access categories 5, 6, and 7 are also access categories to be prioritized compared to the general priority. Can. As another example, access category 5 (speech) may be an access category to be prioritized. As another example, access categories 5 (speech) and 7 (SMS) may be used as access categories to be prioritized. For another example, access categories 5 (speech), 6 (video), and 7 (SMS) can be set as access categories to be prioritized. One or more access categories among access categories 5, 6, and 7 may be classified into access categories to be prioritized compared to general priorities, and may be mapped and used to have a setting cause value to be prioritized.

As another example, one or more access categories of the reserved access categories 9-31 may be divided into access categories to be prioritized. It is possible to classify and use one or more access categories from the access categories 9-31 as access categories that should be prioritized compared to general priorities, so as to have a setting cause value to be prioritized.

As another example, one or more access categories of operator-defined access categories 32-63 may be divided into access categories to be prioritized. One or more access categories of access categories 32-63 can be classified into access categories that should be prioritized compared to general priorities, and can be mapped and used to have a setting cause value to be prioritized.

As another example, one or more access categories of access categories 0, 1, 3, 5, 6, and 7 may be mapped and used as a setting cause value for priority processing. As another example, one or more access categories of access categories 9-31 or one or more access categories of 32-63 may be mapped and used as a setting cause value for priority processing.

For another example, an access category having a higher priority than the normal priority can be used by being divided into two setting cause values. As an example, an access category 0 may be used as a setting cause value for priority processing. In addition, access categories 1, 3, 5, 6, and 7 can be used as a setting cause value for suboptimal processing. As another example, access categories 0 and 3 may be used as a setting cause value for priority processing. In addition, access categories 1, 5, 6, and 7 may be used as a setting cause value for suboptimal processing. As another example, one or more access categories of access categories 0, 1, 3, 5, 6, and 7 may be mapped and used as a setting cause value for priority processing. In addition, one or more access categories among access categories 0, 1, 3, 5, 6, and 7 may be mapped to and used from among access categories not included in the set cause value for the highest priority processing as a setting cause value for suboptimal processing. As another example, one or more access categories of access categories 9-31 or one or more access categories of 32-63 may be mapped and used as a setting cause value for subpriority processing.

For another example, an access category having a priority value similar to normal or normal or normal/normal may be used as a set cause value.

For another example, an access category having a normal or normal or similar priority value may be used as a set cause value. For example, MO signaling by NAS signaling initiation, such as access category 4, and MO data such as access category 8 are used for access categories for purposes such as network access/attach/tracking area update/service request/transmission data transmission of a general terminal. It corresponds. One or more access categories may be provided as one setting cause value. For another example, in addition to the access categories 4 and 8, one or more values of the access categories 6, 7, 9-31 may be provided as one set cause value.

For another example, the reserved access category 9-31 can be used as a set cause value.

For another example, the access category 32-63 assigned/delimited by the operator may be used as a set cause value.

For another example, the access categories 32-63 designated/divided by the operator can be used by dividing them into values that are the cause of setting high priority processing and low priority processing.

For another example, the access categories 32-63 specified/divided by the operator may be divided into high priority processing, normal priority processing, and low priority processing.

For another example, the access category 2 is an access class for processing with a lower priority than the normal priority, and thus may include a value that is a set cause for this.

For another example, a setting cause/resume cause triggered in the AS, such as a RAN location area update (RLAU), may be used as one of access category values or as a set cause value.

For another example, a total of 64 access categories can be grouped and mapped and used as a setting cause value of 3 bits. As an example, the access categories may be classified in the order of n priority. Here, n may be a value of one of 3 to 7 natural numbers.

For another example, an access category not included in access barring configuration information provided in an unspecified access category or system information or RRC connection release message out of a total of 64 access categories is mapped to a default setting source value. Can.

As another example, the default setting cause may use a setting cause value mapped to an access category having a normal priority.

For another example, an access category that is not mapped to a specific setting cause value among a total of 64 access categories may be mapped and used as a default setting cause value.

In this way, the number of set cause values can be reduced by mapping a plurality of access categories to set cause values. Hereinafter, a value of a setting cause that can be configured through the above-described setting cause value mapping method will be described.

If the setting cause is divided into three types, a high priority setting cause, a normal priority setting cause, and a low priority setting cause, only 2 bits can be used as the setting cause value of the RRC connection request, and one spare bit remains. In the future, for consideration of scalability, 3 bits may be used and 5 spare bits may be left.

If the setting cause is divided into 4 types, the high priority setting cause, the normal priority setting cause, the low priority setting cause, and the operator/designated/determined setting cause, only 2 bits can be used as the setting cause value of the RRC connection request. have. It is possible to use 3 bits and leave 4 spare bits for future scalability.

If the setting cause is divided into 4 types, the high priority setting cause, the normal priority setting cause, the low priority setting cause, and the operator/designated/determined setting cause, only 2 bits can be used as the setting cause value of the RRC connection request. have. It is possible to use 3 bits and leave 4 spare bits for future scalability.

If the setting cause is divided into 5 types, the highest priority setting cause, the next priority high priority setting cause, the normal priority setting cause, the low priority setting cause, and the operator-designated/determined setting cause, the RRC connection request Only 3 bits can be used as the setting cause value. You can leave 3 spare bits.

If the cause of setting is the highest priority setting cause, the next priority is the high priority setting cause, the normal priority setting cause, the low priority setting cause, the high priority setting cause assigned/delimited by the operator, and the low assigned/delimited by the operator If it is divided into 6 types of priority setting cause, only 3 bits can be used as the setting cause value of RRC connection request. Two spare bits can be left.

If the default cause is included in the set cause, the bits used as the set cause in the above examples can be increased by 1 bit and the spare bit can be decreased by 1 bit.

On the other hand, even if they have the same setting cause, the network can indicate different access barring configurations for different access categories included in the same setting cause through system information. Since the terminal performs RRC connection request when the barring check according to the access barring configuration indicated for the corresponding access category is successful, distinguishing whether to reject the request is the same priority setting cause by grouping access categories with similar priorities. It may be possible to have

Meanwhile, the above-described methods may be pre-configured and performed in the terminal and the base station.

Alternatively, the above-described methods may be performed by being instructed by the base station to the terminal by system information or information included in the RRC connection release message. For example, mapping/rule/relation information that is a setting cause for each access category may be indicated in the access barring configuration information. For another example, a value mapped to a setting cause of an RRC connection request for each access category may be indicated.

Alternatively, the information described in the above-described embodiments may be stored by being instructed to the terminal through NAS signaling by a core network entity (control plane core network entity).

Alternatively, the information described in the above-described embodiments may be pre-configured in a storage device (for example, USIM/SIM) in the terminal or the information may be indicated and stored by an operator (via a related server such as a core network entity or OTA). For example, a value mapped to a setting cause of an RRC connection request for each access category may be indicated.

The terminal may transmit an RRC connection request message including a setting cause value using the information or method described in the above-described embodiments to the base station.

How to include access category information in an RRC connection setup complete or RRC connection resume complete message

5 is a view for explaining a message processing procedure in the conventional LTE technology.

Referring to FIG. 5, the terminal 500 transmits a random access preamble to the base station 110 (S500). Thereafter, the terminal 500 receives a random access response from the base station 510 (S501), and requests the RRC connection reset to the base station 510 (S502).

The base station 510 sets the RRC connection setup to the terminal 500 (S503), and the terminal 500 reports completion (S504).

When the RRC connection setup is completed to the terminal 500, the base station 510 transmits an initial terminal message to the MME 520 to request a service (S505). The MME 520 requests the initial context setup to the base station 510 (S507). Between steps S505 and S507, the base station 510 may set the measurement configuration by sending an RRC connection reconfiguration message to the terminal 500 (S506). When the measurement configuration is completed, the terminal 500 transmits an RRC connection reconfiguration message to the base station 510 (S508).

The base station 510 transmits a security mode command to the terminal 500 (S509), and receives a response thereto (S510).

Thereafter, the base station 510 transmits an RRC connection reconfiguration message for radio bearer setup to the terminal 500 (S511), and receives a response thereto (S512). The base station 510 transmits a response to the initial context setup to the MME 520 (S513), and the MME 520 transmits a bearer modification request to the gateway 530 (S514).

The terminal 500 transmits a UDP/IP packet to the base station 510 (S515), and the base station 510 transmits the packet to the gateway 530 (S516). The gateway 530 forwards the response to the bearer modification to the MME 520 (S517), and forwards the UDP/IP packet response to the base station 510 (S518). The base station 510 forwards the corresponding packet to the terminal 500 (S519).

Through this procedure, the terminal 500 delivers the packet to the core network.

Thereafter, the terminal 500 transmits the measurement report to the base station 520 periodically or when an event occurs according to the measurement configuration (S520). The base station 520 determines whether to release the terminal 500 based on the measurement report or the deactivation timer (S521). When the RRC connection release of the terminal 500 is determined, the base station 510 requests the MME 520 to release the terminal context (S522). The MME 520 commands the terminal context release to the base station 510 (S523), and the base station 510 instructs the terminal 500 to release the RRC connection accordingly (S524).

After releasing the RRC connection of the terminal 100, the base station 510 transmits a response to the MME 520 (S525).

Through this procedure, the terminal and the base station perform a connection operation and perform a release operation.

On the other hand, as described above, resources for RRC connection request or RRC connection resume request message provided through the CCCH channel must be prioritized than other RRC messages provided through the DCCH channel or used by the resources in the cell. It is desirable to minimize the number. For example, it may be undesirable to include 6-bit access category information in an RRC connection request or RRC connection resume request message.

However, the 0~63 access category information may be necessary for a base station or a core network entity to utilize congestion control for a corresponding terminal.

As an example for solving this, access category information may be included in an RRC connection setup complete or RRC connection resume complete message.

The access category information may cause a base station or a core network entity to use the information. In order to enable the core network entity to use the information, the base station transmits specific access category information received through RRC connection setup complete or RRC connection resume complete to a message between the base station and the core network entity (for example, the initial UE message). It can be transmitted. The specific access category to be included in the message between the base station and the core network entity described above may be pre-configured by the base station or may be indicated through the core network entity. Alternatively, the base station may always transmit the access category sent by the terminal to the core network entity.

The method can be used in combination with other embodiments described above.

Meanwhile, hereinafter, matters that can be considered for integrated access control will be described.

As an example for providing integrated access control, a specific terminal (or a specific application or specific service or specific procedure or specific subscription information or specific QoS class mapping flow or specific authorization authentication check or specific RRC state or specific access barring check layer) by an operator as an example. A category for providing a separate access prohibition may be classified according to each other, and an access control operation classified for each access category may be performed. The operator designates a specific terminal (or specific application or specific service or specific procedure or specific subscription information or specific QoS class mapping flow or specific authorization authentication or specific RRC state or specific access barring check layer) through a network as a specific category, or The operator is configured to designate a specific terminal (or specific application or specific service or specific procedure or specific subscription information or specific QoS class mapping flow or specific authorization authentication check or specific RRC state or specific access barring check layer) through a network to a specific category. The information can be set and instructed to the terminal.

For example, for a specific terminal group, an operator may designate a specific category. A specific category can be designated for a terminal designated as AC 11-15, an operator test terminal, or the like. For another example, the operator can specify a specific category for a specific service type. Specific categories can be specified for emergency calls, high priority access, and public safety services/applications. As another example, the operator may designate a specific category based on specific subscription information. The core network entity may receive specific subscription information from the subscriber information server during the terminal's network registration process. The terminal may provide specific indication information to the terminal based on specific subscription information from the core network entity. The operator may designate a specific category for the terminal receiving the specific indication information. When the terminal is configured with the specific indication information, the NAS of the terminal may indicate the indication information (access category) as a lower layer (RRC) for network access. When receiving the corresponding indication information, the AS of the terminal may perform an access barring check according to the corresponding access category according to the system information. As another example, the NAS of the terminal may receive an access barring parameter corresponding to the corresponding access category from the lower layer (RRC). In addition, an access barring check may be performed on network access of the corresponding access category.

As another example, a specific category may be designated based on specific indication information configured in the terminal. The terminal may be configured to provide a specific function. For example, the terminal may be configured to provide a specific function to the USIM. The operator may designate a specific category for the terminal that has received the specific indication information. When the terminal is configured with the specific indication information, the NAS of the terminal may indicate the indication information to the lower layer (RRC) for network access. When the AS of the terminal receives the indication, the access baring check may be performed according to a specific category according to the indication according to the system information. As another example, the NAS of the terminal may receive an access barring parameter corresponding to the corresponding access category from the lower layer (RRC). In addition, an access barring check for network access of the corresponding access category may be performed.

As another example, an application identifier may be defined by dividing it into an identifier portion that identifies an operator and an identifier portion that identifies a corresponding application in the operator. For another example, the application identifier may be specified by specifying a range/group of identifiers that can be designated by an operator in the terminal, thereby identifying and distinguishing the application.

The NAS of the terminal may indicate the application identification information to a lower layer (RRC) for network access. When the AS of the terminal receives the corresponding application information, it may select a specific access category according to the application information according to the system information, and perform an access barring check according to the selected access category. As another example, the NAS of the terminal may receive an access barring parameter corresponding to the corresponding access category from the lower layer (RRC). In addition, an access barring check may be performed on network access of the corresponding access category. As another example, the application layer of the terminal may receive an access barring parameter corresponding to the corresponding access category from the lower layer (RRC). In addition, an access barring check may be performed on network access of the corresponding access category.

As another example, the NAS layer can pass the integrated access control category to the AS. The category for integrated access control can be defined by the operator. For example, a category for integrated access control may be mapped and set through any terminal type, service type, subscription type, or a combination thereof.

In the RRC layer, integrated access control may be performed based on the integrated access control category information provided by the NAS. The RRC may perform access barring according to access barring parameters for each access category broadcast through system information. As another example, the NAS of the terminal may receive an access barring parameter corresponding to the corresponding access category from the lower layer (RRC). In addition, an access barring check may be performed on network access of the corresponding access category.

Operators must be able to map and configure specific applications or specific services into categories that can be controlled by access.

Barring control information for integrated access control may be provided through a network. For example, barring control information may be provided through system information. Barring control information can be provided through Minimum SI. As another example, when requesting additional system information based on minimum SI, the request for additional system information may be rejected by the base station.

As another example, specific access categories may be provided through minimum SI. As another example, other specific categories may be provided through other SI.

Core network entity is a specific terminal (or specific application or specific service or specific procedure or specific subscription information or specific QoS class mapping flow or specific DRB mapping information or specific authorization authentication check or specific RRC state or specific access barring check layer) in a specific category. It can be specified and delivered to the terminal and/or the base station.

If the NAS layer indicates the unified access category information and the unified access barring information is broadcast in the cell, the RRC of the terminal applies the unified access barring check operation. Otherwise, when the terminal attempts to start a specific service such as an emergency service, a barring check operation due to the start of the corresponding service may not be performed. Information for this may be provided through system information or may be stored in advance and configured in the terminal.

Otherwise, the RRC of the terminal performs access barring according to the default access category classification.

For another example, an access category for a specific terminal may be defined by subscription information, and this may be indicated to the terminal through signaling between the core network and the terminal in the PDU session establishment.

For another example, an access category for a specific application/service may be defined by subscription information, and this may be indicated to the terminal through signaling between the core network and the terminal in the PDU session establishment. The NAS layer of the terminal receiving this can inform the AS.

In the case of the initial connection, it is possible to perform the default access control if it is not for a specific purpose.

For example, the default access control may be performed based on the access class of the USIM to perform an access barring check according to the access barring configuration when it is not a specific access category.

For another example, the default access control is configurable by the network, and the network can direct it to the terminal through system information.

For another example, the core network entity may transmit authorization information on whether it has authority corresponding to a specific access category (received from the subscriber information server) to the base station. This may be performed on the terminal's network initial access. Thereafter, the terminal may skip access barring for a specific access category. If the terminal does not authenticate the access barring for a specific access category, it is possible to perform access barring according to the default access category. The base station does not perform an access barring check on the network access of the terminal in the state of recognizing the corresponding authorization, and when accessing it, can distinguish it and reject the RRC connection request. Alternatively, the base station may authenticate to bypass the access barring for the terminal that has received the corresponding authorization.

The terminal may be designated as a plurality of access categories according to network instructions. Alternatively, the terminal may be designated as a plurality of access categories according to a pre-configuration. When a terminal designated as a plurality of access categories wants to perform a network connection, the terminal may perform access barring through one or more of the following methods.

For example, an access barring check of a high priority access category among a plurality of access categories may be performed.

For another example, access barring checks of a plurality of access categories may be sequentially performed according to a priority among the plurality of access categories. As an example, when access barring is performed by performing an access barring check of a low priority access category, an access barring check of a next low priority access category may be performed. At this time, the access barring check may be performed after the barring timer due to the barring parameter ends. Alternatively, the access barring check can be performed regardless of the timer operation.

As another example, when the access is barred by performing the access barring check of the high priority access category, the access barring check of the next high priority access category may be performed. At this time, the access barring check may be performed after the barring timer due to the barring parameter ends. Alternatively, the access barring check can be performed regardless of the timer operation. Alternatively, it may indicate to the NAS layer and the NAS may indicate a higher priority access category to the AS.

As another example, it is possible to perform only access barring check of a low priority access category among a plurality of access categories.

For another example, only the access barring check of one access category in a predetermined order among a plurality of access categories may be performed. For example, the access barring check can be performed in the order according to the rule number of the mapping table.

As another example, the base station may indicate priority. This may be indicated by including in system information or RRC connection release message. For example, when a terminal is initiated by a specific service such as an emergency service, an access barring check may be skipped. For this category, information may be provided through system information. Alternatively, the category information may be pre-configured. For another example, for this category, the base station needs to receive authentication information from the core network entity so that the base station recognizes the confirmation. For another example, for this category, it is necessary to bypass the access barring check only when the terminal receives authentication information from the core network entity and the terminal is authenticated thereto. As another example, if the terminal is configured to use a specific AC (for example, AC 11-15), the terminal responds to paging, one or more of cases of RRC connection establishment by an emergency call, or any configured by the operator In some cases, the terminal may perform access without performing a specific access barring check. For example, a terminal configured to use a specific AC (for example, AC 11-15) in a selected PLMN may allow the terminal to perform access without performing a specific access barring check.

For another example, for a terminal included in a specific access category in the differential permission category group, it is possible to prevent the cell from starting to establish an RRC connection until the cell system information for the access category is received. The base station or core network entity may indicate a corresponding access category to the terminal. The base station or the core network entity may instruct the terminal to indicate information for not initiating RRC connection establishment in the cell until the cell information of the cell is received in the corresponding access category.

For another example, for a terminal included in a specific access category, it is possible to prevent the cell from initiating an RRC connection establishment until cell information of the cell is received for the corresponding access category. The base station or core network entity may indicate a corresponding access category to the terminal. The base station or the core network entity may instruct the terminal to indicate information for not initiating RRC connection establishment in the cell until the cell information of the cell is received in the corresponding access category.

As another example, when a terminal attempts to access a network due to an access category having a higher priority than a category in which access to the terminal is prohibited in a state in which access is prohibited according to the access barring check, the terminal checks access barring according to the access category. You can do

As another example, when a terminal attempts to access a network due to an access category having a lower priority than a category in which access to the terminal is prohibited while the terminal is prohibited from accessing according to the access barring check, the terminal is also prohibited from accessing the corresponding access category. Can be considered as

As another example, when a network connection is attempted due to an access category having a lower priority than a category in which access to the terminal is prohibited while the terminal is prohibited from accessing according to the access barring check, the terminal may access due to access to the access category. You can start or restart the access barring timer.

For RRC CONNECTED state terminal, fundamentally performing access barring can have a negative effect on user quality. Therefore, it may be desirable to release the RRC connection or adjust the load through scheduling. However, when RRC connection release signaling is also difficult, access barring through system information may inevitably be performed.

In this case, the base station is configured to provide access prohibition classified according to a specific application or specific service or specific procedure (specific PDU session) or specific subscription information or specific QoS class mapping flow or specific wireless bearer or specific QoS flow/wireless bearer combination. The indication information can be broadcast.

If there is information indicating access barring for a specific application or specific service or specific PDU session or specific terminal configuration or specific QoS flow or specific wireless bearer or specific QoS flow/wireless bearer combination in the RRC CONNECTED state, the terminal may Set as a barring parameter. And as an example, the RRC of the terminal delivers it to a higher layer initiating the application or service. The upper layer performs an access barring check operation.

As another example, when a specific PDU session is initiated for an RRC CONNECTED state terminal or when signaling for processing data corresponding to a specific QoS flow is detected, the NAS may transmit information for indicating this (with an access category) to the AS. . The AS performs an access barring check operation for this.

As another example, the RRC of the UE transmits it to the Layer 2 entity that processes radio bearer data mapped to a specific UE configuration or a specific QoS flow in the RRC CONNECTED state. Such an entity may be a PDCP entity or an entity (PDAP entity) that processes QoS on top of the PDCP. The layer 2 entity performs the corresponding access barring check operation. When access is prohibited, the uplink transmission procedure through the corresponding cell is not initiated. That is, the uplink transmission procedure is suspended or suspended. And the SDAP entity transmits information about it to the RRC.

As another example, in a RRC CONNECTED state, a layer 2 entity (PDCP entity or SDAP entity) that processes radio bearer data mapped to a specific UE configuration or a specific QoS flow receives data corresponding to a specific PDU session or a specific QoS flow of the UE. When signaling for processing or specific QoS flow or specific DRB is detected, the layer 2 entity may transmit the data to the RRC of the UE to check access barring. Alternatively, an access barring check may be performed by receiving a parameter for an AS check through the RRC at this layer 2 entity.

Barring configuration information indicated by the base station to the terminal may configure one or more information of a barring category, a barring layer, and a barring parameter.

As another example, the barring configuration indicated by the network to the terminal may configure one or more information of a barring category, a barring layer, and barring parameters. In addition, the Barring ID can be indicated.

For example, one or more of a barring target, a barring layer, and a barring parameter may be configured through a barring id.

6 is a diagram illustrating an example of a configuration of access access prohibition parameters for each access category according to an embodiment.

Referring to FIG. 6, one or more of the following parameters may be selectively used.

uab-category: indicates information for indicating an access category of a terminal to which access barring is applied.

uab-BarringBitmap: Information indicating access barring included in the corresponding baring configuration information (or baring configuration information having the corresponding baring configuration information identifier). The first/leftmost bit is the first value or terminal of a specific AC (Access Category) It is for the first value among the configured values, and the second bit is for the second value among the specific AC or the value configured for the terminal.

uab-Barringfactor: indicates a barring factor for access check included in the corresponding baring configuration information (or baring configuration information having a corresponding baring configuration information identifier).

uab-BarringTime: represents the time to be barred when barred in the access check included in the corresponding barring configuration information (or baring configuration information having the corresponding barring configuration information identifier).

Barring ID: Indicates identification information for distinguishing the corresponding barring configuration information.

uab-priority: Indicates priority class or priority indication information for access barring processing.

Through this, the baring configuration information mapped for a specific category can be classified through the baring ID.

In NR, it is possible to support reflective QoS through RAN under the control of the network. When the network determines the QoS to be applied to the DL traffic, the terminal reflects the DL QoS to the associated UL traffic (reflect). When the UE receives a DL packet to which reflective QoS is applied, the UE creates a new QoS rule. The packet filter in the derived QoS rule is derived from the DL packet (the header of the packet).

In NR, a default QoS rule is provided to the terminal for PDU session establishment. A pre-authenticated QoS rule may be provided to the terminal for PDU session establishment. The NAS level QoS profile of the QoS rule may be delivered to the RAN through NG2 signaling to the wireless network in PDU session establishment. The QoS rules consist of NAS level QoS profile, packet filter, precedence order, 5QI (5G QoS Identifier or QoS floow ID). The QoS rule may further include QoS flow ID, application identifier, information for distinguishing a specific application/service/flow, and one or more of 5QI.

QoS rules signaled to a terminal connected through NG RAN based on 3GPP access are provided through NG1 signaling.

It is possible to classify applications/services in connection with the aforementioned QoS rules (or QoS indication information or QoS-related application/service identification information, hereinafter referred to as QoS rules for convenience) or QoS. For example, a QoS aware application may indicate the requested QoS using DSCP marking. It is possible to classify applications/services linked to QoS using packet filters including DSCP marking.

This may use a default QoS rule provided to the terminal for PDU session establishment, or may be a pre-authenticated QoS rule provided to the terminal for PDU session establishment. Alternatively, this may be a pre-configured QoS rule in the terminal, or may be provided to the terminal USIM through OTA. Alternatively, the default QoS rule provided to the terminal in the previous PDU session establishment may be used, or it may be a pre-authenticated QoS rule provided to the terminal in the previous PDU session establishment.

The terminal may classify the access category information of the corresponding application/service/traffic/flow based on QoS information (eg, marking information, QoS flow information, etc.) indicated from the base station or received from the base station. The terminal may perform access barring according to the corresponding access category for network access from the access category of the corresponding application/service/traffic/flow.

For example, based on QoS information (for example, marking information, QoS flow information, etc.), the application/service/traffic/flow access category information corresponding to the classification is a PDCP entity or an entity that processes QoS on the PDCP (PDAP entity) ). As another example, classification of access category information of an application/service/traffic/flow corresponding to the QoS information (eg, marking information, QoS flow information, etc.) may be applied to the RRC connection state terminal. As another example, based on QoS information (for example, marking information, QoS flow information, etc.), the corresponding application/service/traffic/flow access category information is classified into the RRC IDLE state or the RRC INACTIVE terminal is the previous terminal contact or transfer. It may be applied when performing access barring through terminal connection information.

As described above, the terminal can perform an access barring check operation through an integrated access control operation, and has an effect of efficiently performing an RRC connection connection even in an environment in which NR requirements are reflected.

Hereinafter, an access control operation considering a terminal that is not sensitive to delay or a service that is not sensitive to delay will be described in detail in the integrated access control operation. That is, a terminal that is not sensitive to delay described below may mean a delay-resistant terminal, and a service that is not sensitive to delay may mean a delay-resistant service.

Delay tolerant UE

In the conventional LTE technology, some terminals have a characteristic that is not sensitive to delay (time tolerant or delay tolerant). For example, some MTC terminals may perform data communication that is not sensitive to delay. In conventional LTE technology, access control for a terminal that is not sensitive to delay has been provided in several ways as follows.

The first is to use the RRC connection rejection procedure. When the terminal transmits an RRC connection request/resume message with delay tolerant access as a setting cause, the base station may transmit an RRC connection rejection message to the terminal. Through this, the terminal informs the upper layer of the failure of the access control for the RRC connection establishment request.

Second, to define a terminal capability capable of extended barring among terminals sensitive to delay, an extended access barring (EAB) is used based on system information for a corresponding terminal. The UE must maintain the latest EAB-related system information in RRC IDLE and perform EAB check in RRC connection setup.

For example, the UE shall not initiate the RRC connection establishment/resume procedure subject to EAB until the UE has a valid version until the UE has a valid version of SystemInformationBlockType14. of SystemInformationBlockType14).

If the UE EAB is enabled, when the UE does not store a valid version of SystemInformationBlockType14 when the UE enters RRC_IDLE, when the UE acquires SystemInformationBlockType1 according to the EAB parameter change notification, when entering the cell during RRC_IDLE, RRC connection When eDRX is used with a DRX cycle longer than the modification cycle before setting, and the schedulingInfoList indicates that SystemInformationBlockType14 exists, the UE immediately starts acquiring SystemInformationBlockType14. Alternatively, if the schedulingInfoList does not indicate that SystemInformationBlockType14 is present, the UE deletes SystemInformationBlockType14 if previously received. (1> if the UE is EAB capable:

2> when the UE does not have stored a valid version of SystemInformationBlockType14 upon entering RRC_IDLE, or when the UE acquires SystemInformationBlockType1 following EAB parameters change notification, or upon entering a cell during RRC_IDLE, or before establishing an RRC connection if using eDRX with DRX cycle longer than the modification period:

3> if schedulingInfoList indicates that SystemInformationBlockType14 is present:

4> start acquiring SystemInformationBlockType14 immediately;

3> else:

4> discard SystemInformationBlockType14 , if previously received;

)

Meanwhile, terminals that are not sensitive to delay may exist in various types. In this case, even if the terminals are in a category having characteristics that are sensitive to delay in common, the operator may wish to perform different access control/prohibition in consideration of other characteristics, but specific integrated access control/prohibition in consideration of various use cases and characteristics No method was provided.

In this situation, it is intended to provide a method and apparatus for providing integrated access control for a terminal that is not sensitive to delay in consideration of various usage examples and scenarios of the terminal.

Hereinafter, an access control method and apparatus for a terminal configured as a delay tolerant UE through integrated access control will be described, but this may also be applied to a general terminal capable of providing a corresponding function. The embodiments provided below may be implemented individually or in combination/combination of each. In addition, the present invention can be applied to any mobile communication/fixed communication/wireless communication network including LTE as well as the next generation mobile communication (5G mobile communication) network. The present invention may be provided in a 5G network provided through an NR base station (gNB). Alternatively, the present invention may be provided in an LTE network provided through an LTE base station (eNB). Alternatively, the present invention may be provided in an eLTE network provided through an eLTE base station (eg, ng-eNB) connected to a 5G core network. Alternatively, the present invention can be applied to a terminal accessing a 5G core network using NR and a terminal accessing a 5G core network using E-UTRA. In addition, a service that is not sensitive to delay and a service that has low sensitivity to delay is used in the same sense as the delay immunity service described above, and the term may be changed as necessary.

Hereinafter, for convenience of description, the following description based on a terminal configured for a delay-insensitive service may be applied to a terminal configured with arbitrary configuration information. When a terminal has a configuration with a configuration and a configuration with an access identifier, the same can be applied to a case where a configuration is specified and used as an access category.

The following methods may be used individually or in combination for a terminal configured to provide a service that is not sensitive to delay.

First, a method of configuring a terminal for a service that is not sensitive to delay will be described.

A terminal for a service that is not sensitive to delay may be processed with a lower priority than a general terminal when processing NAS (Non-Access Stratum) signaling. To this end, among device information elements included in the NAS message, device property IEs capable of processing NAS signaling with a low priority are defined, and when an overload occurs in the network, the device property information indicates that the terminal has low NAS signaling priority. When a low priority indicator set to be configured as a priority is included, NAS signaling can be preferentially rejected. The NAS signaling low priority may be assigned/configured/set for each device. For example, a specific terminal may be configured/set with a low priority, and other specific terminals may not have a corresponding priority.

A terminal for a service that is not sensitive to delay may provide an extended access barring function. This defines extended access barring (e.g. EAB) device property information that is distinguished from device properties IEs that can handle NAS signaling with low priority among the information elements included in the above-described NAS message. And, when an overload occurs in the network, when the information for instructing access barring for the EAB capable terminal is broadcast through the system information, the corresponding terminal performs an EAB check. EAB device attribute information may also be assigned/configured/set for each device.

The terminal may be configured to provide a service that is not sensitive to delay. For example, the terminal may be configured with configuration information for providing low priority NAS signaling.

As another example, even a terminal configured to provide the aforementioned low-priority NAS signaling does not have a low priority (or is not a low-priority or high-priority or low-priority, but is not a low-priority for convenience below). The case is expressed as a normal priority, but it may indicate an arbitrary priority rather than a low priority.) It may be configured with configuration information to enable dual priority NAS signaling to enable NAS signaling.

As another example, the terminal may be configured with configuration information for providing access barring (similar to the aforementioned extended access barring).

As another example, the terminal may be configured with respective configuration information to support the aforementioned functions.

As another example, the terminal may be configured with one piece of configuration information for a service that is not sensitive to delay, thereby providing one or more functions described above.

For convenience of description, hereinafter, configuration information for a service that is not sensitive to delay may indicate one or more configuration information described above.

The terminal may be configured for a service that is not sensitive to delay.

For example, when a terminal performs one or more procedures of a registration procedure/attach procedure, a PDU session establishment, a tracking area update, and a service request procedure, a network (for example, a core network entity, a core network control plane entity, AMF) ) May indicate that the terminal is configured for a service that is not sensitive to delay (based on subscription information). The terminal may configure/store/set the corresponding indication information in the terminal context/NAS context/NAS device attribute information/device attribute information in the terminal.

As another example, detailed information of a terminal configured for a service that is not sensitive to delay may be configured. When the terminal performs one or more procedures of a registration procedure (Registration procedure/attach procedure), PDU session establishment, tracking area update, service request procedure, a network (for example, a core network entity, a core network control plane entity, AMF) is (Based on the subscription information) It can be instructed to configure the terminal with the corresponding details. The terminal may configure/store/set the corresponding detailed indication information in the terminal context/NAS context/NAS device attribute information/device attribute information in the terminal.

As another example, the terminal may be configured/stored/set in a specific access category for a service that is not sensitive to delay on the USIM.

As another example, the terminal may be configured/stored/set the indication information for configuring for a service that is not sensitive to delay on the USIM. As another example, the terminal may be configured/stored/set the detailed information of the terminal configured for a service that is not sensitive to delay on the USIM.

A method of performing access control/prohibition processing using baring configuration information linked to the instruction information according to the instruction information provided by the NAS.

Different criteria such as operator policies, deployment scenarios, subscriber profiles, and available services are used to determine whether access attempts are allowed or blocked when congestion occurs within the 5G system. These different criteria for access control can be linked to the indication information provided by the NAS.

The 5G system can provide one single integrated access control that the operator controls access based on the indication information provided by these NAS.

Configuration information for a service that is not sensitive to delay may be configured in the terminal. The network may broadcast baring configuration information (baring parameter list and baring parameter list according to detailed information) for access barring of a terminal configured for a service that is not sensitive to delay through system information. The terminal may determine whether to allow a specific access based on the barrage parameters received from the broadcast barring configuration information, the configuration of the terminal, and the indication information provided by the NAS.

For example, the AS (for example, RRC) of the terminal receives the barrage parameter received from the broadcast barring configuration information about whether a specific access attempt is allowed and the upper layer (for example, NAS: Non Access Stratum) of the terminal. Decision can be made based on one indication.

For example, the instruction information received from the above-described NAS may be access category number information. The access category number indicates a number determined according to the type of access attempt and conditions related to the terminal. When an RRC IDLE terminal establishes an RRC connection by an instruction of an upper layer, or an RRC INACTIVE terminal is configured by an originating signaling of an upper layer (e.g. NAS) or an originating data (MO data) of an upper layer (e.g. IP layer). When establishing an RRC connection, or when an RRC CONNECTED terminal attempts a new access (for example, establishing a new PDU session, modifying an existing PDU session, requesting a service to request a user plane reset for an existing PDU session, a new MMTEL voice or video session , SMS transmission), integrated access control may be applied. In this integrated access control, the NAS directs one access category determined according to the type of access attempt and conditions related to the terminal to the AS of the terminal.

As another example, the indication information received from the above-described NAS may be additional indication information distinguished from the access category number.

The NAS configured for a service that is not sensitive to delay (hereinafter referred to as a terminal configured for configuration information for a service that is not sensitive to delay) sets the RRC connection by an instruction of a higher layer in the RRC IDLE state, or RRC When establishing an RRC connection by originating signaling from the upper layer (e.g., NAS) or MO layer (e.g., IP layer) originating data in the INACTIVE state, or when a new access attempt is initiated in the RRC CONNECTED state. One access category determined according to the type of access attempt and the conditions related to the terminal is indicated to the AS of the terminal. Or, it indicates additional information distinguished from the access category number.

For example, a terminal configured for a delay-sensitive service may indicate specific access category information defined for this in the NAS to the AS.

As another example, if a terminal configured for a delay-sensitive service is an emergency access attempt (for example, emergency bearer service, emergency call, emergency session, emergency flow, emergency PDU session, etc.), the NAS is a specific access category defined for emergency. Information can be directed to the AS.

As another example, a terminal configured for a delay-sensitive service may indicate specific access category information defined for a terminal configured for a delay-sensitive service to the AS, except for an emergency access attempt from the NAS.

As another example, even a terminal configured for a delay-sensitive service attempts to access a standardized specific access (for example, MO signaling with normal priority, MO data with normal priority, MMTEL voice/video, access attempt by one of SMS, etc.) If it is due to, the NAS may direct specific access category information defined for the corresponding standardized specific access attempt to the AS.

As another example, even if a terminal is configured for a delay-sensitive service, specific priority attempts for normal priority/dual priority/standardized access through detailed configuration information for a delay-sensitive service. (E.g., MO signaling with normal priority, MO data with normal priority, MMTEL voice/video, access attempt by one of SMS, etc.), the NAS is defined for the corresponding standardized specific access attempt Specific access category information can be directed to the AS.

The AS of the terminal performs a barring check according to the barring configuration information broadcast by the base station for the access category using the access category information received from the NAS. For example, even a terminal configured for a delay-sensitive service (depending on the detailed configuration) allows the NAS to classify the access category and indicate it to the AS, and the AS of the terminal can perform a barring check according to the corresponding access category. If the terminal configured for the delay-sensitive service also indicates that the NAS indicates the MO data access category (for example, access category 7) to the AS, the AS can perform a barring check according to the barring configuration information associated with the MO data access category. . If the NAS of the terminal configured for the delay-sensitive service indicates an access category (for example, access category 2) for the terminal configured for the delay-sensitive service to the AS, the AS data for the terminal configured for the delay-sensitive service. A baring check may be performed according to the baring configuration information associated with the access category. If the NAS of a terminal configured for a delay-sensitive service instructs an access category and additional indication information for a terminal for a delay-sensitive service to the AS, the AS attaches to the additional indication information for the terminal configured for the delay-sensitive service. A baring check may be performed according to the associated baring configuration information.

Broadcasting of access category-based baring configuration information by a base station and operation of a terminal based on the same can be used with reference to the contents of other embodiments described below.

A method of configuring a terminal configured for a service that is not sensitive to delay as a specific access identifier/access identity and performing an access control/prohibition operation based on this.

Different criteria such as operator policies, deployment scenarios, subscriber profiles, and available services are used to determine whether access attempts are allowed or blocked when congestion occurs within the 5G system. These different criteria for access control can be handled in association with an access identifier that is configured/set/set in the terminal. The 5G system uses access identifiers together to provide a single unified access control where the operator controls access.

Configuration information for a service that is not sensitive to delay may be configured in the terminal. The network may broadcast baring configuration information (baring parameter list and baring parameter list according to detailed information) for access barring of a terminal configured for a service that is not sensitive to delay through system information. The terminal may determine whether to allow a specific access based on a barrage parameter received from the broadcast barring configuration information and the configuration of the terminal.

The AS of the terminal may be determined based on one or more information of a barrage parameter received from the baring configuration information broadcast, whether to allow a specific access attempt, a configuration of the terminal, and an access category received from the AS of the terminal.

For example, configuration information for a service that is not sensitive to delay may be an access identifier/determinant that is information configured in a terminal for access control/prohibition. Configuration information for a service that is not sensitive to delay used as an access identifier to a terminal for a service that is not sensitive to delay may be configured in the terminal as described above.

First, a description will be given of a method of performing a barring check by classifying a terminal for a service that is not sensitive to delay into an access identifier rather than a specific access category.

The configured terminal for a service that is not sensitive to delay may be configured in the terminal with a specific access identifier. For example, the terminal may be configured with an access identifier for providing low priority NAS signaling.

As another example, even a terminal configured to provide the low-priority NAS signaling described above may be configured with access identifier information that enables dual-priority NAS signaling to enable NAS signaling without low priority (or normal priority). have.

As another example, the terminal may be configured with access identifier information for providing access barring (similar to the aforementioned extended access barring).

As another example, the terminal may be configured with each access identifier information to support the aforementioned functions.

As another example, the terminal may be configured with one access identifier information for a service that is not sensitive to delay, thereby providing one or more functions described above.

When an RRC IDLE terminal establishes an RRC connection by an instruction of an upper layer, or an RRC INACTIVE terminal is configured by an originating signaling of an upper layer (e.g. NAS) or an originating data (MO data) of an upper layer (e.g. IP layer). When establishing an RRC connection, or when an RRC CONNECTED terminal attempts a new access (for example, establishing a new PDU session, modifying an existing PDU session, requesting a service to request a user plane reset for an existing PDU session, a new MMTEL voice or video session , SMS transmission), integrated access control may be applied. In this integrated access control, the NAS directs one access category determined according to the type of access attempt and conditions related to the terminal to the AS of the terminal.

The NAS of a terminal configured with a specific access identifier for a service that is not sensitive to delay, when establishing an RRC connection by an instruction of a higher layer in an RRC IDLE state, or an outgoing signaling of an upper layer (for example, NAS) in an RRC INACTIVE state, or When the RRC connection is established by the upper layer (for example, the IP layer) originating data (MO data), or when initiating a new access attempt in the RRC CONNECTED state, one access determined according to the type of access attempt and conditions related to the terminal The category is indicated to the AS of the terminal. Or, it indicates additional information distinguished from the access category number.

For example, the NAS of a terminal configured with a specific access identifier for a delay-sensitive service is a standardized specific access attempt (for example, MO signaling resulting from paging, emergency, non-paging MO signaling, MMTEL voice/video, SMS, MO data It may indicate to the AS specific access category information classified/defined according to the access attempt by one).

As another example, the NAS of a terminal configured with a specific access identifier for a delay-sensitive service may indicate an access identifier (or corresponding configuration information) configured for a delay-sensitive service to the AS.

The AS of the terminal performs a barring check according to the access category information received from the NAS, the access identifier information configured in the terminal (or access identifier information received from the NAS) and the baring configuration information broadcast by the base station. The baring configuration information broadcast by the base station may include access barring configuration information for each access category and access barring configuration information for each access identifier.

For example, for a terminal configured with a specific access identifier for a service sensitive to delay, when the terminal receives the barring configuration information for the corresponding access identifier broadcast from the base station, the barring configuration information for the access identifier for a new access attempt Baring check through. If it is determined that a baring is performed by performing a baring check, the cell is considered to be bared. Otherwise, the cell is considered unbarred.

For another example, for a terminal configured with a specific access identifier for a delay-sensitive service, when the terminal receives the barring configuration information for the corresponding access identifier broadcast from the base station, the barring configuration information for the access identifier for a new access attempt Baring check through. If it is determined that a baring is performed by performing a baring check, the cell is considered to be bared. Otherwise, a barring check is performed through the barring configuration information for the access category received from the NAS for the access attempt. If it is determined that a baring is performed by performing a baring check, the cell is considered to be bared. Otherwise, the cell is considered unbarred.

For another example, for a terminal configured with a specific access identifier for a service sensitive to delay, when the terminal receives the barring configuration information for the corresponding access identifier broadcast from the base station, the barring configuration by the corresponding access category for a new access attempt Baring check is performed through the baring configuration information for the corresponding access identifier without checking the baring through the information.

For another example, for a terminal configured with a specific access identifier for a service sensitive to delay, when the terminal receives the barring configuration information for the corresponding access identifier broadcast from the base station, the barring configuration by the corresponding access category for a new access attempt Considering the information together, a baring check is performed.

For another example, a NAS of a terminal configured with a specific access identifier for a delay-sensitive service attempts to access a specific high priority (for example, attempts to access one or more of emergency, non-paging MO signaling, MMTEL voice/video, SMS) When the specific access category information classified/defined according to is indicated to the AS, the AS of the terminal may perform a barring check based on the access barring configuration information for the corresponding access category for a new access attempt. For example, when the access barring configuration information for the emergency communication access category indicates to skip/access attempt to skip the barring check, the access barring check to skip/access attempt may be allowed. Alternatively, a baring check is performed according to access barring configuration information broadcast by the base station for the MMTEL voice access category.

For another example, a NAS of a terminal configured with a specific access identifier for a delay-sensitive service is classified/defined according to a specific medium priority access attempt (for example, MO signaling rather than paging, access attempt of one or more of MO data) When indicating specific access category information to the AS, the AS of the terminal may perform a barring check based on access barring configuration information for the corresponding access category for a new access attempt. For example, the AS of the terminal may perform a barring check using access barring configuration information for a corresponding access category.

For another example, a NAS of a terminal configured with a specific access identifier for a delay-sensitive service is classified/defined according to a specific medium priority access attempt (for example, MO signaling rather than paging, access attempt of one or more of MO data) When indicating specific access category information to the AS, the AS of the terminal may perform a barring check based on access barring configuration information for the access identifier configured in the terminal for a new access attempt. For example, the AS of the terminal may override/reject/skip the barring check through the access barring configuration information for the access category by performing a barring check using the access barring configuration information for the access identifier.

For another example, standardized access category information (e.g., MO signaling, emergency, and paging caused by paging) defined/defined by the NAS of a terminal configured with a specific access identifier for delay-sensitive service is standardized access attempts. When not indicating MO signaling, MMTEL voice/video, SMS, and each access category according to an access attempt by one of the MO data) to the AS, the AS of the terminal accesses the access identifier configured in the terminal for the new access attempt. A baring check can be performed based on the baring configuration information.

The access barring configuration information for the access identifier broadcast by the base station is classified into standard access categories (MO signaling, emergency, non-paging MO signaling, MMTEL voice/video, SMS, MO data) for which the corresponding access identifier is configured. Baring bitmap configuration information may be included. The corresponding bit is information for indicating whether a terminal having an access identifier (configuration information) configured for a service that is not sensitive to delay applies barring to an access attempt (to an access category received from NAS) of the corresponding access category. Can represent. Or, the corresponding bit allows a terminal with an access identifier (configuration information) configured for a service that is not sensitive to delay to allow/access control (barring) access attempts (to access categories received from NAS) of the corresponding access category. Allow access attempts/Allow access attempts/Override access barring/Access control skip/Instruct access control/barring/permit for terminals that can provide services that are not sensitive to delay and other priorities (or services) at the same time Information can be displayed.

When the terminal is configured with arbitrary configuration information (or access identifier), the base station broadcasting the configuration information for the corresponding configuration information (or access identifier) is standardized by the terminal configured with the corresponding configuration information (or access identifier). Barring bitmap configuration information for one or more categories among the access categories may be included. With the corresponding configuration information (or access identifier), the configuration terminal can perform a barring check using the barring configuration information associated with the configuration information (or access identifier) that is distinct from the barring configuration information associated with the access category.

If the terminal has more than one access identifier (configuration information), access barring configuration information associated with an access identifier having a specific order (eg, highest priority, order indicated by the base station, pre-configured order, etc.) Accordingly, it is possible to perform a barring check.

If a terminal for a service that is not sensitive to delay is classified into a specific access category, and the NAS indicates it to the AS, it can be processed as follows.

For example, for a delay-sensitive service, a NAS of a terminal configured with a specific access identifier attempts to access a specific high-priority access (e.g., emergency, non-paging MO signaling, MMTEL voice/video, SMS). When instructing/defining specific access category information according to AS, the AS of the terminal may perform a barring check based on access barring configuration information for a corresponding access category for a new access attempt. For example, the AS of the terminal may allow the access barring check to be skipped or the access attempt to be skipped when the access barring configuration information skips the barring check or permits the access attempt for emergency communication. The AS of the terminal may allow an attempt to skip or skip the barring check through the access barring configuration information for the access identifier.

For another example, a NAS of a terminal configured with a specific access identifier for a delay-sensitive service is classified/defined according to a specific medium priority access attempt (for example, MO signaling rather than paging, access attempt of one or more of MO data) When indicating specific access category information to the AS, the AS of the terminal may perform a barring check based on access barring configuration information for the access identifier configured in the terminal for a new access attempt. For example, the AS of the terminal may override/reject/skip the barring check through the access barring configuration information for the access category by performing a barring check using the access barring configuration information for the access identifier.

For another example, when a NAS of a terminal configured with a specific access identifier for a delay-sensitive service indicates access category information for the terminal to the AS, the AS of the terminal accesses the access identifier configured on the terminal for a new access attempt. A baring check can be performed based on the baring configuration information. For example, the AS of the terminal may override/reject/skip the barring check through the access barring configuration information for the access category by performing a barring check using the access barring configuration information for the access identifier.

For another example, when a NAS of a terminal configured with a specific access identifier for a delay-sensitive service indicates access category information for the terminal to the AS, the AS of the terminal accesses the access identifier configured on the terminal for a new access attempt. Based on the baring configuration information, the baring check and access to the access category may be performed based on the baring configuration information. For example, the AS of the terminal may override/reject/skip the barring check through the access barring configuration information for the access category by performing a barring check using the access barring configuration information for the access identifier.

The network may broadcast baring configuration information (barring parameter list) associated with one access identifier and/or barring configuration information (barring parameter list) associated with one access category through system information. The terminal may determine whether to allow a specific access based on a barrage parameter received from the broadcast barring configuration information and the configuration of the terminal.

The base station broadcasts the baring configuration information through system information.

For example, the barring configuration information including information for indicating whether barring is applied to an access identifier for a terminal configured for a service that is not sensitive to delay is broadcast.

For another example, when a terminal configured for a delay-insensitive service is configured with a specific access identifier, access control/barred access attempt for one access attempt/access attempt allow/override/access control for access barring skip /Balling configuration information including information for instructing to simultaneously provide services that are not sensitive to delay and other priorities (or services) is broadcast.

For example, the barring configuration information for an access category (or any access category) for a terminal configured for a service that is not sensitive to delay may include one or more of the following information.

-1-bit indication information to indicate whether barring is applied to an access identifier configured for a delay-insensitive service

-Access barring factor information (ac-BarringFactor): If the random number drawn by the terminal is smaller than this value, access is allowed. Otherwise, access is barred. (Or, if the random number drawn by the terminal is greater than this value, access is allowed. Otherwise, access is barred.)

-Access barring time information (ac-BarringTime)

-Information for indicating detailed type/classification/category/access identifier information of an access identifier to be applied to a terminal configured for a service that is not sensitive to delay

a) Access identifiers configured for delay-insensitive services (or terminals with all access identifiers configured for delay-insensitive services)

b) Access identifiers configured for services that are not sensitive to delay and not in the HPLMN or equivalent PLMN.

c) is configured for delay-insensitive services and is not in the PLMN listed in the preferred PLMN of the country in which the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM, not in HPLMN or equivalent to HPLMN Access identifiers not in the PLMN (or access identifiers configured for delay-insensitive services and not in the PLMN listed as the preferred PLMN of the country where the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM)

In another example, the barring configuration information for the access identifier (or any access identifier) for indicating the above-described access operation to the terminal configured for the service that is not sensitive to delay may include one or more of the following information. .

-1-bit indication information to indicate whether barring is applied to the corresponding access identifier

-Access barring factor information for the corresponding access identifier (ac-BarringFactor): If the random number drawn by the terminal is smaller than this value, access is permitted. Otherwise, access is barred. (Or, if the random number drawn by the terminal is greater than this value, access is allowed. Otherwise, access is barred.)

-Access barring time information for the corresponding access identifier (ac-BarringTime)

-Information for indicating detailed type/classification/category/access identifier information of the access identifier

a) Access identifiers configured for delay-insensitive services (or terminals with all access identifiers configured for delay-insensitive services)

b) Access identifiers configured for services that are not sensitive to delay and not in the HPLMN or equivalent PLMN.

c) is configured for delay-insensitive services and is not in the PLMN listed in the preferred PLMN of the country in which the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM, not in HPLMN or equivalent to HPLMN Access identifiers not in the PLMN (or access identifiers configured for delay-insensitive services and not in the PLMN listed as the preferred PLMN of the country where the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM)

-Allow access/access control (barring) access attempts for access attempts of terminals with the corresponding access identifiers/allow access attempts/override/access control skip/delay sensitive services and other priorities for access barring (Or service) 1-bit indication information for instructing access control/barring prohibition/allowance for a terminal capable of simultaneously providing

As another example, when access is triggered by a terminal having an access identifier configured for a service that is not sensitive to delay, the AS of the terminal performs a barring check based on the received system information.

For example, if the access identifier of the corresponding terminal has a specific value and a bit indicating barring for the corresponding access identifier included in the system information is set to 1, the terminal considers the cell to be barred. Otherwise, the terminal considers the cell to be unbarred.

For another example, if PLMN-related information is included, the entry is selected in PLMN-related information corresponding to the PLMN selected by the upper layer. If the system information includes information about the PLMN, and if the terminal is triggered by a terminal having an access identifier configured for a delay-insensitive service, the AS of the terminal is baring based on the received system information Perform a check.

For another example, if the access identifier of the corresponding terminal has a specific value and a bit indicating barring for the corresponding access identifier included in the system information is set to 1, the terminal considers the cell to be barred.

As another example, if a terminal configured for a delay-insensitive service has a specific access identifier described above, when access is triggered by the terminal, the AS of the terminal performs a barring check based on the received system information.

For example, if the access identifier of the corresponding terminal has a specific value, the access attempt is allowed/access control (barring) for the access attempt for the access identifier included in the system information. If a bit indicating access control/barring/disallowed is set to 1 for a terminal capable of simultaneously providing override/access control for skip/delay service and other priority (or service) for the terminal, the terminal may select the cell. Consider unbarred. Otherwise, the terminal considers the cell to be unbarred. Or, the terminal performs access control/barring according to the access category of the terminal.

As another example, when PLMN-related information is included, the entry is selected in PLMN-related information corresponding to the PLMN selected by the upper layer. If the system information includes information on the PLMN, and if the terminal is triggered by a terminal having a specific access identifier, the AS of the terminal performs a barring check based on the received system information.

For example, if the access identifier of the corresponding terminal has a specific value, the access attempt is allowed/access control (barring) for the access attempt for the access identifier included in the system information. If a bit indicating access control/barring/disallowed is set to 1 for a terminal capable of simultaneously providing override/access control for skip/delay service and other priority (or service) for the terminal, the terminal may select the cell. Consider unbarred.

As another example, when access is triggered by a terminal having an access identifier configured for a service that is not sensitive to delay, the AS of the terminal performs a barring check based on the received system information.

For example, if the access identifier of the corresponding terminal has a specific value, the access attempt is allowed/access control (barring) for the access attempt for the access identifier included in the system information. If a bit indicating access control/barring/disallowed is set to 1 for a terminal capable of simultaneously providing override/access control for skip/delay service and other priority (or service) for the terminal, the terminal may select the cell. Consider unbarred. Otherwise, the terminal considers the cell as being barred.

A method of performing an access control/prohibition processing operation in association with a specific access category according to the details of a terminal configured for a service that is not sensitive to delay.

Different criteria such as operator policies, deployment scenarios, subscriber profiles, and available services are used to determine whether access attempts are allowed or blocked when congestion occurs within the 5G system. These different criteria for access control can be linked to access categories. Based on this access category, the 5G system can provide one single unified access control for the operator to control access.

First, a method of processing a terminal configured for a service that is not sensitive to delay in connection with a specific access category will be described.

Configuration information for a service that is not sensitive to delay and/or detailed configuration information of a corresponding terminal may be configured in the terminal. The network may broadcast baring configuration information (baring parameter list and baring parameter list according to detailed information) associated with one access category through system information. The terminal may determine whether to allow a specific access based on a barrage parameter received from the broadcast barring configuration information and the configuration of the terminal.

As another example, the above-described detailed configuration information distinguishes standardized specific access attempts (for example, MO signaling resulting from paging, Emergency, MO signaling other than paging, MMTEL voice/video, SMS, and MO access attempts) It can be information to do.

For example, the terminal may be configured for a service that is not sensitive to delay through NAS signaling. When the terminal performs one or more procedures of a registration procedure (Registration procedure/attach procedure), PDU session establishment, tracking area update, and service request procedure, the network (e.g., core network entity, core network control plane entity, AMF) You can instruct the terminal to configure for a service that is not sensitive to delay (based on subscription information). The terminal may configure/store/set the corresponding indication information in the terminal context/NAS context/NAS device attribute information/device attribute information in the terminal.

As another example, the terminal may configure detailed information of a terminal configured for a service that is not sensitive to delay through NAS signaling. When the terminal performs one or more procedures of a registration procedure (Registration procedure/attach procedure), PDU session establishment, tracking area update, service request procedure, a network (for example, a core network entity, a core network control plane entity, AMF) is (Based on the subscription information) It can be instructed to configure the terminal with the corresponding details. The terminal may configure/store/set the corresponding detailed indication information in the terminal context/NAS context/NAS device attribute information/device attribute information in the terminal.

As another example, the terminal may be configured/stored/set in a specific access category for a service that is not sensitive to delay on the USIM.

As another example, the terminal may be configured/stored/set the detailed information of the terminal configured for a service that is not sensitive to delay on the USIM.

The base station broadcasts the baring configuration information through system information.

For example, the barring configuration information including information for indicating whether barring is applied to an access category for a terminal configured for a service that is not sensitive to delay is broadcast.

Barring configuration information for an access category for a terminal configured for a delay-insensitive service (or barring configuration information for a barring when a terminal configured for a delay-insensitive service attempts to access) is one of the following information: The above information may be included.

-1-bit indication information to indicate whether baring is applied to a terminal configured for a delay-insensitive service (or a terminal configured for a delay-insensitive service)

-Access barring factor information (ac-BarringFactor): If the random number drawn by the terminal is smaller than this value, access is allowed. Otherwise, access is barred. (Or, if the random number drawn by the terminal is greater than this value, access is allowed. Otherwise, access is barred.)

-Access barring time information (ac-BarringTime)

-Information for indicating the detailed type/classification/category of the terminal configured for delay-insensitive service (to which access control is applied)

a) Terminals configured for delay-insensitive services (or all terminals configured for delay-insensitive services)

b) Terminal configured for non-delay sensitive services and not in the HPLMN or equivalent PLMN

(UEs that are configured for delay tolerant service and are neither in their HPLMN nor in a PLMN that is equivalent to it)

c) is configured for delay-insensitive services and is not in the PLMN listed in the preferred PLMN of the country in which the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM, not in HPLMN or equivalent to HPLMN UEs that are configured for delay tolerant service and are neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in a PLMN that is equivalent to their HPLMN) (or PLMN configured for the delay-insensitive service and listed as the preferred PLMN of the country where the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM) Terminal not in)

-Instruction information for indicating whether barring is applied to a specific subgroup/class/access class/division/distribution group of a terminal configured for a service that is not sensitive to delay (access control is applied)

As an example, this may indicate whether baring is applied to AC 0-9 as a bitmap. The first/leftmost bit is for AC 0, the second bit is for AC 1, and so on, and the first/leftmost bit represents the value for AC 0 and the second bit represents the value for AC 1. .).

As another example, this may indicate whether baring is applied to a specific group/class/access class/division/distribution group of a terminal configured/stored/set on the USIM as a bitmap. The first/leftmost bit represents the value for the first group/class/access class/division/variance group, and the second bit consists of the expression for the second group/class/access class/division/variance group.

As another example, this is a standardized access attempt (for example, MO signaling resulting from paging, emergency, non-paging MO signaling, MMTEL voice/video, SMS, access attempt by one of MO data) baring bitmap configuration information for each Can be represented.

As another example, when access is triggered by a terminal configured for a delay-insensitive service, the NAS of the terminal accesses the corresponding access category (for example, access category 1: a terminal configured for a delay-insensitive service except an emergency access attempt) The access category applied to the attempt) is transmitted to the AS of the terminal (for example, RRC).

The AS of the terminal performs a barring check based on the received system information (or baring configuration information for the corresponding access category).

For example, if information about a specific subgroup/class/access class/division/distribution group of the terminal is stored on the USIM (or configured/stored on the terminal through NAS signaling) and has a value within a specific range If it is, if the corresponding bit in the bitmap included in the system information is set to 1, the terminal considers the cell as being barred. If the corresponding bit in the bitmap included in the system information is not set to 1, the terminal considers the cell as unbarred.

As another example, when PLMN-related information is included, the entry is selected in PLMN-related information corresponding to the PLMN selected by the upper layer.

If the system information includes information on the PLMN, if the terminal is included in the type/classification/category indicated by the information indicating the detailed type/classification/category of the terminal configured for the delay-insensitive service If, information about a specific group/class/access class/distribution group/division/access identifier of the terminal is stored on the USIM (or configured/stored on the terminal through NAS signaling) and has a value within a specific range If it is, if the corresponding bit in the bitmap included in the system information is set to 1, the terminal considers the cell as being barred. Otherwise, the terminal considers the cell to be unbarred.

7 is a diagram exemplarily showing a mapping table to which an access category is mapped according to an access attempt according to another embodiment.

As shown in FIG. 7, the access category may have a number from 0 to 63. The access category may be classified in consideration of the type of access attempt and the conditions related to the terminal, and may be classified as a standard access category and an access category designated based on operator classification.

For an integrated access control, for example, for an RRC IDLE terminal or an RRC INACTIVE terminal, when the corresponding terminal wants to establish an RRC connection, the NAS of the terminal may provide access category information to the RRC (AS) of the terminal. . The NAS of the terminal (optionally or in combination with this) may provide additional information for determining the cause of RRC connection establishment in addition to the access category information to the RRC of the terminal.

For an integrated access control, for example, for the RRC CONNECTED terminal, when the terminal wants to establish an RRC connection through NAS signaling to establish a new PDU session, the terminal's NAS accesses the terminal's RRC (AS) Category information can be provided. The NAS of the terminal (optionally or together) may provide the RRC of the terminal with additional information for determining the cause of RRC connection establishment in addition to the access category information.

A method of processing a terminal configured for a delay-insensitive service in association with a specific access identity.

Different criteria such as operator policies, deployment scenarios, subscriber profiles, and available services are used to determine whether access attempts are allowed or blocked when congestion occurs within the 5G system. These different criteria for access control can be handled in association with an access identifier that is configured/set/set in the terminal. The 5G system provides a single unified access control that allows the operator to control access based on the access identifier.

Hereinafter, a method of processing a terminal configured for a service that is not sensitive to delay in association with a specific access identifier will be described.

As described above, the access identifier may be configured in the terminal.

For example, an access identifier is not configured with the corresponding access identifier, allowing access attempts to access control/barring on one access attempt/allowing access attempts/override on access barring/access control skip/delay sensitive services and other priorities It may indicate configuration information for instructing to provide ranking (or service) at the same time. Access identifiers allow access attempts to access control/barred access to one access attempt/accept access attempts/override for access barring/access control skip/delay sensitive services and other priorities (or services) Is used to provide/direct the offer at the same time. The access identifier allows access attempts to be controlled/barred by access categories according to one access attempt according to subscription information/allows access attempts/overrides on access barring/access control skip/delay sensitive services and other priorities It is used to provide/direct the provision of rankings (or services) simultaneously.

As another example, the access identifier may indicate information for indicating access control/barring for one access attempt when configured with the corresponding access identifier. The access identifier is used to indicate access control/barring in one access attempt according to subscription information. The access identifier is used to provide access control/barring for the access attempt regardless of the access category according to one access attempt according to the subscription information.

The network may broadcast baring configuration information (baring parameter list) associated with one access identifier through system information. The terminal may determine whether to allow a specific access based on a barrage parameter received from the broadcast barring configuration information and the configuration of the terminal.

For example, the terminal may be configured for a service that is not sensitive to delay through NAS signaling. When the terminal performs one or more procedures of a registration procedure (Registration procedure/attach procedure), PDU session establishment, tracking area update, service request procedure, a network (for example, a core network entity, a core network control plane entity, AMF) is You can instruct the terminal to configure for a service that is not sensitive to delay (based on subscription information). The terminal may configure/store/set the corresponding indication information as an access identifier in the access identifier information/terminal context/NAS context/NAS device attribute information/device attribute information in the terminal.

As another example, the terminal may be configured with an access identifier for a service that is not sensitive to delay through NAS signaling (or the terminal may be configured with a specific access identifier for a service that is not sensitive to delay through NAS signaling. ). When the terminal performs one or more procedures of a registration procedure (Registration procedure/attach procedure), PDU session establishment, tracking area update, and service request procedure, the network (e.g., core network entity, core network control plane entity, AMF) It is possible to instruct the terminal to configure with a specific access identifier for a service that is not sensitive to delay (based on subscription information). The terminal may configure/store/set the corresponding indication information as an access identifier in the access identifier information/terminal context/NAS context/NAS device attribute information/device attribute information in the terminal.

As another example, the terminal allows/accesses an access attempt (barring) for one access attempt to the terminal for a service that is not sensitive to delay through NAS signaling/allows access/override/access control for access barring skip / Can be configured with an access identifier to provide a service that is not sensitive to delay and other priorities (or services) at the same time. Alternatively, the terminal may be configured with a specific access identifier that can override it even for a terminal that is not sensitive to delay through NAS signaling. When the terminal performs one or more procedures of a registration procedure (Registration procedure/attach procedure), PDU session establishment, tracking area update, and service request procedure, the network (e.g., core network entity, core network control plane entity, AMF) It is possible to instruct the terminal to configure with the corresponding access identifier (based on the subscription information). The terminal may configure/store/set the corresponding indication information as an access identifier in the access identifier information/terminal context/NAS context/NAS device attribute information/device attribute information in the terminal.

As another example, the terminal may be configured/stored/set with a specific value in access identifier information for a service that is not sensitive to delay on the USIM.

As another example, the terminal may be configured/stored/set with a specific value in the access identifier information corresponding to the delay on the USIM.

The base station broadcasts the baring configuration information through system information.

For example, the barring configuration information including information for indicating whether barring is applied to an access identifier for a terminal configured for a service that is not sensitive to delay is broadcast.

For another example, when a terminal configured for a delay-insensitive service is configured with a specific access identifier, access control/barred access attempt for one access attempt/access attempt allow/override/access control for access barring skip /Balling configuration information including information for instructing to simultaneously provide services that are not sensitive to delay and other priorities (or services) is broadcast.

For example, baring configuration information for an access category for a terminal configured for a service that is not sensitive to delay may include one or more of the following information.

-1-bit indication information to indicate whether barring is applied to an access identifier configured for a delay-insensitive service

-Access barring factor information (ac-BarringFactor): If the random number drawn by the terminal is smaller than this value, access is allowed. Otherwise, access is barred. (Or, if the random number drawn by the terminal is greater than this value, access is allowed. Otherwise, access is barred.)

-Access barring time information (ac-BarringTime)

-Information for indicating detailed type/classification/category/access identifier information of an access identifier to be applied to a terminal configured for a service that is not sensitive to delay

a) Access identifiers configured for delay-insensitive services (or terminals with all access identifiers configured for delay-insensitive services)

b) Access identifiers configured for services that are not sensitive to delay and not in the HPLMN or equivalent PLMN.

c) is configured for delay-insensitive services and is not in the PLMN listed in the preferred PLMN of the country in which the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM, not in HPLMN or equivalent to HPLMN Access identifiers not in the PLMN (or access identifiers configured for delay-insensitive services and not in the PLMN listed as the preferred PLMN of the country where the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM)

For another example, the barring configuration information for the access identifier for indicating the above-described access operation for the terminal configured for the service that is not sensitive to delay may include one or more of the following information.

-1-bit indication information to indicate whether barring is applied to the corresponding access identifier

-Access barring factor information for the corresponding access identifier (ac-BarringFactor): If the random number drawn by the terminal is smaller than this value, access is permitted. Otherwise, access is barred. (Or, if the random number drawn by the terminal is greater than this value, access is allowed. Otherwise, access is barred.)

-Access barring time information for the corresponding access identifier (ac-BarringTime)

-Information for indicating detailed type/classification/category/access identifier information of the access identifier

a) Access identifiers configured for delay-insensitive services (or terminals with all access identifiers configured for delay-insensitive services)

b) Access identifiers configured for services that are not sensitive to delay and not in the HPLMN or equivalent PLMN.

c) is configured for delay-insensitive services and is not in the PLMN listed in the preferred PLMN of the country in which the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM, not in HPLMN or equivalent to HPLMN Access identifiers not in the PLMN (or access identifiers configured for delay-insensitive services and not in the PLMN listed as the preferred PLMN of the country where the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM)

-Allow access/access control (barring) access attempts for access attempts of terminals with the corresponding access identifiers/allow access attempts/override/access control skip/delay sensitive services and other priorities for access barring (Or service) 1-bit indication information for instructing access control/barring prohibition/allowance for a terminal capable of simultaneously providing

As another example, when access is triggered by a terminal having an access identifier configured for a service that is not sensitive to delay, the AS of the terminal performs a barring check based on the received system information.

For example, if the access identifier of the corresponding terminal has a specific value and a bit indicating a barring for the corresponding access identifier included in the system information is set to 1, the terminal considers the cell as being barred. Otherwise, the terminal considers the cell to be unbarred.

For another example, if PLMN-related information is included, the entry is selected in PLMN-related information corresponding to the PLMN selected by the upper layer.

If the system information includes information about the PLMN, and if the terminal is triggered by a terminal having an access identifier configured for a delay-insensitive service, the AS of the terminal is baring based on the received system information Perform a check.

For another example, if the access identifier of the corresponding terminal has a specific value and a bit indicating barring for the corresponding access identifier included in the system information is set to 1, the terminal considers the cell to be barred.

As another example, if a terminal configured for a delay-insensitive service has a specific access identifier described above, when access is triggered by the terminal, the AS of the terminal performs a barring check based on the received system information.

For example, if the access identifier of the corresponding terminal has a specific value, the access attempt is allowed/access control (barring) for the access attempt for the access identifier included in the system information. If a bit indicating access control/barring/disallowed is set to 1 for a terminal capable of simultaneously providing override/access control for skip/delay service and other priority (or service) for the terminal, the terminal may select the cell. Consider unbarred. Otherwise, the terminal considers the cell to be unbarred. Or, the terminal performs access control/barring according to the access category of the terminal.

As another example, if PLMN-related information is included, the entry is selected in PLMN-related information corresponding to the PLMN selected by the upper layer.

If the system information includes information on the PLMN, and if the terminal is triggered by a terminal having a specific access identifier, the AS of the terminal performs a barring check based on the received system information.

For example, if the access identifier of the corresponding terminal has a specific value, the access attempt is allowed/access control (barring) for the access attempt for the access identifier included in the system information. If a bit indicating access control/barring/disallowed is set to 1 for a terminal capable of simultaneously providing override/access control for skip/delay service and other priority (or service) for the terminal, the terminal may select the cell. Consider unbarred.

A method of performing access control classified according to a combination of an access category for a terminal configured for a service not sensitive to delay and a specific access identity configured for the terminal.

Different criteria such as operator policies, deployment scenarios, subscriber profiles, and available services are used to determine whether access attempts are allowed or blocked when congestion occurs within the 5G system. These different criteria for access control can be associated with access identifiers and access categories. Based on these two aspects, the 5G system provides a single unified access control in which the operator controls access.

Configuration information for a service that is not sensitive to delay may be configured in the terminal. When a terminal configured for a service that is not sensitive to delay attempts to access (except for an emergency access attempt), the NAS of the terminal may indicate specific access category information to the AS of the terminal.

For example, an access identifier is not configured with the corresponding access identifier, allowing access attempts to access control/barring on one access attempt/allowing access attempts/override on access barring/access control skip/delay sensitive services and other priorities It may indicate configuration information for instructing to provide ranking (or service) at the same time. Access identifiers allow access attempts to access control/barred access to one access attempt/accept access attempts/override for access barring/access control skip/delay sensitive services and other priorities (or services) Is used to provide/direct the offer at the same time. The access identifier allows access attempts to be controlled/barred by access categories according to one access attempt according to subscription information/allows access attempts/overrides on access barring/access control skip/delay sensitive services and other priorities It is used to provide/direct the provision of rankings (or services) simultaneously.

As another example, the access identifier may indicate information for indicating access control/barring for one access attempt when configured with the corresponding access identifier. The access identifier is used to indicate access control/barring in one access attempt according to subscription information. The access identifier is used to provide access control/barring/access attempt permission/access control priority processing for the access attempt regardless of the access category according to one access attempt according to the subscription information.

For example, the terminal may be configured for a service that is not sensitive to delay through NAS signaling. When the terminal performs one or more procedures of a registration procedure (Registration procedure/attach procedure), PDU session establishment, tracking area update, and service request procedure, the network (e.g., core network entity, core network control plane entity, AMF) You can instruct the terminal to configure for a service that is not sensitive to delay (based on subscription information). The network may configure the terminal in association with one or more of the access category or access identifier information of the terminal to configure the terminal for a service that is not sensitive to delay.

The terminal may configure/store/set the corresponding indication information in terminal access identifier information/terminal category/terminal context/NAS context/NAS device attribute information/device attribute information in the terminal.

As another example, the terminal may have a specific value configured/stored/set in terminal access identifier information and/or terminal access category information for a service that is not sensitive to delay on the USIM.

For a service that is not sensitive to delay, the access category or access identifier information of the terminal configured in the terminal may be configured with different detailed configuration information. Alternatively, for a service that is not sensitive to delay, the access category of the terminal configured in the terminal (or access identifier information may be configured with the same detailed configuration information.)

The base station broadcasts the baring configuration information through system information.

For example, when a terminal configured for a delay-insensitive service attempts normal/normal access, it includes information to indicate whether a barring is applied to an access category and/or access identifier corresponding to the access attempt of the terminal. Broadcasts the baring configuration information.

Barring configuration information to indicate whether the barring is applied to the access category and/or access identifier corresponding to the access attempt of the corresponding terminal when the terminal configured for the delay-insensitive service attempts normal/normal access, or delay Barring configuration information for an access category and/or an access identifier for a terminal configured for a service that is not sensitive to information may include one or more of the following information.

-1-bit indication information for indicating whether barring is applied to a terminal having a specific access identifier value among terminals configured for a delay-insensitive service

For convenience of description, a case where a terminal configured for a service that is not sensitive to delay has one of five access identifiers will be described as an example. This is for convenience of explanation only, if it has one of the two access identifiers, if it has one of the three access identifiers, ..., if it has one of the ten access identifiers, and any arbitrary number of 10 or less The case of having one of the access identifiers of is also included in the scope of the present invention.

As an example, if five access identifiers (for convenience of explanation, it is assumed that successive access identifiers 6 to 10. This is only for convenience of description, and any consecutive 5 such as 1 to 5, 2 to 6, 3 to 7) If you have the number of access identifiers can be used.), it is possible to indicate whether the barring is applied to the five access identifiers. The first/leftmost bit consists of a value for access identifier 6 and the second bit is composed of a value for access identifier 7.

As another example, a bitmap may indicate whether barring is applied to an access identifier configured/stored/set on the USIM or mapped to a specific number of a terminal allocated by the network. The first/leftmost bit consists of a value for access identifier 6 and the second bit is composed of a value for access identifier 7. The terminal may have an access identifier mapped to the number of the terminal. The terminal may have one of five access identifiers, and among these, it may be set to one of the access identifiers 6 to 10. For example, MSISDN, IMSI, IMEI, and TMSI of a terminal (TMSI is described as an example for convenience of description, but any number allocated by the core network is also included in the scope of the present invention.), C-RNTI number (For convenience of explanation, the C-RNTI is described as an example, but any number assigned by the base station is included in the scope of the present invention.) An access identifier value can be obtained through a modular operation. If the expression "access identifier = 5 + terminal number mod 5" is used, it can be set to one of the access identifiers 6 to 10 based on the MSISDN, IMSI, IMEI, TMSI, and C-RNTI numbers of the terminals for all terminals. have

-Access barring factor information (ac-BarringFactor): If the random number drawn by the terminal is smaller than this value, access is allowed. Otherwise, access is barred. (Or, if the random number drawn by the terminal is greater than this value, access is allowed. Otherwise, access is barred.)

-Access barring time information (ac-BarringTime)

-Information for indicating the detailed type/classification/category of the terminal configured for delay-insensitive service

a) Terminals configured for delay-insensitive services (or all terminals configured for delay-insensitive services)

b) Terminal configured for non-delay sensitive services and not in the HPLMN or equivalent PLMN

(UEs that are configured for delay tolerant service and are neither in their HPLMN nor in a PLMN that is equivalent to it)

c) is configured for delay-insensitive services and is not in the PLMN listed in the preferred PLMN of the country in which the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM, not in HPLMN or equivalent to HPLMN UEs that are configured for delay tolerant service and are neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in a PLMN that is equivalent to their HPLMN) (or PLMN configured for the delay-insensitive service and listed as the preferred PLMN of the country where the terminal is roaming within the operator-defined PLMN selector list on SIM/USIM) Terminal not in)

-1 bit to indicate the override of access barring skip/priority processing/not barred/access allowed/access attempt allowed/override/access barring for a terminal having a specific access identifier value among terminals configured for delay-insensitive service Information

For convenience of description, it is assumed that a terminal configured for a delay-insensitive service is configured simultaneously for mission critical services such as a multimedia priority service and a public disaster service. This is only for convenience of description, and a terminal configured in one or more other services is also included in the scope of the present invention. For example, a terminal configured to provide an arbitrary service such as an emergency communication service or a specific application service is also included in the scope of the present embodiment.

As an example, it is assumed that access identifier 2 is defined as a mission critical service. This is for convenience of description, and it is also included in the scope of the present invention to define and process one or more services with an access identifier, or to process arbitrary services with a specific access identifier.

It is assumed that barring is applied to the access identifier 2 and the barring skip/priority/not barred/access allowed/access attempt allowed/override/override for access barring is set to 1.

If access is triggered by a terminal configured for a delay-insensitive service, if the terminal has access identifier 2 (or if configured/directed/set with access identifier 2), the corresponding bit in system information is 1 If set to, it is possible to perform the override for the terminal to skip/prefer processing/not barred/access allowed/access attempt allowed/override/access barring for the corresponding terminal.

Otherwise, if the corresponding bit in the system information is set to 0, access barring may be performed for the corresponding terminal (for example, the corresponding access category when access is triggered by a terminal configured for a service that is not sensitive to delay). Access barring by can be performed.

As another example, it is assumed that the access identifier 1 is defined as a multimedia priority service service. This is for convenience of description, and it is also included in the scope of the present invention to define and process one or more services with an access identifier, or to process arbitrary services with a specific access identifier.

It is assumed that barring is applied to access identifier 1 and the barring skip/priority/not barred/access allowed/access attempt allowed/override/override for access barring is set to 1.

If access is triggered by a terminal configured for a delay-insensitive service, if the terminal has access identifier 1 (or if configured/directed/set with access identifier 1), the corresponding bit in system information is 1 If set to, it is possible to perform the override for the terminal to skip/prefer processing/not barred/access allowed/access attempt allowed/override/access barring for the corresponding terminal. For example, it is possible to skip access barring for access category 1, allow access/allow access attempts/override/override for access barring.

Otherwise, if the corresponding bit in the system information is set to 0, access barring may be performed for the corresponding terminal (for example, the corresponding access category when access is triggered by a terminal configured for a service that is not sensitive to delay). Access barring by can be performed.

As another example, it is assumed that the access identifier 1 is defined as a multimedia priority service service. This is for convenience of description, and it is also included in the scope of the present invention to define and process one or more services with an access identifier, or to process arbitrary services with a specific access identifier.

If access is triggered by a terminal configured for a service that is not sensitive to delay, if the terminal has access identifier 1 (or is configured/directed/set with access identifier 1) or the terminal has access to the service If triggered), the terminal (or the NAS of the terminal) indicates the access category value (access category 2 as shown in FIG. 7) when the access is triggered by the terminal configured for a service that is not sensitive to delay in the access category for the access attempt. ) And other access category values to the AS (for example, RRC) of the terminal. For example, MO signaling not belonging to a non-paging MO signaling such as access category 3 or other access categories such as access category 7, any access category by operator classification, or any standardized access category may be delivered.

The AS of the terminal performs a barring check based on the system information for the received access category.

As described above, the present embodiment has an effect of efficiently performing access control of a terminal configured with a specific service/function, such as a service that is not sensitive to delay, based on integrated access control. Also, an access control operation of a terminal configured with a specific service, such as a service that is not sensitive to delay, may be applied in combination with the above-described integrated access control operation.

Hereinafter, a configuration of a terminal capable of performing each embodiment of the present disclosure described above will be mainly described with reference to the embodiment described in FIG. 1. However, in addition to FIG. 1, all of the following terminals may perform the above-described individual embodiments.

8 is a block diagram showing the configuration of a user terminal according to an embodiment.

Referring to FIG. 8, the terminal 800 performing the access control operation, when an access attempt of the receiver 830 and the terminal receiving operator-defined access category information through NAS (Non-Access Stratum) signaling is triggered, the NAS In the (Non-Access Stratum) layer or the Access Stratum (AS) layer, one access category for an access attempt is determined, RRC setting cause information associated with the access category is selected, and access barring parameters associated with the access category are used. The control unit 810 may perform an access barring check operation in an access stratum (AS).

For example, the terminal 800 may be set in advance or perform a connection control operation using the reference access category received from the base station and operator-defined access category information received from the base station through NAS signaling.

For example, the reference access category may be configured with a mapping table that is mapped to determine the access category according to the type of access attempt of the terminal.

As another example, the operator-defined access category may include at least one of an access category number, a 5G QoS Identifier (5QI), an application identifier that triggers an access attempt, and specific PDU session information associated with the slice.

The controller 810 may store operator-defined access category information in the terminal, and detect whether the terminal's access attempt is triggered. In the case of an access attempt, it may occur when a terminal establishes an RRC connection with a base station. Or, an access attempt may be generated in order for the terminal to communicate with the base station.

For example, the controller 810 may determine that the access attempt of the terminal is triggered when a state transition occurs from the RRC idle state to the RRC connected state or when the terminal starts a PDU session in the RRC connected state.

As another example, when an emergency signal is required to be transmitted, the controller 810 may determine that an access attempt is triggered when a response to a paging signal, an access attempt for a low-latency service, or a terminal transmission of voice data is triggered. have.

When an access attempt is triggered, the control unit 810 may select any one of the access categories stored/configured in the terminal. For example, one access category selected by the control unit 810 means category information selected from a set of access categories including reference access categories and operator-defined access category information.

As described above, the control unit 810 may select an access category that is divided and set for each access attempt. For example, the terminal may determine the access category indicated by the access attempt by checking the rules according to the rule number order of the mapping table in which one or more access categories are assigned for each access attempt. To this end, the terminal uses a mapping table to which access attempts and access categories are mapped.

The mapping table may be configured such that the rule number (Rule #), the type of access attempt, and the access category are mapped. Further, the mapping table may be configured using the reference access category described above, or may be configured using an operator-defined access category. Alternatively, the mapping table may be configured using both a reference access category and an operator-defined access category.

Accordingly, the control unit 810 may check each access attempt according to the rule number using the configured mapping table, and select an access category mapped to the access attempt when a triggered access attempt exists.

Meanwhile, when the rule 810 checks the rules according to the mapping table and there is more than one access category mapped to the access attempt, the controller 810 may determine the access category with the lowest rule number as the access category. For example, although an access attempt for a delay immunity service (a service having low delay sensitivity) has been triggered, there may be a case where the specific access attempt is included in an operator-defined access category. That is, access attempts can be mapped to both the reference access category and the operator-defined access category. In this case, since the rule number associated with the operator-defined access category is 3 and the rule number for the delay immunity service is 4, the terminal can select 3 operator-defined access categories with a relatively low rule number.

Alternatively, the control unit 810 checks the access attempt from the lowest rule number in the mapping table, and when there is an access attempt that matches the triggered access attempt, stops further checking the rule number, and selects an access category mapped to the access attempt. You can choose.

To this end, the rule number of the mapping table may be set to check for a specific access attempt from a low number. For example, the rule number of the access attempt mapped to the operator-defined access category may be set smaller than the rule number of the access attempt for the delay immunity service.

Meanwhile, the control unit 810 may select an access category according to the access attempt using a mapping table, and select RRC setting cause information associated with the selected access category. The controller 810 selects an access category associated with an access attempt from one or more reference access categories, and selects an RRC setting cause mapped to the access category. The reason for setting the access category and the RRC may be linked through a separate mapping table. That is, the access category and the cause of RRC establishment may be mapped according to a one-to-one mapping relationship.

The control unit 810 may perform an access barring check operation using the access barring parameters stored in association with the selected access category. The access barring parameter may be received from the base station or may be stored in advance in the terminal, and the value may be set differently for each access category. Accordingly, the control unit 810 checks the access barring parameters configured in association with the determined access category, and applies the corresponding parameters to perform an access barring check operation.

In addition, the control unit 810 performs an integrated access control operation using an operator-defined access category and a reference access category in a method of performing access control in a next-generation mobile communication network required to perform the above-described present disclosure. And, it controls the overall operation of the user terminal 800 according to performing an integrated access control operation considering a service that is not sensitive to delay.

Also, the transmitter 820 and the receiver 830 are used to transmit and receive signals, messages, and data necessary to perform the above-described embodiments with other base stations or other terminals.

The terms "system", "processor", "controller", "component", "module", "interface", "model", and "unit" described above are generally computer-related entity hardware, a combination of hardware and software. , Software or running software. For example, the components described above may be, but are not limited to, processes, processors, controllers, control processors, entities, execution threads, programs and/or computers driven by a processor. For example, both an application running on a controller or processor and a controller or processor can be a component. One or more components can be in a process and/or thread of execution, and the components can be located on one system or deployed to more than one system.

The standard contents or standard documents mentioned in the above-described embodiment are omitted to simplify the description of the specification and constitute a part of the specification. Accordingly, it is to be construed that adding the contents of the above standard contents and parts of the standard documents to the specification or in the claims falls within the scope of the present disclosure.

The above description is merely illustrative of the technical spirit of the present disclosure, and those skilled in the art to which the present disclosure pertains may make various modifications and variations without departing from the essential characteristics of the technical spirit. Therefore, the embodiments disclosed in the present specification are not intended to limit the technical spirit of the present disclosure, but to explain them, and the scope of the technical idea is not limited by these embodiments. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical spirits within the scope equivalent thereto should be interpreted as being included in the scope of this right.

Claims (18)

In the method for the terminal to perform the access control operation,
Receiving operator-defined access category information through NAS (Non-Access Stratum) signaling;
When an access attempt of the terminal is triggered, determining one access category for the access attempt at a Non-Access Stratum (NAS) layer or an Access Stratum (AS) layer;
Selecting RRC setting cause information associated with the access category; And
And performing an access barring check operation in the access stratum (AS) layer using an access barring parameter associated with the access category,
The operator-defined access category information,
5GI (5G QoS Identifier) and includes the application identifier information that triggered the access attempt,
The one access category,
It is selected from a set of access categories including the reference access category and the operator-defined access category information,
Determining the access category,
By checking the rules in the order of rule numbers in the mapping table where one or more access categories are assigned for each access attempt,
Determine the access category indicated by the access attempt,
When there are two or more access categories mapped to the access attempt as a result of checking the rule according to the mapping table,
A method for determining the access category of the lowest rule number as the access category. delete According to claim 1,
The operator-defined access category information,
And further including at least one of access category number and specific PDU session information associated with the slice. According to claim 1,
Determining the access category,
A method characterized in that it is determined that an access attempt of the terminal is triggered when a state transition occurs from the RRC idle state to the RRC connected state or when the terminal initiates a PDU session in the RRC connected state. delete delete According to claim 1,
The rule number of the mapping table,
The method characterized in that the rule number of the access attempt mapped to the operator-defined access category is set smaller than the rule number of the access attempt for delay immunity service. According to claim 1,
The step of selecting the RRC setting cause information,
And selecting an access category associated with the access attempt from one or more of the reference access categories, and selecting the RRC setting cause mapped to the access category. The method of claim 8,
The one or more reference access categories,
And set in association with the operator-defined access category. In the terminal performing the access control operation,
A receiver configured to receive operator-defined access category information through NAS (Non-Access Stratum) signaling; And
When the access attempt of the terminal is triggered, a non-access stratum (NAS) layer or an access stratum (AS) layer determines one access category for the access attempt,
Select RRC setting cause information associated with the access category,
It includes a control unit for performing an access barring (Access Barring) check operation in the AS (Access Stratum) layer using the access barring parameters associated with the access category,
The operator-defined access category information,
5GI (5G QoS Identifier) and includes the application identifier information that triggered the access attempt,
The one access category,
It is selected from a set of access categories including the reference access category and the operator-defined access category information,
The control unit,
By checking the rules in the order of rule numbers in the mapping table where one or more access categories are assigned for each access attempt,
Determine the access category indicated by the access attempt,
When there are two or more access categories mapped to the access attempt as a result of checking the rule according to the mapping table,
The terminal determines the access category of the lowest rule number as the access category. delete The method of claim 10,
The operator-defined access category information,
The terminal comprising at least one of the access category number and specific PDU session information associated with the slice. The method of claim 10,
The control unit,
A terminal characterized in that it is determined that an access attempt of the terminal is triggered when a state transition occurs from the RRC idle state to the RRC connected state or when the terminal initiates a PDU session in the RRC connected state. delete delete The method of claim 10,
The rule number of the mapping table,
The terminal characterized in that the rule number of the access attempt mapped to the operator-defined access category is set smaller than the rule number of the access attempt for delay immunity service. The method of claim 10,
The control unit,
And selecting an access category associated with the access attempt from one or more of the reference access categories, and selecting the RRC setting cause mapped to the access category. The method of claim 17,
The one or more reference access categories,
A terminal characterized in that it is set in association with the operator-defined access category.

Images