[go: up one dir, main page]

WO2025118295A1 - Devices and methods for communication - Google Patents

Devices and methods for communication Download PDF

Info

Publication number
WO2025118295A1
WO2025118295A1 PCT/CN2023/137638 CN2023137638W WO2025118295A1 WO 2025118295 A1 WO2025118295 A1 WO 2025118295A1 CN 2023137638 W CN2023137638 W CN 2023137638W WO 2025118295 A1 WO2025118295 A1 WO 2025118295A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
measurement report
event
mac
report
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/137638
Other languages
French (fr)
Inventor
Lin Liang
Gang Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Priority to PCT/CN2023/137638 priority Critical patent/WO2025118295A1/en
Publication of WO2025118295A1 publication Critical patent/WO2025118295A1/en
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices and methods for measurement report.
  • L1 measurement report there are two types of measurement report, i.e. L1 measurement report and L3 measurement report.
  • L1 measurement report For layer 1 (L1) measurement report, it can be configured by radio resource control (RRC) with: periodic report, semi-Persistent (SP) report on physical uplink control channel (PUCCH) , SP report on physical uplink shared channel (PUSCH) , and/or aperiodic report.
  • RRC radio resource control
  • SP semi-Persistent
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • SRB1 service radio bearer 1
  • the trigger of measurement report is given by one or more conditions and time to trigger (TTT) timer where the condition is satisfied during a time duration of TTT.
  • TTT time to trigger
  • the trigger of transmission is triggered by a request. Therefore, it is worth studying enhancements of the L1 measurement report.
  • embodiments of the present disclosure provide a solution on measurement report.
  • a terminal device comprising: a processor, configured to cause the terminal device to: determine, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; in accordance with a determination that the event of measurement result is satisfied, transmit, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; increase, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, trigger, at the second protocol layer, a measurement report; and in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmit, to a network device, a scheduling request for the measurement report.
  • a communication method performed by a terminal device.
  • the method comprises: determining, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; in accordance with a determination that the event of measurement result is satisfied, transmitting, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; increasing, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, triggering, at the second protocol layer, a measurement report; and in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmitting, to a network device, a scheduling request for the measurement report.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the second aspect.
  • FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates a signaling flow of measurement report in accordance with some embodiments of the present disclosure
  • FIG. 3A and FIG. 3B illustrates schematic diagrams of truncated medium access control control element (MAC CE) structures in accordance with some embodiments of the present disclosure
  • FIG. 5 illustrates a flowchart of a method implemented at a network device, according to some example embodiments of the present disclosure.
  • FIG. 6 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, devices on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV)
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a low power node such as a fe
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • AI Artificial intelligence
  • Machine learning capability it generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g., FR1 (e.g., 450 MHz to 6000 MHz) , FR2 (e.g., 24.25GHz to 52.6GHz) , frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • FR1 e.g., 450 MHz to 6000 MHz
  • FR2 e.g., 24.25GHz to 52.6GHz
  • THz Tera Hertz
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • the embodiments of the present disclosure may be performed in test equipment, e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • the term “resource, ” “transmission resource, ” “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like.
  • a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
  • the term “event of measurement result” used herein may refer to a condition of the measurement result.
  • the term “medium access control (MAC) layer” may refer to a sublayer of data link layer of open system interconnections (OSI) reference model for data transmission.
  • the MAC layer provides two main services to the upper layers; data transfer and radio resource allocation.
  • the term “physical layer” may refer to a bottom-most layer in the OSI.
  • the term “MAC control element (MAC CE) ” used herein may refer to a MAC structure carrying control information.
  • L1 measurement report is introduced.
  • L1 measurement report it needs further study the following mechanisms: reporting as uplink control information (UCI) on PUCCH or PUSCH; and reporting on MAC CE. Further, it also needs to study event triggered report for L1 measurement.
  • UCI uplink control information
  • MAC CE MAC CE
  • a solution on measurement report is proposed.
  • a terminal device determines whether whether an event of measurement result is satisfied based on a measurement result. If the event of measurement result is satisfied, the terminal device increases a counter based on the event satisfied indication. If a value of the counter is equal to or larger than a configured threshold, the terminal device triggers a measurement report. If the measurement report is triggered, the terminal device transmits a scheduling request for the measurement report to a network device. In this way, L1 measurement report can be triggered based on the event of measurement result. The L1 measurement report can be reported in a more suitable manner.
  • FIG. 1 illustrates a schematic diagram of an example communication environment 100 in which example embodiments of the present disclosure can be implemented.
  • a plurality of communication devices including a terminal device 110 and a network device 120, can communicate with each other.
  • the terminal device 110 may be a UE and the network device 120 may be a base station serving the UE.
  • the serving area of the network device 120 may be called a cell 102.
  • the communication environment 100 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell 102, and one or more additional cells may be deployed in the communication environment 100. It is noted that although illustrated as a network device, the network device 120 may be another device than a network device. Although illustrated as a terminal device, the terminal device 110 may be other device than a terminal device.
  • terminal device 110 operating as a UE
  • network device 120 operating as a base station
  • operations described in connection with a terminal device may be implemented at a network device or other device
  • operations described in connection with a network device may be implemented at a terminal device or other device.
  • a link from the network device 120 to the terminal device 110 is referred to as a downlink (DL)
  • a link from the terminal device 110 to the network device 120 is referred to as an uplink (UL)
  • the network device 120 is a transmitting (TX) device (or a transmitter)
  • the terminal device 110 is a receiving (RX) device (or a receiver)
  • the terminal device 110 is a TX device (or a transmitter) and the network device 120 is a RX device (or a receiver) .
  • the communications in the communication environment 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • NR New Radio
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • FIG. 2 illustrates a signaling flow 200 of measurement report in accordance with some embodiments of the present disclosure.
  • the signaling flow 200 will be discussed with reference to FIG. 1, for example, by using the terminal device 110 and the network device 120.
  • the network device 120 may transmit (2005) a first configuration indicating a first set of resources allocated for a scheduling request for a measurement report to the terminal device 110.
  • the terminal device 110 may receive (2005) the first configuration indicating the first set of resources from the network device 120.
  • the first set of resources may be dedicated to the scheduling request.
  • separate scheduling request resources may be be configured for event trigger aperiodic measurement report scheduling request and event trigger SP measurement report scheduling request.
  • the terminal device 110 may perform (2010) a measurement on reference signals.
  • a first layer 1101 (such as, the PHY layer) may perform the measurement.
  • the terminal device 110 may perform the measurement based on a predefined periodicity.
  • the terminal device 110 may perform the measurement based on a configured periodicity.
  • the terminal device 110 may perform a reference signal received power (RSRP) measurement on reference signals from the network device 120.
  • RSRP reference signal received power
  • RSRQ reference signal received quality
  • the terminal device 110 may perform a signal to interference plus noise ratio (SINR) measurement on the reference signals.
  • SINR signal to interference plus noise ratio
  • the terminal device 110 determines (2015) whether an event of measurement result is satisfied based on a measurement result.
  • the measurement result may include one or more of: measured RSRP, measured RSRQ, or measured SINR.
  • the event of measurement result may include that a neighbor cell becomes amount of offset better than primary cell (Pcell) or primary secondary cell (PSCell) .
  • the event of measurement result may include that Pcell/PSCell becomes worse than absolute threshold1 and neighbor cell/Scell becomes better than another absolute threshold2. It is noted that the event of measurement result may also include other events/conditions.
  • the first layer 1101 transmits (2020) an event satisfied indication indicating the event of measurement result being satisfied and the measurement result to a second layer 1102, if the event of measurement result is satisfied.
  • the second layer 1102 receives the event satisfied indication and the measurement result from the first layer 1101, if the event of measurement result is satisfied.
  • the measurement result may include one or more of: measured RSRP, measured RSRQ, or measured SINR.
  • the terminal device 110 for example, the second layer 1102 increases (2025) a counter by a first predetermined number based on the event satisfied indication.
  • the second layer 1102 may increase the counter by one based on the event satisfied indication.
  • the second layer 1102 may start or restart (2030) a first timer after the reception of the event satisfied indication from the first protocol layer 1101. In this case, if the first timer expires, the second layer 1102 may reset the counter to a second predetermined (for example, zero) .
  • the first layer 1101 may transmit (2035) an event unsatisfied indication indicating the event of measurement result being unsatisfied to the second layer 1102.
  • the second layer 1102 may receive the event unsatisfied indication from the first layer 1101.
  • the terminal device 110 may obtain a further measurement result by performing the measurement on reference signals. If the first layer 1101 determines that the event of measurement result is unsatisfied based on the further measurement result, the first layer 1101 may transmit (2035) the event unsatisfied indication to the second layer 1102. In this case, the second layer 1102 may reset the counter to a second predetermined number (for example, zero) based on the event unsatisfied indication.
  • a second predetermined number for example, zero
  • the terminal device 110 for example, the second layer 1102, triggers (2040) a measurement report, if a value of the counter is equal to or larger than a configured threshold.
  • the configured threshold may be preconfigured at the terminal device 110.
  • the network device 120 may configured the configured threshold to the terminal device 110.
  • the terminal device 110 may start a second timer after triggering the measurement report. Alternatively, the terminal device 110 may start the second timer after a transmission of the measurement report. In these cases, if the second timer is running, the terminal device 110 may not trigger the measurement report. In some embodiments, the terminal device 110 may sometimes need periodic measurement reporting when events are contiguously satisfied. For one-shot measurement reporting, the second timer can make the one-shot measurement reporting as if periodic measurement reporting and the period is the timer duration of the second timer.
  • the terminal device 110 may skip triggering the measurement report, during a channel state information (CSI) report being active. Alternatively, the terminal device 110 may cancel the triggered measurement report during the CSI report being active. For example, the terminal device 110 may trigger the event triggered measurement report when periodic or SP L1 CSI reporting are not active. If the CSI reporting is active, the terminal device 110 may not trigger the event measurement report and cancel the triggered measurement report.
  • CSI channel state information
  • the CSI report may be a CSI report on PUSCH.
  • the CSI report may be a semi-persistent (SP) CSI report on PUCCH.
  • the CSI report may be a CSI report indicated by RRC, i.e. no simultaneous activation with event triggered CSI reporting indicator is indicated for those CSI report.
  • the terminal device 110 transmits (2045) a scheduling request for the measurement report to the network device 120, if there are not enough resources for a transmission of the measurement report.
  • the network device 120 receives the scheduling request for the measurement report from the terminal device 110. For example, if the measurement report are trigger by MAC and there is no UL-SCH resources are available for a new transmission, or if the UL-SCH resources cannot accommodate the measurement report MAC CE plus its subheader, the terminal device 110 may transmit the scheduling request for the measurement report.
  • the terminal device 110 may determine whether there are uplink shared channel resources available for the transmission of the measurement report. If there are no uplink shared channel resources available for the transmission of the measurement report, the terminal device 110 may determine that there are not enough resources for the transmission of the measurement report. In some other embodiments, the terminal device 110 may determine whether uplink shared channel resources are able to accommodate a MAC CE including the measurement report and a subheader of the measurement report. If the uplink shared channel resources are unable to accommodate the MAC CE and the subheader, the terminal device 110 may determine that there are not enough resources for the transmission of the measurement report.
  • the network device 120 may transmit (2050) a second configuration indicating a second set of resources allocated for the measurement report to the terminal device 110, after the transmission of the scheduling request.
  • the terminal device 110 may receive the second configuration indicating the second set of resources from the network device 120.
  • the network device 120 may indicate PUSCH resources for aperiodic CSI report, after receiving the scheduling request.
  • the network device 120 may indicate PUSCH resources or PUCCH resources for SP CSI report after receiving the scheduling request.
  • the second layer 1102 of the terminal device 110 may cancel the triggered measurement report if the measurement reported is transmitted on UL-SCH resources.
  • the second layer 1102 of the terminal device 110 may cancel the triggered measurement report if a periodic uplink grant for the measurement report (for example, SP-CSI-radio network temporary identifier (RNTI) scrambled uplink grant DCI for periodic measurement reports or MAC CE activation of SP CSI reporting) is received.
  • RNTI SP-CSI-radio network temporary identifier
  • the terminal device 110 may transmit a new MAC CE or a field in MAC CE indicating the terminal device 110 would like to stop the periodic uplink measurement report, to the network device 120.
  • the terminal device 110 may stop the periodic uplink report when the event is not satisfied any more for a period.
  • the terminal device 110 may transmit (2055) the measurement report to the network device 120.
  • the network device 120 may receive (2055) the measurement report from the terminal device 110.
  • the measurement report may be included in a MAC CE.
  • the MAC CE may be a long MAC CE.
  • the MAC CE may be a short MAC CE.
  • the MAC CE including the measurement report may be truncated.
  • a set of fields in the MAC CE may be truncated based on logic channel prioritization.
  • the long truncated MAC CE may include fields 310-1, 310-2, 310-3, 310-4, 310-5, 310-6, 310-7 and 310-8 and payload 320-1, 320-2, ..., 320-N, where N is an integer number.
  • the short truncated MAC CE may include field 311 and payload 321.
  • a ratio value may be configured for the MAC CE including the measurement report.
  • the ratio value may be indicated by the network device 120.
  • the terminal device 110 may skip generating the MAC CE comprising the measurement report. The terminal device 110 may then transmit the scheduling request for the measurement report. For example, if the ratio of the size of measurement report MAC CE (plus its header) to the size of scheduled MAC PDU is larger than the configured value, the terminal device 110 may not instruct the multiplexing and assembly procedure to generate the MAC CE including the measurement report and trigger scheduling request for the measurement report.
  • the terminal device 110 may skip generating the truncated MAC CE comprising the measurement report. The terminal device 110 may then transmit the scheduling request for the measurement report. For example, if the ratio of the size of measurement report MAC CE after truncation (plus its header) to the size of scheduled MAC PDU is larger than the configured value, the terminal device 110 may not instruct the multiplexing and assembly procedure to generate the truncated measurement report MAC CE and trigger scheduling request for the measurement report.
  • the terminal device 110 may skip generating the MAC CE including the measurement report on the PUSCH.
  • the terminal device 110 may then transmit the scheduling request for the measurement report. For example, if the code rate/modulation coding scheme (MCS) of the PUSCH is higher than a configured value/threshold, the PUSCH is not a valid PUSCH for measurement report, i.e., the terminal device 110 may not generate measurement report MAC CE on this PUSCH.
  • MCS code rate/modulation coding scheme
  • the terminal device 110 may skip generating the MAC CE including the measurement report on the PUSCH.
  • the terminal device 110 may then transmit the scheduling request for the measurement report. For example, if the code rate/modulation coding scheme (MCS) of the PUSCH is lower than a configured value/threshold, the PUSCH is not a valid PUSCH for measurement report, i.e., the terminal device 110 may not generate measurement report MAC CE on this PUSCH.
  • MCS code rate/modulation coding scheme
  • the MAC CE may include a serving cell measurement report and a set of candidate cell measurements.
  • the MAC CE may include cell level RSRP/RSRQ/SINR reporting of serving cell and candidate cells.
  • the set of candidate cell measurements may be sorted in decreasing order. In this case, if the MAC CE is truncated, a subset of lower candidate cell measurements may be truncated.
  • the MAC CE including the measurement report may include an indication of event triggered channel state information report index.
  • the MAC CE may include an indication of event triggered CSI report index, for example, by bitmap indication of all configured CSI report for LTM, value 1 present the CSI report is event triggered and value 0 presents the CSI report is not event triggered.
  • the MAC CE may include each triggered channel state information report.
  • each triggered channel state information report in the MAC CE may be a container of a corresponding channel state information report on uplink control information with padding for byte alignment (i.e. physical layer indicates each reports with the corresponding bit string to MAC) .
  • all triggered channel state information report in the MAC CE may be a container of uplink control information including all corresponding channel state information reports on uplink control information (i.e. physical layer combines each report and indicate one bit string to MAC) .
  • HARQ may not be needed for L1 measurement reports since latency is more important than reliability for L1 measurement.
  • transmission of event trigger measurement report in UCI other than MAC CE has benefit for lower latency where HARQ retransmission is not applied for UCI.
  • UCI may have a scaling factor on the number of allocated resources which has lower code rate than data.
  • For dynamic uplink grant DCI one or more bit fields may be introduced in DCI format, to indicate that event triggered measurement reports or set of indicated event triggered measurement reports is included in the PUSCH granted by this DCI. By using the indication in DCI, network can dynamically schedule measurement report transmission more flexible.
  • the network device 120 may configure PUCCH resources for event triggered periodic reporting, including PUCCH resources and periodicity of PUCCH resources.
  • the terminal device 110 may transmit a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information to the network device 120.
  • the terminal device 110 may request the event triggered periodic reporting by sending MAC CE including the information of satisfied event information and satisfied RS information.
  • the terminal device 110 may receive, from the network device 120, downlink control information indicating a new transmission.
  • the terminal device 110 may then activate a periodic measurement reporting on periodic uplink resources, after a duration from the reception of the downlink control information. For example, after some symbols/time/slot of receiving an uplink grant DCI to indicate new transmission, i.e. NDI field is toggled, for the same HARQ process that includes measurement reporting MAC CE, the terminal device 110 may activate periodic measurement reporting on periodic PUCCH resources.
  • the terminal device 110 may receive, from the network device 120, a downlink MAC CE indicating the MAC is accepted.
  • the terminal device 110 may transmit, to the network device 120, an acknowledgement of the downlink MAC CE and activate a periodic measurement reporting on periodic uplink resources, after a duration from the transmission of the acknowledgement.
  • DL MAC CE from the network device 12 may be indicated to the terminal device 110, including accepted measurement event and reference signal information.
  • the terminal device 110 may activate periodic measurement reporting on periodic PUCCH resources after some symbols/time/slot of transmitting of HARQ-ACK information of PDSCH that includes the DL MAC CE.
  • FIG. 4 illustrates a flowchart of a communication method 400 implemented at a terminal device, in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 400 will be described from the perspective of the terminal device 110 in FIG. 1.
  • a first protocol layer of the terminal device 110 determines whether an event of measurement result is satisfied based on a measurement result.
  • the first protocol layer of the terminal device 110 transmits an event satisfied indication indicating the event of measurement result being satisfied and the measurement result to a second protocol layer of the terminal device.
  • the second protocol layer increases a counter by a first predetermined number based on the event satisfied indication.
  • the second protocol layer triggers a measurement report.
  • the terminal device transmits, to a network device, a scheduling request for the measurement report.
  • the method 400 may further include starting, at the second protocol layer, a first timer after the reception of the event satisfied indication from the first protocol layer; and resetting, at the second protocol layer, the counter to a second predetermined number after an expiration of the timer.
  • the method 400 may further include: in accordance with a determination that the event of measurement result is unsatisfied based on a further measurement result, transmitting, at the first protocol layer to the second protocol layer, an event unsatisfied indication indicating the event of measurement result being unsatisfied; and resetting, at the second protocol layer, the counter to a second predetermined number based on the event unsatisfied indication.
  • the method 400 may further include: starting a second timer after triggering the measurement report; or starting the second timer after the transmission of the measurement report, wherein the measurement report is not triggered during running time of the second timer.
  • the method 400 may further include: performing at least one of the followings during a channel state information report being active: skipping triggering the measurement report, or cancelling the triggered measurement report.
  • the channel state information report comprises at least one of: a channel state information report on physical uplink shared channel, a semi-persistent channel state information report on physical uplink control channel, a channel state information report indicated by radio resource control signaling.
  • the method 400 may further include: determining whether there are uplink shared channel resources available for the transmission of the measurement report; and in accordance with a determination that there are no uplink shared channel resources available for the transmission of the measurement report, determining that there are not enough resources for the transmission of the measurement report.
  • the method 400 may further include: determining whether uplink shared channel resources are able to accommodate a medium access control control element (MAC CE) comprising the measurement report and a subheader of the measurement report; and in accordance with a determination that the uplink shared channel resources are unable to accommodate the MAC CE and the subheader, determining that there are not enough resources for the transmission of the measurement report.
  • MAC CE medium access control control element
  • the method 400 may further include: receiving, from the network device, a first configuration indicating a first set of resources allocated for the scheduling request for the measurement report.
  • the method 400 may further include: receiving, from the network device, a second configuration indicating a second set of resources allocated for the measurement report, after the transmission of the scheduling request.
  • the method 400 may further include: in accordance with a determination that the measurement report is an event trigger one time report, cancelling, at the second protocol layer, the measurement report after the transmission of the measurement report.
  • the method 400 may further include: in accordance with a determination that the measurement report is an event trigger period report, cancelling, at the second protocol layer, the measurement report after a period uplink grant for measurement reporting is received.
  • the method 400 may further include: transmitting, to the network device, a MAC CE indicating that the terminal device is to stop the event trigger period report.
  • the method 400 may further include: transmitting, to the network device, the measurement report comprised in a MAC CE.
  • a set of fields in the MAC CE is truncated based on logic channel prioritization.
  • a ratio value is configured for the MAC CE comprising the measurement report.
  • the method 400 may further include: in accordance with a determination that a ratio of a size of the MAC CE comprising the measurement report to a size of a scheduled medium access control protocol data unit is larger than the ratio value, skipping generating the MAC CE comprising the measurement report; and transmit the scheduling request for the measurement report.
  • the method 400 may further include: in accordance with a determination that a ratio of a size of the MAC CE comprising the measurement report after truncation to a size of a scheduled medium access control protocol data unit is larger than the ratio value, skipping generating the truncated MAC CE comprising the measurement report; and transmit the scheduling request for the measurement report.
  • the method 400 may further include: in accordance with a determination that a code rate of physical uplink shared channel is higher than a configured threshold, skipping generating the MAC CE comprising the measurement report on the physical uplink shared channel; and transmit the scheduling request for the measurement report.
  • the MAC CE comprises a serving cell measurement report and a set of candidate cell measurements.
  • the set of candidate cell measurements is sorted in decreasing order, and wherein if the MAC CE is truncated, a subset of lower candidate cell measurements is truncated.
  • the MAC CE comprising the measurement report comprises an indication of event triggered channel state information report index.
  • the MAC CE comprises each triggered channel state information report, where each triggered channel state information report in the MAC CE is a container of a corresponding channel state information report on uplink control information with padding for byte alignment, or wherein all triggered channel state information report in the MAC CE is a container of uplink control information including all corresponding channel state information reports on uplink control information.
  • the method 400 may further include: transmitting, to the network device, a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information.
  • the method 400 may further include: receiving, from the network device, downlink control information indicating a new transmission; and activating a periodic measurement reporting on periodic uplink resources, after a duration from the reception of the downlink control information.
  • the method 400 may further include: receiving, from the network device, a downlink MAC CE indicating the MAC is accepted; transmitting, to the network device, an acknowledgement of the downlink MAC CE; and activating a periodic measurement reporting on periodic uplink resources, after a duration from the transmission of the acknowledgement.
  • the first protocol layer is a physical layer
  • the second protocol layer is a medium access control layer
  • FIG. 5 illustrates a flowchart of a communication method 500 implemented at a network device, in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 500 will be described from the perspective of the network device 120 in FIG. 1.
  • the network device 120 transmits, to the terminal device 110, a first configuration indicating a first set of resources allocated for the scheduling request for the measurement report.
  • the network device 120 receives, from a terminal device 110, a scheduling request for the measurement report.
  • the network device is caused to: transmit, to the terminal device, a second configuration indicating a second set of resources allocated for the measurement report, after the transmission of the scheduling request.
  • the network device is further caused to: receive, from the terminal device, a MAC CE indicating that the terminal device is to stop the event trigger period report.
  • the network device is further caused to: receive, from the terminal device, the measurement report comprised in a MAC CE.
  • a set of fields in the MAC CE is truncated based on logic channel prioritization.
  • a ratio value is configured for the MAC CE comprising the measurement report.
  • the MAC CE comprises a serving cell measurement report and a set of candidate cell measurements.
  • the set of candidate cell measurements is sorted in decreasing order, and wherein if the MAC CE is truncated, a subset of lower candidate cell measurements is truncated.
  • the MAC CE comprising the measurement report comprises an indication of event triggered channel state information report index.
  • the MAC CE comprises each triggered channel state information report, where each triggered channel state information report in the MAC CE is a container of a corresponding channel state information report on uplink control information with padding for byte alignment, or wherein all triggered channel state information report in the MAC CE is a container of uplink control information including all corresponding channel state information reports on uplink control information.
  • the network device is further caused to: receive, from the terminal device, a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information.
  • the network device is further caused to: transmit, to the terminal device, downlink control information indicating a new transmission.
  • the network device is further caused to: transmit, to the terminal device, a downlink MAC CE indicating the MAC is accepted; and receive, from the terminal device, an acknowledgement of the downlink MAC CE.
  • FIG. 6 is a simplified block diagram of a device 600 that is suitable for implementing embodiments of the present disclosure.
  • the device 600 can be considered as a further example implementation of any of the devices as shown in FIG. 1. Accordingly, the device 600 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
  • the device 600 includes a processor 610, a memory 620 coupled to the processor 610, a suitable transceiver 640 coupled to the processor 610, and a communication interface coupled to the transceiver 640.
  • the memory 620 stores at least a part of a program 630.
  • the transceiver 640 may be for bidirectional communications or a unidirectional communication based on requirements.
  • the transceiver 640 may include at least one of a transmitter 642 and a receiver 644.
  • the transmitter 642 and the receiver 644 may be functional modules or physical entities.
  • the transceiver 640 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the program 630 is assumed to include program instructions that, when executed by the associated processor 610, enable the device 600 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGS. 1 to 5.
  • the embodiments herein may be implemented by computer software executable by the processor 610 of the device 600, or by hardware, or by a combination of software and hardware.
  • the processor 610 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 610 and memory 620 may form processing means 650 adapted to implement various embodiments of the present disclosure.
  • the memory 620 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 620 is shown in the device 600, there may be several physically distinct memory modules in the device 600.
  • the processor 610 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • a terminal device comprising a circuitry.
  • the circuitry is configured to: determine, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; in accordance with a determination that the event of measurement result is satisfied, transmit, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; increase, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, trigger, at the second protocol layer, a measurement report; and in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmit, to a network device, a scheduling request for the measurement report.
  • the circuitry may be configured to perform any method implemented by the terminal device, as discussed above.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • a terminal apparatus comprises means for determining, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; means for in accordance with a determination that the event of measurement result is satisfied, transmitting, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; means for increasing, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; means for in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, triggering, at the second protocol layer, a measurement report; and means for in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmitting, to a network device, a scheduling request for the measurement report.
  • the first apparatus may comprise means for performing the respective operations of the method 400. In some example embodiments, the first apparatus may further comprise means for performing other operations in some example embodiments of the method 400.
  • the means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
  • embodiments of the present disclosure provide the following aspects.
  • a terminal device comprising: a processor, configured to cause the terminal device to: determine, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; in accordance with a determination that the event of measurement result is satisfied, transmit, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; increase, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, trigger, at the second protocol layer, a measurement report; and in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmit, to a network device, a scheduling request for the measurement report.
  • the terminal device is further caused to: start, at the second protocol layer, a first timer after the reception of the event satisfied indication from the first protocol layer; and reset, at the second protocol layer, the counter to a second predetermined number after an expiration of the timer.
  • the terminal device is further caused to: in accordance with a determination that the event of measurement result is unsatisfied based on a further measurement result, transmit, at the first protocol layer to the second protocol layer, an event unsatisfied indication indicating the event of measurement result being unsatisfied; and reset, at the second protocol layer, the counter to a second predetermined number based on the event unsatisfied indication.
  • the terminal device is further caused to: start a second timer after triggering the measurement report; or start the second timer after the transmission of the measurement report, wherein the measurement report is not triggered during running time of the second timer.
  • the terminal device is further caused to: perform at least one of the followings during a channel state information report being active: skipping triggering the measurement report, or cancelling the triggered measurement report.
  • the channel state information report comprises at least one of: a channel state information report on physical uplink shared channel, a semi-persistent channel state information report on physical uplink control channel, a channel state information report indicated by radio resource control signaling.
  • the terminal device is caused to: determine whether there are uplink shared channel resources available for the transmission of the measurement report; and in accordance with a determination that there are no uplink shared channel resources available for the transmission of the measurement report, determine that there are not enough resources for the transmission of the measurement report.
  • the terminal device is caused to: determine whether uplink shared channel resources are able to accommodate a medium access control control element (MAC CE) comprising the measurement report and a subheader of the measurement report; and in accordance with a determination that the uplink shared channel resources are unable to accommodate the MAC CE and the subheader, determine that there are not enough resources for the transmission of the measurement report.
  • MAC CE medium access control control element
  • the terminal device is caused to: receive, from the network device, a first configuration indicating a first set of resources allocated for the scheduling request for the measurement report.
  • the terminal device is caused to: receive, from the network device, a second configuration indicating a second set of resources allocated for the measurement report, after the transmission of the scheduling request.
  • the terminal device is further caused to: in accordance with a determination that the measurement report is an event trigger one time report, cancel, at the second protocol layer, the measurement report after the transmission of the measurement report.
  • the terminal device is further caused to: in accordance with a determination that the measurement report is an event trigger period report, cancel, at the second protocol layer, the measurement report after a period uplink grant for measurement reporting is received.
  • the terminal device is further caused to: transmit, to the network device, a MAC CE indicating that the terminal device is to stop the event trigger period report.
  • the terminal device is further caused to: transmit, to the network device, the measurement report comprised in a MAC CE.
  • a set of fields in the MAC CE is truncated based on logic channel prioritization.
  • a ratio value is configured for the MAC CE comprising the measurement report.
  • the terminal device is caused to: in accordance with a determination that a ratio of a size of the MAC CE comprising the measurement report to a size of a scheduled medium access control protocol data unit is larger than the ratio value, skip generating the MAC CE comprising the measurement report; and transmit the scheduling request for the measurement report.
  • the terminal device is caused to: in accordance with a determination that a ratio of a size of the MAC CE comprising the measurement report after truncation to a size of a scheduled medium access control protocol data unit is larger than the ratio value, skip generating the truncated MAC CE comprising the measurement report; and transmit the scheduling request for the measurement report.
  • the terminal device is caused to: in accordance with a determination that a code rate of physical uplink shared channel is higher than a configured threshold, skip generating the MAC CE comprising the measurement report on the physical uplink shared channel; and transmit the scheduling request for the measurement report.
  • the MAC CE comprises a serving cell measurement report and a set of candidate cell measurements.
  • the set of candidate cell measurements is sorted in decreasing order, and wherein if the MAC CE is truncated, a subset of lower candidate cell measurements is truncated.
  • the MAC CE comprising the measurement report comprises an indication of event triggered channel state information report index.
  • the MAC CE comprises each triggered channel state information report, where each triggered channel state information report in the MAC CE is a container of a corresponding channel state information report on uplink control information with padding for byte alignment, or wherein all triggered channel state information report in the MAC CE is a container of uplink control information including all corresponding channel state information reports on uplink control information.
  • the terminal device is further caused to: transmit, to the network device, a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information.
  • the terminal device is further caused to: receive, from the network device, downlink control information indicating a new transmission; and activate a periodic measurement reporting on periodic uplink resources, after a duration from the reception of the downlink control information.
  • the terminal device is further caused to: receive, from the network device, a downlink MAC CE indicating the MAC is accepted; transmit, to the network device, an acknowledgement of the downlink MAC CE; and activate a periodic measurement reporting on periodic uplink resources, after a duration from the transmission of the acknowledgement.
  • the first protocol layer is a physical layer
  • the second protocol layer is a medium access control layer
  • a terminal device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the terminal device to perform the method implemented by the terminal device, discussed above.
  • the network device is caused to: if the measurement report is triggered and there are not enough resources for a transmission of the measurement report, receive, from a terminal device, a scheduling request for the measurement report.
  • the network device is further caused to: transmit, to the terminal device 110, a first configuration indicating a first set of resources allocated for the scheduling request for the measurement report.
  • the network device is caused to: transmit, to the terminal device, a second configuration indicating a second set of resources allocated for the measurement report, after the transmission of the scheduling request.
  • the network device is further caused to: receive, from the terminal device, a MAC CE indicating that the terminal device is to stop the event trigger period report.
  • the network device is further caused to: receive, from the terminal device, the measurement report comprised in a MAC CE.
  • a set of fields in the MAC CE is truncated based on logic channel prioritization.
  • a ratio value is configured for the MAC CE comprising the measurement report.
  • the MAC CE comprises a serving cell measurement report and a set of candidate cell measurements.
  • the set of candidate cell measurements is sorted in decreasing order, and wherein if the MAC CE is truncated, a subset of lower candidate cell measurements is truncated.
  • the MAC CE comprising the measurement report comprises an indication of event triggered channel state information report index.
  • the MAC CE comprises each triggered channel state information report, where each triggered channel state information report in the MAC CE is a container of a corresponding channel state information report on uplink control information with padding for byte alignment, or wherein all triggered channel state information report in the MAC CE is a container of uplink control information including all corresponding channel state information reports on uplink control information.
  • the network device is further caused to: receive, from the terminal device, a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information.
  • the network device is further caused to: transmit, to the terminal device, downlink control information indicating a new transmission.
  • the network device is further caused to: transmit, to the terminal device, a downlink MAC CE indicating the MAC is accepted; and receive, from the terminal device, an acknowledgement of the downlink MAC CE.
  • a network device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the network device to perform the method implemented by the network device, discussed above.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device, discussed above.
  • a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device, discussed above.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device, discussed above.
  • a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device, discussed above.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGS. 1 to 6.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include 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) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Embodiments of the present disclosure provide a solution for measurement report. In a solution, the terminal device determines whether an event of measurement result is satisfied based on a measurement result; if the event of measurement result is satisfied, transmits, from a first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; increases a counter by a first predetermined number based on the event satisfied indication; if a value of the counter is equal to or larger than a configured threshold, triggers a measurement report; and if the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmit, to a network device, a scheduling request for the measurement report.

Description

DEVICES AND METHODS FOR COMMUNICATION
FIELDS
Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices and methods for measurement report.
BACKGROUND
Currently, there are two types of measurement report, i.e. L1 measurement report and L3 measurement report. For layer 1 (L1) measurement report, it can be configured by radio resource control (RRC) with: periodic report, semi-Persistent (SP) report on physical uplink control channel (PUCCH) , SP report on physical uplink shared channel (PUSCH) , and/or aperiodic report. For L3 measurement report, it is contained in RRC message and transmits on service radio bearer 1 (SRB1) . The trigger of measurement report is given by one or more conditions and time to trigger (TTT) timer where the condition is satisfied during a time duration of TTT. The trigger of transmission is triggered by a request. Therefore, it is worth studying enhancements of the L1 measurement report.
SUMMARY
In general, embodiments of the present disclosure provide a solution on measurement report.
In a first aspect, there is provided a terminal device, comprising: a processor, configured to cause the terminal device to: determine, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; in accordance with a determination that the event of measurement result is satisfied, transmit, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; increase, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, trigger, at the second protocol layer, a measurement report; and in accordance with a determination that the measurement report is triggered and there are  not enough resources for a transmission of the measurement report, transmit, to a network device, a scheduling request for the measurement report.
In a second aspect, there is provided a communication method performed by a terminal device. The method comprises: determining, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; in accordance with a determination that the event of measurement result is satisfied, transmitting, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; increasing, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, triggering, at the second protocol layer, a measurement report; and in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmitting, to a network device, a scheduling request for the measurement report.
In a third aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the second aspect.
Other features of the present disclosure will become easily comprehensible through the following description.
BRIEF DESCRIPTION OF THE DRAWINGS
Through the more detailed description of some example embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:
FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
FIG. 2 illustrates a signaling flow of measurement report in accordance with some embodiments of the present disclosure;
FIG. 3A and FIG. 3B illustrates schematic diagrams of truncated medium access control control element (MAC CE) structures in accordance with some embodiments of the present disclosure;
FIG. 4 illustrates a flowchart of a method implemented at a terminal device, according to some example embodiments of the present disclosure;
FIG. 5 illustrates a flowchart of a method implemented at a network device, according to some example embodiments of the present disclosure; and
FIG. 6 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.
Throughout the drawings, the same or similar reference numerals represent the same or similar element.
DETAILED DESCRIPTION
Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, devices on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft  without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
The term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.
The terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
The terminal or the network device may work on several frequency ranges, e.g., FR1 (e.g., 450 MHz to 6000 MHz) , FR2 (e.g., 24.25GHz to 52.6GHz) , frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum. The terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
The embodiments of the present disclosure may be performed in test equipment, e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator. In some embodiments, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node.  The first network device and the second network device may use different radio access technologies (RATs) . In some embodiments, the first network device may be a first RAT device and the second network device may be a second RAT device. In some embodiments, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device. In some embodiments, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In some embodiments, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
As used herein, the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
As used herein, the term “resource, ” “transmission resource, ” “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
The term “event of measurement result” used herein may refer to a condition of the measurement result. As used herein, the term “medium access control (MAC) layer” may refer to a sublayer of data link layer of open system interconnections (OSI) reference model for data transmission. The MAC layer provides two main services to the upper layers; data transfer and radio resource allocation. The term “physical layer” may refer to a bottom-most layer in the OSI. The term “MAC control element (MAC CE) ” used herein may refer to a MAC structure carrying control information.
As mentioned above, L1 measurement report is introduced. For L1 measurement report, it needs further study the following mechanisms: reporting as uplink control information (UCI) on PUCCH or PUSCH; and reporting on MAC CE. Further, it also needs to study event triggered report for L1 measurement.
According to embodiments of the present disclosure, a solution on measurement report is proposed. In particular, a terminal device determines whether whether an event of measurement result is satisfied based on a measurement result. If the event of measurement result is satisfied, the terminal device increases a counter based on the event satisfied indication. If a value of the counter is equal to or larger than a configured threshold, the terminal device triggers a measurement report. If the measurement report is triggered, the terminal device transmits a scheduling request for the measurement report to a network device. In this way, L1 measurement report can be triggered based on the event of measurement result. The L1 measurement report can be reported in a more suitable manner.
Principles and implementations of the present disclosure will be described in detail below with reference to the figures.
FIG. 1 illustrates a schematic diagram of an example communication environment 100 in which example embodiments of the present disclosure can be implemented. In the communication environment 100, a plurality of communication devices, including a terminal device 110 and a network device 120, can communicate with each other.
In the example of FIG. 1, the terminal device 110 may be a UE and the network device 120 may be a base station serving the UE. The serving area of the network device 120 may be called a cell 102.
It is to be understood that the number of devices and their connections shown in FIG. 1 are only for the purpose of illustration without suggesting any limitation. The communication  environment 100 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell 102, and one or more additional cells may be deployed in the communication environment 100. It is noted that although illustrated as a network device, the network device 120 may be another device than a network device. Although illustrated as a terminal device, the terminal device 110 may be other device than a terminal device.
In the following, for the purpose of illustration, some example embodiments are described with the terminal device 110 operating as a UE and the network device 120 operating as a base station. However, in some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other device.
In some example embodiments, if the terminal device 110 is a terminal device and the network device 120 is a network device, a link from the network device 120 to the terminal device 110 is referred to as a downlink (DL) , while a link from the terminal device 110 to the network device 120 is referred to as an uplink (UL) . In DL, the network device 120 is a transmitting (TX) device (or a transmitter) and the terminal device 110 is a receiving (RX) device (or a receiver) . In UL, the terminal device 110 is a TX device (or a transmitter) and the network device 120 is a RX device (or a receiver) .
The communications in the communication environment 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like. The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
Reference is made to FIG. 2, which illustrates a signaling flow 200 of measurement report in accordance with some embodiments of the present disclosure. For the purposes of  discussion, the signaling flow 200 will be discussed with reference to FIG. 1, for example, by using the terminal device 110 and the network device 120.
The network device 120 may transmit (2005) a first configuration indicating a first set of resources allocated for a scheduling request for a measurement report to the terminal device 110. In other words, the terminal device 110 may receive (2005) the first configuration indicating the first set of resources from the network device 120. The first set of resources may be dedicated to the scheduling request. In some embodiments, separate scheduling request resources may be be configured for event trigger aperiodic measurement report scheduling request and event trigger SP measurement report scheduling request.
The terminal device 110 may perform (2010) a measurement on reference signals. For example, a first layer 1101 (such as, the PHY layer) may perform the measurement. In some embodiments, the terminal device 110 may perform the measurement based on a predefined periodicity. Alternatively, the terminal device 110 may perform the measurement based on a configured periodicity. By way of example, the terminal device 110 may perform a reference signal received power (RSRP) measurement on reference signals from the network device 120. Alternatively, or in addition, the terminal device 110 may perform a reference signal received quality (RSRQ) measurement on the reference signals. In some other example embodiments, the terminal device 110 may perform a signal to interference plus noise ratio (SINR) measurement on the reference signals.
The terminal device 110 determines (2015) whether an event of measurement result is satisfied based on a measurement result. For example, the measurement result may include one or more of: measured RSRP, measured RSRQ, or measured SINR. In some embodiments, the event of measurement result may include that a neighbor cell becomes amount of offset better than primary cell (Pcell) or primary secondary cell (PSCell) . Alternatively, the event of measurement result may include that Pcell/PSCell becomes worse than absolute threshold1 and neighbor cell/Scell becomes better than another absolute threshold2. It is noted that the event of measurement result may also include other events/conditions.
The first layer 1101 transmits (2020) an event satisfied indication indicating the event of measurement result being satisfied and the measurement result to a second layer 1102, if the event of measurement result is satisfied. In other words, the second layer 1102 receives the event satisfied indication and the measurement result from the first layer 1101, if the event of measurement result is satisfied. For example, the measurement result may include one or more of: measured RSRP, measured RSRQ, or measured SINR.
The terminal device 110, for example, the second layer 1102 increases (2025) a counter by a first predetermined number based on the event satisfied indication. For example, the second layer 1102 may increase the counter by one based on the event satisfied indication.
In some embodiments, the second layer 1102 may start or restart (2030) a first timer after the reception of the event satisfied indication from the first protocol layer 1101. In this case, if the first timer expires, the second layer 1102 may reset the counter to a second predetermined (for example, zero) .
In some other embodiments, the first layer 1101 may transmit (2035) an event unsatisfied indication indicating the event of measurement result being unsatisfied to the second layer 1102. In other words, the second layer 1102 may receive the event unsatisfied indication from the first layer 1101. For example, the terminal device 110 may obtain a further measurement result by performing the measurement on reference signals. If the first layer 1101 determines that the event of measurement result is unsatisfied based on the further measurement result, the first layer 1101 may transmit (2035) the event unsatisfied indication to the second layer 1102. In this case, the second layer 1102 may reset the counter to a second predetermined number (for example, zero) based on the event unsatisfied indication.
The terminal device 110, for example, the second layer 1102, triggers (2040) a measurement report, if a value of the counter is equal to or larger than a configured threshold. In some embodiments, the configured threshold may be preconfigured at the terminal device 110. Alternatively, the network device 120 may configured the configured threshold to the terminal device 110.
In some embodiments, the terminal device 110 may start a second timer after triggering the measurement report. Alternatively, the terminal device 110 may start the second timer after a transmission of the measurement report. In these cases, if the second timer is running, the terminal device 110 may not trigger the measurement report. In some embodiments, the terminal device 110 may sometimes need periodic measurement reporting when events are contiguously satisfied. For one-shot measurement reporting, the second timer can make the one-shot measurement reporting as if periodic measurement reporting and the period is the timer duration of the second timer.
In some embodiments, the terminal device 110 may skip triggering the measurement report, during a channel state information (CSI) report being active. Alternatively, the terminal device 110 may cancel the triggered measurement report during the CSI report being active.  For example, the terminal device 110 may trigger the event triggered measurement report when periodic or SP L1 CSI reporting are not active. If the CSI reporting is active, the terminal device 110 may not trigger the event measurement report and cancel the triggered measurement report.
In some embodiments, the CSI report may be a CSI report on PUSCH. Alternatively, or in addition, the CSI report may be a semi-persistent (SP) CSI report on PUCCH. In some other embodiments, the CSI report may be a CSI report indicated by RRC, i.e. no simultaneous activation with event triggered CSI reporting indicator is indicated for those CSI report.
The terminal device 110 transmits (2045) a scheduling request for the measurement report to the network device 120, if there are not enough resources for a transmission of the measurement report. In other words, the network device 120 receives the scheduling request for the measurement report from the terminal device 110. For example, if the measurement report are trigger by MAC and there is no UL-SCH resources are available for a new transmission, or if the UL-SCH resources cannot accommodate the measurement report MAC CE plus its subheader, the terminal device 110 may transmit the scheduling request for the measurement report.
In some embodiments, the terminal device 110 may determine whether there are uplink shared channel resources available for the transmission of the measurement report. If there are no uplink shared channel resources available for the transmission of the measurement report, the terminal device 110 may determine that there are not enough resources for the transmission of the measurement report. In some other embodiments, the terminal device 110 may determine whether uplink shared channel resources are able to accommodate a MAC CE including the measurement report and a subheader of the measurement report. If the uplink shared channel resources are unable to accommodate the MAC CE and the subheader, the terminal device 110 may determine that there are not enough resources for the transmission of the measurement report.
The network device 120 may transmit (2050) a second configuration indicating a second set of resources allocated for the measurement report to the terminal device 110, after the transmission of the scheduling request. In other words, the terminal device 110 may receive the second configuration indicating the second set of resources from the network device 120. For example, the network device 120 may indicate PUSCH resources for aperiodic CSI report, after receiving the scheduling request. Alternatively, or in addition, the network device 120 may indicate PUSCH resources or PUCCH resources for SP CSI report after receiving the scheduling request.
In some embodiments, if the measurement report is event trigger one-shot report, the second layer 1102 of the terminal device 110 may cancel the triggered measurement report if the measurement reported is transmitted on UL-SCH resources. Alternatively, if the measurement report is event trigger period report, the second layer 1102 of the terminal device 110 may cancel the triggered measurement report if a periodic uplink grant for the measurement report (for example, SP-CSI-radio network temporary identifier (RNTI) scrambled uplink grant DCI for periodic measurement reports or MAC CE activation of SP CSI reporting) is received. In some embodiments, if the measurement report is event period report, the terminal device 110 may transmit a new MAC CE or a field in MAC CE indicating the terminal device 110 would like to stop the periodic uplink measurement report, to the network device 120. The terminal device 110 may stop the periodic uplink report when the event is not satisfied any more for a period.
The terminal device 110 may transmit (2055) the measurement report to the network device 120. In other words, the network device 120 may receive (2055) the measurement report from the terminal device 110. For example, the measurement report may be included in a MAC CE. In some embodiments, the MAC CE may be a long MAC CE. Alternatively, the MAC CE may be a short MAC CE.
The MAC CE including the measurement report may be truncated. For example, a set of fields in the MAC CE may be truncated based on logic channel prioritization. For example, as shown in FIG. 3A, the long truncated MAC CE may include fields 310-1, 310-2, 310-3, 310-4, 310-5, 310-6, 310-7 and 310-8 and payload 320-1, 320-2, …, 320-N, where N is an integer number. As another example, the short truncated MAC CE may include field 311 and payload 321.
In some embodiments, a ratio value may be configured for the MAC CE including the measurement report. For example, the ratio value may be indicated by the network device 120.
In some embodiments, if a ratio of a size of the MAC CE including the measurement report to a size of a scheduled medium access control protocol data unit is larger than the ratio value, the terminal device 110 may skip generating the MAC CE comprising the measurement report. The terminal device 110 may then transmit the scheduling request for the measurement report. For example, if the ratio of the size of measurement report MAC CE (plus its header) to the size of scheduled MAC PDU is larger than the configured value, the terminal device 110 may not instruct the multiplexing and assembly procedure to generate the MAC CE including  the measurement report and trigger scheduling request for the measurement report.
In some other embodiments, if a ratio of a size of the MAC CE comprising the measurement report after truncation to a size of a scheduled medium access control protocol data unit is larger than the ratio value, the terminal device 110 may skip generating the truncated MAC CE comprising the measurement report. The terminal device 110 may then transmit the scheduling request for the measurement report. For example, if the ratio of the size of measurement report MAC CE after truncation (plus its header) to the size of scheduled MAC PDU is larger than the configured value, the terminal device 110 may not instruct the multiplexing and assembly procedure to generate the truncated measurement report MAC CE and trigger scheduling request for the measurement report.
Alternatively, if a code rate of physical uplink shared channel is higher than a configured threshold, the terminal device 110 may skip generating the MAC CE including the measurement report on the PUSCH. The terminal device 110 may then transmit the scheduling request for the measurement report. For example, if the code rate/modulation coding scheme (MCS) of the PUSCH is higher than a configured value/threshold, the PUSCH is not a valid PUSCH for measurement report, i.e., the terminal device 110 may not generate measurement report MAC CE on this PUSCH. In some other embodiments, if the code rate of physical uplink shared channel is lower than the configured threshold, the terminal device 110 may skip generating the MAC CE including the measurement report on the PUSCH. The terminal device 110 may then transmit the scheduling request for the measurement report. For example, if the code rate/modulation coding scheme (MCS) of the PUSCH is lower than a configured value/threshold, the PUSCH is not a valid PUSCH for measurement report, i.e., the terminal device 110 may not generate measurement report MAC CE on this PUSCH.
In some embodiments, the MAC CE may include a serving cell measurement report and a set of candidate cell measurements. For example, the MAC CE may include cell level RSRP/RSRQ/SINR reporting of serving cell and candidate cells. In some embodiments, the set of candidate cell measurements may be sorted in decreasing order. In this case, if the MAC CE is truncated, a subset of lower candidate cell measurements may be truncated.
In some embodiments, the MAC CE including the measurement report may include an indication of event triggered channel state information report index. For example, the MAC CE may include an indication of event triggered CSI report index, for  example, by bitmap indication of all configured CSI report for LTM, value 1 present the CSI report is event triggered and value 0 presents the CSI report is not event triggered.
Alternatively, or in addition, the MAC CE may include each triggered channel state information report. In some embodiments, each triggered channel state information report in the MAC CE may be a container of a corresponding channel state information report on uplink control information with padding for byte alignment (i.e. physical layer indicates each reports with the corresponding bit string to MAC) . Alternatively, all triggered channel state information report in the MAC CE may be a container of uplink control information including all corresponding channel state information reports on uplink control information (i.e. physical layer combines each report and indicate one bit string to MAC) .
In some embodiments, HARQ may not be needed for L1 measurement reports since latency is more important than reliability for L1 measurement. Thus, transmission of event trigger measurement report in UCI other than MAC CE has benefit for lower latency where HARQ retransmission is not applied for UCI. Meanwhile, UCI may have a scaling factor on the number of allocated resources which has lower code rate than data. For dynamic uplink grant DCI, one or more bit fields may be introduced in DCI format, to indicate that event triggered measurement reports or set of indicated event triggered measurement reports is included in the PUSCH granted by this DCI. By using the indication in DCI, network can dynamically schedule measurement report transmission more flexible.
In some embodiments, the network device 120 may configure PUCCH resources for event triggered periodic reporting, including PUCCH resources and periodicity of PUCCH resources. The terminal device 110 may transmit a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information to the network device 120. For example, the terminal device 110 may request the event triggered periodic reporting by sending MAC CE including the information of satisfied event information and satisfied RS information.
The terminal device 110 may receive, from the network device 120, downlink control information indicating a new transmission. The terminal device 110 may then activate a periodic measurement reporting on periodic uplink resources, after a duration from the reception of the downlink control information. For example, after some  symbols/time/slot of receiving an uplink grant DCI to indicate new transmission, i.e. NDI field is toggled, for the same HARQ process that includes measurement reporting MAC CE, the terminal device 110 may activate periodic measurement reporting on periodic PUCCH resources.
Alternatively, the terminal device 110 may receive, from the network device 120, a downlink MAC CE indicating the MAC is accepted. The terminal device 110 may transmit, to the network device 120, an acknowledgement of the downlink MAC CE and activate a periodic measurement reporting on periodic uplink resources, after a duration from the transmission of the acknowledgement. For example, DL MAC CE from the network device 12 may be indicated to the terminal device 110, including accepted measurement event and reference signal information. The terminal device 110 may activate periodic measurement reporting on periodic PUCCH resources after some symbols/time/slot of transmitting of HARQ-ACK information of PDSCH that includes the DL MAC CE.
FIG. 4 illustrates a flowchart of a communication method 400 implemented at a terminal device, in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 400 will be described from the perspective of the terminal device 110 in FIG. 1.
At block 410, a first protocol layer of the terminal device 110 determines whether an event of measurement result is satisfied based on a measurement result.
At block 420, if the event of measurement result is satisfied, the first protocol layer of the terminal device 110 transmits an event satisfied indication indicating the event of measurement result being satisfied and the measurement result to a second protocol layer of the terminal device.
At block 430, the second protocol layer increases a counter by a first predetermined number based on the event satisfied indication.
At block 440, if a value of the counter is equal to or larger than a configured threshold, the second protocol layer triggers a measurement report.
At block 450, if the measurement report is triggered and there are not enough resources for a transmission of the measurement report, the terminal device transmits, to a network device, a scheduling request for the measurement report.
In some example embodiments, the method 400 may further include starting, at the second protocol layer, a first timer after the reception of the event satisfied indication from the first protocol layer; and resetting, at the second protocol layer, the counter to a second predetermined number after an expiration of the timer.
In some example embodiments, the method 400 may further include: in accordance with a determination that the event of measurement result is unsatisfied based on a further measurement result, transmitting, at the first protocol layer to the second protocol layer, an event unsatisfied indication indicating the event of measurement result being unsatisfied; and resetting, at the second protocol layer, the counter to a second predetermined number based on the event unsatisfied indication.
In some example embodiments, the method 400 may further include: starting a second timer after triggering the measurement report; or starting the second timer after the transmission of the measurement report, wherein the measurement report is not triggered during running time of the second timer.
In some example embodiments, the method 400 may further include: performing at least one of the followings during a channel state information report being active: skipping triggering the measurement report, or cancelling the triggered measurement report.
In some example embodiments, the channel state information report comprises at least one of: a channel state information report on physical uplink shared channel, a semi-persistent channel state information report on physical uplink control channel, a channel state information report indicated by radio resource control signaling.
In some example embodiments, the method 400 may further include: determining whether there are uplink shared channel resources available for the transmission of the measurement report; and in accordance with a determination that there are no uplink shared channel resources available for the transmission of the measurement report, determining that there are not enough resources for the transmission of the measurement report.
In some example embodiments, the method 400 may further include: determining whether uplink shared channel resources are able to accommodate a medium access control control element (MAC CE) comprising the measurement report and a  subheader of the measurement report; and in accordance with a determination that the uplink shared channel resources are unable to accommodate the MAC CE and the subheader, determining that there are not enough resources for the transmission of the measurement report.
In some example embodiments, the method 400 may further include: receiving, from the network device, a first configuration indicating a first set of resources allocated for the scheduling request for the measurement report.
In some example embodiments, the method 400 may further include: receiving, from the network device, a second configuration indicating a second set of resources allocated for the measurement report, after the transmission of the scheduling request.
In some example embodiments, the method 400 may further include: in accordance with a determination that the measurement report is an event trigger one time report, cancelling, at the second protocol layer, the measurement report after the transmission of the measurement report.
In some example embodiments, the method 400 may further include: in accordance with a determination that the measurement report is an event trigger period report, cancelling, at the second protocol layer, the measurement report after a period uplink grant for measurement reporting is received.
In some example embodiments, the method 400 may further include: transmitting, to the network device, a MAC CE indicating that the terminal device is to stop the event trigger period report.
In some example embodiments, the method 400 may further include: transmitting, to the network device, the measurement report comprised in a MAC CE.
In some example embodiments, a set of fields in the MAC CE is truncated based on logic channel prioritization.
In some example embodiments, a ratio value is configured for the MAC CE comprising the measurement report.
In some example embodiments, the method 400 may further include: in accordance with a determination that a ratio of a size of the MAC CE comprising the measurement report to a size of a scheduled medium access control protocol data unit is  larger than the ratio value, skipping generating the MAC CE comprising the measurement report; and transmit the scheduling request for the measurement report.
In some example embodiments, the method 400 may further include: in accordance with a determination that a ratio of a size of the MAC CE comprising the measurement report after truncation to a size of a scheduled medium access control protocol data unit is larger than the ratio value, skipping generating the truncated MAC CE comprising the measurement report; and transmit the scheduling request for the measurement report.
In some example embodiments, the method 400 may further include: in accordance with a determination that a code rate of physical uplink shared channel is higher than a configured threshold, skipping generating the MAC CE comprising the measurement report on the physical uplink shared channel; and transmit the scheduling request for the measurement report.
In some example embodiments, the MAC CE comprises a serving cell measurement report and a set of candidate cell measurements.
In some example embodiments, the set of candidate cell measurements is sorted in decreasing order, and wherein if the MAC CE is truncated, a subset of lower candidate cell measurements is truncated.
In some example embodiments, the MAC CE comprising the measurement report comprises an indication of event triggered channel state information report index.
In some example embodiments, the MAC CE comprises each triggered channel state information report, where each triggered channel state information report in the MAC CE is a container of a corresponding channel state information report on uplink control information with padding for byte alignment, or wherein all triggered channel state information report in the MAC CE is a container of uplink control information including all corresponding channel state information reports on uplink control information.
In some example embodiments, the method 400 may further include: transmitting, to the network device, a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information.
In some example embodiments, the method 400 may further include: receiving, from the network device, downlink control information indicating a new transmission;  and activating a periodic measurement reporting on periodic uplink resources, after a duration from the reception of the downlink control information.
In some example embodiments, the method 400 may further include: receiving, from the network device, a downlink MAC CE indicating the MAC is accepted; transmitting, to the network device, an acknowledgement of the downlink MAC CE; and activating a periodic measurement reporting on periodic uplink resources, after a duration from the transmission of the acknowledgement.
In some example embodiments, the first protocol layer is a physical layer, and the second protocol layer is a medium access control layer.
FIG. 5 illustrates a flowchart of a communication method 500 implemented at a network device, in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 500 will be described from the perspective of the network device 120 in FIG. 1.
In some embodiments, at block 510, the network device 120 transmits, to the terminal device 110, a first configuration indicating a first set of resources allocated for the scheduling request for the measurement report.
At block 520, if the measurement report is triggered and there are not enough resources for a transmission of the measurement report, the network device 120 receives, from a terminal device 110, a scheduling request for the measurement report.
In some example embodiments, the network device is caused to: transmit, to the terminal device, a second configuration indicating a second set of resources allocated for the measurement report, after the transmission of the scheduling request.
In some example embodiments, the network device is further caused to: receive, from the terminal device, a MAC CE indicating that the terminal device is to stop the event trigger period report.
In some example embodiments, the network device is further caused to: receive, from the terminal device, the measurement report comprised in a MAC CE.
In some example embodiments, a set of fields in the MAC CE is truncated based on logic channel prioritization.
In some example embodiments, a ratio value is configured for the MAC CE  comprising the measurement report.
In some example embodiments, the MAC CE comprises a serving cell measurement report and a set of candidate cell measurements.
In some example embodiments, the set of candidate cell measurements is sorted in decreasing order, and wherein if the MAC CE is truncated, a subset of lower candidate cell measurements is truncated.
In some example embodiments, the MAC CE comprising the measurement report comprises an indication of event triggered channel state information report index.
In some example embodiments, the MAC CE comprises each triggered channel state information report, where each triggered channel state information report in the MAC CE is a container of a corresponding channel state information report on uplink control information with padding for byte alignment, or wherein all triggered channel state information report in the MAC CE is a container of uplink control information including all corresponding channel state information reports on uplink control information.
In some example embodiments, the network device is further caused to: receive, from the terminal device, a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information.
In some example embodiments, the network device is further caused to: transmit, to the terminal device, downlink control information indicating a new transmission.
In some example embodiments, the network device is further caused to: transmit, to the terminal device, a downlink MAC CE indicating the MAC is accepted; and receive, from the terminal device, an acknowledgement of the downlink MAC CE.
FIG. 6 is a simplified block diagram of a device 600 that is suitable for implementing embodiments of the present disclosure. The device 600 can be considered as a further example implementation of any of the devices as shown in FIG. 1. Accordingly, the device 600 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
As shown, the device 600 includes a processor 610, a memory 620 coupled to the processor 610, a suitable transceiver 640 coupled to the processor 610, and a communication interface coupled to the transceiver 640. The memory 620 stores at least  a part of a program 630. The transceiver 640 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 640 may include at least one of a transmitter 642 and a receiver 644. The transmitter 642 and the receiver 644 may be functional modules or physical entities. The transceiver 640 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
The program 630 is assumed to include program instructions that, when executed by the associated processor 610, enable the device 600 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGS. 1 to 5. The embodiments herein may be implemented by computer software executable by the processor 610 of the device 600, or by hardware, or by a combination of software and hardware. The processor 610 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 610 and memory 620 may form processing means 650 adapted to implement various embodiments of the present disclosure.
The memory 620 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 620 is shown in the device 600, there may be several physically distinct memory modules in the device 600. The processor 610 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
According to embodiments of the present disclosure, a terminal device, comprising a circuitry is provided. The circuitry is configured to: determine, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; in accordance with a determination that the event of measurement result is satisfied, transmit, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; increase, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, trigger, at the second protocol layer, a measurement report; and in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmit, to a network device, a scheduling request for the measurement report. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the terminal device, as discussed above.
The term “circuitry” used herein may refer to hardware circuits and/or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
According to embodiments of the present disclosure, a terminal apparatus, is provided. The terminal apparatus, comprises means for determining, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; means for in accordance with a determination that the event of measurement result is satisfied, transmitting, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of  measurement result being satisfied and the measurement result; means for increasing, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; means for in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, triggering, at the second protocol layer, a measurement report; and means for in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmitting, to a network device, a scheduling request for the measurement report. In some embodiments, the first apparatus may comprise means for performing the respective operations of the method 400. In some example embodiments, the first apparatus may further comprise means for performing other operations in some example embodiments of the method 400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
In summary, embodiments of the present disclosure provide the following aspects.
In an aspect, it is proposed a terminal device, comprising: a processor, configured to cause the terminal device to: determine, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result; in accordance with a determination that the event of measurement result is satisfied, transmit, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result; increase, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication; in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, trigger, at the second protocol layer, a measurement report; and in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmit, to a network device, a scheduling request for the measurement report.
In some embodiments, the terminal device is further caused to: start, at the second protocol layer, a first timer after the reception of the event satisfied indication from the first protocol layer; and reset, at the second protocol layer, the counter to a second predetermined number after an expiration of the timer.
In some embodiments, the terminal device is further caused to: in accordance  with a determination that the event of measurement result is unsatisfied based on a further measurement result, transmit, at the first protocol layer to the second protocol layer, an event unsatisfied indication indicating the event of measurement result being unsatisfied; and reset, at the second protocol layer, the counter to a second predetermined number based on the event unsatisfied indication.
In some embodiments, the terminal device is further caused to: start a second timer after triggering the measurement report; or start the second timer after the transmission of the measurement report, wherein the measurement report is not triggered during running time of the second timer.
In some embodiments, the terminal device is further caused to: perform at least one of the followings during a channel state information report being active: skipping triggering the measurement report, or cancelling the triggered measurement report.
In some embodiments, the channel state information report comprises at least one of: a channel state information report on physical uplink shared channel, a semi-persistent channel state information report on physical uplink control channel, a channel state information report indicated by radio resource control signaling.
In some embodiments, the terminal device is caused to: determine whether there are uplink shared channel resources available for the transmission of the measurement report; and in accordance with a determination that there are no uplink shared channel resources available for the transmission of the measurement report, determine that there are not enough resources for the transmission of the measurement report.
In some embodiments, the terminal device is caused to: determine whether uplink shared channel resources are able to accommodate a medium access control control element (MAC CE) comprising the measurement report and a subheader of the measurement report; and in accordance with a determination that the uplink shared channel resources are unable to accommodate the MAC CE and the subheader, determine that there are not enough resources for the transmission of the measurement report.
In some embodiments, the terminal device is caused to: receive, from the network device, a first configuration indicating a first set of resources allocated for the scheduling request for the measurement report.
In some embodiments, the terminal device is caused to: receive, from the  network device, a second configuration indicating a second set of resources allocated for the measurement report, after the transmission of the scheduling request.
In some embodiments, the terminal device is further caused to: in accordance with a determination that the measurement report is an event trigger one time report, cancel, at the second protocol layer, the measurement report after the transmission of the measurement report.
In some embodiments, the terminal device is further caused to: in accordance with a determination that the measurement report is an event trigger period report, cancel, at the second protocol layer, the measurement report after a period uplink grant for measurement reporting is received.
In some embodiments, the terminal device is further caused to: transmit, to the network device, a MAC CE indicating that the terminal device is to stop the event trigger period report.
In some embodiments, the terminal device is further caused to: transmit, to the network device, the measurement report comprised in a MAC CE.
In some embodiments, a set of fields in the MAC CE is truncated based on logic channel prioritization.
In some embodiments, a ratio value is configured for the MAC CE comprising the measurement report.
In some embodiments, the terminal device is caused to: in accordance with a determination that a ratio of a size of the MAC CE comprising the measurement report to a size of a scheduled medium access control protocol data unit is larger than the ratio value, skip generating the MAC CE comprising the measurement report; and transmit the scheduling request for the measurement report.
In some embodiments, the terminal device is caused to: in accordance with a determination that a ratio of a size of the MAC CE comprising the measurement report after truncation to a size of a scheduled medium access control protocol data unit is larger than the ratio value, skip generating the truncated MAC CE comprising the measurement report; and transmit the scheduling request for the measurement report.
In some embodiments, the terminal device is caused to: in accordance with a  determination that a code rate of physical uplink shared channel is higher than a configured threshold, skip generating the MAC CE comprising the measurement report on the physical uplink shared channel; and transmit the scheduling request for the measurement report.
In some embodiments, the MAC CE comprises a serving cell measurement report and a set of candidate cell measurements.
In some embodiments, the set of candidate cell measurements is sorted in decreasing order, and wherein if the MAC CE is truncated, a subset of lower candidate cell measurements is truncated.
In some embodiments, the MAC CE comprising the measurement report comprises an indication of event triggered channel state information report index.
In some embodiments, the MAC CE comprises each triggered channel state information report, where each triggered channel state information report in the MAC CE is a container of a corresponding channel state information report on uplink control information with padding for byte alignment, or wherein all triggered channel state information report in the MAC CE is a container of uplink control information including all corresponding channel state information reports on uplink control information.
In some embodiments, the terminal device is further caused to: transmit, to the network device, a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information.
In some embodiments, the terminal device is further caused to: receive, from the network device, downlink control information indicating a new transmission; and activate a periodic measurement reporting on periodic uplink resources, after a duration from the reception of the downlink control information.
In some embodiments, the terminal device is further caused to: receive, from the network device, a downlink MAC CE indicating the MAC is accepted; transmit, to the network device, an acknowledgement of the downlink MAC CE; and activate a periodic measurement reporting on periodic uplink resources, after a duration from the transmission of the acknowledgement.
In some embodiments, the first protocol layer is a physical layer, and the second protocol layer is a medium access control layer.
In an aspect, a terminal device, comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the terminal device to perform the method implemented by the terminal device, discussed above.
In some embodiments, the network device is caused to: if the measurement report is triggered and there are not enough resources for a transmission of the measurement report, receive, from a terminal device, a scheduling request for the measurement report.
In some embodiments, the network device is further caused to: transmit, to the terminal device 110, a first configuration indicating a first set of resources allocated for the scheduling request for the measurement report.
In some example embodiments, the network device is caused to: transmit, to the terminal device, a second configuration indicating a second set of resources allocated for the measurement report, after the transmission of the scheduling request.
In some example embodiments, the network device is further caused to: receive, from the terminal device, a MAC CE indicating that the terminal device is to stop the event trigger period report.
In some example embodiments, the network device is further caused to: receive, from the terminal device, the measurement report comprised in a MAC CE.
In some example embodiments, a set of fields in the MAC CE is truncated based on logic channel prioritization.
In some example embodiments, a ratio value is configured for the MAC CE comprising the measurement report.
In some example embodiments, the MAC CE comprises a serving cell measurement report and a set of candidate cell measurements.
In some example embodiments, the set of candidate cell measurements is sorted in decreasing order, and wherein if the MAC CE is truncated, a subset of lower candidate cell measurements is truncated.
In some example embodiments, the MAC CE comprising the measurement report comprises an indication of event triggered channel state information report index.
In some example embodiments, the MAC CE comprises each triggered channel state information report, where each triggered channel state information report in the MAC CE is a container of a corresponding channel state information report on uplink control information with padding for byte alignment, or wherein all triggered channel state information report in the MAC CE is a container of uplink control information including all corresponding channel state information reports on uplink control information.
In some example embodiments, the network device is further caused to: receive, from the terminal device, a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information.
In some example embodiments, the network device is further caused to: transmit, to the terminal device, downlink control information indicating a new transmission.
In some example embodiments, the network device is further caused to: transmit, to the terminal device, a downlink MAC CE indicating the MAC is accepted; and receive, from the terminal device, an acknowledgement of the downlink MAC CE.
In an aspect, a network device, comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the network device to perform the method implemented by the network device, discussed above.
In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device, discussed above.
In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device, discussed above.
In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device, discussed above.
In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device, discussed above.
Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGS. 1 to 6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage  medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include 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) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.
Although the present disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (20)

  1. A terminal device, comprising:
    a processor, configured to cause the terminal device to:
    determine, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result;
    in accordance with a determination that the event of measurement result is satisfied, transmit, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result;
    increase, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication;
    in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, trigger, at the second protocol layer, a measurement report; and
    in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmit, to a network device, a scheduling request for the measurement report.
  2. The terminal device of claim 1, wherein the terminal device is further caused to:
    start, at the second protocol layer, a first timer after the reception of the event satisfied indication from the first protocol layer; and
    reset, at the second protocol layer, the counter to a second predetermined number after an expiration of the timer.
  3. The terminal device of claim 1, wherein the terminal device is further caused to:
    in accordance with a determination that the event of measurement result is unsatisfied based on a further measurement result, transmit, at the first protocol layer to the second protocol layer, an event unsatisfied indication indicating the event of measurement result being unsatisfied; and
    reset, at the second protocol layer, the counter to a second predetermined number based on the event unsatisfied indication.
  4. The terminal device of any of claims 1-3, wherein the terminal device is further caused to:
    start a second timer after triggering the measurement report; or
    start the second timer after the transmission of the measurement report,
    wherein the measurement report is not triggered during running time of the second timer.
  5. The terminal device of any of claims 1-3, wherein the terminal device is further caused to:
    perform at least one of the followings during a channel state information report being active:
    skipping triggering the measurement report, or
    cancelling the triggered measurement report.
  6. The terminal device of any of claims 1-5, wherein the terminal device is caused to:
    determine whether there are uplink shared channel resources available for the transmission of the measurement report; and
    in accordance with a determination that there are no uplink shared channel resources available for the transmission of the measurement report, determine that there are not enough resources for the transmission of the measurement report.
  7. The terminal device of any of claims 1-5, wherein the terminal device is caused to:
    determine whether uplink shared channel resources are able to accommodate a medium access control control element (MAC CE) comprising the measurement report and a subheader of the measurement report; and
    in accordance with a determination that the uplink shared channel resources are unable to accommodate the MAC CE and the subheader, determine that there are not enough resources for the transmission of the measurement report.
  8. The terminal device of any of claims 1-7, wherein the terminal device is caused to:
    receive, from the network device, a first configuration indicating a first set of resources allocated for the scheduling request for the measurement report.
  9. The terminal device of any of claims 1-8, wherein the terminal device is caused to:
    receive, from the network device, a second configuration indicating a second set of resources allocated for the measurement report, after the transmission of the scheduling request.
  10. The terminal device of claim 1, wherein the terminal device is further caused to:
    transmit, to the network device, the measurement report comprised in a MAC CE.
  11. The terminal device of claim 10, wherein a ratio value is configured for the MAC CE comprising the measurement report.
  12. The terminal device of claim 11, wherein the terminal device is caused to:
    in accordance with a determination that a ratio of a size of the MAC CE comprising the measurement report to a size of a scheduled medium access control protocol data unit is larger than the ratio value, skip generating the MAC CE comprising the measurement report; and
    transmit the scheduling request for the measurement report.
  13. The terminal device of claim 11, wherein the terminal device is caused to:
    in accordance with a determination that a code rate of physical uplink shared channel is higher than a configured threshold, skip generating the MAC CE comprising the measurement report on the physical uplink shared channel; and
    transmit the scheduling request for the measurement report.
  14. The terminal device of claim 11, wherein the MAC CE comprising the measurement report comprises an indication of event triggered channel state information report index.
  15. The terminal device of claim 11, wherein the MAC CE comprises each triggered channel state information report, where each triggered channel state information report in the MAC CE is a container of a corresponding channel state information report on uplink control information with padding for byte alignment, or
    wherein all triggered channel state information report in the MAC CE is a container of uplink control information including all corresponding channel state information reports on uplink control information.
  16. The terminal device of claim 1, wherein the terminal device is further caused to:
    transmit, to the network device, a MAC comprising information of the event of the measurement result being satisfied and satisfied reference signal information.
  17. The terminal device of claim 16, wherein the terminal device is further caused to:
    receive, from the network device, downlink control information indicating a new transmission; and
    activate a periodic measurement reporting on periodic uplink resources, after a duration from the reception of the downlink control information.
  18. The terminal device of any of claims 1-17, wherein the first protocol layer is a physical layer, and the second protocol layer is a medium access control layer.
  19. A communication method implemented at a terminal device, , comprising:
    determining, at a first protocol layer of the terminal device, whether an event of measurement result is satisfied based on a measurement result;
    in accordance with a determination that the event of measurement result is satisfied, transmitting, at the first protocol layer to a second protocol layer of the terminal device, an event satisfied indication indicating the event of measurement result being satisfied and the measurement result;
    increasing, at the second protocol layer, a counter by a first predetermined number based on the event satisfied indication;
    in accordance with a determination that a value of the counter is equal to or larger than a configured threshold, triggering, at the second protocol layer, a measurement report; and
    in accordance with a determination that the measurement report is triggered and there are not enough resources for a transmission of the measurement report, transmitting, to a network device, a scheduling request for the measurement report.
  20. A computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method according to claim 19.
PCT/CN2023/137638 2023-12-08 2023-12-08 Devices and methods for communication Pending WO2025118295A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/137638 WO2025118295A1 (en) 2023-12-08 2023-12-08 Devices and methods for communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/137638 WO2025118295A1 (en) 2023-12-08 2023-12-08 Devices and methods for communication

Publications (1)

Publication Number Publication Date
WO2025118295A1 true WO2025118295A1 (en) 2025-06-12

Family

ID=95981122

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/137638 Pending WO2025118295A1 (en) 2023-12-08 2023-12-08 Devices and methods for communication

Country Status (1)

Country Link
WO (1) WO2025118295A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210037589A1 (en) * 2018-01-24 2021-02-04 Ntt Docomo, Inc. Terminal and radio communication method
US20220110181A1 (en) * 2019-02-11 2022-04-07 Apple Inc. Apparatus and method for enhanced beam recovery
US20220190939A1 (en) * 2019-01-04 2022-06-16 Apple Inc. System and method for framework of l1-sinr measurement and reporting
CN116074887A (en) * 2021-11-04 2023-05-05 维沃移动通信有限公司 Reporting method, device and terminal

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210037589A1 (en) * 2018-01-24 2021-02-04 Ntt Docomo, Inc. Terminal and radio communication method
US20220190939A1 (en) * 2019-01-04 2022-06-16 Apple Inc. System and method for framework of l1-sinr measurement and reporting
US20220110181A1 (en) * 2019-02-11 2022-04-07 Apple Inc. Apparatus and method for enhanced beam recovery
CN116074887A (en) * 2021-11-04 2023-05-05 维沃移动通信有限公司 Reporting method, device and terminal

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
VIVO: "Discussion on L1 enhancements for L1/L2 mobility", 3GPP DRAFT; R1-2302504, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 7 April 2023 (2023-04-07), XP052351986 *
XUEMING PAN, VIVO: "Discussion on L1 enhancements for L1L2 mobility", 3GPP DRAFT; R1-2300474; TYPE DISCUSSION; NR_MOB_ENH2-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 17 February 2023 (2023-02-17), XP052247619 *

Similar Documents

Publication Publication Date Title
WO2024026641A1 (en) Methods, terminal devices and computer readable medium for communication
WO2023159641A1 (en) Method, device and computer storage medium of communication
US20240397492A1 (en) Methods, devices, and computer readable medium for communication
WO2023184273A1 (en) Method, device and computer storage medium of communication
WO2025118295A1 (en) Devices and methods for communication
WO2023137726A1 (en) Method, device and computer readable medium for communication
WO2023082261A1 (en) Methods, devices, and computer readable medium for communication
WO2025091402A1 (en) Devices and methods for communication
WO2024065771A1 (en) Methods, devices and medium for communication
WO2024168736A1 (en) Devices and methods for communication
WO2025147829A1 (en) Devices and methods of communication
WO2025020196A1 (en) Devices and methods for communication
WO2025065189A1 (en) Device, method and computer readable medium for communications
WO2025091275A1 (en) Devices and methods of communication
WO2025030289A1 (en) Devices and methods for communication
WO2025199912A1 (en) Devices and methods for communication
WO2025015446A1 (en) Devices and methods for communication
WO2025217821A1 (en) Devices and methods for sub-band full duplex relatedtransmission
WO2025145350A1 (en) Devices and methods for communication
WO2024148542A1 (en) Methods, devices and medium for communication
WO2025030515A1 (en) Device, method and computer readable medium for communications
WO2025118245A1 (en) Devices and methods of communication
WO2024229831A1 (en) Devices and methods for communication
WO2025199915A1 (en) Method and apparatus for determining predicted beams to report
WO2025054920A1 (en) Devices and methods of communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23960606

Country of ref document: EP

Kind code of ref document: A1