WO2022038562A1 - Deactivation behavior for semi-persistent csi reporting - Google Patents

Abstract

Apparatuses, methods, and systems are disclosed for deactivation behavior for semi-persistent CSI reporting. One apparatus (700) includes a processor (705) and a transceiver (725) that receives (905) a reporting configuration for semi-persistent CSI reporting from a RAN node (210), said reporting configuration including a deactivation behavior. The processor (705) performs and reports (910) CSI measurements to the RAN node (210) according to an activated semi-persistent CSI reporting configuration. The processor (705) further receives (915) a deactivation command for the semi-persistent CSI reporting from the RAN node (210) and performs (920) the configured deactivation behavior until transmission of an acknowledgement for the deactivation command.

Description

DEACTIVATION BEHAVIOR FOR SEMI-PERSISTENT CSI REPORTING

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to United States Provisional Patent Application Number 63/067,830 entitled “SEMI-PERSISTENT Ll-RSRP REPORTING BEHAVIOR FOR OPERATION IN UNLICENSED SPECTRUM” and filed on August 19, 2020 for Alexander Johann Maria Golitschek Edler von Elbwart, which application is incorporated herein by reference. This application also claims priority to United States Provisional Patent Application Number 63/071,284 entitled “SEMI-PERSISTENT Ll-RSRP REPORTING BEHAVIOR FOR OPERATION IN UNLICENSED SPECTRUM” and filed on August 26, 2020 for Alexander Johann Maria Golitschek Edler von Elbwart, which application is incorporated herein by reference.

FIELD

[0002] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to configuring a deactivation behavior for semi-persistent Channel State Information (“CSI”) reporting (e.g., Layer-1 Reference Signal Received Power (“Ll-RSRP”) reporting), e.g., for operation in unlicensed spectrum.

BACKGROUND

[0003] For operation in unlicensed spectrum, because a channel may be shared among various, unrelated users it is possible that a message cannot be transmitted by the UE because the channel is busy at the corresponding time.

BRIEF SUMMARY

[0004] Disclosed are procedures for deactivation behavior for semi-persistent Channel State Information (“CSI”) reporting, e.g., during operation using unlicensed spectrum. Said procedures may be implemented by apparatus, systems, methods, or computer program products.

[0005] One method of a User Equipment (“UE”) for deactivation behavior for semi- persistent CSI reporting includes receiving a reporting configuration for semi-persistent CSI reporting from a Radio Access Network (“RAN”) node, said reporting configuration including a deactivation behavior. The method includes reporting CSI measurements to the RAN node according to an activated semi-persistent CSI reporting configuration. The method includes receiving a deactivation command for the semi-persistent CSI reporting from the RAN node and performing the configured deactivation behavior until transmission of an acknowledgement for the deactivation command.

[0006] One method of a RAN for deactivation behavior for semi-persistent CSI reporting includes sending to a UE a reporting configuration for semi-persistent CSI reporting, said reporting configuration including a deactivation behavior. The method includes receiving a CSI measurements report from the UE according to an activated semi-persistent CSI reporting configuration and sending to the UE a deactivation command for the semi-persistent CSI reporting. The method includes monitoring for reports from the UE according to the configured deactivation behavior until reception of an acknowledgement for the deactivation command.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0008] Figure 1 is a block diagram illustrating one embodiment of a wireless communication system for deactivation behavior for semi-persistent CSI reporting;

[0009] Figure 2 is a call-flow diagram illustrating one embodiment of semi-persistent CSI reporting behavior for operation in unlicensed spectrum;

[0010] Figure 3 is a call-flow diagram illustrating another embodiment of semi -persistent CSI reporting behavior for operation in unlicensed spectrum;

[0011] Figure 4 is a call -flow diagram illustrating a further embodiment of semi -persistent CSI reporting behavior for operation in unlicensed spectrum;

[0012] Figure 5 is a call-flow diagram illustrating an additional embodiment of semi- persistent CSI reporting behavior for operation in unlicensed spectrum;

[0013] Figure 6 is a block diagram illustrating one embodiment of a Fifth-Generation (“5G”) New Radio (“NR”) protocol stack;

[0014] Figure 7 is a block diagram illustrating one embodiment of a user equipment apparatus that may be used for deactivation behavior for semi-persistent CSI reporting;

[0015] Figure 8 is a block diagram illustrating one embodiment of a network apparatus that may be used for deactivation behavior for semi-persistent CSI reporting;

[0016] Figure 9 is a flowchart diagram illustrating one embodiment of a first method for deactivation behavior for semi-persistent CSI reporting; and [0017] Figure 10 is a flowchart diagram illustrating one embodiment of a second method for deactivation behavior for semi -persistent CSI reporting.

DETAILED DESCRIPTION

[0018] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.

[0019] For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.

[0020] Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non- transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0021] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0022] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc readonly memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0023] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object- oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)).

[0024] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0025] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0026] As used herein, a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of’ includes one and only one of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C,” includes one and only one of A, B, or C, and excludes combinations of A, B, and C.” As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.

[0027] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.

[0028] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams.

[0029] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.

[0030] The call-flow diagrams, flowchart diagrams and/or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0031] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0032] Although various arrow types and line types may be employed in the call-flow, flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0033] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0034] Generally, the present disclosure describes systems, methods, and apparatus for semi-persistent CSI reporting behavior for operation in unlicensed spectrum. In certain embodiments, the methods may be performed using computer code embedded on a computer- readable medium. In certain embodiments, an apparatus or system may include a computer- readable medium containing computer-readable code which, when executed by a processor, causes the apparatus or system to perform at least a portion of the below described solutions.

[0035] The present disclosure defines UE behavior for deactivation of semi-persistent CSI reporting during operation in unlicensed (i.e., shared) spectrum. During operation in unlicensed spectrum, the UE may receive a MAC CE deactivation command corresponding to a previously activated semi-persistent CSI reporting configuration. In response to the MAC CE deactivation command, the UE attempts to send an acknowledgement transmission. [0036] However, the UE may be unable to transmit a corresponding acknowledgement UE because the channel is busy at the corresponding time (also known as Listen-Before-Talk (“LBT”) failure). Because the acknowledgement cannot be transmitted, it is currently unclear whether the UE should still deactivate the corresponding reporting, continue in its previous state (i.e., with the semi-persistent CSI reporting still being active) at least until the acknowledgement corresponding to the deactivation can be transmitted, or perform some other behavior.

[0037] In various embodiments, a UE may require a time period between the reception of a MAC CE command and executing or applying any corresponding action, referred to herein as the "action time". The duration of the action time may depend on the specific action to be executed or applied, and also on processing capabilities of a device. Without loss of generality, the following descriptions use the term "action time" without restricting this to a specific value; however, for illustration it may be envisaged that for the purpose of applying a MAC CE deactivation command for semi-persistent CSI reporting, the action time could be defined as a time duration (such as 3 ms) after the reception of the corresponding MAC CE, or with another reference, e.g. as a time duration (such as 3 ms) after the first acknowledgement is expected to be transmitted, where the acknowledgement corresponds to the reception of the MAC CE.

[0038] Note that for semi-persistent reporting on the Physical Uplink Control Channel (“PUCCH”), the PUCCH resource used for transmitting the CSI report are configured by reportConfigType . Semi-persistent reporting on PUCCH is activated by an activation command (e.g., as described in clause 6.1.3.16 of 3GPP TS 38.321), which selects one of the semi-persistent Reporting Settings for use by the UE on the PUCCH. When the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the Physical Downlink Shared Channel (“PDSCH”) carrying the activation command, the indicated semi-persistent Reporting Setting should be applied starting from the first slot that is after slot n + 2N^^{b rame, i} where p is the Subcarrier Spacing (“SCS”) configuration for the PUCCH. As used herein, “HARQ-ACK” may represent collectively the Positive Acknowledge (“ACK”) and the Negative Acknowledge (“NACK”) and Discontinuous Transmission (“DTX”). ACK means that a Transport Block (“TB”) is correctly received while NACK (or NAK) means a TB is erroneously received and DTX means that no TB was detected.

[0039] For a UE configured with CSI resource setting(s) where the higher layer parameter resourceType set to 'semiPersistent', when a UE receives an activation command (e.g., as described in clause 6.1.3.12 of 3GPP TS 38.321), for a CSI Reference Signal (“CSI-RS”) resource set(s) for channel measurement and CSI for Interference Measurement (“CSI-IM”) and/or Non-Zero Power (“NZP”) CSI-RS resource set(s) for interference measurement associated with configured CSI resource setting(s), then the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the selection command (e.g., the corresponding actions in 3GPP TS 38.321) and the UE assumptions (including QCL assumptions provided by a list of reference to TCI-State's, one per activated resource) on CSI-RS/CSI-IM transmission corresponding to the configured CSI-RS/CSI-IM resource configuration(s) shall be applied starting from the first slot that is after slot n + 2N^^{b rame, i} where p is the SCS configuration for the PUCCH. If a TCI-State referred to in the list is configured with a reference to an Reference Signal (“RS”) associated with 'QCL-TypeD', that the RS can be an Synchronization Signal and/or Physical Broadcast Channel (“SS/PBCH”) block, periodic or semi-persistent CSI-RS located in same or different Component Carrier (“CC”) or Downlink (“DL”) Bandwidth Part (“BWP”).

[0040] Note that the Transmission Configuration Indicator (“TCI”) state include parameters for configuring Quasi-Co-Location (“QCL”) relationships of antenna ports. The antenna ports may be quasi-co-located with respect to various channel properties, including spatial filter. Two antenna ports are said to be quasi-co-located if properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed.

[0041] For a UE configured with CSI resource setting(s) where the higher layer parameter resourceType set to 'semiPersistenf, when the UE receives a deactivation command (e.g., as described in clause 6.1.3.12 of 3GPP TS 38.321), for an activated CSI-RS/CSI-IM resource set(s) associated with configured CSI resource setting(s), and when the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the deactivation command (e.g., the corresponding actions in 3GPP TS 38.321), then the UE assumption on cessation of CSI-RS/CSI-IM transmission corresponding to the deactivated CSI-RS/CSI-IM resource set(s) shall apply starting from the first slot that is after slot n + 2N^^{b rame, i} where p is the SCS configuration for the PUCCH.

[0042] Figure 1 depicts a wireless communication system 100 for deactivation behavior for semi-persistent CSI reporting, according to embodiments of the disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may be composed of a base unit 121 with which the remote unit 105 communicates using wireless communication links 123. Even though a specific number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 may be included in the wireless communication system 100.

[0043] In one implementation, the RAN 120 is compliant with the 5G system specified in the Third Generation Partnership Project (“3GPP”) specifications. For example, the RAN 120 may be a Next Generation Radio Access Network (“NG-RAN”), implementing New Radio (“NR”) Radio Access Technology (“RAT”) and/or Long-Term Evolution (“LTE”) RAT. In another example, the RAN 120 may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers (“IEEE”) 802.11-family compliant WLAN). In another implementation, the RAN 120 is compliant with the LTE system specified in the 3 GPP specifications. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16-family standards, among other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0044] In one embodiment, the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. In some embodiments, the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 105 may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (”WTRU”), a device, or by other terminology used in the art. In various embodiments, the remote unit 105 includes a subscriber identity and/or identification module (“SIM”) and the mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM). In certain embodiments, the remote unit 105 may include a terminal equipment (“TE”) and/or be embedded in an appliance or device (e.g., a computing device, as described above).

[0045] The remote units 105 may communicate directly with one or more of the base units 121 in the RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals may be carried over the wireless communication links 123. Here, the RAN 120 is an intermediate network that provides the remote units 105 with access to the mobile core network 140.

[0046] In some embodiments, the remote units 105 communicate with an application server 151 via a network connection with the mobile core network 140. For example, an application 107 (e.g., web browser, media client, telephone and/or Voice-over-Intemet-Protocol (“VoIP”) application) in a remote unit 105 may trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other data connection) with the mobile core network 140 via the RAN 120. The mobile core network 140 then relays traffic between the remote unit 105 and the application server 151 in the packet data network 150 using the PDU session. The PDU session represents a logical connection between the remote unit 105 and the User Plane Function (“UPF”) 141.

[0047] In order to establish the PDU session (or PDN connection), the remote unit 105 must be registered with the mobile core network 140 (also referred to as “attached to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140. As such, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers.

[0048] In the context of a 5G system (“5GS”), the term “PDU Session” refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) through the UPF 141. A PDU Session supports one or more Quality of Service (“QoS”) Flows. In certain embodiments, there may be a one-to-one mapping between a QoS Flow and a QoS profile, such that all packets belonging to a specific QoS Flow have the same 5G QoS Identifier (“5QI”).

[0049] In the context of a 4G/UTE system, such as the Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also referred to as EPS session) provides E2E UP connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Bearer, i.e., atunnel between the remote unit 105 and a Packet Gateway (“PGW”, not shown) in the mobile core network 140. In certain embodiments, there is a one-to-one mapping between an EPS Bearer and a QoS profile, such that all packets belonging to a specific EPS Bearer have the same QoS Class Identifier (“QCI”).

[0050] The base units 121 may be distributed over a geographic region. In certain embodiments, a base unit 121 may also be referred to as an access terminal, an access point, a base, a base station, aNode-B (“NB”), an Evolved Node B (abbreviated as eNodeB or “eNB,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), a 5G/NR Node B (“gNB”), a Home Node-B, a relay node, a RAN node, or by any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, that may include one or more controllers communicably coupled to one or more corresponding base units 121. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The base units 121 connect to the mobile core network 140 via the RAN 120.

[0051] The base units 121 may serve a number of remote units 105 within a serving area, for example, a cell or a cell sector, via a wireless communication link 123. The base units 121 may communicate directly with one or more of the remote units 105 via communication signals. Generally, the base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the wireless communication links 123. The wireless communication links 123 may be any suitable carrier in licensed or unlicensed radio spectrum. The wireless communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the base units 121. Note that during NR operation on unlicensed spectrum (referred to as “NR- U”), the base unit 121 and the remote unit 105 communicate over unlicensed (i.e., shared) radio spectrum.

[0052] In various embodiments, the remote unit 105 receives a configuration 125 for Semi- Persistent (“SP”) CSI reporting. As described in greater detail below, the configuration 125 may include deactivation behavior, including how the remote unit 105 is to respond to the situation where the remote unit 105 is unable to transmit an acknowledgement of the deactivation command, e.g., due to CCA / LBT failure.

[0053] In certain embodiments, the remote unit 105 may send a UE capability indication 127. In one embodiment, the UE capability indication 127 indicates one or more behaviors it supports for the case that the remote unit 105 receives a MAC CE deactivation command for semi- persistent CSI reporting but is not able to transmit an acknowledgement at the expected time. In another embodiment, the UE capability indication 127 indicates an earliest time, such as a minimum time offset, that the remote unit 105 is able to implement a configured deactivation behavior after an event, such as receiving a deactivation command.

[0054] In one embodiment, the mobile core network 140 is a 5GC or an Evolved Packet Core (“EPC”), which may be coupled to a packet data network 150, like the Internet and private data networks, among other data networks. A remote unit 105 may have a subscription or other account with the mobile core network 140. In various embodiments, each mobile core network 140 belongs to a single mobile network operator (“MNO”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0055] The mobile core network 140 includes several network functions (“NFs”). As depicted, the mobile core network 140 includes at least one UPF 141. The mobile core network 140 also includes multiple control plane (“CP”) functions including, but not limited to, an Access and Mobility Management Function (“AMF”) 143 that serves the RAN 120, a Session Management Function (“SMF”) 145, a Policy Control Function (“PCF”) 147, a Unified Data Management function (“UDM””) and a User Data Repository (“UDR”). Although specific numbers and types of network functions are depicted in Figure 1, one of skill in the art will recognize that any number and type of network functions may be included in the mobile core network 140.

[0056] The UPF(s) 141 is/are responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network (DN), in the 5G architecture. The AMF 143 is responsible for termination ofNAS signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF 145 is responsible for session management (i.e., session establishment, modification, release), remote unit (i.e., UE) IP address allocation & management, DE data notification, and traffic steering configuration of the UPF 141 for proper traffic routing.

[0057] The PCF 147 is responsible for unified policy framework, providing policy rules to CP functions, access subscription information for policy decisions in UDR. The UDM is responsible for generation of Authentication and Key Agreement (“AKA”) credentials, user identification handling, access authorization, subscription management. The UDR is a repository of subscriber information and may be used to service a number of network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data that is permitted to be exposed to third party applications, and the like. In some embodiments, the UDM is colocated with the UDR, depicted as combined entity “UDM/UDR” 149.

[0058] In various embodiments, the mobile core network 140 may also include a Network Repository Function (“NRF”) (which provides Network Function (“NF”) service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces (“APIs”)), a Network Exposure Function (“NEF”) (which is responsible for making network data and resources easily accessible to customers and network partners), an Authentication Server Function (“AUSF”), or other NFs defined for the 5GC. When present, the AUSF may act as an authentication server and/or authentication proxy, thereby allowing the AMF 143 to authenticate a remote unit 105. In certain embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.

[0059] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a “network slice” refers to a portion of the mobile core network 140 optimized for a certain traffic type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband (“eMBB”) service. As another example, one or more network slices may be optimized for ultra-reliable low- latency communication (“URLLC”) service. In other examples, a network slice may be optimized for machine-type communication (“MTC”) service, massive MTC (“mMTC”) service, Intemet- of-Things (“loT”) service. In yet other examples, a network slice may be deployed for a specific application service, a vertical service, a specific use case, etc.

[0060] A network slice instance may be identified by a single-network slice selection assistance information (“S-NSSAI”) while a set of network slices for which the remote unit 105 is authorized to use is identified by network slice selection assistance information (“NS SAI”). Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF 145 and UPF 141. In some embodiments, the different network slices may share some common network functions, such as the AMF 143. The different network slices are not shown in Figure 1 for ease of illustration, but their support is assumed.

[0061] While Figure 1 depicts components of a 5G RAN and a 5G core network, the described embodiments for deactivation behavior for semi-persistent CSI reporting apply to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, i.e., a 2G digital cellular network), General Packet Radio Service (“GPRS”), Universal Mobile Telecommunications System (“UMTS”), LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, and the like.

[0062] Moreover, in an LTE variant where the mobile core network 140 is an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as a Mobility Management Entity (“MME”), a Serving Gateway (“SGW”), a PGW, a Home Subscriber Server (“HSS”), and the like. For example, the AMF 143 may be mapped to an MME, the SMF 145 may be mapped to a control plane portion of a PGW and/or to an MME, the UPF 141 may be mapped to an SGW and a user plane portion of the PGW, the UDM/UDR 149 may be mapped to an HSS, etc.

[0063] In the following descriptions, the term “RAN node” is used for the base station/ base unit, but it is replaceable by any other radio access node, e.g., gNB, ng-eNB, eNB, Base Station (“BS”), Access Point (“AP”), etc. Additionally, the term “UE” is used for the mobile station/ remote unit, but it is replaceable by any other remote device, e.g., remote unit, MS, ME, etc. Further, the operations are described mainly in the context of 5G NR. However, the below described solutions/methods are also equally applicable to other mobile communication systems for deactivation behavior for semi -persistent CSI reporting.

[0064] Figure 2 depicts a first procedure 200 for semi-persistent CSI reporting behavior for operation in unlicensed spectrum, according to embodiments of the disclosure. The first procedure involves a UE 205 and a RAN node 210, such as a gNB. The UE 205 may be one embodiment of the remote unit 105, while the RAN node 210 may be one embodiment of the base unit 121. In the depicted embodiment, the UE 205 may receive an instruction to activate semi- persistent CSI reporting from the RAN node 210 (see messaging 215). The UE 205 then performs measurements and sends CSI reports (e.g., measured Ll-RSRP values) according to the activated semi -persistent CSI reporting (see messaging 220).

[0065] At Step 1, at some later time, the RAN node 210 sends to the UE 205 a deactivation command for the semi-persistent CSI reporting (see messaging 225). Here, the deactivation command may be sent in a MAC CE.

[0066] At Step 2, the UE 205 attempts to transmit an acknowledgement of the deactivation command. However, in some embodiments the UE 205 may not be able to send an acknowledgement to the RAN node 210 at the prescribed time, for example due to CCA / LBT failure (see item 230).

[0067] Accordingly, the UE performs a deactivation behavior in response to the deactivation command. Here, the UE may begin performing the deactivation behavior at the “action time” as discussed above. Note that various deactivation behaviors may be configured to be performed until the UE 205 is able to transmit an acknowledgement of the deactivation command. Thus, the deactivation behavior may be performed during the period between receipt of the deactivation command and transmission of an acknowledgement for the deactivation command.

[0068] In various embodiments, the UE 205 is configured with a “contingency” or “fallback” deactivation behavior to perform in the event that the UE 205 is unable to send an acknowledgement of the deactivation command at the prescribed time. Accordingly, a configuration for semi-persistent CSI reporting may include a deactivation behavior that may include operations or actions to perform in the event that the UE 205 is unable to send an acknowledgement of the deactivation command at the prescribed time.

[0069] According to embodiments of a first solution, in case the UE 205 receives a MAC CE deactivation command for semi-persistent CSI reporting, and the UE 205 is not able to transmit a corresponding acknowledgement, the UE 205 continues to report Ll-RSRP until an acknowledgement corresponding to the MAC CE deactivation can be transmitted.

[0070] Accordingly, at Step 3, starting at the action time for the deactivation command (also referred to as “deactivation time”), the UE 205 is not required to conduct the measurements according to the semi-persistent CSI reporting configuration that is being deactivated by the MAC CE deactivation command (see block 235).

[0071] However, at Step 4, the UE 205 may continue to make CSI reports to the RAN node 210 until it is able to send an acknowledgement to the deactivation command (see messaging 240). Here, the reported values may be a last-measured value or a predefined value, according to the embodiments described herein.

[0072] In some embodiments of the first solutions, the UE 205 reports a predefined value as the reported value. In a specific implementation, the UE 205 reports a value representing a "not valid" value, e.g., as given in Table 1 (see below), which may be one of RSRP 0 to RSRP 16 or RSRP 114 to RSRP 126. In another specific implementation, the UE reports a value representing an infinity value, such as RSRP 127 as given in Table 1.

[0073] In another specific implementation, the UE 205 reports a value representing the lowest possible value, such as "RSRP < -140 dBm" as given in Table 1 for LI SS-RSRP and CSI- RSRP or "SS-RSRP < -156 dBm" as given in Table 1 for LI SS-RSRP and CSI-RSRP or "< -156 dBm". In various implementations, the UE 205 is configured with the predefined value, e.g., by RRC signaling (RRC configuration parameter).

Table 1: SS-RSRP and CSI-RSRP measurement report mapping

[0074] According to an extension to the first solution, differential Ll-RSRP based reporting may be necessary, e.g., if nrofReportedRS is configured to be larger than one, or if groupBasedBeamReporting is enabled. Accordingly, from the action time (i.e., deactivation time) until an acknowledgement corresponding to the MAC CE deactivation can be transmitted, the UE 205 may report a predefined differential value for the differential reported value.

[0075] In a specific implementation, the UE reports a differential value representing a "not valid" value, e.g., as given in Table 1 above, which may be one of RSRP 0 to RSRP 16 or RSRP 114 to RSRP 126. In another specific implementation, the UE reports a differential value representing the largest difference between measured RSRP from strongest RSRP, such as DIFFRSRP 15 to represent "-30 > ARSRP" as given in Table 2 (see below). In another specific implementation, the UE is configured with the predefined differential value, e.g., by RRC signaling (RRC configuration parameter).

Table 2: Differential SS-RSRP and CSI-RSRP measurement report mapping for LI reporting

[0076] Continuing on Figure 2, at Step 5, the UE 205 is able to transmit an acknowledgement of the deactivation command, e.g., due to CCA / LBT success (see messaging 245). Here, the acknowledgement may be sent in a MAC CE. [0077] At Step 6, the UE 205 stops performing CSI measurements and stops performing semi-persistent CSI reporting in response to the sending the acknowledgment command (see block 250). In one embodiment, the UE 205 stops the CSI measurement and reporting at an action time after sending the acknowledgement.

[0078] Figure 3 depicts a second procedure 300 for semi-persistent CSI reporting behavior for operation in unlicensed spectrum, according to embodiments of the disclosure. As depicted, at Step 0a the UE 205 may receive an instruction to activate semi-persistent CSI reporting from the RAN node 210 (see messaging 305). At Step 0b, the UE 205 performs measurements and sends CSI reports (e.g., measured Ll-RSRP values) according to the activated semi -persistent CSI reporting (see messaging 310).

[0079] At Step 1, at some later time, the RAN node 210 sends to the UE 205 a deactivation command for the semi-persistent CSI reporting (see messaging 315). Here, the deactivation command may be sent in a MAC CE.

[0080] At Step 2, the UE 205 attempts to transmit an acknowledgement of the deactivation command. However, in some embodiments the UE 205 may not be able to send an acknowledgement to the RAN node 210 at the prescribed time, for example due to CCA / LBT failure (see item 320). Accordingly, the UE 205 performs a contingency deactivation behavior until acknowledgement of the deactivation command is transmitted.

[0081] At Step 3, the UE 205 continues CSI measurements according to the activated Semi-Persistent CSI Reporting (see block 325).

[0082] At Step 4, the UE 205 sends one or more additional CSI reports, i.e., containing newly measured Ll-RSRP values, according to the activated semi-persistent CSI reporting (see messaging 330).

[0083] At Step 5, the UE 205 is able to transmit an acknowledgement of the deactivation command, e.g., due to CCA / LBT success (see messaging 335). Here, the acknowledgement may be sent in a MAC CE.

[0084] At Step 6, the UE 205 stops performing CSI measurements and stops performing semi-persistent CSI reporting in response to the sending the acknowledgment command (see block 340). In one embodiment, the UE 205 stops the CSI measurement and reporting at an action time after sending the acknowledgement.

[0085] Figure 4 depicts a third procedure 400 for semi-persistent CSI reporting behavior for operation in unlicensed spectrum, according to embodiments of the disclosure. As depicted, at Step 0a the UE 205 may receive an instruction to activate semi-persistent CSI reporting from the RAN node 210 (see messaging 405). At Step 0b, the UE 205 performs measurements and sends CSI reports (e.g., measured Ll-RSRP values) according to the activated semi -persistent CSI reporting (see messaging 410).

[0086] At Step 1, at some later time, the RAN node 210 sends to the UE 205 a deactivation command for the semi-persistent CSI reporting (see messaging 415). Here, the deactivation command may be sent in a MAC CE.

[0087] At Step 2, the UE 205 attempts to transmit an acknowledgement of the deactivation command. However, in some embodiments the UE 205 may not be able to send an acknowledgement to the RAN node 210 at the prescribed time, for example due to CCA / LBT failure (see item 420). Accordingly, the UE 205 performs a contingency deactivation behavior until acknowledgement of the deactivation command is transmitted.

[0088] At Step 3, the UE 205 ignores the deactivation command and continues CSI measurements according to the activated Semi-Persistent CSI Reporting (see block 425) until reception of a subsequent deactivation command.

[0089] At Step 4, the UE 205 sends one or more additional CSI reports, i.e., containing newly measured Ll-RSRP values, according to the activated semi-persistent CSI reporting (see messaging 430).

[0090] At Step 5, the RAN node 210 sends to the UE 205 a subsequent deactivation command for the semi-persistent CSI reporting (see messaging 435). Here, the deactivation command may be sent in a MAC CE.

[0091] At Step 6, the UE 205 is able to transmit an acknowledgement of the deactivation command, e.g., due to CCA / LBT success (see messaging 440). Here, the acknowledgement may be sent in a MAC CE.

[0092] At Step 7, the UE 205 stops performing CSI measurements and stops performing semi-persistent CSI reporting in response to the sending the acknowledgment command (see block 445). In one embodiment, the UE 205 stops the CSI measurement and reporting at an action time after sending the acknowledgement.

[0093] Figure 5 depicts a fourth procedure 500 for semi-persistent CSI reporting behavior for operation in unlicensed spectrum, according to embodiments of the disclosure. As depicted, at Step 0a the UE 205 may receive an instruction to activate semi-persistent CSI reporting from the RAN node 210 (see messaging 505). At Step 0b, the UE 205 performs measurements and sends CSI reports (e.g., measured Ll-RSRP values) according to the activated semi -persistent CSI reporting (see messaging 510).

[0094] At Step 1, at some later time, the RAN node 210 sends to the UE 205 a deactivation command for the semi-persistent CSI reporting (see messaging 515). Here, the deactivation command may be sent in a MAC CE.

[0095] At Step 2, the UE 205 attempts to transmit an acknowledgement of the deactivation command. However, in some embodiments the UE 205 may not be able to send an acknowledgement to the RAN node 210 at the prescribed time, for example due to CCA / LBT failure (see item 520). Accordingly, the UE 205 performs a contingency deactivation behavior until acknowledgement of the deactivation command is transmitted. [0096] In the depicted solution, at Step 3 the UE 205 stops performing CSI measurements and stops performing semi-persistent CSI reporting in response to the deactivation command, even though no acknowledgment was transmitted (see block 525).

[0097] At Step 4, at a next opportunity, the UE 205 sends an acknowledgement to the RAN node 210 (see messaging 530).

[0098] According to embodiments of a second solution, the UE 205 indicates its capability which of the following behaviors it supports for the case that the UE 205 receives a MAC CE deactivation command for semi-persistent CSI reporting, but is not transmitting an acknowledgement.

[0099] In an implementation of the second solution, the UE capability indicates one or more of:

• Continue measuring and reporting as per the configuration prior to the deactivation until the acknowledgement for the corresponding MAC CE deactivation can be transmitted

• Continue measuring and reporting as per the configuration prior to the deactivation

• Ignore the corresponding MAC CE deactivation command

• Stopping measuring and/or reporting at the action time

• Behavior according to the first solution and one or more of its implementations and extensions

• Continue reporting as per the configuration prior to the deactivation until the acknowledgement for the corresponding MAC CE deactivation can be transmitted, wherein any report at or after the action time contains the most recent measured Ll-RSRP value

[0100] In an implementation of the second solution, the indicated capability applies in case the acknowledgement corresponding to the MAC CE deactivation command for semi-persistent CSI reporting cannot be transmitted as a result of a failed clear channel assessment.

[0101] In an implementation of the second solution, the indicated capability applies in case the UE operates on an unlicensed, shared, or license-exempt spectrum.

[0102] According to embodiments of a third solution, a UE 205 indicates at what time it is capable of deactivating the semi-persistent CSI reporting, which may be a time offset value to an event. In an implementation of the third solution, the indicated capability applies in case the UE operates on an unlicensed, shared, or license-exempt spectrum.

[0103] In an implementation of the third solution, the UE capability indicates one or more of: an earliest time for deactivation after reception of a MAC CE deactivation command for semi- persistent CSI reporting; and an earliest time for deactivation after transmission of an acknowledgement for a corresponding MAC CE deactivation command for semi-persistent CSI reporting

[0104] In the case where the event is the reception of a MAC CE deactivation command for semi-persistent CSI reporting, the indicated deactivation time may be a certain number of timeslots after reception of a MAC CE deactivation command, such as 3 timeslots. In the case where the event is the transmission of an acknowledgement for a corresponding MAC CE deactivation command for semi-persistent CSI reporting, the indicated deactivation time may be a certain number of timeslots after transmission of the acknowledgement, such as 3 timeslots.

[0105] According to embodiments of the fourth solution, the UE 205 may be configured with its behavior for the case where the UE 205 receives a MAC CE deactivation command for semi-persistent CSI reporting and the UE is not able to transmit a corresponding acknowledgement. In an implementation of the fourth solution, the UE 205 may be configured with one of the following behaviors:

• Continue measuring and reporting as per the configuration prior to the deactivation until the acknowledgement for the corresponding MAC CE deactivation can be transmitted;

• Continue measuring and reporting as per the configuration prior to the deactivation in case the corresponding acknowledgement cannot be transmitted as a result of a failed clear channel assessment;

• Ignore the corresponding MAC CE deactivation command;

• Stopping measuring and reporting at the action time;

• Behavior according to the first embodiment and one or more of its implementations and extensions; and

• Continue reporting as per the configuration prior to the deactivation until the acknowledgement for the corresponding MAC CE deactivation can be transmitted, wherein any report at or after the action time contains the most recent measured Ll-RSRP value.

[0106] According to an implementation of the fourth solution, if a UE 205 indicates one or more capabilities of behaviors it supports for the case that the UE 205 receives a MAC CE deactivation command for semi-persistent CSI reporting but is not able to transmit an acknowledgement at the expected time, and if the UE 205 is configured with its behavior for said case, then the UE 205 expects to be configured only with one of the behaviors for which it indicated a corresponding capability. Likewise, the UE 205 does not expect to be configured with a behavior for which it has not indicated a corresponding capability.

[0107] In an implementation of the fourth solution, the indicated capability applies in case the UE operates on an unlicensed, shared, or license-exempt spectrum.

[0108] According to embodiments of a fifth solution, a UE 205 may be configured at what time it deactivates the semi -persistent CSI reporting. In an implementation of the fifth solution, the configuration indicates one or more of:

• a time corresponding to an offset after reception of a MAC CE deactivation command for semi-persistent CSI reporting, such as 3 timeslots after reception of a MAC CE deactivation command;

• a time corresponding to an offset before or after the transmission of an acknowledgement for a corresponding MAC CE deactivation command for semi-persistent CSI reporting, such as 3 timeslots after transmission of the acknowledgement;

[0109] According to an implementation of the fifth solution, if a UE 205 indicates a capability about an earliest time, such as a minimum time offset, and if the UE 205 is configured with its deactivation timing behavior, then the UE 205 expects to be configured only with a time that is equal to or larger than said earliest time.

[0110] Likewise, the UE 205 does not expect to be configured with a time that is shorter than what it has not indicated a corresponding capability, or applies its earliest time, such as a minimum time offset, if it should be configured with its deactivation timing behavior resulting in a shorter time than what it reported as its capability.

[0111] In an implementation of the fifth solution, the configuration applies in case the UE operates on an unlicensed, shared, or license-exempt spectrum.

[0112] While the embodiments and implementations of the above solutions have been described exemplarily for the case of a MAC CE reception of a deactivation command for the semi-persistent CSI reporting procedure; in other embodiments, it is to be understood that the embodiments and implementations can be applied mutatis mutandis to other procedures.

[0113] A non-exhaustive list of MAC CEs, configuration options and capability indications for which the above solution may be applied is provided in Table 3, as follows:

Table 3

[0114] It should be noted that a non-exhaustive list of MAC CEs that are applicable is available in TS 38.321 vl6.1.0 clause 5.18.1, including - but not limited to:

• Semi-Persistent (“SP”) CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE; • Aperiodic CSI Trigger State Sub-selection MAC CE;

• TCI States Activation/Deactivation for UE-specific Physical Downlink Shared Channel (“PDSCH”) MAC CE;

• TCI State Indication for UE-specific Physical Downlink Control Channel (“PDCCH”) MAC CE; • SP CSI reporting on PUCCH Activation/Deactivation MAC CE;

• SP Sounding Reference Signal (“SRS”) Activation/Deactivation MAC CE;

• PUCCH spatial relation Activation/Deactivation MAC CE;

• Enhanced PUCCH spatial relation Activation/Deactivation MAC CE;

• SP Zero-Power (“ZP”) CSI-RS Resource Set Activation/Deactivation MAC CE; • Recommended Bit Rate MAC CE;

• Enhanced SP or Aperiodic (“AP”) SRS Spatial Relation Indication MAC CE;

• SRS Pathloss Reference RS Update MAC CE;

• PUSCH Pathloss Reference RS Update MAC CE; • Serving Cell set based SRS Spatial Relation Indication MAC CE;

• SP Positioning SRS Activation/Deactivation MAC CE;

• Timing Delta MAC CE;

• Guard Symbols MAC CEs.

[0115] Figure 6 depicts a NR protocol stack 600, according to embodiments of the disclosure. While Figure 6 shows the UE 205, the RAN node 210 and an AMF 605 in a 5G core network (“5GC”), these are representative of a set of remote units 105 interacting with a base unit 121 and a mobile core network 140. As depicted, the protocol stack 600 comprises a User Plane protocol stack 610 and a Control Plane protocol stack 615. The User Plane protocol stack 610 includes a physical (“PHY”) layer 625, a Medium Access Control (“MAC”) sublayer 630, the Radio Link Control (“RLC”) sublayer 635, a Packet Data Convergence Protocol (“PDCP”) sublayer 640, and Service Data Adaptation Protocol (“SDAP”) layer 645. The Control Plane protocol stack 615 includes a physical layer 625, a MAC sublayer 630, a RLC sublayer 635, and a PDCP sublayer 640. The Control Plane protocol stack 615 also includes a Radio Resource Control (“RRC”) layer 650 and a Non-Access Stratum (“NAS”) layer 655.

[0116] The AS layer (also referred to as “AS protocol stack”) for the User Plane protocol stack 610 consists of at least SDAP, PDCP, RLC and MAC sublayers, and the physical layer. The AS layer for the Control Plane protocol stack 615 consists of at least RRC, PDCP, RLC and MAC sublayers, and the physical layer. The Layer-2 (“L2”) is split into the SDAP, PDCP, RLC and MAC sublayers. The Layer-3 (“L3”) includes the RRC sublayer 650 and the NAS layer 655 for the control plane and includes, e.g., an Internet Protocol (“IP”) layer and/or PDU Layer (not depicted) for the user plane. LI and L2 are referred to as “lower layers,” while L3 and above (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers.”

[0117] The physical layer 625 offers transport channels to the MAC sublayer 630. The physical layer 625 may perform a Clear Channel Assessment and/or Listen-Before-Talk (“CCA/LBT”) procedure using energy detection thresholds, as described herein. In certain embodiments, the physical layer 625 may send a notification of UL Listen-Before-Talk (“LBT”) failure to a MAC entity at the MAC sublayer 630. The MAC sublayer 630 offers logical channels to the RLC sublayer 635. The RLC sublayer 635 offers RLC channels to the PDCP sublayer 640. The PDCP sublayer 640 offers radio bearers to the SDAP sublayer 645 and/or RRC layer 650. The SDAP sublayer 645 offers QoS flows to the core network (e.g., 5GC). The RRC layer 650 provides for the addition, modification, and release of Carrier Aggregation and/or Dual Connectivity. The RRC layer 650 also manages the establishment, configuration, maintenance, and release of Signaling Radio Bearers (“SRBs”) and Data Radio Bearers (“DRBs”). [0118] The NAS layer 655 is between the UE 205 and the 5GC (i.e., AMF 605). NAS messages are passed transparently through the RAN. The NAS layer 655 is used to manage the establishment of communication sessions and for maintaining continuous communications with the UE 205 as it moves between different cells of the RAN. In contrast, the AS layer is between the UE 205 and the RAN (i.e., RAN node 210) and carries information over the wireless portion of the network.

[0119] Figure 7 depicts a user equipment apparatus 700 that may be used for deactivation behavior for semi-persistent CSI reporting, according to embodiments of the disclosure. In various embodiments, the user equipment apparatus 700 is used to implement one or more of the solutions described above. The user equipment apparatus 700 may be one embodiment of the remote unit 105 and/or the UE 205, described above. Furthermore, the user equipment apparatus 700 may include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725.

[0120] In some embodiments, the input device 715 and the output device 720 are combined into a single device, such as a touchscreen. In certain embodiments, the user equipment apparatus 700 may not include any input device 715 and/or output device 720. In various embodiments, the user equipment apparatus 700 may include one or more of: the processor 705, the memory 710, and the transceiver 725, and may not include the input device 715 and/or the output device 720.

[0121] As depicted, the transceiver 725 includes at least one transmitter 730 and at least one receiver 735. In some embodiments, the transceiver 725 communicates with one or more cells (or wireless coverage areas) supported by one or more base units 121. In various embodiments, the transceiver 725 is operable on unlicensed spectrum. Moreover, the transceiver 725 may include multiple UE panels supporting one or more beams. Additionally, the transceiver 725 may support at least one network interface 740 and/or application interface 745. The application interface(s) 745 may support one or more APIs. The network interface(s) 740 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 740 may be supported, as understood by one of ordinary skill in the art.

[0122] The processor 705, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 705 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 705 executes instructions stored in the memory 710 to perform the methods and routines described herein. The processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the transceiver 725.

[0123] In various embodiments, the processor 705 controls the user equipment apparatus 700 to implement the above described UE behaviors. In certain embodiments, the processor 705 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.

[0124] In various embodiments, the processor 705 receives (i.e., via the transceiver 725) a reporting configuration for semi-persistent CSI reporting from a RAN node, said reporting configuration including a deactivation behavior (e.g., contingency deactivation behavior). The processor 705 performs and reports CSI measurements to the RAN node according to an activated semi-persistent CSI reporting configuration, for example in response to receiving an activation command for semi-persistent CSI reporting. The processor 705 further receives a deactivation command for the semi-persistent CSI reporting from the RAN node and performs the configured deactivation behavior until transmission of an acknowledgement for the deactivation command.

[0125] In some embodiments, performing the configured deactivation behavior includes stopping measurements corresponding to the semi-persistent CSI reporting at an action time after reception of the deactivation command. In certain embodiments, the processor 705 reports a last- measured Ll-RSRP value after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command. In other embodiments, the processor 705 reports a predefined measurement value after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0126] In certain embodiments, the predefined measurement value represents one of: a "not valid" report; a lowest representable measurement value; and an infinity measurement value. In certain embodiments, the predefined measurement value is a predefined differential measurement value. In the aforementioned embodiments, the predefined measurement value may be preconfigured by an RRC configuration parameter.

[0127] In some embodiments, performing the configured deactivation behavior occurs in response to (i.e., is triggered by) determining inability to transmit an acknowledgement of the deactivation command. In certain embodiments, determining the inability to transmit an acknowledgement of the deactivation command includes detecting a failed clear channel assessment and/or failed Listen-Before-Talk procedure.

[0128] In various embodiments, the configured deactivation behavior includes at least one of: a) continuing measuring and reporting CSI measurements according to the activated semi- persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted (including the case where the acknowledgement message cannot be transmitted due to CCA/LBT failure); b) ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; c) stopping both measuring and reporting CSI measurements at the deactivation time; and d) stopping measuring and continuing to report CSI measurements (i.e., reporting a last measured value or reporting a predefined value) after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0129] In some embodiments, the processor 705 sends a UE behavior capability to the RAN node. In such embodiments, the UE behavior capability indicates a set of at least one behavior the UE supports in response to the reception of a deactivation command for the semi- persistent CSI reporting. In certain embodiments, the indicated set of behaviors the UE supports includes at least one of: a) continuing measuring and reporting CSI measurements according to the activated semi-persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted (including the case where the acknowledgement message cannot be transmitted due to CCA/LBT failure); b) ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; c) stopping both measuring and reporting CSI measurements at the deactivation time; and d) stopping measuring and continuing to report CSI measurements (i.e., reporting a last measured value or reporting a predefined value) after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0130] The memory 710, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 710 includes volatile computer storage media. For example, the memory 710 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 710 includes non-volatile computer storage media. For example, the memory 710 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 710 includes both volatile and non-volatile computer storage media.

[0131] In some embodiments, the memory 710 stores data related to deactivation behavior for semi-persistent CSI reporting and/or mobile operation. For example, the memory 710 may store various parameters, panel/beam configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 710 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 700.

[0132] The input device 715, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 715 may be integrated with the output device 720, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 715 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 715 includes two or more different devices, such as a keyboard and a touch panel .

[0133] The output device 720, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 720 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 720 may include, but is not limited to, a Liquid Crystal Display (“LCD”), a Light- Emitting Diode (“LED”) display, an Organic LED (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 720 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 700, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0134] In certain embodiments, the output device 720 includes one or more speakers for producing sound. For example, the output device 720 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 720 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 720 may be integrated with the input device 715. For example, the input device 715 and output device 720 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 720 may be located near the input device 715.

[0135] The transceiver 725 communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver 725 operates under the control of the processor 705 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 705 may selectively activate the transceiver 725 (or portions thereof) at particular times in order to send and receive messages.

[0136] The transceiver 725 includes at least transmitter 730 and at least one receiver 735. One or more transmitters 730 may be used to provide UL communication signals to a base unit 121, such as the UL transmissions described herein. Similarly, one or more receivers 735 may be used to receive DL communication signals from the base unit 121, as described herein. Although only one transmitter 730 and one receiver 735 are illustrated, the user equipment apparatus 700 may have any suitable number of transmitters 730 and receivers 735. Further, the transmitter(s) 730 and the receiver(s) 735 may be any suitable type of transmitters and receivers. In one embodiment, the transceiver 725 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

[0137] In certain embodiments, the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, certain transceivers 725, transmitters 730, and receivers 735 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 740.

[0138] In various embodiments, one or more transmitters 730 and/or one ormore receivers 735 may be implemented and/or integrated into a single hardware component, such as a multitransceiver chip, a system -on-a-chip, an Application-Specific Integrated Circuit (“ASIC”), or other type of hardware component. In certain embodiments, one ormore transmitters 730 and/or one or more receivers 735 may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface 740 or other hardware components/circuits may be integrated with any number of transmitters 730 and/or receivers 735 into a single chip. In such embodiment, the transmitters 730 and receivers 735 may be logically configured as a transceiver 725 that uses one more common control signals or as modular transmitters 730 and receivers 735 implemented in the same hardware chip or in a multi-chip module.

[0139] Figure 8 depicts a network apparatus 800 that may be used for deactivation behavior for semi-persistent CSI reporting, according to embodiments of the disclosure. In one embodiment, network apparatus 800 may be one implementation of an evaluation device, such as the base unit 121 and/or the RAN node 205, as described above. Furthermore, the base network apparatus 800 may include a processor 805, a memory 810, an input device 815, an output device 820, and a transceiver 825.

[0140] In some embodiments, the input device 815 and the output device 820 are combined into a single device, such as a touchscreen. In certain embodiments, the network apparatus 800 may not include any input device 815 and/or output device 820. In various embodiments, the network apparatus 800 may include one or more of: the processor 805, the memory 810, and the transceiver 825, and may not include the input device 815 and/or the output device 820.

[0141] As depicted, the transceiver 825 includes at least one transmitter 830 and at least one receiver 835. Here, the transceiver 825 communicates with one or more remote units 105. Additionally, the transceiver 825 may support at least one network interface 840 and/or application interface 845. The application interface(s) 845 may support one or more APIs. The network interface(s) 840 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 840 may be supported, as understood by one of ordinary skill in the art.

[0142] The processor 805, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 805 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller. In some embodiments, the processor 805 executes instructions stored in the memory 810 to perform the methods and routines described herein. The processor 805 is communicatively coupled to the memory 810, the input device 815, the output device 820, and the transceiver 825.

[0143] In various embodiments, the network apparatus 800 is a RAN node (e.g., gNB) that communicates with one or more UEs, as described herein. In such embodiments, the processor 805 controls the network apparatus 800 to perform the above described RAN behaviors. When operating as a RAN node, the processor 805 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.

[0144] In various embodiments, the processor 805 controls the transceiver 825 to send to a UE a reporting configuration for semi-persistent CSI reporting, said reporting configuration including a deactivation behavior (e.g., contingency deactivation behavior). The transceiver 825 receives a CSI measurements report from the UE according to an activated semi-persistent CSI reporting configuration and sends to the UE a deactivation command for the semi-persistent CSI reporting. Via the transceiver 825, the processor 805 monitors for reports from the UE according to the configured deactivation behavior until reception of an acknowledgement for the deactivation command. [0145] In some embodiments, the transceiver 825 receives a UE behavior capability from the UE, where the UE behavior capability indicates a set of at least one behavior the UE supports in response to the reception of a deactivation command for the semi-persistent CSI reporting. In such embodiments, the configured deactivation behavior is selected based on the UE behavior capability. In certain embodiments, the transceiver 825 sends an activation command for semi- persistent CSI reporting prior to receiving the CSI measurement report and prior to sending the deactivation command.

[0146] In some embodiments, the configured deactivation behavior includes at least one of: a) continuing measuring and reporting CSI measurements according to the activated semi- persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted (including the case where the acknowledgement message cannot be transmitted due to CCA/LBT failure); b) ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; c) stopping both measuring and reporting CSI measurements at the deactivation time; and d) stopping measuring and continuing to report CSI measurements (i.e., reporting a last measured value or reporting a predefined value) after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0147] In some embodiments, monitoring for reports from the UE according to the configured deactivation behavior includes receiving at least one CSI measurement report after transmission of the deactivation command that reports a predefined measurement value. In certain embodiments, the predefined measurement value represents one of: a "not valid" report; a lowest representable measurement value; and an infinity measurement value. In certain embodiments, the predefined measurement value is a predefined differential measurement value. In the aforementioned embodiments, the predefined measurement value may be preconfigured by an RRC configuration parameter.

[0148] The memory 810, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 810 includes volatile computer storage media. For example, the memory 810 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 810 includes non-volatile computer storage media. For example, the memory 810 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 810 includes both volatile and non-volatile computer storage media. [0149] In some embodiments, the memory 810 stores data related to deactivation behavior for semi-persistent CSI reporting. For example, the memory 810 may store parameters, configurations, resource assignments, policies, and the like, as described above. In certain embodiments, the memory 810 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 800.

[0150] The input device 815, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 815 may be integrated with the output device 820, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 815 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 815 includes two or more different devices, such as a keyboard and a touch panel.

[0151] The output device 820, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 820 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 820 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 820 may include a wearable display separate from, but communicatively coupled to, the rest of the network apparatus 800, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 820 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0152] In certain embodiments, the output device 820 includes one or more speakers for producing sound. For example, the output device 820 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 820 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 820 may be integrated with the input device 815. For example, the input device 815 and output device 820 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 820 may be located near the input device 815.

[0153] The transceiver 825 includes at least transmitter 830 and at least one receiver 835. One or more transmitters 830 may be used to communicate with the UE, as described herein. Similarly, one or more receivers 835 may be used to communicate with network functions in the PLMN and/or RAN, as described herein. Although only one transmitter 830 and one receiver 835 are illustrated, the network apparatus 800 may have any suitable number of transmitters 830 and receivers 835. Further, the transmitter(s) 830 and the receiver(s) 835 may be any suitable type of transmitters and receivers.

[0154] Figure 9 depicts one embodiment of a method 900 for deactivation behavior for semi-persistent CSI reporting, according to embodiments of the disclosure. In various embodiments, the method 900 is performed by a user equipment device, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 700, as described above. In some embodiments, the method 900 is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0155] The method 900 begins and receives 905 a reporting configuration for semi- persistent CSI reporting from a RAN node, said reporting configuration including a deactivation behavior (e.g., a contingency deactivation behavior). The method 900 includes reporting 910 CSI measurements to the RAN node according to an activated semi-persistent CSI reporting configuration. The method 900 includes receiving 915 a deactivation command for the semi- persistent CSI reporting from the RAN node. The method 900 includes performing 920 the configured deactivation behavior until transmission of an acknowledgement for the deactivation command. The method 900 ends.

[0156] Figure 10 depicts one embodiment of a method 1000 for deactivation behavior for semi-persistent CSI reporting, according to embodiments of the disclosure. In various embodiments, the method 1000 is performed by a RAN device, such as the base unit 121, the RAN node 210, and/or the network apparatus 800, as described above. In some embodiments, the method 1000 is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0157] The method 1000 begins and sends 1005 to a UE a reporting configuration for semi- persistent CSI reporting, said reporting configuration including a deactivation behavior (e.g., contingency deactivation behavior). The method 1000 includes receiving 1010 a CSI measurements report from the UE according to an activated semi-persistent CSI reporting configuration. The method 1000 includes sending 1015 to the UE a deactivation command for the semi-persistent CSI reporting. The method 1000 includes monitoring 1020 for reports from the UE according to the configured deactivation behavior until reception of an acknowledgement for the deactivation command. The method 1000 ends.

[0158] Disclosed herein is a first apparatus for deactivation behavior for semi-persistent CSI reporting, according to embodiments of the disclosure. The first apparatus may be implemented by a UE device, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 700, described above. The first apparatus includes a processor and a transceiver (i.e., implementing a radio interface) that receives a reporting configuration for semi-persistent CSI reporting from a RAN node, said reporting configuration including a deactivation behavior (e.g., contingency deactivation behavior). The processor performs and reports CSI measurements to the RAN node according to an activated semi-persistent CSI reporting configuration, for example in response to the UE device receiving an activation command for semi-persistent CSI reporting. The processor further receives a deactivation command for the semi-persistent CSI reporting from the RAN node and performs the configured deactivation behavior until transmission of an acknowledgement for the deactivation command.

[0159] In some embodiments, performing the configured deactivation behavior includes stopping measurements corresponding to the semi-persistent CSI reporting at an action time after reception of the deactivation command. In certain embodiments, the processor reports a last- measured Ll-RSRP value after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command. In other embodiments, the processor reports a predefined measurement value after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0160] In certain embodiments, the predefined measurement value represents one of: a "not valid" report; a lowest representable measurement value; and an infinity measurement value. In certain embodiments, the predefined measurement value is a predefined differential measurement value. In the aforementioned embodiments, the predefined measurement value may be preconfigured by an RRC configuration parameter.

[0161] In some embodiments, performing the configured deactivation behavior occurs in response to (i.e., is triggered by) determining inability to transmit an acknowledgement of the deactivation command. In certain embodiments, determining the inability to transmit an acknowledgement of the deactivation command includes detecting a failed clear channel assessment and/or failed Listen-Before-Talk procedure.

[0162] In various embodiments, the configured deactivation behavior includes at least one of: a) continuing measuring and reporting CSI measurements according to the activated semi- persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted (including the case where the acknowledgement message cannot be transmitted due to CCA/LBT failure); b) ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; c) stopping both measuring and reporting CSI measurements at the deactivation time; and d) stopping measuring and continuing to report CSI measurements (i.e., reporting a last measured value or reporting a predefined value) after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0163] In some embodiments, the processor sends a UE behavior capability to the RAN node. In such embodiments, the UE behavior capability indicates a set of at least one behavior the UE supports in response to the reception of a deactivation command for the semi-persistent CSI reporting. In certain embodiments, the indicated set of behaviors the UE supports includes at least one of: a) continuing measuring and reporting CSI measurements according to the activated semi- persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted (including the case where the acknowledgement message cannot be transmitted due to CCA/LBT failure); b) ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; c) stopping both measuring and reporting CSI measurements at the deactivation time; and d) stopping measuring and continuing to report CSI measurements (i.e., reporting a last measured value or reporting a predefined value) after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0164] Disclosed herein is a first method for deactivation behavior for semi -persistent CSI reporting, according to embodiments of the disclosure. The first method may be performed by a UE device, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 700, described above. The first method includes receiving a reporting configuration for semi -persistent CSI reporting from a RAN node, said reporting configuration including a deactivation behavior (e.g., a contingency deactivation behavior). The first method includes reporting CSI measurements to the RAN node according to an activated semi-persistent CSI reporting configuration, for example in response to receiving an activation command for semi-persistent CSI reporting. The first method includes receiving a deactivation command for the semi-persistent CSI reporting from the RAN node and performing the configured deactivation behavior until transmission of an acknowledgement for the deactivation command.

[0165] In some embodiments, performing the configured deactivation behavior includes stopping measurements corresponding to the semi-persistent CSI reporting at an action time after reception of the deactivation command. In certain embodiments, performing the configured deactivation behavior further includes reporting a last-measured Ll-RSRP value after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command. In other embodiments, performing the configured deactivation behavior further includes reporting a predefined measurement value after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0166] In certain embodiments, the predefined measurement value represents one of: a "not valid" report; a lowest representable measurement value; and an infinity measurement value. In certain embodiments, the predefined measurement value is a predefined differential measurement value. In the aforementioned embodiments, the predefined measurement value may be preconfigured by an RRC configuration parameter.

[0167] In some embodiments, performing the configured deactivation behavior occurs in response to (i.e., is triggered by) determining inability to transmit an acknowledgement of the deactivation command. In certain embodiments, determining the inability to transmit an acknowledgement of the deactivation command includes detecting a failed clear channel assessment and/or failed Listen-Before-Talk procedure.

[0168] In various embodiments, the configured deactivation behavior includes at least one of: a) continuing measuring and reporting CSI measurements according to the activated semi- persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted (including the case where the acknowledgement message cannot be transmitted due to CCA/LBT failure); b) ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; c) stopping both measuring and reporting CSI measurements at the deactivation time; and d) stopping measuring and continuing to report CSI measurements (i.e., reporting a last measured value or reporting a predefined value) after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0169] In some embodiments, the first method further includes sending a UE behavior capability to the RAN node. In such embodiments, the UE behavior capability indicates a set of at least one behavior the UE supports in response to the reception of a deactivation command for the semi -persistent CSI reporting. In certain embodiments, the indicated set of behaviors the UE supports includes at least one of: a) continuing measuring and reporting CSI measurements according to the activated semi-persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted (including the case where the acknowledgement message cannot be transmitted due to CCA/LBT failure); b) ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; c) stopping both measuring and reporting CSI measurements at the deactivation time; and d) stopping measuring and continuing to report CSI measurements (i.e., reporting a last measured value or reporting a predefined value) after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0170] Disclosed herein is a second apparatus for deactivation behavior for semi-persistent CSI reporting, according to embodiments of the disclosure. The second apparatus may be implemented by a device in a radio access network (“RAN”), such as the base unit 121, the RAN node 210, and/or the network apparatus 800, described above. The second apparatus includes a processor and a transceiver (i.e., implementing a radio interface) that sends to a UE a reporting configuration for semi-persistent CSI reporting, said reporting configuration including a deactivation behavior (e.g., contingency deactivation behavior). The transceiver receives a CSI measurements report from the UE according to an activated semi-persistent CSI reporting configuration and sends to the UE a deactivation command for the semi-persistent CSI reporting. Via the transceiver, the processor monitors for reports from the UE according to the configured deactivation behavior until reception of an acknowledgement for the deactivation command.

[0171] In some embodiments, the transceiver receives a UE behavior capability from the UE, where the UE behavior capability indicates a set of at least one behavior the UE supports in response to the reception of a deactivation command for the semi -persistent CSI reporting. In such embodiments, the configured deactivation behavior is selected based on the UE behavior capability. In certain embodiments, the transceiver sends an activation command for semi- persistent CSI reporting prior to receiving the CSI measurement report and prior to sending the deactivation command.

[0172] In some embodiments, the configured deactivation behavior includes at least one of: a) continuing measuring and reporting CSI measurements according to the activated semi- persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted (including the case where the acknowledgement message cannot be transmitted due to CCA/LBT failure); b) ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; c) stopping both measuring and reporting CSI measurements at the deactivation time; and d) stopping measuring and continuing to report CSI measurements (i.e., reporting a last measured value or reporting a predefined value) after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0173] In some embodiments, monitoring for reports from the UE according to the configured deactivation behavior includes receiving at least one CSI measurement report after transmission of the deactivation command that reports a predefined measurement value. In certain embodiments, the predefined measurement value represents one of: a "not valid" report; a lowest representable measurement value; and an infinity measurement value. In certain embodiments, the predefined measurement value is a predefined differential measurement value. In the aforementioned embodiments, the predefined measurement value may be preconfigured by an RRC configuration parameter.

[0174] Disclosed herein is a second method for deactivation behavior for semi-persistent CSI reporting, according to embodiments of the disclosure. The second method may be performed by a device in a radio access network (“RAN”), such as the base unit 121, the RAN node 210, and/or the network apparatus 800, described above. The second method includes sending to a UE a reporting configuration for semi-persistent CSI reporting, said reporting configuration including a deactivation behavior (e.g., contingency deactivation behavior). The second method includes receiving a CSI measurements report from the UE according to an activated semi-persistent CSI reporting configuration and sending to the UE a deactivation command for the semi -persistent CSI reporting. The second method includes monitoring for reports from the UE according to the configured deactivation behavior until reception of an acknowledgement for the deactivation command.

[0175] In some embodiments, the second method includes receiving a UE behavior capability from the UE, where the UE behavior capability indicates a set of at least one behavior the UE supports in response to the reception of a deactivation command for the semi-persistent CSI reporting. In such embodiments, the configured deactivation behavior is selected based on the UE behavior capability. In certain embodiments, the second method includes sending an activation command for semi-persistent CSI reporting prior to receiving the CSI measurement report and prior to sending the deactivation command.

[0176] In some embodiments, the configured deactivation behavior includes at least one of: a) continuing measuring and reporting CSI measurements according to the activated semi- persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted (including the case where the acknowledgement message cannot be transmitted due to CCA/LBT failure); b) ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; c) stopping both measuring and reporting CSI measurements at the deactivation time; and d) stopping measuring and continuing to report CSI measurements (i.e., reporting a last measured value or reporting a predefined value) after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command.

[0177] In some embodiments, monitoring for reports from the UE according to the configured deactivation behavior includes receiving at least one CSI measurement report after transmission of the deactivation command that reports a predefined measurement value. In certain embodiments, the predefined measurement value represents one of: a "not valid" report; a lowest representable measurement value; and an infinity measurement value. In certain embodiments, the predefined measurement value is a predefined differential measurement value. In the aforementioned embodiments, the predefined measurement value may be preconfigured by an RRC configuration parameter.

[0178] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

42

CLAIMS A method of a User Equipment (“UE”), the method comprising: receiving a reporting configuration for semi-persistent Channel State Information (“CSI”) reporting, said reporting configuration comprising a (i.e., contingency) deactivation behavior; reporting CSI measurements according to an activated semi-persistent CSI reporting configuration; receiving a deactivation command for the semi-persistent CSI reporting; and performing the configured (i.e., contingency) deactivation behavior until transmission of an acknowledgement for the deactivation command. The method of claim 1, wherein performing the configured deactivation behavior comprises: stopping measurements corresponding to the semi-persistent CSI reporting at an action time after reception of the deactivation command; and reporting a last-measured Ll-RSRP value after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command. The method of claim 1, wherein performing the configured deactivation behavior comprises: stopping measurements corresponding to the semi-persistent CSI reporting at an action time after reception of the deactivation command; and reporting a predefined measurement value after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command. The method of claim 4, wherein the predefined measurement value represents one of: a "not valid" report; a lowest representable measurement value; and an infinity measurement value. The method of claim 4, wherein the predefined measurement value is a predefined differential measurement value. 43 The method of any of claims 3-5, wherein the predefined measurement value is preconfigured by an RRC configuration parameter. The method of claim 1, wherein performing the configured deactivation behavior occurs in response to determining inability to transmit an acknowledgement of the deactivation command. The method of claim 1, wherein the configured deactivation behavior comprises at least one of: continuing measuring and reporting CSI measurements according to the activated semi-persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted; ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; stopping both measuring and reporting CSI measurements at the deactivation time; and stopping measuring and continuing to report CSI measurements after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command. The method of claim 1, further comprising sending a UE behavior capability to the RAN node, wherein the UE behavior capability indicates a set of at least one behavior the UE supports in response to the reception of a deactivation command for the semi-persistent CSI reporting. The method of claim 9, wherein the indicated set of behaviors the UE supports includes at least one of: continuing measuring and reporting CSI measurements according to the activated semi-persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted; ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; 44 stopping both measuring and reporting CSI measurements at the deactivation time; and stopping measuring and continuing to report CSI measurements after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command. A User Equipment (“UE”) apparatus comprising: a transceiver that receives a reporting configuration for semi-persistent Channel State Information (“CSI”) reporting, said reporting configuration comprising a deactivation behavior; and a processor that: reports CSI measurements according to an activated semi-persistent CSI reporting configuration; receives a deactivation command for the semi-persistent CSI reporting; and performs the configured deactivation behavior until transmission of an acknowledgement for the deactivation command. A Radio Access Network (“RAN”) apparatus comprising: a transceiver that: sends to a User Equipment (“UE”) a reporting configuration for semi-persistent Channel State Information (“CSI”) reporting, said reporting configuration comprising a deactivation behavior; receiving a CSI measurements report from the UE according to an activated semi- persistent CSI reporting configuration; and sending to the UE a deactivation command for the semi-persistent CSI reporting; and a processor that monitors for reports from the UE according to the configured deactivation behavior until reception of an acknowledgement for the deactivation command. The apparatus of claim 12, wherein the transceiver further receives a UE behavior capability from the UE, wherein the UE behavior capability indicates a set of at least one behavior the UE supports in response to the reception of a deactivation command for the semi-persistent CSI reporting, wherein the processor selects the configured deactivation behavior based on the UE behavior capability. The method of claim 12, wherein the configured deactivation behavior comprises at least one of: continuing measuring and reporting CSI measurements according to the activated semi-persistent CSI reporting configuration until the acknowledgement of the deactivation command is transmitted; ignoring the deactivation command and continuing to measure and report CSI measurements according to the activated semi-persistent CSI reporting configuration until reception of a subsequent deactivation command; stopping both measuring and reporting CSI measurements at the deactivation time; and stopping measuring and continuing to report CSI measurements after reception of the deactivation command and until transmission of an acknowledgement for the deactivation command. The method of claim 12, wherein monitoring for reports from the UE according to the configured deactivation behavior comprises receiving at least one CSI measurement report after transmission of the deactivation command that reports a predefined measurement value.