Communication apparatuses, servers, and communication methods

Abstract

A communication method performed by a communication apparatus is described. The communication method may comprise receiving, from a server, a data request message, the data request message including a first criterion, receive a reference signal from another communication apparatus, and generate a channel measurement based on the reference signal; and sending, to the server, the channel measurement if the channel measurement fulfills the first criterion; wherein the channel measurement consists of at least timing information.

Description

[DESCRIPTION][Title of Invention]COMMUNICATION APPARATUSES, SERVERS, AND COMMUNICATION METHODS[Technical Field]

[0001] The present disclosure relates to a communication apparatus, a server and a communication method.[Background Art]

[0002] At present, as a radio access system and a radio network technology aimed for the fifth-generation (5G) cellular system and the sixth-generation (6G) cellular system, technical investigation and standard development are being conducted, as extended standards of Long Term Evolution (LTE), on LTE- Advanced Pro (LTE-A Pro) and New Radio technology (NR) in The Third Generation Partnership Project (3 GPP).

[0003] In the fifth-generation cellular system, three services of enhanced Mobile BroadBand (eMBB) to achieve high-speed and large-volume transmission, UltraReliable and Low Latency Communication (URLLC) to achieve low-latency and high- reliability communication, and massive Machine Type Communication (mMTC) to allow connection of a large number of machine type devices such as Internet of Things (loT) have been demanded as assumed scenarios.

[0004] Additionally, 3 GPP has been actively engaging in Artificial Intelligence (AI) / Machine Learning (ML) initiatives. The integration of AI / ML into 3GPP’s development of 5G and 6G wireless communication standards is to facilitate the application of AI / ML technologies in commercial cellular system. However, how to enable supporting of AI / ML in 5G and 6G wireless communication standards has not been well discussed, with offering limited flexibility and the efficiency for the whole wireless communication system. As illustrated by this discussion, systems and methods according to the present invention, effectively enabling the support of AI / ML functionality, may improve the communication flexibility and efficiency and may be beneficial.

[0005] 3GPP specified location technologies over the NR. This can be referred to as NR positioning. The NR positioning is aimed at indoor and outdoor use cases (e.g. emergency case and commercial case). In the NR positioning, timing-based and anglebased positioning method is supported. Such methods may suffer from poor accuracyin Non Line Of Sight (NLOS) environments comparing in Line Of Sight (LOS) environments.[Brief Description of the Drawings]

[0006] Figure 1 is a block diagram illustrating one configuration of one or more base stations and one or more user equipments (UEs) in which systems and methods may be implemented;

[0007] Figure 2 is a diagram illustrating one example 200 of a resource grid;

[0008] Figure 3 is a diagram illustrating one example 300 of common resource block grid, carrier configuration and BWP configuration by a UE 102 and a base station 160;

[0009] Figure 4 is a diagram illustrating one 400 example of functional framework for AI / ML for NR air interface by a UE 102 and a base station 160;

[0010] Figure 5 is a conceptual diagram of a wireless communication system for the present disclosure.

[0011] Figure 6 is an example of a sequence diagram of data transfer via LPP or NRPPa.

[0012] Figure 7 is an example of a sequence diagram of dataset transfer via LPP or NRPPa.

[0013] Figure 8 illustrates various components that may be utilized in a UE;

[0014] Figure 9 illustrates various components that may be utilized in a base station;[Description of Embodiments]

[0015] A communication apparatus is described. The communication apparatus may comprise reception circuitry configured to receive, from a server, a data request message, the data request message including a first criterion, receive a reference signal from another communication apparatus, and generate a channel measurement based on the reference signal; and transmission circuitry configured to send, to the server, the channel measurement if the channel measurement fulfills the first criterion; wherein the channel measurement consists of at least timing information.

[0016] The first criterion may correspond to a first quality that indicates an estimate of quality of timing, and a second quality of the timing information included in the channel measurement is better than the first quality.

[0017] A server is described. The server may comprise transmission circuitry configured to send a data request message, to a communication apparatus, the datarequest message including a first criterion, and reception circuitry configured to receive a channel measurement the channel measurement consisting of at least timing information and fulfillings the first criterion.

[0018] The first criterion may correspond to a first quality that indicates an estimate of quality of timing, and a second quality of the timing information included in the channel measurement is better than the first auality.

[0019] A communication method performed by a communication apparatus is described. The communication method may comprise receiving, from a server, a data request message, the data request message including a first criterion, receive a reference signal from another communication apparatus, and generate a channel measurement based on the reference signal; and sending, to the server, the channel measurement if the channel measurement fulfills the first criterion; wherein the channel measurement consists of at least timing information.

[0020] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements. In one aspect, UMTS has been modified to provide support and specification for the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN). 3GPP NR (New Radio) is the name given to a project to improve the LTE mobile phone or device standard to cope with future requirements. In one aspect, LTE has been modified to provide support and specification (TS 38.331, 38.321, 38.300, 37.340, 38.211, 38.212, 38.213, 38.214, etc.) for the New Radio Access (NR) and Next generation - Radio Access Network (NG-RAN).

[0021] At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A), LTE-Advanced Pro, New Radio Access (NR), and other 3G / 4G / 5G standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, and / or 19 and / or Narrow Band-Internet of Things (NB- IoT)). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.

[0022] A wireless communication device may be an electronic device used to communicate voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet,etc.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE (User Equipment), an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, a relay node, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, industrial wireless sensors, video surveillance, wearables, vehicles, roadside units, infrastructure devices, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. However, as the scope of the present disclosure should not be limited to the 3GPP standards, the terms “UE” and “wireless communication device” may be used interchangeably herein to mean the more general term “wireless communication device”.

[0023] In 3 GPP specifications, a base station is typically referred to as a gNB, a Node B, an eNB, a home enhanced or evolved Node B (HeNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms “base station,”, “gNB”, “Node B,” “eNB,” and “HeNB” may be used interchangeably herein to mean the more general term “base station.” Furthermore, one example of a “base station” is an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term “communication device” may be used to denote both a wireless communication device and / or a base station.

[0024] It should be noted that as used herein, a “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced), IMT-2020 (5G) and all of it or a subset of it may be adopted by 3GPP as licensed bands (e.g., frequency bands) to be used for communication between a base station and a UE. It should also be noted that in NR, NG-RAN, E-UTRA and E-UTRAN overall description, as used herein, a “cell” may be defined as “combination of downlink and optionally uplink resources.” The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

[0025] “Configured cells” are those cells of which the UE is aware and is allowed by a base station to transmit or receive information. “Configured cell(s)” may beserving cell(s). The UE may receive system information and perform the required measurements on configured cells. “Configured cell(s)” for a radio connection may consist of a primary cell and / or no, one, or more secondary cell(s). “Activated cells” are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells for which the UE monitors the physical downlink control channel (PDCCH) and in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH). “Deactivated cells” are those configured cells that the UE is not monitoring the transmission PDCCH. It should be noted that a “cell” may be described in terms of differing dimensions. For example, a “cell” may have temporal, spatial (e.g., geographical) and frequency characteristics.

[0026] The base stations may be connected by the NG interface to the 5G - core network (5G-CN). 5G-CN may be called as to NextGen core (NGC), or 5G core (5GC). The base stations may also be connected by the S 1 interface to the evolved packet core (EPC). For instance, the base stations may be connected to a NextGen (NG) mobility management function by the NG-2 interface and to the NG core User Plane (UP) functions by the NG-3 interface. The NG interface supports a many-to-many relation between NG mobility management functions, NG core UP functions and the base stations. The NG-2 interface is the NG interface for the control plane and the NG-3 interface is the NG interface for the user plane. For instance, for EPC connection, the base stations may be connected to a mobility management entity (MME) by the Sl- MME interface and to the serving gateway (S-GW) by the Sl-U interface. The SI interface supports a many-to-many relation between MMEs, serving gateways and the base stations. The SI -MME interface is the SI interface for the control plane and the Sl-U interface is the SI interface for the user plane. The Uu interface is a radio interface between the UE and the base station for the radio protocol.

[0027] The UE may make measurements of downlink signals from NG-RAN, sidelink signals from other UEs, and other sources such as E-UTRAN, different GNSS and TBS systems, WLAN access points, Bluetooth beacons, UE barometric pressure and motion sensors. The measurements to be made may be determined by the chosen positioning method. The UE may also contain LCS applications, or access an LCS application either through communication with a network accessed by the UE or through another application residing in the UE. This LCS application may include the needed measurement and calculation functions to determine the UE's position with orwithout network assistance. The UE may also, for example, contain an independent positioning function (e.g., GPS) and thus be able to report its position, independent of the NG-RAN transmissions. The UE with an independent positioning function may also make use of assistance information obtained from the network.

[0028] Figure 5 is a conceptual diagram of a wireless communication system for the present disclosure.

[0029] The base station 502 (e.g. gNB) may be a network element of NG-RAN that may provide measurement information for a target UE and may communicate this information to an LMF 503. To support NR RAT-Dependent positioning, the gNB 502 may make measurements of radio signals for a target UE 501a, and provide measurement results for position estimation. A gNB 502 may serve several Transmission and Reception Points (TRPs), including for example remote radio heads, and UL-SRS only Reception Points (RPs) and DL-PRS-only Transmission Points (TPs). For NTN, a TRP may be located on board the satellite. A gNB 502 may broadcast assistance data information, received from an LMF 503, in positioning System Information messages.

[0030] The ng-eNB 502 may be a network element of NG-RAN that may provide measurement results for position estimation and makes measurements of radio signals for a target UE 501a and communicates these measurements to an LMF 503. The ng- eNB 502 may make its measurements in response to requests from the LMF 503 (on demand or periodically). An ng-eNB 502 may serve several TPs, including for example remote radio heads and PRS-only TPs for PRS-based TBS positioning for E-UTRA. An ng-eNB 502 may broadcast assistance data information, received from an LMF 503, in positioning System Information messages.

[0031] The gNB and ng-eNB can be referred to as NG-RAN node 502. The NG- RAN node 502 is name of a base station. The NG-RAN may equip Transmission and Reception Point (TRP), Reception Point (RP) or Transmission Point (TP).

[0032] The LMF 503 may manage the support of different location services for target UEs, including positioning of UEs and delivery of assistance data to UEs. The LMF 503 can be referred to as location server or positioning server. The LMF 503 may interact with the serving gNB or serving ng-eNB for a target UE in order to obtain position measurements for the UE, including uplink measurements made by an NG- RAN and downlink measurements made by the UE that were provided to an NG-RANas part of other functions such as for support of handover. The LMF 503 may interact with a target UE in order to deliver assistance data if requested for a particular location service, or to obtain a location estimate if that was requested. The LMF 503 may interact with multiple NG-RAN nodes 502 to provide assistance data information for broadcasting. The assistance data information for broadcast may optionally be segmented and / or ciphered by the LMF 503. The LMF 503 may also interact with AMFs to provide ciphering key data information to the AMF. For position ing of a target UE, the LMF 503 may decide on the position methods to be used, based on factors that may include the LCS Client type, the required QoS, UE positioning capabilities, gNB positioning capabilities and ng-eNB positioning capabilities. The LMF 503 then may invoke these positioning methods in the UE, serving gNB and / or serving ng eNB. The positioning methods may yield a location estimate for UE-based position methods and / or positioning measurements for UE-assisted and network-based position methods. The LMF 503 may combine all the received results and determine a single location estimate for the target UE (hybrid positioning). Additional information like accuracy of the location estimate and velocity may also be determined. The LMF 503 may interact with the AMF to provide (updated) UE Positioning Capability to AMF and to receive stored UE Positioning Capability from AMF.

[0033] The Location Management Function (LMF) 503 is the network entity in the 5G Core Network (5GC) in charge of at least the following functionality.Supports location determination for a UE.- Obtains downlink location measurements or a location estimate from the UE.Obtains uplink location measurements from the NG RAN.- Obtains non-UE associated assistance data from the NG RAN.

[0034] A Positioning Reference Unit (PRU) 501b at a known location may perform positioning measurements (e.g., RSTD, RSRP, UE Rx-Tx Time Difference measurements, DL-RSCPD, DL-RSCP, etc.) and report these measurements to a LMF. In addition, the PRU 501b may transmit SRS to enable TRPs to measure and report UL positioning measurements (e.g., RTOA, UL-AoA, gNB Rx-Tx Time Difference, UL- RSCP, etc.) from PRU 501b at a known location. The PRU measurements may be compared by a LMF 503 with the measurements expected at the known PRU location to determine correction terms for other nearby target devices. The DL- and / or UL location measurements for other target devices can then be corrected based on thepreviously determined correction terms. PRU 501b measurements may also be provided to the target device in the assistance data. From a location server perspective, the PRU functionality is realized by a UE with known location. Hereinafter, the UE 501a may refer to the PRU 501b.

[0035] The LTE Positioning Protocol (LPP) 504 may be terminated between a target device (the terminal device 501a and 501b in the control-plane case) and a positioning server (the LMF 503 in the control-plane case). It may use either the control- or user-plane protocols as underlying transport. In this specification, only control plane use of LPP 504 is defined.

[0036] Positioning procedures in the NG-RAN are modelled as transactions of the LPP protocol using the procedures defined in this specification. A procedure consists of a single operation of one of the following types:Exchange of positioning capabilities;Transfer of assistance data;Transfer of location information (positioning measurements and / or position estimate);Error handling;Abort.

[0037] Parallel transactions are permitted (i.e. a new LPP 504 transaction may be initiated, while another one is outstanding). The protocol may operate between a "target" and a "server". In the control-plane context, these entities may be the UE and LMF respectively. A procedure may be initiated by either the target or the server.

[0038] The NR Positioning Protocol A (NRPPa) 505 may carry information between the NG-RAN Node (e.g. gNB) 502 and the LMF503. It may be used to support the following positioning functions:E-CID for E-UTRA where measurements are transferred from the ng-eNB to the LMF.Data collection from ng-eNB's and gNB's for support of OTDOA positioning for E-UTRA.Cell-ID and Cell Portion ID retrieval from gNB's for support of NR Cell ID positioning method.Exchange of information between LMF and NG-RAN node for the purpose of assistance data broadcasting.NR E-CID where measurements are transferred from the gNB to the LMF. NR Multi-RTT where measurements are transferred from the gNB to the LMF.NR UL-AoA where measurements are transferred from the gNB to the LMF.NR UL-TDOA where measurements are transferred from the gNB to the LMF.Data collection from gNBs for support of DL-TDOA, DL-AoD, Multi-RTT, UL-TDOA, UL-AoA.Measurement Preconfiguration Information Transfer which allows the LMF 503 to request the NG-RAN node 502 to pre-configure and activate / deactivate measurement gap and / or PRS processing window. The NRPPa protocol 505 may be transparent to the AMF. The AMF may route the NRPPa PDUs transparently based on a Routing ID corresponding to the involved LMF over NG-C interface without knowledge of the involved NRPPa transaction. It may carry the NRPPa PDUs over NG- C interface either in UE associated mode or non-UE associated mode. In case of a split gNB architecture, the NRPPa protocol 505 is terminated at the gNB-CU.

[0039] Positioning and data acquisition transactions between a LMF 503 and NG- RAN node 502 may be modelled by using procedures of the NRPPa protocol 505. There may be two types of NRPPa procedures:UE associated procedure, i.e. transfer of information for a particular UE, including the procedures supporting the Positioning Information Transfer, E-CID Location Information Transfer and Measurement Pre-configuration Information Transfer functions;Non UE associated procedure, i.e. transfer of information applicable to the NG-RAN node and associated TRP, including the procedures supporting the OTDOA Information Transfer, Assistance Information Transfer, TRP Information Transfer, Measurement Information Transfer and PRS Information Transfer functions.

[0040] Parallel transactions between the same LMF 503 and NG-RAN node 502 may be supported; i.e. a pair of LMF 503 and NG-RAN node 502 may have more than one instance of an NRPPa procedure 505 in execution at the same time. For possible extensibility, the protocol is considered to operate between a generic "access node" (e.g. gNB 502, ng-eNB 502) and a "server" (e.g. LMF 503). An NRPPa transaction is only initiated by the server.

[0041] The radio protocol architecture may include the user plane and the control plane. The user plane protocol stack may include packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC) and physical (PHY) layers. A DRB (Data Radio Bearer) is a radio bearer that carries user data (as opposed to control plane signaling). For example, a DRB may be mapped to the user plane protocol stack. The PDCP, RLC, MAC and PHY sublayers (terminated at the base station 460a on the network) may perform functions (e.g., header compression, ciphering, scheduling, ARQ and HARQ) for the user plane. PDCP entities are located in the PDCP sublayer. RLC entities may be located in the RLC sublayer. MAC entities may be located in the MAC sublayer. The PHY entities may be located in the PHY sublayer.

[0042] The control plane may include a control plane protocol stack. The PDCP sublayer (terminated in base station on the network side) may perform functions (e.g., ciphering and integrity protection) for the control plane. The RLC and MAC sublayers (terminated in base station on the network side) may perform the same functions as for the user plane. The Radio Resource Control (RRC) (terminated in base station on the network side) may perform the following functions. The RRC may perform broadcast functions, paging, RRC connection management, radio bearer (RB) control, mobility functions, UE measurement reporting and control. The Non-Access Stratum (NAS) control protocol (terminated in MME on the network side) may perform, among other things, evolved packet system (EPS) bearer management, authentication, evolved packet system connection management (ECM)-IDLE mobility handling, paging origination in ECM-IDLE and security control.

[0043] Signaling Radio Bearers (SRBs) are Radio Bearers (RB) that may be used only for the transmission of RRC and NAS messages. Three SRBs may be defined. SRB0 may be used for RRC messages using the common control channel (CCCH) logical channel. SRB1 may be used for RRC messages (which may include a piggybacked NAS message) as well as for NAS messages prior to the establishment of SRB2, all using the dedicated control channel (DCCH) logical channel. SRB2 may be used for RRC messages which include logged measurement information as well as for NAS messages, all using the DCCH logical channel. SRB2 has a lower priority than SRB1 and may be configured by a network (e.g., base station) after security activation. A broadcast control channel (BCCH) logical channel may be used for broadcastingsystem information. Some of BCCH logical channel may convey system information which may be sent from the network to the UE via BCH (Broadcast Channel) transport channel. BCH may be sent on a physical broadcast channel (PBCH). Some of BCCH logical channel may convey system information which may be sent from the network to the UE via DL-SCH (Downlink Shared Channel) transport channel. Paging may be provided by using paging control channel (PCCH) logical channel.

[0044] System information may be divided into the Masterin formations lock (MIB) and a number of SystemlnformationB locks (SIBs).

[0045] A higher-layer parameter is a parameter included in an RRC message, LPP message, NRPPa message or a MAC CE (Medium Access Control Control Element). The higher-layer parameter is a generic name of information included in a MIB, system information, a message which corresponds to CCCH, a message which corresponds to DCCH, and a MAC CE. A higher-layer parameter may be referred to as an RRC parameter or an RRC configuration if the higher-layer parameter is the parameter included in the RRC message. A higher-layer parameter may be referred to as an LPP parameter or an LPP configuration if the higher-layer parameter is the parameter included in the LPP message. A higher-layer parameter may be referred to as an NRPPa parameter or an NRPPa configuration if the higher-layer parameter is the parameter included in the NRPPa message. RRC parameter, LPP parameter and NRPPa parameter consists of Information Element (IE).

[0046] The UE may receive one or more RRC messages from the base station to obtain RRC configurations or parameters. The RRC layer of the UE may configure RRC layer and / or lower layers (e.g., PHY layer, MAC layer, RLC layer, PDCP layer) of the UE according to the RRC configurations or parameters which may be configured by the RRC messages, broadcasted system information, and so on. The base station may transmit one or more RRC messages to the UE to cause the UE to configure RRC layer and / or lower layers of the UE according to the RRC configurations or parameters which may be configured by the RRC messages, broadcasted system information, and so on.

[0047] The UE may receive one or more LPP messages from the LMF to obtain LPP configurations or parameters. The LPP layer of the UE may configure LPP layer and / or lower layers (e.g., PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer) of the UE according to the LPP configurations or parameters which may be configuredby the LPP messages, broadcasted system information (e.g. posSIB), and so on. The LMF may transmit one or more LPP messages to the UE to cause the UE to configure LPP layer and / or lower layers of the UE according to the LPP configurations or parameters which may be configured by the LPP messages, broadcasted system information (e.g. posSIB), and so on.

[0048] The NR-RAN node (e.g. gNB) may receive one or more NRPPa messages from the LMF to obtain NRPPa configurations or parameters. The NRPPa layer of the NG-RAN node may configure NRPPa layer and / or lower layers (e.g., PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer) of the NG-RAN node according to the NRPPa configurations or parameters which may be configured by the NRPPa messages. The LMF may transmit one or more NRPPa messages to the NG-RAN node to cause the NG-RAN node to configure NRPPa layer and / or lower layers of the NG-RAN node according to the NRPPa configurations or parameters which may be configured by the NRPPa messages.

[0049] The size of various fields in the time domain is expressed in time units The constant103and

[0050] Multiple OFDM num erol ogies are supported as given by Table 4.2-1 of [TS 38.211] where p and the cyclic prefix for a bandwidth part are obtained from the higher- layer parameter subcarrierSpacing and cyclicPrefix, respectively.

[0051] The size of various fields in the time domain may be expressed as a number of time units Tc=l / (15000x2048) seconds. Downlink and uplink transmissions are organized into frames with Tjf10ms duration, each consisting of ten subframes of Ts<- = (A fmaxNf / 1000) ■ Tc= 1ms duration. The number of consecutive OFDM symbols per subframe isEach frame is divided into two equally-sized halfframes of five subframes each with half-frame 0 consisting of subframes 0 -4 and halfframe 1 consisting of subframes 5 - 9.

[0052] For subcarrier spacing (SCS) configuration p, slots are numbered in increasing order within a subframe andin increasing order within a frame jsqie number ofslots per subframe for subcarrier spacing configuration / r. There are consecutiveOFDM symbols in a slot wheredepends on the cyclic prefix as given by Tables 4.3.2-1 and 4.3.2-2 of [TS 38.211], The start of slot in a subframe is aligned in timewith the start of OFDM symbol n the same subframe. Subcarrier spacingrefers to a spacing (or frequency bandwidth) between two consecutive subcarriers in the frequency domain. For example, the subcarrier spacing can be set to 15kHz (i.e., Aresource block is defined as a number of consecutive subcarriers (e.g., 12) in the frequency domain. For a carrier with different frequency, the applicable subcarrier may be different. For example, for a carrier in a frequency rang 1, a subcarrier spacing only among a set of {15kHz, 30kHz, 60kHz} is applicable. For a carrier in a frequency rang 2, a subcarrier spacing only among a set of {60kHz, 120kHz, 240kHz} is applicable. The base station may not configure an inapplicable subcarrier spacing for a carrier.

[0053] OFDM symbols in a slot can be classified as 'downlink', 'flexible', or 'uplink'. Signaling of slot formats is described in subclause 11.1 of [TS 38.213],

[0054] In a slot in a downlink frame, the UE may assume that downlink transmissions only occur in 'downlink' or 'flexible' symbols. In a slot in an uplink frame, the UE may only transmit in 'uplink' or 'flexible' symbols.

[0055] Various examples of the systems and methods disclosed herein are now described with reference to the Figures, where like reference numbers may indicate functionally similar elements. The systems and methods as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different implementations. Thus, the following more detailed description of several implementations, as represented in the Figures, is not intended to limit scope, as claimed, but is merely representative of the systems and methods.

[0056] Figure 1 is a block diagram illustrating one configuration of one or more base stations 160 (e.g., eNB, gNB) and one or more user equipments (UEs) 102 in which systems and methods for reporting measurement results may be implemented. The one or more UEs 102 may communicate with one or more base stations 160 using one or more antennas 122a-n. For example, a UE 102 transmits electromagnetic signals to the base station 160 and receives electromagnetic signals from the base station 160using the one or more antennas 122a-n. The base station 160 communicates with the UE 102 using one or more antennas 180a-n.

[0057] It should be noted that in some configurations, one or more of the UEs 102 described herein may be implemented in a single device. For example, multiple UEs 102 may be combined into a single device in some implementations. Additionally or alternatively, in some configurations, one or more of the base stations 160 described herein may be implemented in a single device. For example, multiple base stations 160 may be combined into a single device in some implementations. In the context of Figure 1 , for instance, a single device may include one or more UEs 102 in accordance with the systems and methods described herein. Additionally or alternatively, one or more base stations 160 in accordance with the systems and methods described herein may be implemented as a single device or multiple devices.

[0058] The UE 102 and the base station 160 may use one or more channels 119, 121 to communicate with each other. For example, a UE 102 may transmit information or data to the base station 160 using one or more uplink (UL) channels 121 and signals. Examples of uplink channels 121 include a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH), etc. Examples of uplink signals include a demodulation reference signal (DMRS), a sounding reference signal (SRS) and a sounding reference signal for positioning (SRS for Positioning), etc. The one or more base stations 160 may also transmit information or data to the one or more UEs 102 using one or more downlink (DL) channels 119 and signals, for instance. Examples of downlink channels 119 include a PDCCH, a PDSCH, etc. A PDCCH can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH, where the Downlink Control Information (DC1) on PDCCH includes downlink assignment and uplink scheduling grants. The PDCCH is used for transmitting Downlink Control Information (DCI) in a case of downlink radio communication (radio communication from the base station to the UE). Here, one or more DCIs (may be referred to as DCI formats) are defined for transmission of downlink control information. Information bits are mapped to one or more fields defined in a DCI format. Examples of downlink signals include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a cell-specific reference signal (CRS), a non-zero power channel state information reference signal (NZP CSLRS), a zero-power channel state informationreference signal (ZP CSI-RS), and a downlink positioning reference signal (DL-PRS) etc. Other kinds of channels or signals may be used.

[0059] Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, one or more data buffers 104 and one or more UE operations modules 124. For example, one or more reception and / or transmission paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150 and modulator 154 are illustrated in the UE 102, though multiple parallel elements (e.g., transceivers 118, decoders 108, demodulators 114, encoders 150 and modulators 154) may be implemented.

[0060] The transceiver 118 may include one or more receivers (reception units) 120 and one or more transmitters (transmission units) 158. The one or more receivers 120 may receive signals (e.g., downlink channels, downlink signals, sidelink channels, sidelink signals) from the base station 160 or from another UE 102 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert signals to produce one or more received signals 116. The one or more received signals 116 may be provided to a demodulator 114. The one or more transmitters 158 may transmit signals (e.g., uplink channels, uplink signals, sidelink channels, sidelink signals) to the base station 160 or to another UE 102 using one or more antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit one or more modulated signals 156.

[0061] The demodulator 114 may demodulate the one or more received signals 116 to produce one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode signals. The decoder 108 may produce one or more decoded signals 106, 110. For example, a first UE-decoded signal 106 may comprise received payload data, which may be stored in a data buffer 104. A second UE-decoded signal 110 may comprise overhead data and / or control data. For example, the second UE-decoded signal 110 may provide data that may be used by the UE operations module 124 to perform one or more operations.

[0062] As used herein, the term “module” may mean that a particular element or component may be implemented in hardware, software or a combination of hardware and software. However, it should be noted that any element denoted as a “module”herein may alternatively be implemented in hardware. For example, the UE operations module 124 may be implemented in hardware, software or a combination of both.

[0063] In general, the UE operations module 124 may enable the UE 102 to communicate with the one or more base stations 160. The UE operations module 124 may include a UE RRC information configuration module 126. The UE operations module 124 may include a UE control module 128. In some implementations, the UE operations module 124 may include physical (PHY) entities, Medium Access Control (MAC) entities, Radio Link Control (RLC) entities, packet data convergence protocol (PDCP) entities, and a Radio Resource Control (RRC) entity. For example, the UE RRC information configuration module 126 may process RRC parameters for random access configurations, initial UL BWP configuration, CSI report configuration(s), and so on.

[0064] For a UE which is capable of implementing operations of AI / ML models and / or AI / ML functionalities, the UE operations module 124 may implement functions of Data Collection, Model Training, Management, Inference, and / or model storage.

[0065] The UE operations module 124 may provide information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the receiver(s) 120 when or when not to receive transmissions based on the Radio Resource Control (RRC) message (e.g., broadcasted system information, RRC reconfiguration message), MAC control element, SCI (Sidelink Control Information) and / or the DCI (Downlink Control Information). The UE operations module 124 may provide information 148, including the PDCCH monitoring occasions, DCI format size, PSCCH monitoring occasions and SCI format size, to the one or more receivers 120. The UE operation module 124 may inform the receiver(s) 120 when or where to receive / monitor the PDCCH candidate for DCI formats and / or the PSCCH candidate for SCI formats.

[0066] The UE operations module 124 may provide information 138 to the demodulator 114. For example, the UE operations module 124 may inform the demodulator 114 of a modulation pattern anticipated for transmissions from the base station 160.

[0067] The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of an anticipated encoding for transmissions from the base station 160. For example, the UEoperations module 124 may inform the decoder 108 of an anticipated PDCCH candidate encoding with which DCI size for transmissions from the base station 160.

[0068] The UE operations module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operations module 124 may instruct the encoder 150 to encode transmission data 146 and / or other information 142.

[0069] The encoder 150 may encode transmission data 146 and / or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction coding, mapping data to space, time and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide encoded data 152 to the modulator 154.

[0070] The UE operations module 124 may provide information 144 to the modulator 154. For example, the UE operations module 124 may inform the modulator 154 of a modulation type (e.g., constellation mapping) to be used for transmissions to the base station 160. The modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to the one or more transmitters 158.

[0071] The UE operations module 1 4 may provide information 140 to the one or more transmitters 158. This information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to transmit a signal to the base station 160. The one or more transmitters 158 may upconvert and transmit the modulated signal(s) 156 to one or more base stations 160.

[0072] The base station 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, one or more data buffers 162 and one or more base station operations modules 182. For example, one or more reception and / or transmission paths may be implemented in a base station 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109 and modulator 113 are illustrated in the base station 160, though multiple parallel elements (e.g., transceivers 176, decoders 166, demodulators 172, encoders 109 and modulators 113) may be implemented.

[0073] The transceiver 176 may include one or more receivers (reception units) 178 and one or more transmitters (transmission units) 117. The one or more receivers 178 may receive signals (e.g., uplink channels, uplink signals) from the UE 102 using oneor more antennas 180a-n. For example, the receiver 178 may receive and downconvert signals to produce one or more received signals 174. The one or more received signals 174 may be provided to a demodulator 172. The one or more transmitters 117 may transmit signals (e.g., downlink channels, downlink signals) to the UE 102 using one or more antennas 180a— n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

[0074] The demodulator 172 may demodulate the one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The base station 160 may use the decoder 166 to decode signals. The decoder 166 may produce one or more decoded signals 164, 168. For example, a first base station-decoded signal 164 may comprise received payload data, which may be stored in a data buffer 162. A second base station-decoded signal 168 may comprise overhead data and / or control data. For example, the second base station-decoded signal 168 may provide data (e.g., PUSCH transmission data) that may be used by the base station operations module 182 to perform one or more operations.

[0075] In general, the base station operations module 182 may enable the base station 160 to communicate with the one or more UEs 102. The base station operations module 182 may include a base station RRC information configuration module 194. The base station operations module 182 may include a base station control module 196 (or a base station processing module 196). The base station operations module 182 may include PHY entities, MAC entities, RLC entities, PDCP entities, and an RRC entity.

[0076] For a base station which is capable of implementing operations of AI / ML models and / or AI / ML functionalities, the base station operation 182 may implement functions of Data Collection, Model Training, Management, Inference, and / or model storage.

[0077] The base station operations module 182 may provide the benefit of performing PDCCH candidate search and monitoring efficiently. The base station operations module 182 may provide information 190 to the one or more receivers 178. For example, the base station operations module 182 may inform the receiver(s) 178 when or when not to receive transmissions based on the RRC message (e.g., broadcasted system information, RRC reconfiguration message), MAC control element, and / or the DCI (Downlink Control Information).

[0078] The base station operations module 182 may provide information 188 to the demodulator 172. For example, the base station operations module 182 may inform the demodulator 172 of a modulation pattern anticipated for transmissions from the UE(s) 102.

[0079] The base station operations module 182 may provide information 186 to the decoder 166. For example, the base station operations module 182 may inform the decoder 166 of an anticipated encoding for transmissions from the UE(s) 102.

[0080] The base station operations module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and / or instructions for encoding. For example, the base station operations module 182 may instruct the encoder 109 to encode transmission data 105 and / or other information 101.

[0081] In general, the base station operations module 182 may enable the base station 160 to communicate with one or more network nodes (e.g., a NG mobility management function, a NG core UP functions, a mobility management entity (MME), serving gateway (S-GW), gNBs). The base station operations module 182 may also generate a RRC reconfiguration message to be signaled to the UE 102.

[0082] The encoder 109 may encode transmission data 105 and / or other information 101 provided by the base station operations module 182. For example, encoding the data 105 and / or other information 101 may involve error detection and / or correction coding, mapping data to space, time and / or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide encoded data 111 to the modulator 113. The transmission data 105 may include network data to be relayed to the UE 102.

[0083] The base station operations module 182 may provide information 103 to the modulator 113. This information 103 may include instructions for the modulator 113. For example, the base station operations module 182 may inform the modulator 113 of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) 102. The modulator 113 may modulate the encoded data 111 to provide one or more modulated signals 115 to the one or more transmitters 117.

[0084] The base station operations module 182 may provide information 192 to the one or more transmitters 117. This information 192 may include instructions for the one or more transmitters 117. For example, the base station operations module 182 may instruct the one or more transmitters 117 when to (or when not to) transmit a signal tothe UE(s) 102. The base station operations module 182 may provide information 192, including the PDCCH monitoring occasions and DCI format size, to the one or more transmitters 117. The base station operation module 182 may inform the transmitter(s) 117 when or where to transmit the PDCCH candidate for DCI formats with which DCI size. The one or more transmitters 117 may upconvert and transmit the modulated signal(s) 115 to one or more UEs 102.

[0085] It should be noted that one or more of the elements or parts thereof included in the base station(s) 160 and UE(s) 102 may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.

[0086] Abase station may generate a RRC message including the one or more RRC parameters and may transmit the RRC message to a UE. A UE may receive, from a base station, a RRC message including one or more RRC parameters. In the present disclosure, the terms ‘RRC parameter(s)’, ‘RRC information element(s)’, ‘higher layer parameter(s)’ can be used interchangeably. In the present disclosure, higher layer may refer to a layer upper than the physical layer (i.e., Layer 1), for example, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and / or application layer.

[0087] A higher-layer parameter is a parameter included in an RRC message, LPP message, NRPPa message or a MAC CE (Medium Access Control Control Element). The higher-layer parameter is a generic name of information included in a MIB, system information, a message which corresponds to CCCH, a message which corresponds to DCCH, and a MAC CE. A higher-layer parameter may be referred to as an RRC parameter or an RRC configuration if the higher-layer parameter is the parameter included in the RRC message. A higher-layer parameter may be referred to as an LPP parameter or an LPP configuration if the higher-layer parameter is the parameter included in the LPP message. A higher-layer parameter may be referred to as an NRPPa parameter or an NRPPa configuration if the higher-layer parameter is the parameter included in the NRPPa message.

[0088] A RRC parameter may further include one or more RRC parameter(s). In the present disclosure, a RRC message may include system information. A RRC message may include one or more RRC parameters. A RRC message may be sent on a broadcast control channel (BCCH) logical channel, a common control channel (CCCH) logical channel or a dedicated control channel (DCCH) logical channel.

[0089] A LPP parameter may further include one or more LPP parameter(s). In the present disclosure, a LPP message may include system information. A LPP message may include one or more LPP parameters. A LPP message may be sent on a broadcast control channel (BCCH) logical channel, a common control channel (CCCH) logical channel or a dedicated control channel (DCCH) logical channel.

[0090] ANRPPa parameter may further include one or more NRPPa parameter(s). In the present disclosure, a NRPPa message may include system information. ANRPPa message may include one or more NRPPa parameters. A NRPPa message may be sent on a broadcast control channel (BCCH) logical channel, a common control channel (CCCH) logical channel or a dedicated control channel (DCCH) logical channel.

[0091] In the present disclosure, a description “a UE is configured with or is provided a parameter” also implies the description “the UE may receive, from the base station, an RRC or NRPPa message (or information) which includes the parameter”. Likewise, the description “a base station configures the UE with or provides the UE the parameter” also implies the description “the base station may transmit, to the UE, an RRC or LPP message (or information) which includes the parameter”.

[0092] Figure 2 is a diagram illustrating one example of a resource grid 200.

[0093] For each numerology (i.e., for each SCS u) and carrier, a resource grid ofsubcarriers and OFDM symbols is defined, starting atcommon resource block Agridstort, / / indicated by higher layer signaling. There is one set of resource grids per transmission direction (uplink or downlink) with the subscript x set to DL and UL for downlink and uplink, respectively. There is one resource grid for a given antenna port p, subcarrier spacing configuration p, and the transmission direction (downlink or uplink). When there is no risk for confusion, the subscript x may be dropped.

[0094] In the Figure 2, the resource gird 200 includes the (202)subcarriers in the frequency domain and includes Nsymbsub^ame,tl(204) symbols in the time domain. In the Figure 2, as an example for illustration, the subcarrier spacingconfigurationp s set to 0. That is, in the Figure 2, the number of consecutive OFDM symbols(204) per subframe is equal to 14.

[0095] The carrier bandwidth for subcarrier spacingconfiguration / / is given by the higher-layer (RRC) parameter carrierBandwidth in the SCS-SpecificCarrier IE. The starting position for subcarrier spacingconfiguration p is given by the higher-layer parameter offsetToCarrier in the SCS- SpecificCarrier IE. The frequency location of a subcarrier refers to the center frequency of that subcarrier.

[0096] In the Figure 2, for example, a value of offset is provided by the higher-layer parameter offsetToCarrier. That is, k= 12 X offset is the lowest usable subcarrier on this carrier.

[0097] Each element in the resource grid for antenna port p and subcarrier spacing configuration p is called a resource element and is uniquely identified by wherek is the index in the frequency domain and I refers to the symbols position in the time domain relative to same reference point. The resource element consists of one subcarrier during one OFDM symbol.

[0098] A resource block is defined asconsecutive subcarriers in the frequency domain. As shown in the Figure 2, a resource block 206 includes 12 consecutive subcarriers in the frequency domain. Resource block can be classified as common resource block (CRB) and physical resource block (PRB).

[0099] Common resource blocks are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration p. The center of subcarrier 0 of common resource block with index 0 (i.e. CRB0) for subcarrier spacing configuration p coincides with point A. The relation between the common resource block number infrequency domain and resource element (k, I) for subcarrier spacingconfiguration p is given by Formula where k is defined relativeto the point A such that &=0 corresponds to the subcarrier centered around the point A. The function floor(A) hereinafter is floor operation to output a maximum integer not larger than the A.

[0100] Point A refers to as a common reference point. Point A coincides with subcarrier 0 (i.e., Zr O) of a CRB 0 for all subcarrier spacing. Point A can be obtained from a RRC parameter offsetToPointA or a RRC parameter absoluteFrequencyPointA.The RRC parameter offsetToPointA is used for a PCell downlink and represents the frequency offset between point A and the lowest subcarrier of the lowest resource block, which has the subcarrier spacing provided by a higher-layer parameter subCarrierSpacingCommon and overlaps with the SS / PBCH block used by the UE for initial cell selection, expressed in units of resource blocks assuming 15 kHz subcarrier spacing for frequency range (FR) 1 and 60 kHz subcarrier spacing for frequency range (FR2). FR1 corresponds to a frequency range between 410MHz and 7125MHz. FR2 corresponds to a frequency range between 24250MHz and 52600MHz. The RRC parameter absoluteFrequencyPointA is used for all cased other than the PCell case and represents the frequency-location of point A expressed as in ARFCN. The frequency location of point A can be the lowest subcarrier of the carrier bandwidth ( or the actual carrier). Additionally, point A may be located outside the carrier bandwidth ( or the actual carrier).

[0101] As above mentioned, the information element (IE) SCS-SpecificCarrier provides parameters determining the locati on and width of the carrier bandwidth or the actual carrier. That is, a carrier (or a carrier bandwidth, or an actual carrier) is determined (identified, or defined) at least by a RRC parameter offsetToCarrier, a RRC parameter subcarrierSpacing, and a RRC parameter carrier Bandwidth in the SCS- SpecificCarrier IE.

[0102] The subcarrierSpacing indicates (or defines) a subcarrier spacing of the carrier. The offsetToCarrier indicates an offset in frequency domain between point A and a lowest usable subcarrier on this carrier in number of resource blocks (e.g. CRBs) using the subcarrier spacing defined for the carrier. The carrierBandwidth indicates width of this carrier in number of resource blocks (e.g., CRBs or PRBs) using the subcarrier spacing defined for the carrier. A carrier includes at most 275 resource blocks.

[0103] Physical resource blocks for subcarrier spacing configuration p are defined within a bandwidth part and numbered form 0 to where i is the number of thebandwidth part. The relation between the physical resource block npif1in bandwidth part (BWP) i and the common resource block ncnf is given by Formula (2)is the common resource block where bandwidth part i starts relative to common resource block 0 (CRB0). When there is no risk for confusion the index p may be dropped.

[0104] A BWP is a subset of contiguous common resource block for a given subcarrier spacing configuration / / on a given carrier. To be specific, a BWP can be identified (or defined) at least by a subcarrier spacing p indicated by the RRC parameter subcarrierSpacing, a cyclic prefix determined by the RRC parameter cyclicPrefix, a frequency domain location, a bandwidth, an BWP index indicated by bwp-Id and so on. The locationAndBandwidth can be used to indicate the frequency domain location and bandwidth of a BWP. The value indicated by the locationAndBandwidth is interpreted as resource indicator value (RIV) corresponding to an offset (a starting resource block) RB$\srt and a length ZRB in terms of contiguously resource blocks. The offset 7^Bstart is a number of CRBs between the lowest CRB of the carrier and the lowest CRB of the BWP. The is given as Formula (3) N The value ofOcarrier is provided by offsetTocarrier for the corresponding subcarrier spacing configuration p.

[0105] A UE 102 configured to operate in BWPs of a serving cell, is configured by higher layers for the serving cell a set of at most four BWPs in the downlink for reception. At a given time, a single downlink BWP is active. The bases station 160 may not transmit, to the UE 102, PDSCH and / or PDCCH outside the active downlink BWP. A UE 102 configured to operate in BWPs of a serving cell, is configured by higher layers for the serving cell a set of at most four BWPs for transmission. At a given time, a single uplink BWP is active. The UE 102 may not transmit to the base station 160, PUSCH or PUCCH outside the active BWP. The specific signaling (higher layers signaling) for BWP configurations are described later.

[0106] Figure 3 is a diagram illustrating one example 300 of common resource block grid, carrier configuration and BWP configuration by a UE 102 and a base station 160.

[0107] Point A 301 is the lowest subcarrier of a CRB0 for all subcarrier spacing configurations. The CRB grid 302 and the CRB grid 312 are corresponding to two different subcarrier spacing configurations. The CRB grid 302 is for subcarrier spacing configuration p =0 (i.e., the subcarrier spacing with 15kHz). The CRB grid 312 is for subcarrier spacing configuration p -1 (i.e., the subcarrier spacing with 30kHz).

[0108] One or more carriers are determined by respective SCS-SpecificCarrier lEs, respectively. In the Figure 3, the carrier 304 uses the subcarrier spacing configuration / / =0. And the carrier 314 uses the subcarrier spacing configuration p=\ . The startingpositionof the carrier 304 is given based on the value of an offset 303 (i.e. O carrier) indicated by an offsetToCarrier in an SCS-SpecificCarrier IE. As shown in the Figure 3, for example, the offsetToCarrier indicates the value of the offset 303 as O=3. That is, the starting positionof the carrier 304 corresponds to the CRB3 of the CRB grid 302 for subcarrier spacing configuration In the meantime, thestarting position A of the carrier 314 is given based on the value of an offset 313(i.e. Ocamer) indicated by an offsetToCarrier in another SCS-SpecificCarrier IE. For example, the offsetToCarrier indicates the value of the offset 313 as Ocamer =1. That is, the starting positionof the carrier 314 corresponds to the CRB1 of the CRB grid 312 for subcarrier spacing configuration p=\. A carrier using different subcarrier spacing configurations can occupy different frequency ranges.

[0109] As above-mentioned, a BWP is for a given subcarrier spacing configuration p. One or more BWPs can be configured for a same subcarrier spacing configuration p. For example, in the Figure 3, the BWP 306 is identified at least by thea frequency domain location, a bandwidth (ZRB), and an BWP index (index A). The first PRB (i.e. PRB0) of a BWP is determined at least by the subcarrier spacing of the BWP, an offset derived by the locationAndBandwidth and an offset indicated by the offsetToCarrier corresponding to the subcarrier spacing of the BWP. An offset 305 (TLBstart) is derived as 1 by the locationAndBandwidth. According to the Formulas (2) and (3), the PRB0 of BWP 306 corresponds to CRB 4 of the CRB grid 302, and the PRB1 of BWP 306 corresponds to CRB 5 of the CRB grid 302, and so on.

[0110] Additionally, in the Figure 3, the BWP 308 is identified at least by the p=0, a frequency domain location, a bandwidth (ZRB), and an BWP index (index B). For example, an offset 307 (Restart) is derived as 6 by the locationAndBandwidth. According to the Formulas (2) and (3), the PRB0 of BWP 308 corresponds to CRB 9 of the CRB grid 302, and the PRB1 of BWP 308 corresponds to CRB 10 of the CRB grid 302, and so on.

[0111] Additionally, in the Figure 3, the BWP 316 is identified at least by the p=l, a frequency domain location, a bandwidth (ZRB), and an BWP index (index C). For example, an offset 315 (Restart) is derived as 1 by the locationAndBandwidth. According to the Formulas (2) and (3), the PRB0 of BWP 316 corresponds to CRB 2 of the CRB grid 312, and the PRB1 of BWP 316 corresponds to CRB 3 of the CRB grid 312, and so on.

[0112] In the present disclosure, a BWP illustrated in the Figure 3 may refer to a DL BWP, a UL BWP, or a sidelink BWP.

[0113] As shown in the Figure 3, a carrier with the defined subcarrier spacing locate in a corresponding CRB grid with the same subcarrier spacing. A BWP with the defined subcarrier spacing locate in a corresponding CRB grid with the same subcarrier spacing as well.

[0114] A base station may transmit a RRC message including one or more RRC parameters related to BWP configuration to a UE. A UE may receive the RRC message including one or more RRC parameters related to BWP configuration from a base station. For each cell, the base station may configure at least an initial DL BWP, one initial uplink bandwidth parts (initial UL BWP) and one sidelink BWP to the UE. Furthermore, the base station may configure additional UL and DL BWPs to the UE for a cell.

[0115] SIB1, which is a cell-specific system information block (SystemlnformationBlock, SIB), may contain information relevant when evaluating if a UE is allowed to access a cell and define the scheduling of other system information. SIB1 may also contain radio resource configuration information that is common for all UEs, and barring information applied to the unified access control. The RRC parameter ServingCellConfigCommon is used to configure cell specific parameters of a UE's serving cell. The RRC parameter ServingCellConfig is used to configure (add or modify) the UE with a serving cell, which may be the SpCell or an SCell of an MCG or SCG. The RRC parameter ServingCellConfig herein are mostly UE specific but partly also cell specific.

[0116] The base station may configure the UE with a RRC parameter BWP- Downlink and a RRC parameter BWP -Uplink. The RRC parameter BWP -Downlink can be used to configure an additional DL BWP. The RRC parameter BWP-Uplink can be used to configure an additional UL BWP.' The base station may transmit the BWP- Downlink and the BWP-Uplink which may be included in RRC parameter ServingCellConfig to the UE.

[0117] The UE may be configured by the based station, at least one initial BWP and up to 4 additional BWP(s). One of the initial BWP and the configured additional BWP(s) may be activated as an active BWP. The UE may monitor DCI format, and / or receive PDSCH in the active DL BWP. The UE may not monitor DCI format, and / orreceive PDSCH in a DL BWP other than the active DL BWP The UE may transmit PUSCH and / or PUCCH in the active UL BWP. The UE may not transmit PUSCH and / or PUCCH in a BWP other than the active UL BWP.

[0118] As above-mentioned, a UE may monitor DO format in the active DL BWP. To be more specific, a UE may monitor a set of PDCCH candidates in one or more CORESETs on the active DL BWP on each activated serving cell configured with PDCCH monitoring according to corresponding search space set where monitoring implies decoding each PDCCH candidate according to the monitored DCI formats.

[0119] A set of PDCCH candidates for a UE to monitor is defined in terms of PDCCH search space sets. A search space set can be a CSS set or a USS set. A UE may monitor a set of PDCCH candidates in one or more of the search space sets.

[0120] Hereinafter, NR positioning methods, DL-TDOA, UL-TDOA, Multi-RTT, DL-AoD and UL-AoA, are described. NR positioning methods are not limited to those described in this embodiment.

[0121] In the DL-Time Difference Of Arrival (DL-TDOA) positioning method, the UE position may be estimated based on DL RSTD (and optionally DL-PRS-RSRP and / or DL-PRS-RSRPP and / or DL-RSCPD) measurements taken at the UE of downlink radio signals from multiple NR TRPs, along with knowledge of the geographical coordinates of the TRPs and their relative downlink timing. The UE while connected to a gNB may require measurement gaps to perform the DL-TDOA measurements from NR TRPs. The UE may request measurement gaps from a gNB. The UE may also request to activate pre-configured measurement gaps. The specific positioning techniques used to estimate the UE's location from this information are beyond the scope of this specification.

[0122] In the UL-Time Difference Of Arrival (UL-TDOA) positioning method, the UE position may be estimated based on UL-RTOA (and optionally UL-SRS-RSRP and / or UL-SRS-RSRPP and / or UL-RSCP) measurements taken at different TRPs of uplink radio signals from UE, along with other configuration information. In order to obtain uplink measurements, the TRPs may need to know the characteristics of the SRS signal transmitted by the UE for the time period required to perform uplink measurement. These characteristics maybe static over the periodic transmission of SRS during the uplink measurements. Hence, the LMF may indicate to the serving gNB the need to direct the UE to transmit SRS signals for uplink positioning. It may be up to theserving gNB to make the final decision on resources to be assigned and to communicate this SRS configuration information back to the LMF so that LMF can forward the SRS configuration to the TRPs. The gNB may decide (e.g., in case no resources are available) to configure no resources for the UE and may report the empty resource configuration to the LMF.

[0123] In the Multi-Round Trip Time (Multi-RTT) positioning method, the UE position may be estimated based on measurements performed at both, UE and TRPs. The measurements may be performed at the UE and TRPs are UE / gNB Rx-Tx time difference measurements (and optionally DL-PRS-RSRP, DL-PRS-RSRPP, UL-SRS- RSRP, UL-SRS-RSRPP, and / or DL-RSCP / UL-RSCP) of DL-PRS and UL-SRS, which may be used by an LMF to determine the RTTs. The additional measurements performed at UE may be the UE Rx - Tx time difference subframe offset in unit of subframe and the DL timing drift due to Doppler in service link between UE and satellite. The UE may require measurement gaps to perform the Multi-RTT measurements from NR TRPs. The UE may request measurement gaps from a gNB. The UE may also request to activate pre-configured measurement gaps.

[0124] In the DL-Angle of Departure (AoD) positioning method, the UE position may be estimated based on DL-PRS-RSRP and / or DL-PRS-RSRPP measurements taken at the UE of downlink radio signals from multiple NR TRPs, along with knowledge of the spatial information of the downlink radio signals and geographical coordinates of the TRPs. The UE while connected to a gNB may require measurement gaps to perform the DL-AoD measurements from NR TRPs. The UE may request measurement gaps from a gNB. The UE may also request to activate pre-configured measurement gaps.

[0125] In the UL- Angle of Arrival (AoA) positioning method, the UE position may be estimated based on UL-AoA (and optionally UL-SRS-RSRP and / or UL-SRS- RSRPP) of uplink radio signals taken at different TRPs, along with other configurati on information. In order to obtain uplink measurements, the TRPs may need to know the characteristics of the SRS signal transmitted by the UE for the time period required to calculate uplink measurement. These characteristics may be static over the periodic transmission of SRS during the uplink measurements. Hence, the LMF may indicate to the serving gNB the need to direct the UE to transmit SRS signals for uplink positioning. It may be up to the gNB to make the final decision on resources to be assigned and tocommunicate this configuration information back to the LMF so that LMF can configure the TRPs. The gNB may decide (e.g., in case no resources are available) to configure no resources for the UE and fail the corresponding NRPPa procedure.

[0126] Hereinafter, measurements for NR positioning are described. Measurements for NR positioning are not limited to those described in this embodiment.

[0127] DL reference signal time difference (DL RSTD) may be the DL relative timing difference between the Transmission Point (TP) j and the reference TP i, defined as where: may be the time when theUE receives the start of one subframe from TP j. may be the time whenthe UE receives the corresponding start of one subframe from TP i that is closest in time to the subframe received from TP j. Multiple DL PRS resources may be used to determine the start of one subframe from a TP.

[0128] The UL Relative Time of Arrival (UL-RTOA or TUL-RTOA) may be the beginning of subframe i containing SRS received in Reception Point (RP) j, relative to the RTOA Reference Time. The UL RTOA Reference Time is defined aswhere may be the nominal beginning time of SFN 0 provided by SFN InitializationTime, and where may be the system framenumber and the subframe number of the SRS, respectively. Multiple SRS resources may be used to determine the beginning of one subframe containing SRS received at a RP.

[0129] The gNB Rx - Tx time difference is defined aswhere: may be the Transmission and Reception Point (TRP) receivedtiming of uplink subframe #i containing SRS associated with UE, defined by the first detected path in time. may be the TRP transmit timing of downlinksubframe that is closest in time to the subframe #i received from the UE. Multiple SRS resources may be used to determine the start of one subframe containing SRS.

[0130] UE Rx - Tx time difference subframe offset is the index difference which represents the number of subframes between the uplink subframe #j and the uplink subframe #i, where uplink subframej is the closest in time to the DL subframe #i received from a transmission point (TP) and i is the index of the DL subframe used for the UE Rx - Tx time difference measurement.

[0131] For downlink measurements, the UE may be requested, subject to UE capability, to report LoS / NLoS indicator(s) via higher layer parameter nr-los-nlos-Indicator Request. The UE may report LoS / NLoS indicator(s) via higher layer parameter nr-los-nlos-Indicator associated with each DL RSTD, DL PRS-RSRP, DL PRS-RSRPP, and UE Rx-Tx time difference measurements. The UE may report LoS / NLoS indicator(s) via higher layer parameter nr-los-nlos-Indicator associated with each dl-PRS-ID in a measurement report. For the LoS / NLoS indicator(s) associated with DL RSTD, the UE may report one indicator associated with the dl-PRS-ID indicated by higher layer parameter dl-PRS-Referencelnfo and one indicator associated with the dl-PRS-ID of the DL RSTD measurement. A UE may be provided with LoS / NLoS indicator(s) via higher layer parameter nr-los-nlos-Indicator , and it may be associated with each DL PRS resource of each configured dl-PRS-ID or may be associated with each configured dl-PRS-ID. The values of the higher layer parameter LOS-NLOS-Indicator may be soft values (0, 0.1, ..., 0.9, 1) or hard values (0, 1) with the values corresponding to the likelihood of LoS, with a value of 1 corresponding to LoS and a value of 0 corresponding to NLoS.

[0132] For uplink measurements, the gNB may be requested, subject to gNB capability, to report LoS / NLoS indicator(s) via higher layer parameter LoS / NLoS Information. The gNB may report LoS / NLoS indicator(s) via higher layer parameter LoS / NLoS Information associated with each UL RTOA, UL SRS-RSRP, UL SRS- RSRPP, and gNB Rx-Tx time difference measurements. The values of the higher layer parameter LOS-NLOS-Indicator contained in LoS / NLoS Information may be soft values (0, 0.1, ..., 0.9, 1) or hard values (0, 1) with the values corresponding to the likelihood of LoS, with a value of 1 corresponding to LoS and a value of 0 corresponding to NLoS.

[0133] The UE may be configured to measure and report via higher layer parameter additional? aths or additional? athsExt, subject to UE capability, the timing and the quality metrics of up to 8 additional detected paths, that are associated with each DL RSTD or UE Rx - Tx time difference. The timing of each additional path may be reported relative to the path timing used for determining nr-RSTD or nr-UE- RxTxTimeDiff. For UE positioning measurement reporting in higher layer parameters NR-DL-TDOA-SignalMeasurementlnformation or NR-Multi-RTT-SignalMeasurementlnformation, the UE may be configured to measure and report, subject to UE capability, the DL PRS-RSRPP of the first path and the up to 8 additionalpaths that are associated with each RSTD or UE Rx - Tx time difference. For the purpose of AI / ML based positioning, the number of maximum additional paths may be larger than 8.

[0134] In present disclosure, above positioning measurement(s) (i.e. LOS / NLOS indicator, DL-RTOA, UL-RTOA, DL-RSTD, UL-RSTD, gNB Rx-Tx time difference, UE Rx-Tx time difference, DL-AoD and UL-AoA) which is not generated by AI / ML can be referred to as legacy positioning measurement(s).

[0135] Hereinafter, reference signals for NR positioning are described. Measurements for NR positioning are not limited to those described in this embodiment.

[0136] The DL Positioning Reference Singal (DL PRS) may be defined to facilitate support of different positioning methods such as DL-TDOA, DL-AoD, multi-RTT through the following set ofUE measurements DLRSTD, DLPRS-RSRP, and UE Rx- Tx time difference respectively. Besides DL PRS signals, UE may be use SSB and CSL RS for RRM (RSRP and RSRQ) measurement for E-CID type of positioning.

[0137] A positioning frequency layer consists of one or more downlink PRS resource sets, each of which consists of one or more downlink PRS resources.

[0138] The UE may expect that it will be configured with dl-PRS-ID each of which is defined such that it is associated with multiple DL PRS resource sets. The UE may expect that one of these dl-PRS-ID along with a ID of DL PRS resource set (nr-DL- PRS-ResourceSetlD) and a ID of DL PRS resource (nr-DL-PRS-ResourcelD-rl 6) can be used to uniquely identify a DL PRS resource.

[0139] The UE may be configured by the network with nr-PhysCelllD, nr- CellGloballD, and nr-ARFCN associated with a dl-PRS-ID.If nr-PhysCelllD or nr-CellGloballD is provided, and if nr-PhysCelllD, nr- CellGloballD and nr-ARFCN associated with the dl-PRS-ID, if provided, are the same as the corresponding information of a serving cell, the UE may assume that the DLPRS is transmitted from the serving cell;Otherwise, the UE may assume that the DL PRS is not transmitted from a serving cell.

[0140] The periodic, semipersistent and aperiodic transmission SRS may be defined for gNB ULRTOA, UL SRS-RSRP, UL-AoA measurements to facilitate support of UL TDOA and UL AoA positioning methods.

[0141] The periodic, semipersistent and aperiodic transmission of SRS for positioning may be defined for gNB UL RTOA, UL SRS-RSRP, UL-AoA, gNB Rx-Tx time difference measurements to facilitate support of UL TDOA, UL AoA and multi- RTT positioning methods.

[0142] Area ID may identify the UE location of a measurement that sent with it. For example, the Area ID may be provided by the IE ArealD-CellList. The IE ArealD- CellList provides the NR Cell-IDs of the TRPs belonging to a particular network area where the associated assistance data are valid. Each cell is included in only one area. The IE ArealD-CellList may consist of one or more of IE NR-Cell-LDs. The NR-Cell- LDs may include nr-CellGlobalLD, nr-PhysCelllD and nr-ARFCN. The nr- CellGloballD may specify the NR Cell Global ID of the TRP belonging to a particular network area where the associated assistance data are applicable. The nr-PhysCelllD may specify the physical cell identity of the TRP belonging to a particular network area where the associated assistance data are applicable. The nr-ARFCN specify the NR- ARFCN of the TRP's CD-SSB corresponding to nr-PhysCellLD.

[0143] Quality indicator may indicate the quality of a measurement that sent with it. For example, the Quality indicator may be provided by the IE NR-TimingQuality. The IE NR-TimingQuality may define the quality of a timing value (e.g., of a Time Of Arrival (TOA) measurement). The IE NR-TimingQuality may include timingQualityValue and timingQuality Resolution. The timingQualityValue may provide an estimate of uncertainty of the timing value for which the IE NR-TimingQuality is provided in units of metres. The timingQualityResolution may provide the resolution used in the timingQualityValue field. Enumerated values mdotl, ml, mlO, m30 correspond to 0.1, 1, 10, 30 metres, respectively.

[0144] Time stamp may indicate the timing of a measurement that sent with it. For example, the Time stamp may be provided by the IE NR-TimeStamp. The IE NR- TimeStamp may define the UE measurement associated time stamp. The NR-TimeStamp may include dl-PRS-ID, nr-PhysCelllD, nr-CellGloballD, nr-ARFCN, nr-SFN, nr-Slot and nr-Symbol. The nr-SFN may specify the NR system frame number for the time stamp. The nr-Slot may specify the NR slot number within the NR system frame number indicated by nr-SFN for the time stamp. The nr-Symbol may specify the NR symbol index within the NR slot number indicated by nr-Slot for the time stamp.

[0145] LOS indicator may indicate the associated measurement is measured in LOS environment.

[0146] Hereinafter, method of positioning using AI / ML is described. The method of positioning using AI / ML can be referred to as AI / ML based positioning, AI / ML positioning.

[0147] Figure 4 is a diagram illustrating one 400 example of functional framework for AI / ML for NR air interface by a UE 102 and a base station 160.

[0148] As illustrated in the Figure 4, the AI / ML functional framework for the NR air interface includes a set of core functions, including Data Collection 401, Model Training 402, Management 403, Inference 404, and model storage 405.

[0149] The Data Collection 401 is a function that provides input data to the Model Training, Management, and Inference functions. Specifically, the Data Collection 401 function may provide training data to the Model Training function. That is, the training data refers to data needed as input for the AI / ML Model Training function. The Data Collection 401 function may provide monitoring data to the Management function. That is, the monitoring data refers to data needed as input for the Management of AI / ML Models or AI / ML functionalities. The Data Collection 401 function may provide inference data to the Inference function. That is, the inference data refers to data needed as input for the AI / ML Inference function.

[0150] The Model Training function 402 is a function that performs AI / ML model training, validation, and testing which may generate model performance metrics which can be used as part of the model testing procedure. The Model Training function is also responsible for data preparation based on training data delivered by the Data Collection function. In case of having a Model Storage function 405, the trained, validated, and tested AI / ML models may be delivered to the Model Storage function. Additionally, an updated version of a model may be also delivered to the Model Storage function.

[0151] The Management function 403 is a function that oversees the operation (e.g., selection / (de)activation / switching / fallback) and monitoring (e.g., performance) of AI / ML models or AI / ML functionalities. This function is also responsible for making decisions to ensure the proper inference operation based on data received from the Data Collection function and the Inference function.

[0152] The Inference function 404 is a function that provides outputs from the process of applying AI / ML models or AI / ML functionalities, using the data that isprovided by the Data Collection function (i.e., Inference Data) as an input. The Inference function is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on Inference Data delivered by a Data Collection function, if required.

[0153] The Model Storage 405 is a function responsible for storing trained / updated models that can be used to perform the Inference function.

[0154] In the present disclosure, the functional framework illustrated in the Figure 4 provides a general functional architecture that can be applied to both AI / ML model and AI / ML functionalities.

[0155] An AI / ML model or an AI / ML functionality needs to be developed, deployed, and managed during the entire lifecycle, i.e., AI / ML model-based life cycle management (LCM) or AI / ML functionality-based LCM.

[0156] An AI / ML model may be identified by a model ID. A model ID is a distinctive identifier for an AI / ML model. The model ID may be a logical ID. A logical AI / ML model refers to a model that is identified and assigned a model ID. The logical AI / ML model can be mapped to a physical AI / ML model by implementation. That is, a physical AI / ML model refers to an actual implementation of a logical AI / ML model.

[0157] In AI / ML model-based LCM, models are identified at the network, and the network and / or the UE may activate, deactivate, select, or switch individual AI / ML models via model ID. In the present disclosure, the AI / ML model-based LCM can be referred to as model-ID-based LCM.

[0158] An AI / ML functionality is a functionality defined within an AI / ML-enabled feature whereby AI / ML-enabled feature refers to a feature where AI / ML may be used. A UE, gNB or LMF may have one AI / ML model for one functionality or may have multiple AI / ML models for one functionality.

[0159] In AI / ML functionality-based LCM, the UE may indicate its supported functionalities by using UE capability signaling to network. Additionally, the UE may also indicate its applicable functionalities that the UE is ready to apply for model inference. Upon reception of UE capability signaling, the network may indicate activation, deactivation, fallback, and / or switching of an AI / ML functionality through signaling such as RRC signaling, MAC CE, DCI. The exact AI / ML model that underpin a given functionality might not be identified at the network.

[0160] In the present disclosure, the UE 102 and / or the base station 160 may apply the AI / ML model and / or the AI / ML functionalities for positioning accuracy enhancement

[0161] The AI / ML based positioning may be classified into two. One is direct AI / ML positioning (also can be referred to as AI / ML direct positioning), the other one is AI / ML assisted positioning (also can be referred to as Assisted AI / ML positioning).

[0162] In case of the direct AI / ML positioning and AI / ML assisted positioning, the input of the AI / ML model may be channel measurement. The channel measurement may be classified three types of measurement: time-domain channel impulse response (CIR), power delay profile (PDP) and delay profile (DP). The UE 501a and the UE 501b may generate CIR, PDP or DP by measuring DL-PRS, CSI-RS or SSB. The NG- RAN node 502 may generate CIR, PDP or DP by measuring UL-SRS for positioning or UL-SRS.

[0163] The CIR may have the largest measurement size, where CIR is composed of a list of measurements where each measurement contains the information of delay, power and phase. The PDP may have smaller measurement size than CIR, where PDP is composed of a list of measurements where each measurement contains the information of delay and power. The DP may have the smallest measurement size, where DP is composed of a list of measurements where each measurement contains the information of delay.

[0164] For the model input used for AI / ML based positioning, if CIR or PDP is used as model input, the input dimension may be N_TRP * N_port * N_t, where N 1 RP is the number of TRPs, N_port is the number of transmit / receive antenna port pairs, N_t is the number of consecutive time domain samples. If subsampling is applied for the model input, N’_t (N’_t < N_t) samples with the strongest power within the N_t samples may be selected as model input, with remaining (N_t - N’_t) time domain samples may set to zero. It may be also assumed that timing info for the N’_t samples need to be provided as model input. By applying subsampling of the measurement, the overhead of the measurement report may be reduced.

[0165] For example, when time domain samples are used as model input and subsampling is applied, the selection of N'_t measurements may be based on the strongest power, unless explicitly stated otherwise. When sub-sampling is applied the N'_t measurement may be not necessarily consecutive in time.

[0166] Dataset may consist of one or more data, where the data may include either measurements or label, or both. Training dataset may refer the dataset for the Model Training function. Test dataset may refer the dataset for the test of the model. Inference dataset may refer the dataset for the Inference function. Monitoring dataset may refer the dataset for the Management function.

[0167] Training dataset, test dataset, inference dataset and monitoring dataset may use the same measurement selection method (e.g., strongest power).

[0168] For AI / ML based positioning, when timing information is included in model input (e.g., in CIR / PDP / DP), training dataset, test dataset, inference dataset and monitoring dataset may use the same timing format (i.e., both are absolute time, or both are relative time).

[0169] If the model input is the CIR, then each input value of the CIR may be a complex number, i.e., it may contain two real values, either {real, imaginary} or {magnitude, phase}. If the model input is the PDP, then each input value of the PDP may be a real value.

[0170] For each model input type (CIR, PDP, DP), the measurement size may increase approximately linearly as N'_TRP increases, where N'_TRP is the number of active TRPs that provide measurements for the positioning. The measurement size may increase approximately linearly as N_port increases, where N_port is the number of transmit / receive antenna port pairs that provide measurements for the positioning. If N'_t (N'_t < N_t) measurements are selected as model input, measurement size for model input may increase approximately linearly with N'_t. For model input type CIR and PDP, if the full set of N_t measurements in time domain is used as model input, measurement size for model input may increase approximately linearly with NJ. If DP is used as model input, DP may not use full set of N_t measurements in time domain (i.e., N'_t < N_t always). The model input dataset for training, inference or performance monitoring may be provided in the dataset message.

[0171] For both the direct AI / ML positioning and AI / ML assisted positioning, there may be the trade-off among model performance, model complexity and computational complexity.

[0172] For the direct AI / ML positioning, the AI / ML model may output the UE location coordination. The UE location coordination can be reported to the LMF using LPP protocol.

[0173] For the AI / ML assisted positioning, the output of the AI / ML model may be the intermediate positioning measurement. The intermediate positioning measurement may include one or more of LOS / NLOS indicator, DL-RTOA, UL-RTOA, DL-RSTD, UL-RSTD, gNB Rx-Tx time difference, UE Rx-Tx time difference, DL-AoD, UL-AoA or other timing based or angle based measurement. The intermediate positioning measurements may have same or different meaning as the corresponding legacy positioning measurements as described above (i.e. legacy positioning measurements).

[0174] For the AI / ML based positioning, the measurement of the dataset may be the CIR, PDP or DP. The label of the dataset may be the UE location for the direct AI / ML positioning, or intermediate positioning measurement for the AI / ML assisted positioning.

[0175] In AI / ML based positioning, AI / ML model is located at UE (UE side model), gNB (gNB side model) or LMF (LMF side model).

[0176] The following use cases may be available for AI / ML based positioning:Case 1 : UE-based positioning with UE-side model, direct AI / ML or AI / ML assisted positioningCase 2a: UE-assisted / LMF -based positioning with UE-side model, AI / ML assisted positioningCase 2b: UE-assisted / LMF -based positioning with LMF-side model, direct AI / ML positioningCase 3a: NG-RAN node assisted positioning with gNB-side model, AI / ML assisted positioningCase 3b: NG-RAN node assisted positioning with LMF-side model, direct AI / ML positioning

[0177] For AI / ML based positioning, for model training, training data may be generated by UE 501a, PRU 501b, NG-RAN node 502 and / or LMF 503.

[0178] For AI / ML based positioning, for LMF-side model inference (Case 2b, Case 3b), input data may be generated by UE / gNB and terminated at LMF. For gNB-side model inference (Case 3a), input data may be internally available at gNB. For UE-side model inference (Case 1, Case 2a), input data may be internally available at UE.

[0179] For AI / ML based positioning, for performance monitoring at the LMF side, calculated performance metrics (if needed) or data needed for performance metric calculation (if needed) may be generated by UE / gNB and terminated at LMF. ForAI / ML based positioning, for performance monitoring at the gNB side, calculated performance metrics (if needed) or data needed for performance metric calculation (if needed) may be generated by at least gNB.

[0180] Hereinafter, procedure of the dataset transfer for AI / ML based positioning is described. This procedure may be applied for the model training 402 and / or performance monitoring of the model in the management 403. Also, the dataset, hereinafter, implies the set of the data where the data consists of either measurement data (e.g. CIR, PDP or DP) for model input or label data, or both. This procedure is shown in the figure 7 for LPP and NRPPa.

[0181] The node requiring the dataset (can be referred to as the node B) 704 may send the dataset request message 701 to the node storing the dataset (can be referred to as the node A) 703. In response to the dataset request message 701, the node B 704, subject to the capability, may send the dataset message 702 to the node A. The dataset message 702 may contain the dataset. The dataset may consist of one or more of data. The data may consist of at least measurement data and optionally label data. The data may consist of at least the timing information and optionally power information. The node B 704 may typically be either NG-RAN node 502, UE 501a or PRU 501b. The node A 703 may typically be LMF 503. In case the node B 704 is NG-RAN node 502, the communication protocol may be NRPPa 505. In case the node B 704 is UE 501a or PRU 501b, the communication protocol may be LPP 504. The node A 703 may send the dataset message to the node B 704 without the request message from the node B 704. The measurement data may refer to the CIR, PDP or DP and the label data may refer to the LOS / NLOS indicator or the intermediate measurement of AI / ML assisted positioning (i.e. DL-RTOA, UL-RTOA, DL-RSTD, UL-RSTD, gNB Rx-Tx time difference, UE Rx-Tx time difference, DL-AoD, UL-AoA or other timing based or angle based measurement). The measurement data may consist of the timing information and power information. The measurement data may be generated using downlink reference signal (e.g. DL-PRS, CSI-RS or SSB) in case the node B is the UE 501a or PRU 501b. The measurement data may be generated using uplink reference signal (e.g. UL-SRS for positioning or UL-SRS) in case the node B is the NG-RAN node 502.

[0182] The timing information may specify the timing when the receiver detects the path. Alternatively, the timing information may be represented by at least samplingperiod of consecutive N_t samples and optionally corresponding bitmap. Alternatively, the timing information may specify the timing of the X' I strongest path within the consecutive N_t samples. Alternatively, the timing information may be represented by the RSTD, RTOA, gNB Rx-Tx time difference, UE Rx-Tx time difference.

[0183] The power information may specify the reference signal received path power and may correspond to the timing information. Alternatively, the power information may specify the reference signal received power of one sample.

[0184] If the dataset request message 701 sent from the node B to the node A includes the criterion, the node A may determine to be sent to the node B based on the criterion. Specifically, the node A may determine a dataset that fulfills the criterion that is included in the data request message 701 and send the determined dataset in the dataset message 702 to the node B. The criterion may be one or more of DL PRS ID, area ID, time stamp, quality indicator or LOS indicator. By using the criterion for the data collection, signaling overhead for the data collection may be reduced. Furthermore, consistency of training data and inference data may be guaranteed.

[0185] In an embodiment of the present disclosure, the criterion may be the DL PRS ID. In a case that the dataset request message sent from the node B to the node A includes the DL PRS ID, the node A may send the dataset message that is generated based on the DL PRS ID included in the dataset request message. For example, the node A may send the dataset that is generated by the DL PRS corresponding to DL PRS ID included in the dataset request message.

[0186] In an embodiment of the present disclosure, the criterion may be the area ID. In a case that the dataset request message sent from the node B to the node A includes the area ID, the node A may send the dataset generated in the area where the area ID specifies. The area ID may be an ID related to a particular network area. The area ID may be used to indicate or specify an area. The area ID may be used to indicate where an AI / ML model or functionality is applied. The area ID may be used to indicate where the data to be used for training of an AI / ML model or functionality may be collected or generated. For example, the area ID may provide one or more cell IDs and then the dataset may be generated in the one or more cells specified by the area ID.

[0187] In an embodiment of the present disclosure, the criterion is the time stamp. In a case that the dataset request message sent from the node B to the node A includes the time stamp, the node A may send the dataset that is generated based on the timestamp. For example, the dataset may be generated after the time specified by the time stamp.

[0188] In an embodiment of the present disclosure, the criterion is the quality indicator. There are two cases can be considered. For the case A, if the dataset request message sent from the node B to the node A includes the quality indicator for measurement data, the node A may send the measurement data of the dataset based on the quality indicator for measurement data. For example, the uncertainty of the measurement data of the dataset may be less than the uncertainty indicated by the quality indicator. For case B, if the dataset request message sent from the node B to the node A includes the quality indicator for label data, the node A may send the label data of the dataset based on the quality indicator for label data. For example, the uncertainty of the label data of the dataset may be less than the uncertainty indicated by the quality indicator. Either case A or case B, or a combination of both, may be applied in the present disclosure. In an example of the embodiment, the quality indicator may indicate an estimate of uncertainty of timing value.

[0189] In an embodiment of the present disclosure, the criterion is the LOS indicator. In a case that the dataset request message sent from the node B to the node A includes the LOS indicator, the node A may send the dataset that is generated in the environment assumed as Line-Of-Sight.

[0190] Hereinafter, procedure of the data transfer for AI / ML based position ing is described. Also, the data, hereinafter, consists of either measurement data for model input or label data, or both. This procedure is shown in the figure 6 for LPP and NRPPa.

[0191] The node requiring the data (can be referred to as the node A) 604 may send the data request message 601 to the node generating the data (can be referred to as the node B) 603. In response to the reception of the data request message 601 , the node B 603, subject to the capability, may send the data message 602 to the node A 604. The data message 602 may contain the data. The node A 604 may typically be LMF 503. The node B 603 may typically be either NG-RAN node 502, UE 501a or PRU 501b. In case the node B 603 is NG-RAN node 502, the communication protocol may be NRPPa 505. In case the node B 603 is UE 501a or PRU 501b, the communication protocol may be LPP 504. The node B 603 may send the data to the node A 604 without the request message from the node A 604. The data may consist of the measurement data and the label data. The measurement data may refer to the CIR, PDP or DP and the label datamay refer to the LOS / NLOS indicator or the intermediate measurement of AI / ML assisted positioning (i.e. DL-RTOA, UL-RTOA, DL-RSTD, UL-RSTD, gNB Rx-Tx time difference, UE Rx-Tx time difference, DL-AoD, UL-AoA or other timing based or angle based measurement). The measurement data may consist of the timing information and power information. The measurement data may be generated using downlink reference signal (e.g. DL-PRS, CSI-RS or SSB) in case the node B is the UE 501a or PRU 501b. The measurement data may be generated using uplink reference signal (e.g. UL-SRS for positioning or UL-SRS) in case the node B is the NG-RAN node 502.

[0192] If the data request message 601 sent from the node A to the node B includes the criterion, the node B may determine to be sent to the node A based on the criterion. Specifically, the node B may determine a dataset that fulfills the criterion that is included in the data request message 601 and send the determined dataset in the dataset message 602 to the node A. The criterion may be one or more of DL PRS ID, area ID, time stamp, quality indicator or LOS indicator. By using the criterion for the data collection, signaling overhead for the data collection may be reduced. Furthermore, consistency of training data and inference data may be guaranteed.

[0193] In an embodiment of the present disclosure, the criterion may be the DL PRSID. In a case that the data request message sent from the node A to the node B includes the DL PRS ID, the node B may send the data that is generated based on the DL PRS ID included in the data request message. For example, the node B may send the data that is generated by the DL PRS corresponding to DL PRS ID included in the data request message.

[0194] In an embodiment of the present disclosure, the criterion may be the area ID. In a case that the data request message sent from the node A to the node B includes the area ID, the node B may send the data if the node B is belonging the area where the area ID specifies. The area ID may be an ID related to a particular network area. The area ID may be used to indicate or specify an area. The area ID may be used to indicate where an AI / ML model or functionality is applied. The area ID may be used to indicate where the data to be used for training of an AI / ML model or functionality may be collected or generated. For example, the area ID may provide one or more cell IDs and then the data may be generated in the one or more cells specified by the area ID.

[0195] In an embodiment of the present disclosure, the criterion is the time stamp. In a case that the data request message sent from the node A to the node B includes the time stamp, the node B may send the data that is generated based on the time stamp. For example, the data may be generated after the time specified by the time stamp.

[0196] In an embodiment of the present disclosure, the criterion is the quality indicator. There are two cases can be considered. For the case A, if the data request message sent from the node A to the node B includes the quality indicator for the data, the node B may send the data based on the quality indicator for measurement data. For example, the uncertainty of the measurement data of the data may be less than the uncertainty indicated by the quality indicator. For case B, if the data request message sent from the node A to the node B includes the quality indicator for label data, the node B may send the label data of the dataset based on the quality indicator for label data. For example, the uncertainty of the label data of the data may be less than the uncertainty indicated by the quality indicator. Either case A or case B, or a combination of both, may be applied in the present disclosure. In an example of the embodiment, the quality indicator may indicate an estimate of uncertainty of timing value.

[0197] In an embodiment of the present disclosure, the criterion is the LOS indicator. In a case that the data request message sent from the node A to the node B includes the LOS indicator, the node B may send the data that is generated in the environment assumed as Line-Of-Sight.

[0198] A communication apparatus is described. The communication apparatus may be the UE 501a, PRU 501b or NG-RAN node 502. The communication apparatus may refer to the node B 604. A server may be the LMF 503. The server may refer to the node A 604. The communication apparatus may comprise reception circuitry configured to receive a data request message 601 in a higher layer parameter, from a server, including a first criterion, and receive a reference signal from another communication apparatus, and generate a data based on the reference signal, wherein the data consists of at least timing information, and transmission circuitry configured to send a data message 602 in a higher layer parameter, including the data that fulfills the first criterion.

[0199] The first criterion corresponds to quality indicator that indicates an estimate of uncertainty of timing, and uncertainty of the timing information included in the data message 602 is less than the uncertainty indicated by the first criterion.

[0200] A server is described. The server may comprise transmission circuitry configured to send a data request message 601 in a higher layer parameter, to a communication apparatus, including a first criterion, and reception circuitry configured to receive a data message 602 in a higher layer parameter, including a data consists of at least timing information, wherein the data fulfills the first criterion.

[0201] The first criterion may correspond to quality indicator that indicates an estimate of uncertainty of timing, and uncertainty of the timing information included in the data message 602 is less than the uncertainty indicated by the first criterion.

[0202] A communication method performed by a communication apparatus is described. The communication method may comprise receiving a data request message 601 in a higher layer parameter, from the server, including a first criterion, and receiving a reference signal from another communication apparatus, and generating the data based on the reference signal, wherein the data consists of at least timing information, and sending a data message 602 in a higher layer parameter, including the data that fulfills the first criterion.

[0203] Figure 8 illustrates various components that may be utilized in a UE 802. The UE 802 (UE 102) described in connection with Figure 8 may be implemented in accordance with the UE 102 described in connection with Figure 1. The UE 802 includes a processor 881 that controls operation of the UE 802. The processor 881 may also be referred to as a central processing unit (CPU). Memory 887, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 883a and data 885a to the processor 881. A portion of the memory 887 may also include non-volatile random access memory (NVRAM). Instructions 883b and data 885b may also reside in the processor 881. Instructions 883b and / or data 885b loaded into the processor 881 may also include instructions 883a and / or data 885a from memory 887 that were loaded for execution or processing by the processor 881. The instructions 883b may be executed by the processor 881 to implement one or more of the methods described above.

[0204] The UE 802 may also include a housing that contains one or more transmitters 858 and one or more receivers 820 to allow transmission and reception of data. The transmitter(s) 858 and receiver(s) 820 may be combined into one or moretransceivers 818. One or more antennas 822a-n are attached to the housing and electrically coupled to the transceiver 818.

[0205] The various components of the UE 802 are coupled together by a bus system 889, which may include a power bus, a control signal bus and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in Figure 8 as the bus system 889. The UE 802 may also include a digital signal processor (DSP) 891 for use in processing signals. The UE 802 may also include a communications interface 893 that provides user access to the functions of the UE 802. The UE 802 illustrated in Figure 8 is a functional block diagram rather than a listing of specific components.

[0206] Figure 9 illustrates various components that may be utilized in a base station 960. The base station 960 described in connection with Figure 9 may be implemented in accordance with the base station 160 described in connection with Figure 1. The base station 960 includes a processor 981 that controls operation of the base station 960. The processor 981 may also be referred to as a central processing unit (CPU). Memory 987, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 983a and data 985a to the processor 981. A portion of the memory 987 may also include non-volatile random access memory (NVRAM). Instructions 983b and data 985b may also reside in the processor 981. Instructions 983b and / or data 985b loaded into the processor 981 may also include instructions 983a and / or data 985a from memory 987 that were loaded for execution or processing by the processor 981. The instructions 983b may be executed by the processor 981 to implement one or more of the methods 300 described above.

[0207] The base station 960 may also include a housing that contains one or more transmitters 917 and one or more receivers 978 to allow transmission and reception of data. The transmitter(s) 917 and receiver(s) 978 may be combined into one or more transceivers 976. One or more antennas 980a-n are attached to the housing and electrically coupled to the transceiver 976.

[0208] The various components of the base station 960 are coupled together by a bus system 989, which may include a power bus, a control signal bus and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in Figure 9 as the bus system 989. The base station 960 may also include adigital signal processor (DSP) 991 for use in processing signals. The base station 960 may also include a communications interface 993 that provides user access to the functions of the base station 960. The base station 960 illustrated in Figure 9 is a functional block diagram rather than a listing of specific components.

[0209] The term “computer-readable medium” refers to any available medium that can be accessed by a computer or a processor. The term “computer-readable medium,” as used herein, may denote a computer- and / or processor-readable medium that is non- transitory and tangible. By way of example, and not limitation, a computer-readable or processor-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

[0210] It should be noted that one or more of the methods described herein may be implemented in and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or realized using circuitry, a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.

[0211] Each of the methods disclosed herein comprises one or more steps or actions for achieving the described method. The method steps and / or actions may be interchanged with one another and / or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0212] It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods and apparatus described herein without departing from the scope of the claims.

Claims

[CLAIMS]1. A communication apparatus, comprising: reception circuitry configured to receive, from a server, a data request message, the data request message including a first criterion, receive a reference signal from another communication apparatus, and generate a channel measurement based on the reference signal; and transmission circuitry configured to send, to the server, the channel measurement if the channel measurement fulfills the first criterion; wherein the channel measurement consists of at least timing information.

2. The communication apparatus according to the claim 1, wherein the first criterion corresponds to a first quality that indicates an estimate of quality of timing, and a second quality of the timing information included in the channel measurement is better than the first quality.

3. A server, comprising: transmission circuitry configured to send a data request message, to a communication apparatus, the data request message including a first criterion, and reception circuitry configured to receive a channel measurement, the channel measurement consisting of at least timing information and fulfilling the first criterion.

4. The server according to the claim 3, wherein the first criterion corresponds to a first quality that indicates an estimate of quality of timing, and a second quality of the timing information included in the channel measurement is better than the first quality.

5. A communication method performed by a communication apparatus, comprising: receiving, from a server, a data request message, the data request message including a first criterion, receive a reference signal from another communication apparatus, and generate a channel measurement based on the reference signal; and sending, to the server, the channel measurement if the channel measurement fulfills the first criterion; wherein the channel measurement consists of at least timing information.

Images