Apparatus and method for preferentially processing random access in wireless communication system

Abstract

The present disclosure is for preferentially processing random access in a wireless communication system, and a method performed by a terminal may include the steps of: transmitting a random access preamble to a base station; receiving a contention resolution message from the base station; transmitting, to a server, a first message including information related to an application that started random access; and receiving, by the terminal, information on a dedicated random access channel (RACH) resource for the application from the base station, wherein the information related to the application includes traffic type information of the application.

Description

Device and method for prioritizing random access in a wireless communication system

[0001] The following description relates to a wireless communication system, and to a device and method for priority handling of random access in a wireless communication system.

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

[0003] In particular, as numerous communication devices demand greater communication capacity, enhanced mobile broadband (eMBB) communication technologies are being proposed, improving upon existing radio access technology (RAT). Furthermore, massive machine type communications (mMTC), which connects multiple devices and objects to provide diverse services anytime and anywhere, as well as communication systems that consider reliability and latency-sensitive services / user equipment (UE), are being proposed. Various technological configurations are being proposed for these solutions.

[0004] The present disclosure relates to a device and method for prioritizing random access in a wireless communication system.

[0005] The present disclosure relates to a device and method for allocating dedicated resources for random access in a wireless communication system.

[0006] The present disclosure relates to a device and method for allocating dedicated resources for random access to a terminal using a delay-sensitive service in a wireless communication system.

[0007] The present disclosure relates to a device and method for determining whether a terminal requires priority processing based on a traffic type of a service and / or application in a wireless communication system.

[0008] The present disclosure relates to a device and method for determining whether a terminal requires priority processing based on a geographical area of ​​the terminal in a wireless communication system.

[0009] The present disclosure relates to a device and method for determining whether priority processing is required based on at least one of a first delay tolerance value according to a traffic type of an application initiating random access in a wireless communication system and a second delay tolerance value according to a geographical area.

[0010] The present disclosure relates to a device and method for determining the validity of a second delay tolerance value according to a geographical area in a wireless communication system.

[0011] The present disclosure relates to a device and method for determining whether to give priority to a terminal based on whether a second delay tolerance value according to a geographical area is valid in a wireless communication system.

[0012] The present disclosure relates to a device and method for determining whether a terminal requires priority processing based on at least one function of an application running in a wireless communication system.

[0013] The present disclosure relates to a device and method for notifying a server of information regarding whether a state requires priority processing in a wireless communication system.

[0014] The present disclosure relates to a device and method for performing random access using dedicated resources allocated for priority processing in a wireless communication system.

[0015] The technical objectives to be achieved in the present disclosure are not limited to those mentioned above, and other technical tasks not mentioned can be considered by a person having ordinary skill in the technical field to which the technical configuration of the present disclosure is applied from the embodiments of the present disclosure described below.

[0016] As an example of the present disclosure, a method performed by a terminal includes the steps of transmitting a random access preamble to a base station, receiving a contention resolution message from the base station, transmitting a first message including information related to an application that initiates random access to a server, and receiving information about a dedicated random access channel (RACH) resource for the application from the base station, wherein the information related to the application may include traffic type information of the application.

[0017] As an example of the present disclosure, a method performed by a base station may include the steps of receiving a random access preamble from a terminal, transmitting a contention resolution message to the terminal, receiving a message requesting priority processing of the terminal from a server, and transmitting information about a dedicated random access channel (RACH) resource for an application initiating random access.

[0018] As an example of the present disclosure, a method performed by a server includes the steps of receiving a first message including information related to an application that initiates random access from a terminal, determining a first delay tolerance value according to a traffic type of the application and a second delay tolerance value according to a geographical area of ​​the terminal based on the first message, and requesting a base station to prioritize processing of the terminal based on a comparison result of the first delay tolerance value and the second delay tolerance value, wherein the first message may include at least one of traffic type information of the application, identification information of the base station, or identification information of the terminal.

[0019] As an example of the present disclosure, a terminal device includes a transceiver and a processor connected to the transceiver, wherein the processor controls to transmit a random access preamble to a base station, receive a contention resolution message from the base station, transmit a first message including information related to an application that initiates random access to a server, and receive information about a dedicated random access channel (RACH) resource for the application from the base station, wherein the information related to the application may include traffic type information of the application.

[0020] As an example of the present disclosure, a base station device includes a transceiver, a processor connected to the transceiver, and the processor is configured to receive a random access preamble from a terminal, transmit a contention resolution message to the terminal, receive a message requesting priority processing of the terminal from a server, and control transmission of information about a dedicated random access channel (RACH) resource for an application to the terminal.

[0021] As an example of the present disclosure, a server device includes a transceiver and a processor connected to the transceiver, wherein the processor receives a first message including information related to an application that initiates random access from a terminal, determines a first delay tolerance value according to a traffic type of the application and a second delay tolerance value according to a geographical area of ​​the terminal based on the first message, and controls a base station to request priority processing of the terminal based on a comparison result of the first delay tolerance value and the second delay tolerance value, wherein the first message may include at least one of traffic type information of the application, identification information of the base station, or identification information of the terminal.

[0022] As an example of the present disclosure, a communication device includes at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, direct operations, the operations including: transmitting a random access preamble to a base station; receiving a contention resolution message from the base station; transmitting a first message to a server, the first message including information related to an application that initiates random access; and receiving information about a dedicated random access channel (RACH) resource for the application from the base station, wherein the information related to the application may include traffic type information of the application.

[0023] As an example of the present disclosure, a non-transitory computer-readable medium stores at least one instruction executable by a processor, the at least one instruction controlling a base station to transmit a random access preamble, to receive a contention resolution message from the base station, to transmit a first message including information related to an application that initiates random access to a server, and to receive information about a dedicated random access channel (RACH) resource for the application from the base station, wherein the information related to the application may include traffic type information of the application.

[0024] The following effects may be achieved by embodiments based on the present disclosure.

[0025] The present disclosure can prevent unnecessary waste of network resources for fast random access in a wireless communication system.

[0026] The effects that can be obtained from the embodiments of the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly derived and understood by those skilled in the art to which the technical configuration of the present disclosure is applied, from the description of the embodiments of the present disclosure below. In other words, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by those skilled in the art from the embodiments of the present disclosure.

[0027] The accompanying drawings are intended to aid in understanding the present disclosure and, together with detailed descriptions, may provide embodiments of the present disclosure. However, the technical features of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. Reference numerals in each drawing may indicate structural elements.

[0028] Figure 1 illustrates an example of a communication system applicable to the present disclosure.

[0029] FIG. 2 illustrates an example of a user equipment (UE) applicable to the present disclosure.

[0030] FIG. 3 illustrates an example of functional separation of a next generation radio access network (NG-RAN) and a 5th generation core (5GC) applicable to the present disclosure.

[0031] FIG. 4 illustrates an example of a general architecture of a 5G (5th generation) system applicable to the present disclosure.

[0032] FIG. 5a and FIG. 5b illustrate examples of a procedure for prioritizing random access according to an embodiment of the present disclosure.

[0033] FIG. 6 illustrates an example of a procedure for performing random access using dedicated resources according to one embodiment of the present disclosure.

[0034] FIG. 7 illustrates an example of a procedure for allocating dedicated resources according to one embodiment of the present disclosure.

[0035] FIG. 8 illustrates an example of a procedure for requesting priority processing according to one embodiment of the present disclosure.

[0036] FIG. 9 illustrates an example of a procedure for acquiring dedicated RACH resources according to one embodiment of the present disclosure.

[0037] FIG. 10 illustrates an example of a procedure for allocating dedicated RACH resources according to one embodiment of the present disclosure.

[0038] FIG. 11 illustrates an example of a procedure for requesting priority processing according to one embodiment of the present disclosure.

[0039] The following embodiments combine components and features of the present disclosure in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, some components and / or features may be combined to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.

[0040] In the description of the drawings, procedures or steps that may obscure the gist of the present disclosure are not described, and procedures or steps that can be understood by a person skilled in the art are also not described.

[0041] Throughout the specification, when a part is said to "comprising" or "including" a component, this does not mean that other components may be included, but rather that other components may be excluded, unless otherwise specifically stated. In addition, terms such as "...part," "...unit," and "module" described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software. In addition, the words "a" or "an," "one," "the," and similar related words may be used in the context of describing the present disclosure (especially in the context of the claims below) to include both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context.

[0042] Embodiments of the present disclosure described herein focus on the data transmission and reception relationship between a base station and a mobile station. Here, the base station is understood as a terminal node of a network that directly communicates with the mobile station. Certain operations described herein as being performed by the base station may, in some cases, be performed by an upper node of the base station.

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

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

[0045] Additionally, a transmitter refers to a fixed and / or mobile node that provides data or voice services, and a receiver refers to a fixed and / or mobile node that receives data or voice services. Therefore, for uplink, a mobile station can be the transmitter, and a base station can be the receiver. Similarly, for downlink, a mobile station can be the receiver, and a base station can be the transmitter.

[0046] Embodiments of the present disclosure are wireless access systems such as IEEE 802.xx system, 3rd Generation Partnership Project (3GPP) system, 3GPP Long Term Evolution (LTE) system, 3GPP 5G (5 th generation) NR (New Radio) system and 3GPP2 system, and in particular, embodiments of the present disclosure may be supported by 3GPP TS (technical specification) 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.321 and 3GPP TS 38.331 documents.

[0047] Furthermore, the embodiments of the present disclosure can be applied to other wireless access systems and are not limited to the aforementioned systems. For example, they can also be applied to systems implemented after the 3GPP 5G NR system, and are not limited to a specific system.

[0048] That is, obvious steps or parts not described in the embodiments of the present disclosure can be explained by referring to the above documents. In addition, all terms disclosed in this document can be explained by the above standard documents.

[0049] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the technical configurations of the present disclosure may be implemented.

[0050] Additionally, specific terms used in the embodiments of the present disclosure are provided to aid in understanding the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.

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

[0052]

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

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

[0055] For terms, abbreviations, and other background technologies that may be used in this document, please refer to the following standard documents published prior to this document. In particular, terms, abbreviations, and other background technologies related to LTE / EPS (Evolved Packet System) can refer to the 36.xxx series, 23.xxx series, and 24.xxx series, and terms, abbreviations, and other background technologies related to NR (new radio) / 5GS (5G system) can refer to the 38.xxx series, 23.xxx series, and 24.xxx series.

[0056] Hereinafter, this specification is described based on the terms defined above.

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

[0058] Some use cases may require optimization across multiple domains, while others may focus on just one Key Performance Indicator (KPI). 5G supports these diverse use cases in a flexible and reliable manner.

[0059] Communication system applicable to the present disclosure

[0060] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present disclosure disclosed in this document may be applied to various fields requiring wireless communication / connectivity (e.g., 5G) between devices.

[0061] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0062] Figure 1 illustrates an example of a communication system applied to the present disclosure.

[0063] Referring to FIG. 1, a communication system (100) applied to the present disclosure includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR, LTE) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (extended reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI (artificial intelligence) device / server (100g). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicles (100b-1, 100b-2) may include unmanned aerial vehicles (UAVs) (e.g., drones). The XR devices (100c) include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. The portable devices (100d) may include smartphones, smart pads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.), etc. The home appliances (100e) may include TVs, refrigerators, washing machines, etc. The IoT devices (100f) may include sensors, smart meters, etc. For example, the base station (120) and the network (130) may also be implemented as wireless devices, and a specific wireless device (120a) may act as a base station / network node to other wireless devices.

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

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

[0066]

[0067] Figure 2 illustrates an example of a UE applicable to the present disclosure.

[0068] Referring to FIG. 2, the UE (200) may include a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0069] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (200) to implement the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipset, logic circuit, and / or data processing device. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator).

[0070] The memory (104) is operatively coupled to the processor (102) and can store various information for operating the processor (102). The memory (104) may include ROM, RAM, flash memory, a memory card, a storage medium, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in the memory (14) and executed by the processor (102). The memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

[0071] A transceiver (106) is operably coupled to the processor (102) and is capable of transmitting and / or receiving radio signals. The transceiver (106) may include a transmitter and a receiver. The transceiver (106) may include baseband circuitry for processing radio frequency signals. The transceiver (106) may control one or more antennas (108) to transmit and / or receive radio signals.

[0072] The power management module (141) can manage the power of the processor (102) and / or the transceiver (106). The battery (142) can supply power to the power management module (141).

[0073] The display (143) can output the results processed by the processor (102). The keypad (144) can receive input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0074] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and can be used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, contact information can be stored on many SIM cards.

[0075] The speaker (146) can output sound-related results processed by the processor (102). The microphone (147) can receive sound-related input to be used by the processor (102).

[0076] In implementations of this specification, a UE may operate as a transmitter in the uplink and as a receiver in the downlink. In implementations of this specification, a base station may operate as a receiver in the uplink and as a transmitter in the downlink. In this specification, a base station may be referred to as a Node B (Node B), an eNode B (eNB), or a gNB, and may not be limited to a specific form.

[0077] In addition, for example, the UE may be implemented in various forms depending on the use case / service. The UE may be composed of various components, devices / parts, and / or modules. For example, each UE may include a communication device, a control device, a memory device, and additional components. The communication device may include a communication circuit and a transceiver. For example, the communication circuit may include one or more processors and / or one or more memories. For example, the transceiver may include one or more transceivers and / or one or more antennas. The control device is electrically connected to the communication device, the memory device, and the additional components, and may control the overall operation of each UE. For example, the control device may control the electrical / mechanical operation of each UE based on a program / code / command / information stored in the memory device. The control device may transmit information stored in the memory device to an external device (e.g., another communication device) via the communication device via a wireless / wired interface, or may store information received from an external device (e.g., another communication device) via the communication device via a wireless / wired interface in the memory device.

[0078] Additional components may be configured in various ways depending on the type of UE. For example, the additional components may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. In addition, the UE is not limited thereto, and may be implemented in the form of a robot (100a in FIG. 1), a vehicle (100b-1 and 100b-2 in FIG. 1), an XR device (100c in FIG. 1), a portable device (100d in FIG. 1), a home appliance (100e in FIG. 1), an IoT device (100f in FIG. 1), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (100g in FIG. 1), a base station (120 in FIG. 1), or a network node. UE can be used in mobile or fixed locations depending on the use case / service.

[0079] The various components, devices / parts, and / or modules of the UE may all be connected to each other via a wired interface, or at least some of them may be connected wirelessly via a communication device. In addition, each component, device / part, and / or module of the UE may further include one or more elements. For example, the control device may be configured by a set of one or more processors. For example, the control device may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory device may be configured by a random access memory (RAM), a dynamic random access memory (DRAM), a read-only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0080]

[0081] 5G system architecture applicable to the present disclosure

[0082] The 5G system is an advanced technology from the 4th generation LTE mobile communication technology. It supports new radio access technology (RAT: Radio Access Technology), extended LTE (eLTE) as an extended technology of LTE (Long Term Evolution), and non-3GPP (e.g., WLAN) access through the evolution or clean-state structure of the existing mobile communication network structure.

[0083] 5G systems are defined as service-based, and the interactions between network functions (NFs) within the architecture for 5G systems can be expressed in two ways as follows.

[0084] - Reference point representation: Represents the interaction between NF services within NFs described by a point-to-point reference point (e.g., N11) between two NFs (e.g., AMF and SMF).

[0085] Service-based representation: Network functions (e.g., AMF) within the control plane (CP) allow other authorized network functions to access their services. This representation also includes point-to-point reference points, if necessary.

[0086] 5GC (5G Core) can include various components, some of which include access and mobility management function (AMF), session management function (SMF), policy control function (PCF), user plane function (UPF), application function (AF), unified data management (UDM), and non-3GPP interworking function (N3IWF).

[0087] The UE connects to the data network via the UPF via the next-generation radio access network (NG-RAN) that includes the gNB. The UE can receive data services via untrusted non-3GPP access points, such as wireless local area networks (WLANs). To connect non-3GPP access points to the core network, an N3IWF may be deployed.

[0088] The N3IWF manages interworking between non-3GPP access and 5G systems. When a UE is connected to a non-3GPP access (e.g., WiFi, also known as IEEE 802.11), it can connect to a 5G system via the N3IWF. The N3IWF performs control signaling with the AMF and connects to the UPF via the N3 interface for data transmission.

[0089] AMF can manage access and mobility in 5G systems. It can also manage non-access stratum (NAS) security. It can also handle mobility in idle states.

[0090] The UPF functions as a gateway for transmitting and receiving user data. A UPF node can perform all or part of the user plane functions of a 4G mobile communications S-GW (serving gateway) and P-GW (packet data network gateway).

[0091] The UPF acts as a boundary between the next generation RAN (NG-RAN) and the core network, and is an element that maintains the data path between the gNB and the SMF. In addition, the UPF acts as a mobility anchor point when the UE moves across the area served by the gNB. The UPF can perform the function of handling PDUs. For mobility within the NG-RAN (e.g., NG-RAN defined after 3GPP Release-15), the UPF can route packets. In addition, the UPF can also act as an anchor point for mobility with other 3GPP networks (e.g., RAN defined before 3GPP Release-15), such as UTRAN (UMTS (universal mobile telecommunications system) terrestrial radio access network), E-UTRAN (evolved-UTRAN), or GERAN (GSM (global system for mobile communication) / EDGE (enhanced data rates for global evolution) radio access network). A UPF may correspond to the termination point of a data interface toward a data network.

[0092] The PCF is a node that controls the operator's policies. The AF is a server that provides various services to UEs. The UDM is a server that manages subscriber information, similar to the HSS (home subscriber server) of 4G mobile communications. The UDM (460) stores and manages subscriber information in a unified data repository (UDR).

[0093] The SMF can perform the function of assigning an IP (Internet protocol) address to the UE. In addition, the SMF can control the PDU (protocol data unit) session.

[0094] For convenience of explanation below, the drawing symbols for AMF, SMF, PCF, UPF, AF, UDM, N3IWF, gNB, or UE may be omitted, and operation may be performed by referring to the matters described in standard documents published prior to this document.

[0095] Figure 3 illustrates an example of functional separation of NG-RAN and 5GC (5th generation core) applicable to the present disclosure.

[0096] Referring to Figure 3, the UE connects to a data network (DN) via a next-generation RAN. The control plane function (CPF) node performs all or part of the functions of the mobility management entity (MME) of 4G mobile communications, and all or part of the control plane functions of the serving gateway (S-GW) and the PDN gateway (P-GW). The CPF node includes the AMF and the SMF.

[0097] The UPF node functions as a gateway through which user data is transmitted and received.

[0098] The authentication server function (AUSF) authenticates and manages UEs. The Network Slice Selection Function (NSSF) is a node for network slicing, as described below.

[0099] The network exposure function (NEF) provides a mechanism to securely expose the services and functions of the 5G core.

[0100] The reference points shown in Fig. 3 are as follows. N1 represents a reference point between the UE and the AMF. N2 represents a reference point between the (R)AN and the AMF. N3 represents a reference point between the (R)AN and the UPF. N4 represents a reference point between the SMF and the UPF. N5 represents a reference point between the PCF and the AF. N6 represents a reference point between the UPF and the DN. N7 represents a reference point between the SMF and the PCF. N8 represents a reference point between the UDM and the AMF. N9 represents a reference point between the UPFs. N10 represents a reference point between the UDM and the SMF. N11 represents a reference point between the AMF and the SMF. N12 represents a reference point between the AMF and the AUSF. N13 represents a reference point between the UDM and the AUSF. N14 represents a reference point between the AMFs. N15 represents a reference point between a PCF and an AMF in a non-roaming scenario, and a reference point between an AMF and a PCF of a visited network in a roaming scenario. N16 represents a reference point between SMFs. N22 represents a reference point between an AMF and an NSSF. N30 represents a reference point between a PCF and an NEF. N33 may represent a reference point between an AF and an NEF, and the entities and interfaces described above may be configured with reference to those described in standard documents published before this document. N58 represents a reference point between an AMF and an NSSAAF. N59 represents a reference point between a UDM and an NSSAAF. N80 represents a reference point between an AMF and an NSACF. N81 represents a reference point between an SMF and an NSACF.

[0101] The radio interface protocol is based on the 3GPP radio access network standard. Horizontally, the radio interface protocol consists of the physical layer, data link layer, and network layer. Vertically, it is divided into the user plane for data information transmission and the control plane for control signaling.

[0102] Protocol layers can be divided into L1 (layer-1), L2 (layer-2), and L3 (layer-3) based on the three lower layers of the open systems interconnection (OSI) standard model, which is widely known in communication systems.

[0103] Below, the present disclosure describes each layer of the wireless protocol. Figure 4 illustrates an example of a general architecture of a 5G (5th generation) system applicable to the present disclosure.

[0104] Referring to FIG. 4, the AS (access stratum) layer may include a physical (PHY) layer, a medium access control layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a radio resource control (RRC) layer, and operations based on each layer may be performed by referring to matters described in standard documents published prior to this document.

[0105]

[0106] Specific embodiments of the present disclosure

[0107] The present disclosure relates to a device and method for prioritizing random access in a wireless communication system. Specifically, the present disclosure relates to a device and method for prioritizing random access of a terminal based on at least one of a disruption tolerance for a traffic type and an expected tolerance within a geographical area in a wireless communication system.

[0108]

[0109] A terminal establishes a connection to a network based on initial access and can receive various services through the network connection. During this process, the terminal may utilize services that are sensitive to disconnection. If a terminal experiences a network disconnection while using a service sensitive to disconnection, a method must be provided to resume or restore the connection within the short time required by the service. However, unconditionally preparing for disconnection of terminals using services sensitive to disconnection can result in waste of wireless network resources. Therefore, appropriate standards and procedures that consider the efficient use of wireless network resources are needed.

[0110] Meanwhile, in next-generation mobile application and service delivery systems, a vast number of applications are expected to generate diverse types of traffic with different volumes, patterns, and characteristics. In other words, traffic may be generated by a vast number of applications in next-generation communication systems. Therefore, when UEs (e.g., UAM (urban air mobility), robots, V2X UEs, etc.) request network resources to meet their traffic needs, specifying a specific application is expected to be impractical from a system control and management perspective.

[0111] Therefore, the present disclosure proposes a simplified method to reduce the control and management burden of the system. In particular, the present disclosure proposes a method that utilizes traffic types and geographic areas to simplify traffic characteristics, such as QoS requirements. Here, QoS requirements may include the need for rapid random access completion. By combining geographic areas with traffic types, the present disclosure can more accurately estimate the traffic characteristics of approximate geographic locations, such as farm areas, factory sites, or general residential areas.

[0112]

[0113] The present disclosure proposes a technology for preferentially reconnecting UEs connected to a satellite gNB and performing tasks that are disruption-tolerant or disruption-sensitive. Specifically, the present disclosure requests priority processing for a UE based on at least one of a disruption tolerance based on a traffic type of a service and / or application and an expected tolerance based on a geographical area, and allocates dedicated resources for random access of the UE based on the priority processing request. This allows the UE to perform fast random access using the dedicated resources when a situation requiring random access occurs. Here, the situation requiring random access may include at least one of a situation in which an RRC connection is disconnected, a situation in which synchronization is misaligned or lost, or a situation requiring a handover. This is merely an example to aid understanding, and the situation requiring random access in the present disclosure is not limited thereto. The satellite gNB may include a satellite onboard gNB (satellite onboard gNB).

[0114] FIGS. 5A and 5B illustrate examples of a procedure for prioritizing random access according to an embodiment of the present disclosure. In FIGS. 5A and 5B , the server (530) may be a non-3GPP entity.

[0115] Referring to FIG. 5A, in step S501, the UE (510) performs initial access to the satellite gNB (520). The UE (510) may transmit a random access preamble according to a type 2 or type 4 random access procedure to the satellite gNB (520) for initial access.

[0116] In step S503, the satellite gNB (520) transmits a contention resolution message to the UE (510). The contention resolution message may include identification information for identifying the UE (510) and satellite gNB identification information. The satellite gNB identification information may include at least one of a gNB ID and a cell ID. The identification information for identifying the UE (510) may include a temporary identifier (e.g., a temporary cell radio network temporary identifier (C-RNTI)).

[0117] In step S505, the UE (510) transmits a message related to an application that initiates random access to the server (530). The message related to the application that initiates random access may include at least one of T1, base station identification information, or UE identification information indicating a service corresponding to an application running on the terminal or a traffic type of a service to be used. The base station identification information may include satellite gNB identification information included in a contention resolution message. The service to be used by the terminal may be determined based on an application running on the terminal. Here, the traffic type of the service may include the traffic type of the application. The application that initiates random access may include an application that drives, starts, initiates, executes, and / or activates a random access procedure.

[0118] In step S507, the server (530) determines an interruption tolerance D1 for traffic type T1. The interruption tolerance D1 may indicate a maximum time value for which connection disconnection is allowed according to the traffic type T1 of the service. The interruption tolerance may be replaced with an interruption tolerance value, a disconnection tolerance value, a first delay tolerance value, a delay value, or other terms having an equivalent technical meaning. According to one embodiment, the interruption tolerance D1 may be determined based on the traffic type T1. For example, the server (530) may determine the interruption tolerance D1 using a specified rule based on the traffic type. As another example, the server (530) may search for an interruption tolerance corresponding to the traffic type T1 in a table of interruption tolerances for each traffic type that is preset or stored, and determine the searched interruption tolerance as the interruption tolerance D1 for the traffic type T1.

[0119] In step S509, the server (530) estimates the expected tolerance E1 within the geographic area. The server (530) can identify the geographic area where the UE (510) is located based on the base station identification information included in the application-related message. The server (530) can estimate the expected tolerance E1 according to the geographic area for the identified corresponding traffic type T1. The expected tolerance E1 can indicate the maximum time value for which connection interruption is allowed for the corresponding traffic type T1 within the geographic area where the UE is located. For example, the expected tolerance E1 can be estimated based on at least one of the pattern of traffic occurring within the geographic area or the geographic area-specific requirements of the corresponding traffic. The expected tolerance can be replaced with the expected interruption tolerance value, the expected interruption tolerance value, the second delay tolerance value, the expected delay value, or other terms having an equivalent technical meaning.

[0120] In step S511, the server (530) compares the expected tolerance E1 and the interruption tolerance D1. In other words, the server (530) can determine whether the expected tolerance E1 based on the geographical area has a value greater than the interruption tolerance D1 based on the traffic type.

[0121] In step S513, the server (530) transmits a response message to the UE (510) based on the comparison result. The response message may include an expected tolerance E1 and an interruption tolerance D1. If the expected tolerance E1 is greater than the interruption tolerance D1, the server (530) may transmit a response message including the expected tolerance E1 and the interruption tolerance D1 to the UE (510). On the other hand, if the expected tolerance E1 is less than or equal to the interruption tolerance D1, the server (530) may terminate the UE priority processing procedure according to an embodiment of the present disclosure.

[0122] In step S515, the UE (510) compares the expected tolerance E1 and the error range e1. The error range e1 indicates the interruption tolerance of the executed application, i.e., the application associated with the service. The error range e1 may be set differently for each application. By comparing the expected tolerance E1 and the error range e1, the UE (510) can determine whether the E1 estimated by the server (530) is valid. If the expected tolerance E1 falls within the error range e1, the UE (510) can determine that the E1 estimated by the server (530) is valid. On the other hand, if the expected tolerance E1 does not fall within the error range e1, the UE (510) can determine that the E1 estimated by the server (530) is invalid.

[0123] In step S517, the UE (510) transmits an indication message to the server (530) based on the comparison result. The indication message may include at least one of a positive indication and a negative indication. The positive indication may include an indication indicating that E1 estimated by the server (530) is valid. The negative indication may be an indication indicating that E1 estimated by the server (530) is invalid. If the expected tolerance E1 falls within the error range e1, the UE (510) may transmit an indication message including a positive indication to the server (530). On the other hand, if the expected tolerance E1 does not fall within the error range e1, the UE (510) may transmit an indication message including a negative indication to the server (530). According to one embodiment, if the expected tolerance E1 is not within the error range e1, the UE (510) may omit the operation of transmitting the indication message to the server (530) or transmit a message that does not include the indication to the server (530).

[0124] In step S519, the server (530) verifies the indication message. For example, the server (530) verifies whether the indication message contains a positive indication or a negative indication.

[0125] At step S521, the server (530) requests the gNB (520) to prioritize the UE (510) based on the confirmation result of the indication message. If the indication message contains a positive indication, the server (530) may transmit a message requesting priority processing for the UE (510) to the satellite gNB (520). On the other hand, if the indication message contains a negative indication, the server (530) may terminate the procedure according to the embodiment of the present disclosure.

[0126] In step S523, the satellite gNB (520) checks the availability for priority processing. For example, the satellite gNB (520) checks whether dedicated resources for a random access channel (RACH) can be allocated to the corresponding UE (510). The dedicated resources may include at least one of a dedicated RACH occasion (RO) or a dedicated preamble. For example, the satellite gNB (520) can check the availability for priority processing by checking whether a dedicated RACH opportunity or a dedicated preamble that can be allocated to the corresponding UE (510) exists. If a dedicated RACH opportunity or a dedicated preamble that can be allocated to the corresponding UE (510) exists, the satellite gNB (520) can determine that priority processing is possible. On the other hand, if a dedicated RACH opportunity or a dedicated preamble that can be allocated to the corresponding UE (510) does not exist, the satellite gNB (520) can determine that priority processing is not possible.

[0127] At step S525, the satellite gNB (520) transmits an acceptance message for the request to the server (530) based on the availability check result for priority processing. The satellite gNB (520) may transmit an acceptance message for the request to the server (530) based on the availability check result determining that priority processing is possible. In other words, the satellite gNB (520) may transmit a message indicating to the server (530) that priority processing for the corresponding UE (510) is possible. On the other hand, if the availability check result determines that priority processing is not possible, the satellite gNB (520) may transmit a rejection message for the request to the server (530). In other words, the satellite gNB (520) may transmit a message indicating to the server (530) that priority processing for the corresponding UE (510) is not possible.

[0128] In step S527, the satellite gNB (520) allocates dedicated resources to the UE (510). The gNB (520) can allocate dedicated resources for the RACH to the UE (510) and transmit information about the allocated dedicated resources. The dedicated resources for the RACH can include at least one of a dedicated RACH opportunity (RO) or a dedicated preamble.

[0129] At step S529, the UE (510) determines whether priority processing is required. The UE (510) may determine whether priority processing is required based on whether a specific function or specific task of an application or service related to the traffic is running. The specific function or specific task may include at least one of a function or task sensitive to connection interruption or a function or task that generates traffic. For example, even if the application related to the traffic is running, if the execution of a specific function that generates the traffic is temporarily suspended, the UE (510) may determine that priority processing is not required. If the application related to the traffic is running and a specific function that generates the traffic is running, the UE (510) may determine that priority processing is required. In one embodiment, whether priority processing is required may be determined by the application layer of the UE (510). This is because the execution of a specific function or specific task can be confirmed at the application layer. The application layer of the UE (510) can determine whether priority processing is required based on whether a specific function or specific task is being executed, and can notify the transport layer of the UE (510) of the determination result.

[0130] If priority processing is not required, at step S531, the UE (510) transmits information to the server (530) indicating that priority processing is not required. The UE (510) can inform the server (530) that priority processing is not currently required. In this case, the server can update information related to whether priority processing is required, and prevent unnecessary waste of network resources.

[0131] If priority processing is required, at step S533, the UE (510) performs random access using dedicated resources. For example, if the connection is disconnected while executing an application or service related to traffic, the UE (510) may perform random access based on at least one of a dedicated RO and a dedicated preamble allocated by the gNB (520). A dedicated RO refers to a specific time interval during which the UE can access the network using the RACH. By performing random access using dedicated resources, the UE (510) can quickly restore the disconnected connection.

[0132] In the embodiment described with reference to FIGS. 5A and 5B, the server (530) may wait for an indication message for a time period based on a designated timer. For example, the server (530) may start a designated timer based on the time at which the response message was transmitted in step S513, and wait for an indication message to be received from the UE (510) until the designated timer expires. If no indication message is received from the UE (510) until the designated timer expires, the server (530) may assume that the UE (510) has omitted the transmission of a negative indication.

[0133] In one embodiment, the interruption tolerance may vary depending on a specific application, which may be specified by at least one of traffic type, gNB identification information, or UE identification information. For example, the gNB ID may correspond to a specific area with specific traffic demands required by a specific human user or robot application, and the UE identification information may indicate the type of UE. For example, the UE identification information may indicate that the UE is a robot using goggles or a video codec for machine (VCM). In this case, the server may specify the application running on the UE (510) based on at least one of the traffic type, gNB identification information, or UE identification information, and determine the interruption tolerance D1 based on the specified application.

[0134]

[0135] FIG. 6 illustrates an example of a procedure for performing random access using dedicated resources according to one embodiment of the present disclosure. FIG. 6 illustrates a method performed by a UE. The UE may include the UE (510) of FIG. 5A and FIG. 5B.

[0136] Referring to FIG. 6, in step S601, the UE transmits a random access preamble. The UE may transmit the random access preamble for initial access to the satellite gNB. In one embodiment, the UE may support a Type 2 random access procedure or a Type 4 random access procedure for initial access. For example, the UE may transmit a message including a random access preamble and a PUSCH payload to the satellite gNB according to a Type 2 random access procedure. In another example, the UE may transmit a message including a random access preamble to the satellite gNB according to a Type 4 random access procedure and receive a random access response message from the satellite gNB. The UE may transmit a scheduled transmission message using a scheduled UL grant in the random access response message.

[0137] In step S603, the UE receives a contention resolution message. The contention resolution message may include satellite gNB identification information. If the contention resolution message is successfully received, the UE may terminate the random access procedure.

[0138] In step S605, the UE transmits a message related to an application initiating random access. The message related to the application initiating random access may include at least one of the traffic type of an application or service running on the UE, base station identification information, or UE identification information. For example, the UE detects the execution of an application generating traffic or the start of a service generating traffic, and identifies the traffic type of the corresponding application or service. The UE may transmit a message to the server including at least one of the identified traffic type, base station identification information, or UE identification information. In this case, the base station identification information may include satellite gNB identification information acquired during the random access procedure.

[0139] At step S607, the UE receives D1 and E1. The UE may receive information from the server regarding D1, which indicates the interruption tolerance for the traffic type, and E1, which indicates the expected interruption tolerance within the geographical area. The geographical area may be determined based on base station identification information. D1 and E1 may be retrieved and / or determined by the server based on the traffic type and / or geographical area.

[0140] At step S609, the UE determines whether E1 falls within the error range. The UE can determine whether the expected tolerance E1 within the geographical area determined by the server falls within the error range e1. The error range e1 may be set differently for each application and / or service.

[0141] If E1 is not within the error range, the UE transmits a negative indication at step S613. If E1 is not within the error range, the UE may determine that the E1 estimated by the server is invalid. The UE may transmit a negative indication to the server indicating that E1 is invalid. In one embodiment, the transmission of the negative indication may be omitted.

[0142] If E1 is within the error range, the UE transmits a positive indication in step S611. If E1 is within the error range, the UE may determine that E1 estimated by the server is valid. A positive indication indicating that E1 is valid may be transmitted to the server.

[0143] In step S615, the UE receives information about dedicated resources. The UE may receive information about dedicated resources for the RACH from the satellite gNB. The information about the dedicated resources for the RACH may include at least one of a dedicated RACH opportunity (RO) or a dedicated preamble.

[0144] At step S617, the UE determines whether priority processing is required. Upon receiving information about dedicated resources, the UE can determine whether priority processing is required. The UE can determine whether priority processing is required based on whether a specific function or task of an application or service related to the traffic is running. If a specific function or task generating traffic is running, the UE may determine that priority processing is required. Conversely, if a specific function or task generating traffic is suspended, the UE may determine that priority processing is not required.

[0145] If priority processing is not required, the UE notifies the server that priority processing is not required at step S619. This is to prevent unnecessary waste of network resources by notifying the server that the UE does not require priority processing.

[0146] If priority processing is required, the UE performs random access using dedicated resources at step S621. The UE may perform random access using dedicated resources based on a connection loss during the execution of an application or service related to the traffic. For example, the UE may perform random access based on at least one of the dedicated RO and dedicated preamble allocated by the satellite gNB, thereby quickly restoring a disconnected connection.

[0147] FIG. 7 illustrates an example of a procedure for allocating dedicated resources according to one embodiment of the present disclosure. FIG. 7 illustrates a method performed by a satellite gNB. The satellite gNB may include the satellite gNB (520) of FIGS. 5A and 5B.

[0148] Referring to FIG. 7, in step S701, the satellite gNB receives a random access preamble. The satellite gNB may receive a random access preamble for initial access from the UE. In one embodiment, the satellite gNB may support a Type 2 random access procedure or a Type 4 random access procedure. For example, the satellite gNB may receive a message including a random access preamble and a PUSCH payload from the UE according to a Type 2 random access procedure. In another example, the satellite gNB may receive a message including a random access preamble from the UE according to a Type 4 random access procedure and transmit a random access response message to the UE. Thereafter, the satellite gNB may receive a scheduled transmission message transmitted using a scheduled UL grant in the random access response message.

[0149] In step S703, the satellite gNB transmits a contention resolution message. The contention resolution message may include satellite gNB identification information. If the UE successfully receives the contention resolution message, the random access procedure may be terminated.

[0150] At step S705, the satellite gNB receives a priority processing request message. The satellite gNB can receive a message from the server requesting priority processing for a terminal.

[0151] In step S707, the satellite gNB determines whether priority processing is possible. For example, the satellite gNB determines whether dedicated resources for RACH are available for the UE requesting priority processing. Dedicated resources may include at least one of a dedicated RACH opportunity (RO) or a dedicated preamble. For example, the satellite gNB can determine whether priority processing is possible by determining whether a dedicated RACH opportunity or a dedicated preamble is available for allocation to the UE.

[0152] If priority processing is possible, the satellite gNB transmits an acceptance message for the request at step S709. If priority processing is confirmed to be possible for the UE, the satellite gNB may transmit an acceptance message for the priority processing request to the server.

[0153] In step S711, the satellite gNB allocates dedicated resources. The satellite gNB may transmit information to the UE regarding at least one of a dedicated RACH opportunity or a dedicated preamble.

[0154] If priority processing is not possible, the satellite gNB sends a rejection message to the request at step S713. If priority processing is determined not to be possible for the UE, the satellite gNB may send a rejection message to the server for the priority processing request.

[0155] FIG. 8 illustrates an example of a procedure for requesting priority processing according to one embodiment of the present disclosure. FIG. 8 illustrates a method performed by a server. The server may include the server (530) of FIGS. 5A and 5B.

[0156] Referring to FIG. 8, in step S801, the server receives a message related to an application initiating random access. The message related to the application initiating random access may include at least one of the traffic type of the application or service running on the UE, base station identification information, or UE identification information.

[0157] In step S803, the server determines the interruption tolerance D1 based on the traffic type. The server can retrieve or determine the interruption tolerance D1, which indicates the maximum time for which connection disruption is permitted, based on the traffic type received from the UE. The server can retrieve the interruption tolerance D1 for the traffic type from a pre-stored table containing information on interruption tolerances for each traffic type, or determine the interruption tolerance D1 for the traffic type based on a specified rule.

[0158] In step S805, the server estimates the expected tolerance E1 based on the geographic area. Based on the base station identification information received from the UE, the server can determine the geographic area in which the UE is located and estimate the expected tolerance within the geographic area for the corresponding traffic type. For example, the server can estimate the expected tolerance E1 for connection interruption for a traffic type by considering the characteristics of the geographic area.

[0159] At step S807, the server determines whether E1 is greater than D1. The server can determine whether the expected tolerance E1 is greater than the interruption tolerance D1 by comparing the interruption tolerance D1 based on the traffic type with the expected tolerance E1 within the geographic area.

[0160] If E1 is greater than D1, in step S809, the server transmits D1 and E1. If the expected tolerance E1 is greater than the interruption tolerance D1, the server may transmit the interruption tolerance D1 determined by the server and the expected tolerance E1 estimated by the server to the UE.

[0161] At step S811, the server receives an indication. The server may receive an indication message from the UE. After transmitting D1 and E1 to the UE, the server may wait for the indication message to be received within a specified time interval. If the indication message is not received within the specified time interval, the server may determine that the expected tolerance E1 estimated by the server is invalid.

[0162] In step S813, the server verifies whether the received indication is a positive indication. The server can verify whether the indication included in the indication message is a positive indication indicating that the expected tolerance E1 is valid, or a negative indication indicating that the expected tolerance E1 is invalid.

[0163] If the received indication is positive, the server transmits a priority processing request message in step S815. If a positive indication indicating that the expected tolerance E1 is valid is received from the UE, the server may transmit a message to the satellite gNB requesting priority processing for the UE.

[0164] In step S817, the server receives the result of the request. The server may receive a result message for the priority processing request message. The result message for the priority processing request message may include an acceptance message indicating that the UE is eligible for priority processing, or a rejection message indicating that the UE is not eligible for priority processing.

[0165] In one embodiment, if the result message for the priority processing request message is an acceptance message, the server may receive a notification message from the UE indicating that priority processing is not required. In this case, the server may determine that a specific function or task generating traffic in the UE has been temporarily suspended and perform at least one function to prevent unnecessary waste of network resources. For example, by sending a priority processing cancellation message for the UE to the satellite gNB, the server may control the release of dedicated resources for the UE.

[0166] FIG. 9 illustrates an example of a procedure for acquiring dedicated RACH resources according to one embodiment of the present disclosure. FIG. 9 illustrates a method performed by a terminal. The terminal may include the UE (510) of FIGS. 5A and 5B and / or the UE (510) of FIG. 6 .

[0167] Referring to FIG. 9, in step S901, the terminal transmits a random access preamble. The terminal transmits the random access preamble to the base station based on a Type 2 or Type 4 random access procedure for initial access. For example, the terminal may transmit a message including a random access preamble and a PUSCH payload to the base station according to a Type 2 random access procedure. As another example, the terminal may transmit a message including a random access preamble to the base station according to a Type 4 random access procedure. In this case, after receiving a random access response message from the base station, the terminal may transmit a scheduled transmission message using a UL grant scheduled in the random access response message.

[0168] In step S903, the terminal receives a contention resolution message. The terminal may receive a contention resolution message including base station identification information from the base station. The base station identification information may include at least one of a gNB ID and a cell ID.

[0169] In step S905, the terminal transmits information related to the application initiating random access. If an application generating traffic for a service is running, the terminal may transmit information about the type of traffic generated by the application to the server. The terminal may also transmit base station identification information and terminal identification information to the server, along with information about the traffic type.

[0170] In step S907, the terminal receives information about dedicated RACH resources. The terminal may receive information about at least one of a dedicated RACH opportunity and / or a dedicated preamble from the base station. When a connection to a service is lost, the terminal can quickly restore the lost connection by performing random access based on the received information about the dedicated RACH resources.

[0171] According to one embodiment, the terminal may further perform at least one operation of the UE described with reference to FIGS. 5A and 5B, and / or FIG. 6.

[0172] FIG. 10 illustrates an example of a procedure for allocating dedicated RACH resources according to one embodiment of the present disclosure. FIG. 10 illustrates a method performed by a base station. The base station may include the satellite gNB (520) of FIGS. 5A and 5B and / or the satellite gNB (520) of FIG. 7.

[0173] Referring to FIG. 10, in step S1001, the base station receives a random access preamble. The base station receives a random access preamble based on a Type 2 or Type 4 random access procedure from the terminal. For example, the base station may receive a message including a random access preamble and a PUSCH payload from the terminal according to a Type 2 random access procedure. As another example, the base station may receive a message including a random access preamble from the terminal according to a Type 4 random access procedure. In this case, the base station may transmit a random access response message to the terminal and then receive a scheduled transmission message based on a scheduled UL grant from the terminal.

[0174] In step S1003, the base station transmits a contention resolution message. The base station may transmit a contention resolution message including base station identification information to the terminal. The base station identification information may include at least one of a gNB ID and a cell ID.

[0175] In step S1005, the base station receives a priority processing request for a terminal. The base station may receive a message from the server requesting priority processing for a specific terminal using a service sensitive to connection interruption. The message requesting priority processing may include a message requesting allocation of dedicated RACH resources to the terminal.

[0176] In step S1007, the base station allocates a dedicated RACH resource to the terminal. The dedicated RACH resource may include at least one of a dedicated RACH opportunity or a dedicated RACH preamble. According to one embodiment, the base station may check whether there are dedicated RACH resources that can be allocated to the terminal. The base station may transmit a response message to the server for a priority processing request based on whether there are dedicated RACH resources that can be allocated to the terminal. If there are no dedicated RACH resources that can be allocated to the terminal, the base station may not allocate a dedicated RACH resource to the terminal and may transmit a message to the server indicating that priority processing of the terminal is not possible.

[0177] According to one embodiment, the base station may further perform at least one operation of the satellite gNB described with reference to FIGS. 5A and 5B, and / or FIG. 7.

[0178] FIG. 11 illustrates an example of a procedure for requesting priority processing according to one embodiment of the present disclosure. FIG. 11 illustrates a method performed by a server. The server may include the server (530) of FIGS. 5A and 5B and / or the server (530) of FIG. 8.

[0179] Referring to FIG. 11, in step S1101, the server receives a message related to an application initiating random access. The server may receive a message from a terminal containing information related to the application initiating random access. The message related to the application initiating random access may include information about the type of traffic generated by the application running on the terminal for service. Additionally, the message related to the application initiating random access may further include at least one of base station identification information and terminal identification information.

[0180] In step S1103, the server compares a first delay tolerance value based on a traffic type and a second delay tolerance value based on a geographic area. The server may determine the first delay tolerance value based on a traffic type included in a message related to an application initiating random access, and estimate the second delay tolerance value based on a geographic area based on base station identification information included in the message related to the application initiating random access. The first delay tolerance value may include an interruption tolerance value D1, and the second delay tolerance value may include an expected tolerance value E1.

[0181] In step S1105, the server requests priority processing based on the comparison result. The server can determine whether priority processing is required for the terminal based on the comparison result of the first delay tolerance value and the second delay tolerance value. If the first delay tolerance value is smaller than the second delay tolerance value, the server determines that priority processing is required for the terminal and can request priority processing for the terminal from the base station. If the first delay tolerance value is greater than or equal to the second delay tolerance value, the server determines that priority processing is not required for the terminal and can not request priority processing for the terminal from the base station.

[0182] According to one embodiment, the server may further perform at least one operation of the server described with reference to FIGS. 5A and 5B, and / or FIG. 8.

[0183] It is clear that the examples of the proposed methods described above can also be considered as a type of proposed methods, as they can be included as one of the implementation methods of the present disclosure. Furthermore, the proposed methods described above can be implemented independently, but they can also be implemented in the form of a combination (or merge) of some of the proposed methods. Information regarding the applicability of the proposed methods (or information regarding the rules of the proposed methods) can be defined by a rule such that the base station notifies the terminal of the application of the proposed methods through a predefined signal (e.g., a physical layer signal or a higher layer signal).

[0184] The present disclosure may be embodied in other specific forms without departing from the technical ideas and essential features described herein. Therefore, the above detailed description should not be construed as limiting in all respects but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are intended to be included within the scope of the present disclosure. Furthermore, claims that do not explicitly cite each other in the claims may be combined to form embodiments or incorporated into new claims through post-filing amendments.

[0185] Embodiments of the present disclosure can be applied to various wireless access systems. Examples of various wireless access systems include the 3rd Generation Partnership Project (3GPP) or 3GPP2 systems.

[0186] The embodiments of the present disclosure can be applied not only to the various wireless access systems described above, but also to all technical fields that utilize these various wireless access systems. Furthermore, the proposed method can also be applied to mmWave and THz communication systems utilizing ultra-high frequency bands.

[0187] Additionally, embodiments of the present disclosure can be applied to various applications of various types of UEs, such as autonomous vehicles, UAMs, and drones.

Claims

1. In the method, A step in which a terminal transmits a random access preamble to a base station; A step in which the terminal receives a contention resolution message from the base station; The step of the terminal transmitting a first message including information related to an application that initiates random access to the server; and The step of the terminal receiving information about a dedicated RACH (random access channel) resource for the application from the base station includes, A method in which information related to the above application includes traffic type information of the above application.

2. In claim 1, The first message further includes at least one of identification information of the base station and identification information of the terminal, The above base station is a method including a satellite base station.

3. In claim 1, A step of receiving a delay tolerance value according to the geographical area where the terminal is located from the server; Further comprising a step of transmitting information related to the validity of the received delay tolerance value to the server, A method in which the validity of the above delay tolerance value is determined based on a comparison result between the above delay tolerance value and a delay tolerance value set for a service corresponding to the above application.

4. In claim 1, A step of determining whether priority processing of the terminal is required based on the information received about the dedicated RACH resource; and Further comprising a step of transmitting information indicating whether priority processing of the terminal is required to the server, A method in which whether priority processing of the above terminal is required is determined based on whether at least one function of the service corresponding to the above application is executed.

5. In claim 1, Further comprising a step of performing a random access procedure using the dedicated RACH resource based on the disconnection of the above service, A method wherein the dedicated RACH resource includes at least one of a dedicated RACH opportunity or a dedicated preamble.

6. In the method, A step in which a base station receives a random access preamble from a terminal; A step in which the base station transmits a contention resolution message to the terminal; A step of receiving a message requesting priority processing of the terminal from the server; and A method comprising the step of transmitting information about a dedicated random access channel (RACH) resource for an application that initiates random access to the terminal.

7. In claim 6, The above contention resolution message includes base station identification information, The above base station is a method including a satellite base station.

8. In claim 6, A step of determining whether there is a dedicated RACH resource that can be allocated to the terminal based on receiving a message requesting priority processing of the terminal; and A method further comprising the step of transmitting a message to the server indicating whether priority processing of the terminal is possible based on whether there is a dedicated RACH resource allocable to the terminal.

9. In the method, A step in which the server receives a first message containing information related to an application that initiates random access from a terminal; A step of determining a first delay tolerance value according to the traffic type of the application and a second delay tolerance value according to the geographical area of ​​the terminal based on the first message; and A step of requesting the base station to prioritize processing of the terminal based on the comparison result of the first delay tolerance value and the second delay tolerance value, A method wherein the first message includes at least one of traffic type information of the application, identification information of the base station, or identification information of the terminal.

10. In claim 9, A method in which the geographical area of ​​the terminal is determined based on the identification information of the base station included in the first message.

11. In claim 9, The step of requesting priority processing of the above terminal is: A step of transmitting at least one of the first delay tolerance value and the second delay tolerance value to the terminal based on the comparison result; A step of receiving information related to the validity of the second delay tolerance value from the terminal; and A method comprising a step of requesting the base station to prioritize processing of the terminal based on information related to the validity.

12. In claim 9, A method further comprising the step of receiving a message from the base station indicating whether priority processing of the terminal is possible.

13. In claim 12, A method further comprising the step of receiving information from the terminal indicating whether priority processing of the terminal is required.

14. In the device, Transmitter and receiver; and A processor connected to the above transmitter and receiver is included, The above processor, Transmit a random access preamble to the base station, Receive a contention resolution message from the base station, Sending a first message containing information related to an application that initiates random access to the server, configured to receive information about dedicated RACH (random access channel) resources for the application from the base station, Information related to the above application, a device including traffic type information of the above application.

15. In the device, Transmitter and receiver; and A processor connected to the above transmitter and receiver is included, The above processor, Receive a random access preamble from the terminal, Send a contention resolution message to the terminal, Receive a message requesting priority processing of the terminal from the server, A device configured to transmit information about dedicated RACH (random access channel) resources for an application that initiates random access to the terminal.

16. In the device, Transmitter and receiver; and A processor connected to the above transmitter and receiver is included, The above processor, Receive a first message containing information related to an application that initiates random access from a terminal, Based on the first message, a first delay tolerance value according to the traffic type of the application and a second delay tolerance value according to the geographical area of ​​the terminal are determined, It is configured to request the base station to prioritize processing of the terminal based on the comparison result of the first delay tolerance value and the second delay tolerance value, A device wherein the first message includes at least one of traffic type information of the application, identification information of the base station, or identification information of the terminal.

17. In communication devices, At least one processor; At least one memory storing instructions that direct operations when executed by at least one processor, The above actions are, A step of transmitting a random access preamble to a base station; A step of receiving a contention resolution message from the base station; A step of transmitting a first message containing information related to an application that initiates random access to the server; and A step of receiving information about a dedicated RACH (random access channel) resource for the application from the base station, Information related to the above application, a communication device including traffic type information of the above application.

18. In a non-transitory computer-readable medium storing at least one instruction, At least one instruction executable by the processor, Transmit a random access preamble to the base station, Receive a contention resolution message from the base station, Sending a first message containing information related to an application that initiates random access to the server, Instructs the base station to receive information about dedicated RACH (random access channel) resources for the application, Information related to the above application, a computer-readable medium including traffic type information of the above application.

Images