Method for controlling urban aerial mobility (UAM) identification (ID) and capability of terminal in wireless communication system and apparatus therefor

Abstract

A method by which a terminal performs cell camping, according to some embodiments of the present specification, may comprise: receiving, from a base station, first camping information regarding cell camping permission, second camping information regarding whether or not a cell is reserved, and system information including a first urban aerial mobility (UAM) identification (ID) regarding UAM cell camping; on the basis that the first camping information is set to the cell camping permission and the second camping information is set to reservation, performing a cell camping procedure for UAM on the basis that the first UAM ID matches a second UAM ID of the terminal; and performing a terrestrial cell camping procedure on the basis that the first UAM ID does not match the second UAM ID.

Description

Method for controlling UAM (URBAN AERIAL MOBILITY) ID IDENTIFICATION and capability of a terminal in a wireless communication system and device therefor

[0001] This specification relates to a method for controlling UAM (Urban Aerial Mobility) ID Identification) and capability of a terminal in a wireless communication system, and more particularly, to a technology for setting the UAM capability and UAM ID of a terminal so that it can access a UAM reserved cell or a ground cell.

[0002] Urban Air Mobility (UAM), also known as short-distance urban mobility, is an aerial vehicle that takes off from the ground, travels to its destination, and then lands there. Recently, new services based on this UAM system have emerged.

[0003] For example, UAM could provide transportation services, such as taxis, via vehicles flying hundreds of meters in the air. Such services provided via UAM in the air, rather than on the ground, could have a different wireless communication environment than those on the ground.

[0004] When a passenger's terminal boarding a UAM on the ground attempts to connect to a UAM-only cell in the sky, or when a terminal operating in the sky attempts to connect to a cell that only ground terminals can connect to, a problem may arise where the terminal cannot connect to the cell depending on the status of the passenger's terminal.

[0005] The technical problem to be achieved by the present specification includes providing a method and a device therefor for performing cell access by controlling the terminal state so that a terminal of a UAM passenger can more efficiently access (camp) a UAM cell in the sky and access a cell for a ground terminal when the UAM passenger comes down to the ground.

[0006] This specification is not limited to the technical problems described above, and other technical problems can be inferred from some embodiments of this specification.

[0007] In one aspect of the present disclosure, a method for a terminal to perform cell access in a wireless communication system is provided. The method comprises: receiving system information including first access information regarding cell access permission, second access information regarding whether a cell is reserved, and a first UAM (Urban Aerial Mobility) ID (UAM Identification) regarding UAM cell access from a base station; and, based on the first access information being set to cell access permission and the second access information being set to reservation: performing a cell access (camping) procedure for UAM based on a matching between the first UAM ID and the second UAM ID of the terminal; and performing a terrestrial cell access procedure based on a mismatch between the first UAM ID and the second UAM ID.

[0008] In another aspect of the present disclosure, a terminal for performing cell access in a wireless communication system is provided. The terminal comprises: a transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations including: receiving system information including first access information regarding cell access permission from a base station, second access information regarding whether a cell is reserved, and a first UAM (Urban Aerial Mobility) ID (UAM Identification) regarding UAM cell access; and based on the first access information being set to cell access permission and the second access information being set to reservation: performing a cell access (camping) procedure for UAM based on a matching between the first UAM ID and a second UAM ID of the terminal, and performing a terrestrial cell access procedure based on a mismatch between the first UAM ID and the second UAM ID.

[0009] In another aspect of the present disclosure, a computer-readable storage medium is provided. The storage medium stores at least one program code comprising instructions that, when executed, cause at least one processor to perform operations, the operations including: receiving system information including first access information regarding cell access permission from a base station, second access information regarding whether a cell is reserved, and a first UAM (Urban Aerial Mobility) ID (UAM Identification) regarding UAM cell access; and, based on the first access information being set to cell access permission and the second access information being set to reservation: performing a cell access (camping) procedure for UAM based on a matching between the first UAM ID and the second UAM ID of the terminal, and performing a terrestrial cell access procedure based on a mismatch between the first UAM ID and the second UAM ID.

[0010] In each aspect of the present specification, based on the second UAM ID of the terminal being unset, the method may further include: transmitting a second UAM ID change request to the UAM APP (UAM Application) server, receiving a second UAM ID change response including UAM ID information from the UAM APP server, and setting the second UAM ID of the terminal based on the received UAM ID information.

[0011] In each aspect of the present specification, the terminal may further include transmitting a UAM boarding signal to a UAM APP (UAM Application) server; and receiving a response signal regarding the UAM boarding signal from the UAM APP server.

[0012] In each aspect of the present specification, based on the UAM Capability of the terminal being UAM-unsupported: transmitting a first UAM capability change request to the UAM APP (UAM Application) server, receiving a first UAM capability change response including UAM capability information from the UAM APP server, and setting the UAM capability of the terminal to support based on the received UAM capability information; and based on the UAM capability of the terminal being UAM-supported: continuing to perform the UAM cell access procedure.

[0013] In each aspect of the present specification, the terminal may further include connecting to the UAM reserved cell based on the RRC (Radio Resource Control) state, wherein the terminal may be connected to the UAM reserved cell in a handover manner based on the RRC state being RRC_CONNECTED, and may be connected to the UAM reserved cell in a cell selection or reselection manner based on the RRC state being RRC_IDLE.

[0014] In each aspect of the present specification, the method may further include: transmitting a UAM disembarkation signal to the UAM APP server by the terminal; receiving a response signal regarding the UAM disembarkation signal from the UAM APP server; transmitting a second UAM capability change request to the UAM APP server based on the UAM capability of the terminal being UAM support; receiving a second UAM capability change response including the UAM capability information from the UAM APP server; setting the UAM capability of the terminal to not support based on the received UAM capability information; and performing an access procedure for a ground cell based on the UAM capability of the terminal being UAM not support.

[0015] According to some embodiments of the present specification, when a terminal connects to a cell, if the cell to which the terminal is trying to connect is a UAM-only cell, the terminal can be enabled to support UAM, and if the cell is a ground-only cell, the terminal can be enabled to not support UAM, so that when a UAM passenger's terminal moves between the air and the ground, the terminal can be enabled to connect to a cell flexibly.

[0016] If the UAM cell is a reserved cell, the UAM ID can be set so that only specific terminals can access it.

[0017] Even if there is a cell that only terminals supporting UAM can access, connection from ground terminals can be blocked, preventing unnecessary handovers.

[0018] Additionally, even passengers with terminals that do not support UAM can receive UAM services in the sky by changing the UAM capability.

[0019] The technical effects of this specification are not limited to the effects described above, and other technical effects can be inferred from some embodiments of this specification.

[0020] The drawings attached to this specification are intended to provide an understanding of the specification, illustrate various embodiments of the specification, and together with the description of the specification serve to explain the principles of the specification.

[0021] Figure 1 is a drawing for explaining UAM (Urban Aerial Mobility) service.

[0022] FIG. 2 is a diagram illustrating an example of a network architecture in a 5G (5th generation mobile communications) NR (New Radio) system.

[0023] FIG. 3 is a schematic diagram illustrating a process in which a passenger's terminal on board a UAM moves between the ground and the sky according to some embodiments of the present specification.

[0024] Figure 4 is a diagram schematically illustrating an existing procedure for a terminal to connect to a cell searched.

[0025] FIG. 5 is a diagram schematically illustrating an overall procedure for a terminal to connect to a UAM dedicated cell based on a 4G (4th generation mobile communications) system according to some embodiments of the present specification.

[0026] FIG. 6 is a diagram schematically illustrating an overall procedure for a terminal to connect to a UAM dedicated cell based on a 5G system according to some embodiments of the present specification.

[0027] FIG. 7 is a diagram schematically illustrating a process for changing settings for UAM capabilities hard-coded into a terminal to connect to a UAM-only cell or a cell for terrestrial terminals only, according to some embodiments of the present specification.

[0028] FIG. 8 is a diagram schematically illustrating a process in which a terminal changes related UAM settings according to UAM capability information received through a UAM APP (UAM Application) server in order to access a UAM-only cell or a cell for terrestrial terminals only, according to some embodiments of the present specification.

[0029] FIG. 9 is a diagram schematically illustrating a process for controlling settings related to UAM-ID (UAM Identity) and UAM capability information for a terminal to access a UAM-only cell or a cell for terrestrial terminals only, according to some embodiments of the present specification.

[0030] FIG. 10 is an example schematically illustrating a process in which a terminal performs a cell access procedure according to embodiments of the present specification.

[0031] FIG. 11 is another example schematically illustrating a process in which a terminal performs a cell access procedure according to embodiments of the present specification.

[0032] FIG. 12 is a diagram schematically illustrating the configuration of a base station and a terminal applied to cell access according to some embodiments of the present specification.

[0033] Exemplary implementations of the present disclosure are 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 implementations of the present disclosure and is not intended to represent the only possible implementations according to the present disclosure. The detailed description below includes specific details to provide a thorough understanding of the present disclosure. However, it will be apparent to one of ordinary skill in the art that the present disclosure may be practiced without these specific details.

[0034] In various examples herein, " / " and "," should be interpreted as indicating "and / or". For example, "A / B" can mean "A and / or B". Furthermore, "A, B" can mean "A and / or B". Furthermore, "A / B / C" can mean "at least one of A, B, and / or C". Furthermore, "A, B, C" can mean "at least one of A, B, and / or C".

[0035] Hereinafter, embodiments of the present specification will be described in detail one by one.

[0036] Figure 1 is a drawing for explaining UAM (Urban Aerial Mobility) service.

[0037] Referring to Figure 1, UAM service provides taxi-like transportation via vehicles flying 300 to 600 meters above the ground. It can also refer to a transportation system that uses aerial vehicles to move people within urban areas. Ground-based transportation has raised concerns about traffic congestion and noise pollution. UAM services, which provide services via aerial vehicles, are emerging as a means to address these issues.

[0038] The range of radio waves transmitted from base stations on the ground can differ from that in the air due to objects of varying heights, such as buildings and vehicles. Therefore, UAM services provided in the air may experience a different wireless communication environment than on the ground.

[0039] FIG. 2 is a diagram illustrating an example of a network architecture in a 5G (5th generation mobile communications) NR (New Radio) system.

[0040] The NR system network is largely composed of a next generation radio access network (NG-RAN) and a next generation core (NGC) network.

[0041] Referring to FIG. 2, the next-generation wireless access network is composed of base stations (gNBs) that provide termination of user plane protocols (e.g., SDAP, PDCP, RLC, MAC, PHY) and control plane protocols (e.g., RRC, PDCP, RLC, MAC, PHY) for user equipment (UE). The gNBs are interconnected via interfaces. For example, the gNB is connected to a core network node having an access and mobility management function (AMF) via an N2 interface, which is one of the interfaces between the gNB and a GC, and to a core network node having a user plane function (UPF) via an N3 interface, which is another of the interfaces between the gNB and the next-generation core network. The AMF and the UPF may be implemented by different core network devices, or may be implemented by a single core network device. In the RAN, signal transmission / reception between the gNB and the UE is performed via a wireless interface. For example, in RAN, signal transmission / reception between base stations and terminals is performed via physical resources (e.g., radio frequency (RF)). In contrast, in core networks, signal transmission / reception between base stations (gNBs) and network functions (e.g., AMF, UPF) can be performed via physical connections (e.g., optical cables) between core network nodes or logical connections between core network functions, rather than via radio interfaces.

[0042] FIG. 3 is a schematic diagram illustrating a process in which a passenger's terminal on board a UAM moves between the ground and the sky according to some embodiments of the present specification.

[0043] UAM is an aerial vehicle that takes off from the ground, flies to its destination, and then lands there. Operating in the air, rather than on the ground, UAM can connect to cells in the sky and communicate with base stations while in flight.

[0044] The present invention is not limited to UAM, but can also be applied to unmanned aerial vehicles (UAVs) such as UAVs. The invention described herein will be described using UAM as an example.

[0045] A cell refers to the area covered by a single base station. It can be used solely for ground-based terminals, airborne terminals, or both. Cells used solely for airborne terminals are called UAM-only cells or UAM cells. Cells used for both ground-based and airborne terminals are called general cells.

[0046] Users can board a UAM on the ground with a terminal, take off, move in the sky, and then land on the ground.

[0047] Referring to Figure 3, it depicts a UAM atop a vertiport taking off, operating in the air, and then landing on a vertiport on the ground. The terminal on the ground may or may not support UAM. Depending on the terminal's UAM capabilities, it may or may not be able to connect to a specific cell.

[0048] In other words, from before boarding UAM until disembarking from UAM, passengers may need to connect to at least one of the following: a cell that only UAM-supporting terminals can connect to, a cell that only non-UAM-supporting terminals can connect to, and a cell that both UAM-supporting and non-UAM-supporting terminals can connect to.

[0049] Therefore, the settings for the UAM capability of the terminal must be able to change flexibly as the terminal moves between cells.

[0050] For example, a user on the ground can board a UAM with a terminal that does not support UAM. Before the UAM takes off, the user can change the terminal's UAM settings to support UAM and then take off.

[0051] When a terminal takes off into the air while supporting UAM by changing the UAM settings, it can connect to a UAM-only cell by performing a UAM-only cell connection procedure for terminals in the air.

[0052] A terminal connected to a cell may need to move from its current cell to another while moving through the air. This is called a handover.

[0053] A handover can mean moving from one UAM-only cell to another, from a UAM-only cell to a cell exclusively for terrestrial terminals, or from a UAM-only cell to a regular cell. Cell movement of a terminal is not limited to these.

[0054] Handover can be performed when the terminal is in the RRC_Connected state. The RRC_Connected state can also refer to the state when the terminal is connected to a specific cell. The terminal can perform procedures to connect to a specific cell while in the RRC_Idle state, and upon connecting to the cell, it can enter the RRC_Connected state.

[0055] UAM can land on the ground from the sky. On the ground, passengers may need to access cells that are only accessible to non-UAM-supporting terminals. In other words, they may need to access cells exclusively for ground-based terminals. In this case, the terminal's UAM settings may need to be changed to a non-UAM-supporting state. The invention described herein proposes a method for dynamically changing the terminal's UAM capability settings so that the terminal can connect to a UAM-only cell, a cell exclusively for ground-based terminals, or a general cell, depending on the situation.

[0056] According to one embodiment of the present specification, a method for changing a setting of a UAM capability of a terminal is presented as follows.

[0057] 1) How to change the settings for UAM capability on the terminal itself when UAM capability is hardcoded in the terminal.

[0058] 2) A method for setting UAM capabilities by receiving information about UAM capabilities to be set from a UAM APP server.

[0059] Figure 4 is a diagram schematically illustrating an existing procedure for a terminal to connect to a cell searched.

[0060] Cell connection of a terminal may also be referred to as cell camping.

[0061] The cell access process for a terminal varies depending on whether the network is 4G or 5G. Drawing 4(a) illustrates the cell access process for a terminal in a 4G system, and Drawing 4(b) illustrates the cell access process for a terminal in a 5G system.

[0062] Specifically, cell connection is performed through the following process. Referring to Drawing 4(a)(b),

[0063] 1) The terminal searches for a cell to connect to through cell search (410).

[0064] 2) Receive MIB (Master Information Block) (420) and SIB1 (System information block type 1) (430) information including access information for the cell found from the base station.

[0065] 3) It is checked from MIB (420) or SIB1 information (430) whether the cell found by the terminal is a cell to which access is prohibited (Cell Barred) (440).

[0066] 4) If the cell is barred from connection, the terminal terminates the connection procedure for the cell and searches for another cell to connect to (450).

[0067] 5) If the cell is not barred from access (Not Barred), the terminal obtains other system information from MIB or SIB1 (460).

[0068] 6) Check whether the cell meets the cell selection criteria of the terminal (470).

[0069] 7) If the cell meets the cell selection criteria of the terminal, the terminal connects (camps) to the cell (480).

[0070] More specifically, the terminal searches for a cell expected to be accessible within a supportable frequency range (410). The terminal may transmit a cell access request signal to the base station. For example, the cell access request signal may be a Random Access Channel (RACH) signal.

[0071] When a cell is found, the base station receives MIB (Master Information Block) (420) and SIB1 (System Information Block Type 1) (430) messages. The MIB contains the most basic parameters required for a terminal to access a cell. SIB1 contains information related to the terminal's cell access. The MIB and SIB1 can also be considered system information.

[0072] Whether the cell searched by the terminal is an accessible cell can be confirmed through the Cell Barred information included in the MIB or SIB1. In the case of a 4G network, this can be confirmed by receiving Cell Barred information through SIB1 as shown in the drawing (a), and in the case of a 5G network, this can be confirmed by receiving Cell Barred information through the MIB as shown in the drawing (b). Cell Barred information can include access prohibition information (Barred) that prohibits cell access and access permission information (Not Barred). If there is no information, it can be regarded as access prohibition information (Barred).

[0073] If the Cell Barred information received by the terminal is access prohibited (Barred), access to the corresponding cell is considered to be prohibited for a certain period of time, and the terminal stops the cell access process and searches for another cell (450).

[0074] If the Cell Barred information is Access Allowed (Not Barred), the terminal obtains other system information from SIB1 (460) and checks whether the terminal satisfies the criteria for selecting a cell (470).

[0075] If the cell does not satisfy the criteria, the terminal searches for a new cell again, and if it satisfies the criteria, it completes the connection to the cell (480).

[0076] Depending on whether the network is 4G or 5G, the difference in the cell access process is the location where the cell barred information is determined to be a barred cell. As mentioned, in 4G, the cell barred information is determined through SIB1 (440), and in 5G, the cell barred information is determined through MIB (431) to determine whether the cell searched by the terminal is an accessible cell.

[0077] The existing process according to FIG. 4 has the problem that it is difficult to distinguish whether the cell searched by the terminal is for an airborne terminal or a ground-based terminal, and even if it is an airborne cell, it cannot prevent access to a ground-based cell. Therefore, a method is required to distinguish whether the searched cell is a UAM-only cell for airborne terminals only, and to enable airborne terminals to access the UAM-only cell.

[0078] FIG. 5 is a diagram schematically illustrating an overall procedure for a terminal to connect to a UAM dedicated cell based on a 4G system according to some embodiments of the present specification.

[0079] 1) The terminal searches for a cell to connect to through cell search (510).

[0080] 2) Receive MIB (Master Information Block) (520) and SIB1 (System information block type 1) (530) messages containing access information (Cell Barred) for a cell found from a base station.

[0081] 3) The terminal checks whether the cell is barred from access from the SIB1 (Cell Barred information) (540).

[0082] 4) If the Cell Barred information is Barred and the terminal has UAM capability, the UAM Cell Barred information is checked from SIB1 (551).

[0083] 5) If the UAM Cell Barred information of the cell is access permitted (Not Barred), other system information is obtained from SIB1 (570).

[0084] 6) Check whether the cell meets the cell access criteria set by the terminal (580).

[0085] 7) If the cell satisfies the cell selection criteria, the terminal connects (camps) to the UAM-only cell (590).

[0086] More specifically, the terminal searches for a cell that is expected to be accessible within the supportable frequency (510).

[0087] Terminals may include both UAM-supported and non-UAM-supported general terminals. UAM-supported terminals can access UAM-only cells, as well as general cells accessible to both UAM-supported and non-UAM-supported general terminals. However, UAM-supported terminals may not be able to access cells that are only accessible to non-UAM-supported general terminals.

[0088] A cell may include a cell that can only be accessed by terminals that support UAM, a cell that can be accessed by both terminals that support UAM and general terminals that do not support UAM, and a cell that can only be accessed by general terminals that do not support UAM.

[0089] The terminal transmits a cell access request signal to the base station. For example, the cell access request signal may be a RACH (Random Access Channel) signal.

[0090] Receives MIB (Master Information Block) (520) and SIB1 (System information block type 1) (530) messages containing access information for cells found from a base station.

[0091] The above SIB1 may include only Cell Barred information, or may include both Cell Barred information and UAM Cell Barred information.

[0092] The base station can transmit both Cell Barred information and UAM Cell Barred information if the cell that the terminal is trying to connect to is a cell that only terminals that support UAM can connect to.

[0093] As another example, if the cell to which the terminal is attempting to connect is a cell to which both terminals supporting UAM and general terminals not supporting UAM can connect, the base station may transmit both Cell Barred information and UAM Cell Barred information, or may transmit only Cell Barred information.

[0094] As another example, the base station can transmit both Cell Barred information and UAM Cell Barred information if the cell to which the terminal is attempting to connect is a cell that can only be accessed by general terminals that do not support UAM.

[0095] Whether the above cell is a UAM-only cell can be determined based on Cell Barred information and UAM Barred information.

[0096] The terminal verifies the Cell Barred information of the cell found through search (540). In the case of a 4G system, Cell Barred information can be verified by receiving it via SIB1. Cell Barred information can include access prohibition information (Barred) that prohibits cell access and access permission information (Not Barred).

[0097] If the Cell Barred information received by the terminal is Access Allowed (Not Barred), unlike the existing procedure, the terminal reports that the searched cell is not a UAM-only cell and can perform a general cell access procedure as shown in Fig. 4.

[0098] If the Cell Barred information received by the terminal is access prohibited (Barred), the terminal continues the cell access procedure, unlike the existing procedure of FIG. 4.

[0099] Only terminals that support UAM can access UAM-only cells. Terminals that do not support UAM stop the UAM-only cell access procedure and search for a new cell to access (560).

[0100] A terminal supporting UAM checks UAM Cell Barred information via the received SIB1 (551). If the UAM Cell Barred information indicates access is prohibited (Barred), the connection process is halted, and the terminal searches for a new UAM-dedicated cell to connect to.

[0101] If the UAM Cell Barred information is "Not Barred," it is confirmed that the cell searched by the terminal is a UAM-only cell, the terminal obtains separate system information through SIB1 (570), and checks whether the cell satisfies the cell access criteria (580). If the criteria are not met, the terminal terminates the cell access procedure for a new cell access and performs cell search again. If the criteria are met, the cell access is performed, thereby completing the UAM-only cell access procedure (590).

[0102] In other words, a UAM-only cell can be defined as having Cell Barred information that prohibits access (Barred), and UAM Cell Barred information that allows access (Not Barred).

[0103] Additionally, terminals that can access UAM-only cells may be terminals with UAM capabilities. Terminals with UAM capabilities can also be referred to as terminals that support UAM.

[0104] The difference from the conventional cell access process illustrated in FIG. 4 is that access to a UAM-only cell is possible according to the UAM Cell Barred information even when the Cell Barred information (540) is access prohibited (Barred), and that UAM capability information (550) is separately checked so that only terminals with UAM capability can access the UAM-only cell.

[0105] In the conventional cell access process in a 4G system illustrated in FIG. 5(a), if the Cell Barred information is Barred, the cell is determined to be unreachable and the terminal searches for another cell. However, in the invention according to the present specification illustrated in FIG. 5, the cell access process continues when the Cell Barred information is Barred.

[0106] FIG. 6 is a diagram schematically illustrating an overall procedure for a terminal to connect to a UAM dedicated cell based on a 5G system according to some embodiments of the present specification.

[0107] The difference between the procedure for a terminal to connect to a UAM-only cell based on a 4G system and the procedure for connecting to a UAM-only cell based on a 5G system is whether Cell Barred information is checked through MIB or SIB1.

[0108] In a 4G system, the terminal can check Cell Barred information through SIB1, and in a 5G system as shown in Fig. 6, the terminal can check Cell Barred information through MIB.

[0109] The terminal can check UAM Cell Barred information through SIB1 for both 4G and 5G systems.

[0110] Specifically, it proceeds through the following process.

[0111] 1) The terminal searches for a cell to connect to through cell search (610).

[0112] 2) The terminal receives MIB information including access information (Cell Barred) for the cell found from the base station (620).

[0113] 3) The terminal checks whether the found cell is a cell to which access is prohibited through Cell Barred information (630).

[0114] 4) Based on the terminal having UAM capability, the terminal receives SIB1 including UAM Cell Barred information from the base station (641).

[0115] 5) If the UAM Cell information is access permitted (Not Barred) (642), the terminal obtains other system information from SIB1 (670).

[0116] 6) Check whether the cell meets the cell access criteria set by the terminal (680).

[0117] 7) If the cell satisfies the cell selection criteria, the terminal connects (camps) to the UAM-only cell (690).

[0118] In FIG. 7 and below, a method for changing the settings for the UAM capability of a terminal to connect to a UAM-only cell in the air or a cell for a ground terminal according to some embodiments of the present specification is described.

[0119] FIG. 7 is a diagram schematically illustrating a process for changing settings for UAM capabilities hard-coded into a terminal to connect to a UAM-only cell or a cell for terrestrial terminals only, according to some embodiments of the present specification.

[0120] The process for a terminal with hardcoded UAM capability to connect to a UAM-only cell or a general cell proceeds as follows.

[0121] 1) A user boards a UAM and transmits a UAM boarding signal to the UAM APP server through an APP installed on the terminal (710).

[0122] 2) The UAM APP server receives the UAM boarding instruction signal transmitted by the terminal and transmits a response signal to the terminal (711).

[0123] 3) If the terminal does not support UAM (720), the UAM capability hard-coded in the terminal is set to support (730).

[0124] 4) If the terminal supports UAM, UAM takes off, and the terminal performs cell selection, reselection, or handover depending on the status to connect to the UAM cell (740).

[0125] 5) When the UAM lands on the ground in the sky, the user transmits a UAM disembarkation signal to the UAM APP server through the APP installed on the terminal (750).

[0126] 6) The UAM APP server receives the UAM disembarkation signal transmitted by the terminal and transmits a response signal to the terminal (751).

[0127] 7) A terminal whose UAM capability was set to support in the air changes the UAM capability to not support (760), and performs cell access to a ground cell in the form of cell selection, reselection, or handover depending on the terminal status (770).

[0128] More specifically, users can board UAM with their terminals. The terminals they possess may or may not support UAM capabilities.

[0129] The user's terminal may be a mobile phone, PDA, laptop, etc. It is not limited to any one device.

[0130] Users can board a UAM with their terminal and authenticate their boarding through the app installed on the terminal. Authentication is performed by transmitting a UAM boarding signal from the terminal to the UAM APP server (710). The UAM APP server transmits a response signal to the terminal indicating that it has received the UAM boarding signal from the terminal (711). The user can also check the response signal transmitted by the UAM APP server through the APP.

[0131] If the terminal currently supports UAM, the UAM takes off and the terminal can perform the UAM cell connection procedure in the air.

[0132] However, if the terminal does not currently support UAM, the terminal's UAM capability settings may need to be changed before UAM takes off (720). The current UAM capability may be hard-coded into the terminal. Therefore, the user can change the hard-coded UAM capability into a state that supports UAM (730). The hard-coded UAM capability can also be changed through the APP installed on the terminal. However, the method for changing the hard-coded UAM capability is not limited to this.

[0133] If the setting for the UAM capability of the terminal is supported, the UAM can take off, and in the air, the terminal can perform access (camping) to a cell supporting UAM or a general cell (740).

[0134] Whether the cell that the terminal is trying to connect to is a UAM cell, a general cell, or a cell only for terrestrial terminals can be determined based on information received from the base station as illustrated in FIGS. 5 and 6. For a cell that only terminals supporting UAM can connect to, the CellBarred information related to cell access permission may be Barred, and the UAMCellBarred information related to UAM cell access permission may be Not Barred. For a cell that only terrestrial terminals that do not support UAM can connect to, the CellBarred information may be Not Barred.

[0135] Access to a UAM cell, which only terminals supporting UAM can access in the airspace above the terminal, can be accessed in different ways depending on the RRC_Connection_State of the terminal. The RRC_Connection_State may also be referred to as an RRC state. The RRC state can be an RRC_Idle state or an RRC_Connected state, and the terminal may be in the RRC_Idle state before accessing a cell. A terminal in the RRC_Idle state can access a UAM cell using a selection or reselection method. If the terminal is already accessing a specific cell, the terminal may be in the RRC_Connected state, in which case the terminal can access the UAM cell through a handover method. The handover can be performed by transmitting the terminal's UAM configuration information to the base station.

[0136] When the terminal is in the RRC_Connected state, it can perform various actions according to the base station's policy, such as transmitting its own UAM capability information to the base station at the base station's request or performing a handover.

[0137] As such, UAM cell access methods can vary depending on the RRC status of the terminal. This is not limited to UAM cell access; it can also be applied to cells exclusively for terrestrial terminals or to general cells.

[0138] When a UAM lands on the ground from the sky, the terminal must change the UAM settings so that it can connect to a general cell on the ground or a cell exclusively for ground terminals and communicate. Accordingly, the terminal can transmit an alighting signal to the UAM APP server (750) and receive a response signal from the UAM APP server (751).

[0139] The terminal can change the hardcoded UAM capability setting to unsupported and connect to a ground cell (760). If the UAM capability setting is changed to unsupported, the terminal cannot connect to a UAM cell unless the setting is changed again.

[0140] The terminal can change the setting for UAM capability to unsupported and connect to a cell on the ground by selection, reselection, or handover depending on the RRC status of the terminal (770).

[0141] FIG. 8 is a diagram schematically illustrating a process in which a terminal changes settings for related UAM capabilities according to UAM capability information received by the terminal through a UAM APP server in order to access a UAM-only cell or a cell for terrestrial terminals only, according to some embodiments of the present specification.

[0142] The process by which a terminal sets UAM capabilities through the UAM APP server and connects to a UAM-only cell or a general cell is as follows.

[0143] 1) A user boards a UAM and transmits a UAM boarding signal to the UAM APP server through an APP installed on the terminal (810).

[0144] 2) The UAM APP server receives the UAM boarding instruction signal transmitted by the terminal and transmits a response signal to the terminal (811).

[0145] 3) If the terminal does not support UAM (820), the terminal transmits a UAM Capability Writing Request to the UAM APP server (830).

[0146] 4) The UAM APP server transmits a UAM Capability Writing Response (831) containing UAM capability information and network slice ID information in response to the terminal's request. When the terminal receives information from the UAM server, it sets the UAM capability to UAM support based on the received information.

[0147] 5) If the terminal supports UAM, UAM takes off, and the terminal performs UAM cell access through cell selection, reselection, or handover (840).

[0148] 6) When the UAM lands on the ground from the sky, the user transmits a UAM disembarkation signal to the UAM APP server through the APP installed on the terminal (850).

[0149] 7) The UAM APP server receives the UAM disembarkation signal transmitted by the terminal and transmits a response signal to the terminal (851).

[0150] 8) A terminal whose UAM capability in the air is set to UAM support transmits a UAM Capability Writing Request to the UAM APP server (860).

[0151] 9) The UAM APP server transmits a UAM Capability Writing Response (861) containing UAM capability information and network slice ID information to be changed in response to the terminal's request. When the terminal receives information from the UAM server, it changes the UAM capability setting to UAM non-support based on the received information.

[0152] 10) A terminal that has changed the setting for UAM capability performs cell selection, reselection, or handover according to the terminal status to connect to a ground cell for a ground terminal (870).

[0153] Specifically, users can board UAM with their terminals. The terminals they carry may or may not support UAM.

[0154] A user can board a UAM with a terminal and authenticate their boarding through the app (APP) installed on the terminal (810). Authentication is performed by transmitting a UAM boarding signal from the terminal to the UAM APP server. The UAM APP server transmits a response signal to the terminal indicating that it has received the UAM boarding signal from the terminal (811). The user can also check the response signal transmitted by the UAM APP server through the APP.

[0155] If the terminal currently supports UAM, the UAM takes off and the terminal can perform the UAM cell connection procedure in the air.

[0156] However, if the terminal does not currently support UAM (820), the terminal's UAM capability settings may need to be changed before the UAM takes off. The terminal transmits a UAM Capability Writing Request for the terminal's capabilities to the UAM APP server (830). Upon receiving the request from the terminal, the UAM server transmits a UAM Capability Writing Response including the necessary UAM configuration information and slice ID to the terminal (831). In this specification, the UAM Capability Writing Request and the UAM Capability Writing Response are also referred to as a UAM Capability Change Request and a UAM Capability Change Response, respectively.

[0157] The terminal changes the UAM capability settings based on information received from the UAM APP server. If the terminal's UAM capability is set to UAM support, the terminal performs a UAM cell access procedure (840).

[0158] Access to a UAM cell, which only terminals supporting UAM can access in the airspace above the terminal, can be accessed in different ways depending on the RRC_Connection_State of the terminal. The RRC_Connection_State can be either RRC_Idle or RRC_Connected, and the terminal can be in RRC_Idle before accessing a cell. A terminal in RRC_Idle can access a UAM cell using the Selection or Reselection method. The terminal can be in RRC_Connected when it is already accessing a specific cell, in which case the terminal can access the UAM cell through a handover method.

[0159] When a UAM lands on the ground from the sky, the terminal must change the UAM settings so that it can connect to a general cell on the ground or a cell exclusively for ground terminals and communicate. Accordingly, the terminal can transmit a landing signal to the UAM APP server (850) and receive a response from the UAM APP server (851).

[0160] The terminal transmits a UAM Capability Writing Request regarding terminal capabilities to the UAM APP server (860). Upon receiving the request from the terminal, the UAM server transmits a UAM Capability Writing Response including UAM capability information and a slice ID required by the terminal (861).

[0161] The terminal changes the UAM capability setting to UAM non-support based on the terminal capability information received from the UAM APP server. If the terminal's UAM capability is set to non-support, the terminal performs a cell access procedure for a cell on the ground (870).

[0162] The terminal does not support UAM capability and can connect to a cell on the ground by selection, reselection, or handover depending on the RRC status.

[0163] FIG. 9 is a diagram schematically illustrating a process for controlling settings related to UAM ID (Urban Aerial Mobility Identification) and UAM capability information in order for a terminal according to some embodiments of the present specification to access a UAM-only cell or a cell for terrestrial terminals only.

[0164] The process of setting whether the terminal supports UAM through the UAM APP server and connecting to a UAM reserved cell or general cell is as follows.

[0165] 1) Receive cell barred information (CellBarred), cell reservation information (UAM cell Reserved For Other Use) and UAM ID information from the base station (910).

[0166] 2) The user boards the UAM and transmits a UAM boarding signal to the UAM APP server through the APP installed on the terminal (920).

[0167] 3) The UAM APP server receives the UAM boarding instruction signal transmitted by the terminal and transmits a response signal to the terminal (921).

[0168] 3) If the terminal does not support UAM (922), the terminal transmits a UAM capability change request (UAM Capability Writing Request) to the UAM APP server (923).

[0169] 4) The UAM APP server transmits a UAM Capability Writing Response (924) containing the UAM capability information and network slice ID information requested by the terminal. When the terminal receives information from the UAM server, it sets the UAM capability to UAM support based on the received information and checks whether the UAM ID is set.

[0170] 5) If the terminal does not have a UAM ID set to access the UAM reservation cell (930), the terminal requests UAM ID information to be set from the UAM APP server (940).

[0171] 6) The UAM-APP server transmits the UAM ID information to be set by the terminal (941).

[0172] 7) The terminal that has received UAM ID information sets the UAM ID based on the received information (950).

[0173] 8) Check whether the UAM ID information transmitted by the base station to the terminal matches the UAM ID information set in the terminal (960).

[0174] 9) If the UAM ID matches, the UAM takes off, and the terminal performs UAM reserved cell access through cell selection, reselection, or handover (970).

[0175] 10) When the UAM lands on the ground from the sky, the user transmits a UAM disembarkation signal to the UAM APP server through the APP installed on the terminal (971).

[0176] 11) The UAM APP server receives the UAM disembarkation signal transmitted by the terminal and transmits a response signal to the terminal (972).

[0177] 12) A terminal whose UAM capability in the air is set to UAM support transmits a UAM capability change request (UAM Capability Writing Request) to the UAM APP server (973).

[0178] 13) The UAM APP server transmits a UAM Capability Writing Response (974) containing the UAM configuration information and network slice ID information requested by the terminal. When the terminal receives information from the UAM server, it changes the UAM capability to unsupported based on the received information.

[0179] 14) A terminal that has changed its UAM capability performs cell selection, reselection, or handover according to the terminal status to connect to a cell on the ground for a ground terminal (980).

[0180] Specifically, users can board UAM with their terminals. The terminals they carry may or may not support UAM.

[0181] The terminal can receive MIB and SIB information from the base station, and the MIB or SIB information can include cell access information (Cell Barred), cell reservation information (UAM cell Reserved For Other Use), and UAM ID information (UAM Identity) related to UAM cell access permission (910)(911). Cell reservation means that only specific terminals are allowed to access the cell during a specific time, and other terminals are not allowed to access it.

[0182] Cell connection information includes cell connection prohibited (Barred) and cell connection allowed (Not Barred).

[0183] To utilize cell reservation, the received cell access information (Cell Barred) must be cell access permitted (Not Barred) and the cell reservation information (UAM cell Reserved For Other Use) must be True. In the invention according to this specification, True may also be referred to as reservation or cell reservation. If the cell access information is cell access prohibited (Barred) or the cell reservation information is False, cell reservation cannot be performed on the corresponding cell. In addition, if there is no cell access information, it can be considered Barred, and if there is no cell reservation information, it can be considered False.

[0184] When cell reservation is performed based on information received from the base station, the user can authenticate that he or she has boarded the UAM through the app (APP) installed on the terminal (920). Authentication is performed by transmitting a UAM boarding signal from the terminal to the UAM APP server. The UAM APP server transmits a response signal to the terminal indicating that it has received the UAM boarding signal from the terminal (921). The user can also check the response signal transmitted by the UAM APP server through the APP.

[0185] If the terminal does not currently support UAM (922), the terminal's UAM capability settings may need to be changed before the UAM takes off. The terminal transmits a UAM capability change request (UAM Capability Writing Request) to the UAM APP server (923). Upon receiving the UAM capability change request from the terminal, the UAM server transmits a UAM capability change response (UAM Capability Writing Response) containing the necessary UAM configuration information and slice ID to the terminal (924).

[0186] The terminal changes the UAM capability settings based on information received from the UAM APP server. If the terminal's UAM capability is supported, the terminal checks whether a UAM ID is set (930).

[0187] UAM ID is information used to check whether a specific UAM cell can be accessed through cell reservation.

[0188] If a UAM ID is not set in the terminal, the terminal requests UAM ID information to be set from the UAM-APP server (940). Based on the request, the UAM-APP server transmits UAM ID information to be set by the terminal (941).

[0189] The terminal sets the UAM ID based on the UAM ID information received from the UAM-APP server (950).

[0190] If the UAM-ID set in the terminal matches the UAM-ID information received from the base station, the terminal can access the reserved UAM cell (960). Accordingly, the terminal can continue performing the UAM cell access procedure.

[0191] However, if the UAM ID set on the terminal and the UAM ID information received from the base station do not match, the terminal cannot access the reserved UAM cell even if it supports UAM.

[0192] Alternatively, if the UAM ID information received by the terminal from the UAM-APP server matches the UAM ID information received from the base station, the terminal can perform the UAM cell connection procedure; if they do not match, the terminal may have to search for another cell to connect to, or may have to attempt to connect to a general cell on the ground.

[0193] For example, the UAM ID of a reserved UAM cell in region A may be "1", and the UAM ID of a reserved UAM cell in region B may be "2". If the UAM ID information received by the terminal from the base station is 1, the terminal cannot access the UAM cell in region B.

[0194] Access to the UAM cell is performed in a different manner depending on the RRC status of the terminal based on the matching of the UAM ID set in the terminal and the UAM ID information received from the base station (970).

[0195] When a UAM lands on the ground from the sky, the terminal must change its UAM capability settings to enable communication with a general cell on the ground or a cell specifically for ground terminals. Accordingly, the terminal can transmit a landing signal to the UAM APP server (971) and receive a response from the UAM APP server (972).

[0196] The terminal transmits a UAM Capability Writing Request to the UAM APP server (973). Upon receiving the request from the terminal, the UAM server transmits a UAM Capability Writing Response containing the necessary UAM configuration information, slice ID, and UAM-ID to the terminal (974).

[0197] The terminal changes UAM capabilities, etc., based on information received from the UAM APP server. The terminal may also delete the UAM ID set based on information received from the UAM APP server. If the terminal's UAM capabilities are not supported, the terminal performs a cell access procedure for a cell on the ground (980).

[0198] The terminal can change the setting for UAM capability to unsupported and connect to a cell on the ground by selection, reselection, or handover depending on the RRC status.

[0199] FIG. 10 is an example schematically illustrating a process in which a terminal performs a cell access procedure according to some embodiments of the present specification.

[0200] First, referring to FIG. 10, a method for a terminal supporting UAM (Urban Aerial Mobility) in a wireless communication system to perform a connection procedure through a cell is as follows.

[0201] 1) A process in which the terminal transmits a UAM boarding signal to a UAM APP (Urban Aerial Mobility Application) server and receives a response signal regarding the UAM boarding signal from the UAM APP server (S1010).

[0202] 2) A process of transmitting a first UAM capability change request to the UAM APP server based on the UAM capability of the terminal not supporting UAM, and receiving a first UAM capability change response including UAM capability information from the UAM APP server (S1020);

[0203] 3) A process of setting the UAM capability of the terminal to support based on the received UAM capability information (S1030),

[0204] 4) Based on the UAM capability of the terminal supporting UAM, the process proceeds to the process of performing a connection (camping) procedure for the UAM cell (S1040).

[0205] FIG. 11 is an example schematically illustrating a process in which a terminal performs a cell access procedure according to some embodiments of the present specification.

[0206] Referring to FIG. 11, a method for a terminal supporting UAM (Urban Aerial Mobility) in a wireless communication system to perform a connection procedure through a cell is as follows.

[0207] a) A process for receiving system information including first access information regarding cell access permission from a base station, second access information regarding whether a cell is reserved, and first UAM ID (UAM Identification) regarding UAM (Urban Aerial Mobility) cell access (S1110)

[0208] b) A process for checking information about a reserved cell included in system information, a process for checking whether the first connection information is set to allow cell connection and the second connection information is set to reservation (S1120),

[0209] c) A process for checking whether the UAM-ID received from the base station matches the UAM-ID of the terminal (S1130),

[0210] d) Based on the matching of the first UAM ID and the second UAM ID of the terminal, a cell access (camping) procedure for UAM is performed, and based on the non-match of the first UAM ID and the second UAM ID, a ground cell access procedure is performed (S1140).

[0211] FIG. 12 is a diagram schematically illustrating the configuration of a base station and a terminal applied to cell access according to some embodiments of the present specification.

[0212] The base station (1210) may include a processor (1220), a transceiver (1230), a memory (1240), etc. The processor (1220) may be configured to implement the procedures or inventions proposed in the invention of the present specification. The memory (1240) is connected to the processor (1220) and stores various information related to the operation of the processor (1220). The transceiver (1230) is connected to the processor (1220) and transmits or receives a wireless signal. The terminal (1250) may include a processor (1260), a transceiver (1270), a memory (1280), etc. The processor (1260) may be configured to implement the procedures or inventions proposed in the invention of the present specification. The memory (1280) is connected to the processor (1260) and stores various information related to the operation of the processor (1260). The transceiver (1270) is connected to the processor (1260) and transmits or receives a wireless signal.

[0213] More specifically, the transceiver (1230) of the base station (1210) and the transceiver (1270) of the terminal (1250) can transmit and receive signals or data for the terminal to perform cell access. The transceiver (1230) of the base station (1210) and the transceiver (1270) of the terminal (1250) can include wired or wireless transceivers. The transceiver (1230) of the base station (1210) and the transceiver (1270) of the terminal (1250) can include one or more components that enable communication via a Local Area Network (LAN), a Wide Area Network (WAN), a Value Added Network (VAN), a mobile radio communication network, a satellite communication network, and a combination thereof. Additionally, the base station's transmitter / receiver (1230) and the terminal's transmitter / receiver (1270) can wirelessly transmit and receive data or signals using cellular communication, wireless LAN (e.g., Wi-Fi), etc.

[0214] The memory (1240) of the base station and the memory (1280) of the terminal can store programs for the operations of the processor (1220) of the base station and the processor (1260) of the terminal, respectively, and can temporarily or permanently store input / output data. The memory (1240) of the base station and the memory (1280) of the terminal can include at least one type of storage medium among RAM, SRAM, ROM, EEPROM, PROM, magnetic memory, magnetic disk, optical disk, hard disk type, multimedia card micro type, flash memory type, and card type memory (e.g., SD or XD memory, etc.).

[0215] Additionally, the memory (1240) of the base station and the memory (1280) of the terminal can store various functions and algorithms, and can store various data, applications, software, commands, codes, etc.

[0216] The processor (1220) of the base station and the processor (1260) of the terminal can control the overall operation of the base station (1210) and the terminal (1250), respectively. The processor (1220) of the base station and the processor (1260) of the terminal can execute one or more programs. The processor (1220) of the base station and the processor (1260) of the terminal can refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to some embodiments of the present specification are performed.

[0217] In some embodiments, the processor (1220) of at least one terminal may control a method for the terminal to perform cell access, the method including receiving system information including first access information regarding cell access permission, second access information regarding whether a cell is reserved, and a first UAM (Urban Aerial Mobility) ID (UAM Identification) regarding UAM cell access from a base station, and based on the first access information being set to cell access permission and the second access information being set to reservation: performing a cell access (Camping) procedure for UAM based on a match between the first UAM ID and the second UAM ID of the terminal, and performing a terrestrial cell access procedure based on a mismatch between the first UAM ID and the second UAM ID.

[0218] A method for performing cell access of a terminal according to some embodiments may be implemented as a program code that can be executed by various computer means and recorded on a computer-readable medium. The computer-readable medium may include program commands, data files, data structures, etc., either singly or in combination. The program commands recorded on the medium may be those specially designed and configured for the present specification or may be known and usable by those skilled in the art in computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program commands, such as ROMs, RAMs, and flash memories. Examples of program commands include not only machine language codes but also high-level language codes that can be executed by a computer.

[0219] Additionally, a method for performing cell connection of a terminal according to embodiments may be provided as included in a computer program product.

[0220] A computer program product may include a software program and a computer-readable storage medium on which the software program is stored. For example, a computer program product may include a product in the form of a software program distributed electronically by an electronic device manufacturer or through an electronic marketplace. In this case, the storage medium may be the storage medium of a server or a relay server that stores the program.

[0221] As seen above, the invention of the present specification has the characteristics of 1) being able to dynamically change whether a terminal supports UAM when moving from the ground to the sky or from the sky to the ground, so that it can connect to a UAM cell or a cell for ground terminals only depending on the situation, and 2) allowing only terminals with matching UAM-IDs to connect to a reserved cell.

[0222] As described in detail with respect to the embodiments, the scope of the present specification is not limited thereto, and various modifications and improvements made by those skilled in the art using the basic concepts of the present specification defined in the following claims also fall within the scope of the present specification.

[0223] This specification can be used in various wireless communication environments.

Claims

1. When a terminal performs cell access in a wireless communication system, Receiving system information including first access information regarding cell access permission from a base station, second access information regarding whether a cell is reserved, and first UAM ID (UAM Identification) regarding UAM (Urban Aerial Mobility) cell access; and Based on the above first connection information being set to allow cell connection and the above second connection information being set to reservation: Based on the matching of the first UAM ID and the second UAM ID of the terminal, a cell access (camping) procedure for UAM is performed, Including performing a ground cell access procedure based on the first UAM ID and the second UAM ID not matching, How to connect to a cell phone.

2. In paragraph 1, Based on the second UAM ID of the above terminal not being set: Send a second UAM ID change request to the above UAM APP (UAM Application) server; Receive a second UAM ID change response including UAM ID information from the UAM APP server; Further comprising setting a second UAM ID of the terminal based on the received UAM ID information. How to connect to a cell phone.

3. In paragraph 1, The above terminal transmits a UAM boarding signal to the UAM APP (UAM Application) server; and Further comprising receiving a response signal regarding the UAM boarding signal from the UAM APP server. How to connect to a cell phone.

4. In paragraph 1, Based on the UAM Capability of the above terminal not supporting UAM: Sending a first UAM capability change request to the above UAM APP (UAM Application) server; Receive a first UAM capability change response including UAM capability information from the UAM APP server; Setting the UAM capability of the terminal to support based on the received UAM capability information; and Based on the UAM capability of the above terminal supporting UAM: Further comprising continuing to perform the above UAM cell connection procedure, How to connect to a cell phone.

5. In paragraph 1, Further comprising connecting to the UAM reservation cell based on the RRC (Radio Resource Control) status of the terminal, Connect to the UAM reserved cell in a handover manner based on the RRC state being RRC_CONNECTED, Characterized in that the UAM reserved cell is connected in a cell selection or reselection manner based on the RRC state being RRC_IDLE. How to connect to a cell phone.

6. In paragraph 1, The terminal transmits a UAM disembarkation signal to the UAM APP server; Receive the response signal regarding the UAM disembarkation signal from the UAM APP server; Based on the UAM capability of the above terminal supporting UAM: Send a second UAM capability change request to the above UAM APP server; Receive a second UAM capability change response including the UAM capability information from the UAM APP server; Setting the UAM capability of the terminal to not support based on the received UAM capability information; and Further comprising performing an access procedure for a ground cell based on the UAM capability of the terminal not supporting UAM. How to connect to a cell phone.

7. In a terminal for performing cell access in a wireless communication system, Transmitter and receiver; at least one processor; and At least one computer memory operably connectable to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations; The above actions are: Receiving system information including first access information regarding cell access permission from a base station, second access information regarding whether a cell is reserved, and first UAM ID (UAM Identification) regarding UAM (Urban Aerial Mobility) cell access; and Based on the above first connection information being set to allow cell connection and the above second connection information being set to reservation: Based on the matching of the first UAM ID and the second UAM ID of the terminal, a cell access (camping) procedure for UAM is performed, Including performing a ground cell access procedure based on the first UAM ID and the second UAM ID not matching, Terminal.

8. In paragraph 7, Based on the second UAM ID of the above terminal not being set: Send a second UAM ID change request to the above UAM APP (UAM Application) server; Receive a second UAM ID change response including UAM ID information from the UAM APP server; Further comprising setting a second UAM ID of the terminal based on the received UAM ID information. Terminal.

9. In paragraph 7, The above terminal transmits a UAM boarding signal to the UAM APP (UAM Application) server; and Further comprising receiving a response signal regarding the UAM boarding signal from the UAM APP server. Terminal.

10. In paragraph 7, Based on the UAM Capability of the above terminal not supporting UAM: Sending a first UAM capability change request to the above UAM APP (UAM Application) server; Receive a first UAM capability change response including UAM capability information from the UAM APP server; Setting the UAM capability of the terminal to support based on the received UAM capability information; and Based on the UAM capability of the above terminal supporting UAM: Further comprising continuing to perform the above UAM cell connection procedure, Terminal.

11. In paragraph 7, Further comprising connecting to the UAM reservation cell based on the RRC (Radio Resource Control) status of the terminal, Connect to the UAM reserved cell in a handover manner based on the RRC state being RRC_CONNECTED, Characterized in that the UAM reserved cell is connected in a cell selection or reselection manner based on the RRC state being RRC_IDLE. Terminal.

12. In paragraph 7, The terminal transmits a UAM disembarkation signal to the UAM APP server; Receive the response signal regarding the UAM disembarkation signal from the UAM APP server; Based on the UAM capability of the above terminal supporting UAM: Send a second UAM capability change request to the above UAM APP server; Receive a second UAM capability change response including the UAM capability information from the UAM APP server; Setting the UAM capability of the terminal to not support based on the received UAM capability information; and Further comprising performing an access procedure for a ground cell based on the UAM capability of the terminal not supporting UAM. Terminal.

13. In a computer-readable storage medium, The storage medium stores at least one program code including instructions that, when executed, cause at least one processor to perform operations, The above actions are: Receiving system information including first access information regarding cell access permission from a base station, second access information regarding whether a cell is reserved, and first UAM ID (UAM Identification) regarding UAM (Urban Aerial Mobility) cell access; and Based on the above first connection information being set to allow cell connection and the above second connection information being set to reservation: Based on the matching of the first UAM ID and the second UAM ID of the terminal, a cell access (camping) procedure for UAM is performed, Including performing a ground cell access procedure based on the first UAM ID and the second UAM ID not matching, Storage medium.

14. In paragraph 13, Based on the second UAM ID of the above terminal not being set: Send a second UAM ID change request to the above UAM APP (UAM Application) server; Receive a second UAM ID change response including UAM ID information from the UAM APP server; Further comprising setting a second UAM ID of the terminal based on the received UAM ID information. Storage medium.

15. In paragraph 13, The above terminal transmits a UAM boarding signal to the UAM APP (UAM Application) server; and Further comprising receiving a response signal regarding the UAM boarding signal from the UAM APP server. Storage medium.

16. In paragraph 13, Based on the UAM Capability of the above terminal not supporting UAM: Sending a first UAM capability change request to the above UAM APP (UAM Application) server; Receive a first UAM capability change response including UAM capability information from the UAM APP server; Setting the UAM capability of the terminal to support based on the received UAM capability information; and Based on the UAM capability of the above terminal supporting UAM: Further comprising continuing to perform the above UAM cell connection procedure, Storage medium.

17. In paragraph 13, Further comprising connecting to the UAM reservation cell based on the RRC (Radio Resource Control) status of the terminal, Connect to the UAM reserved cell in a handover manner based on the RRC state being RRC_CONNECTED, Characterized in that the UAM reserved cell is connected in a cell selection or reselection manner based on the RRC state being RRC_IDLE. Storage medium.

18. In paragraph 13, The terminal transmits a UAM disembarkation signal to the UAM APP server; Receive the response signal regarding the UAM disembarkation signal from the UAM APP server; Based on the UAM capability of the above terminal supporting UAM: Send a second UAM capability change request to the above UAM APP server; Receive a second UAM capability change response including the UAM capability information from the UAM APP server; Setting the UAM capability of the terminal to not support based on the received UAM capability information; and Further comprising performing an access procedure for a ground cell based on the UAM capability of the terminal not supporting UAM. Storage medium.

Images