Patent Description:
<CIT> discloses a terminal device which performs a process of determining height information, wherein the height information is intricately linked to a first parameter. Subsequently, the terminal device receives comprehensive configuration information from a first network device, encompassing a clear correspondence or mapping between the height information and the aforementioned first parameter. By leveraging the received height information, the terminal device engages in a determination process to identify and ascertain the specific first parameter that corresponds to the terminal device based on the given height information.

<CIT> discloses (see paragraphs [<NUM>] to [<NUM>]) the "so-called time to trigger (TTT)" or "distance to trigger (DTT)" as possible conditions for performing tracking area update coming along with a random access procedure toward a neighboring cell.

In NR, the network may configure the configurations related to NAS, such as IMS, network-slice, during the registration procedure for a registration area, and most NAS parameters may be applicable for the registration area.

The UE may initiate the registration process when it needs to change some settings, such as slice(s), other than when the UE detects that the UE is entering a tracking area that is not in the list of previously registered tracking areas with AMF.

In other words, for the aerial UE, if some settings related to NAS in the UE need to be updated based on the height, the UE can perform the registration process. However, if the network needs to update the NAS configuration based on its height, there is no process to inform the network (NAS) of the height of the UE. The network may need height information to provide an aerial UE-specific service. Therefore, it is necessary to inform the network (NAS) that the height of the UE has changed.

Therefore, studies for height-based location update in a wireless communication system are required.

In an aspect, a method performed by a wireless device in a wireless communication system as defined by independent claim <NUM> is provided.

In another aspect, a wireless device in a wireless communication system as defined by independent claim <NUM> is provided. According to still another aspect, a non-transitory computer-readable medium as defined by independent claim <NUM> is provided. Specific embodiments are defined by the dependent claims.

The present disclosure can have various advantageous effects.

According to some embodiments of the present disclosure, a wireless device could efficiently perform the height-based location update.

For example, as UAV UEs are commercialized, the network will provide more diverse services exclusively for UAV UEs. Based on the height-based registration, the network can configure new NAS or AS configurations related to the height and provide UAV-specific services to the UE.

In other words, according to the present disclosure, a wireless device (for example, a UAV UE) could perform location area update according to the change in height of the wireless device.

According to some embodiments of the present disclosure, a wireless network system could provide an efficient solution for the height-based location update.

Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and/or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

Also, parentheses used in the present disclosure may mean "for example". In detail, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

In addition, one of the most expected <NUM> use cases relates a function capable of smoothly connecting embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential Internet-of-things (IoT) devices will reach <NUM> hundred million up to the year of <NUM>. An industrial IoT is one of categories of performing a main role enabling a smart city, asset tracking, smart utility, agriculture, and security infrastructure through <NUM>.

Technical requirements of a self-driven vehicle demand ultra-low latency and ultrahigh reliability so that traffic safety is increased to a level that cannot be achieved by human being.

Mission critical application (e.g., e-health) is one of <NUM> use scenarios. A health part contains many application programs capable of enjoying benefit of mobile communication. A communication system may support remote treatment that provides clinical treatment in a faraway place. Remote treatment may aid in reducing a barrier against distance and improve access to medical services that cannot be continuously available in a faraway rural area. Remote treatment is also used to perform important treatment and save lives in an emergency situation. The wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Referring to <FIG>, a first wireless device <NUM> and a second wireless device <NUM> may transmit/receive radio signals to/from an external device through a variety of RATs (e.g., LTE and NR). In <FIG>, {the first wireless device <NUM> and the second wireless device <NUM>} may correspond to at least one of {the wireless device 100a to 100f and the BS <NUM>}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and/or {the BS <NUM> and the BS <NUM>} of <FIG>.

The processor(s) <NUM> may control the memory(s) <NUM> and/or the transceiver(s) <NUM> and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. The processor(s) <NUM> may receive radio signals including second information/signals through the transceiver(s) <NUM> and then store information obtained by processing the second information/signals in the memory(s) <NUM>. For example, the memory(s) <NUM> may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) <NUM> or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. The transceiver(s) <NUM> may be interchangeably used with radio frequency (RF) unit(s). In the present disclosure, the first wireless device <NUM> may represent a communication modem/circuit/chip.

The processor(s) <NUM> may control the memory(s) <NUM> and/or the transceiver(s) <NUM> and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the memory(s) <NUM> may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) <NUM> or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. In the present disclosure, the second wireless device <NUM> may represent a communication modem/circuit/chip.

As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors <NUM> and <NUM>. descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be included in the one or more processors <NUM> and <NUM> or stored in the one or more memories <NUM> and <NUM> so as to be driven by the one or more processors <NUM> and <NUM>. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

The one or more transceivers <NUM> and <NUM> may be connected to the one or more antennas <NUM> and <NUM> and the one or more transceivers <NUM> and <NUM> may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, through the one or more antennas <NUM> and <NUM>. In the present disclosure, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

The one or more transceivers <NUM> and <NUM> may convert received radio signals/channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc., using the one or more processors <NUM> and <NUM>. The one or more transceivers <NUM> and <NUM> may convert the user data, control information, radio signals/channels, etc., processed using the one or more processors <NUM> and <NUM> from the base band signals into the RF band signals. For example, the transceivers <NUM> and <NUM> can up-convert OFDM baseband signals to a carrier frequency by their (analog) oscillators and/or filters under the control of the processors <NUM> and <NUM> and transmit the up-converted OFDM signals at the carrier frequency. The transceivers <NUM> and <NUM> may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and/or filters under the control of the transceivers <NUM> and <NUM>.

In the implementations of the present disclosure, a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (DL). In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device <NUM> acts as the UE, and the second wireless device <NUM> acts as the BS. For example, the processor(s) <NUM> connected to, mounted on or launched in the first wireless device <NUM> may be configured to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) <NUM> to perform the UE behavior according to an implementation of the present disclosure. The processor(s) <NUM> connected to, mounted on or launched in the second wireless device <NUM> may be configured to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) <NUM> to perform the BS behavior according to an implementation of the present disclosure.

The communication unit <NUM> may include a communication circuit <NUM> and transceiver(s) <NUM>. For example, the communication circuit <NUM> may include the one or more processors <NUM> and <NUM> of <FIG> and/or the one or more memories <NUM> and <NUM> of <FIG>. For example, the transceiver(s) <NUM> may include the one or more transceivers <NUM> and <NUM> of <FIG> and/or the one or more antennas <NUM> and <NUM> of <FIG>. The control unit <NUM> is electrically connected to the communication unit <NUM>, the memory <NUM>, and the additional components <NUM> and controls overall operation of each of the wireless devices <NUM> and <NUM>. For example, the control unit <NUM> may control an electric/mechanical operation of each of the wireless devices <NUM> and <NUM> based on programs/code/commands/information stored in the memory unit <NUM>.

As an example, the control unit <NUM> may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory <NUM> may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

<FIG> shows another example of wireless devices to which implementations of the present disclosure is applied.

The first wireless device <NUM> may include at least one transceiver, such as a transceiver <NUM>, and at least one processing chip, such as a processing chip <NUM>. The processing chip <NUM> may include at least one processor, such a processor <NUM>, and at least one memory, such as a memory <NUM>. The memory <NUM> may be operably connectable to the processor <NUM>. The memory <NUM> may store various types of information and/or instructions. The memory <NUM> may store a software code <NUM> which implements instructions that, when executed by the processor <NUM>, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code <NUM> may implement instructions that, when executed by the processor <NUM>, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code <NUM> may control the processor <NUM> to perform one or more protocols. For example, the software code <NUM> may control the processor <NUM> may perform one or more layers of the radio interface protocol.

The second wireless device <NUM> may include at least one transceiver, such as a transceiver <NUM>, and at least one processing chip, such as a processing chip <NUM>. The processing chip <NUM> may include at least one processor, such a processor <NUM>, and at least one memory, such as a memory <NUM>. The memory <NUM> may be operably connectable to the processor <NUM>. The memory <NUM> may store various types of information and/or instructions. The memory <NUM> may store a software code <NUM> which implements instructions that, when executed by the processor <NUM>, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code <NUM> may implement instructions that, when executed by the processor <NUM>, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code <NUM> may control the processor <NUM> to perform one or more protocols. For example, the software code <NUM> may control the processor <NUM> may perform one or more layers of the radio interface protocol.

Referring to <FIG>, a UE <NUM> may correspond to the first wireless device <NUM> of <FIG> and/or the first wireless device <NUM> of <FIG>.

The processor <NUM> may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The processor <NUM> may be configured to control one or more other components of the UE <NUM> to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor <NUM>. The processor <NUM> may include ASIC, other chipset, logic circuit and/or data processing device. The processor <NUM> may be an application processor. The processor <NUM> may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). An example of the processor <NUM> may be found in SNAPDRAGON™ series of processors made by Qualcomm®, EXYNOS™ series of processors made by Samsung®, A series of processors made by Apple®, HELIO™ series of processors made by MediaTek®, ATOM™ series of processors made by Intel® or a corresponding next generation processor.

<FIG> and <FIG> show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

In particular, <FIG> illustrates an example of a radio interface user plane protocol stack between a UE and a BS and <FIG> illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring to <FIG>, the user plane protocol stack may be divided into Layer <NUM> (i.e., a PHY layer) and Layer <NUM>. Referring to <FIG>, the control plane protocol stack may be divided into Layer <NUM> (i.e., a PHY layer), Layer <NUM>, Layer <NUM> (e.g., an RRC layer), and a non-access stratum (NAS) layer. Layer <NUM>, Layer <NUM> and Layer <NUM> are referred to as an access stratum (AS).

In the 3GPP LTE system, the Layer <NUM> is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer <NUM> is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to <NUM> core network quality of service (QoS) flows.

In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in case of carrier aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.

Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information, paging control channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing public warning service (PWS) broadcasts, common control channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and dedicated control channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated traffic channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to broadcast channel (BCH); BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged node (AM). The RLC configuration is per logical channel with no dependency on numerologies and/or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.

In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to/from NAS from/to UE.

<FIG> shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

The frame structure shown in <FIG> is purely exemplary and the number of subframes, the number of slots, and/or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).

Referring to <FIG>, downlink and uplink transmissions are organized into frames. Each frame has Tf = <NUM> duration. Each frame is divided into two half-frames, where each of the half-frames has <NUM> duration. Each half-frame consists of <NUM> subframes, where the duration Tsf per subframe is <NUM>. Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing. Each slot includes <NUM> or <NUM> OFDM symbols based on a cyclic prefix (CP). In a normal CP, each slot includes <NUM> OFDM symbols and, in an extended CP, each slot includes <NUM> OFDM symbols. The numerology is based on exponentially scalable subcarrier spacing △f = <NUM>u*<NUM>.

Table <NUM> shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frame Nframe,uslot, and the number of slots per subframe Nsubframe,uslot for the normal CP, according to the subcarrier spacing △f = <NUM>u*<NUM>.

Table <NUM> shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frame Nframe,uslot, and the number of slots per subframe Nsubframe,uslot for the extended CP, according to the subcarrier spacing △f = <NUM>u*<NUM>.

A slot includes plural symbols (e.g., <NUM> or <NUM> symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid of Nsize,ugrid,x*NRBsc subcarriers and Nsubframe,usymb OFDM symbols is defined, starting at common resource block (CRB) Nstart,ugrid indicated by higher-layer signaling (e.g., RRC signaling), where Nsize,ugrid,x is the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink. NRBsc is the number of subcarriers per RB. In the 3GPP based wireless communication system, NRBsc is <NUM> generally. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth Nsize,ugrid for subcarrier spacing configuration u is given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is referred to as a resource element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index / representing a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by <NUM> consecutive subcarriers in the frequency domain.

In the 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered from <NUM> and upwards in the frequency domain for subcarrier spacing configuration u. The center of subcarrier <NUM> of CRB <NUM> for subcarrier spacing configuration u coincides with 'point A' which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a bandwidth part (BWP) and numbered from <NUM> to NsizeBWP,i-<NUM>, where i is the number of the bandwidth part. The relation between the physical resource block nPRB in the bandwidth part i and the common resource block nCRB is as follows: nPRB = nCRB + NsizeBWP,i, where NsizeBWP,i is the common resource block where bandwidth part starts relative to CRB <NUM>. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., <NUM>) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

In the present disclosure, the term "cell" may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A "cell" as a geographic area may be understood as coverage within which a node can provide service using a carrier and a "cell" as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The "cell" associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL component carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the "cell" of radio resources used by the node. Accordingly, the term "cell" may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.

In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the primary cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, secondary cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of special cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For dual connectivity (DC) operation, the term SpCell refers to the PCell of the master cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). An SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA/DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA/DC, the term "serving cells" is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.

<FIG> shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

Referring to <FIG>, "RB" denotes a radio bearer, and "H" denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted/received using radio resources through the PHY layer to/from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block.

In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their physical channels PUSCH and PRACH, respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to PDSCH, PBCH and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to PUCCH, and downlink control information (DCI) is mapped to PDCCH. A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.

Hereinafter, technical features related to the present disclosure are described. Parts of section <NUM>. <NUM>, <NUM>. <NUM>, <NUM>. <NUM>, <NUM>. <NUM>, and <NUM>. <NUM> of 3GPP TS <NUM> v16. <NUM> may be referred.

Operations related to reception of the RRCConnectionSetup by the UE are described.

Operations related to reception of the UEInformationRequest message are described.

Technical features related to a UEInformationRequest message are described. The UEInformationRequest is the command used by E-UTRAN to retrieve information from the UE.

For example, signalling radio bearer for the UEInformationRequest may include SRB1. RLC- Service Access Point (SAP) for the UEInformationRequest may include AM. Logical channel for the UEInformationRequest may include DCCH. Direction for the UEInformationRequest may be E-UTRAN to UE.

The UEInformationRequest may include information on a flightPathInfoReq (for example, FlightPathInfoReportConfig) and/or information on nonCriticalExtension.

Technical features related to a UEInformationResponse message are described. For example, the UEInformationResponse message is used by the UE to transfer the information requested by the E-UTRAN.

For example, signalling radio bearer for the UEInformationResponse may include SRB1 or SRB2 (when logged measurement information is included). RLC-SAP for the UEInformationResponse may include an AM. Logical channel for the UEInformationResponse may include a DCCH. Direction for the UEInformationResponse may be UE to E-UTRAN.

For example, UEInformationResponse message may include a flightPathInfoReport. For example, the flightPathInfoReport may include information on one or more flightPaths and/or one or more wayPointLocations.

Technical features related to Locationinfo are described. For example, the IE Locationinfo is used to transfer detailed location information available at the UE to correlate measurements and UE position information.

For example, Locationinfo information element may include verticalVelocityInfo including information on a verticalVelocity and a verticalVelocityAndUncertainty.

For example, a verticalVelocityAndUncertainty may include information on a parameter verticalVelocityAndUncertainty corresponds to horizontalWithVerticalVelocityAndUncertainty. The first/leftmost bit of the first octet contains the most significant bit.

For example, a verticalVelocity may include information on a parameter verticalVelocity corresponds to horizontalWithVerticalVelocity. The first/leftmost bit of the first octet contains the most significant bit.

UE operations related to Event H1 (The Aerial UE height is above a threshold) are described.

The variables in the formula are defined as follows:.

UE operations related to Event H2 (The Aerial UE height is below a threshold) are described.

Hereinafter, technical features related to Aerial UE communication are described. Parts of section <NUM> of 3GPP TS <NUM> v16. <NUM> may be referred.

E-UTRAN based mechanisms providing LTE connection to UEs capable of Aerial communication are supported via the following functionalities:.

Support of Aerial UE function is stored in the user's subscription information in HSS. HSS transfers this information to the MME during Attach, Service Request and Tracking Area Update procedures.

The subscription information can be provided from the MME to the eNB via the S1 AP Initial Context Setup Request during Attach, Tracking Area Update and Service Request procedures. In addition, for X2-based handover, the source eNodeB can include the subscription information in the X2-AP Handover Request message to the target eNodeB.

For the intra and inter MME S1 based handover, the MME provides the subscription information to the target eNB after the handover procedure.

An aerial UE can be configured with event based height reporting. UE sends height report when the altitude of the aerial UE is above or below a configured threshold. The report contains height and location if configured.

For interference detection, an aerial UE can be configured with RRM event A3, A4 or A5 that triggers measurement report when individual (per cell) RSRP values for a configured number of cells fulfill the configured event. The report contains RRM results and location if configured.

For interference mitigation an aerial UE can be configured with a dedicated UE-specific alpha parameter for PUSCH power control.

E-UTRAN can request a UE to report flight path information consisting of a number of waypoints defined as 3D locations. A UE reports up to configured number of waypoints if flight path information is available at the UE. The report can consist also time stamps per waypoint if configured in the request and if available at the UE.

Location information for Aerial UE communication can include horizontal and vertical speed if configured. Location information can be included in RRM report and in height report.

Hereinafter, technical features related to network slicing are described. Parts of section <NUM> of 3GPP TS <NUM> v17. <NUM> may be referred.

The 5GS supports network slicing. Within a PLMN or SNPN, a network slice is identified by an S-NSSAI, which is comprised of a slice/service type (SST) and a slice differentiator (SD). Inclusion of an SD in an S-NSSAI is optional. A set of one or more S-NSSAIs is called the NSSAI. The following NSSAIs are defined:.

The following NSSAIs are defined in the present document:.

In roaming scenarios, rejected NSSAI for the current PLMN or SNPN, or rejected NSSAI for the current registration area, or rejected NSSAI for the maximum number of UEs reached includes one or more S-NSSAI for the current PLMN and also contains a set of mapped S-NSSAI(s) if available. An S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA is an HPLMN S-NSSAI.

In case of a PLMN, a serving PLMN may configure a UE with the configured NSSAI per PLMN. In addition, the HPLMN may configure a UE with a single default configured NSSAI and consider the default configured NSSAI as valid in a PLMN for which the UE has neither a configured NSSAI nor an allowed NSSAI.

In case of an SNPN, the SNPN may configure a UE with a configured NSSAI applicable to the SNPN if the UE is neither registering nor registered for onboarding services in SNPN. In addition, the credential holder may configure a single default configured NSSAI associated with the selected entry of the "list of subscriber data" or the PLMN subscription and consider the default configured NSSAI as valid in a SNPN for which the UE has neither a configured NSSAI nor an allowed NSSAI. If the UE is registering or registered for onboarding services in SNPN, the serving SNPN shall not provide a configured NSSAI to the UE.

The allowed NSSAI and the rejected NSSAI for the current registration area are managed per access type independently, i.e. 3GPP access or non-3GPP access, and is applicable for the registration area. If the UE does not have a valid registration area, the rejected NSSAI for the current registration area is applicable to the tracking area on which it was received. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, the allowed NSSAI and the rejected NSSAI for the current registration area are applicable to these PLMNs in this registration area.

Upon registration to a PLMN or SNPN (except for the registration procedure for periodic registration update, the initial registration for onboarding services in SNPN, and the registration procedure for mobility registration update when registered for onboarding services in SNPN), the UE shall send to the AMF the requested NSSAI which includes one or more S-NSSAIs of the allowed NSSAI for the PLMN or SNPN or the configured NSSAI and corresponds to the network slice(s) to which the UE intends to register with, if:.

Hereinafter, technical features related to mobility and periodic registration update initiation are described. Parts of section <NUM>. <NUM> of 3GPP TS <NUM> v17. <NUM> may be referred.

The UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message to the AMF,.

Hereinafter, technical features related to identification and selection of a Network Slice: the S-NSSAI and the NSSAI are described. Parts of section <NUM>. <NUM> of 3GPP TS <NUM> v17. <NUM> may be referred.

The NSSAI is a collection of S-NSSAIs. An NSSAI may be a Configured NSSAI, a Requested NSSAI or an Allowed NSSAI. There can be at most eight S-NSSAIs in Allowed and Requested NSSAIs sent in signalling messages between the UE and the Network. The Requested NSSAI signalled by the UE to the network allows the network to select the Serving AMF, Network Slice(s) and Network Slice instance(s) for this UE.

Based on the operator's operational or deployment needs, a Network Slice instance can be associated with one or more S-NSSAIs, and an S-NSSAI can be associated with one or more Network Slice instances. Multiple Network Slice instances associated with the same S-NSSAI may be deployed in the same or in different Tracking Areas. When multiple Network Slice instances associated with the same S-NSSAI are deployed in the same Tracking Areas, the AMF instance serving the UE may logically belong to (i.e. be common to) more than one Network Slice instance associated with this S-NSSAI.

The (R)AN may use Requested NSSAI in access stratum signalling to handle the UE Control Plane connection before the 5GC informs the (R)AN of the Allowed NSSAI. The Requested NSSAI is used by the RAN for AMF selection, as described in clause <NUM>. The UE shall not include the Requested NSSAI in the RRC Resume when the UE asks to resume the RRC connection and is CM-CONNECTED with RRC Inactive state.

When a UE is successfully registered over an Access Type, the CN informs the (R)AN by providing the Allowed NSSAI for the corresponding Access Type.

Hereinafter, technical features related to Tracking area updating procedure are described. Parts of section <NUM>. <NUM> of 3GPP TS <NUM> v17. <NUM> may be referred.

The tracking area updating procedure is always initiated by the UE and is used for the following purposes:.

The periodic tracking area updating procedure is controlled in the UE by timer T3412. When timer T3412 expires, the periodic tracking area updating procedure is started.

The UE in state EMM-REGISTERED shall initiate the tracking area updating procedure by sending a TRACKING AREA UPDATE REQUEST message to the MME.

If the tracking area update request has been accepted by the network, the MME shall send a TRACKING AREA UPDATE ACCEPT message to the UE. If the MME assigns a new GUTI for the UE, a GUTI shall be included in the TRACKING AREA UPDATE ACCEPT message. If the MME includes the GUTI IE in the TRACKING AREA UPDATE ACCEPT message, the MME shall start timer T3450 and enter state EMM-COMMON-PROCEDURE-INITIATED as described in clause <NUM>. The MME may include a new TAI list for the UE in the TRACKING AREA UPDATE ACCEPT message. The MME shall not assign a TAI list containing both tracking areas in NB-S1 mode and tracking areas in WB-S1 mode.

If the tracking area updating cannot be accepted by the network, the MME sends a TRACKING AREA UPDATE REJECT message to the UE including an appropriate EMM cause value.

Meanwhile, in NR, the network may configure the configurations related to NAS, such as IMS, network-slice, during the registration procedure for a registration area, and most NAS parameters may be applicable for the registration area.

Hereinafter, a method for height-based location update in a wireless communication system, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals/messages/fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings. Herein, a wireless device may be referred to as a user equipment (UE).

<FIG> shows an example of a method for height-based location update in a wireless communication system, according to some embodiments of the present disclosure.

In particular, <FIG> shows an example of a method performed by a wireless device in a wireless communication system.

In step S1001, a wireless device may receive information on one or more threshold heights between a plurality of height spans.

For example, network may configure a single threshold height or multiple threshold heights.

For example, the wireless device may receive a configuration including information on a single threshold height. For another example, the wireless device may receive a configuration including information on multiple threshold heights.

In step S1002, a wireless device may monitor a height of the wireless device.

For example, the wireless device may determine a current height span among the plurality of height spans based on the height of the wireless device. The wireless device may apply a configuration associated with the current height span.

For example, the configuration associated with the current height span may include a network slice configuration according to the current height span.

For example, the configuration associated with the current height span may include a IP Multimedia Subsystem (IMS) configuration according to the current height span.

For example, the configuration associated with the current height span may include a Multicast and Broadcast Services (MBS) configuration according to the current height span.

For example, when the current height span is different from the previous height span, the wireless device may apply a configuration associated with the current height span. In other words, then the height span of the wireless device is changed, the wireless device may apply a configuration associated with the current height span.

In step S1003, a wireless device may initiate a tracking area update procedure based on the height of the wireless device being passed the one or more threshold heights.

For example, thew wireless device may initiate the tracking area update procedure based on a height span of the wireless device being changed.

For example, the wireless device may transmit, to an AMF, a TRACKING AREA UPDATE REQUEST message including information on the height of the wireless device. The wireless device may receive, from the AMF, a TRACKING AREA UPDATE ACCEPT message.

According to some embodiments of the present disclosure, the wireless device may perform registration procedure based on the height of the wireless device being passed the one or more threshold heights.

For example, the wireless device may transmit, to an Access and Mobility management Function (AMF), a registration request message including information on the current height span. The wireless device may receive, from the AMF, a registration accept message including a new configuration for the current height span.

For example, the new configuration may include a Non-Access-Stratum (NAS) configuration or an Access-Stratum (AS) configuration related to the current height span. For example, the new configuration may include a slice priority or slice group priority information applicable for the current height span.

According to some embodiments of the present disclosure, the wireless device may be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

Hereinafter, embodiments of a method for height-based location update in a wireless communication system are described.

The network may configure one or more thresholds related to the height of the UE. The threshold(s) may divide the entire height space into several height spans. The height spans may be disjoint so that each height span covers a unique height range.

The UE may determine the current height to decide whether to initiate a registration procedure for the network.

For example, the UE may initiate the registration procedure when the current height is higher than the threshold.

For example, the UE may initiate the registration procedure when the current height is lower than the threshold.

For example, the UE may initiate the registration procedure when the current height span is different from the height span considered by the previous location update procedure.

The network may configure different configurations according to the height.

For example, different network slice configurations are based on height. (UAV-specific slice).

For example, different IMS configurations are based on height. (UAV-specific IMS service).

For example, different MBS configurations are based on height. (UAV-specific MBS service).

The UE may perform a registration procedure based on the thresholds related to height. While performing registration, the UE may receive new NAS or AS configurations related to the height. For example, the UE may be configured with new slice priority or slice group priority information applicable for the height.

<FIG> shows an example of a method for height-based location update procedure in a wireless communication system, according to some embodiments of the present disclosure.

In step S1101, UE may receive, from a network, one more height thresholds related to a height of the UE.

For example, the N threshold divides the entire height space into N+<NUM> disjoint height spans.

In step S1102, UE may determine the current height span based on the current UE height.

In step S1103, UE may initiate a location area update procedure based on the current height span.

For example, UE may initiate a location area update procedure if the current height span is different from the height span considered by the previous location update procedure.

For example, the location area update may indicate that the UE enters a new height span. For example, the UE may indicate the current height of the UE or the current height span.

<FIG> shows an example of a method for registration update with a threshold, according to some embodiments of the present disclosure.

Referring to <FIG>, a UE may configure a threshold height (for example, a single threshold height). That is, there may be two height spans separated by the single threshold height.

For example, UE may be located below than the threshold height. For example, when the UE passes the threshold height by raising the UE's altitude (for example, when the height of the UE is passed the threshold height), the UE may perform the registration process and/or location update process (for example, a TA update process). For example, when the UE passes the threshold height by lowering the UE's altitude (for example, when the UE's altitude is passed the threshold height), the UE may perform the registration process and/or location update process (for example, a TA update process).

For other example, UE may be located above than the threshold height. For example, when the UE passes the threshold height by lowering the UE's altitude (for example, when the height of the UE is passed the threshold height), the UE may perform the registration process and/or location update process (for example, a TA update process). For example, when the UE passes the threshold height by raising the UE's altitude (for example, when the UE's altitude is passed the threshold height), the UE may perform the registration process and/or location update process (for example, a TA update process).

Referring to <FIG>, in step S1301, UE may determine the current height. For example, UE may determine that the current height is higher than a threshold.

In step S1302, UE may perform, with a gNB, processing according to the configuration associated with the height. For example, UE may perform processing based on the the current height which is higher than the threshold.

In step S1303, UE may transmit, to an AMF (for example, via the gNB), a registration request with a height information.

In step S1304, UE may receive, form the AMF (for example, via the gNB), a registration accept with new configuration for the height information.

In step S1305, UE may determine the current height. For example, UE may determine that the current height is lower than a threshold.

In step S1306, UE may perform, with a gNB, processing according to the configuration associated with the height. For example, UE may perform processing based on the the current height which is lower than the threshold.

In step S1307, UE may transmit, to an AMF (for example, via the gNB), a registration request with a height information.

In step S1308, UE may receive, form the AMF (for example, via the gNB), a registration accept with new configuration for the height information.

Referring to <FIG>, in step S1401, the network may configure a threshold related to the height of the UE. The threshold may divide the entire height space into disjoint height spans.

In step S1402, at an altitude that is different from the height span considered by the previous registration update procedure (that is, at an altitude higher than the threshold in <FIG>), the UE may send a registration request message to the network.

For example, at an altitude higher than the threshold, the UE may send a registration request message to the network.

In step S1403, the UE may receive a registration accept message with new configurations for the height from the network.

In step S1404, at an altitude that is different from the height span considered by the previous registration update procedure (that is, at an altitude lower than the threshold in <FIG>), the UE sends a registration request message to the network.

In step S1405, the UE may receive a registration accept message with new configurations for the height from the network.

<FIG> shows an example of a method for registration update with multiple thresholds, according to some embodiments of the present disclosure.

Referring to <FIG>, a UE may configure multiple threshold heights (for example, N threshold heights). That is, there may be N+<NUM> height spans separated by the N threshold heights.

For example, when the UE passes the threshold height by raising or lowering the UE's altitude, the UE may perform the registration process and/or location update process (for example, a TA update process).

In other words, for example, when the height of the UE is passed the first threshold height (Threshold <NUM>) or the second threshold height (Threshold <NUM>), the UE may perform the registration process and/or location update process (for example, a TA update process).

Referring to <FIG>, in step S1601, UE may determine the current height. For example, UE may determine that the current height is higher than a threshold <NUM>.

In step S1602, UE may perform, with a gNB, processing according to the configuration associated with the height. For example, UE may perform processing based on the the current height which is higher than the threshold <NUM>.

In step S1603, UE may transmit, to an AMF (for example, via the gNB), a registration request with a height information.

In step S1604, UE may receive, form the AMF (for example, via the gNB), a registration accept with new configuration for the height information.

In step S1605, UE may determine the current height. For example, UE may determine that the current height is higher than a threshold <NUM>.

For example, the threshold <NUM> is higher than the threshold <NUM>.

In step S1606, UE may perform, with a gNB, processing according to the configuration associated with the height. For example, UE may perform processing based on the the current height which is higher than the threshold <NUM>.

In step S1607, UE may transmit, to an AMF (for example, via the gNB), a registration request with a height information.

In step S1608, UE may receive, form the AMF (for example, via the gNB), a registration accept with new configuration for the height information.

In step S1609, UE may determine the current height. For example, UE may determine that the current height is lower than a threshold <NUM>.

In step S1610, UE may perform, with a gNB, processing according to the configuration associated with the height. For example, UE may perform processing based on the the current height which is lower than the threshold <NUM>.

In step S1611, UE may transmit, to an AMF (for example, via the gNB), a registration request with a height information.

In step S1612, UE may receive, form the AMF (for example, via the gNB), a registration accept with new configuration for the height information.

Referring to <FIG>, in step S1701, the network may configure several thresholds related to the height of the UE. The thresholds may divide the entire height space into disjoint height spans.

In step S1702, at an altitude that is different from the height span considered by the previous registration update procedure (that is, at an altitude higher than a first threshold, Threshold <NUM>), the UE may send a registration request message to the network.

In step S1703, the UE may receive a registration accept message with new configurations for the height from the network.

In step S1704, at an altitude that is different from the height span considered by the previous registration update procedure (that is, at an altitude higher than a second threshold, Threshold <NUM>), the UE may send a registration request message to the network.

In step S1705, the UE may receive a registration accept message with new configurations for the height from the network.

In step S1706, at an altitude that is different from the height span considered by the previous registration update procedure (that is, at an altitude lower than the second threshold, Threshold <NUM>), the UE may send a registration request message to the network.

In step S1707, the UE receive a registration accept message with new configurations for the height from the network.

<FIG> shows an example of Base Station (BS) operations for height-based location update in a wireless communication system, according to some embodiments of the present disclosure.

In step S1801, a BS may transmit, to a wireless device, information on one or more threshold heights between a plurality of height spans.

For example, the BS may transmit, to the wireless device, a configuration including information on the one or more height thresholds.

In step S1802, the BS may receive, from the wireless device, a message related to a tracking area update (TAU) procedure including information on the height of the wireless device.

For example, the BS may receive, from the wireless device, a TRACKING AREA UPDATE REQUEST message including information on the height of the wireless device.

In step S1803, the BS may forward the received message to a core network.

For example, the BS may forward the TRACKING AREA UPDATE REQUEST message to an AMF.

In step S1804, the BS may receive a response message related to the tracking area update procedure from the core network.

For example, the BS may receive the TRACKING AREA UPDATE ACCEPT message from the AMF.

In step S1805, the BS may forward the response message related to the tracking area update procedure to the wireless device.

For example, the BS may forwards the TRACKING AREA UPDATE ACCEPT message to the wireless device.

Some of the detailed steps shown in the examples of <FIG> may not be essential steps and may be omitted. In addition to the steps shown in <FIG>, other steps may be added, and the order of the steps may vary. Some of the above steps may have their own technical meaning.

Hereinafter, an apparatus for height-based location update in a wireless communication system, according to some embodiments of the present disclosure, will be described. Herein, the apparatus may be a wireless device (<NUM> or <NUM>) in <FIG>, <FIG>, and <FIG>.

For example, a wireless device may perform the methods described above. The detailed description overlapping with the above-described contents could be simplified or omitted.

Referring to <FIG>, a wireless device <NUM> may include a processor <NUM>, a memory <NUM>, and a transceiver <NUM>.

According to some embodiments of the present disclosure, the processor <NUM> may be configured to be coupled operably with the memory <NUM> and the transceiver <NUM>.

The processor <NUM> may be configured to control the transceiver <NUM> to receive information on one or more threshold heights between a plurality of height spans. The processor <NUM> may be configured to monitor a height of the wireless device. The processor <NUM> may be configured to initiate a tracking area update procedure based on the height of the wireless device being passed the one or more threshold heights.

For example, the processor <NUM> may be configured to initiate the tracking area update procedure based on a height span of the wireless device being changed.

For example, the processor <NUM> may be configured to determine a current height span among the plurality of height spans based on the height of the wireless device.

For example, the processor <NUM> may be configured to apply a configuration associated with the current height span.

For example, the processor <NUM> may be configured to control the transceiver <NUM> to transmit, to an Access and Mobility management Function (AMF), a registration request message including information on the current height span.

For example, the processor <NUM> may be configured to control the transceiver <NUM> to receive, from the AMF, a registration accept message including a new configuration for the current height span.

For example, the new configuration may include a Non-Access-Stratum (NAS) configuration or an Access-Stratum (AS) configuration related to the current height span.

For example, the new configuration may include a slice priority or slice group priority information applicable for the current height span.

For example, in the tracking area update procedure, the processor <NUM> may be configured to control the transceiver <NUM> to transmit, to an AMF, a TRACKING AREA UPDATE REQUEST message including information on the height of the wireless device. The processor <NUM> may be configured to control the transceiver <NUM> to receive, from the AMF, a TRACKING AREA UPDATE ACCEPT message.

For example, the processor <NUM> may be configured to control the transceiver <NUM> to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

Hereinafter, a processor for a wireless device for height-based location update in a wireless communication system, according to some embodiments of the present disclosure, will be described.

The processor may be configured to control the wireless device to receive information on one or more threshold heights between a plurality of height spans. The processor may be configured to control the wireless device to monitor a height of the wireless device. The processor may be configured to control the wireless device to initiate a tracking area update procedure based on the height of the wireless device being passed the one or more threshold heights.

For example, the processor may be configured to control the wireless device to initiate the tracking area update procedure based on a height span of the wireless device being changed.

For example, the processor may be configured to control the wireless device to determine a current height span among the plurality of height spans based on the height of the wireless device.

For example, the processor may be configured to control the wireless device to apply a configuration associated with the current height span.

For example, the processor may be configured to control the wireless device to transmit, to an Access and Mobility management Function (AMF), a registration request message including information on the current height span.

For example, the processor may be configured to control the wireless device to receive, from the AMF, a registration accept message including a new configuration for the current height span.

For example, in the tracking area update procedure, the processor may be configured to control the wireless device to transmit, to an AMF, a TRACKING AREA UPDATE REQUEST message including information on the height of the wireless device. The processor may be configured to control the wireless device to receive, from the AMF, a TRACKING AREA UPDATE ACCEPT message.

For example, the processor may be configured to control the wireless device to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for height-based location update in a wireless communication system, according to some embodiments of the present disclosure, will be described.

According to some embodiment of the present disclosure, the technical features of the present disclosure could be embodied directly in hardware, in a software executed by a processor, or in a combination of the two. For example, a method performed by a wireless device in a wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, a software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other storage medium.

Some example of storage medium is coupled to the processor such that the processor can read information from the storage medium. For other example, the processor and the storage medium may reside as discrete components.

The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.

For example, non-transitory computer-readable media may include random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures. Non-transitory computer-readable media may also include combinations of the above.

In addition, the method described herein may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and/or executed by a computer.

According to some embodiment of the present disclosure, a non-transitory computer-readable medium has stored thereon a plurality of instructions. The stored a plurality of instructions may be executed by a processor of a wireless device.

The stored a plurality of instructions may cause the wireless device to receive information on one or more threshold heights between a plurality of height spans. The stored a plurality of instructions may cause the wireless device to monitor a height of the wireless device. The stored a plurality of instructions may cause the wireless device to initiate a tracking area update procedure based on the height of the wireless device being passed the one or more threshold heights.

For example, the stored a plurality of instructions may cause the wireless device to initiate the tracking area update procedure based on a height span of the wireless device being changed.

For example, the stored a plurality of instructions may cause the wireless device to determine a current height span among the plurality of height spans based on the height of the wireless device.

For example, the stored a plurality of instructions may cause the wireless device to apply a configuration associated with the current height span.

For example, the stored a plurality of instructions may cause the wireless device to transmit, to an Access and Mobility management Function (AMF), a registration request message including information on the current height span.

For example, the stored a plurality of instructions may cause the wireless device to receive, from the AMF, a registration accept message including a new configuration for the current height span.

For example, in the tracking area update procedure, the stored a plurality of instructions may cause the wireless device to transmit, to an AMF, a TRACKING AREA UPDATE REQUEST message including information on the height of the wireless device. The stored a plurality of instructions may cause the wireless device to receive, from the AMF, a TRACKING AREA UPDATE ACCEPT message.

According to some embodiments of the present disclosure, the stored a plurality of instructions may cause the wireless device to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

Hereinafter, a base station (BS) for height-based location update in a wireless communication system, according to some embodiments of the present disclosure, will be described.

The BS may include a transceiver, a memory, and a processor operatively coupled to the transceiver and the memory.

The processor may be configured to control the transceiver to transmit, to a wireless device, information on one or more threshold heights between a plurality of height spans. The processor may be configured to control the transceiver to receive, from the wireless device, a message related to a tracking area update (TAU) procedure including information on the height of the wireless device. The processor may be configured to forward the received message to a core network. The processor may be configured to receive a response message related to the tracking area update procedure from the core network. The processor may be configured to control the transceiver to forward the response message related to the tracking area update procedure to the wireless device.

Claim 1:
A method performed by a wireless device (<NUM>) in a wireless communication system, the method comprising:
receiving (S1001) information on one or more threshold heights between a plurality of height spans,
wherein the one or more threshold heights divide an entire height space into the plurality of height spans, and
wherein each of the plurality of height spans covers a unique height range;
applying a first configuration associated with a first height span where the wireless device belongs;
monitoring (S1002) a current height of the wireless device (<NUM>); and
transmitting (S1303, S1307), to an Access and Mobility management Function, AMF, a registration request message including height information for the wireless device, based on the current height being changed from the first height span to a second height span; and
receiving (S1304, S1308), from the AMF, a registration accept message including a second configuration associated with the second height span,
wherein the second configuration is different from the first configuration, and
wherein the first configuration and the second configuration include (i) a network slice configuration, (ii) an Internet Protocol, IP, Multimedia Subsystem, IMS, configuration, (iii) a Multicast and Broadcast Services, MBS, configuration, and (iv) a slice priority or slice group priority information, respectively.