Data transmission method, terminal device, network device, storage medium and product
Patent Information
- Application Number
- CN202510472801.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-15
- Publication Date
- 2026-10-23
AI Technical Summary
[0003]然而,相关网络或设备无法确定具体有多少CC上触发了多少个event,那么,相关网络或设备将依据最大载荷(payload)大小为第二PUSCH分配资源,即分配的资源要能承载所有CC所有event同时触发时所需要的payload,如此,导致资源浪费
[0022]本申请提出一种跨载波场景下的数据传输方法,通过将多个分量载波的多个事件对应的信息在第一物理上行控制信道和/或第二物理上行信道的多个上报时机上发送,使得网络设备能够准确的了解每一分量载波上触发的事件的数量,那么,网络设备就可以根据实际数量配置资源,解决了相关技术中资源浪费的问题。
Smart Images

Figure CN122969748A_ABST
Abstract
Description
Technical Field
[0001] This application relates to, but is not limited to, the field of communications, and particularly to a data transmission method, terminal equipment, network equipment, computer-readable storage medium, and computer program product. Background Technology
[0002] Currently, for the UE-initiated beam management process when the user equipment (UE) is operating in a carrier aggregation (CA) scenario, the relevant technology uses one bit of the first physical uplink control channel (PUCCH) to indicate to the second physical uplink shared channel (PUSCH) that there is at least one event of at least one component carrier (CC) to trigger the UE to initiate beam reporting (UEIBR).
[0003] However, if the relevant network or device cannot determine exactly how many events were triggered on how many CCs, then the relevant network or device will allocate resources to the second PUSCH based on the maximum payload size. That is, the allocated resources must be able to carry the payload required when all events on all CCs are triggered simultaneously, thus resulting in resource waste. Summary of the Invention
[0004] This application provides a data transmission method, a terminal device, a network device, a computer-readable storage medium, and a computer program product.
[0005] The technical solution of this application embodiment is implemented as follows:
[0006] Firstly, embodiments of this application provide a data transmission method applied to a terminal device, the method comprising:
[0007] At the reporting timing of the first physical uplink control channel and / or the second physical uplink channel, first information is transmitted; wherein the first information includes information corresponding to a first event in the component carrier, the first event being used to trigger or instruct the terminal device to report.
[0008] Secondly, embodiments of this application provide a data transmission method applied to a network device, the method comprising:
[0009] At the reporting timing of the first physical uplink control channel and / or the second physical uplink channel, first information is received; wherein the first information includes information corresponding to a first event in the component carrier, the first event being used to trigger or instruct the terminal device to report.
[0010] Thirdly, embodiments of this application provide a terminal device, the terminal device comprising:
[0011] The first transmitting module is configured to transmit first information at the reporting timing of the first physical uplink control channel and / or the second physical uplink channel; wherein the first information includes information corresponding to a first event in the component carrier, and the first event is used to trigger or instruct the terminal device to report.
[0012] Fourthly, embodiments of this application provide a network device, the network device comprising:
[0013] The second receiving module is configured to receive first information during the reporting timing of the first physical uplink control channel and / or the second physical uplink channel; wherein the first information includes information corresponding to a first event in the component carrier, and the first event is used to trigger or instruct the terminal device to report.
[0014] Fifthly, embodiments of this application provide a terminal device, the terminal device comprising:
[0015] The first memory is used to store executable instructions;
[0016] The first processor, when executing executable instructions stored in the first memory, performs the steps of the above-described data transmission method.
[0017] Sixthly, embodiments of this application provide a network device, the network device comprising:
[0018] The second memory is used to store executable instructions;
[0019] The second processor, when executing executable instructions stored in the second memory, performs the steps of the above-described data transfer method.
[0020] Seventhly, embodiments of this application provide a computer-readable storage medium having stored thereon one or more computer programs, which can be executed by one or more processors to implement the steps of the above-described data transmission method.
[0021] Eighthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the above-described data transmission method.
[0022] This application proposes a data transmission method in a cross-carrier scenario. By sending information corresponding to multiple events on multiple component carriers at multiple reporting times on the first physical uplink control channel and / or the second physical uplink channel, the network device can accurately understand the number of events triggered on each component carrier. Thus, the network device can configure resources according to the actual number, solving the problem of resource waste in related technologies. Attached Figure Description
[0023] Figure 1 This is a schematic diagram of a communication system according to an embodiment of this application;
[0024] Figure 2 A flowchart illustrating a data transmission method provided in an embodiment of this application;
[0025] Figure 3 A schematic block diagram of a terminal device provided in an embodiment of this application;
[0026] Figure 4 A schematic block diagram of a network device provided in an embodiment of this application;
[0027] Figure 5 This is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation
[0028] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0029] The embodiments of this application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, New Radio (NR) system, evolution system of NR system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wi-Fi), next-generation communication systems or other communication systems, etc.
[0030] Figure 1 This is a schematic diagram of a communication system according to an embodiment of this application.
[0031] like Figure 1 As shown, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.
[0032] exist Figure 1 In the communication system 100 shown, network device 120 can be an access network device that communicates with terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal device 110 located within that coverage area.
[0033] Network device 120 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB or gNodeB) in an NR system, or a radio controller in a Cloud Radio Access Network (CRAN), or network device 120 may be a relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, or network equipment in a future evolved Public Land Mobile Network (PLMN), etc.
[0034] Terminal equipment 110 can also be referred to as UE, tag, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc. Terminal equipment can be a station in a WLAN, a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and next-generation communication system, such as terminal equipment in an NR network or a future evolved Public Land Mobile Network (PLMN) network, etc.
[0035] Figure 1 An exemplary illustration shows a base station and two UEs. Optionally, the communication system 100 may include multiple base stations, and each base station may include other numbers of UEs within its coverage area. This application embodiment does not limit this.
[0036] It should be noted that, Figure 1This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as LTE protocol, NR protocol, and related protocols applied to future communication systems, and this application does not limit this.
[0037] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.
[0038] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit the scope of this application.
[0039] Before explaining this application, the following explanation is given regarding UE-initiated beam reporting in related technologies:
[0040] Channel State Information (CSI) Reporting: The CSI feedback reporting framework is a crucial component of 5G NR, allowing the UE to report channel state information to the gNB for effective beam management and resource scheduling. Beam management refers to beamforming technology, which adjusts the amplitude and phase of the antenna to concentrate signal energy into a narrow beam in a specific direction, thereby enhancing coverage and reducing interference. The beam management process mainly includes: First, scanning, where the gNB transmits multiple beams in different spatial directions, and the UE listens to / scans these beams in different receiving spaces. The UE evaluates the received signal quality of each beam, including metrics such as Reference Signal Receiving Power (RSRP) and Signal-to-Interference-plus-Noise Ratio (SINR); then, the UE reports the beam quality and decision information to the gNB. The network can then adjust the current beam based on the beam measurement results reported by the UE.
[0041] It should be noted that the CSI feedback process consists of two main steps: first, CSI resource configuration, where the gNB configures the UE to send a Channel State Information Reference Signal (CSI-RS) and / or a Synchronization Signal / Physical Broadcast Channel block (SS / PBCH block / SSB); second, CSI report configuration, where the UE measures the CSI-RS and / or SSB, and then reports the CSI to the gNB according to the configuration.
[0042] In traditional beam management procedures, existing standards primarily focus on L1 layer beam measurement and reporting configured by the gNB. Specifically, the gNB can configure or activate periodic or semi-persistent (P / SP) beam reporting, for example, reporting N optimal beams and their corresponding L1 RSRP values. Furthermore, the gNB can also trigger aperiodic (AP) beam reporting to quickly acquire the optimal beam for data or control channel transmission. However, such frequent beam reporting configuration undoubtedly increases the uplink reporting burden and control signaling overhead. If the beam reporting configuration or triggering frequency is low, the UE's beam reports may become outdated, and the gNB may not be able to continuously obtain the optimal beam, leading to a significant degradation in performance and coverage, as well as increased beam measurement reporting latency.
[0043] Considering the significant overhead and latency of traditional CSI measurement and reporting configuration frameworks, this paper proposes to further enhance the UE-initiated / event-driven beam management process to reduce beam management overhead and / or latency. By enhancing the UE-initiated / event-driven beam management approach, if the UE has a better and more timely understanding of beam quality changes, the UE-initiated beam reporting process will obtain more timely beam reports while reducing reporting overhead. If the UE determines, for example, that the current beam quality has deteriorated, the UE can trigger a beam report without requiring network configuration or frequent reporting.
[0044] Based on the discussion of User Equipment (UE)-initiated beam management in 3rd Generation Partnership Project (3GPP) Release 19 (R19), the Radio Access Network (RAN) 1#116bis meeting agreed to implement UE-initiated beam reporting (UEIBR) through the following modes based on uplink control information (UCI): Mode A (gNB dynamically scheduling UCI) and Mode B (UCI in pre-configured resource(s) for second UL channel).
[0045] Here, during the beam report transmission procedure for UE-initiated / event-driven beamreporting, the following modes are supported:
[0046] Mode A:
[0047] Step 1: The UE sends a first PUCCH (one-bit / multi-bit) to request resources for a second UL channel to carry beam reports.
[0048] FFS: Request format, e.g., SR or a new UCI type.
[0049] Step 2: The UE detects the DCI format and indicates that resource UL channel 1 carries a beam report.
[0050] Step 3: Send a beam report in the second UL channel.
[0051] FFS: Details on the second UL channel, e.g., whether the second UL channel is PUCCH, PUSCH, or both.
[0052] Mode A represents a basic UE capability (i.e., all UEs supporting UE-initiated / event-driven beam reporting should support this feature).
[0053] Mode B:
[0054] Step 1: The UE transmits a first PUCCH (one-bit / multi-bit) notifying a second UL channel to carry beam report;
[0055] FFS: Notification format, e.g., SR or a new UCI type;
[0056] Step 2: The UE transmits the beam report in the second UL channel 1.
[0057] FFS: Details on the second UL channel, e.g., whether the second UL channel is PUCCH, PUSCH or both.
[0058] The notification in step 1 is in a separate reporting instance from the beamreport in step 2;
[0059] FFS: Whether the UE receives acknowledgment information with response to each step for all modes. For the above procedures, cross-CC beamreporting is supported in both modes.
[0060] It should be noted that, for UEs operating in CA scenarios, there may be situations where one or more CCs among multiple CCs simultaneously meet the first condition, triggering a report. Furthermore, current standardization discussions may aim to support a maximum of three events: the current serving beam quality is below a threshold; at least one new beam quality is above a threshold compared to the current serving beam quality; at least one new beam quality is above a threshold compared to the Mth best quality in the active TCI state. Therefore, it is possible for multiple CCs and multiple events to simultaneously meet the first condition, triggering a report.
[0061] Considering CCs operating in different frequency bands, high-frequency CCs will frequently meet the first condition; while low-frequency CCs are more stable, and not many CCs will simultaneously meet the first condition. Considering multiple CCs operating in similar frequency bands, multiple CCs will simultaneously meet the first condition. Furthermore, when multiple CCs are configured in a CC list, their indicated TCI states are identical, and any new beams meeting the first condition will also be identical. To address these two scenarios, related technologies use a bit from the first PUCCH to indicate to the second PUSCH that at least one event from at least one CC triggers the UE to initiate beam reporting (UE-initiated beam reporting, UEIBR).
[0062] Figure 2 This is a flowchart illustrating a data transmission method provided in an embodiment of this application, as shown below. Figure 2 As shown, this method is applied to Figure 1 In the communication system 100 shown, the method includes:
[0063] Step 201: On the transmission occasion of the first physical uplink control channel and / or the second physical uplink channel, the terminal device sends the first information.
[0064] The first information includes information corresponding to the first event in the component carrier, and the first event is used to trigger or instruct the terminal device to report.
[0065] In this application embodiment, the reporting timing may refer to the time slot in which the first PUCCH and / or the second physical uplink channel resources are to be transmitted (or located).
[0066] In this embodiment, the first event includes one or more of the following: the quality measurement of the current serving beam is less than a first threshold; the quality measurement of at least one new beam is higher than the quality measurement of the current serving beam and higher than a second threshold; the quality measurement of at least one new beam is higher than the Mth best quality measurement in the active TCI state and higher than a third threshold. Here, the first threshold, the second threshold, and the third threshold can be absolute thresholds; an absolute threshold refers to the minimum signal value required for normal communication between the terminal device and the network device.
[0067] In this embodiment of the application, beam quality is evaluated by one or more of RSRP, Reference Signal Receiving Quality (RSRQ), and SINR.
[0068] In this embodiment of the application, the information corresponding to the first event includes the CSI information corresponding to the first event, or the specific triggering condition content corresponding to the first event, or the beam information corresponding to the first event, or the CC information corresponding to the first event; that is, in this application, the terminal device reports the specific information of the event triggered on each CC at the reporting time of the first physical uplink control channel and / or the second physical uplink channel.
[0069] Here, CSI information includes the Channel State Indicator Reference Signal Resource Indicator (CSI-RSresource indicator, CRI) / Synchronization Data Block ID (SSB ID) corresponding to each event, and its corresponding Layer 1 (L1)-RSRP / L1-SINR.
[0070] Based on this, assume that each of the M CCs has at least one event triggered, where CC#m has N events. m If a number of events are triggered, then there are a total of An event is triggered, and the CSI information corresponding to each event is defined as the first information.
[0071] In this embodiment of the application, the second physical uplink channel includes the second PUCCH and the second PUSCH.
[0072] It should be noted that PUCCH (i.e., the first PUCCH or the second PUCCH) is used to carry UCI, meaning that UCI is sent on the PUCCH resource. PUSCH is used to carry data.
[0073] Here, UCI includes at least one of the following: Hybrid Automatic Repeat reQuest ACK (HARQ-ACK) information, channel state information (CSI), and scheduling request (SR) information.
[0074] It should be noted that in CA scenarios, PUCCH is transmitted on the primary component carrier (PCC) or primary cell (PCell). When the CA scenario is configured to transmit PUCCH on secondary component carriers (SCC) or secondary cells (SCell), the aggregated carriers can be divided into two PUCCH carrier groups. Each PUCCH carrier group has a designated carrier for PUCCH transmission. The carrier group containing the PCC (or PCell) is the primary PUCCH carrier group, and PUCCH is transmitted on the PCC (or PCell). The secondary PUCCH carrier groups all contain SCCs (or SCells). Higher-layer signaling configures one of the SCCs (or SCells) to transmit PUCCH, which is called PUCCHSCell. The HARQ-ACK of all downlink transmissions (including PDSCH and PDCCH requiring HARQ-ACK feedback) on all carriers in each carrier group is transmitted in the PUCCH on the designated carrier.
[0075] Step 202: The network device receives the first information.
[0076] It should be noted that the first message can be sent directly by the terminal device or by a third-party device connected to the terminal device.
[0077] This application provides a data transmission method, comprising: a terminal device sending first information at reporting times on a first physical uplink control channel and / or a second physical uplink channel; wherein the first information includes information corresponding to a first event in a component carrier, the first event being used to trigger or instruct the terminal device to report; and a network device receiving the first information. In other words, this application proposes a data transmission method in a cross-carrier scenario. By sending specific information corresponding to multiple events on multiple component carriers at multiple reporting times on the first physical uplink control channel and / or the second physical uplink channel, the network device can accurately understand the number of events triggered on each component carrier. Therefore, the network device can configure resources according to the actual number, solving the problem of resource waste in related technologies.
[0078] In this embodiment of the application, for the first information sent by the terminal device, the component carrier corresponding to the first information in each reporting time is different, and / or the first event supported or occurred by the component carrier corresponding to the first information in each reporting time is different.
[0079] For example, the first information in timing 1 includes information corresponding to event 1 and event 2 supported or transmitted by component carrier 1; the first information in timing 2 includes information corresponding to component carrier 2; and the first information in timing 3 includes information corresponding to event 3 supported or transmitted by component carrier 1.
[0080] In this embodiment of the application, for the first information sent by the terminal device, information corresponding to one or more first events is transmitted at each reporting time.
[0081] For example, the first information in timing 4 includes information corresponding to events 1 and 2 supported or transmitted by component carrier 1, or the first information in timing 5 includes information corresponding to component carrier 4.
[0082] In practical applications, the first physical uplink control channel and / or the second physical uplink channel may correspond to multiple reporting opportunities. Based on this, step 201, sending the first information during the reporting opportunities of the first PUCCH and / or the second physical uplink channel, can be achieved through the following steps:
[0083] At the Kth reporting opportunities of the first PUCCH and / or the second physical uplink channel, or at the Kth available reporting opportunities, send K sets of first information.
[0084] Where K is a positive integer.
[0085] It should be noted that if each of the M CCs has at least one event triggered, then among the M CCs, CC#m contains event#{i=1,…,N}. m When a PUCCH is triggered (m = 1, ..., M), these events are divided into K event groups; then the terminal can send the CSI information corresponding to these K event groups on K transmission occasions after the first PUCCH or on K available transmission occasions.
[0086] In this embodiment of the application, K groups of first information are information corresponding to one component carrier or one group of component carriers; each group of first information includes information corresponding to all triggered first events in one component carrier or one group of component carriers.
[0087] It should be noted that if each of the M CCs has at least one event triggered, the CSI information corresponding to one CC or one CC group is considered as one group of CSI information. Each group of CSI information contains the CSI information corresponding to all the triggered events in that CC or CC group, for a total of K groups. Then the terminal can send these K groups of corresponding CSI information on K transmission occasions or K available transmission occasions after the first PUCCH.
[0088] In the case of CC groups, M CCs can be divided into A CC groups. The grouping method can be configured in advance according to RRC. A is less than or equal to M, and each CC can only belong to one CC group. The CCs in each group do not overlap.
[0089] For example, in a CA scenario, the CA includes multiple CCs, namely CC1, CC2, CC3, CC4, CC5, and CC6. CC1 and CC2 are grouped into the same CC group, CC3 and CC4 into the same CC group, and CC5 and CC6 into the same CC group. During the three reporting opportunities of the first PUCCH and / or the second physical uplink channel, or during the three available reporting opportunities, information corresponding to all triggered events of the CCs in the three CC groups is reported three times. Specifically, the first report is for all triggered events corresponding to CC1 and CC2; the second report is for all triggered events corresponding to CC5 and CC6; and the third report is for all triggered events corresponding to CC3. (Here, why is there no report of relevant information for CC4? Because there are no corresponding triggered events in CC4.)
[0090] For example, in a CA scenario, the CA includes multiple CCs, namely CC1, CC2, CC3, CC4, CC5 and CC6; during the six reporting opportunities of the first PUCCH and / or the second physical uplink channel, or the six available reporting opportunities, information corresponding to all the triggered events in CC1, CC2, CC3, CC4, CC5 and CC6 are reported six times respectively.
[0091] In this embodiment of the application, K groups of first information are information corresponding to the same first event as a group, and the component carriers corresponding to each group of first information belong to the same component carrier or different component carriers.
[0092] It should be noted that if each of the M CCs has at least one event triggered, the CSI information corresponding to one type of event in the M CCs is considered as one group. The event type corresponding to each group of CSI information is the same, and the CC corresponding to each group of CSI information can belong to one CC or multiple CCs. Similarly, the terminal can send these K groups of corresponding CSI information on K transmission occasions after the first PUCCH or on K available transmission occasions.
[0093] For example, in a CA scenario, the CA includes multiple CCs, namely CC1, CC2, CC3, CC4, CC5, and CC6; CC1 supports or occurs events corresponding to the first type, CC2 supports or occurs events corresponding to the first type, CC3 supports or occurs events corresponding to the third type, CC4 supports or occurs events corresponding to the second type, CC5 supports or occurs events corresponding to the second type, and CC6 supports or occurs events corresponding to the third type. CC1 and CC2 are grouped into the same CC group, CC3 and CC6 are grouped into the same CC group, and CC4 and CC5 are grouped into the same CC group. Therefore, during the three reporting opportunities of the first PUCCH and / or the second physical uplink channel, or the three available reporting opportunities, the three... Report the information corresponding to the triggered events of the CCs in the three CC groups. The CCs corresponding to the first information in each group belong to the same CC or different CCs. For example, the first report reports the information corresponding to all the triggered events of CC3 and CC6 (the first report means that the information corresponding to all the triggered events belongs to different CCs); the second report reports the information corresponding to all the triggered events of CC4 and CC5 (the second report means that the information corresponding to all the triggered events belongs to different CCs); the third report reports the information corresponding to all the triggered events of CC1; (here, there is no corresponding triggered event in CC2, the third report means that the information corresponding to all the triggered events belongs to the same CC).
[0094] Based on this, if the first information in group K includes For each first event, the terminal device will divide the S first events into K groups; S is a positive integer; here, the division can be based on the event type.
[0095] Here, the S first events can also be divided by the following steps: sort the S first events in a predefined order to obtain a list of first events, and divide the S first events into K groups according to the list of first events; wherein, the predefined order includes priority according to component carrier index or priority according to first event index.
[0096] Here, the S first events can also be divided by the following steps: the S first events are divided into K groups according to the order of component carrier index priority or first event index priority.
[0097] It should be noted that, assuming each of the M CCs has at least one event triggered, and CC#m has N events... m If a number of events are triggered, then there are a total of When an event is triggered, the S events can be divided into K groups; the terminal can send the corresponding CSI information for these K groups on K transmission occasions after the first PUCCH or on K available transmission occasions.
[0098] For example, dividing S events into K groups can be achieved through the following steps:
[0099] Sort the S events in a predefined order to form an event list {event#1, ..., event#S}. Divide all the sorted events into K groups (i.e., before (after)). There are in the group There are 1 event, and the remaining ones are 10. There are in the group (one event);
[0100] Based on this, the S events are sorted in a predefined order as follows:
[0101] The first method: prioritizes the CC index, that is, {the first CC of the first event type, the second CC of the first event type, ..., the G1st CC of the first event type, the first CC of the second event type, ..., the G2nd CC of the second event type, ..., the first CC of the I-th event type, ..., the G1st CC of the I-th event type}. I One CC};
[0102] Wherein, assuming that the i-th event type contains G i The event is triggered on a CC (i = 1, ..., I). The i-th event type refers to the event type with the smallest or largest index among all the event types that the event type satisfies; or the g-th CC with the i-th event type refers to the CC with the smallest or largest index among all the CCs where the i-th event type is triggered.
[0103] The second method: prioritizes the event index, i.e., {the first event of the 1st CC, the second event of the 1st CC, ..., the N1st event of the 1st CC, the first event of the 2nd CC, ..., the N2nd event of the 2nd CC, ..., the first event of the Mth CC, ..., the N1st event of the Mth CC}. M One event};
[0104] Wherein, the m-th CC refers to the CC with the smallest or largest CC index among all CCs where at least one event has been triggered; or, the n-th event in the m-th CC refers to the event with the smallest or largest index associated with the event among the events triggered on the m-th CC.
[0105] For example, in M = 4 CCs, CC#m contains event#{i = 1, ..., N}. M When events are triggered (m = 1, ..., M), they are divided into K = 4 event groups, and events within the same CC are grouped into the same event group. The terminal then sends the CSI information corresponding to the events in the first event group (corresponding to the first CC) on the first transmission occasion or the first available transmission occasion after the first PUCCH; it sends the CSI information corresponding to the events in the second event group (corresponding to the second CC) on the second transmission occasion or the second available transmission occasion, and so on, until the Kth event group (corresponding to the Kth CC) is sent on the Kth available transmission occasion.
[0106] For example, in M = 4 CCs, CC#m contains event#{i = 1, ..., N}. MIf an event is triggered (m = 1, ..., M), then the CCs triggered by event #1 are CCs #{1, 2, 3}, those triggered by event #2 are CCs #{2, 3, 4}, and those triggered by event #3 are CCs #{3, 4}. All events on all CCs are then divided into three groups, each corresponding to one event type: Group 1: {event #1 on CC #1, event #1 on CC #2, event #1 on CC #3}, Group 2: {event #2 on CC #2, event #2 on CC #3, event #2 on CC #4}, and Group 3: {event #3 on CC #3, event #3 on CC #4}. The terminal then sends the CSI information corresponding to the events in Group 1 on the first transmission occasion or the first available transmission occasion after the first PUCCH, and on the second transmission occasion or the second available transmission occasion. On the first transmission occasion, send the CSI information corresponding to the event in group 2, ..., on the third transmission occasion or the third available transmission occasion, send the CSI information corresponding to the event in group 3.
[0107] For example, in M = 4 CCs, CC#m contains event#{i = 1, ..., N}. MWhen triggered (m = 1, ..., M), CC#1 has event#1, CC#2 has event#{1, 2}, CC#3 has event#{2, 3}, and CC#4 has event#{2, 3}. Following the order of method 2 in the lower branch 3, the order is: {event#1 on CC#1, event#1 on CC#2, event#2 on CC#2, event#2 on CC#3, event#3 on CC#3, event#2 on CC#4, event#3 on CC#4}. Assuming it can be divided into K = 4 groups, group 1: {event#1 on CC#1, event#1 on CC#2}, group 2: {event#2 on CC#2, event#2 on CC#3}, group 3: {event#3 on CC#3, event#2 on CC#4}, group 4: {event#3 on CC#4}. Then, the terminal's first transmission after the first PUCCH... On the first available transmission occasion, CSI information corresponding to the event in group 1 is sent; on the second available transmission occasion, CSI information corresponding to the event in group 2 is sent; ... on the fourth available transmission occasion, CSI information corresponding to the event in group 4 is sent.
[0108] In one embodiment, the first information includes one or more of the following:
[0109] Component carrier index (CC Index); Here, the CC index can be indicated in the form of a bitmap, where bit = 0 indicates that no event was triggered on the CC, and bit = 1 indicates that at least one event was triggered on the CC;
[0110] The number of component carriers; at least one event is triggered on the CC here;
[0111] Component carrier group index;
[0112] The number of component carrier groups;
[0113] First event index;
[0114] The number of first events;
[0115] The association between a component carrier or a group of component carriers and the first event; such as the event index triggered on a certain CC or CC group;
[0116] The number corresponding to K is the number of transmission occasions K or the number of groups K.
[0117] It should be noted that since the number of groups is equal to the number of CCs or CC groups, the UE can report only the number of CCs or CC groups, or only the number of transmission occasions K.
[0118] It should be noted that since the number of groups is equal to the number of event types, the UE can report only the number of event types or only the number K of transmission occasions.
[0119] Regarding K, this application can determine it through the following steps: The network device sends second information; wherein the second information includes one or more of the following: the number of uplink control information payloads that the configured second physical uplink channel can carry; the number of component carriers or component carrier groups; and the number of first events. The terminal device receives the second information and determines K based on the second information.
[0120] In some embodiments, the method provided in this application includes the following:
[0121] By sending the content of a CSI report over multiple transmission occasions, a large amount of CSI report information can be sent through a PUSCH with a limited payload. However, extending the transmission time may lead to excessive transmission delay and invalidation of the transmitted CSI content. Therefore, a UCI discarding mechanism can be used, combined with the number of UCI payloads that the second PUSCH can carry in K transmission occasions configured by the base station. This ensures that as much effective CSI content as possible is transmitted, preventing excessive transmission delay, while also maximizing the transmission of CSI.
[0122] Specifically, firstly, multiple CSIs are arranged sequentially according to their priority from highest to lowest, with lower-priority CSIs placed after the bits corresponding to higher-priority CSIs. When the maximum payload size that the PUSCH can carry in K transmission occurrences is less than the payload size of the information reported by the terminal, the terminal needs to discard lower-priority CSIs according to their priority (the terminal device determines the priority of the first information and discards part of the first information based on the priority) until the payload size of the reported information does not exceed the carrying capacity of the PUSCH.
[0123] The granularity of the discarded event includes one of the following: CC; first event type; first event in the component carrier (event on CC).
[0124] In some embodiments, if the granularity of discarding is CC, the first information such as CSI information corresponding to multiple events on multiple CCs each corresponds to a priority. The first information such as CSI information corresponding to different events with the same CC index has the same priority. The terminal device will discard all first information such as CSI information with the same priority.
[0125] In some embodiments, if the granularity of the discard is event type, the first information such as CSI information corresponding to multiple events on multiple CCs each corresponds to a priority. The first information such as CSI information corresponding to the same event type on different CCs has the same priority. The terminal device will discard all first information such as CSI information with the same priority.
[0126] The CSI priority value calculation formula includes a factor of the event that triggers the terminal to report beams, that is, the terminal device determines the priority of the first information based on the first factor; wherein the first factor is related to the event used to trigger or instruct the terminal device to report.
[0127] In some embodiments, if the granularity of the discarded event is an event on a CC, the first information such as CSI information corresponding to multiple events on multiple CCs each corresponds to a priority, and the first information such as CSI information corresponding to events with different event types has different priorities; the first information such as CSI information corresponding to events with different CC indices has different priorities.
[0128] The CSI priority value calculation formula includes a factor of the event that triggers the terminal to report beams, that is, the terminal device determines the priority of the first information based on the first factor; wherein the first factor is related to the event used to trigger or instruct the terminal device to report.
[0129] It should be noted that the first information sent on the K reporting occasions or K available reporting occasions is the first information after the data has been discarded. For example, the content of the CSI report transmitted in K transmission occasions is the CSI content after the data has been discarded.
[0130] Embodiments of this application provide a terminal device that can be used to implement... Figure 2 A data transmission method is provided in the corresponding embodiment, referring to... Figure 3 As shown, the terminal device 300 includes:
[0131] The first transmitting module 301 is configured to transmit first information at the reporting timing of the first physical uplink control channel and / or the second physical uplink channel; wherein the first information includes information corresponding to a first event in the component carrier, and the first event is used to trigger or instruct the terminal device to report.
[0132] In other embodiments of this application, the component carriers and / or the first events supported or occurring by the first information in each reporting timing are different.
[0133] In other embodiments of this application, information corresponding to one or more first events is transmitted at each reporting time.
[0134] In other embodiments of this application, the first sending module 301 is used to send K sets of first information at K reporting opportunities on the first physical uplink control channel and / or the second physical uplink channel, or at K available reporting opportunities; wherein K is a positive integer.
[0135] In other embodiments of this application, the K groups of first information are grouped together by information corresponding to a component carrier or a group of component carriers. Each group of first information includes information corresponding to all triggered first events in a component carrier or a group of component carriers.
[0136] In other embodiments of this application, K groups of first information are information corresponding to the same first event as a group, and the component carriers corresponding to each group of first information belong to the same component carrier or different component carriers.
[0137] In other embodiments of this application, the first processing module 302 is used to divide the S first events into K groups; S is a positive integer.
[0138] In other embodiments of this application, the first processing module 302 is used to sort the S first events in a predefined order to obtain a list of first events; and to divide the S first events into K groups according to the list of first events; wherein the predefined order includes priority according to component carrier index or priority according to first event index;
[0139] The first processing module 302 is used to divide the S first events into K groups according to the order of component carrier index priority or first event index priority.
[0140] In other embodiments of this application, the first information includes one or more of the following:
[0141] Component carrier index;
[0142] The number of component carriers;
[0143] Component carrier group index;
[0144] The number of component carrier groups;
[0145] First event index;
[0146] The number of first events;
[0147] The correlation between component carriers or component carrier groups and the first event;
[0148] The number corresponding to K.
[0149] In other embodiments of this application, the first receiving module 303 is used to receive second information; wherein the second information includes one or more of the following: the number of uplink control information payloads that can be carried by the configured second physical uplink channel; the number of component carriers or component carrier groups; and the number of first events;
[0150] The first processing module 302 is used to determine K based on the second information.
[0151] In other embodiments of this application, the first processing module 302 is used to determine the priority of the first information; and based on the priority, discard part of the first information.
[0152] In other embodiments of this application, the granularity of discard includes one of the following: component carrier; first event type; first event in component carrier.
[0153] In other embodiments of this application, if the granularity of the discarded component carrier is a component carrier, the first information corresponding to the first events on multiple component carriers each corresponds to a priority, and the first information corresponding to different first events with the same component carrier index has the same priority.
[0154] In other embodiments of this application, if the granularity of the discarded event is the first event type, the first information corresponding to the first event on multiple component carriers each corresponds to a priority, and the first information corresponding to the same first event type on different component carriers has the same priority.
[0155] In other embodiments of this application, if the granularity of the discarded event is the first event in the component carrier, the first information corresponding to the first events on multiple component carriers each corresponds to a priority, and the first information corresponding to the first events with different first event types has different priorities; the first information corresponding to the first events with different component carrier indices has different priorities.
[0156] In other embodiments of this application, the first processing module 302 is used to determine the priority of the first information based on a first factor; wherein the first factor is associated with an event used to trigger or instruct the terminal device to report.
[0157] In other embodiments of this application, the first processing module 302 is used to discard all first information with the same priority.
[0158] In other embodiments of this application, the K sets of first information sent at the Kth reporting time or the Kth available reporting time are the discarded first information.
[0159] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.
[0160] It should be noted that, in the embodiments of this application, if the above-described data transmission method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.
[0161] Embodiments of this application provide a network device that can be used to implement... Figure 2 A data transmission method is provided in the corresponding embodiment, referring to... Figure 4 As shown, network device 400 includes:
[0162] The second receiving module 401 is used to receive first information at the reporting time of the first physical uplink control channel and / or the second physical uplink channel; wherein the first information includes information corresponding to a first event in the component carrier, and the first event is used to trigger or instruct the terminal device to report.
[0163] In other embodiments of this application, the component carriers and / or the first events supported or occurring by the first information in each reporting timing are different.
[0164] In other embodiments of this application, information corresponding to one or more first events is transmitted at each reporting time.
[0165] In other embodiments of this application, the second receiving module 401 is used to receive K sets of first information during K reporting opportunities of the first physical uplink control channel and / or the second physical uplink channel, or during K available reporting opportunities; wherein K is a positive integer.
[0166] In other embodiments of this application, the K groups of first information are grouped together by information corresponding to a component carrier or a group of component carriers. Each group of first information includes information corresponding to all triggered first events in a component carrier or a group of component carriers.
[0167] In other embodiments of this application, K groups of first information are information corresponding to the same first event as a group, and the component carriers corresponding to each group of first information belong to the same component carrier or different component carriers.
[0168] In other embodiments of this application, the K groups of first information include S first events.
[0169] The list of first events obtained by sorting S first events in a predefined order is divided into K groups; or, the S first events are divided into K groups according to the component carrier index priority or the first event index priority.
[0170] In other embodiments of this application, the first information includes one or more of the following:
[0171] Component carrier index;
[0172] The number of component carriers;
[0173] Component carrier group index;
[0174] The number of component carrier groups;
[0175] First event index;
[0176] The number of first events;
[0177] The correlation between component carriers or component carrier groups and the first event;
[0178] The number corresponding to K.
[0179] In other embodiments of this application, the second sending module 402 is used to send second information; wherein the second information includes one or more of the following: the number of uplink control information payloads that the configured second physical uplink channel can carry; the number of component carriers or component carrier groups; and the number of first events.
[0180] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.
[0181] It should be noted that, in the embodiments of this application, if the above-described data transmission method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, ROMs, magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.
[0182] Figure 5 This is a schematic structural diagram of a communication device 500 provided in an embodiment of this application. The communication device can be a terminal device or a network device. Figure 5 The communication device 500 shown includes a processor 510, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0183] Optionally, such as Figure 5 As shown, the communication device 500 may further include a memory 520. The processor 510 can retrieve and run computer programs from the memory 520 to implement the methods described in this embodiment.
[0184] The memory 520 can be a separate device independent of the processor 510, or it can be integrated into the processor 510.
[0185] Optionally, such as Figure 5 As shown, the communication device 500 may also include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.
[0186] The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include antennas, and the number of antennas may be one or more.
[0187] Optionally, the communication device 500 may specifically be a terminal device in the embodiments of this application, and the communication device 500 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0188] Optionally, the communication device 500 may specifically be a network device in the embodiments of this application, and the communication device 500 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0189] This application also provides a computer program product, including a computer program that can be executed by the processor 510 of the communication device 500 to complete the steps described in any of the foregoing methods.
[0190] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be 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 devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.
[0191] As one embodiment, the processor may include one or more general-purpose central processing units (CPUs). Each of these processors may be a single-core processor or a multi-core processor. Here, "processor" may refer to one or more devices, circuits, and / or processing cores used for processing data (e.g., executing instructions).
[0192] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), or flash memory. The volatile memory can be Random Access Memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0193] This application also provides a computer-readable storage medium for storing computer programs.
[0194] Optionally, the computer-readable storage medium can be applied to the terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0195] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0196] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.
[0197] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).
[0198] The data transmission method, terminal device, network device, computer-readable storage medium, and computer program product provided in the embodiments of this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
[0199] It should be understood that the phrases "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiment," "some implementations," or "some embodiments" mentioned throughout the specification mean that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, the phrases "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiment," "some implementations," or "some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.
[0200] Unless otherwise specified, any step in the embodiments of this application performed by the terminal device / network device may be executed by the processor of the terminal device / network device. Unless otherwise specified, the embodiments of this application do not limit the order in which the terminal device / network device performs the following steps. Furthermore, the methods used to process data in different embodiments may be the same or different methods.
[0201] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.
[0202] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.
[0203] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.
[0204] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.
[0205] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.
[0206] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.
[0207] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.
[0208] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.
[0209] The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.
[0210] It should be noted that in the various embodiments involved in this application, all steps or some steps may be performed, as long as a complete technical solution can be formed.
[0211] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A data transmission method, characterized in that, Applied to a terminal device, the method includes: At the reporting timing of the first physical uplink control channel and / or the second physical uplink channel, first information is transmitted; wherein the first information includes information corresponding to a first event in the component carrier, the first event being used to trigger or instruct the terminal device to report.
2. The method according to claim 1, characterized in that, The first information in each reporting time point corresponds to a different component carrier and / or the first event supported or occurring by the component carrier.
3. The method according to claim 1, characterized in that, Each time a report is submitted, information corresponding to one or more first events is transmitted.
4. The method according to claim 1, characterized in that, The transmission of first information at the reporting timing of the first physical uplink control channel and / or the second physical uplink channel includes: The K sets of first information are sent during the K reporting opportunities of the first physical uplink control channel and / or the second physical uplink channel, or during the K available reporting opportunities; Wherein, K is a positive integer.
5. The method according to claim 4, characterized in that, The K groups of first information are grouped together by information corresponding to a component carrier or a group of component carriers. Each group of first information includes information corresponding to all triggered first events in a component carrier or a group of component carriers.
6. The method according to claim 4, characterized in that, The K groups of first information are grouped together by information corresponding to the same first event, and the component carriers corresponding to each group of first information belong to the same component carrier or different component carriers.
7. The method according to claim 4, characterized in that, The K groups of first information include S first events, and the method further includes: Divide the S first events into K groups; Wherein, S is a positive integer.
8. The method according to claim 7, characterized in that, The method of dividing the S first events into K groups includes at least one of the following methods: The S first events are sorted in a predefined order to obtain a list of first events; the S first events are divided into K groups according to the list of first events; wherein, the predefined order includes priority based on component carrier index or priority based on first event index; The S first events are divided into K groups according to the order of priority of component carrier index or priority of first event index.
9. The method according to claim 1, characterized in that, The first information includes one or more of the following: Component carrier index; The number of component carriers; Component carrier group index; The number of component carrier groups; First event index; The number of first events; The correlation between component carriers or component carrier groups and the first event; The number corresponding to K.
10. The method according to claim 4, characterized in that, The method further includes: Receive second information; wherein the second information includes one or more of the following: the number of uplink control information payloads that the configured second physical uplink channel can carry; the number of component carriers or component carrier groups; and the number of first events. Based on the second information, K is determined.
11. The method according to claim 1, characterized in that, The method further includes: Determine the priority of the first information; Based on the aforementioned priority, a portion of the first information is discarded.
12. The method according to claim 11, characterized in that, The granularity of the discarded component carrier includes one of the following: component carrier; first event type; first event in the component carrier.
13. The method according to claim 12, characterized in that, If the granularity of the discarded component carrier is component carrier, the first information corresponding to the first event on multiple component carriers each has a priority. The first information corresponding to different first events with the same component carrier index has the same priority.
14. The method according to claim 12, characterized in that, If the granularity of the discarded event is the first event type, the first information corresponding to the first event on multiple component carriers will each have a priority, and the first information corresponding to the same first event type on different component carriers will have the same priority.
15. The method according to claim 12, characterized in that, If the granularity of the discarded event is the first event in the component carrier, the first information corresponding to the first event on multiple component carriers each has a priority. The first information corresponding to the first event with different first event types has different priorities; the first information corresponding to the first event with different component carrier indices has different priorities.
16. The method according to claim 14 or 15, characterized in that, Determining the priority of the first information includes: The priority of the first information is determined based on a first factor; wherein the first factor is associated with an event used to trigger or instruct the terminal device to report.
17. The method according to any one of claims 13, 14, or 15, characterized in that, The step of discarding a portion of the first information based on the priority includes: Discard all first messages with the same priority.
18. The method according to claim 4, characterized in that, The K sets of first information sent at the K reporting opportunities or the K available reporting opportunities are the first information after being discarded.
19. A data transmission method, characterized in that, Applied to network devices, the method includes: At the reporting timing of the first physical uplink control channel and / or the second physical uplink channel, first information is received; wherein the first information includes information corresponding to a first event in the component carrier, the first event being used to trigger or instruct the terminal device to report.
20. The method according to claim 19, characterized in that, The first information in each reporting time point corresponds to a different component carrier and / or the first event supported or occurring by the component carrier.
21. The method according to claim 19, characterized in that, Each time a report is submitted, information corresponding to one or more first events is transmitted.
22. The method according to claim 19, characterized in that, Receiving the first information during the reporting timing of the first physical uplink control channel and / or the second physical uplink channel includes: The K sets of first information are received during the K reporting opportunities of the first physical uplink control channel and / or the second physical uplink channel, or during the K available reporting opportunities; Wherein, K is a positive integer.
23. The method according to claim 22, characterized in that, The K groups of first information are grouped together by information corresponding to a component carrier or a group of component carriers. Each group of first information includes information corresponding to all triggered first events in a component carrier or a group of component carriers.
24. The method according to claim 22, characterized in that, The K groups of first information are grouped together by information corresponding to the same first event, and the component carriers corresponding to each group of first information belong to the same component carrier or different component carriers.
25. The method according to claim 22, characterized in that, The K groups of first information include S first events. The list of first events obtained by sorting the S first events in a predefined order is divided into K groups; or, the S first events are divided into K groups according to the component carrier index priority or the first event index priority.
26. The method according to claim 19, characterized in that, The first information includes one or more of the following: Component carrier index; The number of component carriers; Component carrier group index; The number of component carrier groups; First event index; The number of first events; The correlation between component carriers or component carrier groups and the first event; The number corresponding to K.
27. The method according to claim 22, characterized in that, The method further includes: Send a second message; wherein the second message includes one or more of the following: the number of uplink control information payloads that the configured second physical uplink channel can carry; the number of component carriers or component carrier groups; and the number of first events.
28. A terminal device, characterized in that, The terminal device includes: The first transmitting module is configured to transmit first information at the reporting timing of the first physical uplink control channel and / or the second physical uplink channel; wherein the first information includes information corresponding to a first event in the component carrier, and the first event is used to trigger or instruct the terminal device to report.
29. A network device, characterized in that, The network device includes: The second receiving module is configured to receive first information during the reporting timing of the first physical uplink control channel and / or the second physical uplink channel; wherein the first information includes information corresponding to a first event in the component carrier, and the first event is used to trigger or instruct the terminal device to report.
30. A terminal device, characterized in that, The terminal device includes: A first memory is used to store executable instructions; a processor is used to implement the data transmission method according to any one of claims 1 to 18 when executing the executable instructions stored in the memory.
31. A network device, characterized in that, The network device includes: A second memory is used to store executable instructions; a second processor is used to implement the data transmission method according to any one of claims 19 to 27 when executing the executable instructions stored in the second memory.
32. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the data transmission method of any one of claims 1 to 18, or to implement the data transmission method of any one of claims 19 to 27.
33. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the data transmission method of any one of claims 1 to 18, or the data transmission method of any one of claims 19 to 27.