Method and apparatus for application layer measurement reporting in unlicensed spectrum

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a user equipment (UE) in a wireless communication system is provided. The method comprises: receiving configuration information for an application layer measurement report from a base station; generating a media access control (MAC) protocol data unit (PDU) including a media access control (MAC) service data unit (SDU) of the application layer measurement report message based on the configuration information; determining a channel access priority level (CAPC) of the MAC PDU based on a channel access priority level (CAPC) of a logical channel (LCH) for a signaling radio bearer 4 (SRB4) in a case where an uplink (UL) grant for the MAC PDU is associated with a shared spectrum; and transmitting the MAC PDU to the base station after the channel access procedure of the CAPC based on the MAC PDU.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly to an apparatus, method, and system for application layer measurement reporting in unlicensed spectrum. Background Art

[0002] 5G mobile communications technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands, known as millimeter waves, including 28 GHz and 39 GHz. Furthermore, in order to achieve transmission rates 50 times faster than 5G mobile communications technology and ultra-low latency that is one-tenth that of 5G mobile communications technology, consideration has been given to implementing 6G mobile communications technology in the terahertz (THz) frequency band (e.g., the 95 GHz to 3 THz band) (referred to as a "beyond 5G system").

[0003] In the early stages of 5G mobile communications technology development, in order to support services and meet performance requirements related to enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC) and massive Machine-Type Communications (mMTC), standardization is underway on the following: beamforming and massive MIMO to mitigate radio wave path loss and increase radio wave transmission distance in millimeter waves; support parameter sets (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and dynamic operation of time slot formats; initial access technology to support multi-beam transmission and broadband; definition and operation of BWP (BandWidth Part); new channel coding methods such as LDPC (Low Density Parity Check) codes for large-scale data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing to provide dedicated networks dedicated to specific services.

[0004] Currently, discussions are underway on improvements and performance enhancements to initial 5G mobile communication technologies in view of the services they will support, and there is already physical layer standardization on technologies such as: V2X (Vehicle-to-everything), for assisting driving determinations of autonomous vehicles based on information about the location and status of vehicles sent by the vehicles, and for enhancing user convenience; NR-U (New Radio Unlicensed), for system operation in compliance with various regulatory requirements in unlicensed frequency bands; NR UE energy saving; Non-Terrestrial Network (NTN), which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] Furthermore, in terms of air interface architecture / protocols, standardization is underway on technologies such as the Industrial Internet of Things (IIoT), which supports new services through interoperability and integration with other industries; Integrated Access and Backhaul (IAB), which provides a node for network service area expansion by integrating wireless backhaul and access links; enhanced mobility, including conditional handover and DAPS (Dual Active Protocol Stack) handover; and two-step random access, which simplifies random access procedures (2-step RACH (Random Access Channel) for NR). In terms of system architecture / services, standardization is also underway on the following: 5G baseline architecture (e.g., service-based architecture or service-based interface), which combines Network Function Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and Mobile Edge Computing (MEC), which enables UE location-based service delivery.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially increasing number of connected devices will be connected to the communication network. Accordingly, it is expected that enhanced functionality and performance of 5G mobile communication systems and the integrated operation of connected devices will become necessary. To this end, new research is planned related to: extended reality (XR) to effectively support AR (augmented reality), VR (virtual reality), MR (mixed reality), etc.; improving 5G performance and reducing complexity by leveraging artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communications.

[0007] Furthermore, this development of 5G mobile communication systems will serve not only as a foundation for the development of new waveforms, multi-antenna transmission technologies (such as Full Dimensional MIMO (FD-MIMO), array antennas, and massive antennas) for providing coverage of the terahertz band for 6G mobile communication technology, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technologies using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also as a foundation for the development of full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technologies for implementing system optimization by leveraging satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technologies for implementing services with a level of complexity that exceeds the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical issues

[0009] With advancements in wireless communication technology, application layer measurement reporting in licensed spectrum has been introduced. A user equipment (UE) capable of application layer measurement reporting in the RRC_CONNECTED state can initiate this procedure when configured with application layer measurements. However, in the context of new radio-unlicensed (NR-U) systems, application layer measurement reporting functionality is currently not supported. Therefore, aspects of the present disclosure are intended to address at least the aforementioned issues and / or shortcomings.

[0010] Problem Solution

[0011] According to one aspect of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system is provided. The method includes: receiving configuration information for application layer measurement reporting from a base station; generating a medium access control (MAC) protocol data unit (PDU) including a medium access control (MAC) service data unit (SDU) of an application layer measurement report message based on the configuration information; determining a channel access priority level (CAPC) of a logical channel (LCH) for signaling radio bearer 4 (SRB4) based on a CAPC of the MAC PDU when an uplink (UL) grant for the MAC PDU is associated with shared spectrum; and transmitting the MAC PDU to the base station after a channel access procedure based on the CAPC of the MAC PDU.

[0012] According to another aspect of the present disclosure, a method performed by a base station in a wireless communication system is provided. The method includes transmitting configuration information for application layer measurement reporting to a UE; and receiving a MAC protocol data unit (PDU) including an application layer measurement report message, generated based on the configuration information, from the UE. When an UL grant for the MAC PDU is associated with shared spectrum, a CAPC of the MAC PDU is associated with a CAPC of an LCH for SRB4.

[0013] According to another aspect of the present disclosure, a UE in a wireless communication system is provided. The UE includes a transceiver and a controller operatively coupled to the transceiver. The controller is configured to receive configuration information for an application layer measurement report from a base station via the transceiver; generate a MAC PDU including a MAC SDU of an application layer measurement report message based on the configuration information; determine a CAPC of the MAC PDU based on a CAPC of an LCH for SRB4 when an UL grant for the MAC PDU is associated with shared spectrum; and transmit the MAC PDU to the base station via the transceiver after a channel access procedure based on the CAPC of the MAC PDU.

[0014] According to another aspect of the present disclosure, a base station in a wireless communication system is provided. The base station includes a transceiver and a controller operably coupled to the transceiver. The controller is configured to transmit configuration information for application layer measurement reporting to a UE via the transceiver; and receive, from the UE via the transceiver, a MAC PDU including a MAC SDU containing an application layer measurement report message, generated based on the configuration information. When the UL grant for the MAC PDU is associated with shared spectrum, the CAPC of the MAC PDU is associated with the CAPC of the LCH for SRB4.

[0015] Advantageous Effects of the Invention

[0016] According to various embodiments of the present disclosure, application layer measurement reporting is enabled in unlicensed / shared spectrum, and the network can efficiently collect user quality of experience (QoE). BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:

[0018] Figure 1 The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0019] Figure 2 The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0020] Figure 3A The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0021] Figure 3B The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0022] Figure 4A The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0023] Figure 4B The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0024] Figure 5A The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0025] Figure 5B The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0026] Figure 6A The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0027] Figure 6B The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0028] Figure 7 The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0029] Figure 8 The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0030] Figure 9A The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0031] Figure 9B The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0032] Figure 10A The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0033] Figure 10B The signaling flow for application layer measurement reporting between a UE and a gNB according to an embodiment of the present disclosure is shown;

[0034] Figure 11 An electronic device according to an embodiment of the present disclosure is shown; and

[0035] Figure 12 A base station according to an embodiment of the present disclosure is shown.

[0036] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

[0037] Before proceeding with the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives mean including but not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated therewith" and their derivatives may mean including, included within, interconnected with, containing, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interwoven, juxtaposed, proximate to, bound to or bound with, having, having the property of, and the like; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device being implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0038] Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed of computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or portions thereof suitable for implementation in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard drives, compact discs (CDs), digital video discs (DVDs), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data as well as media that can store data and later rewrite it (such as rewritable optical discs or erasable storage devices).

[0039] Definitions for certain words and phrases are also provided throughout this patent document, which those of ordinary skill in the art should understand that in many, if not most, instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0040] Discussed below Figures 1 to 12 The various embodiments used to describe the principles of the present disclosure in this patent document are merely exemplary and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0041] The following description with reference to the accompanying drawings is provided to facilitate a fuller understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes various specific details to aid understanding, but these details are to be considered as exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and conciseness.

[0042] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0043] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0044] The term "substantially" means that the stated characteristic, parameter or value need not be achieved precisely, but deviations or variations (including, for example, tolerances, measurement errors, measurement accuracy limitations and other factors known to those skilled in the art) may occur in amounts that do not negate the effect that the characteristic is intended to provide.

[0045] Those skilled in the art will recognize that the blocks of a flowchart (or sequence diagram) and the combination of the flowcharts can be represented and executed by computer program instructions. These computer program instructions can be loaded onto a processor of a general-purpose computer, a special-purpose computer, or a programmable data processing device. When the loaded program instructions are executed by the processor, they create components for performing the functions described in the flowchart. Because computer program instructions can be stored in a computer-readable memory usable in a special-purpose computer or a programmable data processing device, an article of manufacture can also be created that performs the functions described in the flowchart. Because the computer program instructions can be loaded onto a computer or a programmable data processing device, when executed as a process, they can perform the operations of the functions described in the flowchart.

[0046] The blocks of the flowchart may correspond to modules, segments or codes containing one or more executable instructions that implement one or more logical functions, or may correspond to portions thereof. In some cases, the functions described by the blocks may be performed in an order different from the order in which they are listed. For example, two blocks listed in sequence may be executed simultaneously or in reverse order.

[0047] Throughout this specification, the terms "unit," "module," and the like may refer to software or hardware components, such as, for example, a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC) capable of performing a function or operation. However, "unit," etc., is not limited to hardware or software. Units, etc., may be configured to reside in an addressable storage medium or drive one or more processors. Units, etc., may refer to software components, object-oriented software components, class components, task components, processes, functions, properties, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. The functionality provided by components and units may be a combination of smaller components and units, and may be combined with other components and units to form larger components and units. Components and units may be configured to drive devices or one or more processors in a secure multimedia card.

[0048] Before the detailed description, terms or definitions necessary for understanding the present disclosure are described, but these terms should be interpreted in a non-restrictive manner.

[0049] A "base station (BS)" is an entity that communicates with a user equipment (UE) and may be referred to as a BS, base transceiver station (BTS), node B (NB), evolved NB (eNB), access point (AP), 5G NB (5GNB), or gNB.

[0050] A “UE” is an entity communicating with a BS and may be referred to as a UE, a device, a mobile station (MS), a mobile equipment (ME), or a terminal.

[0051] In recent years, several broadband wireless technologies have been developed to meet the growing demand for broadband subscribers and provide more and better applications and services. Second-generation wireless communication systems were developed to provide voice services while ensuring user mobility. Third-generation wireless communication systems support not only voice services but also data services. In recent years, fourth-generation wireless communication systems have been developed to provide high-speed data services. However, fourth-generation wireless communication systems currently lack the resources to meet the growing demand for high-speed data services. Therefore, fifth-generation wireless communication systems (also known as Next Generation Radio (NR)) are being developed to meet the growing demand for high-speed data services and support ultra-reliability and low-latency applications.

[0052] Fifth-generation wireless communication systems support not only lower frequency bands but also higher frequency (mmWave) bands, such as the 10 GHz to 100 GHz band, to achieve higher data rates. To mitigate radio wave propagation losses and increase transmission range, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technologies are being considered in the design of fifth-generation wireless communication systems. Furthermore, fifth-generation wireless communication systems are expected to target diverse use cases with distinct requirements in terms of data rate, latency, reliability, mobility, and so on. However, the design of the air interface of fifth-generation wireless communication systems is expected to be flexible enough to serve UEs with vastly different capabilities, depending on the use cases and market segments they serve. Example use cases anticipated to be targeted by fifth-generation wireless communication systems include enhanced mobile broadband (eMBB), massive machine-type communications (m-MTC), and ultra-reliable low-latency communications (URLLC). eMBB requirements, such as tens of Gbps data rates, low latency, and high mobility, target the market segment representing traditional wireless broadband subscribers who require internet connectivity anywhere, at all times, and while on the move. m-MTC requirements, such as very high connection density, infrequent data transmission, very long battery life, and low mobility, target the Internet of Things (IoT) / Internet of Everything (IoE) market segment, which envisions connecting hundreds of millions of devices. URLLC requirements, such as very low latency, very high reliability, and variable mobility, target the industrial automation applications and vehicle-to-vehicle / vehicle-to-infrastructure communications market segment, which is envisioned as one of the enabling technologies for autonomous vehicles.

[0053] In fifth-generation wireless communication systems operating in higher-frequency (mmWave) bands, UEs and gNBs communicate with each other using beamforming. Beamforming technology is used to mitigate propagation path loss and increase the propagation range of communications in higher frequency bands. Beamforming uses high-gain antennas to enhance transmission and reception performance. Beamforming can be categorized as transmit (TX) beamforming, performed by the transmitter, and receive (RX) beamforming, performed by the receiver. Generally, TX beamforming increases directivity by using multiple antennas to densely distribute the area of ​​propagation in a specific direction. In this context, a collection of multiple antennas is referred to as an antenna array, and each antenna in the array is referred to as an array element. Antenna arrays can be configured in various forms, such as linear arrays and planar arrays. The use of TX beamforming increases signal directivity, thereby increasing propagation range. Furthermore, since signals are rarely transmitted in directions other than the directional direction, signal interference on other receivers is significantly reduced. A receiver can perform beamforming on RX signals using an RX antenna array. RX beamforming increases the strength of RX signals transmitted in a specific direction by concentrating propagation in that direction and excluding signals transmitted in directions other than the specific direction from the RX signal, thereby blocking interfering signals. Using beamforming technology, a transmitter can create multiple transmit beam patterns in different directions. Each of these transmit beam patterns is also referred to as a transmit (TX) beam. Wireless communication systems operating at high frequencies use multiple narrow TX beams to transmit signals within a cell, as each narrow TX beam provides coverage for a portion of the cell. The narrower the TX beam, the higher the antenna gain, thus increasing the propagation distance of signals transmitted using beamforming. A receiver can also create multiple receive (RX) beam patterns in different directions. Each of these receive patterns is also referred to as a receive (RX) beam.

[0054] Fifth-generation wireless communication systems support standalone operation mode as well as dual connectivity (DC). In DC, a multi-Rx / Tx UE can be configured to utilize resources provided by two different nodes (or NBs) connected via a non-ideal backhaul. One node acts as a master node (MN), while the other acts as a secondary node (SN). The MN and SN are connected via a network interface, with at least the MN connected to the core network. NR also supports multi-RAT dual connectivity (MR-DC) operation, whereby a UE in the RRC_CONNECTED state is configured to utilize radio resources provided by two different schedulers located in two different nodes connected via a non-ideal backhaul and providing E-UTRA (i.e., if the node is an ng-eNB) or NR access (i.e., if the node is a gNB). In NR, for a UE in the RRC_CONNECTED state that is not configured with CA / DC, there is only one serving cell, including the primary cell.

[0055] For UEs in the RRC_CONNECTED state configured with Carrier Access Control (CA) / Carrier Disconnection (DC), the term "serving cell" is used to refer to the set of cells that includes a special cell and all secondary cells. In NR, the term "master cell group" (MCG) refers to the set of serving cells associated with a primary node, consisting of a PCell and, optionally, one or more SCells. In NR, the term "secondary cell group" (SCG) refers to the set of serving cells associated with a secondary node, consisting of a PSCell and, optionally, one or more SCells. In NR, a PCell (primary cell) refers to the serving cell in an MCG operating on the primary frequency, where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. In NR, for UEs configured with Carrier Access Control (CA), an Scell ​​is a cell that provides additional radio resources on top of a special cell. A primary SCG cell (PSCell) refers to the serving cell in an SCG, where the UE performs random access when performing a synchronized reconfiguration procedure. For dual connectivity operation, the term "SpCell" (i.e., special cell) refers to the PCell of an MCG or the PSCell of an SCG; otherwise, the term "special cell" refers to the PCell.

[0056] System Information Acquisition in Fifth Generation Wireless Communication Systems: In fifth generation wireless communication systems, the Node B (gNB) or base station in a cell broadcasts synchronization signals and PBCH blocks (SSBs), which consist of primary and secondary synchronization signals (PSS, SSS) and system information. System information includes common parameters required for communication in the cell. In fifth generation wireless communication systems (also known as next generation radio or NR), system information (SI) is divided into the MIB and multiple SIBs, where:

[0057] - The MIB is always sent on the BCH with a period of 80ms and repeated within 80ms, and it includes the parameters required to obtain SIB1 from the cell;

[0058] - SIB1 is sent on the DL-SCH with a periodicity of 160ms and variable transmission repetition. The default transmission repetition period of SIB1 is 20ms, but the actual transmission repetition period depends on the network implementation. The scheduling information in SIB1 includes the mapping between SIBs and SI messages, the periodicity of each SI message, and the SI window length. The scheduling information in SIB1 includes an indicator for each SI message that indicates whether the relevant SI message is being broadcast. If at least one SI message is not being broadcast, SIB1 may include random access resources (PRACH preamble and PRACH resources) for requesting the gNB to broadcast one or more SI messages; and

[0059] - SIBs other than SIB1 are carried in system information (SI) messages, which are sent on the DL-SCH. Only SIBs with the same periodicity can be mapped to the same SI message. Each SI message is sent within a time domain window that occurs periodically (called an SI window that has the same length for all SI messages). Each SI message is associated with an SI window, and the SI windows of different SI messages do not overlap. That is, within one SI window, only the corresponding SI messages are sent. Using the indication in SIB1, any SIB other than SIB1 can be configured as cell-specific or area-specific. Cell-specific SIBs are applicable only within the cell where the SIB is provided, while area-specific SIBs are applicable within an area called an SI area, which consists of one or more cells and is identified by systemInformationAreaID.

[0060] PDCCH in fifth-generation wireless communication systems: In fifth-generation wireless communication systems, the physical downlink control channel (PDCCH) is used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. The downlink control information (DCI) on the PDCCH includes: downlink assignments containing at least the modulation and coding format, resource allocation, and hybrid ARQ information related to the DL-SCH; uplink scheduling grants containing at least the modulation and coding format, resource allocation, and hybrid ARQ information related to the UL-SCH. In addition to scheduling, the PDCCH can also be used to: activate and deactivate configured PUSCH transmissions using configuration grants; activate and deactivate PDSCH semi-persistent transmissions; notify one or more UEs of the timeslot format; notify one or more UEs of the PRBs and OFDM symbols in which the UE can assume no transmission for the UE; transmit TPC commands for PUCCH and PUSCH; transmit one or more TPC commands for SRS transmission by one or more UEs; switch the active bandwidth portion of a UE; and initiate a random access procedure.

[0061] The UE monitors the set of PDCCH candidates during the configured monitoring opportunities in one or more configured control resource sets (CORESETs) according to the corresponding search space configuration. A CORESET consists of a set of PRBs with a duration of one to three OFDM symbols. Resource elements (REGs) and control channel elements (CCEs) are defined within a CORESET, with each CCE comprising a set of REGs. The control channel is formed by aggregating CCEs. Different code rates for the control channel are achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE-to-REG mapping is supported within the CORESET. Polarization coding is used for the PDCCH. Each resource element group carrying the PDCCH carries its own DMRS. Quadratic Phase-Shift Keying (QPSK) modulation is used for the PDCCH.

[0062] In fifth-generation wireless communication systems, the gNB signals a list of search space configurations for each configured BWP, where each search configuration is uniquely identified by an identifier. The gNB explicitly signals the identifier of the search space configuration to be used for specific purposes (such as paging reception, signaling information reception, and random access response reception). In NR, the search space configuration includes the parameters Monitoring-periodicity-PDCCH-slot, Monitoring-offset-PDCCH-slot, Monitoring-symbols-PDCCH-within-slot, and Duration. The UE uses the parameters Monitoring-periodicity-PDCCH-slot, Monitoring-offset-PDCCH-slot, and Monitoring-symbols-PDCCH-within-slot to determine the PDCCH monitoring opportunities within a timeslot. The PDCCH monitoring opportunity exists in time slots "x" to x+duration, where the time slot with number "x" in the radio frame with number "y" satisfies the following equation:

[0063] (y (number of slots in a radio frame) + x - Monitoring-offset-PDCCH-slot) mod (Monitoring-periodicity-PDCCH-slot) = 0.

[0064] The starting symbol of a PDCCH monitoring opportunity in each slot with a PDCCH monitoring opportunity is given by Monitoring-symbols-PDCCH-within-slot. The length of a PDCCH monitoring opportunity (in symbols) is given in the coreset associated with the search space. The search space configuration includes the identifier of the coreset configuration associated with it. The gNB signals a list of coreset configurations for each configured BWP, where each coreset configuration is uniquely identified by an identifier. Note that each radio frame has a duration of 10 ms. A radio frame is identified by a radio frame number or system frame number. Each radio frame consists of several slots, where the number of slots in a radio frame and the duration of the slots depend on the subcarrier spacing. The number of slots in a radio frame and the duration of the slots depend on each supported SCS predefined in the NR. Each coreset configuration is associated with a list of TCI (Transmission Configuration Indicator) states.

[0065] A DL RS ID (SSB or CSI RS) is configured for each TCI state. The gNB signals a list of TCI states corresponding to the coreset configuration via RRC signaling. One of the TCI states in the TCI state list is activated and indicated to the UE by the gNB via a MAC CE. The TCI state indicates the DL TX beam used by the gNB to transmit the PDCCH in the PDCCH monitoring opportunity in the search space (the DL TX beam is quasi-co-located with the SSB / CSI RS of the TCI state). For the PDSCH, the TCI state of the scheduled PDCCH can be used for the scheduled PDSCH. Alternatively, the TCI state of the PDCCH with the lowest coreset ID in the slot is used for the PDSCH. Alternatively, a combination of RRC, MAC CE, and DCI is used to indicate the TCI state of the PDSCH. The RRC configures the list of TCI states, the MAC CE indicates a subset of these TCI states, and the DCI indicates one of the TCI states from the list indicated in the MAC CE.

[0066] Bandwidth Adaptation in Fifth-Generation Wireless Communication Systems: Bandwidth Adaptation (BA) is supported in fifth-generation wireless communication systems. With BA, the UE's receive and transmit bandwidth need not be as large as the cell's bandwidth and can be adjusted: the width can be commanded to change (e.g., shrinking during periods of low activity to save power); the location can be moved in the frequency domain (e.g., to increase scheduling flexibility); and the subcarrier spacing can be commanded to change (e.g., to allow for different services). A subset of a cell's total cell bandwidth is called a bandwidth part (BWP). BA is implemented by configuring a BWP for an RRC-connected UE and informing the UE which of the configured BWPs is currently active. When BA is configured, the UE only needs to monitor the PDCCH on one active BWP; that is, it does not have to monitor the PDCCH across the entire DL frequency range of the serving cell.

[0067] In the RRC Connected state, the UE is configured with one or more DL and UL BWPs for each configured serving cell (i.e., PCell or SCell). For an activated serving cell, there is always one active UL and DL BWP at any point in time. BWP switching for a serving cell is used to activate an inactive BWP and deactivate an active BWP at a time. BWP switching is controlled by the PDCCH indicating a downlink assignment or uplink grant, by the bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself when initiating the random access procedure. After the addition of a SpCell or the activation of an SCell, the DL BWP and UL BWP, indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id, respectively, are active in the absence of a PDCCH indicating a downlink assignment or uplink grant. The active BWP of a serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP switching is common for both UL and DL. After the BWP inactivity timer expires, the UE switches the active DL BWP to the default DL BWP or the initial DL BWP (if the default DL BWP is not configured).

[0068] Random Access in Fifth Generation Wireless Communication Systems: 5G wireless communication systems support random access (RA). RA is used to achieve uplink (UL) time synchronization. RA is used by non-synchronized UEs in the RRC_CONNECTED state during initial access, handover, radio resource control (RRC) connection re-establishment procedures, scheduling request transmission, secondary cell group (SCG) addition / modification, beam failure recovery, and data or control information transmission in the UL. Several types of random access procedures are supported, including two-step or four-step contention-based random access and contention-free random access.

[0069] Paging in fifth-generation wireless communication systems: In fifth-generation (also known as NR or New Radio) wireless communication systems, a UE can be in one of the following RRC states: RRC IDLE, RRC INACTIVE, and RRC CONNECTED. The RRC states can be further characterized as follows:

[0070] - In the RRC_IDLE state, UE-specific DRX can be configured by upper layers (i.e., NAS). The UE monitors short messages sent via DCI with P-RNTI; monitors the paging channel for CN paging using 5G-S-TMSI; performs neighbor cell measurements and cell (re)selection; obtains system information and can send SI requests (if configured).

[0071] - In the RRC_INACTIVE state, UE-specific DRX can be configured by upper layers or the RRC layer; in this state, the UE stores the UE inactive AS context. The RAN-based notification area is configured by the RRC layer. The UE monitors short messages sent via DCI with the P-RNTI; monitors the paging channel for CN paging using 5G-S-TMSI and RAN paging using the full I-RNTI (fullI-RNTI); performs neighbor cell measurements and cell (re)selection; performs RAN-based notification area updates periodically and when moving outside the configured RAN-based notification area; obtains system information and may send an SI request (if configured).

[0072] - In the RRC_CONNECTED state, the UE stores the AS context. Unicast data is sent to / received from the UE. At lower layers, the UE may be configured with UE-specific DRX. The UE monitors short messages sent on the DCI with the P-RNTI (if configured); monitors the control channel associated with the shared data channel to determine whether data is scheduled for it; provides channel quality and feedback information; performs neighbor cell measurements and measurement reports; and obtains system information.

[0073] The NR-based 5G or Next Generation Radio Access Network (NG-RAN) consists of NG-RAN nodes, of which the gNB provides NR user plane and control plane protocol termination to the UE. The gNB is also connected to the 5GC via the NG interface, more specifically, to the Access and Mobility Management Function (AMF) via the NG-C interface, and to the User Plane Function (UPF) via the NG-U interface. In fifth-generation (also known as NR or New Radio) wireless communication systems, UEs can use discontinuous reception (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. In the RRC_IDLE / RRC_INACTIVE states, the UE wakes up for short periods at regular intervals (i.e., every DRX cycle) to receive paging, SI update notifications, and emergency notifications.

[0074] Paging messages are sent using the Physical Downlink Shared Channel (PDSCH). If a paging message is included in the PDSCH, the Physical Downlink Common Control Channel (PDCCH) is addressed to the P-RNTI. The P-RNTI is common to all UEs. The UE identity (i.e., S-TMSI for RRC_IDLE UEs or I-RNTI for RRC_INACTIVE UEs) is included in the paging message to indicate paging for a specific UE. A paging message can include multiple UE identities to page multiple UEs. The paging message is broadcast on the data channel (i.e., PDSCH) (i.e., the PDCCH is masked with the P-RNTI). SI updates and emergency notifications are included in the DCI, and the PDCCH carrying this DCI is addressed to the P-RNTI. In RRC Idle / Inactive mode, the UE monitors one Paging Occasion (PO) per DRX cycle. In RRC Idle / Inactive mode, the UE monitors the PO in the initial DL BWP. In RRC Connected state, the UE monitors one or more POs to receive SI update notifications and emergency notifications. In the RRC connected state, the UE can monitor any PO in the paging DRX cycle and monitor at least one PO in the SI modification period. In RRC idle / inactive mode, the UE monitors the PO every DRX cycle in its active DL BWP. The PO is a set of "S" PDCCH monitoring opportunities used for paging, where "S" is the number of SSBs (i.e., synchronization signal and PBCH blocks (SSBs) consisting of primary and secondary synchronization signals (PSS, SSS) and PBCH) transmitted in the cell. The UE first determines the paging frame (PF) and then determines the PO relative to the determined PF. One PF is a radio frame (10ms).

[0075] - The PF of the UE is the one that satisfies the equation (SFN+PF_offset) mod T=(T div N) (UE_ID mod N) System Frame Number "SFN" of the radio frame.

[0076] - Index (i_s), indicating the index of the PO is determined by i_s = floor (UE_ID / N) mod Ns.

[0077] - T is the DRX cycle of the UE.

[0078] In the RRC_INACTIVE state, T is determined by the shortest value among the UE-specific DRX value configured by RRC, the UE-specific DRX value configured by NAS, and the default DRX value broadcast in the system information.

[0079] In the RRC_IDLE state, T is determined by the shortest value between the UE-specific DRX value configured by NAS and the default DRX value broadcast in the system information. If the upper layer (i.e. NAS) does not configure UE-specific DRX, the default value applies:

[0080] - N: the total number of paging frames in T;

[0081] - Ns: number of paging occasions of PF;

[0082] - PF_offset: offset used for PF determination;

[0083] - UE_ID: 5G-S-TMSI mod 1024;

[0084] - Signal the parameters Ns, nAndPagingFrameOffset and the length of the default DRX cycle in SIB 1. The values ​​of N and PF_offset are derived from the parameter nAndPagingFrameOffset as defined in TS 38.331. If the UE does not have a 5G-S-TMSI, for example when the UE has not yet registered on the network, the UE may use the default identifier UE_ID = 0 in the above PF and i_s formulas;

[0085] - Determine the PDCCH monitoring occasion for paging based on the paging search space configuration (paging-SearchSpace) signaled by the gNB;

[0086] - When SearchSpaceId=0 is configured for pagingSearchSpace, the PDCCH monitoring occasions for paging are the same as for RMSI as defined in clause 13 of TS 38.213. When SearchSpaceId=0 is configured for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO, which starts from the first PDCCH monitoring occasion for paging in the PF. For Ns=2, the PO is in the first half-frame (i_s=0) or the second half-frame (i_s=1) of the PF; and / or

[0087] When a SearchSpaceId other than 0 is configured for the pagingSearchSpace, the UE monitors the (i_s+1)th Paging Search Space (PO). The PDCCH monitoring occasions for paging are determined based on the paging search space configuration (paging-SearchSpace) signaled by the gNB. PDCCH monitoring occasions for paging that do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are numbered sequentially starting from zero, starting with the first PDCCH monitoring occasion for paging in the PF. The gNB may signal the parameter firstPDCCH-MonitoringOccasionOfPO for each PO corresponding to the PF. When firstPDCCH-MonitoringOccasionOfPO is signaled, the (i_s+1)th Paging Search Space (PO) is the set of S consecutive PDCCH monitoring occasions for paging, starting with the PDCCH monitoring occasion number indicated by firstPDCCH-MonitoringOccasionOfPO (i.e., the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter). Otherwise, the (i_s+1)th PO is from the (i_s The set of "S" consecutive PDCCH monitoring occasions for paging, starting with the first PDCCH monitoring occasion (S) for paging. "S" is the number of SSBs actually transmitted, as determined by the parameter ssb-PositionsInBurst signaled in SystemInformationBlock1 received from the gNB. The parameter firstPDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter firstPDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0088] The design of 5G wireless communication systems needs to support operation on both licensed and unlicensed carriers. The main motivation for using unlicensed carriers is CAPEX reduction for cellular operators through intelligent data offloading using liberalized spectrum access; improved and intelligent spectrum access and management to address the growing demand for wireless traffic within the limited available spectrum, and allowing network operators without licensed spectrum to utilize radio-efficient 3GPP radio access technologies. Various deployment scenarios are being considered for operation on unlicensed carriers, such as:

[0089] - NR-U LAA: Carrier aggregation between licensed NR (PCell) and unlicensed NR-U (SCell);

[0090] - NR-U SA: Independent NR-U;

[0091] - ENU-DC: Dual connectivity between licensed LTE (PCell) and unlicensed NR-U (PSCell);

[0092] - NNU-DC: Dual connectivity between licensed NR (PCell) and unlicensed NR-U (PSCell);

[0093] Note that the above scenario includes NR cells with DL in the unlicensed band and UL in the licensed band.

[0094] The Listen Before Talk (LBT) process is essential for fair and friendly coexistence of devices and technologies operating in unlicensed / shared spectrum. The LBT process on a node attempting to transmit on a carrier in the unlicensed spectrum requires the node to perform a Clear Channel Assessment to determine if the channel is free for use. The various types or categories of LBT processes used for transmissions are as follows:

[0095] Category 1: No LBT;

[0096] The sending entity does not perform the LBT procedure; and

[0097] Category 2: LBT without random backoff.

[0098] The duration that the channel is sensed as idle before the transmitting entity transmits is deterministic. In an example, the sensing interval may be 25 us, i.e., the UE may transmit after sensing that the channel is idle for at least a sensing interval of Td = 25 us. For UL transmissions, Category 3 is also known as a Type 2 channel access procedure.

[0099] Category 3: LBT with random backoff, with a fixed-size contention window.

[0100] The LBT process has the following process as one of its components. The transmitting entity draws a random number N within the contention window. The size of the contention window is specified by the minimum and maximum values ​​of N. The size of the contention window is fixed. The random number N is used in the LBT process to determine the duration of time the channel is sensed as idle before the transmitting entity transmits on the channel. The detailed Category 3 LBT process is as follows:

[0101] The UE transmits after sensing that the channel is idle during the time slot duration of the delay duration (Td); and transmits after the counter reaches zero in step 4. The detailed process is as follows:

[0102] Step 1: Set N = Ninit, where Ninit is a random number uniformly distributed between 0 and CWp. CWp is the contention window for a given channel access priority level "p". Table 1 below lists various LBT parameters for different channel access priority levels (CAPC).

[0103] [Table 1]

[0104]

[0105] If it can be guaranteed on a long-term basis (e.g., by regulatory authorities) that there are no other technologies sharing the carrier, the maximum channel occupancy time is 10 ms for LBT priority classes 3 and 4. Otherwise, the maximum channel occupancy time is 8 ms for LBT priority classes 3 and 4.

[0106] Step 2: If N>0, decrement the counter and set N=N-1.

[0107] Step 3: Sense the channel during the additional time slot duration (Ts). If the additional time slot duration is idle, go to step 4, otherwise go to step 5.

[0108] Step 4: If N=0, perform the transfer, otherwise, go to step 2.

[0109] Step 5: Sense the channel during the time slot duration with an additional delay duration Td. The delay duration (Td) is equal to Tf + mp x Ts, where Tf is equal to 16us and Ts is equal to 9us.

[0110] Step 6: If the channel is sensed to be idle during Td, go to step 2, otherwise go to step 5.

[0111] Category 4: LBT with random backoff, with variable-sized contention windows.

[0112] The LBT procedure has the following as one of its components. The transmitting entity draws a random number N within the contention window. The size of the contention window is specified by the minimum and maximum values ​​of N. The transmitting entity can change the size of the contention window when the random number N is drawn. The random number N is used in the LBT procedure to determine the duration for which the channel is sensed as idle before the transmitting entity transmits on the channel. The detailed procedure is the same as Category 3. The only difference is that in Category 3, the size of the contention window is fixed, while in Category 4, the transmitting entity can change the size of the contention window when the random number N is drawn. For UL transmission, Category 4 is also known as Type 1 channel access procedure.

[0113] Application Layer Measurement Reporting in Fifth Generation Wireless Communication Systems: A UE capable of application layer measurement reporting in the RRC_CONNECTED state can initiate this procedure when configured with application layer measurements (i.e., when appLayerMeasConfig and SRB4 have been configured by the network). This functionality is supported only for licensed spectrum. Table 2 below shows an example of a message sent by the UE to the gNB for application layer measurement reporting.

[0114] [Table 2]

[0115]

[0116]

[0117] Table 3 below shows an example of UE capabilities sent by the UE to the gNB for application layer measurement reporting.

[0118] [Table 3]

[0119]

[0120] Table 4 below shows an example of a configuration sent by the gNB to the UE for application layer measurement reporting.

[0121] [Table 4]

[0122]

[0123] Application layer measurement reporting is supported only for licensed spectrum. Enhancement is needed to support this functionality for unlicensed spectrum so that backward compatibility is maintained (i.e., legacy UEs that support this functionality only in licensed spectrum and new UEs that support this functionality in both licensed and unlicensed spectrum may be able to operate in the cell, and the network may be able to differentiate between them and configure application measurements accordingly).

[0124] Figure 1 The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown.

[0125] refer to Figure 1 , illustrates a method for application layer measurement reporting, where the CAPC for SRB4 is configured using an RRC reconfiguration message. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are required for this disclosure, and some operations may be selectively omitted as appropriate.

[0126] In operation 100, the UE may be in an RRC_CONNECTED state. In operation 105, the gNB may send a UE Capability Query message to query the UE's capabilities (the UE Capability Query message may request UE capabilities for application layer measurement reporting). In operation 110, the UE may send a UE Capability Information message including UE capabilities for application layer measurement reporting. The UE capabilities may indicate whether the UE supports application layer measurement reporting in unlicensed spectrum. The gNB may support one or more serving cells for the UE.

[0127] In operation 115, if there is at least one unlicensed serving cell configured by the gNB to the UE (i.e., a cell operating on or using unlicensed spectrum) and the UE supports application layer measurement reporting in the unlicensed spectrum, the gNB may configure the UE with SRB4, AppLayerMeasConfig, and CAPC for the LCH of SRB4. In operation 120, the gNB may send these configurations to the UE in an RRCReconfiguration message. Alternatively, if there is no unlicensed serving cell configured by the gNB to the UE, the gNB may configure SRB4 and AppLayerMeasConfig to the UE and send these configurations to the UE in an RRCReconfiguration message. Alternatively, if there is at least one unlicensed serving cell configured by the gNB to the UE (i.e., a cell operating on or using unlicensed spectrum) and the UE does not support application layer measurement reporting in the unlicensed spectrum, the gNB may not configure SRB4 and AppLayerMeasConfig to the UE.

[0128] In operation 125, upon receiving the RRCReconfiguration message with the AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. In operation 130, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 135, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 140, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU in an UL grant (configured grant or dynamic grant).

[0129] In operation 145, if the UL grant for transmitting the MAC PDU is for an unlicensed cell and the gNB does not indicate a CAPC for the UL grant, the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the CAPC of the SRB4 received in the RRC message and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of the RBs of the other MAC SDUs), if any. In operation 150, the UE (or the MAC layer in the UE) may access the channel based on the determined CAPC of the MAC PDU and transmit the MAC PDU.

[0130] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0131] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0132] - Fixed as the highest priority among SRB0, SRB1, SRB3 and other MAC CEs; and / or

[0133] -Configured by the gNB for SRB2, SRB4 and DRB.

[0134] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0135] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0136] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0137] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0138] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0139] Figure 2 The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown.

[0140] refer to Figure 2 , illustrates a method for application layer measurement reporting, where the CAPC of SRB4 is fixed or predetermined. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are required for this disclosure, and some operations may be selectively omitted as appropriate.

[0141] In operation 200, the UE may be in the RRC_CONNECTED state. In operation 205, the gNB may send a UE Capability Query message to query the UE capabilities (the UE Capability Query message may request UE capabilities for application layer measurement reporting). In operation 210, the UE may send a UE Capability Information message including UE capabilities for application layer measurement reporting. The UE capabilities may indicate whether the UE supports application layer measurement reporting in unlicensed spectrum. The gNB may support one or more serving cells for the UE.

[0142] In operation 215, if there is at least one unlicensed serving cell configured by the gNB to the UE (i.e., a cell operating on or using unlicensed spectrum) and the UE supports application layer measurement reporting in the unlicensed spectrum, the gNB may configure SRB4 and AppLayerMeasConfig for the UE. In operation 220, the gNB may send these configurations to the UE in an RRCReconfiguration message. Alternatively, if there is no unlicensed serving cell configured by the gNB to the UE, the gNB may configure SRB4 and AppLayerMeasConfig for the UE and send these configurations to the UE in an RRCReconfiguration message. Alternatively, if there is at least one unlicensed serving cell configured by the gNB to the UE (i.e., a cell operating on or using unlicensed spectrum) and the UE does not support application layer measurement reporting in the unlicensed spectrum, the gNB may not configure SRB4 and AppLayerMeasConfig for the UE.

[0143] In operation 225, upon receiving the RRCReconfiguration message with the AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. In operation 230, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 235, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 240, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU in an UL grant (configured grant or dynamic grant).

[0144] In operation 245, if the UL grant for transmitting the MAC PDU is for an unlicensed cell and the gNB does not indicate a CAPC for the UL grant, the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the fixed CAPC of SRB4 (e.g., CAPC 4, CAPC 3, CAPC 2, or CAPC 1) and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of the RBs of other MAC SDUs), if any. In operation 250, the UE (or the MAC layer in the UE) may access the channel based on the determined CAPC of the MAC PDU and transmit the MAC PDU.

[0145] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0146] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0147] - Fixed as the highest priority among SRB0, SRB1, SRB3, SRB4 and other MAC CEs; and / or

[0148] -Configured by the gNB for SRB2 and DRB.

[0149] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0150] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0151] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0152] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0153] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0154] Figure 3A and Figure 3B The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown.

[0155] refer to Figure 3A and Figure 3B , illustrates a method for application layer measurement reporting in a recovery operation, where the CAPC for SRB4 is configured using an RRC recovery message. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are required for this disclosure, and some operations may be selectively omitted as appropriate.

[0156] In operation 300, cell 1 in the licensed spectrum may send a capability query message to a UE in the RRC_CONNECTED state to query the UE's capabilities (e.g., the UE capability query message may request the UE's capabilities for application layer measurement reporting). In operation 305, the UE may send a UE capability information message, which includes the UE's capabilities for application layer measurement reporting. The UE capabilities indicate whether the UE supports application layer measurement reporting in the unlicensed spectrum. In operation 310, cell 1 may configure SRB4 and AppLayerMeasConfig for the UE. In operation 315, cell 1 may send these configurations to the UE in an RRCReconfiguration message.

[0157] In operation 320, upon receiving the RRCReconfiguration message with the AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. In operation 325, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 330, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 335, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. In operation 340, the UE may transmit the MAC PDU to cell 1 in an UL grant (configured grant or dynamic grant).

[0158] In operation 345, the UE may receive an RRCRelease message from cell 1, which includes a suspend configuration (SuspendConfig). In operation 350, the UE may enter the RRC_INACTIVE state. In operation 355, while in the RRC_INACTIVE state, the UE may perform cell reselection to cell 2, which operates in unlicensed spectrum. When the UE camps on cell 2, connection recovery is initiated by the UE. In operation 360, the UE may send an RRCResumeRequest to cell 2. In operation 365, if the UE supports application layer measurement reporting in unlicensed spectrum, cell 2 may configure SRB4, AppLayerMeasConfig, and the CAPC for the LCH of SRB4 to the UE. In operation 370, cell 2 may send these configurations to the UE in an RRCResume message. Here, if cell 2 belongs to the last serving gNB, AppLayerMeasUnlicensed is stored in the UE's AS context. Alternatively, if cell 2 does not belong to the last serving gNB, AppLayerMeasUnlicensed is received in the UE's AS context obtained from the last serving gNB.

[0159] In operation 375, upon receiving RRCResome, the UE may enter RRC_CONNECTED. Upon receiving the RRCResume message with AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. The UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. The UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. The UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU in an UL grant (configured grant or dynamic grant).

[0160] In operation 380, if the gNB does not indicate a CAPC for a UL grant (configured grant or dynamic grant), the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the CAPC of the SRB4 received in the RRC message and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of RBs of other MAC SDUs), if any. The UE (or the MAC layer in the UE) may transmit the MAC PDU after accessing a channel based on the determined CAPC of the MAC PDU.

[0161] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0162] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0163] - Fixed as the highest priority among SRB0, SRB1, SRB3 and other MAC CEs; and / or

[0164] -Configured by the gNB for SRB2, SRB4 and DRB.

[0165] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0166] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0167] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0168] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0169] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0170] Figure 4A and Figure 4B The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown.

[0171] refer to Figure 4A and Figure 4B , illustrates a method for application layer measurement reporting in recovery operations, where the CAPC of SRB4 is fixed or predetermined. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are required for this disclosure, and some operations may be selectively omitted as appropriate.

[0172] In operation 400, cell 1 in the licensed spectrum may send a capability query message to a UE in the RRC_CONNECTED state to query the UE's capabilities (e.g., the UE capability query message may request the UE's capabilities for application layer measurement reporting). In operation 405, the UE may send a UE capability information message, which includes the UE's capabilities for application layer measurement reporting. The UE capabilities indicate whether the UE supports application layer measurement reporting in the unlicensed spectrum. In operation 410, cell 1 may configure SRB4 and AppLayerMeasConfig for the UE. In operation 415, cell 1 may send these configurations to the UE in an RRCReconfiguration message.

[0173] In operation 420, upon receiving the RRCReconfiguration message with the AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. In operation 425, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 430, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 435, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. In operation 440, the UE may transmit the MAC PDU to cell 1 in an UL grant (configured grant or dynamic grant).

[0174] In operation 445, the UE may receive an RRCRelease message from cell 1, which includes a suspension configuration. In operation 450, the UE may enter the RRC_INACTIVE state. In operation 455, while in the RRC_INACTIVE state, the UE may perform cell reselection to cell 2 operating in unlicensed spectrum. When the UE camps on cell 2, connection recovery is initiated by the UE. In operation 460, the UE may send an RRCResumeRequest to cell 2. In operation 465, if the UE supports application layer measurement reporting in unlicensed spectrum, cell 2 may configure SRB4 and AppLayerMeasConfig to the UE. In operation 470, cell 2 may send these configurations to the UE in an RRCResume message. Here, if cell 2 belongs to the last serving gNB, AppLayerMeasUnlicensed is stored in the UE's AS context. Alternatively, if cell 2 does not belong to the last serving gNB, AppLayerMeasUnlicensed is received in the UE's AS context obtained from the last serving gNB.

[0175] In operation 475, upon receiving RRCResome, the UE may enter the RRC_CONNECTED state. Upon receiving the RRCResume message with AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. The UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. The UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. The UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU in an UL grant (configured grant or dynamic grant).

[0176] In operation 480, if the gNB does not indicate a CAPC for a UL grant (configured grant or dynamic grant), the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the fixed CAPC of SRB4 (e.g., CAPC 4, CAPC 3, CAPC 2, or CAPC 1) and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of RBs of other MAC SDUs), if any. The UE (or the MAC layer in the UE) may transmit the MAC PDU after accessing the channel based on the determined CAPC of the MAC PDU.

[0177] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0178] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0179] - Fixed as the highest priority among SRB0, SRB1, SRB3, SRB4 and other MAC CEs; and / or

[0180] -Configured by the gNB for SRB2 and DRB.

[0181] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0182] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0183] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0184] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0185] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0186] Figure 5A and Figure 5B The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown.

[0187] refer to Figure 5A and Figure 5B , illustrates a method for application layer measurement reporting during recovery operation, where the CAPC for SRB4 is configured using an RRC Resume message, and support for application layer measurements in unlicensed spectrum is indicated using an RRC Resume Request message. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are required for this disclosure, and some operations may be selectively omitted as appropriate.

[0188] In operation 500, cell 1 in the licensed spectrum may send a capability query message to a UE in the RRC_CONNECTED state to query the UE's capabilities (e.g., the UE capability query message may request the UE's capabilities for application layer measurement reporting). In operation 505, the UE may send a UE capability information message, which includes the UE's capabilities for application layer measurement reporting. The UE capabilities indicate whether the UE supports application layer measurement reporting in the unlicensed spectrum. In operation 510, cell 1 may configure SRB4 and AppLayerMeasConfig for the UE. In operation 515, cell 1 may send these configurations to the UE in an RRCReconfiguration message.

[0189] In operation 520, upon receiving the RRCReconfiguration message with the AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. In operation 525, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 530, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 535, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. In operation 540, the UE may transmit the MAC PDU to cell 1 in an UL grant (configured grant or dynamic grant).

[0190] In operation 545, the UE may receive an RRCRelease message from cell 1, wherein the message includes a suspension configuration. In operation 550, the UE may enter an RRC_INACTIVE state. In operation 555, while in the RRC_INACTIVE state, the UE may perform cell reselection to cell 2 operating on an unlicensed spectrum. When the UE resides in cell 2, connection recovery is initiated by the UE. In operation 560, the UE may send an RRCResumeRequest to cell 2. The UE may indicate in the RRCResumeRequest whether the UE supports application layer measurement reporting on the unlicensed spectrum. In operation 565, if the UE supports application layer measurement reporting in the unlicensed spectrum, cell 2 may configure SRB4, AppLayerMeasConfig, and CAPC for LCH of SRB4 to the UE. In operation 570, cell 2 may send these configurations to the UE in an RRCResume message.

[0191] In operation 575, upon receiving RRCResome, the UE may enter the RRC_CONNECTED state. Upon receiving the RRCResume message with AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. The UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. The UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. The UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU in an UL grant (configured grant or dynamic grant).

[0192] In operation 580, if the gNB does not indicate a CAPC for a UL grant (configured grant or dynamic grant), the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the CAPC of the SRB4 received in the RRC message and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of RBs of other MAC SDUs), if any. The UE (or the MAC layer in the UE) may transmit the MAC PDU after accessing the channel based on the determined CAPC of the MAC PDU.

[0193] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0194] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0195] - Fixed as the highest priority among SRB0, SRB1, SRB3 and other MAC CEs; and / or

[0196] -Configured by the gNB for SRB2, SRB4 and DRB.

[0197] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0198] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0199] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0200] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0201] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0202] Figure 6A and Figure 6B The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown.

[0203] refer to Figure 6A and Figure 6B , illustrates a method for application layer measurement reporting in a resume operation, where the CAPC for SRB4 is fixed or predetermined, and support for application layer measurements in unlicensed spectrum is indicated by an RRC resume request message. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are required for this disclosure, and some operations may be selectively omitted as appropriate.

[0204] In operation 600, cell 1 in the licensed spectrum may send a capability query message to a UE in the RRC_CONNECTED state to query the UE's capabilities (e.g., the UE capability query message may request the UE's capabilities for application layer measurement reporting). In operation 605, the UE may send a UE capability information message, which includes the UE's capabilities for application layer measurement reporting. The UE capabilities indicate whether the UE supports application layer measurement reporting in the unlicensed spectrum. In operation 610, cell 1 may configure SRB4 and AppLayerMeasConfig for the UE. In operation 415, cell 1 may send these configurations to the UE in an RRCReconfiguration message.

[0205] In operation 620, upon receiving the RRCReconfiguration message with the AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. In operation 625, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 630, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 635, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. In operation 640, the UE may transmit the MAC PDU to cell 1 in an UL grant (configured grant or dynamic grant).

[0206] In operation 645, the UE may receive an RRCRelease message from cell 1, wherein the message includes a suspension configuration. In operation 650, the UE may enter an RRC_INACTIVE state. In operation 655, while in the RRC_INACTIVE state, the UE may perform cell reselection to cell 2 operating on an unlicensed spectrum. When the UE resides in cell 2, connection recovery is initiated by the UE. In operation 660, the UE may send an RRCResumeRequest to cell 2. The UE may indicate in the RRCResumeRequest whether the UE supports application layer measurement reporting on the unlicensed spectrum. In operation 665, if the UE supports application layer measurement reporting in the unlicensed spectrum, cell 2 may configure SRB4 and AppLayerMeasConfig to the UE. In operation 470, cell 2 may send these configurations to the UE in an RRCResume message.

[0207] In operation 675, upon receiving RRCResome, the UE may enter RRC_CONNECTED. Upon receiving the RRCResume message with AppLayerMeasConfig, the UE (or the RRC layer in the UE) may notify the application layer of the configuration of the application layer measurement report. The UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. The UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. The UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU in an UL grant (configured grant or dynamic grant).

[0208] In operation 680, if the gNB does not indicate a CAPC for a UL grant (configured grant or dynamic grant), the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the fixed CAPC of SRB4 (e.g., CAPC 4, CAPC 3, CAPC 2, or CAPC 1) and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of RBs of other MAC SDUs), if any. The UE (or the MAC layer in the UE) may transmit the MAC PDU after accessing the channel based on the determined CAPC of the MAC PDU.

[0209] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0210] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0211] - Fixed as the highest priority among SRB0, SRB1, SRB3, SRB4 and other MAC CEs; and / or

[0212] -Configured by the gNB for SRB2 and DRB.

[0213] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0214] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0215] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0216] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0217] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0218] Figure 7 The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown.

[0219] refer to Figure 7, illustrates a method for application layer measurement reporting in a handover scenario, where the SRB4 CAPC is configured by a handover command. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are required for this disclosure, and some operations may be selectively omitted as appropriate.

[0220] In operation 700, cell 1 (i.e., the source cell / serving cell) may send a capability query message to a UE in the RRC_CONNECTED state to query the UE's capabilities (e.g., the UE capability query message may request the UE's capabilities for application layer measurement reporting). In operation 705, the UE may send a UE capability information message including the UE's capabilities for application layer measurement reporting. The UE capabilities indicate whether the UE supports application layer measurement reporting in unlicensed spectrum.

[0221] In operation 710, cell 1 may transmit the UE's capabilities for application layer measurement reporting (including whether the UE supports application layer measurement reporting in unlicensed spectrum) in a handover request message to cell 2 (i.e., the target cell) via the Xn interface. Here, cell 2 may operate in unlicensed spectrum. Cell 2 may configure the UE with SRB4, AppLayerMeasConfig, and the CAPC for the LCH used for SRB4. In operation 715, if the UE supports application layer measurement reporting in unlicensed spectrum, cell 2 may transmit these configurations to cell 1 in a handover request confirm message. In operation 720, cell 1 may transmit these configurations to the UE in an RRCReconfiguration message with synchronization (or a handover command for handover to cell 2). In operation 725, the UE may perform handover to cell 2 by performing a random access procedure. In operation 730, the UE may transmit an RRCReconfigurationComplete message to cell 2.

[0222] In operation 735, the UE (or the RRC layer in the UE) may also notify the application layer of the configuration of the application layer measurement report for cell 2 received from cell 1. In operation 740, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 745, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 750, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU to cell 2 in a UL grant (configured grant or dynamic grant).

[0223] In operation 755, if the UL grant for transmitting the MAC PDU is for an unlicensed cell and the gNB does not indicate a CAPC for the UL grant, the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the CAPC of SRB4 received in the RRC message and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of the RBs of other MAC SDUs), if any. In operation 760, the UE (or the MAC layer in the UE) may access the channel based on the determined CAPC of the MAC PDU and transmit the MAC PDU.

[0224] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0225] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0226] - Fixed as the highest priority among SRB0, SRB1, SRB3 and other MAC CEs; and / or

[0227] -Configured by the gNB for SRB2, SRB4 and DRB.

[0228] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0229] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0230] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0231] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0232] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0233] Figure 8 The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown.

[0234] refer to Figure 8, illustrates a method for application layer measurement reporting in a handover scenario, where the CAPC of SRB4 is fixed or predetermined. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are required for this disclosure, and some operations may be selectively omitted as appropriate.

[0235] In operation 800, cell 1 (i.e., the source cell / serving cell) may send a capability query message to a UE in the RRC_CONNECTED state to query the UE's capabilities (e.g., the UE capability query message may request the UE's capabilities for application layer measurement reporting). In operation 805, the UE may send a UE capability information message including the UE's capabilities for application layer measurement reporting. The UE capabilities indicate whether the UE supports application layer measurement reporting in unlicensed spectrum.

[0236] In operation 810, cell 1 may transmit the UE's capabilities for application layer measurement reporting (including whether the UE supports application layer measurement reporting in unlicensed spectrum) in a handover request message to cell 2 (i.e., the target cell) via the Xn interface. Here, cell 2 may operate in unlicensed spectrum. Cell 2 may configure SRB4 and AppLayerMeasConfig for the UE. In operation 815, if the UE supports application layer measurement reporting in unlicensed spectrum, cell 2 may transmit these configurations to cell 1 in a handover request confirm message. In operation 820, cell 1 may transmit these configurations to the UE in an RRCReconfiguration message with synchronous reconfiguration (or a handover command for handover to cell 2). In operation 825, the UE may perform handover to cell 2 by performing a random access procedure. In operation 830, the UE may transmit an RRCReconfigurationComplete message to cell 2.

[0237] In operation 835, the UE (or the RRC layer in the UE) may also notify the application layer of the configuration of the application layer measurement report for cell 2 received from cell 1. In operation 840, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 845, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 850, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU to cell 2 in a UL grant (configured grant or dynamic grant).

[0238] In operation 855, if the UL grant for transmitting the MAC PDU is for an unlicensed cell and the gNB does not indicate a CAPC for the UL grant, the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the fixed CAPC of SRB4 (e.g., CAPC 4, CAPC 3, CAPC 2, or CAPC 1) and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of the RBs of other MAC SDUs), if any. In operation 860, the UE (or the MAC layer in the UE) may access the channel based on the determined CAPC of the MAC PDU and transmit the MAC PDU.

[0239] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0240] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0241] - Fixed as the highest priority among SRB0, SRB1, SRB3, SRB4 and other MAC CEs; and / or

[0242] -Configured by the gNB for SRB2 and DRB.

[0243] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0244] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0245] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0246] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0247] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0248] Figure 9A and Figure 9B The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown. Figure 9A and Figure 9B, illustrates a method for application layer measurement reporting in a handover scenario, where the SRB4 CAPC is configured via an RRC reconfiguration message after the handover is complete. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are required for this disclosure, and some operations may be selectively omitted as appropriate.

[0249] In operation 900, cell 1 (i.e., the source cell / serving cell) may send a capability query message to a UE in the RRC_CONNECTED state to query the UE's capabilities (e.g., the UE capability query message may request the UE's capabilities for application layer measurement reporting). In operation 905, the UE may send a UE capability information message including the UE's capabilities for application layer measurement reporting. The UE capabilities indicate whether the UE supports application layer measurement reporting in unlicensed spectrum.

[0250] In operation 910, cell 1 may transmit the UE's capabilities for application layer measurement reporting (including whether the UE supports application layer measurement reporting in unlicensed spectrum) in a handover request message to cell 2 (i.e., the target cell) via the Xn interface. Here, cell 2 may operate in unlicensed spectrum. In operation 915, cell 2 transmits the target cell configuration to cell 1 in a handover request confirm message. In operation 920, cell 1 may transmit the target cell configuration to the UE in an RRCReconfiguration message with synchronous reconfiguration (or a handover command for handover to cell 2). In operation 925, the UE may perform handover to cell 2 by performing a random access procedure. In operation 930, the UE may transmit an RRCReconfigurationComplete message to cell 2.

[0251] In operation 935, upon handover completion, if the UE supports application layer measurement reporting over unlicensed spectrum, cell 2 may configure SRB4, AppLayerMeasConfig, and the CAPC for the LCH of SRB4 to the UE. In operation 940, cell 2 may send these configurations to the UE in an RRCReconfiguration message. Alternatively, if the UE does not support application layer measurement reporting over unlicensed spectrum, cell 2 may not configure SRB4, AppLayerMeasConfig, and the CAPC for the LCH of SRB4 to the UE because cell 2 is operating over unlicensed spectrum. In operation 945, the UE (or the RRC layer in the UE) may also notify the application layer of the configuration of cell 2's application layer measurement reporting received from cell 1. In operation 950, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 955, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 960, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU to cell 2 in a UL grant (configured grant or dynamic grant).

[0252] In operation 965, if the UL grant for transmitting the MAC PDU is for an unlicensed cell and the gNB does not indicate a CAPC for the UL grant, the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the CAPC of SRB4 received in the RRC message and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of the RBs of other MAC SDUs), if any. In operation 970, the UE (or the MAC layer in the UE) may transmit the MAC PDU after accessing the channel based on the determined CAPC of the MAC PDU.

[0253] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0254] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0255] - Fixed as the highest priority among SRB0, SRB1, SRB3 and other MAC CEs; and / or

[0256] -Configured by the gNB for SRB2, SRB4 and DRB.

[0257] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0258] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0259] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0260] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0261] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0262] Figure 10A and Figure 10B The signaling flow for application layer measurement reporting between the UE and the gNB according to an embodiment of the present disclosure is shown.

[0263] refer to Figure 10A and Figure 10B This document illustrates a method for application layer measurement reporting in a handover scenario, where SRB4 and AppLayerMeasConfig are configured via an RRC reconfiguration message after the handover is complete, but the SRB4 CAPC is fixed or predetermined. For clarity and ease of understanding, the following operations are disclosed. It should be understood that not all of these operations are essential to this disclosure, and some operations may be selectively omitted as appropriate.

[0264] In operation 1000, cell 1 (i.e., the source cell / serving cell) may send a capability query message to a UE in the RRC_CONNECTED state to query the UE's capabilities (e.g., the UE capability query message may request the UE's capabilities for application layer measurement reporting). In operation 1005, the UE may send a UE capability information message including the UE's capabilities for application layer measurement reporting. The UE capabilities indicate whether the UE supports application layer measurement reporting in unlicensed spectrum.

[0265] In operation 1010, cell 1 may transmit the UE's capabilities for application layer measurement reporting (including whether the UE supports application layer measurement reporting in unlicensed spectrum) in a handover request message to cell 2 (i.e., the target cell) via the Xn interface. Here, cell 2 may operate in unlicensed spectrum. In operation 1015, cell 2 transmits the target cell configuration to cell 1 in a handover request confirm message. In operation 1020, cell 1 may transmit the target cell configuration to the UE in an RRCReconfiguration message with synchronous reconfiguration (or a handover command for handover to cell 2). In operation 1025, the UE may perform handover to cell 2 by performing a random access procedure. In operation 1030, the UE may transmit an RRCReconfigurationComplete message to cell 2.

[0266] In operation 1035, upon handover completion, if the UE supports application layer measurement reporting in unlicensed spectrum, cell 2 may configure SRB4 and AppLayerMeasConfig for the UE. In operation 1040, cell 2 may send these configurations to the UE in an RRCReconfiguration message. Alternatively, if the UE does not support application layer measurement reporting in unlicensed spectrum, cell 2 may not configure SRB4 and AppLayerMeasConfig for the UE because cell 2 is operating in unlicensed spectrum. In operation 1045, the UE (or the RRC layer in the UE) may also notify the application layer of the configuration of cell 2's application layer measurement reporting received from cell 1. In operation 1050, the UE (or the RRC layer in the UE) may receive the application layer measurement report from the application layer. In operation 1055, the UE (or the RRC layer in the UE) may generate a MeasurementReportAppLayer message for transmission using SRB4. In operation 1060, the UE (or the MAC layer in the UE) may generate a MAC PDU including the MAC SDU of the MeasurementReportAppLayer message. The UE may determine to transmit the MAC PDU to cell 2 in a UL grant (configured grant or dynamic grant).

[0267] In operation 1065, if the UL grant for transmitting the MAC PDU is for an unlicensed cell and the gNB does not indicate a CAPC for the UL grant, the UE (or the MAC layer in the UE) may determine the CAPC of the MAC PDU by considering the fixed CAPC of SRB4 (e.g., CAPC 4, CAPC 3, CAPC 2, or CAPC 1) and the CAPCs of other MAC SDUs included in the MAC PDU (i.e., the CAPCs of the RBs of other MAC SDUs), if any. In operation 1070, the UE (or the MAC layer in the UE) may access the channel based on the determined CAPC of the MAC PDU and transmit the MAC PDU.

[0268] Determination of the CAPC of the MAC PDU: The Channel Access Priority Class (CAPC) of the radio bearer and MAC CE is fixed or configurable:

[0269] - Fixed as the lowest priority for filling BSR and recommending bit rate MAC CE;

[0270] - Fixed as the highest priority among SRB0, SRB1, SRB3, SRB4 and other MAC CEs; and / or

[0271] -Configured by the gNB for SRB2 and DRB.

[0272] When Type 1 LBT is performed for transmission of uplink TBs and when CAPC is not indicated in the DCI, the UE may select the CAPC as follows:

[0273] - If only MAC CEs are included in the TB, the highest priority CAPC of those MAC CEs is used;

[0274] - If a CCCH SDU is included in the TB, the highest priority CAPC (i.e., CAPC 1) is used (or the highest priority CAPC of the CCCH SDU is used);

[0275] - If a DCCH SDU is included in the TB, the highest priority CAPC of the DCCH SDU is used; and / or

[0276] - Otherwise, the lowest priority CAPC of the logical channel with MAC SDUs multiplexed in the TB is used.

[0277] In various embodiments of the present disclosure, if a UE is in the RRC_IDLE state, the UE may include an indication of whether the UE supports application layer measurement reporting over unlicensed spectrum in the RRC Setup Request (RRCSetupRequest) or RRC Setup Complete (RRCSetupComplete) message during the connection establishment procedure. Based on this indication, if the UE supports application layer measurement reporting over unlicensed spectrum and the cell to which the UE is establishing a connection is an unlicensed cell, the cell may configure SRB4 and AppLayerMeasConfig for the UE and send these configurations to the UE in an RRC Setup (RRCSetup) or RRCReconfiguration message. The CAPC for the LCH used for SRB4 may be fixed. Alternatively, based on this indication, if the UE supports application layer measurement reporting over unlicensed spectrum and the cell to which the UE is establishing a connection is an unlicensed cell, the cell may configure SRB4, AppLayerMeasConfig, and the CAPC for the LCH used for SRB4 and send these configurations to the UE in an RRCSetup or RRCReconfiguration message.

[0278] In various embodiments of the present disclosure, the CAPC for the LCH of SRB4 may be configured by the gNB in ​​system information rather than a dedicated RRC message, and is used to determine the CAPC of the MAC PDU including the application layer measurement report.

[0279] Figure 11 An electronic device according to an embodiment of the present disclosure is shown.

[0280] refer to Figure 11 , the electronic device 1100 may include a processor 1110, a transceiver 1120, and a memory 1130. However, not all of the components shown are required. The electronic device 1100 may be composed of Figure 11 Furthermore, according to another embodiment, the processor 1110 , the transceiver 1120 , and the memory 1130 may be implemented as a single chip.

[0281] The electronic device 1100 may correspond to the above-mentioned UE.

[0282] The aforementioned components will now be described in detail.

[0283] The processor 1110 may include one or more processors or other processing devices that control the functions, processes, and / or methods provided. The operations of the electronic device 1100 may be implemented by the processor 1110.

[0284] The transceiver 1120 may include an RF transmitter for up-converting and amplifying a transmitted signal, and an RF receiver for down-converting the frequency of a received signal. However, according to another embodiment, the transceiver 1120 may be implemented by more or fewer components than those shown in the components.

[0285] The transceiver 1120 may be connected to the processor 1110 and transmit and / or receive signals. The signals may include control information and data. In addition, the transceiver 1120 may receive signals through a wireless channel and output the signals to the processor 1110. The transceiver 1120 may transmit signals output from the processor 1110 through a wireless channel.

[0286] The memory 1130 may store control information or data included in a signal obtained by the electronic device 1100. The memory 1130 may be connected to the processor 1110 and store at least one instruction, protocol, or parameter for the provided functions, processes, and / or methods. The memory 1130 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0287] Figure 12 A base station according to an embodiment of the present disclosure is shown.

[0288] refer to Figure 12 , the base station 1200 may include a processor 1210, a transceiver 1220, and a memory 1230. However, all the components shown are not required. The base station 1200 may be composed of Figure 12 Furthermore, according to another embodiment, the processor 1210 , the transceiver 1220 , and the memory 1230 may be implemented as a single chip.

[0289] Base station 1200 may correspond to the above-mentioned gNB.

[0290] The aforementioned components will now be described in detail.

[0291] The processor 1210 may include one or more processors or other processing devices that control the functions, processes, and / or methods provided. The operations of the base station 1200 may be implemented by the processor 1210.

[0292] The transceiver 1220 may include an RF transmitter for up-converting and amplifying a transmitted signal, and an RF receiver for down-converting the frequency of a received signal. However, according to another embodiment, the transceiver 1220 may be implemented by more or fewer components than those shown in the components.

[0293] The transceiver 1220 may be connected to the processor 1210 and transmit and / or receive signals. The signals may include control information and data. In addition, the transceiver 1220 may receive signals through a wireless channel and output the signals to the processor 1210. The transceiver 1220 may transmit signals output from the processor 1210 through a wireless channel.

[0294] The memory 1230 may store control information or data included in a signal obtained by the base station 1200. The memory 1230 may be connected to the processor 1210 and store at least one instruction, protocol, or parameter for the provided functions, processes, and / or methods. The memory 1230 may include a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, a DVD, or other storage devices.

[0295] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

[0296] As described above, the embodiments disclosed in the specification and the drawings are only used to present specific examples to easily explain the content of the present disclosure and to help understand, and are not intended to limit the scope of the present disclosure. Therefore, in addition to the embodiments disclosed herein, the scope of the present disclosure should be analyzed to include all changes or modifications derived from the technical concept of the present disclosure.

[0297] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: receiving configuration information for application layer measurement reporting from a base station; Generate a MAC protocol data unit (PDU) including a medium access control MAC service data unit (SDU) of an application layer measurement report message based on the configuration information; determining a CAPC for the MAC PDU based on a channel access priority level CAPC of a logical channel LCH for signalling radio bearer 4 SRB4, in case the uplink UL grant for the MAC PDU is associated with a shared spectrum; and After the channel access procedure of the MAC PDU-based CAPC, the MAC PDU is sent to the base station.

2. The method according to claim 1, wherein The CAPC for the LCH of SRB4 is configured by a radio resource control RRC message or is predetermined.

3. The method according to claim 1, wherein Determining the CAPC of a MAC PDU also includes: The CAPC of the MAC PDU is determined based on the CAPC of the LCH for SRB4 and one or more CAPCs of one or more other MAC SDUs included in the MAC PDU.

4. The method according to claim 1, further comprising: receiving a UE capability query message from a base station requesting capability for application layer measurement reporting; and A UE capability information message is sent to the base station, indicating that the UE can support application layer measurement reporting on the shared spectrum.

5. A method performed by a base station in a wireless communication system, the method comprising: Sending configuration information for application layer measurement reporting to user equipment UE; and receiving a MAC protocol data unit (PDU) including a medium access control MAC service data unit (SDU) of an application layer measurement report message generated based on the configuration information from the UE, In a case where an uplink UL grant for a MAC PDU is associated with a shared spectrum, a channel access priority level CAPC of the MAC PDU is associated with a CAPC of a logical channel LCH for signaling radio bearer 4 SRB4.

6. The method according to claim 5, wherein: The CAPC for the LCH of SRB4 is configured by a radio resource control RRC message or is predetermined.

7. The method according to claim 5, wherein: The CAPC of the MAC PDU is associated with the CAPC of the LCH for SRB4 and one or more CAPCs of one or more other MAC SDUs included in the MAC PDU.

8. The method according to claim 5, further comprising: Sending a UE capability query message to the UE requesting capability for application layer measurement reporting; and A UE capability information message is received from the UE indicating that the UE is capable of supporting application layer measurement reporting on the shared spectrum.

9. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; and a controller operatively coupled to the transceiver, the controller configured to: receiving, via the transceiver, configuration information for application layer measurement reporting from a base station, Generate a MAC protocol data unit (PDU) including a medium access control MAC service data unit (SDU) of an application layer measurement report message based on the configuration information, determining the CAPC of the MAC PDU based on the channel access priority level CAPC of the logical channel LCH for signalling radio bearer 4 SRB4 in case the uplink UL grant for the MAC PDU is associated with shared spectrum, and After the channel access procedure of the MAC PDU-based CAPC, the MAC PDU is transmitted to the base station via the transceiver.

10. The UE according to claim 9, wherein: The CAPC for the LCH of SRB4 is configured by a radio resource control RRC message or is predetermined.

11. The UE according to claim 9, wherein: The controller is further configured to: The CAPC of the MAC PDU is determined based on the CAPC of the LCH for SRB4 and one or more CAPCs of one or more other MAC SDUs included in the MAC PDU.

12. The UE according to claim 9, wherein: The controller is further configured to: receiving, via the transceiver, a UE capability query message from a base station requesting capability for application layer measurement reporting, and A UE capability information message indicating that the UE can support application layer measurement reporting on the shared spectrum is sent to the base station via the transceiver.

13. A base station in a wireless communication system, the base station comprising: transceiver; and a controller operatively coupled to the transceiver, the controller configured to: sending configuration information for application layer measurement reporting to a user equipment UE via a transceiver, and receiving, via the transceiver, a MAC protocol data unit (PDU) including a medium access control (MAC) service data unit (SDU) of an application layer measurement report message generated based on the configuration information from the UE, In a case where an uplink UL grant for a MAC PDU is associated with a shared spectrum, a channel access priority level CAPC of the MAC PDU is associated with a CAPC of a logical channel LCH for signaling radio bearer 4 SRB4.

14. The base station according to claim 13, wherein: The CAPC for the LCH of SRB4 is configured by a radio resource control RRC message or is predetermined, and The CAPC of the MAC PDU is associated with the CAPC of the LCH for SRB4 and one or more CAPCs of one or more other MAC SDUs included in the MAC PDU.

15. The base station according to claim 13, wherein: The controller is further configured to: sending a UE capability query message to the UE via the transceiver requesting capability for application layer measurement reporting, and A UE capability information message is received from the UE via the transceiver, indicating that the UE is capable of supporting application layer measurement reporting on the shared spectrum.

Images