Method and apparatus for sending or receiving information, and communication system

Abstract

Embodiments of the present application provide a method and apparatus for sending or receiving information, and a communication system. The apparatus for sending information is applied to a terminal device, and comprises a first processing unit. The first processing unit enables the terminal device to perform the following operations: upon detecting the occurrence of an event, the terminal device sending first information; and sending a channel state information (CSI) report on a scheduled or pre-configured resource, wherein when the first information overlaps in the time domain with a first physical uplink shared channel (PUSCH) having an uplink shared channel (UL-SCH), the terminal device sends the first PUSCH and the first information, and the first information is multiplexed onto the first PUSCH for transmission.

Description

Method, device and communication system for sending or receiving information Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] 5G NR supports Channel State Information (CSI) reporting. For example, a CSI report can 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 and Noise Ratio (L1-SINR), i.e., it includes beam-related reporting. The terminal device sends a beam report to the network device, which can perform beam management based on the report, for example, indicating a better beam for the terminal device.

[0003] The network device determines when a terminal device sends a CSI report. The network device can configure periodic CSI reporting, which causes the terminal device to send CSI reports periodically. It can also configure semi-persistent CSI reporting, which causes the terminal device to send CSI reports periodically after being activated by the network device. It can also configure aperiodic CSI reporting, which causes the terminal device to send a single CSI report after being triggered by the network device. CSI reports include measurement results for the serving cell.

[0004] Release 17 (Rel-17) adds support for Inter Cell Beam Management (ICBM). In ICBM, CSI reports can include measurement results for non-serving cells, so that the network equipment can instruct the terminal device to use the beam of the non-serving cell, but the terminal device does not switch to the non-serving cell.

[0005] Rel-18 adds support for LTM CSI reporting. Rel-18 supports Layer 1 / Layer 2 Triggered Mobility (L1 / L2 Triggered Mobility, LTM). In LTM, the terminal device can send LTM CSI reports. The LTM CSI report of Rel-18 includes SSBRI and L1-RSRP. Unlike the traditional CSI report mentioned above, the LTM CSI report includes the measurement results for the candidate cell. The network device can determine the beam to be used in the candidate cell for the terminal device based on this, and indicate the beam to the terminal device before switching to the candidate cell, so that the terminal device can quickly apply the appropriate beam for data transmission after switching. In other words, in LTM, the terminal device switches to the candidate cell and uses the beam of the candidate cell after switching. Similarly, the terminal device can send LTM CSI reports in a periodic, semi-continuous, or non-periodic manner.

[0006] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0007] Summary of the Invention

[0008] The upcoming Rel-19 release will introduce event-triggered reporting. More specifically, further enhancements will be introduced to CSI and LTM CSI reporting, supporting event-triggered CSI and LTM CSI reporting. These reporting methods correspond to traditional CSI and LTM CSI reporting, respectively. For simplicity, the term "event-triggered CSI reporting" will be used to refer to both types of reporting methods.

[0009] Unlike traditional reporting, event-triggered reporting determines when a terminal device sends a report. This is triggered by an event. In other words, the terminal device only sends reports when necessary, resulting in more timely reporting. Furthermore, by avoiding unnecessary reports, reporting overhead is reduced.

[0010] The terminal device needs to send an event-triggered CSI report on certain time-frequency resources. The determination of resources requires corresponding information interaction. For example, the terminal device sends a first information request to dynamically schedule resources or to notify whether semi-statically configured resources are actually used.

[0011] The inventors of this application discovered that for a terminal device, the first information may overlap with other uplink information in the time domain (i.e., collide). When the first information overlaps with other uplink information in the time domain, how the terminal device should handle it, including which information should be sent, are problems that need to be solved.

[0012] In response to at least one of the above problems or other similar problems, embodiments of the present application provide a method, device, and communication system for sending or receiving information.

[0013] According to one aspect of an embodiment of the present application, a device for sending information is provided, which is applied to a terminal device. The device includes a first processing unit, which causes the terminal device to perform the following operations:

[0014] The terminal device sends first information when detecting that an event occurs; and

[0015] Sending channel state information (CSI) reports on scheduled or pre-configured resources,

[0016] When the first information overlaps with the first physical uplink shared channel (PUSCH) with an uplink shared channel (UL-SCH) in the time domain, the terminal device sends the first physical uplink shared channel (PUSCH) and the first information, wherein the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent.

[0017] According to another aspect of an embodiment of the present application, a device for receiving information is provided, which is applied to a network device. The device includes a second processing unit, which causes the network device to perform the following operations:

[0018] receiving first information sent by the terminal device when an event is detected; and

[0019] receiving channel state information (CSI) reports on scheduled or pre-configured resources,

[0020] When the first information overlaps with the first physical uplink shared channel (PUSCH) with an uplink shared channel (UL-SCH) in the time domain, the first physical uplink shared channel (PUSCH) and the first information sent by the terminal device are received, wherein the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent.

[0021] One of the beneficial effects of the embodiments of the present application is that it provides a processing method when the first information sent during the event-triggered CSI reporting process overlaps with other uplink information in the time domain (i.e., a collision occurs). This can avoid ambiguity between the terminal device and the network device on which information to send when a collision occurs, and avoid the terminal device missing the opportunity to send an event-triggered report.

[0022] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0023] Features described and / or illustrated with respect to 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.

[0024] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0026] FIG1 is a schematic diagram of a communication system of the present application;

[0027] FIG2 is a schematic diagram of a first method of event-triggered CSI reporting;

[0028] FIG3 is a schematic diagram of a second method of event-triggered CSI reporting;

[0029] FIG4 is a schematic diagram of a third method of event-triggered CSI reporting;

[0030] FIG5 is a schematic diagram of a method for sending information according to an embodiment of the first aspect;

[0031] FIG6 is a schematic diagram of first information being multiplexed onto a first physical uplink shared channel for transmission;

[0032] FIG7 is a schematic diagram showing that the first information and other UCI are multiplexed onto the first PUSCH;

[0033] FIG8 is a schematic diagram of the overlap of the first information and the second PUSCH;

[0034] FIG9 is a schematic diagram of a method for receiving information according to an embodiment of the second aspect;

[0035] FIG10 is a schematic diagram of an apparatus for sending information in an embodiment of the third aspect;

[0036] FIG11 is a schematic diagram of an apparatus for receiving information in an embodiment of the fourth aspect;

[0037] FIG12 is a schematic diagram of an electronic device according to an embodiment of the fifth aspect. DETAILED DESCRIPTION

[0038] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0039] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0040] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0041] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as New Radio (NR), Long Term Evolution (LTE), Enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0042] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, 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), etc., and / or other communication protocols currently known or to be developed in the future.

[0043] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device. Network devices may include, but are not limited to, the following devices: an integrated access and backhaul node (IAB-node), a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), and the like.

[0044] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0045] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0046] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0047] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0048] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as mentioned above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as mentioned above.

[0049] In the following description, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" are interchangeable, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" are interchangeable to avoid confusion.

[0050] The terms "downlink control signal" and "downlink control information (DCI)" or "physical downlink control channel (PDCCH)" are interchangeable, and the terms "downlink data signal" and "downlink data information" or "physical downlink shared channel (PDSCH)" are interchangeable.

[0051] In addition, sending or receiving PUSCH can be understood as sending or receiving uplink data carried by PUSCH, sending or receiving PUCCH can be understood as sending or receiving uplink information carried by PUCCH, and sending or receiving PRACH can be understood as sending or receiving preamble carried by PRACH; uplink signals can include uplink data signals and / or uplink control signals, etc., and can also be referred to as uplink transmission (UL transmission) or uplink information or uplink channels. Sending uplink transmission on uplink resources can be understood as sending the uplink transmission using the uplink resources. Similarly, downlink data / signals / channels / information can be understood accordingly.

[0052] In the embodiments of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, MIB, system information, or a dedicated RRC message; or an RRC information element (RRC IE). The high-layer signaling may also be, for example, MAC (Medium Access Control) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto.

[0053] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0054] Figure 1 is a schematic diagram of the communication system of the present application, which schematically illustrates a situation taking a terminal device and a network device as an example. As shown in Figure 1, the communication system 100 may include a network device 101 and a terminal device 102 (for simplicity, Figure 1 only illustrates one terminal device as an example).

[0055] In the embodiment of the present application, existing services or future services can be carried out between the network device 101 and the terminal device 102. For example, these services include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0056] Among them, the terminal device 102 can send data to the network device 101, for example, using authorization (for example, a configured authorization, i.e., a configured grant) or an authorization-free transmission mode. In the authorization mode, the network device 101 can receive data sent by one or more terminal devices 102 in the authorization, and feedback information to the terminal device 102, such as confirmation ACK / non-confirmation NACK information, etc., or indicate a new authorization to the terminal device 102. The terminal device 102 can confirm the end of the transmission process based on the feedback information or the new authorization, or can also perform new data transmission, or can retransmit the data. For the authorization-free transmission mode, the terminal device can transmit new data on the configured authorization, or can retransmit.

[0057] Embodiments of the first aspect

[0058] FIG2 is a schematic diagram of a first method of event-triggered CSI reporting.

[0059] As shown in Figure 2, the first resource used to send the first information is a pre-configured (RRC signaling configured) periodic physical uplink control channel (PUCCH) resource (only one period is shown), and the second resource used to send the CSI report is a resource scheduled by the uplink DCI (downlink control information). The terminal device measures one or more reference signals (RS1 to RS4), and after detecting the occurrence of an event that triggers the CSI report, it requests the network device to send the resources required for the CSI report (i.e., request the second resource) by sending the first information, and then receives the uplink DCI and sends the CSI report on the second resource scheduled by the uplink DCI. The CSI report is carried by UCI (uplink control information), and the UCI is multiplexed and transmitted in the physical uplink shared channel (PUSCH) scheduled by the uplink DCI. Not shown in the figure, the uplink DCI can also schedule PUCCH, so that the UCI is sent through PUCCH. The CSI report can be carried by PUSCH or PUCCH, and the first information is carried by PUCCH. The resources here refer to time-frequency resources.

[0060] There are no restrictions on the events that trigger CSI reporting. For example, the event may be that the measurement result (L1-RSRP) of a new beam (one of RS1 to RS4) is higher than the measurement result of the current beam by a certain value, or that the measurement result of the current beam is lower than a certain value. There are no restrictions on the content of the CSI report. For example, the CSI report includes a reference signal index and an L1-RSRP measured based on the reference signal. The CSI report may include one or more reference signal indices and L1-RSRPs. The CSI report is used to report beam information. Its purpose is to report the beam and the measurement results for the beam. The CSI report may also be replaced by a beam report.

[0061] Figure 3 is a schematic diagram of the second method of event-triggered CSI reporting. The difference between Figure 3 and Figure 2 is that the CSI report is carried by MAC-CE, which is carried in the PUSCH scheduled by uplink DCI.

[0062] FIG4 is a schematic diagram of a third method of event-triggered CSI reporting.

[0063] As shown in Figure 4, the first resource used to send the first information is a preconfigured periodic PUCCH resource (only one period is shown), and the second resource used to send the CSI report is a preconfigured periodic resource (only one period is shown). The first resource and the second resource are associated with each other, for example, one first resource is associated with one second resource. The terminal device measures one or more reference signals (RS1 to RS4), and after detecting the occurrence of an event that triggers a CSI report, it notifies the network device by sending the first information that there is a CSI report transmission on the second resource associated with the first information (first resource), and thus does not need to receive uplink DCI, and can directly send the CSI report on the associated second resource. On the contrary, if the terminal device does not detect the occurrence of the event, the terminal device may not send the first information, in this way notifying the network device that there is no CSI report transmission on the second resource associated with the first information, so that the network device can schedule other terminal devices for transmission on the second resource, thereby avoiding the waste of the second resource pre-configured in a semi-static manner. Without loss of generality, if the terminal device does not detect the occurrence of an event, the terminal device may also send a first message, but the content of the first message is different from the previous one. At this time, the first message notifies the network device that there is no CSI report transmission on the second resource associated with the first information.

[0064] Event-triggered CSI reporting can be implemented using the three methods mentioned above. Regardless of which method is used, the terminal device needs to send the first information via the PUCCH. The terminal device may need to send other uplink information. When the first information and other uplink information overlap in the time domain, how the terminal device should handle it, including which information to send, are issues that need to be addressed.

[0065] In order to solve the above problems or at least similar problems, an embodiment of the first aspect of the present application provides a method for sending information, which is applied to a terminal device, for example, the terminal device 102 in Figure 1.

[0066] FIG5 is a schematic diagram of a method for sending information according to an embodiment of the first aspect. As shown in FIG5 , the method for sending information includes:

[0067] 501. The terminal device sends first information when detecting that an event occurs; and

[0068] 502. Send a channel state information (CSI) report on scheduled or pre-configured resources.

[0069] In operation 501, when the first information overlaps with a first physical uplink shared channel (PUSCH) having an uplink shared channel (UL-SCH) in the time domain, the terminal device sends the first physical uplink shared channel (PUSCH) and the first information, wherein the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent.

[0070] For example, the first message is a dedicated SR for CSI reporting (dedicated SR). The terminal device requests the resources required for CSI report transmission by sending the SR. The terminal device is provided with a separate SR configuration that is specifically used for event-triggered CSI reporting and is not used to request resources required for uplink service data transmission.

[0071] The traditional SR is used to request the resources required for uplink data transmission. When the traditional SR overlaps with the first PUSCH with UL-SCH (PUSCH with UL-SCH) in the time domain, according to the existing standard, the terminal device sends the first PUSCH and does not send the SR. This is because by scheduling and sending the first PUSCH with UL-SCH, the network device already knows that the terminal device is willing to send uplink data, and the purpose of the traditional SR has been achieved, so there is no need to send the traditional SR. In other words, if uplink data has already been scheduled, there is no need for the terminal device to send a traditional SR to request uplink data scheduling.

[0072] However, unlike the traditional SR, in this application, the dedicated SR here is to request the sending of the CSI report (or to notify the existence of the CSI report on the second resource). If only the first PUSCH is sent and the dedicated SR is not sent, the network device can know from the first PUSCH that the terminal device has the intention to request the sending of uplink data, but cannot know that the terminal device has the intention to request the sending of the CSI report (or does not know to receive the CSI report on the second resource), and thus will not send the uplink DCI scheduling terminal device to send the CSI report (or will not receive the CSI report on the second resource), so that the terminal device misses the opportunity to send the CSI report and cannot notify the network device of the beam change in a timely manner.

[0073] Figure 6 is a schematic diagram of first information being multiplexed onto a first physical uplink shared channel (PUSCH) for transmission. As shown in Figure 6, when a dedicated SR carrying the first information overlaps with a PUSCH (first PUSCH) with a UL-SCH in the time domain, the terminal device transmits the PUSCH multiplexed with the dedicated SR.

[0074] For another example, the first information is carried by a PUCCH dedicated to CSI reporting. If the first information includes only one bit, as mentioned above, the first information can be carried by a dedicated SR. Since SR is essentially a type of PUCCH, "the first information is SR" is also equivalent to "the first information is single-bit information carried by PUCCH". When the first information includes multiple bits, the terminal device is provided with a separate PUCCH configuration specifically for the transmission of the first information. By using multi-bit information, in addition to indicating a request for a second resource or the presence of a CSI report on the second resource, the first information can also indicate additional information, for example, the number of bits reported by the CSI. Since the first information is carried by PUCCH, the first information is also a type of UCI. When the dedicated PUCCH carrying the first information overlaps with the PUSCH with UL-SCH in the time domain, the terminal device sends a PUSCH with the first information (UCI) multiplexed.

[0075] In some embodiments, the first information is multiplexed onto a first physical uplink shared channel (PUSCH) and sent, including:

[0076] The first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a rate matching manner and sent.

[0077] For example, when the first information is multiplexed onto the first PUSCH as UCI, UCI multiplexing can be performed using a puncturing method or a rate matching method. In the puncturing method, the resource element (RE) carrying the first information directly replaces the mapped PUSCH RE at the corresponding position. In the rate matching method, the PUSCH is mapped to the REs that avoid the REs carrying the first information.

[0078] As shown in FIG5 , the method further includes:

[0079] 503. At least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) is multiplexed onto the first physical uplink shared channel (PUSCH) and sent.

[0080] For example, the first PUSCH with UL-SCH may overlap with the first information in the time domain and may also overlap with other types of UCI (PUCCH) in the time domain. Therefore, the first information and other UCI can be multiplexed on the first PUSCH.

[0081] Figure 7 is a schematic diagram illustrating that first information and other UCI are multiplexed onto the first PUSCH. As shown in Figure 7, the first information and other UCI are multiplexed onto the first PUSCH. The other UCI includes at least one of HARQ-ACK, CSI Part 1, and CSI Part 2. For example, in some cases, the first information, HARQ-ACK, CSI Part 1, and CSI Part 2 are all multiplexed onto the first PUSCH.

[0082] In some embodiments of the present application, when the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain:

[0083] If the second physical uplink shared channel (PUSCH) carries a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, the terminal device sends the second physical uplink shared channel (PUSCH) and does not send the first information; and / or,

[0084] If the second physical uplink shared channel (PUSCH) does not carry a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, the terminal device does not send the second physical uplink shared channel (PUSCH) but sends the first information.

[0085] Figure 8 is a schematic diagram of the overlap of the first information and the second PUSCH. As shown in Figure 8 (a), when the second PUSCH carries HARQ-ACK, the second PUSCH is sent; as shown in Figure 8 (b), when the second PUSCH does not carry HARQ-ACK, the first information is sent.

[0086] For example, the first information is a dedicated SR. For the second PUSCH without an uplink shared channel, it mainly carries HARQ-ACK and / or CSI. When the traditional SR overlaps with the second PUSCH in the time domain, according to the existing standard, the terminal device sends the traditional SR and does not send the second PUSCH, that is, it is considered that the traditional SR requesting data transmission has a higher priority. In contrast, the purpose of the dedicated SR is not to request data transmission, but to request event-triggered CSI report transmission. Event-triggered CSI reports do not necessarily always take precedence over the second PUSCH. Considering that event-triggered CSI reports are only triggered when absolutely necessary, event-triggered CSI reports take precedence over traditional CSI reports. If the second PUSCH does not carry HARQ-ACK (that is, it only carries CSI), the terminal device does not send the second PUSCH, but sends a dedicated SR. Since HARQ-ACK is closely related to data transmission, HARQ-ACK takes precedence over event-triggered CSI reports. If the second PUSCH carries HARQ-ACK, the terminal device sends the second PUSCH and does not send a dedicated SR. Similarly, it can be extended to the case where the first information is carried by a dedicated PUCCH.

[0087] In some other embodiments of the present application, when the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain, the terminal device transmits the second physical uplink shared channel (PUSCH) and the first information, wherein the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and transmitted. Reference may be made to the above description of operation 501.

[0088] In some examples, at least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) is multiplexed and transmitted on the second physical uplink shared channel (PUSCH). Reference may be made to the above description regarding operation 503.

[0089] The first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent, including:

[0090] The first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a rate matching manner and sent.

[0091] In some embodiments of the present application, when the first information overlaps with the first PUSCH or the second PUSCH in the time domain, the terminal device sends the first PUSCH or the second PUSCH and does not send the first information, or the terminal device does not send the first PUSCH or the second PUSCH and sends the first information.

[0092] For example, when a PUSCH (eg, the first PUSCH or the second PUSCH) overlaps with the first information in the time domain, one of the first PUSCH, the second PUSCH, and the first information is selected for transmission according to a predefined rule.

[0093] In some embodiments of the present application, when the first information or the channel state information (CSI) report overlaps with the aperiodic sounding reference signal (SRS) in the time domain:

[0094] The terminal device sends the first information or the channel state information (CSI) report, and does not send the aperiodic sounding reference signal (SRS); or,

[0095] The terminal device does not send the first information or the channel state information (CSI) report, but sends the non-periodic sounding reference signal (SRS).

[0096] For example, the first information is carried by the PUCCH, and the PUCCH may overlap with the aperiodic SRS in the time domain. In this case, one of them may be selected for transmission according to a predefined rule.

[0097] For another example, the CSI report is carried by the PUCCH. In the case that the PUCCH and the aperiodic SRS overlap in the time domain, one of them can be selected for transmission according to a predefined rule.

[0098] In some embodiments of the present application, when the first information or channel state information (CSI) report overlaps with a periodic or semi-persistent sounding reference signal (SRS) in the time domain:

[0099] The terminal device sends the first information or the channel state information (CSI) report, and does not send the periodic or continuous sounding reference signal (SRS).

[0100] For example, the first information or CSI report is carried by PUCCH. When PUCCH overlaps with periodic or semi-persistent SRS in the time domain, the terminal device sends the first information or CSI report but does not send SRS, that is, it considers that the periodic or semi-persistent SRS has a lower priority.

[0101] In some embodiments of the present application, the terminal device requests resources for sending a channel state information (CSI) report through the first information, and the terminal device receives downlink control information (DCI) after sending the first information. In operation 502, the terminal device sends the channel state information (CSI) report on a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) scheduled by the downlink control information (DCI).

[0102] For example, as shown in Figure 2 or Figure 3, the first information can be used to request the second resource. After receiving the first information, the network device schedules the second resource via uplink DCI, and the terminal device sends a CSI report on the second resource. The second resource scheduled by the uplink DCI can be a PUSCH resource or a PUCCH resource.

[0103] In some embodiments of the present application, the resources used to send the first information are associated with a preconfigured physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) resource, and the first information indicates that the channel state information (CSI) report transmission exists on the preconfigured resources associated with the first information.

[0104] For example, as shown in FIG4 , the first resource is associated with the second resource, and the first information is used to indicate that a CSI report transmission exists on the associated second resource.

[0105] In some embodiments of the present application, the channel state information (CSI) report is carried by uplink control information (UCI) or by a media access control element (MAC-CE).

[0106] For example, as shown in FIG3 , the CSI report is carried by MAC-CE; as shown in FIG2 and FIG4 , the CSI report is carried by UCI.

[0107] The terminal device does not send the first information when no event is detected, or sends the first information, where the first information indicates that there is no resource request or there is no CSI report transmission on the preconfigured resources associated with it.

[0108] For example, if the terminal device does not detect the occurrence of an event, the terminal device may not send the first information. Alternatively, the terminal device may send the first information, but the content of the first information is different from the content when the event is detected. In this way, for Figure 2 or Figure 3, it means that the terminal device does not request the second resource, and for Figure 4, it means that there is no CSI report transmission on the second resource.

[0109] In some embodiments, the channel state information (CSI) report includes at least a reference signal index and a layer 1 reference signal received power (L1-RSRP). For example, the CSI report includes a reference signal index and an L1-RSRP measured based on the reference signal. The CSI report may include one or more such reference signal indices and L1-RSRPs.

[0110] In some embodiments, the terminal device detects the occurrence of an event (in operation 501) when at least one of the following conditions is met:

[0111] The measurement result of at least one new beam is higher than the measurement result of the current beam by a first value; or

[0112] The measurement result of the current beam is lower than the second value.

[0113] For example, an event is defined as the L1-RSRP of at least one new beam being higher than the L1-RSRP of the current beam by a certain value, or the L1-RSRP of the current beam being lower than a certain value. A beam can be characterized by a reference signal. The reference signal corresponding to the new beam can be from a reference signal set configured separately via RRC signaling, or from one or more reference signals in one or more activated TCI states. The reference signal corresponding to the current beam can be a reference signal in the currently indicated TCI state. The reference signal can be an SSB or a CSI-RS.

[0114] When the first information is multi-bit information carried by PUCCH and the first information overlaps with HARQ-ACK in the time domain, multiplexing of the first information and HARQ-ACK is determined according to a UCI multiplexing method when CSI and HARQ-ACK overlap in the time domain.

[0115] For example, the first information is regarded as CSI, and the multiplexing of the first information and HARQ-ACK is determined according to the method of multiplexing CSI and HARQ-ACK.

[0116] When the first information is multi-bit information carried by PUCCH and the first information overlaps with CSI in the time domain, multiplexing of the first information and CSI is determined according to a UCI multiplexing method when multi-bit HARQ-ACK overlaps with CSI in the time domain.

[0117] For example, the first information is regarded as HARQ-ACK, and the multiplexing of the first information and CSI is determined according to the method of multiplexing HARQ-ACK and CSI.

[0118] In the case where the first information is multi-bit information carried by PUCCH and the first information overlaps with SR in the time domain, the multiplexing of the first information and the SR is determined according to the UCI multiplexing method when multi-bit HARQ-ACK overlaps with SR in the time domain, or the multiplexing of the first information and the SR is determined according to the UCI multiplexing method when CSI overlaps with SR in the time domain.

[0119] For example, the SR here refers to the traditional SR, and the first information is regarded as HARQ-ACK, so that the multiplexing of the first information and SR is determined according to the method of multiplexing HARQ-ACK and SR, or the first information is regarded as CSI, so that the multiplexing of the first information and SR is determined according to the method of multiplexing CSI and SR.

[0120] An embodiment of the first aspect of the present application provides a method for processing when the first information sent during an event-triggered CSI report overlaps with other uplink information in the time domain. This can avoid ambiguity between the terminal device and the network device on which information to send when a collision occurs, and avoid the terminal device missing the opportunity to send an event-triggered report.

[0121] Embodiments of the second aspect

[0122] The embodiment of the second aspect provides a method for receiving information, which is applied to a network device and corresponds to the method for sending information in the embodiment of the first aspect.

[0123] FIG9 is a schematic diagram of a method for receiving information according to an embodiment of the second aspect. As shown in FIG9 , the method includes:

[0124] 901. Receive first information sent by the terminal device when an event is detected; and

[0125] 902. Receive a channel state information (CSI) report on scheduled or pre-configured resources.

[0126] In some embodiments, when the first information overlaps with a first physical uplink shared channel (PUSCH) having an uplink shared channel (UL-SCH) in the time domain, the first physical uplink shared channel (PUSCH) and the first information sent by the terminal device are received, wherein the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent.

[0127] In some embodiments, the first information is a scheduling request (SR) or multi-bit information carried by a physical uplink control channel (PUCCH).

[0128] In some embodiments, as shown in FIG9 , the method further includes:

[0129] 903. The network device also receives at least one of a hybrid automatic repeat request acknowledgment (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) multiplexed into the first physical uplink shared channel (PUSCH).

[0130] In some embodiments, the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent, including:

[0131] The first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a rate matching manner and sent.

[0132] In some embodiments, when the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain:

[0133] If the second physical uplink shared channel (PUSCH) carries a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, receiving the second physical uplink shared channel (PUSCH) sent by the terminal device; and / or,

[0134] If the second physical uplink shared channel (PUSCH) does not carry a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, the first information sent by the terminal device is received.

[0135] In some embodiments, the method further comprises:

[0136] In the case where the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain,

[0137] The second physical uplink shared channel (PUSCH) and the first information sent by the terminal device are received, wherein the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent.

[0138] In some embodiments, the network device also receives at least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) multiplexed into the second physical uplink shared channel (PUSCH).

[0139] In some embodiments, the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent, including:

[0140] The first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a rate matching manner and sent.

[0141] In some embodiments, when the first information or channel state information (CSI) report overlaps with an aperiodic sounding reference signal (SRS) in the time domain:

[0142] receiving the first information or the channel state information (CSI) report sent by the terminal device; or

[0143] Receive the non-periodic sounding reference signal (SRS) sent by the terminal device.

[0144] In some embodiments, when the first information or channel state information (CSI) report overlaps with a periodic or semi-persistent sounding reference signal (SRS) in the time domain:

[0145] Receive the first information or the channel state information (CSI) report sent by the terminal device.

[0146] In some embodiments, the first information requests resources for sending a channel state information (CSI) report, and the network device sends downlink control information (DCI) after receiving the first information.

[0147] The channel state information (CSI) report is sent on a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) scheduled by the downlink control information (DCI).

[0148] In some embodiments, the resources used to send the first information are associated with pre-configured physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) resources,

[0149] The first information indicates that the channel state information (CSI) report transmission exists on preconfigured resources associated with the first information.

[0150] In some embodiments, the channel state information (CSI) report is carried by uplink control information (UCI) or by a medium access control element (MAC-CE).

[0151] In some embodiments, the channel state information (CSI) report includes at least a reference signal index and a layer 1 reference signal received power (L1-RSRP).

[0152] In some embodiments, the terminal device detects the occurrence of an event when at least one of the following conditions is met:

[0153] The measurement result of at least one new beam is higher than the measurement result of the current beam by a first value; or

[0154] The measurement result of the current beam is lower than the second value.

[0155] Embodiments of the third aspect

[0156] The embodiment of the third aspect of the present application provides an apparatus for sending information, which is applied to a terminal device, for example, the terminal device 102 in Figure 1. The apparatus corresponds to the method of the embodiment of the first aspect.

[0157] FIG10 is a schematic diagram of an apparatus for sending information in an embodiment of the third aspect. As shown in FIG10 , the apparatus 1000 for sending information includes a first processing unit 1001. The first processing unit 1001 controls the terminal device so that the terminal device performs the following operations:

[0158] The terminal device sends first information when detecting that an event occurs; and

[0159] Sending channel state information (CSI) reports on scheduled or pre-configured resources,

[0160] When the first information overlaps with the first physical uplink shared channel (PUSCH) with an uplink shared channel (UL-SCH) in the time domain, the terminal device sends the first physical uplink shared channel (PUSCH) and the first information, wherein the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent.

[0161] In some embodiments, the first information is a scheduling request (SR) or multi-bit information carried by a physical uplink control channel (PUCCH).

[0162] In some embodiments, the operations further include:

[0163] At least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) is multiplexed and sent on the first physical uplink shared channel (PUSCH).

[0164] In some embodiments, the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent, including:

[0165] The first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a rate matching manner and sent.

[0166] In some embodiments, when the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain:

[0167] If the second physical uplink shared channel (PUSCH) carries a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, the terminal device sends the second physical uplink shared channel (PUSCH) and does not send the first information; and / or,

[0168] If the second physical uplink shared channel (PUSCH) does not carry a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, the terminal device does not send the second physical uplink shared channel (PUSCH) but sends the first information.

[0169] In some embodiments, when the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain,

[0170] The terminal device sends the second physical uplink shared channel (PUSCH) and the first information, wherein the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent.

[0171] In some embodiments, the operations further include:

[0172] At least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) is multiplexed and sent on the second physical uplink shared channel (PUSCH).

[0173] In some embodiments, the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent, including:

[0174] The first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a rate matching manner and sent.

[0175] In some embodiments, when the first information or channel state information (CSI) report overlaps with an aperiodic sounding reference signal (SRS) in the time domain:

[0176] The terminal device sends the first information or the channel state information (CSI) report, and does not send the aperiodic sounding reference signal (SRS); or,

[0177] The terminal device does not send the first information or the channel state information (CSI) report, and sends the non-periodic sounding reference signal (SRS).

[0178] In some embodiments, when the first information or channel state information (CSI) report overlaps with a periodic or semi-persistent sounding reference signal (SRS) in the time domain:

[0179] The terminal device sends the first information or the channel state information (CSI) report, and does not send the periodic or continuous sounding reference signal (SRS).

[0180] In some embodiments, the terminal device requests resources for sending a channel state information (CSI) report via the first information,

[0181] The terminal device receives downlink control information (DCI) after sending the first information,

[0182] The channel state information (CSI) report is sent on a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) scheduled by the downlink control information (DCI).

[0183] In some embodiments, the resources used to send the first information are associated with pre-configured physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) resources,

[0184] The first information indicates that the channel state information (CSI) report transmission exists on preconfigured resources associated with the first information.

[0185] In some embodiments, the channel state information (CSI) report is carried by uplink control information (UCI) or by a medium access control element (MAC-CE).

[0186] In some embodiments, the channel state information (CSI) report includes at least a reference signal index and a layer 1 reference signal received power (L1-RSRP).

[0187] In some embodiments, the terminal device detects the occurrence of an event when at least one of the following conditions is met:

[0188] The measurement result of at least one new beam is higher than the measurement result of the current beam by a first value; or

[0189] The measurement result of the current beam is lower than the second value.

[0190] Embodiments of the fourth aspect

[0191] The fourth aspect of the present application provides an apparatus for receiving information, which is applied to a network device, for example, the network device 202 in FIG1 . The apparatus corresponds to the method of the second aspect of the present application.

[0192] FIG11 is a schematic diagram of an apparatus for receiving information in an embodiment of the fourth aspect. As shown in FIG11 , the apparatus 1100 for receiving information includes a second processing unit 1101. The second processing unit 1101 controls the network device so that the network device performs the following operations:

[0193] receiving first information sent by the terminal device when an event is detected; and

[0194] receiving channel state information (CSI) reports on scheduled or pre-configured resources,

[0195] When the first information overlaps with the first physical uplink shared channel (PUSCH) with an uplink shared channel (UL-SCH) in the time domain, the first physical uplink shared channel (PUSCH) and the first information sent by the terminal device are received, wherein the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent.

[0196] In some embodiments, the first information is a scheduling request (SR) or multi-bit information carried by a physical uplink control channel (PUCCH).

[0197] In some embodiments, the operations further include:

[0198] The network device also receives at least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) multiplexed into the first physical uplink shared channel (PUSCH).

[0199] In some embodiments, the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent, including:

[0200] The first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a rate matching manner and sent.

[0201] In some embodiments, when the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain:

[0202] If the second physical uplink shared channel (PUSCH) carries a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, receiving the second physical uplink shared channel (PUSCH) sent by the terminal device; and / or,

[0203] If the second physical uplink shared channel (PUSCH) does not carry a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, the first information sent by the terminal device is received.

[0204] In some embodiments, the operations further include:

[0205] In the case where the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain,

[0206] The second physical uplink shared channel (PUSCH) and the first information sent by the terminal device are received, wherein the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent.

[0207] In some embodiments, the operations further include:

[0208] The network device also receives at least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) multiplexed into the second physical uplink shared channel (PUSCH).

[0209] In some embodiments, the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent, including:

[0210] The first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a rate matching manner and sent.

[0211] In some embodiments, when the first information or channel state information (CSI) report overlaps with an aperiodic sounding reference signal (SRS) in the time domain:

[0212] receiving the first information or the channel state information (CSI) report sent by the terminal device; or,

[0213] Receive the non-periodic sounding reference signal (SRS) sent by the terminal device.

[0214] In some embodiments, when the first information or channel state information (CSI) report overlaps with a periodic or semi-persistent sounding reference signal (SRS) in the time domain:

[0215] Receive the first information or the channel state information (CSI) report sent by the terminal device.

[0216] In some embodiments, the first information requests resources for sending a channel state information (CSI) report,

[0217] The network device sends downlink control information (DCI) after receiving the first information,

[0218] The channel state information (CSI) report is sent on a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) scheduled by the downlink control information (DCI).

[0219] In some embodiments, the resources used to send the first information are associated with pre-configured physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) resources,

[0220] The first information indicates that the channel state information (CSI) report transmission exists on preconfigured resources associated with the first information.

[0221] In some embodiments, the channel state information (CSI) report is carried by uplink control information (UCI) or by a medium access control element (MAC-CE).

[0222] In some embodiments, the channel state information (CSI) report includes at least a reference signal index and a layer 1 reference signal received power (L1-RSRP).

[0223] In some embodiments, the terminal device detects the occurrence of an event when at least one of the following conditions is met:

[0224] The measurement result of at least one new beam is higher than the measurement result of the current beam by a first value; or

[0225] The measurement result of the current beam is lower than the second value.

[0226] Embodiments of the fifth aspect

[0227] An embodiment of the fifth aspect of the present application provides a communication system, which may include a network device and a terminal device.

[0228] Figure 12 is a schematic diagram of an electronic device according to an embodiment of the fifth aspect. As shown in Figure 12 , electronic device 1200 may correspond to terminal device 102 or network device 101 in Figure 1 . Electronic device 1200 may include a processor 1210 and a memory 1220; memory 1220 stores data and programs and is coupled to processor 1210. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0229] For example, the processor 1210 can be configured to execute a program to implement the method in the first embodiment and the method in the second embodiment.

[0230] As shown in Figure 12 , the terminal device 1200 may further include: a communication module 1230, an input unit 1240, a display 1250, and a power supply 1260. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1200 does not necessarily include all of the components shown in Figure 12 , and these components are not essential. Furthermore, the terminal device 1200 may also include components not shown in Figure 12 , for which reference may be made to the prior art.

[0231] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method in the embodiment of the first aspect.

[0232] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method in the embodiment of the first aspect.

[0233] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method in the embodiment of the second aspect.

[0234] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method in the embodiment of the second aspect.

[0235] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0236] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0237] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the 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 large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0238] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may 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.

[0239] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0240] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0241] 1. A method for receiving information, applied to a network device, the method comprising:

[0242] receiving first information sent by the terminal device when an event is detected; and

[0243] receiving channel state information (CSI) reports on scheduled or pre-configured resources,

[0244] In a case where the first information overlaps with a first physical uplink shared channel (PUSCH) having an uplink shared channel (UL-SCH) in the time domain, receiving the first physical uplink shared channel (PUSCH) and the first information sent by the terminal device, wherein the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent,

[0245] The first information is a scheduling request (SR) or multi-bit information carried by a physical uplink control channel (PUCCH).

[0246] 2. The method as described in Note 1, wherein:

[0247] The method further comprises:

[0248] In the case where the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain,

[0249] receiving the second physical uplink shared channel (PUSCH) and the first information sent by the terminal device, wherein the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent,

[0250] The method further comprises:

[0251] The network device also receives at least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) multiplexed into the second physical uplink shared channel (PUSCH).

[0252] 3. The method according to Note 2, wherein the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent, comprising:

[0253] The first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a rate matching manner and sent.

[0254] 4. The method as described in Note 1, wherein:

[0255] In a case where the first information or the channel state information (CSI) report overlaps with the aperiodic sounding reference signal (SRS) in the time domain:

[0256] receiving the first information or the channel state information (CSI) report sent by the terminal device; or,

[0257] Receive the non-periodic sounding reference signal (SRS) sent by the terminal device.

[0258] 5. The method as described in Note 1, wherein:

[0259] In the case where the first information or the channel state information (CSI) report overlaps with a periodic or semi-persistent sounding reference signal (SRS) in the time domain:

[0260] Receive the first information or the channel state information (CSI) report sent by the terminal device.

[0261] 6. The method as described in Note 1, wherein:

[0262] The first information requests resources for sending a channel state information (CSI) report,

[0263] The network device sends downlink control information (DCI) after receiving the first information,

[0264] The channel state information (CSI) report is sent on a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) scheduled by the downlink control information (DCI).

[0265] 7. The method as described in Note 1, wherein:

[0266] The resources used to send the first information are associated with pre-configured physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) resources,

[0267] The first information indicates that the channel state information (CSI) report transmission exists on preconfigured resources associated with the first information.

[0268] 8. The method as described in Note 1, wherein:

[0269] The channel state information (CSI) report is carried by uplink control information (UCI) or by a media access control element (MAC-CE).

[0270] 9. The method as described in Supplement 1, wherein:

[0271] The channel state information (CSI) report includes at least a reference signal index and a layer 1 reference signal received power (L1-RSRP).

[0272] 10. The method as described in Supplement 1, wherein:

[0273] The terminal device detects the occurrence of an event when at least one of the following conditions is met:

[0274] The measurement result of at least one new beam is higher than the measurement result of the current beam by a first value; or

[0275] The measurement result of the current beam is lower than the second value.

Claims

1. A device for sending information, applied to a terminal device, characterized in that: The apparatus includes a first processing unit, which causes the terminal device to perform the following operations: The terminal device sends first information when detecting that an event occurs; and Sending channel state information (CSI) reports on scheduled or pre-configured resources, When the first information overlaps with the first physical uplink shared channel (PUSCH) with an uplink shared channel (UL-SCH) in the time domain, the terminal device sends the first physical uplink shared channel (PUSCH) and the first information, wherein the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent.

2. The device according to claim 1, wherein The first information is a scheduling request (SR) or multi-bit information carried by a physical uplink control channel (PUCCH).

3. The device according to claim 1, wherein The operations further include: At least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) is multiplexed and sent on the first physical uplink shared channel (PUSCH).

4. The device according to claim 1, wherein The first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent, including: The first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a rate matching manner and sent.

5. The device according to claim 1, wherein In a case where the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain: If the second physical uplink shared channel (PUSCH) carries a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, the terminal device sends the second physical uplink shared channel (PUSCH) and does not send the first information; and / or, If the second physical uplink shared channel (PUSCH) does not carry a hybrid automatic repeat request acknowledgment (HARQ-ACK) message, the terminal device does not send the second physical uplink shared channel (PUSCH) but sends the first information.

6. The device according to claim 1, wherein In the case where the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain, The terminal device sends the second physical uplink shared channel (PUSCH) and the first information, wherein the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent.

7. The device according to claim 6, wherein The operations further include: At least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) is multiplexed and sent on the second physical uplink shared channel (PUSCH).

8. The device according to claim 7, wherein The first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent, including: The first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the second physical uplink shared channel (PUSCH) in a rate matching manner and sent.

9. The device according to claim 1, wherein In a case where the first information or the channel state information (CSI) report overlaps with the aperiodic sounding reference signal (SRS) in the time domain: The terminal device sends the first information or the channel state information (CSI) report, and does not send the aperiodic sounding reference signal (SRS); or, The terminal device does not send the first information or the channel state information (CSI) report, and sends the non-periodic sounding reference signal (SRS).

10. The device of claim 1, wherein In the case where the first information or the channel state information (CSI) report overlaps with a periodic or semi-persistent sounding reference signal (SRS) in the time domain: The terminal device sends the first information or the channel state information (CSI) report, and does not send the periodic or continuous sounding reference signal (SRS).

11. The device according to claim 1, wherein The terminal device requests resources for sending a channel state information (CSI) report through the first information, The terminal device receives downlink control information (DCI) after sending the first information, The channel state information (CSI) report is sent on a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) scheduled by the downlink control information (DCI).

12. The device of claim 1, wherein The resources used to send the first information are associated with pre-configured physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) resources, The first information indicates that the channel state information (CSI) report transmission exists on preconfigured resources associated with the first information.

13. The device of claim 1, wherein: The channel state information (CSI) report is carried by uplink control information (UCI) or by a media access control element (MAC-CE).

14. The device of claim 1, wherein: The channel state information (CSI) report includes at least a reference signal index and a layer 1 reference signal received power (L1-RSRP).

15. The apparatus of claim 1, wherein: The terminal device detects the occurrence of an event when at least one of the following conditions is met: The measurement result of at least one new beam is higher than the measurement result of the current beam by a first value; or The measurement result of the current beam is lower than the second value.

16. A device for receiving information, applied to a network device, characterized in that: The apparatus includes a second processing unit, which causes the network device to perform the following operations: receiving first information sent by the terminal device when an event is detected; and receiving channel state information (CSI) reports on scheduled or pre-configured resources, When the first information overlaps with the first physical uplink shared channel (PUSCH) with an uplink shared channel (UL-SCH) in the time domain, the first physical uplink shared channel (PUSCH) and the first information sent by the terminal device are received, wherein the first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent.

17. The apparatus of claim 16, wherein: The operations further include: The network device also receives at least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, channel state information part 1 (CSI part 1), and channel state information part 2 (CSI part 2) multiplexed into the first physical uplink shared channel (PUSCH).

18. The apparatus of claim 16, wherein: The first information is multiplexed onto the first physical uplink shared channel (PUSCH) and sent, including: The first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a puncturing manner and sent, or the first information is multiplexed onto the first physical uplink shared channel (PUSCH) in a rate matching manner and sent.

19. The apparatus of claim 16, wherein: In a case where the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain: If the second physical uplink shared channel (PUSCH) carries a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, receiving the second physical uplink shared channel (PUSCH) sent by the terminal device; and / or, If the second physical uplink shared channel (PUSCH) does not carry a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, the first information sent by the terminal device is received.

20. The apparatus of claim 16, wherein: The operations further include: In the case where the first information overlaps with a second physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH) in the time domain, The second physical uplink shared channel (PUSCH) and the first information sent by the terminal device are received, wherein the first information is multiplexed onto the second physical uplink shared channel (PUSCH) and sent.

Images