Method and apparatus for sending report
By using terminal devices to determine event instances based on reference signals and initiate time windows, the problems of untimely time windows and unclear resource usage in the CSI reporting process are resolved. This enables timely event reporting and efficient resource utilization, improving the reliability of reports and transmission performance.
Patent Information
- Application Number
- PCT/CN2025/093527
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
The existing CSI reporting process has problems such as the inability to open time windows in a timely manner, undefined CPU usage time, coexistence issues with SBFD, and excessive PUCCH transmission, which lead to untimely event reporting and unclear resource usage.
The terminal device determines the event instance based on the first reference signal and the second reference signal, starts the time window and sends a report when the conditions are met, clarifies the start and end points of CPU usage, and selects an appropriate PUSCH timing to avoid excessive transmission.
It enables timely reporting of incidents, avoids missed detections and unnecessary resource consumption, ensures high performance and reliability of reports, and reduces additional overhead and interference.
Smart Images

Figure CN2025093527_12112026_PF_FP_ABST
Abstract
Description
Report transmission method and device Technical Field
[0001] The embodiments of this application relate to the field of communication technology. Background Technology
[0002] 5G NR supports Channel State Information (CSI) reporting. For example, a CSI report may include at least one of the following: CSI-RS Resource Indicator (CRI), SSB Resource Indicator (SSBRI), Layer 1 Reference Signal Received Power (L1-RSRP), and Layer 1 Signal-to-Interference-plus-Noise Ratio (L1-SINR), i.e., beam-related reporting. The terminal device sends beam reports to the network device, which can then perform beam management based on these reports, for example, indicating a better beam for the terminal device.
[0003] When a terminal device sends a CSI report is determined by the network device; that is, the report is scheduled by the network device. The network device can be configured to send periodic CSI reports, thus the terminal device sends CSI reports periodically; the network device can be configured to send semi-persistent CSI reports, which the terminal device sends periodically after being activated by the network device; the network device can be configured to send a non-periodic CSI reports, which the terminal device sends once after being triggered by the network device. The CSI report includes measurement results specific to the serving cell.
[0004] In Rel-19 (Release-19, version 19), event-driven reporting (also known as event-triggered reporting or end-device initiated reporting) was introduced. Event-driven CSI reporting corresponds to traditional CSI reporting.
[0005] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention
[0006] The inventors discovered that the reporting process initiated by a terminal device mainly includes: the terminal device determining an event instance based on measurements of the new beam reference signal and / or the current beam reference signal; determining whether the event is satisfied based on the event instance; and, if the event is satisfied, sending a PUCCH (Physical Uplink Control Channel) and then sending the report on a PUSCH (Physical Uplink Shared Channel). However, the current reporting process is incomplete, and some problems remain unresolved, such as the inability to open the time window in a timely manner, the undefined CPU (CSI Processing Unit) occupancy time, the coexistence with SBFD (Subband non-overlapping Full Duplex), and excessive PUCCH transmission.
[0007] To address at least one of the above-mentioned problems or other similar issues, embodiments of this application provide a method and apparatus for sending a report.
[0008] According to one aspect of the embodiments of this application, a method for sending a report is provided, applied to a terminal device, the method comprising:
[0009] The terminal device determines the event instance based on at least one of the first reference signal, the second reference signal, and the first threshold;
[0010] If the event instance is not within the time window for the first reference signal or the second reference signal, the terminal device activates the time window for the first reference signal or the second reference signal;
[0011] If the first condition is met, the terminal device determines that the time window for the first reference signal or the second reference signal has ended;
[0012] If the number of event instances within the time window for the first reference signal or the second reference signal is greater than or equal to the second threshold, the terminal device sends a report on the PUSCH.
[0013] According to another aspect of the embodiments of this application, a report transmitting apparatus is provided, configured in a terminal device, the apparatus including a processing unit and a transmitting unit:
[0014] The processing unit determines the event instance based on at least one of the first reference signal, the second reference signal, and the first threshold;
[0015] If the event instance is not within the time window for the first reference signal or the second reference signal, the processing unit activates the time window for the first reference signal or the second reference signal;
[0016] If the first condition is met, the processing unit determines that the time window for the first reference signal or the second reference signal has ended;
[0017] If the number of event instances within the time window for the first reference signal or the second reference signal is greater than or equal to the second threshold, the sending unit sends a report on the PUSCH.
[0018] According to one aspect of the embodiments of this application, a method for sending a report is provided, applied to a terminal device, the method comprising:
[0019] The terminal device determines whether to send PUCCH at the PUCCH timing based on L first periodic reference signals and / or K second periodic reference signals, where L≥1 and K≥1;
[0020] If it is determined that the PUCCH will be sent, the terminal device sends a report on the PUSCH; if it is determined that the PUCCH will not be sent, the terminal device does not send a report.
[0021] The report occupies the CPU starting from a second time point, which is the first symbol of the earliest reference signal in a set of reference signals; the set of reference signals includes L first reference signals and / or K second reference signals; the l-th first reference signal is the latest reference signal in the l-th first periodic reference signal that is no later than the first time point before the PUCCH timing, 1≤l≤L; the k-th second reference signal is the latest reference signal in the k-th second periodic reference signal that is no later than the first time point before the PUCCH timing; or, the report occupies the CPU starting from a third time point before the PUCCH timing, where the third time point is configured or predefined.
[0022] Wherein, the L first periodic reference signals are new beam reference signals configured by RRC signaling; when the report is for event 7, the K second periodic reference signals are determined according to K active TCI states, 1≤K≤8; and / or, when the report is for event 2 or event 1, the K second periodic reference signals are determined according to K indicated TCI states, K=1.
[0023] According to another aspect of the embodiments of this application, a report transmitting apparatus is provided, configured in a terminal device, the apparatus including a processing unit and a transmitting unit:
[0024] The processing unit determines whether to send a PUCCH at the PUCCH timing based on L first periodic reference signals and / or K second periodic reference signals, where L≥1 and K≥1.
[0025] If it is determined that the PUCCH will be sent, the sending unit sends a report on the PUSCH; if it is determined that the PUCCH will not be sent, the sending unit does not send a report.
[0026] The report occupies the CPU starting from a second time point, which is the first symbol of the earliest reference signal in a set of reference signals; the set of reference signals includes L first reference signals and / or K second reference signals; the l-th first reference signal is the latest reference signal in the l-th first periodic reference signal that is no later than the first time point before the PUCCH timing, 1≤l≤L; the k-th second reference signal is the latest reference signal in the k-th second periodic reference signal that is no later than the first time point before the PUCCH timing; or, the report occupies the CPU starting from a third time point before the PUCCH timing, where the third time point is configured or predefined.
[0027] Wherein, the L first periodic reference signals are new beam reference signals configured by RRC signaling; when the report is for event 7, the K second periodic reference signals are determined according to K active TCI states, 1≤K≤8; and / or, when the report is for event 2 or event 1, the K second periodic reference signals are determined according to K indicated TCI states, K=1.
[0028] According to one aspect of the embodiments of this application, a method for sending a report is provided, applied to a terminal device, the method comprising:
[0029] The terminal device sends a PUCCH at the appropriate PUCCH timing based on the event instance.
[0030] When the terminal device is configured in the first mode, the terminal device sends the PUSCH of the bearer report according to the DCI;
[0031] When the terminal device is configured in the second mode, the terminal device sends the PUSCH of the bearer report at the first valid PUSCH timing after the first time interval following the PUCCH timing;
[0032] Wherein, the effective PUSCH timing satisfies at least one of the following:
[0033] When the terminal device can only transmit the PUSCH on SBFD symbols, the valid PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with valid PRACH timing;
[0034] When the terminal device can only transmit the PUSCH on non-SBFD symbols, the valid PUSCH timing includes uplink symbols, and / or includes non-SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with downlink symbols, and / or does not overlap with valid PRACH timing.
[0035] When the terminal device is capable of transmitting PUSCH on SBFD symbols and / or non-SBFD symbols, the effective PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with effective PRACH timing; or, the effective PUSCH timing includes uplink symbols, and / or, includes non-SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with downlink symbols, and / or, does not overlap with effective PRACH timing.
[0036] According to another aspect of the embodiments of this application, a report transmitting apparatus is provided, configured in a terminal device, the apparatus including a transmitting unit:
[0037] The sending unit sends a PUCCH at the PUCCH timing according to the event instance;
[0038] When the terminal device is configured in the first mode, the sending unit sends the PUSCH of the bearer report according to the DCI;
[0039] When the terminal device is configured in the second mode, the sending unit sends the PUSCH of the bearer report at the first valid PUSCH timing after the first time interval following the PUCCH timing;
[0040] Wherein, the effective PUSCH timing satisfies at least one of the following:
[0041] When the transmitting unit can only transmit the PUSCH on SBFD symbols, the valid PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with valid PRACH timing;
[0042] When the transmitting unit can only transmit the PUSCH on non-SBFD symbols, the valid PUSCH timing includes uplink symbols, and / or includes non-SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with downlink symbols, and / or does not overlap with valid PRACH timing.
[0043] When the transmitting unit is capable of transmitting PUSCH on SBFD symbols and / or non-SBFD symbols, the effective PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with effective PRACH timing; or, the effective PUSCH timing includes uplink symbols, and / or, includes non-SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with downlink symbols, and / or, does not overlap with effective PRACH timing.
[0044] According to another aspect of the embodiments of this application, a terminal device is provided, including a memory and a processor, the memory storing a computer program, and the processor being configured to execute the computer program to implement the report sending method as described above.
[0045] According to another aspect of the embodiments of this application, a communication system is provided, including a network device and a terminal device, wherein the terminal device is configured to perform the report sending method as described above, and the network device is configured to receive the report sent by the terminal device.
[0046] One of the beneficial effects of this application's embodiments is that, on the one hand, the terminal device determines whether the time window has ended based on a first condition. Therefore, the time window can be promptly activated when the event needs to be re-detected, thus avoiding missed events and enabling timely reporting of events, providing continuous assurance for high-performance and highly reliable transmission. On the other hand, it clarifies the time point from which the report sent by the terminal device begins to occupy the CPU. Therefore, the terminal device and network device have a consistent understanding of the start and end points of the CPU usage for the report, thus avoiding ambiguity regarding CPU usage time. The network device can then configure the report reasonably based on the terminal device's CPU usage. Furthermore, it clarifies the conditions that must be met for a valid PUSCH timing. Therefore, the terminal device and network device have a consistent understanding of a valid PUSCH timing, thus avoiding ambiguity regarding when to send or receive reports, thereby ensuring the timeliness and reliability of report transmission. Finally, the terminal device always maintains a set of event instances and sends PUCCHs to this set of event instances, thus avoiding excessive PUCCH sending and the resulting overhead and interference. For example, excessive PUCCH sending can be avoided when maintaining multiple event instance sets simultaneously and sending PUCCH to each event instance set.
[0047] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.
[0048] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.
[0049] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description
[0050] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.
[0051] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;
[0052] Figure 2 is a schematic diagram of an event-driven report according to an embodiment of this application;
[0053] Figure 3 is another schematic diagram of an event-driven report according to an embodiment of this application;
[0054] Figure 4 is a schematic diagram of time-frequency domain resources configured with SBFD subbands;
[0055] Figure 5 is a schematic diagram of a report sending method according to an embodiment of this application;
[0056] Figure 6 is a schematic diagram of an example of a terminal device determining the end of a time window according to the method of an embodiment of this application;
[0057] Figure 7 is a schematic diagram of another example of a terminal device determining the end of a time window according to the method of an embodiment of this application;
[0058] Figure 8 is a schematic diagram of an applicable scenario for the method of this application embodiment;
[0059] Figure 9 is a schematic diagram of the scenario shown in Figure 8, assuming that no additional processing is performed for the first condition.
[0060] Figure 10 is a schematic diagram of the scenario shown in Figure 8, assuming additional processing is performed on the first condition.
[0061] Figure 11 is a schematic diagram of a report receiving method according to an embodiment of this application;
[0062] Figure 12 is another schematic diagram of a report sending method according to an embodiment of this application;
[0063] Figures 13 to 15 are schematic diagrams illustrating examples of reports sent by a terminal device according to the method of an embodiment of this application;
[0064] Figure 16 is another schematic diagram of a report receiving method according to an embodiment of this application;
[0065] Figure 17 is another schematic diagram of the report sending method according to an embodiment of this application;
[0066] Figure 18 is another schematic diagram of the report sending method according to an embodiment of this application;
[0067] Figure 19 is a schematic diagram of an example of a terminal device sending a report between the first PUCCH timing and the second PUCCH timing;
[0068] Figure 20 is a schematic diagram of a terminal device determining the event satisfaction based on the first set;
[0069] Figure 21 is a schematic diagram of a terminal device determining that an event is not satisfied based on a first set.
[0070] Figure 22 is a schematic diagram of a report receiving method according to an embodiment of this application;
[0071] Figures 23 to 25 are schematic diagrams of a report sending device according to an embodiment of this application;
[0072] Figures 26 to 28 are schematic diagrams illustrating the receipt of reports according to embodiments of this application;
[0073] Figure 29 is a schematic diagram of a terminal device according to an embodiment of this application;
[0074] Figure 30 is a schematic diagram of a network device according to an embodiment of this application. Detailed Implementation
[0075] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.
[0076] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.
[0077] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.
[0078] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.
[0079] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other currently known or future communication protocols.
[0080] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.
[0081] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), IAB hosts, etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" can encompass some or all of their functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.
[0082] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.
[0083] The terminal device may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine-type communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, etc.
[0084] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.
[0085] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.
[0086] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.
[0087] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, Figure 1 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.
[0088] In this embodiment of the application, network device 101 and terminal devices 102 and 103 can transmit existing services or services that can be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.
[0089] It is worth noting that Figure 1 shows that both terminal devices 102 and 103 are within the coverage area of network device 101, but this application is not limited to this. Both terminal devices 102 and 103 may be outside the coverage area of network device 101, or one terminal device 102 may be within the coverage area of network device 101 while the other terminal device 103 may be outside the coverage area of network device 101.
[0090] In the embodiments of this application, the signaling may be, for example, Radio Resource Control (RRC) signaling; for example, referred to as an RRC message, including MIB, system information, dedicated RRC messages; or referred to as an RRC information element. The signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as a MAC control element. However, this application is not limited to these.
[0091] In the following description, without confusion, the terms "PDCCH" and "Physical Downlink Control Channel" or "Downlink Control Information" are used interchangeably, as are the terms "PDSCH" and "Physical Downlink Data Channel" or "Downlink Data". Furthermore, transmitting or receiving a PDCCH can be understood as transmitting or receiving downlink control information carried by the PDCCH; transmitting or receiving a PDSCH can be understood as transmitting or receiving downlink data carried by the PDSCH.
[0092] Furthermore, the terms "PUCCH" and "Physical Uplink Control Channel" or "Uplink Control Information" are interchangeable, as are the terms "PUSCH" and "Physical Uplink Data Channel" or "Uplink Data." Additionally, transmitting or receiving a PUCCH can be understood as transmitting or receiving downlink control information carried by the PUCCH; transmitting or receiving a PUSCH can be understood as transmitting or receiving uplink data carried by the PUSCH.
[0093] In this application embodiment, the terminal device needs to send event-driven reports on certain time-frequency resources. The determination of resources requires corresponding information interaction. For example, the terminal device can send a first message to request dynamically scheduled resources or notify whether semi-statically configured resources are actually used.
[0094] Figure 2 is a schematic diagram of an event-driven report according to an embodiment of this application, referred to as Mode B. As shown in Figure 2, the first resource used to send the first information is a configured periodic PUCCH resource (only one period is shown in Figure 2 for simplicity), and the second resource used to send the event-driven report is a configured periodic PUSCH or PUCCH resource (only one resource is shown). The first and second resources are associated, for example, one first resource is associated with one second resource. A PUCCH resource (or PUSCH resource) can also be called a PUCCH timing (or PUSCH timing).
[0095] As shown in Figure 2, the terminal device measures one or more reference signals (RS1 to RSN). After detecting an event that triggers a report, it notifies the network device that a report is being transmitted on the second resource associated with the first information (first resource) by sending a first message, and then sends a report on the associated second resource.
[0096] Conversely, if the terminal device does not detect an event, it may not send the first message.
[0097] Figure 3 is another schematic diagram of event-driven reporting according to an embodiment of this application, referred to as Mode A. As shown in Figure 3, the first resource for sending the first information is a configured periodic PUCCH resource (only one resource is shown), and the second resource for sending the event-driven report is a PDCCH (or DCI) scheduled resource.
[0098] As shown in Figure 3, the terminal device measures one or more reference signals (RS1 to RSN). After detecting an event that triggers a report, it requests the resources needed to send the report (i.e., requests the second resource) from the network device by sending first information on the first resource. Then, it receives the PDCCH and sends the report on the second resource scheduled by the PDCCH. The report can be carried by either PUSCH or PUCCH, and the first information is carried by PUCCH. Here, "resources" refers to time-frequency resources.
[0099] In this embodiment, as shown in Figures 2 and 3, the first information is used to notify the network device that a report transmission exists on the PUSCH associated with the first information (Mode B), or to request the PUSCH resources required to send the report from the network device (Mode A). In general, the first information is used to notify the network device that the terminal device has a report to send. After sending the PUCCH carrying the first information, the terminal device will send the report on the PUSCH. This PUSCH is configured by RRC signaling (Mode B) or scheduled by PDCCH (Mode A). For simplicity, in this embodiment, this PUSCH is referred to as the PUSCH associated with the PUCCH.
[0100] In this embodiment, the event that triggers the report is not limited. For example, an event could be that the measurement (L1-RSRP) of a new beam (one of RS1 to RSN) is higher than the measurement of the current beam by a certain value, or an event could be that the measurement of the current beam is lower than a certain value, i.e., corresponding to different types of events. In other words, the triggering condition for an event (e.g., event 2 or event 7) is that the measurement of a new beam is higher than the measurement of the current beam by a certain threshold. When the triggering condition is met, the event occurs. Events 2 and 7 have different definitions for the current beam; or, the triggering condition for an event (e.g., event 1) is that the measurement of the current beam is lower than a certain threshold. When the triggering condition is met, the event occurs. The terminal device can be configured with different types of events, for example, a report triggered by event 1 and a report triggered by event 2. A report is associated with an event, and the terminal device sends the report when the event occurs.
[0101] In the embodiments of this application, "event occurrence" can be referred to as event fulfillment, event fulfillment of triggering conditions, event being triggered, or report fulfillment of triggering conditions. The embodiments of this application do not limit the content of the report. For example, the report includes a reference signal index and measurements based on that reference signal; the report may include one or more reference signal indices and measurements. The report is used to report beam information, its purpose being to report the beam and measurements for that beam; the report can also be replaced by a beam report. A new beam can also be replaced by a candidate beam. "The measurements of the new beam are higher than the measurements of the current beam" means that the measurements of the reference signal associated with the new beam are higher than the measurements of the reference signal associated with the current beam; it can also be referred to as "the new beam is better than the current beam," or "the quality of the new beam is better than / better than the current beam." "Higher than" can also be replaced by "greater than or equal to." "Lower than" can also be replaced by "less than or equal to."
[0102] In this embodiment, "report" refers to "event-driven report." "Event-driven" can be replaced with "UE-initiated" or "event-triggered." DCI (Downlink Control Information) can be replaced with PDCCH or uplink DCI. The uplink channel carrying the report (also known as the CSI report) is, for example, the Physical Uplink Shared Channel (PUSCH). Report configuration information refers to the report configuration information for event-driven reports; the PUCCH carrying the first information and the PUSCH carrying the report are both used by the terminal device during the transmission of the event-driven report.
[0103] In this embodiment, a report is associated with a report configuration (i.e., report configuration information CSI-ReportConfig), and the two can be interchanged. The parameters, modules, or components shown in the figures are not limited to appearing simultaneously; the presence of only some parameters, modules, or components is also permitted.
[0104] On the other hand, Rel-17 (Release-17) standardized the unified transmission configuration indication (TCI) state. The Rel-17 unified TCI state is designed for single TRP scenarios, where the TCI field of DCI format 1_1 or DCI format 1_2 indicates one or more TCI states. DCI format 1_1 or DCI format 1_2 can schedule downlink data (DCI format 1_1 / 1_2 with DL assignment) or not schedule downlink data (DCI format 1_1 / 1_2 without DL assignment). Rel-19's support for event-driven reporting is based on the unified TCI state assumption.
[0105] In this embodiment, the indication or update of the TCI state includes the indication or update of the beam used by the terminal device. For the unified TCI state, the higher-layer parameter "unifiedTCI-StateType" can be configured to use a joint TCI state or a separate TCI state. When the value of the higher-layer parameter "unifiedTCI-StateType" is 'joint', the TCI state is a joint TCI state; when the value of the higher-layer parameter "unifiedTCI-StateType" is 'separate', the TCI state is a downlink TCI state and / or an uplink TCI state. For Rel-17 unified TCI, a TCI field indicates a joint TCI state, or indicates a downlink TCI state, or indicates an uplink TCI state, or indicates a downlink TCI state and an uplink TCI state. If a cell is configured with the higher-layer parameter "unifiedTCI-StateType", then the cell uses the unified TCI state. In this embodiment, a TCI state can be applied to a carrier or multiple carriers in a list. Without loss of generality, “a TCI state applied to a carrier” also means “a TCI state applied to a BWP (bandwidth part) of a carrier”.
[0106] Furthermore, in the embodiments of this application, the indication or update of the TCI state also includes the indication or update of the power control parameters used by the terminal device. For a unified TCI state, the TCI state IE includes power control parameters (including at least one of the target received power, path loss compensation factor, and closed-loop power control state index). For uplink transmission, the terminal device also applies the power control parameters in the TCI state when applying the TCI state.
[0107] In this embodiment, the terminal device can be instructed to a TCI state, thereby applying that TCI state, which is referred to as the "instructed TCI state". The "instructed TCI state" can be indicated by DCI, MAC CE, or RRC signaling. For example, MAC CE activates multiple TCI states, and then DCI indicates one of these TCI states, which is the indicated TCI state. Alternatively, MAC CE may activate only one TCI state, which is the indicated TCI state. For example, the set of TCI states configured by RRC signaling may include only one TCI state, which is the indicated TCI state. In this embodiment, a TCI state can be a combined TCI state, a downlink TCI state, or an uplink TCI state.
[0108] In this embodiment, for Subband Non-Overlapping Full Duplex (SBFD), the terminal device can be configured with non-overlapping downlink and uplink subbands within the existing downlink symbols (or time slots) or flexible symbols (or time slots), thus making the symbol (or time slot) an SBFD symbol (or time slot). Within an SBFD symbol, the terminal device can transmit uplink information on the uplink subband, or receive downlink information on the downlink subband; that is, the terminal device operates in half-duplex mode (receiving or transmitting only at the same time), while the network device can operate in full-duplex mode (receiving and transmitting simultaneously). Through SBFD, the terminal device can perform uplink transmission within the existing downlink symbols or flexible symbols, which is equivalent to increasing the time-frequency resources available for uplink transmission. Therefore, it can improve the uplink transmission capacity and coverage, and reduce the uplink transmission latency.
[0109] Figure 4 is a schematic diagram of time-frequency domain resources configured with SBFD subbands. As shown in Figure 4, the terminal device is configured with SBFD subbands. SBFD subbands include downlink subbands and uplink subbands; for example, the uplink subband is located between two downlink subbands in the frequency domain. The time slot containing the SBFD subband is called an SBFD time slot, and the symbol containing the SBFD subband is called an SBFD symbol. Other time slots (or symbols) are called non-SBFD time slots (or symbols). By configuring SBFD subbands in some symbols, some additional symbols can be used for uplink transmission, which helps to enhance uplink coverage, increase uplink capacity, and reduce uplink transmission latency.
[0110] In this embodiment, as shown in Figure 4, the SBFD subband includes an uplink subband and a downlink subband. Some time slots contain SBFD subbands; these time slots are SBFD time slots, and the symbols they include are SBFD symbols. Some time slots do not contain SBFD subbands; these time slots are non-SBFD time slots, and the symbols they include are non-SBFD symbols. It is also possible for a time slot to include both SBFD and non-SBFD symbols, which are not all listed here. By configuring SBFD subbands in some symbols, some additional symbols can be used for uplink transmission, thereby enhancing uplink coverage, increasing uplink capacity, and reducing uplink transmission latency.
[0111] In the embodiments of this application, "SBFD symbol" can be replaced with "SBFD time slot", and "non-SBFD symbol" can be replaced with "non-SBFD time slot".
[0112] In the embodiments of this application, a carrier (or cell) can be configured with SBFD subbands, referred to as an SBFD carrier. A portion of the bandwidth (BWP) of a carrier overlaps with the SBFD subband in the frequency domain; therefore, the BWP includes both SBFD symbols and non-SBFD symbols. For simplicity, the term SBFD carrier can also refer to the BWP within that carrier that overlaps with the SBFD subband. A carrier that is not configured with SBFD subbands can be referred to as a non-SBFD carrier. A non-SBFD carrier does not include SBFD symbols, only non-SBFD symbols.
[0113] In this embodiment, the terminal device receives configuration information from the network device. This configuration information is used to configure the time-domain and / or frequency-domain positions of the SBFD sub-band. Therefore, the terminal device can determine which symbols are SBFD symbols and which are non-SBFD symbols based on the configuration information.
[0114] In this embodiment, a terminal device supporting SBFD can operate under Configuration 1 (i.e., the terminal device is not configured with sbfd-Configuration2-Transmission) or Configuration 2 (i.e., the terminal device is not configured with sbfd-Configuration2-Transmission). Under Configuration 1, the terminal device can only perform uplink transmissions on SBFD symbols (i.e., uplink transmissions are restricted to SBFD symbols), or it can only perform uplink transmissions on non-SBFD symbols (i.e., uplink transmissions are restricted to non-SBFD symbols). Under Configuration 2, the terminal device can perform uplink transmissions on SBFD symbols and / or non-SBFD symbols (i.e., there is no restriction on uplink transmissions). In other words, under Configuration 2, there is no restriction on the symbol type for uplink transmissions by the terminal device; the terminal device's uplink transmissions can be located only on SBFD symbols, or only on non-SBFD symbols, or span between SBFD symbols and non-SBFD symbols.
[0115] The embodiments of this application will now be described with reference to the accompanying drawings. It is worth noting that "when," "if," and "under certain circumstances" have the same meaning and can be used interchangeably.
[0116] First aspect of the embodiments
[0117] The inventors discovered that a terminal device can be configured to detect (or evaluate) an event based on measurement results over a period of time (i.e., a time window) to determine whether the event meets the requirements. The duration of the terminal device's event detection must be long enough, i.e., the length of a time window. However, within a time window, certain conditions may change, requiring the terminal device to re-detect the event. Because a new round of detection is initiated midway through the time window, the duration of this new round of detection may not reach the length of a time window, leading to inaccurate detection results, missed detections, and delayed event reporting.
[0118] To address at least one of the aforementioned problems or other similar issues, embodiments of this application provide a method for sending a report, described from the perspective of a terminal device. Without loss of generality, embodiments of this application are described from the perspective of a report, specifically a report configuration (CSI-ReportConfig).
[0119] Figure 5 is a schematic diagram of a report sending method according to an embodiment of this application. As shown in Figure 5, the method includes:
[0120] 510: The terminal device determines an event instance based on at least one of the first reference signal, the second reference signal, and the first threshold;
[0121] 520: If the above event instance is not within the time window for the first reference signal or the second reference signal, the terminal device starts the time window for the first reference signal or the second reference signal;
[0122] 530: If the first condition is met, the terminal device determines that the time window for the first reference signal or the second reference signal has ended;
[0123] 540: If the number of event instances within the time window of the first reference signal or the second reference signal is greater than or equal to the second threshold, the terminal device sends a report on the PUSCH.
[0124] It is worth noting that Figure 5 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 5 above.
[0125] According to the above embodiments, the terminal device determines the end of the time window when the first condition is met. Therefore, the time window can be started in a timely manner when it is necessary to re-detect the event, thereby avoiding missed detection of the event and realizing timely reporting of the event, providing continuous protection for high-performance and high-reliability transmission.
[0126] In the above embodiment, in operation 530, if the first condition is met within the time window for the first reference signal or the second reference signal, the terminal device determines that the time window has ended.
[0127] The method of this application embodiment will be illustrated below using Event 2 as an example.
[0128] For event 2, the first reference signal is, for example, a new beam reference signal, and the second reference signal is, for example, the current beam reference signal. The new beam reference signal can be a reference signal configured by RRC signaling, and the current beam reference signal can be a reference signal indicating the TCI state. When the L1-RSRP of the first reference signal is higher than the L1-RSRP of the second reference signal by a first threshold (denoted as time t), the terminal device determines an event instance, that is, the terminal device determines the event instance based on the first reference signal, the second reference signal, and the first threshold.
[0129] In the example above, the terminal device can be configured with one or more first reference signals, and the terminal device maintains a time window for each first reference signal. Assume that the terminal device determines an event instance for a first reference signal at time t. If the event instance (i.e., time t) is not within the time window of the first reference signal (i.e., the time window of the first reference signal has not yet been activated), the terminal device activates the time window for the first reference signal. Conversely, if the event instance is within the time window of the first reference signal, the terminal device does not activate the time window for the first reference signal.
[0130] In the example above, the length of the time window (denoted as W) can be configured by RRC signaling.
[0131] Based on the above example, the terminal device determines whether there is an event instance for each first reference signal, maintains a time window for each first reference signal, and determines whether to start the time window when an event instance occurs. The started time window ends after a time length W.
[0132] In the embodiments of this application, unless otherwise specified, event instances and time windows refer to event instances and time windows for the same first reference signal (or second reference signal), and the descriptions of event instances and time windows apply to the same first reference signal (or second reference signal). Based on this, additional operations are performed for the first condition.
[0133] In the example above, if the first condition is met, the terminal device considers the time window to be in an ended state. For example, assuming the first condition is met at time t0, if time t0 is within the time window (i.e., the time window is running at this moment, but its length has not yet reached W), the terminal device considers the time window to have ended at time t0 (i.e., the time window ends early); if time t0 is not within the time window (i.e., the time window is not running at this moment), then naturally, the time window is already in an ended state. Simply put, when the first condition is met, if the time window has not yet ended, then the time window ends, thus placing the time window in an ended state; if the time window has already ended, then no further action is needed, and the time window is already in an ended state.
[0134] In the example above, a time window is opened by an event instance. Event instances may still occur during the time window's operation. If the number of event instances within a time window is greater than or equal to the second threshold (denoted as M), the terminal device considers event 2 satisfied (i.e., triggered), and sends a PUCCH and a report. For mode A, the terminal device requests resources from the network device via PUCCH and sends a report on the PUSCH scheduled by DCI. For mode B, the terminal device notifies the network device via PUCCH that a report exists on the PUSCH associated with the PUCCH, and then sends the report on that PUSCH.
[0135] Figure 6 is a schematic diagram of an example of a terminal device determining the end of a time window according to the method of an embodiment of this application, showing the case of event 2.
[0136] As shown in Figure 6, for the periodic new beam reference signal 1 and new beam reference signal 2, the terminal device periodically determines whether an event instance has occurred. Taking new beam reference signal 1 as an example, if an event instance occurs and the event instance is not within the time window of new beam reference signal 1, the terminal device starts a time window of length W for new beam reference signal 1.
[0137] If no additional processing is performed on the first condition, that is, if the method of the embodiment of this application is not used, and an event instance occurs at time t1, the terminal device determines a time window of length W starting from time t1. Since the event instance at time t3 is within the time window, the terminal device will not start a time window again at time t3.
[0138] If the aforementioned additional processing is applied to the first condition, i.e., using the method of the embodiments of this application, assuming the first condition is met at time t2, the terminal device considers the time window to end at time t2, thus obtaining a time window from time t1 to time t2. At this time, the event instance at time t3 is no longer within the time window, so the terminal device can start a time window of length W at time t3. Therefore, after the first condition is met, the terminal device can restart the time window and determine whether event 2 is met based on the number of event instances within the time window, thereby making a more timely and accurate judgment on the situation where event 2 is met.
[0139] For the new beam reference signal 2, at time t2 when the first condition is met, the time window has already ended, that is, it also satisfies the previously mentioned "the terminal device considers the time window to be over". Therefore, the terminal device can start the time window when the next event instance occurs.
[0140] The method of this application embodiment will be described below using Event 7 as an example. The similarities to Event 2 will not be repeated.
[0141] For event 7, the difference from event 2 is that the current beam reference signal is the reference signal of the active TCI state with the highest L1-RSRP of Q, where 1 ≤ Q ≤ 8. Similarly, when the L1-RSRP of the new beam reference signal is higher than the L1-RSRP of the current beam reference signal by a first threshold, the terminal device determines an event instance.
[0142] The example in Figure 6 also applies to event 7, and will not be repeated here.
[0143] The method of this application embodiment will be described below using Event 1 as an example. The similarities to Event 2 will not be repeated.
[0144] For event 1, the difference from event 2 is that the terminal device determines an event instance when the L1-RSRP of the second reference signal is lower than the first threshold. Although the terminal device has both a first and a second reference signal, it determines the event instance based solely on the second reference signal and the first threshold. The terminal device determines the event instance for the second reference signal and initiates a time window for the second reference signal.
[0145] Figure 7 is a schematic diagram of another example of a terminal device determining the end of a time window according to the method of an embodiment of this application, showing the case of event 1.
[0146] As shown in Figure 7, for a periodic current beam reference signal, the terminal device periodically determines whether an event instance has occurred. If an event instance occurs and the event instance is not within the time window of the current beam reference signal, the terminal device initiates a time window of length W for the current beam reference signal.
[0147] If no additional processing is performed on the first condition, that is, if the method of the embodiment of this application is not used, and an event instance occurs at time t1, the terminal device determines a time window of length W starting from time t1. Since the event instance at time t3 is within the time window, the terminal device will not start a time window again at time t3.
[0148] If the aforementioned additional processing is applied to the first condition, i.e., using the method of the embodiments of this application, assuming the first condition is met at time t2, the terminal device considers the time window to end at time t2, thus obtaining a time window from time t1 to time t2. At this time, the event instance at time t3 is no longer within the time window, so the terminal device can start a time window of length W at time t3. Therefore, after the first condition is met, the terminal device can restart the time window and determine whether event 1 is met based on the number of event instances within the time window, thereby making a more timely and accurate judgment on the situation where event 1 is met.
[0149] In the embodiments of this application, unless otherwise specified, "time window" can be replaced with "timer"; "within the time window" can be replaced with "during the timer's operation" or "when the timer is running"; "the terminal device considers the time window to have ended" can be replaced with "the terminal device considers the timer to have timed out".
[0150] In some embodiments of this application, satisfying the first condition includes at least one of the following: the second reference signal changes; the first threshold changes; the second threshold changes; the time window length of the RRC signaling configuration changes; the count of the number of event instances is reset; the first reference signal changes; the above report is sent; the DCI scheduling PUSCH is received; and a set of active TCI states changes.
[0151] For example, for event 2, satisfying the first condition includes at least one of the following: the second reference signal changes; the first threshold changes; the second threshold changes; the time window length of the RRC signaling configuration changes; the count of the number of event instances is reset; the first reference signal changes; the above report is sent; the DCI of the PUSCH scheduling is received.
[0152] For example, for event 7, satisfying the first condition includes at least one of the following: the first threshold changes; the second threshold changes; the time window length of the RRC signaling configuration changes; the count of the number of event instances is reset; the first reference signal changes; the above report is sent; the DCI scheduling PUSCH is received; or a set of active TCI states changes.
[0153] For example, for event 1, satisfying the first condition includes at least one of the following: the second reference signal changes; the first threshold changes; the second threshold changes; the time window length of the RRC signaling configuration changes; the count of the number of event instances is reset; the above report is sent; the DCI of the PUSCH scheduling is received.
[0154] The following example, Event 2, illustrates the meaning of "satisfying the first condition".
[0155] Figure 8 is a schematic diagram of an applicable scenario of the method of the present application embodiment; Figure 9 is a schematic diagram of the scenario shown in Figure 8, assuming that no additional processing is performed on the first condition (i.e., the method of the present application embodiment is not used, that is, the time window is not determined according to the first condition); Figure 10 is a schematic diagram of the scenario shown in Figure 8, assuming that additional processing is performed on the first condition (i.e., the method of the present application embodiment is used, that is, the time window is determined according to the first condition).
[0156] In the example above, for event 2, "meeting the first condition" includes "the second reference signal changes", that is, the current beam reference signal changes.
[0157] The impact of the first condition will be illustrated using the scenario shown in Figure 8 as an example. Figure 8 only illustrates a new beam reference signal and only shows the moment when the event instance occurs. Furthermore, Figure 8 also provides the time window length and the values of the second threshold. In the example in Figure 8, the current beam reference signal has changed, but the new beam reference signal has not. Under the unified TCI state framework, a change in the indicated TCI state can cause a change in the current beam reference signal.
[0158] As shown in Figure 8, the current beam reference signal changes at time t. Before time t, the current beam reference signal is current beam reference signal 1. From time t onwards, the current beam reference signal is current beam reference signal 2. Before time t, if the L1-RSRP of the new beam reference signal is higher than the L1-RSRP of current beam reference signal 1 by a first threshold, the terminal device determines an event instance (e.g., event instance 1). From time t onwards, if the L1-RSRP of the new beam reference signal is higher than the L1-RSRP of current beam reference signal 2 by a first threshold, the terminal device determines an event instance (e.g., event instance 2). The terminal device counts the number of event instances within a time window (e.g., using a counter). If the current beam reference signal changes, the count value (denoted as C) is reset to zero, and counting restarts after the current beam reference signal changes. If the count value within a time window is greater than or equal to a second threshold (denoted as M), the terminal device considers event 2 to be satisfied.
[0159] For the scenario shown in Figure 8, Figure 9 assumes no additional processing is performed for the first condition (i.e., the method of this application embodiment is not used). In this case, the terminal device will determine four time windows sequentially. The terminal device starts time window 2 at event instance 1. The current beam reference signal changes within time window 2, and an event instance occurs after the change. Since event instance 2 is located within time window 2, the terminal device cannot start another time window at event instance 2. Because the current beam used to determine event instance 1 and the current beam used to determine event instance 2 are different, the count cannot be accumulated across event instance 1 and event instance 2. Therefore, the count value needs to be reset to zero at time t. This causes the count value (C=2) within time window 2 to fail to reach the second threshold value (M=3), so the event is not satisfied. The terminal device can only determine that the event is satisfied based on subsequent event instances; for example, the event is not satisfied until the terminal device determines time window 4.
[0160] For the scenario shown in Figure 8, Figure 10 assumes additional processing for the first condition (i.e., using the method of the embodiments of this application). In this case, the terminal device ends the time window 2 shown in Figure 9 at time t, so event instance 2 is not within time window 2. Therefore, the terminal device can start the time window 3 shown in Figure 10 at event instance 2. After the current beam reference signal changes, the terminal device re-executes the operation of starting the time window, instead of using the time window generated before the change of the current beam reference signal. Similarly, the count value is reset to zero at time t. Within the time window 3 shown in Figure 10, the count value (C=3) reaches the second threshold value (M=3), so the event is satisfied. After the change of the current beam reference signal, the three event instances starting from event instance 2 can satisfy the event for the first time. However, the method of Figure 9 cannot identify the event when it is satisfied for the first time, but needs to wait until the next event is satisfied to identify it, so it cannot send a report in time and cannot report the event to the network device in time. In contrast, the method in Figure 10 can identify an event as soon as it is met, thus enabling more timely reporting and timely transmission of the event to network devices.
[0161] In the example above, for event 2, "satisfying the first condition" includes "a change in the first threshold," and / or "a change in the second threshold," and / or "a change in the length W of the time window." That is, when any of the above changes, it will ultimately lead to a change in the criteria used to determine whether the event is satisfied. Because the criteria have changed, after the change occurs, the terminal device re-executes the operation to start the time window, instead of relying on the old time window before the change to determine whether the event is satisfied. Therefore, when any of the above changes, the terminal device considers the time window to have ended.
[0162] In the example above, for event 2, "meeting the first condition" includes "the count of the number of event instances being reset." That is, when the count is reset to zero, the terminal device considers the time window to have ended. After the count is reset to zero, the terminal device recounts the number of event instances within the time window and re-executes the operation of starting the time window, instead of using the old time window.
[0163] For example, if the count value is reset to zero in the middle of a time window, and it continues to count within that time window, it is equivalent to counting within a time window of length less than W (W is configured by RRC signaling), i.e., counting within an incomplete time window. This is unfair for detecting whether an event is satisfied and may lead to missed events. As shown in Figure 9, the count value is reset to zero at time t, thus causing the three event instances starting from event instance 2 to not be detected as event satisfied.
[0164] In the example above, for event 2, "meeting the first condition" includes "the first reference signal changes". That is, each first reference signal has a time window. After the first reference signal changes due to reconfiguration, the terminal device re-executes the start time window operation for the new first reference signal, and no longer uses the time window of the old first reference signal.
[0165] In the example above, for event 2, "meeting the first condition" includes "the report is sent" and / or "the DCI of the scheduling PUSCH is received". That is, after the report is sent or the DCI of the scheduling PUSCH is received, the terminal device completes the previous round of reporting for the event and starts a new round of reporting for the event. Therefore, it also re-executes the start time window operation and no longer uses the old time window.
[0166] The meaning of "satisfying the first condition" will be explained below using event 7 as an example.
[0167] In the example above, for event 7, "satisfying the first condition" includes "a change in the active set of TCI states." For example, the terminal device can be activated with a set of A TCI states, where 1 ≤ A ≤ 8. For event 7, the current beam reference signal (i.e., the second reference signal) is the reference signal of the active TCI state with the highest L1-RSRP (1 ≤ Q ≤ 8). In other words, the second reference signal corresponds to the Q-th best TCI state among the A active TCI states. After the terminal device reactivates a set of TCI states, the meaning of the second reference signal changes, therefore the terminal device re-executes the startup time window operation instead of using the old time window.
[0168] In the example above, for event 7, the other cases included in "satisfying the first condition" have already been explained in the case of event 2, and will not be repeated here.
[0169] The following explanation uses event 1 as an example to illustrate the meaning of satisfying the first condition.
[0170] In the example above, all the cases included in "satisfying the first condition" for event 1 have been explained in the case of event 2, and will not be repeated here.
[0171] In the above embodiments, "the second reference signal changes" includes a change in the indicated TCI state and a change in the second reference signal determined according to the indicated TCI state; "the first threshold changes", "the second threshold changes", or "the length W of the time window changes" includes a change in the first threshold, the second threshold, or the length W of the time window due to reconfiguration; "the first reference signal changes" includes the terminal device being reconfigured with a set of first reference signals; "the activated set of TCI states changes" includes the terminal device being reactivated with a set of TCI states.
[0172] In some embodiments of this application, the first reference signal is a new beam reference signal configured by RRC signaling; in the case that the above report is for event 2 or event 1, the second reference signal is the current beam reference signal determined according to the indicated TCI state; in the case that the above report is for event 7, the second reference signal is the current beam reference signal determined according to the activated TCI state with the Q-highest L1-RSRP.
[0173] For example, for events 1, 2, and 7, the first reference signal is the new beam reference signal configured by the RRC signaling. After an event occurs, the terminal device can include one or more first reference signals in its transmitted report. The network device can then determine a more suitable new beam based on the reported first reference signal, thereby applying a better beam to the terminal device.
[0174] For example, for event 2 or event 1, the second reference signal is the current beam reference signal, which is the source reference signal of the indicated TCI state (e.g., CSI-RS), or a reference signal quasi-co-located with the source reference signal of the indicated TCI state (e.g., quasi-co-located SSB).
[0175] For example, for event 7, the second reference signal is the current beam reference signal, which is either the source reference signal of the active TCI state with the highest L1-RSRP (e.g., CSI-RS), or a reference signal quasi-co-located with the source reference signal of the active TCI state with the highest L1-RSRP (e.g., quasi-co-located SSB).
[0176] In some embodiments of this application, when the above report is for event 2 or event 7, if the L1-RSRP of the first reference signal is higher than the L1-RSRP of the second reference signal by a first threshold, the terminal device determines an event instance; when the above report is for event 1, if the L1-RSRP of the second reference signal is lower than the first threshold, the terminal device determines an event instance.
[0177] For example, for event 2 or event 7, if the L1-RSRP of the first reference signal is higher than the L1-RSRP of the second reference signal by a first threshold, the terminal device determines an event instance, wherein, as mentioned above, events 2 and 7 have different definitions for the second reference signal.
[0178] For example, for event 1, if the L1-RSRP of the second reference signal is lower than the first threshold, the terminal device determines an event instance.
[0179] In the above embodiments, the first thresholds corresponding to events 1, 2 and 7 are configured independently, and may be the same or different. This application does not impose any restrictions on this.
[0180] This application also provides a method for receiving reports, which is described from the perspective of a network device. The same content as in the previous embodiments will not be repeated.
[0181] Figure 11 is a schematic diagram of a report receiving method according to an embodiment of this application. As shown in Figure 11, the method includes:
[0182] 1110: The network device sends a first reference signal and / or a second reference signal to the terminal device;
[0183] 1120: The network device receives a report sent by the terminal device.
[0184] In some embodiments, the network device can also configure the length of the time window, a first threshold, a second threshold, etc., for the terminal device, send RRC signaling, PDCCH, PDSCH, DCI, etc. to the terminal device, and receive PUCCH, PUSCH, UCI, etc. from the terminal device. For details, please refer to the relevant technologies, which will not be elaborated here.
[0185] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined. The embodiments of this application are illustrated using two reports as an example, but can be extended to cases with more than two reports, which will not be elaborated further.
[0186] Through the embodiments of this application, the terminal device determines whether the time window has ended based on a first condition. Thus, the time window can be started in a timely manner when it is necessary to re-detect the event, thereby avoiding missed detection of the event and realizing timely reporting of the event, providing continuous protection for high-performance and high-reliability transmission.
[0187] Second aspect of the embodiments
[0188] The inventors discovered that a terminal device can determine whether to update one or more reports with the lowest priority based on CPU usage time. For example, if the total CPU usage of multiple reports over a period of time exceeds the number of CPUs the terminal device can support, the terminal device can choose not to update one or more reports with the lowest priority. With the introduction of event-driven reporting, it is also necessary to define CPU usage time for event-driven reports. In particular, determining the start and end points of CPU usage for reports targeting different events is a problem that needs to be solved.
[0189] To address at least one of the above-mentioned problems or other similar issues, embodiments of this application provide a method for sending a report, described from the perspective of a terminal device.
[0190] Figure 12 is a schematic diagram of a report sending method according to an embodiment of this application. As shown in Figure 12, the method includes:
[0191] 1210: The terminal device determines whether to send a PUCCH at the PUCCH timing based on L first periodic reference signals and / or K second periodic reference signals, where L≥1 and K≥1;
[0192] 1220: If it is determined that a PUCCH will be sent, the terminal device sends a report on the PUSCH; if it is determined that a PUCCH will not be sent, the terminal device does not send a report.
[0193] The aforementioned report occupies the CPU starting from a second time point, where the second time point is the first symbol of the earliest reference signal in a set of reference signals; the set of reference signals includes L first reference signals and / or K second reference signals; the l-th first reference signal is the latest reference signal among the l-th first periodic reference signals, no later than the first time point before the PUCCH timing, 1≤l≤L; the k-th second reference signal is the latest reference signal among the k-th second periodic reference signals, no later than the first time point before the PUCCH timing; or, the aforementioned report occupies the CPU starting from a third time point before the PUCCH timing, where the third time point is configured or predefined;
[0194] Wherein, the above-mentioned L first periodic reference signals are new beam reference signals configured by RRC signaling; in the case that the above-mentioned report is for event 7, the above-mentioned K second periodic reference signals are determined according to K active TCI states, 1≤K≤8; and / or, in the case that the above-mentioned report is for event 2 or event 1, the above-mentioned K second periodic reference signals are determined according to K indicated TCI states, K=1.
[0195] It is worth noting that Figure 12 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 12 above.
[0196] According to the above embodiments, it is clear from which point in time the report sent by the terminal device begins to occupy the CPU. As a result, the terminal device and the network device have a consistent understanding of the start and end points of the CPU occupation of the report, thereby avoiding ambiguity in CPU occupation time. The network device can make reasonable report configurations for the terminal device according to its CPU occupation.
[0197] Figure 13 is a schematic diagram of an example of a report sent by a terminal device according to the method of an embodiment of this application, showing the case of event 7 as an example.
[0198] As shown in Figure 13, for event 7, for a report, the terminal device is configured with L = 2 new beam reference signals, denoted as the first periodic reference signal w and the first periodic reference signal x, respectively. Each new beam reference signal is a periodic reference signal (the first periodic reference signal).
[0199] Furthermore, the terminal device activates K = 2 TCI states (the terminal device can activate a maximum of 8 TCI states). Based on the K activated TCI states, the terminal device determines K second periodic reference signals, denoted as second periodic reference signal y and second periodic reference signal z, respectively. For each activated TCI state, the corresponding second periodic reference signal is the reference signal for that activated TCI state. For example, it may be the source reference signal of that activated TCI state (e.g., CSI-RS), or a reference signal quasi-co-located with the source reference signal of that activated TCI state (e.g., quasi-co-located SSB).
[0200] In the example above, the terminal device determines an event instance based on the new beam reference signal and K current beam reference signals. Since the current beam reference signal is the reference signal for the active TCI state with the highest L1-RSRP (Q-th value), it is one of the K second-periodic reference signals. The terminal device determines an event instance when the L1-RSRP of the new beam reference signal is higher than the L1-RSRP of the current beam reference signal by a first threshold. If the terminal device has a time window configured, the terminal device considers event 7 satisfied if the number of event instances within a time window is greater than or equal to the second threshold. If the terminal device has no time window configured, the terminal device considers event 7 satisfied if the number of event instances is greater than or equal to 1. If event 7 is satisfied, the terminal device sends a PUCCH at the PUCCH timing. Afterwards, the terminal device sends a report on the DCI-scheduled PUSCH, or on the PUSCH associated with the PUCCH timing. If event 7 is not satisfied, the terminal device does not send a PUCCH at the PUCCH timing and therefore does not send a report.
[0201] The following explains the CPU usage of the report.
[0202] In the example above, the first time point is no later than the PUCCH timing, and the time interval between the first and second time points is T1 (T1≥0). T1 can be configured in the RRC signaling or predefined. When T1=0, the first time point is the first symbol of the PUCCH timing. Each first periodic reference signal includes multiple reference signals distributed across multiple periods. Among the reference signals no later than the first time point, the reference signal closest to the first time point (latest) is determined and denoted as the latest reference signal w and the latest reference signal x. Similarly, for the second periodic reference signals, the latest reference signal y and the latest reference signal z can be determined. The latest reference signal w and the latest reference signal x are called L first reference signals, and the latest reference signal y and the latest reference signal z are called K second reference signals. The earliest reference signal among the L first reference signals and the K second reference signals is the "latest reference signal z". That is, the report starts occupying the CPU from the first symbol (second time point) of the "latest reference signal z".
[0203] Figure 14 is a schematic diagram of another example of a report sent by a terminal device according to the method of the embodiments of this application, showing the case of event 2 or event 1 as an example. The similarities with the example shown in Figure 13 will not be repeated.
[0204] As shown in Figure 14, for either event 2 or event 1, for a report, the associated new beam reference signals include a first periodic reference signal w and a first periodic reference signal x. The associated current beam reference signal is the reference signal of the indicated TCI state, i.e., the source reference signal of the indicated TCI state (e.g., CSI-RS), or a reference signal quasi-co-located with the source reference signal of the indicated TCI state (e.g., quasi-co-located SSB). The number of indicated TCI states is one; for example, the indicated TCI state is one of the active TCI states, therefore there is only one associated second periodic reference signal, i.e., the second periodic reference signal y. In this case, the latest reference signals no later than the first time point include the latest reference signal w, the latest reference signal x, and the latest reference signal y; that is, the report occupies the CPU starting from the first symbol of the "latest reference signal w".
[0205] Figure 15 is a schematic diagram of another example of a report sent by a terminal device according to the method of the embodiments of this application, showing the case of event 1 as an example. The similarities with the example shown in Figure 14 will not be repeated.
[0206] As shown in Figure 15, for event 1, unlike the example shown in Figure 14, there is only one second periodic reference signal corresponding to the current beam reference signal. Whether the event is satisfied depends only on whether the L1-RSRP of the current beam reference signal is below a certain threshold. Therefore, as an implementation, the CPU's starting point can be determined solely based on the second periodic reference signal. In this case, the latest reference signal no later than the first time point only includes the latest reference signal y; that is, the report occupies the CPU starting from the first symbol of the "latest reference signal y".
[0207] Figures 13 to 15 above illustrate the CPU usage scenarios of reports using events 7, 2, 1, and 1 as examples, respectively. This application is not limited to these examples. For events 2, 1, or 7, a report can also begin occupying the CPU from a third time point no later than the PUCCH timing. This third time point can be configured or predefined by RRC signaling. The third time point is no later than the PUCCH timing, and the time interval between the third time point and the PUCCH timing is T3 (T3≥0). T3 can be configured or predefined by RRC signaling. When T3=0, the third time point is the first symbol of the PUCCH timing.
[0208] In some embodiments of this application, the above report ends CPU usage at a fourth time point, which is either the last symbol of PUSCH or the fifth time point after the PUCCH timing.
[0209] For example, for event 2, event 1, or event 7, the fourth time point is used to represent the end time of the CPU for a report. If the terminal device sends a report on the PUSCH, the fourth time point is the last symbol of the PUSCH. If the terminal device does not send a report, the fourth time point is the fifth time point following the PUCCH timing. The time interval between the fifth time point and the PUCCH timing is T2 (T2≥0), where T2 can be configured in the RRC signaling or predefined. When T2=0, the fifth time point is the last symbol of the PUCCH timing.
[0210] This application also provides a method for receiving reports, which is described from the perspective of a network device. The same content as in the previous embodiments will not be repeated.
[0211] Figure 16 is a schematic diagram of a report receiving method according to an embodiment of this application. As shown in Figure 16, the method includes:
[0212] 1610: The network device sends a first periodic reference signal and / or a second periodic reference signal to the terminal device;
[0213] 1620: The network device receives a report sent by the terminal device;
[0214] The aforementioned report occupies the CPU starting from a second time point, which is the first symbol of the earliest reference signal in a set of reference signals; the set of reference signals includes L first reference signals and / or K second reference signals; the l-th first reference signal is the latest reference signal among the l-th first periodic reference signals, no later than the first time point before the PUCCH timing, 1≤l≤L; the k-th second reference signal is the latest reference signal among the k-th second periodic reference signals, no later than the first time point before the PUCCH timing; or, the aforementioned report occupies the CPU starting from a third time point before the PUCCH timing, where the third time point is configured or predefined;
[0215] Wherein, L first periodic reference signals are new beam reference signals configured by RRC signaling; in the case that the above report is for event 7, K second periodic reference signals are determined according to K active TCI states, 1≤K≤8; and / or, in the case that the above report is for event 2 or event 1, K second periodic reference signals are determined according to K indicated TCI states, K=1.
[0216] In some embodiments, the above report ends CPU usage at a fourth time point, which is either the last symbol of PUSCH or the fifth time point after the PUCCH timing.
[0217] In some embodiments, the network device can also perform relevant configurations for the terminal device, such as configuring the aforementioned third time point. The network device can also send RRC signaling, PDCCH, PDSCH, DCI, etc. to the terminal device, or receive PUCCH, PUSCH, UCI, etc. from the terminal device. For details, please refer to the relevant technologies, which will not be elaborated here.
[0218] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0219] This application clarifies the time point from which reports sent by terminal devices begin to occupy CPU. As a result, terminal devices and network devices have a consistent understanding of the start and end points of CPU usage for reports, thereby avoiding ambiguity regarding CPU usage time. Network devices can then configure reports reasonably based on the CPU usage of terminal devices.
[0220] Third aspect of the embodiments
[0221] The inventors discovered that in Mode B, when an event is satisfied, the terminal device sends a report at the first valid PUSCH timing, X symbols after the PUCCH timing. Defining the valid PUSCH timing is a problem that needs to be solved. For example, for terminal devices supporting SBFD, determining the valid PUSCH timing in an SBFD scenario is a problem that needs to be solved.
[0222] To address at least one of the above-mentioned problems or other similar issues, embodiments of this application provide a method for sending a report, described from the perspective of a terminal device.
[0223] Figure 17 is a schematic diagram of a report sending method according to an embodiment of this application. As shown in Figure 17, the report sending method includes:
[0224] 1710: The terminal device sends a PUCCH at the appropriate PUCCH timing based on the event instance;
[0225] 1720: When the terminal device is configured in the first mode, the terminal device sends the bearer report PUSCH according to the DCI; when the terminal device is configured in the second mode, the terminal device sends the bearer report PUSCH at the first valid PUSCH timing after the first time interval following the PUCCH timing.
[0226] Among them, an effective PUSCH timing satisfies at least one of the following:
[0227] When the terminal device can only send PUSCH on SBFD symbols, the valid PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with valid PRACH timing;
[0228] When the terminal device can only send PUSCH on non-SBFD symbols, the effective PUSCH timing includes uplink symbols, and / or, including non-SBFD symbols, and / or, not overlapping with SSB symbols, and / or, not overlapping with downlink symbols, and / or, not overlapping with the effective PRACH timing.
[0229] When the terminal device is able to transmit PUSCH on SBFD symbols and / or non-SBFD symbols, the effective PUSCH timing includes SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with the effective PRACH timing; or, the effective PUSCH timing includes uplink symbols, and / or includes non-SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with downlink symbols, and / or does not overlap with the effective PRACH timing.
[0230] It is worth noting that Figure 17 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 17 above.
[0231] According to the above embodiments, the conditions that a valid PUSCH timing must meet are clearly defined. As a result, the terminal device and the network device have a consistent understanding of the valid PUSCH timing, thereby avoiding ambiguity regarding which PUSCH timing to send or receive reports, and thus ensuring the timeliness and reliability of report transmission.
[0232] In operation 1710, in some possible implementations, the terminal device determines an event instance according to the method described in the embodiments of the first and / or second aspects above, determines whether the event is satisfied based on the event instance, and sends a PUCCH at the PUCCH timing if the event is satisfied.
[0233] In the above embodiments, the terminal device can be configured with either mode A (first mode) or mode B (second mode). In mode A, the terminal device requests resources from the network device via PUCCH and sends a report on the PUSCH scheduled by DCI. In mode B, the terminal device notifies the network device via PUCCH that a report exists on the PUSCH associated with the PUCCH, and then sends the report on that PUSCH. In mode B, the report can be sent at periodic PUSCH times configured by RRC signaling. After sending the PUCCH, the terminal device sends the report at the first valid PUSCH time after a first time interval following the PUCCH time. In this embodiment, the first time interval is denoted as X (X≥0), and the unit of X can be symbols or seconds.
[0234] The following explains the definition of an effective PUSCH timing.
[0235] In this embodiment of the application, the terminal device may send PUSCH in any of the following situations.
[0236] Case 1: The terminal device can only send PUSCH on SBFD symbols;
[0237] Case 2: The terminal device can only send PUSCH on non-SBFD symbols;
[0238] Case 3: The terminal device can send PUSCH on both SBFD symbols and non-SBFD symbols.
[0239] In the above embodiments, for terminal devices that support SBFD, the specific configuration in which the terminal device sends PUSCH can be determined based on the configuration, and this application does not limit the specific configuration method; for terminal devices that do not support SBFD, the terminal device sends PUSCH in the above-mentioned case 2.
[0240] For example, in case 1, a PUSCH timing is a valid PUSCH timing if it satisfies the following condition:
[0241] -PUSCH timing includes symbols for SBFD symbols;
[0242] -PUSCH timing does not overlap with SSB symbols, i.e., it does not include SSB symbols.
[0243] Optionally, the above conditions may also include:
[0244] -PUSCH timing does not overlap with effective PRACH timing.
[0245] That is, in case 1, if a PUSCH timing satisfies all of the above conditions, then the PUSCH timing is a valid PUSCH timing.
[0246] In the embodiments of this application, unless otherwise specified, "overlap" includes "overlapping in the time domain and / or frequency domain"; "satisfying the following conditions" includes "at least satisfying the following conditions".
[0247] For example, in case 2, a PUSCH timing is a valid PUSCH timing if it meets the following conditions:
[0248] The symbols included in the -PUSCH event are all uplink symbols.
[0249] Optionally, the above conditions may also include:
[0250] -PUSCH timing does not overlap with effective PRACH timing.
[0251] That is, in case 2, if a PUSCH timing satisfies all of the above conditions, then the PUSCH timing is a valid PUSCH timing.
[0252] For example, in case 2, a PUSCH timing is a valid PUSCH timing if it meets the following conditions:
[0253] -PUSCH timing includes all non-SBFD symbols; here, a non-SBFD symbol can be an uplink symbol or a flexible symbol; therefore, PUSCH timing can include uplink symbols and flexible symbols, or only uplink symbols, or only flexible symbols.
[0254] -PUSCH timing does not overlap with downlink symbols, i.e., it does not include downlink symbols;
[0255] -PUSCH timing does not overlap with SSB symbols, i.e., it does not include SSB symbols.
[0256] Optionally, the above conditions may also include:
[0257] -PUSCH timing does not overlap with effective PRACH timing.
[0258] That is, in case 2, if a PUSCH timing satisfies all of the above conditions, then the PUSCH timing is a valid PUSCH timing.
[0259] For example, in case 3, if a PUSCH timing is a valid PUSCH timing under case 1, or a valid PUSCH timing under case 2, then that PUSCH timing is a valid PUSCH timing under case 3.
[0260] In the examples above, the downlink symbol, uplink symbol, or flexible symbol can be configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated; the SSB can be configured by ssb-PositionsInBurst.
[0261] In the examples above, unless otherwise specified, “PUCCH timing” can be replaced with “valid PUCCH timing”. The method for determining “valid PUCCH timing” can be any of the methods described above for determining valid PUSCH timing, simply by replacing “PUSCH” with “PUCCH”.
[0262] In some embodiments of this application, when the terminal device can only send PUSCH on non-SBFD symbols, the terminal device determines the valid PRACH timing based on at least one of the following:
[0263] When the terminal device is provided with a first PRACH configuration and a second PRACH configuration, the terminal device determines the effective PRACH timing according to the first PRACH configuration, or the terminal device determines the effective PRACH timing according to the first PRACH configuration and the second PRACH configuration.
[0264] In the above embodiments, the terminal device refers to a terminal device that supports SBFD. For a terminal device that supports SBFD, its configured PRACH timings can include multiple types. For example, a PRACH timing may only be located on non-SBFD symbols (Type 1), or only on SBFD symbols (Type 2), or across SBFD symbols and non-SBFD symbols (Type 3). The terminal device determines the valid PRACH timings among the PRACH timings; therefore, valid PRACH timings are a subset of PRACH timings.
[0265] In the above embodiments, the terminal device can receive a first PRACH configuration and a second PRACH configuration. The first PRACH configuration is used to configure PRACH timings located only on non-SBFD symbols, and the configured PRACH timing is type 1. The second PRACH configuration is used to configure additional PRACH timings, and the configured PRACH timing is type 2 or type 3. For terminal devices that do not support SBFD, they can only receive the first PRACH configuration, and the configured PRACH timing can only be type 1.
[0266] The following description pertains to terminal devices that support SBFD.
[0267] When determining whether a PUSCH timing overlaps with a valid PRACH timing, if the PUSCH timing is only located on an SBFD symbol, then the valid PRACH timing is actually determined only according to the second PRACH configuration, because only valid PRACH timing determined according to the second PRACH configuration can overlap with the PUSCH timing; if the PUSCH timing is only located on a non-SBFD symbol, then the valid PRACH timing can be determined only according to the first PRACH configuration, or according to both the first and second PRACH configurations, because valid PRACH timings determined according to both the first and second PRACH configurations can overlap with the PUSCH timing.
[0268] For example, the valid PRACH timing determined according to the first PRACH configuration may be located on a non-SBFD symbol, while the valid PRACH timing determined according to the second PRACH configuration may be located on both SBFD and non-SBFD symbols. Therefore, the valid PRACH timings generated by both configurations may overlap with PUSCHs located only on non-SBFD symbols. In this case, it is necessary to clarify which of the first and second PRACH configurations determines the valid PRACH timing.
[0269] For example, the effective PRACH timing is determined only based on the first PRACH configuration. Therefore, both terminal devices that support SBFD and those that do not support SBFD determine the effective PRACH timing based on the first PRACH configuration, and thus the effective PRACH timing determined by the two can be the same.
[0270] For example, the effective PRACH timing is determined based on the first PRACH configuration and the second PRACH configuration. Thus, terminal devices that support SBFD determine the effective PRACH timing based on the first PRACH configuration and the second PRACH configuration, while terminal devices that do not support SBFD determine the effective PRACH timing based on the first PRACH configuration. Therefore, the effective PRACH timings determined by the two can be different.
[0271] In the embodiments of this application, there are no restrictions on how to determine the valid PRACH timing in the configured PRACH timing; for example, existing technologies can be used.
[0272] In some embodiments, the PRACH timing determined according to the first PRACH configuration is located on a non-SBFD symbol, that is, the first PRACH configuration is used to configure the PRACH timing located on a non-SBFD symbol; the PRACH timing determined according to the second PRACH configuration is located on an SBFD symbol, or on both an SBFD symbol and a non-SBFD symbol, that is, the second PRACH configuration is used to configure the PRACH timing located on an SBFD symbol, and / or on both an SBFD symbol and a non-SBFD symbol.
[0273] For example, as mentioned above, the terminal device can receive a first PRACH configuration and a second PRACH configuration. The first PRACH configuration is used to configure PRACH timings that are only located on non-SBFD symbols, and the configured PRACH timings are of type 1. The second PRACH configuration is used to configure additional PRACH timings, and the configured PRACH timings are of type 2 or type 3.
[0274] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0275] On the other hand, the inventors discovered that in SBFD, when the PDSCH is located in an SBFD symbol, there is a situation where the resources allocated to the PDSCH partially overlap with the downlink subband, meaning that some PDSCH resources fall into the uplink subband. In this case, how to map the PDSCH PT-RS (Phase-Tracking Reference Signal) is a problem that needs to be solved. Similarly, when the PUSCH is located in an SBFD symbol, there is a situation where the resources allocated to the PUSCH partially overlap with the uplink subband, meaning that some PUSCH resources fall into the downlink subband. In this case, how to map the PUSCH PT-RS is a problem that needs to be solved.
[0276] To address at least one of the above issues or other similar issues, when the PDSCH is located in the SBFD symbol, the terminal device can map the PDSCH PT-RS (Phase-Tracking Reference Signal) to the RE (Resource Element), where the RE is located in the downlink subband and within the active downlink BWP.
[0277] For example, when the PDSCH is located on an SBFD symbol, if the terminal device wants to map a PDSCH PT-RS to a RE, it will only map the PDSCH PT-RS to the RE if the RE is located within a downlink subband and within an active downlink BWP. Otherwise, the terminal device will not map the PDSCH PT-RS to the RE. In other words, it is equivalent to puncturing the PT-RS.
[0278] To address at least one of the above issues or other similar issues, when the PUSCH is located on the SBFD symbol, the terminal device can map the PUSCH PT-RS to the RE, where the RE is located within the uplink subband and within the active uplink BWP.
[0279] For example, when the PUSCH is located on an SBFD symbol, if the terminal device wants to map a PUSCH PT-RS to a RE, it will only map the PUSCH PT-RS to that RE if the RE is located within an uplink subband and within an active uplink BWP. Otherwise, the terminal device will not map the PUSCH PT-RS to that RE. In other words, it is equivalent to puncturing the PT-RS.
[0280] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0281] On the other hand, the inventors discovered that the terminal device determines whether an event is satisfied based on the event instance. If the event is satisfied, the terminal device sends a PUCCH and a report on the PUSCH. In other words, the event instance triggers the terminal device to send a PUCCH. Since PUCCH (or PUSCH) transmission may fail, an ideal design should support PUCCH (or PUSCH) retransmission. As time increases, new event instances will appear. New event instances will trigger PUCCH (including PUCCH retransmission) transmission, and old events will also trigger PUCCH (including PUCCH retransmission) transmission. If the terminal device sends PUCCH for new event instances and old event instances separately (i.e., the terminal device maintains multiple event instance sets simultaneously and sends PUCCH for each event instance set), the terminal device needs to send multiple PUCCHs, and the number of PUCCHs to be sent may become increasingly large, resulting in additional overhead and interference. Therefore, how to avoid excessive PUCCH transmission is a problem that needs to be solved.
[0282] To address at least one of the above-mentioned problems or other similar issues, in operation 1710, the terminal device can send a PUCCH at the PUCCH timing based on the event instance, which can be achieved through the PUCCH sending method shown in Figure 18. As shown in Figure 18, the method includes:
[0283] 1810: The terminal device determines a first set before the first PUCCH timing, determines whether an event is satisfied based on the first set, the first set including event instances before the first PUCCH timing; and / or, the terminal device determines a second set before the second PUCCH timing, determines whether an event is satisfied based on the second set, the second set including event instances before the second PUCCH timing, the second PUCCH timing being later in time than the first PUCCH timing;
[0284] 1820: When the event is satisfied, the terminal device sends a PUCCH at the first PUCCH timing or the second PUCCH timing.
[0285] It is worth noting that Figure 18 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 18 above.
[0286] According to the above embodiments, the terminal device always maintains a set of event instances and sends PUCCHs for this set of event instances, thereby avoiding excessive PUCCH sending and the resulting additional overhead and interference. For example, it can avoid excessive PUCCH sending that would occur if multiple event instance sets were maintained simultaneously and PUCCHs were sent for each event instance set.
[0287] In the above embodiments, the terminal device can be configured with periodic PUCCH resources to generate periodic PUCCH opportunities. Before each PUCCH opportunity, the terminal device determines a set of event instances and determines whether to send a PUCCH on that PUCCH opportunity based on this set of event instances. Assume that the second PUCCH opportunity is time-wise after the first PUCCH opportunity. Before the first PUCCH opportunity, the terminal device determines a first set, which includes event instances preceding the first PUCCH opportunity. Before the second PUCCH opportunity, the terminal device determines a second set, which includes event instances preceding the second PUCCH opportunity. The first or second set can be an empty set.
[0288] In some embodiments, if the terminal device sends a report between the first PUCCH timing and the second PUCCH timing, the second set does not include the first set.
[0289] Figure 19 is a schematic diagram of an example of a terminal device sending a report between the first PUCCH timing and the second PUCCH timing. As shown in Figure 19, the first set determined by the terminal device before the first PUCCH timing includes event instance 1 and event instance 2. The terminal device determines that the events are satisfied based on the first set, and thus sends a PUCCH at the first PUCCH timing, followed by sending a report on the PUSCH. The second PUCCH timing is the next available PUCCH timing after the first PUCCH timing. The terminal device determines a second set before the second PUCCH timing. Since the terminal device has previously sent a report for the first set, the determined second set no longer includes the event instances in the first set, but only includes the newly emerging event instances 3 and 4. The terminal device determines whether the events are satisfied based on the second set, and thus determines whether to send a PUCCH at the second PUCCH timing. In other words, after the terminal device sends a report for the first set, the terminal device clears the event instances included in the first set, so that the event instances before the second PUCCH timing do not include event instances 1 and 2.
[0290] In other embodiments, if the terminal device does not send a report between the first PUCCH timing and the second PUCCH timing, the second set may or may not include the first set.
[0291] For example, if the terminal device does not send a report between the first PUCCH timing and the second PUCCH timing, the second set may include the first set, or it may not include the first set.
[0292] In the above embodiments, if the terminal device determines that the event is satisfied based on the first set, the second set may include the first set; and / or, if the terminal device determines that the event is not satisfied based on the first set, the second set may not include the first set.
[0293] Figure 20 is a schematic diagram of a terminal device determining that an event is satisfied based on a first set. As shown in Figure 20, the first set determined by the terminal device before the first PUCCH timing includes event instance 1 and event instance 2. The terminal device determines that the event is satisfied based on the first set, but fails to send a report for the first set.
[0294] This application does not limit the reasons for the failure to send a report. For example, because the first PUCCH timing overlaps with an uplink transmission with higher priority, the terminal device fails to send a PUCCH at the first PUCCH timing, and therefore cannot send a report. Or, for example, because the PUCCH sent by the terminal device at the first PUCCH timing is not successfully received by the network device, the network device does not send the DCI for scheduling the PUSCH, and therefore the terminal device cannot send a report.
[0295] According to an embodiment of this application, if an event is met but a report is not sent for the first set, the second set includes event instances 1 and 2 from the first set, as well as newly emerging event instances 3 and 4. When the terminal device generates and sends a report for the second set, the report content may also include the content of a report previously generated for the first set but not sent, effectively granting another opportunity to send a report for the first set.
[0296] As another example, assuming that event instance 3 and event instance 4 do not appear in Figure 20, in this case, the second set will be the same as the first set, which is equivalent to the terminal device resending the PUCCH (sending the PUCCH at the second PUCCH timing) and sending the report (sending the report after the second PUCCH timing) based on the first set, thereby improving the reliability of the report transmission.
[0297] Figure 21 is a schematic diagram of a terminal device determining that an event is not satisfied based on a first set. As shown in Figure 21, the first set determined by the terminal device before the first PUCCH timing includes event instance 1 and event instance 2. However, the terminal device determines that the event is not satisfied based on the first set, and therefore does not send a PUCCH or a report at the first PUCCH timing.
[0298] This application does not limit the reasons why the event is not satisfied. For example, although there are event instances in the first set, the number of event instances within the time window is lower than a certain threshold, so the event is not satisfied.
[0299] According to an embodiment of this application, if no report is sent to the first set due to event non-compliance, the second set does not include event instances 1 and 2 from the first set. When the second set is determined before the second PUCCH timing, the second set only includes newly emerging event instances 3 and 4. The terminal device determines whether the event is satisfied based on event instances 3 and 4, thereby determining whether to send a PUCCH at the second PUCCH timing.
[0300] In some other embodiments, after determining the second set, the terminal device no longer sends a PUCCH or report for the first set.
[0301] For example, according to Figure 19, the terminal device has already sent a report for the first set. To avoid additional overhead and interference caused by repeatedly sending reports, the terminal device will no longer send reports for the first set.
[0302] For example, according to Figure 20, although the terminal device does not send a report for the first set, when the terminal device generates and sends a report for the second set, the report content can also include the content of the report that was previously generated for the first set but not sent. Therefore, there is no need to send a report for the first set again, thereby avoiding additional overhead and interference caused by repeatedly sending reports.
[0303] For example, according to Figure 21, the terminal device determines that the event is not satisfied based on the first set, so there is no need to send a report for the first set at any time thereafter.
[0304] In the above embodiment, it is equivalent to the first set being updated to the second set. The terminal device always maintains an event instance set, and only one event instance set can trigger PUCCH sending and report sending. Therefore, it can avoid repeatedly triggering PUCCH sending and report sending, thereby avoiding the additional overhead and interference caused by it.
[0305] In some other embodiments, the terminal device is configured to determine a first set based on the latest event instance before the first PUCCH timing, and / or, to determine a second set based on the latest event instance before the second PUCCH timing.
[0306] For example, for event 2 or event 7, an event instance is generated when the L1-RSRP of a new beam reference signal is higher than the L1-RSRP of the current beam reference signal by a first threshold. Since each new beam reference signal is a periodic reference signal, each new beam reference signal can generate one or more event instances, with the latest event instance referring to the latest event instance among one or more event instances of the same new beam reference signal.
[0307] For example, for event 1, if the L1-RSRP of the current beam reference signal is lower than the first threshold, an event instance is generated. Since the current beam reference signal is a periodic reference signal, it can generate one or more event instances. The latest event instance refers to the latest event instance among one or more event instances of the same current beam reference signal.
[0308] In the above embodiments, the terminal device can be configured to determine whether an event is satisfied based on the latest event instance (i.e., the first set or the second set only includes the latest event instance), thereby determining whether to send a PUCCH and report.
[0309] This application also provides a method for receiving reports, which is described from the perspective of a network device. The same content as in the previous embodiments will not be repeated.
[0310] Figure 22 is a schematic diagram of a report receiving method according to an embodiment of this application. As shown in Figure 22, the method includes:
[0311] 2210: Network devices receive PUCCH and PUSCH of bearer reports sent by terminal devices;
[0312] Wherein, the aforementioned PUCCH is sent by the terminal device at the PUCCH timing according to the event instance. When the terminal device is configured in the first mode, the PUSCH carrying the report is sent by the terminal device according to the DCI. When the terminal device is configured in the second mode, the PUSCH carrying the report is sent by the terminal device at the first valid PUSCH timing after the first time interval following the PUCCH timing.
[0313] Among them, the above-mentioned effective PUSCH timing satisfies at least one of the following:
[0314] When the terminal device can only send PUSCH on SBFD symbols, the valid PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with valid PRACH timing;
[0315] When the terminal device can only send PUSCH on non-SBFD symbols, the effective PUSCH timing includes uplink symbols, and / or, including non-SBFD symbols, and / or, not overlapping with SSB symbols, and / or, not overlapping with downlink symbols, and / or, not overlapping with the effective PRACH timing.
[0316] When the terminal device is able to transmit PUSCH on SBFD symbols and / or non-SBFD symbols, the effective PUSCH timing includes SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with the effective PRACH timing; or, the effective PUSCH timing includes uplink symbols, and / or includes non-SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with downlink symbols, and / or does not overlap with the effective PRACH timing.
[0317] In some embodiments, the network device may also provide the terminal device with a first PRACH configuration and a second PRACH configuration, wherein the terminal device determines the effective PRACH timing based on the first PRACH configuration, or the terminal device determines the effective PRACH timing based on the first PRACH configuration and the second PRACH configuration.
[0318] In the above embodiments, the first PRACH configuration is used to configure the PRACH timing located on non-SBFD symbols; the second PRACH configuration is used to configure the PRACH timing located on SBFD symbols, and / or the PRACH timing located on both SBFD symbols and non-SBFD symbols.
[0319] In some embodiments, the network device can also configure the terminal device, for example, configure the terminal device to determine a first set based on the latest event instance before the first PUCCH timing, and / or determine a second set based on the latest event instance before the second PUCCH timing. Furthermore, the network device can also send RRC signaling, PDCCH, PDSCH, DCI, etc. to the terminal device, or receive PUCCH, PUSCH, UCI, etc. from the terminal device; details can be found in related technologies and will not be elaborated here.
[0320] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0321] Through the embodiments of this application, on the one hand, the conditions for a valid PUSCH timing are clarified, thereby ensuring a consistent understanding between the terminal device and the network device regarding valid PUSCH timing. This avoids ambiguity regarding when to send or receive reports, thus guaranteeing the timeliness and reliability of report transmission. On the other hand, the terminal device always maintains a set of event instances and sends PUCCHs for this set of event instances, thereby avoiding excessive PUCCH sending and the resulting overhead and interference. For example, it avoids excessive PUCCH sending that would occur if multiple event instance sets were maintained simultaneously and PUCCHs were sent for each event instance set.
[0322] Fourth aspect of the embodiment
[0323] This application provides a report sending device, which may be, for example, a terminal device, or one or more parts or components configured on the terminal device.
[0324] Figure 23 is a schematic diagram of a report sending device according to an embodiment of this application. Since the principle of this device in solving the problem is similar to the report sending method of the first aspect embodiment, its specific implementation can refer to the implementation of the report sending method described in the first aspect embodiment. The same or related contents will not be repeated.
[0325] As shown in Figure 23, the report sending device 2300 includes a processing unit 2310 and a sending unit 2320, wherein,
[0326] Processing unit 2310 determines an event instance based on at least one of the first reference signal, the second reference signal, and the first threshold;
[0327] If the above event instance is not within the time window for the first reference signal or the second reference signal, the processing unit 2310 starts the time window for the first reference signal or the second reference signal;
[0328] If the first condition is met, the processing unit 2310 determines that the time window for the first reference signal or the second reference signal has ended.
[0329] If the number of event instances within the time window for the first or second reference signal is greater than or equal to the second threshold, the sending unit 2320 sends a report on the PUSCH.
[0330] In some embodiments, if a first condition is met within a time window for a first reference signal or a second reference signal, the processing unit 2310 determines that the time window has ended.
[0331] In some embodiments, satisfying the first condition includes at least one of the following:
[0332] The second reference signal has changed;
[0333] The first threshold has changed;
[0334] The second threshold has changed;
[0335] The time window length configured for RRC signaling has changed;
[0336] The count of event instances has been reset;
[0337] The first reference signal has changed;
[0338] The aforementioned report was sent;
[0339] The DCI for scheduling PUSCH is received;
[0340] The activated set of TCI states changes.
[0341] In some embodiments, the first reference signal is a new beam reference signal configured by RRC signaling; in the case that the above report is for event 2 or event 1, the second reference signal is the current beam reference signal determined according to the indicated TCI state; in the case that the above report is for event 7, the second reference signal is the current beam reference signal determined according to the activated TCI state with the highest L1-RSRP of Q.
[0342] In some embodiments, when the above report is for event 2 or event 7, if the L1-RSRP of the first reference signal is higher than the L1-RSRP of the second reference signal by a first threshold, the processing unit 2310 determines an event instance; when the above report is for event 1, if the L1-RSRP of the second reference signal is lower than the first threshold, the processing unit 2310 determines an event instance.
[0343] In some embodiments, as shown in FIG23, the device 2300 further includes a receiving unit 2330, which receives information from network devices, such as configuration information, downlink signals, etc.
[0344] Figure 24 is another schematic diagram of the report sending device according to an embodiment of this application. Since the principle of the device in solving the problem is similar to the report sending method of the second aspect embodiment, its specific implementation can refer to the implementation of the report sending method described in the second aspect embodiment. The same or related contents will not be repeated.
[0345] As shown in Figure 24, the report sending device 2400 includes a processing unit 2410 and a sending unit 2420, wherein,
[0346] The processing unit 2410 determines whether to send PUCCH at the PUCCH timing based on L first periodic reference signals and / or K second periodic reference signals, where L≥1 and K≥1;
[0347] If it is determined that PUCCH will be sent, the sending unit 2420 sends a report on PUSCH; if it is determined that PUCCH will not be sent, the sending unit 2420 does not send a report.
[0348] The aforementioned report occupies the CPU starting from a second time point, which is the first symbol of the earliest reference signal in a set of reference signals; the set of reference signals includes L first reference signals and / or K second reference signals; the l-th first reference signal is the latest reference signal among the l-th first periodic reference signals, no later than the first time point before the PUCCH timing, 1≤l≤L; the k-th second reference signal is the latest reference signal among the k-th second periodic reference signals, no later than the first time point before the PUCCH timing; or, the aforementioned report occupies the CPU starting from a third time point before the PUCCH timing, where the third time point is configured or predefined;
[0349] Wherein, L first periodic reference signals are new beam reference signals configured by RRC signaling; in the case that the above report is for event 7, K second periodic reference signals are determined according to K active TCI states, 1≤K≤8; and / or, in the case that the above report is for event 2 or event 1, K second periodic reference signals are determined according to K indicated TCI states, K=1.
[0350] In some embodiments, the above report ends CPU usage at a fourth time point, which is either the last symbol of PUSCH or the fifth time point after the PUCCH timing.
[0351] In some embodiments, as shown in FIG24, the device 2400 further includes a receiving unit 2430, which receives information from network devices, such as configuration information, downlink signals, etc.
[0352] Figure 25 is another schematic diagram of the report sending device according to an embodiment of this application. Since the principle of the device in solving the problem is similar to the report sending method of the third aspect embodiment, its specific implementation can refer to the implementation of the report sending method described in the third aspect embodiment. The same or related contents will not be repeated.
[0353] As shown in Figure 25, the report sending device 2500 includes a processing unit 2510 and a sending unit 2520, wherein,
[0354] Sending unit 2520 sends PUCCH at the PUCCH timing according to the event instance;
[0355] When the terminal device is configured in the first mode, the transmitting unit 2520 transmits the PUSCH of the bearer report according to the DCI.
[0356] When the terminal device is configured in the second mode, the sending unit 2520 sends the PUSCH of the bearer report at the first valid PUSCH timing after the first time interval following the PUCCH timing.
[0357] Among them, the above-mentioned effective PUSCH timing satisfies at least one of the following:
[0358] When the transmitting unit 2520 can only transmit PUSCH on SBFD symbols, the effective PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with effective PRACH timing.
[0359] When the transmitting unit 2520 can only transmit PUSCH on non-SBFD symbols, the effective PUSCH timing includes uplink symbols, and / or, includes non-SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with downlink symbols, and / or, does not overlap with effective PRACH timing.
[0360] When the transmitting unit 2520 is able to transmit PUSCH on SBFD symbols and / or non-SBFD symbols, the effective PUSCH timing includes SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with effective PRACH timing; or, the effective PUSCH timing includes uplink symbols, and / or includes non-SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with downlink symbols, and / or does not overlap with effective PRACH timing.
[0361] In some embodiments, when the transmitting unit 2520 can only transmit PUSCH on non-SBFD symbols, the processing unit 2510 determines the valid PRACH timing based on at least one of the following: when the terminal device is provided with a first PRACH configuration and a second PRACH configuration, the processing unit 2510 determines the valid PRACH timing based on the first PRACH configuration, or determines the valid PRACH timing based on the first PRACH configuration and the second PRACH configuration.
[0362] In the above embodiments, the first PRACH configuration is used to configure the PRACH timing located on non-SBFD symbols; the second PRACH configuration is used to configure the PRACH timing located on SBFD symbols, and / or the PRACH timing located on both SBFD symbols and non-SBFD symbols.
[0363] In some embodiments, processing unit 2510 determines a first set before a first PUCCH timing, determines whether an event is satisfied based on the first set, the first set including event instances prior to the first PUCCH timing; and / or, processing unit 2510 determines a second set before a second PUCCH timing, determines whether an event is satisfied based on the second set, the second set including event instances prior to the second PUCCH timing, the second PUCCH timing being later than the first PUCCH timing; if the event is satisfied, sending unit 2520 sends a PUCCH at either the first PUCCH timing or the second PUCCH timing.
[0364] In the above embodiments, optionally, if the sending unit 2520 sends a report between the first PUCCH timing and the second PUCCH timing, the second set does not include the first set.
[0365] In the above embodiments, optionally, if the sending unit 2520 does not send a report between the first PUCCH timing and the second PUCCH timing, the second set may or may not include the first set.
[0366] In the above embodiments, optionally, if the processing unit 2510 determines that the event is satisfied according to the first set, the second set includes the first set; and / or, if the processing unit 2510 determines that the event is not satisfied according to the first set, the second set does not include the first set.
[0367] In the above embodiments, optionally, after the processing unit 2510 determines the second set, the sending unit 2520 no longer sends PUCCH or reports for the first set.
[0368] In the above embodiments, optionally, the processing unit 2510 is configured to determine a first set based on the latest event instance before the first PUCCH timing, and / or to determine a second set based on the latest event instance before the second PUCCH timing.
[0369] In some embodiments, as shown in FIG25, the device 2500 further includes a receiving unit 2530, which receives information from network devices, such as configuration information, downlink signals, etc.
[0370] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The report transmitting devices 2300, 2400, and 2500 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.
[0371] Furthermore, for simplicity, Figures 23 to 25 only exemplarily illustrate the connection relationships or signal flows between the various components or modules. However, those skilled in the art should understand that various related technologies, such as bus connections, can be employed. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.
[0372] Through the embodiments of this application, on the one hand, the terminal device determines whether the time window has ended based on a first condition. This allows the time window to be promptly activated when events need to be re-detected, thus avoiding missed events and ensuring timely reporting, providing continuous assurance for high-performance and highly reliable transmission. On the other hand, it clarifies the time point from which the reports sent by the terminal device begin occupying the CPU. This ensures that the terminal device and network device have a consistent understanding of the start and end points of CPU usage for the reports, avoiding ambiguity regarding CPU usage time. The network device can then configure reports appropriately based on the terminal device's CPU usage. Furthermore, it clarifies the conditions for a valid PUSCH timing. This ensures that the terminal device and network device have a consistent understanding of a valid PUSCH timing, avoiding ambiguity regarding when to send or receive reports, thus guaranteeing the timeliness and reliability of report transmission. Finally, the terminal device always maintains a set of event instances and sends PUCCHs to this set of event instances, thereby avoiding excessive PUCCH sending and the resulting overhead and interference. For example, excessive PUCCH sending can be avoided when maintaining multiple event instance sets simultaneously and sending PUCCH to each event instance set.
[0373] Fifth aspect of the embodiment
[0374] This application provides a report receiving device, which may be, for example, a network device, or one or more parts or components configured in a network device.
[0375] Figure 26 is a schematic diagram of a report receiving device according to an embodiment of this application. Since the principle of this device in solving the problem is similar to the report receiving method of the first aspect embodiment, its specific implementation can refer to the implementation of the report receiving method described in the first aspect embodiment. The same or related contents will not be repeated.
[0376] As shown in Figure 26, the report receiving device 2600 includes a sending unit 2610 and a receiving unit 2620, wherein the sending unit 2610 sends a first reference signal and / or a second reference signal to the terminal device; and the receiving unit 2620 receives the report sent by the terminal device.
[0377] In some embodiments, the sending unit 2610 can also send configuration information to the terminal device to perform relevant configurations for the terminal device, such as configuring the length of the aforementioned time window, the first threshold, the second threshold, etc. In addition, the sending unit 2610 can also send RRC signaling, PDCCH, PDSCH, DCI, etc. to the terminal device, and the receiving unit 2620 can also receive PUCCH, PUSCH, UCI, etc. from the terminal device. For details, please refer to the relevant technology, which will not be elaborated here.
[0378] In some embodiments, as shown in FIG26, the device 2600 further includes a processing unit 2630, which controls the transmitting unit 2610 and the receiving unit 2620.
[0379] Figure 27 is another schematic diagram of a report receiving device according to an embodiment of this application. Since the principle of this device in solving the problem is similar to the report receiving method of the second aspect embodiment, its specific implementation can refer to the implementation of the report receiving method described in the second aspect embodiment. The same or related contents will not be repeated.
[0380] As shown in Figure 27, the report receiving device 2700 includes a sending unit 2710 and a receiving unit 2720, wherein the sending unit sends a first periodic reference signal and / or a second periodic reference signal to the terminal device; and the receiving unit 2720 receives the report sent by the terminal device.
[0381] The aforementioned report occupies the CPU starting from a second time point, which is the first symbol of the earliest reference signal in a set of reference signals; the set of reference signals includes L first reference signals and / or K second reference signals; the l-th first reference signal is the latest reference signal among the l-th first periodic reference signals, no later than the first time point before the PUCCH timing, 1≤l≤L; the k-th second reference signal is the latest reference signal among the k-th second periodic reference signals, no later than the first time point before the PUCCH timing; or, the aforementioned report occupies the CPU starting from a third time point before the PUCCH timing, where the third time point is configured or predefined;
[0382] Wherein, L first periodic reference signals are new beam reference signals configured by RRC signaling; in the case that the above report is for event 7, K second periodic reference signals are determined according to K active TCI states, 1≤K≤8; and / or, in the case that the above report is for event 2 or event 1, K second periodic reference signals are determined according to K indicated TCI states, K=1.
[0383] In some embodiments, the above report ends CPU usage at a fourth time point, which is either the last symbol of PUSCH or the fifth time point after the PUCCH timing.
[0384] In some embodiments, the sending unit 2710 may also send configuration information to the terminal device to perform relevant configurations for the terminal device, such as configuring the aforementioned third time point. The sending unit 2710 may also send RRC signaling, PDCCH, PDSCH, DCI, etc. to the terminal device. The receiving unit 2720 may also receive PUCCH, PUSCH, UCI, etc. from the terminal device. For details, please refer to the relevant technologies, which will not be elaborated here.
[0385] In some embodiments, as shown in FIG27, the device 2700 further includes a processing unit 2730, which controls the transmitting unit 2710 and the receiving unit 2720.
[0386] Figure 28 is a schematic diagram of a report receiving device according to an embodiment of this application. Since the principle of this device in solving the problem is similar to the report receiving method of the third aspect embodiment, its specific implementation can refer to the implementation of the report receiving method described in the third aspect embodiment. The same or related contents will not be repeated.
[0387] As shown in Figure 28, the receiving device 2800 for this report includes a sending unit 2810 and a receiving unit 2820, wherein the receiving unit 2820 receives the PUCCH and the PUSCH carrying the report sent by the terminal device.
[0388] Wherein, the aforementioned PUCCH is sent by the terminal device at the PUCCH timing according to the event instance. When the terminal device is configured in the first mode, the PUSCH carrying the report is sent by the terminal device according to the DCI. When the terminal device is configured in the second mode, the PUSCH carrying the report is sent by the terminal device at the first valid PUSCH timing after the first time interval following the PUCCH timing.
[0389] Among them, the above-mentioned effective PUSCH timing satisfies at least one of the following:
[0390] When the terminal device can only send PUSCH on SBFD symbols, the valid PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with valid PRACH timing;
[0391] When the terminal device can only send PUSCH on non-SBFD symbols, the effective PUSCH timing includes uplink symbols, and / or, including non-SBFD symbols, and / or, not overlapping with SSB symbols, and / or, not overlapping with downlink symbols, and / or, not overlapping with the effective PRACH timing.
[0392] When the terminal device is able to transmit PUSCH on SBFD symbols and / or non-SBFD symbols, the effective PUSCH timing includes SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with the effective PRACH timing; or, the effective PUSCH timing includes uplink symbols, and / or includes non-SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with downlink symbols, and / or does not overlap with the effective PRACH timing.
[0393] In some embodiments, the sending unit 2810 may also send first configuration information to the terminal device to provide the terminal device with a first PRACH configuration and a second PRACH configuration. The terminal device determines the effective PRACH timing based on the first PRACH configuration, or the terminal device determines the effective PRACH timing based on the first PRACH configuration and the second PRACH configuration.
[0394] In the above embodiments, the first PRACH configuration is used to configure the PRACH timing located on non-SBFD symbols; the second PRACH configuration is used to configure the PRACH timing located on SBFD symbols, and / or the PRACH timing located on both SBFD symbols and non-SBFD symbols.
[0395] In some embodiments, the sending unit 2810 may also send second configuration information to the terminal device to perform relevant configurations for the terminal device, such as configuring the terminal device to determine a first set based on the latest event instance before the first PUCCH timing, and / or to determine a second set based on the latest event instance before the second PUCCH timing. Furthermore, the sending unit 2810 may also send RRC signaling, PDCCH, PDSCH, DCI, etc., to the terminal device, and the receiving unit 2820 may also receive PUCCH, PUSCH, UCI, etc., from the terminal device; details can be found in related technologies and will not be elaborated here.
[0396] In some embodiments, as shown in FIG28, the device 2800 further includes a processing unit 2830, which controls the transmitting unit 2810 and the receiving unit 2820.
[0397] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The receiving devices 2600, 2700, and 2800 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.
[0398] Furthermore, for simplicity, Figures 26 to 28 only illustrate the connection relationships or signal flows between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.
[0399] The present application embodiments solve the aforementioned problems mentioned in the foregoing embodiments by means of information interaction between network devices and terminal devices.
[0400] Implementation of the sixth aspect
[0401] This application also provides a communication system, which can be referred to FIG1. The contents that are the same as those in the embodiments of the first to fifth aspects will not be repeated.
[0402] In some embodiments, the communication system 100 may include at least: terminal device 102 or 103 and / or network device 101. Terminal device 102 / 103 may perform the report sending method described in any of the embodiments of the first to third aspects, including the report sending apparatus described in the embodiments of the fourth aspect; network device 101 may perform the report receiving method described in any of the embodiments of the first to third aspects, including the report receiving apparatus described in the embodiments of the fifth aspect, which will not be elaborated further here.
[0403] This application also provides a terminal device, but the application is not limited to this and may also include other devices.
[0404] Figure 29 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 29, the terminal device 2900 may include a processor 2910 and a memory 2920; the memory 2920 stores data and programs and is coupled to the processor 2910. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.
[0405] For example, processor 2910 can be configured to execute a program to implement the report sending method as described in the embodiments of the first to third aspects.
[0406] As shown in Figure 29, the terminal device 2900 may further include: a communication module 2930, an input unit 2940, a display 2950, and a power supply 2960. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the terminal device 2900 does not necessarily include all the components shown in Figure 29; these components are not essential. Furthermore, the terminal device 2900 may also include components not shown in Figure 29, which can be referred to in the prior art.
[0407] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.
[0408] Figure 30 is a schematic diagram of the configuration of a network device according to an embodiment of this application. As shown in Figure 30, the network device 3000 may include: a processor 3010 (e.g., a central processing unit CPU) and a memory 3020; the memory 3020 is coupled to the processor 3010. The memory 3020 can store various types of data; in addition, it also stores an information processing program 3030, and executes the program 3030 under the control of the processor 3010.
[0409] For example, processor 3010 may be configured to execute a program to implement the report receiving method as described in the embodiments of the first, second, or third aspects.
[0410] In addition, as shown in Figure 30, the network device 3000 may also include a transceiver 3040 and an antenna 3050, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that the network device 3000 does not necessarily need to include all the components shown in Figure 30; furthermore, the network device 3000 may also include components not shown in Figure 30, which can be referred to in the prior art.
[0411] This application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the report sending method described in the first to third embodiments.
[0412] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to execute the report sending method described in the first to third embodiments.
[0413] This application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to perform the report receiving method described in the first to third aspects of the embodiments.
[0414] This application also provides a storage medium storing a computer program, wherein the computer program causes a network device to perform the report receiving method described in the first to third embodiments.
[0415] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.
[0416] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.
[0417] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.
[0418] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.
[0419] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.
[0420] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:
[0421] 1. A method for transmitting uplink data, applied to a terminal device, wherein the method includes:
[0422] The terminal device determines a first set before the first PUCCH timing, and determines whether an event is satisfied based on the first set, wherein the first set includes event instances prior to the first PUCCH timing; and / or,
[0423] The terminal device determines a second set before the second PUCCH timing, and determines whether the event is satisfied based on the second set. The second set includes event instances before the second PUCCH timing, and the second PUCCH timing is later than the first PUCCH timing in time.
[0424] If the event is satisfied, the terminal device sends a PUCCH at the first PUCCH timing or the second PUCCH timing.
[0425] 2. According to the method described in Appendix 1, wherein,
[0426] If the terminal device sends a report between the first PUCCH timing and the second PUCCH timing, the second set does not include the first set.
[0427] 3. According to the method described in Appendix 1, wherein,
[0428] If the terminal device does not send a report between the first PUCCH timing and the second PUCCH timing, the second set may or may not include the first set.
[0429] 4. According to the method described in Appendix 3, wherein,
[0430] If the terminal device determines that an event is satisfied based on the first set, the second set includes the first set; and / or,
[0431] If the terminal device determines that the event is not satisfied based on the first set, the second set does not include the first set.
[0432] 5. According to the method described in Appendix 1, wherein,
[0433] After determining the second set, the terminal device no longer sends PUCCH or reports for the first set.
[0434] 6. The method according to Appendix 1, wherein the method further comprises:
[0435] The terminal device is configured to determine the first set based on the latest event instance before the first PUCCH timing, and / or to determine the second set based on the latest event instance before the second PUCCH timing.
[0436] 7. A mapping method, wherein the method comprises:
[0437] When the PDSCH is located on the SBFD symbol, the terminal device maps the PDSCH PT-RS to the RE, wherein the RE is located within the downlink subband and within the active downlink BWP.
[0438] 8. A mapping method, wherein the method comprises:
[0439] When the PUSCH is located on the SBFD symbol, the terminal device maps the PUSCH PT-RS to the RE, wherein the RE is located within the uplink subband and within the active uplink BWP.
[0440] 9. A terminal device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in any one of Appendices 1 to 8.
[0441] 10. A communication system having terminal equipment and network equipment as described in Appendix 9.
Claims
1. A report transmitting device, configured in a terminal device, wherein, The device includes a processing unit and a transmitting unit, wherein... The processing unit determines the event instance based on at least one of the first reference signal, the second reference signal, and the first threshold; If the event instance is not within the time window for the first reference signal or the second reference signal, the processing unit activates the time window for the first reference signal or the second reference signal; If the first condition is met, the processing unit determines that the time window for the first reference signal or the second reference signal has ended; If the number of event instances within the time window for the first reference signal or the second reference signal is greater than or equal to the second threshold, the sending unit sends a report on the PUSCH.
2. The apparatus according to claim 1, wherein, The first condition being met includes at least one of the following: The second reference signal changes; The first threshold changes; The second threshold changes; The time window length configured for RRC signaling has changed; The count of event instances has been reset; The first reference signal changes; The report was sent; The DCI for scheduling the PUSCH is received; The activated set of TCI states changes.
3. The apparatus according to claim 1, wherein, The first reference signal is a new beam reference signal configured by RRC signaling; In the case of a report concerning event 2 or event 1, the second reference signal is the current beam reference signal determined according to the indicated TCI state; in the case of a report concerning event 7, the second reference signal is the current beam reference signal determined according to the active TCI state with the highest Q-order L1-RSRP.
4. The apparatus according to claim 1, wherein, In the case where the report is for event 2 or event 7, if the L1-RSRP of the first reference signal is higher than the first threshold than the L1-RSRP of the second reference signal, the processing unit determines the event instance; In the case where the report is for event 1, if the L1-RSRP of the second reference signal is lower than the first threshold, the processing unit determines the event instance.
5. A report transmitting device, configured in a terminal device, wherein, The device includes a processing unit and a transmitting unit, wherein... The processing unit determines whether to send PUCCH at the PUCCH timing based on L first periodic reference signals and / or K second periodic reference signals, where L≥1 and K≥1. If it is determined that the PUCCH will be sent, the sending unit sends a report on the PUSCH; if it is determined that the PUCCH will not be sent, the sending unit does not send a report. The report occupies the CPU starting from a second time point, which is the first symbol of the earliest reference signal in a set of reference signals; the set of reference signals includes L first reference signals and / or K second reference signals; the l-th first reference signal is the latest reference signal in the l-th first periodic reference signal that is no later than the first time point before the PUCCH timing, 1≤l≤L; the k-th second reference signal is the latest reference signal in the k-th second periodic reference signal that is no later than the first time point before the PUCCH timing; or, the report occupies the CPU starting from a third time point before the PUCCH timing, where the third time point is configured or predefined. Wherein, the L first periodic reference signals are new beam reference signals configured by RRC signaling; when the report is for event 7, the K second periodic reference signals are determined according to K active TCI states, 1≤K≤8; and / or, when the report is for event 2 or event 1, the K second periodic reference signals are determined according to K indicated TCI states, K=1.
6. The apparatus according to claim 5, wherein, The report ends CPU usage at a fourth time point, which is either the last symbol of the PUSCH or the fifth time point after the PUCCH timing.
7. A report transmitting device, configured in a terminal device, wherein, The device includes a transmitting unit, wherein... The sending unit sends a PUCCH at the PUCCH timing according to the event instance; When the terminal device is configured in the first mode, the sending unit sends the PUSCH of the bearer report according to the DCI; When the terminal device is configured in the second mode, the sending unit sends the PUSCH of the bearer report at the first valid PUSCH timing after the first time interval following the PUCCH timing; Wherein, the effective PUSCH timing satisfies at least one of the following: When the transmitting unit can only transmit the PUSCH on SBFD symbols, the valid PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with valid PRACH timing; When the transmitting unit can only transmit the PUSCH on non-SBFD symbols, the valid PUSCH timing includes uplink symbols, and / or includes non-SBFD symbols, and / or does not overlap with SSB symbols, and / or does not overlap with downlink symbols, and / or does not overlap with valid PRACH timing. When the transmitting unit is capable of transmitting the PUSCH on SBFD symbols and / or non-SBFD symbols, the effective PUSCH timing includes SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with effective PRACH timing; or, the effective PUSCH timing includes uplink symbols, and / or, includes non-SBFD symbols, and / or, does not overlap with SSB symbols, and / or, does not overlap with downlink symbols, and / or, does not overlap with effective PRACH timing.
8. The apparatus according to claim 7, wherein, The device further includes: In the case where the transmitting unit can only transmit the PUSCH on non-SBFD symbols, the processing unit determines the valid PRACH timing based on at least one of the following: When the terminal device is provided with a first PRACH configuration and a second PRACH configuration, the terminal device determines the effective PRACH timing according to the first PRACH configuration, or the terminal device determines the effective PRACH timing according to the first PRACH configuration and the second PRACH configuration.
9. The apparatus according to claim 8, wherein, The first PRACH configuration is used to configure PRACH timings located on non-SBFD symbols; the second PRACH configuration is used to configure PRACH timings located on SBFD symbols, and / or PRACH timings located on both SBFD symbols and non-SBFD symbols.
10. The apparatus according to claim 7, wherein, The device further includes: A processing unit that determines a first set before a first PUCCH timing, determines whether an event is satisfied based on the first set, the first set including event instances prior to the first PUCCH timing; and / or determines a second set before a second PUCCH timing, determines whether an event is satisfied based on the second set, the second set including event instances prior to the second PUCCH timing, the second PUCCH timing being later in time than the first PUCCH timing. If the event is satisfied, the sending unit sends a PUCCH at the first PUCCH timing or the second PUCCH timing.
11. The apparatus according to claim 10, wherein, If the sending unit sends a report between the first PUCCH timing and the second PUCCH timing, the second set does not include the first set.
12. The apparatus according to claim 10, wherein, If the sending unit does not send a report between the first PUCCH timing and the second PUCCH timing, the second set may or may not include the first set.
13. The apparatus according to claim 12, wherein, If the processing unit determines that an event is satisfied based on the first set, the second set includes the first set; and / or, If the processing unit determines that the event is not satisfied based on the first set, the second set does not include the first set.
14. The apparatus according to claim 10, wherein, After determining the second set, the sending unit no longer sends PUCCH or reports for the first set.
15. The apparatus according to claim 10, wherein, The processing unit is configured to determine the first set based on the latest event instance before the first PUCCH timing, and / or to determine the second set based on the latest event instance before the second PUCCH timing.
