Method and apparatus for enhanced access barring in wireless communication system
Patent Information
- Application Number
- KR1020250028361
- Authority / Receiving Office
- KR · KR
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-05
- Publication Date
- 2026-09-14
Smart Images

Figure PAT00007_ABST
Abstract
Description
Technology Field
[0001] This specification relates to wireless communication, and more specifically, to a method and apparatus for improved access control in a wireless communication system. Background Technology
[0002] In a mobile system, a terminal remains in idle mode when there is no traffic to minimize power consumption. On the other hand, when data transmission is required from the terminal (e.g., Mobile Originated (MO) data / voice call) or when data transmission to the terminal occurs (e.g., Mobile Terminated (MT) data / voice call), the terminal can switch to active mode and resume communication. Additionally, the terminal can switch to active mode to update the network with changed information when detecting changes in a specific area, such as in TAU (Tracking Area Update) or RNAU (RAN-based Notification Area Update). The problem to be solved
[0003] Problems can arise due to background traffic in places where a large number of users utilize communication services, such as subways or shopping malls. Many users in subways or shopping malls may not actually be using their devices; in other words, the screens of many devices may be turned off. Even in such cases, some non-essential background traffic, such as updates from internal applications, may occur, and the device generating this traffic may attempt to restore the connection through an RRC re-establishment process. At this time, the traffic generated by these connection restoration attempts may cause a degradation in communication quality based on issues such as RACH failures for users who are actually using their devices, such as playing games or watching YouTube. To resolve this problem, a method is required to appropriately block access to background traffic from devices that are not actually in use (access barring). means of solving the problem
[0004] According to one embodiment, a method performed by a terminal in a wireless communication system is proposed, wherein the terminal obtains information regarding a low priority packet-based access ban from a base station, and performs an access barring operation based on the information regarding the low priority packet-based access ban and a low priority packet marker, wherein the information regarding the low priority packet-based access ban includes a type indicator indicating the type of a low priority packet, and the terminal inserts the low priority packet marker into a packet based on the information regarding the low priority packet-based access ban, and the access barring operation includes an operation in which the terminal determines whether to transmit a random access preamble to the base station.
[0005] Here, the information related to low-priority packet-based access prohibition includes at least one of an access prohibition indicator indicating that a low-priority packet-based access prohibition operation is performed, an application / slice identifier for an application / slice having a high priority, access prohibition factor information, and access prohibition timer information, and the type indicator may include at least one of packet type information and traffic pattern information.
[0006] Here, when the terminal determines whether to transmit a random access preamble to the base station, the terminal determines whether the low priority packet marker exists, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is a first type, the terminal determines whether the application / slice identifier is high, and based on the fact that the application / slice identifier is determined to be high, the terminal determines whether the factor value indicated by the access prohibition factor information is greater than a value arbitrarily selected by the terminal, and based on the fact that the factor value is greater than a value arbitrarily selected by the terminal, the terminal transmits the random access preamble to the base station, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is a second type, the terminal can transmit the random access preamble to the base station.
[0007] Here, based on the determination that the low priority packet marker does not exist or that the application / slice identifier is not high, the terminal does not perform the access prohibition operation, and based on the determination that the factor value is smaller than a value arbitrarily selected by the terminal, the terminal may perform an access delay based on the access prohibition timer information.
[0008] Here, in response to the random connection preamble, the terminal can receive a random connection response from the base station.
[0009] Here, based on receiving the random connection response, the terminal can transmit a message to the base station for RRC (Radio Resource Control) re-establishment.
[0010] Here, the information regarding the low-priority packet-based access prohibition mentioned above can be transmitted through system information.
[0011] According to another embodiment, the terminal comprises one or more memories for storing instructions; one or more transceivers; and one or more processors connecting the one or more memories and the one or more transceivers, wherein the one or more processors execute the instructions to obtain information regarding low priority packet-based access barring from a base station, and perform an access barring operation based on the information regarding low priority packet-based access barring and a low priority packet marker, wherein the information regarding low priority packet-based access barring includes a type indicator indicating the type of a low priority packet, and the terminal inserts the low priority packet marker into a packet based on the information regarding low priority packet-based access barring, and the access barring operation includes an operation in which the terminal determines whether to transmit a random access preamble to the base station.
[0012] Here, the information related to low-priority packet-based access prohibition includes at least one of an access prohibition indicator indicating that a low-priority packet-based access prohibition operation is performed, an application / slice identifier for an application / slice having a high priority, access prohibition factor information, and access prohibition timer information, and the type indicator may include at least one of packet type information and traffic pattern information.
[0013] Here, when the terminal determines whether to transmit a random access preamble to the base station, the terminal determines whether the low priority packet marker exists, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is a first type, the terminal determines whether the application / slice identifier is high, and based on the fact that the application / slice identifier is determined to be high, the terminal determines whether the factor value indicated by the access prohibition factor information is greater than a value arbitrarily selected by the terminal, and based on the fact that the factor value is greater than a value arbitrarily selected by the terminal, the terminal transmits the random access preamble to the base station, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is a second type, the terminal can transmit the random access preamble to the base station.
[0014] Here, based on the determination that the low priority packet marker does not exist or that the application / slice identifier is not high, the terminal does not perform the access prohibition operation, and based on the determination that the factor value is smaller than a value arbitrarily selected by the terminal, the terminal may perform an access delay based on the access prohibition timer information.
[0015] Here, in response to the random connection preamble, the terminal can receive a random connection response from the base station.
[0016] Here, based on receiving the random connection response, the terminal can transmit a message to the base station for RRC (Radio Resource Control) re-establishment.
[0017] Here, the information regarding the low-priority packet-based access prohibition mentioned above can be transmitted through system information.
[0018] Herein, in at least one computer-readable medium comprising an instruction based on execution by at least one processor included in a terminal, the device is configured to obtain low-priority packet-based access barring information from a base station, and is configured to perform an access barring operation based on the low-priority packet-based access barring information and a low-priority packet marker, wherein the low-priority packet-based access barring information includes a type indicator indicating the type of a low-priority packet, and the terminal inserts the low-priority packet marker into a packet based on the low-priority packet-based access barring information, and the access barring operation may include an operation in which the terminal determines whether to transmit a random access preamble to the base station.
[0019] Here, the information related to low-priority packet-based access prohibition includes at least one of an access prohibition indicator indicating that a low-priority packet-based access prohibition operation is performed, an application / slice identifier for an application / slice having a high priority, access prohibition factor information, and access prohibition timer information, and the type indicator may include at least one of packet type information and traffic pattern information.
[0020] Here, when the terminal determines whether to transmit a random access preamble to the base station, the terminal determines whether the low priority packet marker exists, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is a first type, the terminal determines whether the application / slice identifier is high, and based on the fact that the application / slice identifier is determined to be high, the terminal determines whether the factor value indicated by the access prohibition factor information is greater than a value arbitrarily selected by the terminal, and based on the fact that the factor value is greater than a value arbitrarily selected by the terminal, the terminal transmits the random access preamble to the base station, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is a second type, the terminal can transmit the random access preamble to the base station.
[0021] Here, based on the determination that the low priority packet marker does not exist or that the application / slice identifier is not high, the terminal does not perform the access prohibition operation, and based on the determination that the factor value is smaller than a value arbitrarily selected by the terminal, the terminal may perform an access delay based on the access prohibition timer information.
[0022] Here, in response to the random access preamble, the terminal receives a random access response from the base station, and based on receiving the random access response, the terminal can transmit a message to the base station for the re-establishment of Radio Resource Control (RRC).
[0023] Here, the information regarding the low-priority packet-based access prohibition mentioned above can be transmitted through system information. Effects of the invention
[0024] According to the present specification, access prohibition is performed based on the type and priority of the packet, so communication for the user actually performing the communication is preferentially allowed, and communication efficiency is increased.
[0025] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification. Brief explanation of the drawing
[0026] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings. FIG. 1 is a conceptual diagram illustrating a wireless communication system according to one embodiment of the present invention. FIG. 2 is an exemplary diagram showing a 5G system to which a data transmission method according to one embodiment of the present invention can be applied. FIG. 3 is a diagram illustrating a resource grid supported by wireless access technology to which the present invention can be applied. FIG. 4 is a diagram illustrating a bandwidth part (BWP) supported by wireless access technology to which the present invention can be applied. FIG. 5 is a diagram illustrating an exemplary Sync. Signal Block (SSB) in a wireless access technology to which the present invention can be applied. FIG. 6 illustrates an example of an RRC re-establishment procedure performed by a terminal according to one embodiment of the present specification. FIG. 7 illustrates another example of an RRC re-establishment procedure performed by a terminal according to one embodiment of the present specification. FIG. 8 illustrates an example of a low-priority packet-based access prohibition operation according to one embodiment of the present specification. FIG. 9 illustrates an example of a NAS protocol structure according to one embodiment of the present specification. FIG. 10 is a flowchart of an example of a communication method performed by a terminal according to an embodiment of the present specification. FIG. 11 shows a terminal and a network node in which an embodiment of the present specification is implemented. Specific details for implementing the invention
[0027] The present invention is susceptible to various modifications and may have various embodiments; specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the invention to specific embodiments, and it should be understood that the invention includes all modifications, equivalents, and substitutions that fall within the spirit and scope of the invention. Similar reference numerals have been used for similar components in the description of each drawing.
[0028] In this specification, terms such as "first," "second," "A," "B," etc., may be used to describe various components, but said components should not be limited by said terms. These terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be named the second component, and similarly, the second component may be named the first component. Additionally, the term "and / or" includes a combination of a plurality of related described items or any one of a plurality of related described items.
[0029] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.
[0030] The terms used herein are merely for describing specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, terms such as “comprising” or “having” are intended to indicate the presence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.
[0031] Unless otherwise defined, the terms used in this specification, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the present invention pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this specification.
[0032] Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the attached drawings.
[0033] FIG. 1 is a conceptual diagram illustrating a wireless communication system according to one embodiment of the present invention.
[0034] Referring to FIG. 1, the wireless communication system (100) may be composed of a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6).
[0035] Each of the multiple communication nodes may support at least one communication protocol. For example, each of the multiple communication nodes may support a CDMA (Code Division Multiple Access) based communication protocol, a WCDMA (Wideband CDMA) based communication protocol, a TDMA (Time Division Multiple Access) based communication protocol, a FDMA (Frequency Division Multiple Access) based communication protocol, an OFDM (Orthogonal Frequency Division Multiplexing) based communication protocol, an OFDMA (Orthogonal Frequency Division Multiple Access) based communication protocol, a SC (Single Carrier)-FDMA based communication protocol, a NOMA (Non-Orthogonal Multiple Access) based communication protocol, a SDMA (space division multiple access) based communication protocol, etc.
[0036] The wireless communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of user equipments (130-1, 130-2, 130-3, 130-4, 130-5, 130-6).
[0037] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can form a macro cell. Each of the fourth base station (120-1) and the fifth base station (120-2) can form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) may be located within the coverage of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) may be located within the coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be within the coverage of the third base station (110-3). The first terminal (130-1) may be within the coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the coverage of the fifth base station (120-2).
[0038] Here, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as Node B, evolved Node B, next generation Node B (gNB), next generation 6G base station, Base Transceiver Station (BTS), radio base station, radio transceiver, access point, access node, roadside unit (RSU), Digital Unit (DU), Cloud Digital Unit (CDU), Radio Remote Head (RRH), Radio Unit (RU), Transmission Point (TP), transmission and reception point (TRP), relay node, etc. Each of the multiple terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as a terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, etc.
[0039] Each of the multiple communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6) can support cellular communication (e.g., LTE (long term evolution), LTE-A (advanced), NR (New Radio), 6G Radio Access Technology, etc. as defined in 3GPP (3rd generation partnership project) standards). Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can operate in different frequency bands or in the same frequency band. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can be connected to each other via an ideal backhaul or a non-ideal backhaul, and can exchange information with each other via the ideal backhaul or the non-ideal backhaul. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can be connected to a core network (not shown) via an ideal backhaul or a non-ideal backhaul. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit a signal received from the core network to the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), and can transmit a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) to the core network.
[0040] Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can support OFDM-based downlink transmission. Additionally, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can support OFDM or DFT-Spread-OFDM-based uplink transmission. In addition, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can support MIMO (Multiple Input Multiple Output) transmission (e.g., SU (Single User)-MIMO, MU (Multi User)-MIMO, massive MIMO, etc.), CoMP (Coordinated Multipoint) transmission, carrier aggregation transmission, transmission in an unlicensed band, and device-to-device (D2D) communication (or ProSe (proximity services), etc.). Here, each of the multiple terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) supports base stations (110-1, 110-2, 110-3, 120-1, It can perform operations corresponding to 120-2) and / or operations supported by base stations (110-1, 110-2, 110-3, 120-1, 120-2).
[0041] For example, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) based on the SU-MIMO method, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) based on the SU-MIMO method. Alternatively, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) and the fifth terminal (130-5) based on the MU-MIMO method, and each of the fourth terminal (130-4) and the fifth terminal (130-5) can receive a signal from the second base station (110-2) based on the MU-MIMO method. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP method, and the fourth terminal (130-4) can receive a signal from the first base station (110-1), the second base station (110-2), and the third base station (110-3) by the CoMP method. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive signals based on the CA method with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its coverage area.
[0042] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can coordinate D2D communication between the fourth terminal (130-4) and the fifth terminal (130-5), and each of the fourth terminal (130-4) and the fifth terminal (130-5) can perform D2D communication through the coordination of each of the second base station (110-2) and the third base station (110-3).
[0043] In the following, even when a method performed at a first communication node among the communication nodes (e.g., transmission or reception of a signal) is described, the corresponding second communication node may perform a method corresponding to the method performed at the first communication node (e.g., reception or transmission of a signal). That is, when the operation of a terminal is described, the corresponding base station may perform an operation corresponding to the operation of the terminal. Conversely, when the operation of a base station is described, the corresponding terminal may perform an operation corresponding to the operation of the base station.
[0044] In addition, as described below, the downlink (DL) refers to communication from a base station to a terminal, and the uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter may be part of the base station, and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal, and the receiver may be part of the base station.
[0045] Recently, with the rapid proliferation of smartphones and IoT (Internet of Things) devices, the volume of information exchanged through communication networks is increasing. Accordingly, next-generation wireless access technologies need to consider environments that provide faster services to more users than existing communication systems (or radio access technologies) (e.g., enhanced mobile broadband communication). To this end, the design of communication systems that consider Machine Type Communication (MTC), which connects multiple devices and objects to provide services, is being discussed. Furthermore, the design of communication systems that consider services and / or terminals sensitive to communication reliability and / or latency (e.g., Ultra-Reliable and Low Latency Communication (URLC)) is also being discussed.
[0046] In the following specification, for convenience of explanation, the next-generation wireless access technology is referred to as New RAT (Radio Access Technology), and the wireless communication system to which the New RAT is applied is referred to as NR (New Radio) system. In this specification, frequency, frame, subframe, resource, resource block, region, band, subband, control channel, data channel, synchronization signal, various reference signals, various signals, or various messages related to NR may be interpreted in the sense used in the past or present, or in various senses used in the future.
[0047] FIG. 2 is an exemplary diagram showing an NR system to which a data transmission method according to an embodiment of the present invention can be applied.
[0048] 5G, standardized by 3GPP, is a wireless access technology that provides enhanced data transmission rates compared to LTE and can satisfy various QoS requirements demanded by segmented and specific usage scenarios. In particular, eMBB (enhanced Mobile BroadBand), mMTC (massive MTC), and URLLC (Ultra Reliable and Low Latency Communications) have been defined as representative usage scenarios for NR. As a method to satisfy the requirements of each scenario, a flexible frame structure compared to LTE is provided. The frame structure of 5G NR supports a multiple subcarrier-based frame structure. The default Subcarrier Spacing (SCS) is 15 kHz, and a total of five types of SCS are supported as 15 kHz * 2^n (n=0, 1, 2, 3, 4).
[0049] Referring to FIG. 2, the NG-RAN (Next Generation-Radio Access Network) consists of gNBs that provide control plane (RRC) protocol endpoints for the NG-RAN user plane (SDAP / PDCP / RLC / MAC / PHY) and the UE (User Equipment). Here, NG-C represents a control plane interface used for the NG2 reference point between the NG-RAN and the 5GC (5th Generation Core). NG-U represents a user plane interface used for the NG3 reference point between the NG-RAN and the 5GC.
[0050] The gNB is interconnected through the Xn interface and connected to the 5GC through the NG interface. More specifically, the gNB is connected to the Access and Mobility Management Function (AMF) through the NG-C interface and to the User Plane Function (UPF) through the NG-U interface.
[0051] In the NR system of Fig. 2, multiple numerologies may be supported. Here, the numerology can be defined by subcarrier spacing and CP (Cyclic Prefix) overhead. In this case, multiple subcarrier spacings can be derived by scaling the basic subcarrier spacing by an integer. Additionally, even if it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band.
[0052] In addition, various frame structures based on multiple numerologies can be supported in the NR system.
[0053] The NR waveform, numeral, and frame structure are described below.
[0054] In NR, CP-OFDM waveforms using a cyclic prefix are used for downlink transmission, and CP-OFDM or DFT-S-OFDM are used for uplink transmission. OFDM technology is easy to combine with MIMO (Multiple Input Multiple Output) and has the advantage of allowing the use of low-complexity receivers along with high frequency efficiency.
[0055] Meanwhile, in NR, since the requirements for data rate, latency, coverage, etc. differ for each of the three scenarios mentioned above, it is necessary to efficiently satisfy the requirements for each scenario through the frequency bands that constitute an arbitrary NR system. To this end, a technology has been proposed to efficiently multiplex wireless resources based on multiple different numerologies.
[0056] Specifically, the NR transmission numerator is determined based on sub-carrier spacing and CP (Cyclic prefix), and as shown in Table 1 below, the μ value is used as an exponential value of 2 based on 15 kHz and changes exponentially.
[0057] μ 서브캐리어 간격(kHz) Cyclic prefix Supported for data Supported for synch 0 15 Normal Yes Yes 1 30 Normal Yes Yes 2 60 Normal, Extended Yes No 3 120 Normal Yes Yes 4 240 Normal No Yes
[0058] As shown in Table 1 above, the numerators of NR can be classified into five types based on the subcarrier spacing. This differs from LTE, one of the 4G communication technologies, where the subcarrier spacing is fixed at 15 kHz. Specifically, the subcarrier spacings used for data transmission in NR are 15, 30, 60, and 120 kHz, while the subcarrier spacings used for synchronization signal transmission are 15, 30, 120, and 240 kHz. Additionally, extended CP is applied only to the 60 kHz subcarrier spacing. Meanwhile, the frame structure in NR defines a frame with a length of 10 ms, composed of 10 subframes of equal length of 1 ms. A single frame can be divided into 5 ms half-frames, and each half-frame contains 5 subframes. For a 15kHz subcarrier interval, one subframe consists of one slot, and each slot consists of 14 OFDM symbols.
[0059] NR physical resources are described below.
[0060] Regarding physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, and bandwidth parts are considered.
[0061] An antenna port is defined such that the channel carrying a symbol on the antenna port can be inferred from the channel carrying another symbol on the same antenna port. If the large-scale property of the channel carrying a symbol on one antenna port can be inferred from the channel carrying a symbol on another antenna port, the two antenna ports can be said to be in a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale property includes one or more of delay spread, Doppler spread, Doppler shift, average delay, and spatial reception parameters.
[0062] FIG. 3 is a diagram illustrating a resource grid supported by wireless access technology to which the present invention can be applied.
[0063] Referring to FIG. 3, a resource grid may exist for each numerator because NR supports multiple numerators on the same carrier. Additionally, a resource grid may exist depending on the antenna port, subcarrier spacing, and transmission direction.
[0064] A resource block consists of 12 subcarriers and is defined only in the frequency domain. Additionally, a resource element consists of one OFDM symbol and one subcarrier. Therefore, as shown in Fig. 3, the size of a single resource block can vary depending on the subcarrier spacing. Furthermore, NR defines "Point A," which serves as a common reference point for the resource block grid, as well as a common resource block, a physical resource block, and the like.
[0065] FIG. 4 is a diagram illustrating the bandwidth part supported by the wireless access technology to which the present invention can be applied.
[0066] In NR, unlike LTE where the carrier bandwidth is fixed at 20 MHz, the maximum carrier bandwidth is set from 50 MHz to 400 MHz depending on the subcarrier interval. Therefore, it is not assumed that all terminals use this entire carrier bandwidth. Accordingly, in NR, as shown in Fig. 4, a Bandwidth Part (BWP) can be designated within the carrier bandwidth for the terminal to use. Additionally, a Bandwidth Part is associated with a single numerator and consists of a subset of a continuous common resource block, and can be dynamically activated over time. Up to four Bandwidth Parts are configured for the uplink and downlink respectively, and data is transmitted and received using the Bandwidth Part activated at a given time.
[0067] In the case of paired spectrum, the uplink and downlink bandwidth parts are set independently, whereas in the case of unpaired spectrum, the downlink and uplink bandwidth parts are paired to share a center frequency in order to prevent unnecessary frequency re-tuning between downlink and uplink operations.
[0068] The initial NR connection is described below.
[0069] In NR, the terminal performs cell search and random access procedures to connect to the base station and perform communication.
[0070] Cell search is a procedure in which a terminal uses a Synchronization Signal Block (SSB) transmitted by a base station to synchronize with the corresponding base station's cell, obtain a physical layer cell ID, and acquire system information.
[0071] The wireless protocol structure for the user plane and the control plane is described below.
[0072] The physical layer (PHY layer) provides information transfer services to upper layers using physical channels. The physical layer is connected to the upper layer, the MAC (Medium Access Control) layer, through transport channels. Data travels between the MAC layer and the physical layer through transport channels. Transport channels are classified according to how and with what characteristics data is transmitted through wireless interfaces.
[0073] Data travels between different physical layers, specifically between the physical layers of the transmitter and the receiver, through a physical channel. This physical channel can be modulated using the Orthogonal Frequency Division Multiplexing (OFDM) method and utilizes time and frequency as wireless resources.
[0074] The functions of the MAC layer include mapping between logical channels and transmission channels, and multiplexing / demultiplexing MAC SDUs (service data units) belonging to logical channels into transport blocks provided as physical channels over the transmission channels. The MAC layer provides services to the RLC (Radio Link Control) layer through logical channels.
[0075] The functions of the RLC layer include the concatenation, segmentation, and reassembly of RLC SDUs. To ensure the various Quality of Service (QoS) required by the Radio Bearer (RB), the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through Automatic Repeat Requests (ARQ).
[0076] The RRC (Radio Resource Control) layer is defined only in the control plane. The RRC layer is responsible for controlling logical channels, transmission channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers. RB refers to a logical path provided by the first layer (PHY layer) and the second layer (MAC layer, RLC layer, PDCP layer) for data transmission between a terminal and a network.
[0077] The functions of the PDCP (Packet Data Convergence Protocol) layer in the user plane include the delivery of user data, header compression, and ciphering. The functions of the PDCP (Packet Data Convergence Protocol) layer in the control plane include the delivery of control plane data and encryption / integrity protection.
[0078] The establishment of an RB refers to the process of defining the characteristics of the wireless protocol layer and channel to provide specific services, and setting their respective specific parameters and operating methods. RBs can be further divided into two types: SRBs (Signaling RBs) and DRBs (Data RBs). SRBs are used as a channel for transmitting RRC messages in the control plane, while DRBs are used as a channel for transmitting user data in the user plane.
[0079] When an RRC connection is established between the terminal's RRC layer and the E-UTRAN's RRC layer, the terminal is in an RRC connected state; otherwise, it is in an RRC idle state.
[0080] Downlink transmission channels for transmitting data from a network to a terminal include a Broadcast Channel (BCH) for transmitting system information and a Shared Channel (SCH) for transmitting user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services may be transmitted via the Shared Channel (SCH) or via a separate Multicast Channel (MCH). Meanwhile, uplink transmission channels for transmitting data from a terminal to a network include a Random Access Channel (RACH) for transmitting initial control messages and a Shared Channel (SCH) for transmitting user traffic or control messages.
[0081] Logical channels that are located above the transmission channel and mapped to the transmission channel include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), and MTCH (Multicast Traffic Channel).
[0082] A physical channel consists of multiple OFDM symbols in the time domain and multiple subcarriers in the frequency domain. A single subframe consists of multiple OFDM symbols in the time domain. A resource block is a resource allocation unit composed of multiple OFDM symbols and multiple subcarriers. Additionally, each subframe may utilize specific subcarriers of specific OFDM symbols (e.g., the first OFDM symbol) within that subframe for the Physical Downlink Control Channel (PDCCH), i.e., the L1 / L2 control channel. A Transmission Time Interval (TTI) is a unit of time for transmission, which can be, for example, a subframe or a slot.
[0083] FIG. 5 is a diagram illustrating an exemplary synchronization signal block in a wireless access technology to which the present invention can be applied.
[0084] Referring to FIG. 5, the SSB consists of a PSS (Primary Synchronization Signal) and an SSS (Secondary Synchronization Signal) each occupying 1 symbol and 127 subcarriers, and a PBCH spanning 3 OFDM symbols and 240 subcarriers.
[0085] The terminal monitors the SSB in the time and frequency domains and receives the SSB.
[0086] SSBs can be transmitted up to 64 times within 5ms. Multiple SSBs are transmitted via different transmission beams within the 5ms timeframe, and the terminal performs detection by assuming that an SSB is transmitted every 20ms when viewed from the perspective of a specific beam used for transmission. The number of beams available for SSB transmission within the 5ms timeframe can increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted at 3GHz or lower, up to 8 beams in the frequency band from 3GHz to 6GHz, and up to 64 different beams can be used to transmit SSBs in the frequency band above 6GHz.
[0087] Two SSBs are included in a single slot, and the starting symbol and number of repetitions within the slot are determined according to the subcarrier interval as follows.
[0088] Meanwhile, unlike the SS of conventional LTE, the SSB is not transmitted at the center frequency of the carrier bandwidth. That is, the SSB can be transmitted even at locations other than the center of the system band, and multiple SSBs can be transmitted across the frequency domain when broadband operation is supported. Accordingly, the terminal monitors the SSB using a synchronization raster, which is a candidate frequency location for monitoring the SSB. The carrier raster, which is information on the center frequency location of the channel for initial connection, and the synchronization raster were newly defined in NR, and the synchronization raster is set with a wider frequency interval compared to the carrier raster, thereby supporting fast SSB search by the terminal.
[0089] The terminal can obtain the MIB through the SSB's PBCH. The Master Information Block (MIB) contains the minimum information required for the terminal to receive the remaining system information (RMSI, Remaining Minimum System Information, or SIB1 (System Information Block 1)) broadcast by the network. Additionally, the PBCH may include information regarding the location of the first DM-RS (demodulation reference signal) symbol in the time domain, information for the terminal to monitor SIB1 (e.g., SIB1 numerology information, information related to SIB1 CORESET, search space information, parameter information related to PDCCH (physical downlink control channel), etc.), and offset information between the Common Resource Block and the SSB (the absolute location of the SSB within the carrier is transmitted via SIB1). Here, the SIB1 numerology information is also applied identically to some messages used in the random access procedure for the terminal to connect to the base station after completing the cell search procedure. For example, the numerology information of SIB1 may be applied to at least one of messages 1 to 4 for a random access procedure.
[0090] The aforementioned RMSI may refer to SIB1 (System Information Block 1), and SIB1 is broadcast periodically (e.g., 160ms) from the cell. SIB1 contains information necessary for the terminal to perform the initial random access procedure and is transmitted periodically via PDSCH. To receive SIB1, the terminal must receive the numerology information used for transmitting SIB1 and the CORESET (Control Resource Set) information used for scheduling SIB1 via PBCH. The terminal checks the scheduling information for SIB1 using SI-RNTI within the CORESET and obtains SIB1 on the PDSCH according to the scheduling information. The remaining SIBs, excluding SIB1, may be transmitted periodically or upon the terminal's request.
[0091] Hereinafter, the method proposed by this specification is described. The method, configuration, and technical features described in this specification are described based on a 5G NR system, but the method, configuration, and technical features described in this specification may also be applied to other communication systems, such as next-generation wireless communication systems, other than 5G NR systems.
[0092] In a mobile system, a terminal remains in idle mode when there is no traffic to minimize power consumption. On the other hand, when data transmission is required from the terminal (e.g., Mobile Originated (MO) data / voice call) or when data transmission to the terminal occurs (e.g., Mobile Terminated (MT) data / voice call), the terminal can switch to active mode and resume communication. Additionally, the terminal can switch to active mode to update the network with changed information when detecting changes in a specific area, such as in TAU (Tracking Area Update) or RNAU (RAN-based Notification Area Update).
[0093] To switch the terminal to an active mode, the terminal may perform a Radio Resource Control (RRC) reestablishment procedure. FIG. 6 illustrates an example of an RRC reestablishment procedure performed by a terminal according to an embodiment of the present specification.
[0094] Referring to FIG. 6, the terminal performs a cell selection procedure for one or more cells (S610). Specifically, the terminal performs signal strength measurement to find a suitable cell for receiving frequency priority, etc., through System Information Block (SIB) information, etc. When the terminal finds a suitable cell, the terminal can obtain various information, such as access barring information for the cell, frequency priority of surrounding cells, and slice priority, through messages such as SIB1, SIB2, etc.
[0095] The terminal performs a cell reselection procedure for one or more cells (S620). Specifically, through the information received via step S610, the terminal can perform a new measurement of the cell to form the actual RRC connection. For example, if there are multiple cells with sufficiently high signal strengths based on frequency priority information, the terminal can preferentially select the cell with the relatively high priority frequency to perform the RRC connection procedure.
[0096] In particular, regarding access prevention, the terminal can perform a Unified Access Control process based on the Access Class and Application type among the information received through the above S610 step.
[0097] The terminal performs a Random Access Channel (RACH) procedure for the cell re-selected in step S620 (S630). That is, the terminal can transmit a preamble related to random access to the cell. The signaling may be named Message 1 (Msg 1) or Physical Random Access Channel (PRACH).
[0098] If the PRACH transmitted from the terminal to the network is successfully delivered without error, the base station notifies the terminal that the corresponding preamble has been successfully delivered via message 2 (Msg 2) (S640). At this time, Msg 2 may be named Random Access Response (RAR). The RAR may include an index value transmitted via the preamble. Additionally, Msg 2 may include uplink resource allocation information for the terminal to transmit message 3 (Msg 3) to the base station. Msg 3 may be an RRC establishment message upon initial access, or an RRC re-establishment message transmitted after RLF (Radio Link Failure) recovery. In the example of FIG. 6, the message may be an RRC re-establishment message.
[0099] Based on the information regarding uplink resources received via Msg 2, the terminal constructs an RRC re-establishment request message and transmits it to the base station (S650). Subsequently, if the network determines that the message from step S650 has been successfully delivered to the base station and that there are no issues with the content, the base station transmits an RRC re-establishment message to the terminal (S660). The terminal confirms that it will proceed by restoring the Access Stratum (AS) security, etc., allowed through step S660, by transmitting an RRC re-establishment completion message to the network (S670).
[0100] For example, access control can be applied by classifying it into an access barring factor and an access barring time based on the access level or access class and the type of application.
[0101] Regarding the access prohibition factor, when access to a terminal or application type of the corresponding access class is required based on the set factor, the terminal generates a random value, and whether access is prohibited is determined probabilistically based on the random value. For example, if the prohibition factor is p75 (75%), access prohibition occurs with a 75% probability, and if access prohibition occurs, the RACH process cannot proceed. Specifically, the access prohibition factor is determined by a network, etc., as a specific value between 0 and 1, and the terminal selects a random value between 0 and 1. If the value selected by the terminal is smaller than the access prohibition factor determined by the network, the terminal connects to the network; otherwise, the terminal can wait for the next transmission opportunity.
[0102] The access denial time may refer to the delay between the occurrence of the access denial and the next access attempt. For example, the access denial time may be calculated as (0.7+0.6*rand)*(uac-Barring Time)(seconds). Here, rand is a random value uniformly distributed within the range from 0 to 1, and uac-Barring Time may refer to the average time between an access attempt being blocked in an access denial check for the same access category and a new access attempt being performed.
[0103] Meanwhile, problems can arise due to background traffic in places where a large number of users utilize communication services, such as subways or shopping malls. Many users in subways or shopping malls may not actually be using their devices; in other words, the screens of many devices may be turned off. Even in such cases, some non-essential background traffic, such as updates from internal applications, may occur, and the device generating this traffic may attempt to restore the connection through an RRC re-establishment process. At this time, the traffic generated by these connection restoration attempts may cause a degradation in communication quality based on issues such as RACH failures for users who are actually using their devices, such as playing games or watching YouTube. To resolve this problem, a method is required to appropriately block access to background traffic from devices that are not actually in use.
[0104] FIG. 7 illustrates another example of an RRC re-establishment procedure performed by a terminal according to one embodiment of the present specification.
[0105] Referring to FIG. 7, the terminal performs a SIB reception procedure with a base station (S710). Here, the SIB may include information instructing a ban on access to packets having a low priority, that is, information regarding a ban on access based on low priority packets. For example, the information may include the priority per packet or per packet type, information regarding the value of the priority for which the ban on access is instructed, etc. In step S710, the base station may instruct the execution of a ban on access to packets having a low priority (in this specification, the operation is referred to as a ban on access based on low priority packets) through the SIB. The terminal may determine whether to perform the ban on access based on the information. The information may include one or more of the following information.
[0106] - Low-priority packet-based access denial indicator: The network can use the above indicator to instruct base stations to execute access denial for low-priority packets in response to situations where many people gather.
[0107] - Indicator for the type of packet with low priority: The above information is an indicator indicating the type of packet with low priority and may include one or more of the following information.
[0108] -- Packet type information: The above information may indicate the type of traffic, such as background traffic, update traffic, etc.
[0109] -- Traffic pattern information: The above information may indicate a traffic pattern. For example, the above information may include information such as the traffic transmission cycle, transmission duration, and packet non-transmission duration.
[0110] - High-priority application identifier / slice identifier: The above information may be used to indicate that, even in the case of low-priority packets, low-priority packet-based access denial actions are not performed if the packet is involved in communication through a specific application or a specific network slice. For example, an application identifier and / or slice identifier may be included in the above information.
[0111] The terminal performs an access prohibition operation for packets with low priority, that is, a low priority packet-based access prohibition operation (S720). Here, for example, a filtered packet may be transmitted to the AS layer (e.g., RRC / PDCP / RLC / MAC / PHY layer) through the terminal's Application / NAS (Non Access Stratum) layer. As another example, along with the filtering of the packet to the AS layer through the Application / NAS layer, a mark / identifier / indicator indicating that the packet has low priority may be included in the packet and transmitted. Here, the NAS layer refers to a layer for signaling between the terminal and a core network, such as an AMF (Access and Mobility Management Function), rather than between the terminal and the base station. The NAS protocol structure will be described later.
[0112] If access to the packet is permitted in step S720, the terminal transmits a preamble or Msg 1 (PRACH) to the base station (S730). If the PRACH transmitted from the terminal to the network is successfully delivered without error, the base station transmits Msg 2 (RAR) to the terminal (S740). Through step S740, the terminal can be notified that the corresponding preamble has been successfully delivered to the base station. At this time, the RAR may include an index value transmitted via the preamble. Additionally, the RAR may include information for allocating uplink resources for the terminal to transmit Msg 3 to the base station. Here, Msg 3 may be an RRC establishment message upon initial access or an RRC re-establishment message after RLF recovery.
[0113] Based on the information about the uplink resource received via Msg 2, the terminal constructs an RRC re-establishment message and transmits it to the base station (S750). If the network determines that the RRC re-establishment message is successfully delivered to the base station and there are no issues with the content, the base station transmits an RRC re-establishment completion message to the terminal (S760).
[0114] FIG. 8 illustrates an example of a low-priority packet-based access prohibition operation according to one embodiment of the present specification.
[0115] When a terminal receives an SIB from a base station, the terminal can obtain information regarding low-priority packet-based access prohibition included in the SIB. For example, the information may include priority per packet or per packet type, information regarding the priority value at which access prohibition is indicated, etc. The terminal transmits the information regarding low-priority packet-based access prohibition to the application / NAS layer (S810). The information regarding low-priority packet-based access prohibition may include at least one of the following information.
[0116] - Low Priority Packet-Based Access Denial Indicator: The indicator can inform the NAS / Application Layer that the terminal has received a request from the network for low priority packet-based access denial. Through this, the terminal can perform filtering of packets with low priority.
[0117] - Information regarding the types of packets with low priority: The above information may be used to instruct the NAS / application layer regarding traffic patterns / types that the network intends to prohibit. Through this, packets with low priority can be distinguished through traffic matching. The above information may include at least one of the following.
[0118] -- Packet type information: The above information may indicate the type of traffic, such as background traffic or update traffic. For the packet type indicated by the above information, the terminal may insert / add a low priority marker to the packet corresponding to the above packet type.
[0119] -- Traffic pattern information: The above information may refer to a specific traffic pattern. For example, the above information may include information such as the traffic transmission period, transmission duration, and packet non-transmission duration. The terminal may insert / add a low priority marker for packets having the traffic pattern indicated by the above information.
[0120] The terminal performs packet marking based on the information obtained in step S810 (S820). Here, the packet marking may include the operation of inserting / adding a marker to the packet to identify low-priority packets. For example, the marker may include one of the following information.
[0121] - Low-priority packet on marker information: The above information may indicate that only low-priority packets are generated for the service associated with the packet. Here, through the above information, information signaling the start of processing of low-priority packets may be transmitted to the RRC layer. Alternatively, packet marking may be performed on PDCP packets along with the above information.
[0122] - Low-priority packet off marker information: The above information may indicate that the service associated with the packet has entered an active state. In other words, the above information may indicate that only high-priority packets are generated for the service associated with the packet. Here, the above information may be transmitted to the AS layer, such as the RRC layer. Alternatively, packet marking may be performed on PDCP packets along with the above information.
[0123] In other words, the terminal can determine whether to insert a marker into a packet based on the information obtained in step S810. At this time, the marker may be one of first information indicating that only low-priority packets are generated (or exchanged) for the service associated with the packet, or second information indicating that only high-priority packets are generated for the service associated with the packet. Here, the marker may be information interpreted at the RRC layer, PDCP layer, or other AS layers.
[0124] The terminal performs an access prohibition procedure related to the service transmitting the packet (S830). In step S830, the access prohibition operation may include an operation in which the terminal determines whether to transmit a preamble to the base station based on at least one of the low-priority packet-based access prohibition related information and the marker.
[0125] As an example of the above access prohibition procedure, the terminal may determine whether to insert a marker for a packet (at the AS layer). The terminal may coordinate packet transmission to the AS layer based on an access prohibition factor based on the verification / detection of low-priority packet-on marker information. As another example, the terminal may perform a delay before packet transmission to the AS layer based on an access prohibition time based on the verification / detection of low-priority packet-on marker information. Here, for example, the time during which the delay is performed may be a time calculated as (0.7 + 0.6 * rand) * (uac - Barring Time) (seconds). Alternatively, the two methods described above may be applied in combination. In this case, information regarding the access prohibition factor and the timer indicating the access prohibition time may be transmitted by the base station to the terminal. For example, information regarding the access prohibition factor and the timer indicating the access prohibition time may be transmitted through step S810. As another example of the above access prohibition procedure, the terminal may stop the access prohibition or transmit Msg 1 to the base station based on the verification / detection of low-priority packet off marker information. Here, if no marker is inserted, the terminal may not perform a low-priority packet-based access prohibition operation. If the terminal does not perform a low-priority packet-based access prohibition operation for the packet, the terminal may discard the packet without transmitting it.
[0126] When the terminal checks the marker, the terminal can determine whether the application identifier / slice identifier / access type (or access type) is high. Here, if the application identifier / slice identifier / access type is low, the terminal may not perform a low-priority packet-based access prohibition operation. If the terminal does not perform a low-priority packet-based access prohibition operation for the packet, the terminal may not transmit the packet and may discard the packet.
[0127] If the application identifier / slice identifier / access type is high, the terminal can check the access prohibition factor. Here, if the value selected by the terminal is greater than the access prohibition factor, that is, if it fails to pass the check of the access prohibition factor, the terminal performs a delay during the access prohibition time.
[0128] If the value selected by the terminal is smaller than the access prohibition factor, that is, if it passes the inspection of the access prohibition factor, the terminal transmits Msg 1 to the base station (S840). That is, the terminal that is not prohibited from accessing through step S830 transmits Msg 1 to the base station. Since the transmission step of Msg 1 is as described above in FIG. 6 and / or FIG. 7, a redundant description is omitted.
[0129] FIG. 9 illustrates an example of a NAS protocol structure according to one embodiment of the present specification.
[0130] FIG. 9 defines three sub-layers for 5GS services. Referring to FIG. 9, the NR or E-UTRA AS sub-layer can provide services to the 5GMM (5GS mobility management) sub-layer. The 5GMM sub-layer can provide services to entities of the 5GCM (5GS connection management) sub-layer. The 5GMM sub-layer may include a single 5GMM entity. The 5GCM sub-layer may include a 5GSM entity. The 5GSM entity can provide services to a QoS flow control (QFC) entity and utilize the services of the 5GMM sub-layer. The QFC entity can hide the concept of radio resources that can be enabled, disabled, or suspended while the 5GS context is active. If the terminal's uplink data needs to be transmitted and the 5GS radio resources are disabled or suspended, the QFC can notify the 5GMM.
[0131] FIG. 10 is a flowchart of an example of a communication method performed by a terminal according to an embodiment of the present specification.
[0132] Referring to FIG. 10, the terminal obtains information regarding low priority packet-based access prohibition from a base station (S1010). Here, the information regarding low priority packet-based access prohibition may be transmitted via system information. Additionally, the information regarding low priority packet-based access prohibition may include access prohibition factor information and access prohibition timer information per packet (or packet type). Furthermore, the information regarding low priority packet-based access prohibition may include at least one of the following information.
[0133] - Low-priority packet-based access denial indicator: The network can use the above indicator to instruct base stations to execute access denial for low-priority packets in response to situations where many people gather.
[0134] - Indicator for the type of packet with low priority: The above information is an indicator indicating the type of packet with low priority and may include one or more of the following information.
[0135] -- Packet type information: The above information may indicate the type of traffic, such as background traffic or update traffic.
[0136] -- Traffic pattern information: The above information may indicate a traffic pattern. For example, the above information may include information such as the traffic transmission cycle, transmission duration, and packet non-transmission duration.
[0137] - High-priority application identifier / slice identifier: The above information may be used to indicate that, even in the case of low-priority packets, low-priority packet-based access denial actions are not performed if the packet is involved in communication through a specific application or a specific network slice. For example, an application identifier and / or slice identifier may be included in the above information.
[0138] Meanwhile, the terminal may insert the low-priority packet marker into the packet based on the information regarding the low-priority packet-based access prohibition. The marker may be one of the following two types.
[0139] - Low-priority packet on marker information: The above information may indicate that only low-priority packets are generated for the service associated with the packet. Here, through the above information, information signaling the start of processing of low-priority packets may be transmitted to the RRC layer. Alternatively, packet marking may be performed on PDCP packets along with the above information.
[0140] - Low-priority packet off marker information: The above information may indicate that the service associated with the packet has entered an active state. In other words, the above information may indicate that only high-priority packets are generated for the service associated with the packet. Here, the above information may be transmitted to the AS layer, such as the RRC layer. Alternatively, packet marking may be performed on PDCP packets along with the above information.
[0141] The terminal performs an access prohibition operation based on the low priority packet-based access prohibition information and the low priority packet marker (S1020). Here, the access prohibition operation may include an operation to determine whether the terminal transmits a preamble to the base station based on the low priority packet-based access prohibition information, and a marker identification operation.
[0142] With respect to an example of FIG. 10, the configurations, technical features, and / or methods described in this specification through FIG. 1 to 9 may be combined and applied within the scope that they are not incompatible with each other. Accordingly, redundant descriptions are omitted.
[0143] FIG. 11 illustrates a terminal and a network node in which an embodiment of the present specification is implemented. The terminal of FIG. 11 may include a user device and / or a Network Controlled Repeater (NCR). Additionally, the network node of FIG. 11 may include an NCR.
[0144] Referring to FIG. 11, the terminal (1000) includes a processor (1010), a memory (1020), and a transceiver (1030). The processor (1010) may be configured to implement the functions, processes, and / or methods described herein. Layers of a wireless interface protocol may be implemented in the processor (1010).
[0145] The memory (1020) is connected to the processor (1010) and stores various information for operating the processor (1010). The transceiver (1030) is connected to the processor (1010) and transmits a wireless signal to a network node (1050) or receives a wireless signal from the network node (1050).
[0146] The network node (1050) includes a processor (1060), memory (1070), and a transceiver (1080). In this embodiment, the network node (1050) may be a node of a non-terrestrial network and may include an artificial satellite that performs a wireless access procedure according to the present specification. Alternatively, in this embodiment, the network node (1050) may be a node of a terrestrial network and may include a base station that performs a wireless access procedure according to the present specification.
[0147] The processor (1060) may be configured to implement the functions, processes, and / or methods described herein. Layers of the wireless interface protocol may be implemented in the processor (1060). A memory (1070) is connected to the processor (1060) and stores various information for operating the processor (1060). A transceiver (1080) is connected to the processor (1060) and transmits a wireless signal to a terminal (1000) or receives a wireless signal from the terminal (1000).
[0148] The processor (1010, 1060) may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The memory (1020, 1070) may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. The transceiver (1030, 1080) may include a baseband circuit for processing radio frequency signals. When the embodiment is implemented in software, the above-described technique may be implemented as a module (process, function, etc.) that performs the above-described function. The module may be stored in the memory (1020, 1070) and executed by the processor (1010, 1060). The memory (1020, 1070) may be inside or outside the processor (1010, 1060) and may be connected to the processor (1010, 1060) by various well-known means.
[0149] In the exemplary system described above, methods that can be implemented according to the features of the present invention described above have been described based on flowcharts. For convenience, the methods have been described as a series of steps or blocks; however, the claimed features of the present invention are not limited to the order of the steps or blocks, and some steps may occur with other steps in a different order or simultaneously with those described above. Furthermore, those skilled in the art will understand that the steps shown in the flowcharts are not exclusive, and that other steps may be included, or that one or more steps of the flowcharts may be omitted without affecting the scope of the present invention.
[0150] Various embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof. In the case of implementation by hardware, it may be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), general processors, controllers, microcontrollers, microprocessors, etc.
[0151] The scope of the present invention includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that enable operations according to the methods of various embodiments to be executed on a device or computer, and a non-transitory computer-readable medium on which such software or instructions, etc. are stored and which are executable on a device or computer. Examples of computer-readable media include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Examples of program instructions include machine code, such as that produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The hardware devices described above may be configured to operate as at least one software module to perform the operations of the present invention, and vice versa.
[0152] The methods according to the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. A computer-readable medium may include program instructions, data files, data structures, etc., either individually or in combination. The program instructions recorded on the computer-readable medium may be those specifically designed and configured for the present invention, or they may be those known and available to those skilled in the art of computer software. The operation of the method according to an embodiment of the present invention may be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device in which information that can be read by a computer system is stored. Additionally, the computer-readable recording medium may be distributed across networked computer systems, allowing computer-readable programs or code to be stored and executed in a distributed manner.
[0153] Some aspects of the invention have been described in the context of a device, but may also be described according to a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described according to a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one of the most important method steps may be performed by such a device.
[0154] In the embodiments, a programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described herein. In the embodiments, the field-programmable gate array may operate with a microprocessor to perform one of the methods described herein. Generally, it is preferable that the methods be performed by some hardware device.
[0155] The exemplary methods of the present invention are described as a series of operations for clarity of description, but this is not intended to limit the order in which the steps are performed, and if necessary, each step may be performed simultaneously or in a different order. To implement the method according to the present invention, additional steps may be included in addition to the steps exemplified, steps excluding some steps and including the remaining steps, or steps excluding some steps and including additional steps.
[0156] The various embodiments of the present invention are not intended to list all possible combinations but are intended to explain representative aspects of the invention, and the matters described in the various embodiments may be applied independently or in combination of two or more.
[0157] Although the present invention has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the invention without departing from the spirit and scope of the invention as described in the following claims.
[0158] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to be implemented as a device, and the technical features of the device claims of this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to be implemented as a method. Moreover, the embodiments described in this specification may be combined within a range that is not mutually incompatible.
Claims
Claim 1 A method performed by a terminal in a wireless communication system, wherein the terminal obtains information regarding a low priority packet-based access barring from a base station, and performs an access barring operation based on the information regarding the low priority packet-based access barring and a low priority packet marker, wherein the information regarding the low priority packet-based access barring includes a type indicator indicating the type of a low priority packet, and the terminal inserts the low priority packet marker into a packet based on the information regarding the low priority packet-based access barring, and the access barring operation includes an operation in which the terminal determines whether to transmit a random access preamble to the base station. Claim 2 A method according to claim 1, wherein the information related to low priority packet-based access prohibition includes at least one of an access prohibition indicator indicating that a low priority packet-based access prohibition operation is performed, an application / slice identifier for an application / slice having a high priority, access prohibition factor information, and access prohibition timer information, and wherein the type indicator includes at least one of packet type information and traffic pattern information. Claim 3 A method according to paragraph 2, wherein when the terminal determines whether to transmit a random access preamble to the base station, the terminal determines whether the low priority packet marker exists, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is of the first type, the terminal determines whether the application / slice identifier is high, and based on the fact that the application / slice identifier is determined to be high, the terminal determines whether the factor value indicated by the access prohibition factor information is greater than a value arbitrarily selected by the terminal, and based on the fact that the factor value is greater than a value arbitrarily selected by the terminal, the terminal transmits the random access preamble to the base station, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is of the second type, the terminal transmits the random access preamble to the base station. Claim 4 A method according to claim 3, wherein the terminal does not perform the access prohibition operation based on the determination that the low priority packet marker does not exist or that the application / slice identifier is not high, and the terminal performs an access delay based on the access prohibition timer information based on the determination that the factor value is smaller than a value arbitrarily selected by the terminal. Claim 5 A method according to claim 1, wherein in response to the random connection preamble, the terminal receives a random connection response from the base station. Claim 6 A method according to claim 5, wherein, based on receiving the random connection response, the terminal transmits a message to the base station for the re-establishment of RRC (Radio Resource Control). Claim 7 A method according to claim 1, characterized in that the information regarding the low priority packet-based access prohibition is transmitted via system information. Claim 8 A device comprising: one or more memory storing instructions; one or more transceivers; and one or more processors connecting the one or more memory and the one or more transceivers, wherein the one or more processors execute the instructions to obtain information regarding low priority packet-based access barring from a base station, and perform an access barring operation based on the information regarding low priority packet-based access barring and a low priority packet marker, wherein the information regarding low priority packet-based access barring includes a type indicator indicating the type of a low priority packet, and the terminal inserts the low priority packet marker into a packet based on the information regarding low priority packet-based access barring, and the access barring operation includes an operation in which the terminal determines whether to transmit a random access preamble to the base station. Claim 9 A device according to claim 8, wherein the information related to low priority packet-based access prohibition includes at least one of an access prohibition indicator indicating that a low priority packet-based access prohibition operation is performed, an application / slice identifier for an application / slice having a high priority, access prohibition factor information, and access prohibition timer information, and wherein the type indicator includes at least one of packet type information and traffic pattern information. Claim 10 An apparatus according to claim 9, wherein when the terminal determines whether to transmit a random access preamble to the base station, the terminal determines whether the low priority packet marker exists, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is a first type, the terminal determines whether the application / slice identifier is high, and based on the fact that the application / slice identifier is determined to be high, the terminal determines whether the factor value indicated by the access prohibition factor information is greater than a value arbitrarily selected by the terminal, and based on the fact that the factor value is greater than a value arbitrarily selected by the terminal, the terminal transmits the random access preamble to the base station, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is a second type, the terminal transmits the random access preamble to the base station. Claim 11 A device according to claim 10, characterized in that, based on the determination that the low priority packet marker does not exist or that the application / slice identifier is not high, the terminal does not perform the access prohibition operation, and based on the determination that the factor value is smaller than a value arbitrarily selected by the terminal, the terminal performs an access delay based on the access prohibition timer information. Claim 12 A device according to claim 8, characterized in that, in response to the random connection preamble, the terminal receives a random connection response from the base station. Claim 13 A device according to claim 12, characterized in that, based on receiving the random connection response, the terminal transmits a message to the base station for RRC (Radio Resource Control) re-establishment. Claim 14 A device according to claim 8, characterized in that the information regarding the low priority packet-based access prohibition is transmitted via system information. Claim 15 A computer-readable medium comprising at least one instruction based on execution by at least one processor included in a terminal, wherein the terminal is configured to obtain information regarding low priority packet-based access barring from a base station, and is configured to perform an access barring operation based on the information regarding low priority packet-based access barring and a low priority packet marker, wherein the information regarding low priority packet-based access barring includes a type indicator indicating the type of a low priority packet, and the terminal inserts the low priority packet marker into a packet based on the information regarding low priority packet-based access barring, and the access barring operation includes an operation in which the terminal determines whether to transmit a random access preamble to the base station. Claim 16 A recording medium characterized in that, in paragraph 15, the information related to low priority packet-based access prohibition includes at least one of an access prohibition indicator indicating that a low priority packet-based access prohibition operation is performed, an application / slice identifier for an application / slice having a high priority, access prohibition factor information, and access prohibition timer information, and the type indicator includes at least one of packet type information and traffic pattern information. Claim 17 A recording medium characterized in that, in paragraph 16, when the terminal determines whether to transmit a random access preamble to the base station, the terminal determines whether the low priority packet marker exists, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is of the first type, the terminal determines whether the application / slice identifier is high, and based on the fact that the application / slice identifier is determined to be high, the terminal determines whether the factor value indicated by the access prohibition factor information is greater than a value arbitrarily selected by the terminal, and based on the fact that the factor value is greater than a value arbitrarily selected by the terminal, the terminal transmits the random access preamble to the base station, and based on the fact that the low priority packet marker exists and the type of the low priority packet marker is of the second type, the terminal transmits the random access preamble to the base station. Claim 18 A recording medium characterized in that, in claim 17, the terminal does not perform the access prohibition operation based on the determination that the low priority packet marker does not exist or that the application / slice identifier is not high, and the terminal performs an access delay based on the access prohibition timer information based on the determination that the factor value is smaller than a value arbitrarily selected by the terminal. Claim 19 A recording medium characterized in that, in the 15th paragraph, the terminal receives a random connection response from the base station in response to the random connection preamble, and based on receiving the random connection response, the terminal transmits a message to the base station for the re-establishment of RRC (Radio Resource Control). Claim 20 A recording medium characterized in that, in paragraph 15, the above-mentioned low-priority packet-based access prohibition information is transmitted via system information.
