An information determination method and a computer-readable storage medium
By determining the priority of the HARQ process, the transmitting end establishes a mapping relationship between the physical layer and the MAC layer, which solves the problem of time domain overlap in the transmission of multiple services in wireless communication and realizes the effective transmission of high-priority services.
Patent Information
- Application Number
- CN202310524899.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-03-28
- Publication Date
- 2025-10-31
- Estimated Expiration
- 2039-03-28
AI Technical Summary
In wireless communication, existing technologies cannot effectively determine the priority of multiple service transmissions, which leads to the inability to guarantee the transmission of high-priority services when time domains overlap.
By determining the priority of the Hybrid Automatic Repeat Request (HARQ) process, the sender establishes a mapping relationship between the physical layer and the media access control (MAC) layer, and transmits service channels and control channels according to the priority of the HARQ process, ensuring the transmission of high-priority services.
During transmission, high-priority services are effectively distinguished and processed, while low-priority service transmission is avoided or adjusted to ensure the successful transmission of high-priority services.
Smart Images

Figure CN116506068B_ABST
Abstract
Description
[0001] This application is a divisional application of patent application number 201910246492.5 (the original application was filed on March 28, 2019, and the invention was entitled "A method, apparatus and computer-readable storage medium for determining transmission priority"). Technical Field
[0002] This application relates to wireless communication networks, and for example to an information determination method and a computer-readable storage medium. Background Technology
[0003] During service interaction between a User Equipment (UE) and a base station, multiple services may need to be transmitted simultaneously due to their different requirements. Therefore, determining transmission priority is crucial to avoid temporal overlap during service interaction. However, there is currently no detailed discussion on how to determine transmission priority. Summary of the Invention
[0004] This application provides a method, apparatus, and computer-readable storage medium for determining transmission priority, which can determine the priority of transmission to ensure the transmission of high-priority services when the preparation or transmission processes of at least two transmissions overlap.
[0005] This application provides a method for determining transmission priority, including:
[0006] The sending end determines the priority of the Hybrid Automatic Repeat reQuest (HARQ) process;
[0007] The transmitting end transmits at least one of the traffic channel and control channel according to the priority of the HARQ process.
[0008] This application provides an apparatus for determining transmission priority, comprising:
[0009] The priority determination module is configured to determine the priority of the Hybrid Automatic Repeat Request (HARQ) process.
[0010] The transmission module is configured to transmit at least one of the service channel and the control channel according to the priority of the HARQ process.
[0011] This application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the methods described in this application.
[0012] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description
[0013] Figure 1 This is a schematic diagram illustrating the temporal overlap between URLLC and eMBB transmissions in one embodiment.
[0014] Figure 2 A flowchart illustrating a method for determining transmission priority according to one embodiment;
[0015] Figure 3 A schematic diagram of a device for determining transmission priority is provided in one embodiment;
[0016] Figure 4 A schematic diagram of another device for determining transmission priority provided in one embodiment;
[0017] Figure 5 This is a schematic diagram of the structure of a base station provided in one embodiment. Detailed Implementation
[0018] The embodiments of this application will be described below with reference to the accompanying drawings.
[0019] With the development of wireless communication technology, Ultra-Reliable and Low-Latency Communications (URLLC) transmission has emerged. Compared with Enhanced Mobile Broadband (eMBB) transmission, URLLC transmission requires higher reliability and timeliness, such as very stringent latency requirements, demanding that transmission be completed within a certain time. eMBB transmission, on the other hand, has less stringent latency requirements and can complete transmission through multiple retransmissions.
[0020] In some scenarios, a UE may support both eMBB and URLLC transmissions. Since eMBB and URLLC transmissions have different requirements, their time domains may overlap. For example, when a UE's eMBB needs to be scheduled, the base station sends eMBB transmission grant information (i.e., downlink control information (DCI) – for services scheduled via grant information, this is called dynamic grant transmission) in slot n to the UE to schedule the eMBB transmission in slot n or a subsequent slot (e.g., via the Physical Downlink Shared Channel (PDSCH) when scheduling downlink services, and via the Physical Uplink Shared Channel (PUSCH) when scheduling uplink services). After the eMBB transmission grant information is sent, if there is a sudden demand for URLLC transmission, the base station sends URLLC transmission grant information to the UE to schedule the URLLC transmission. (It's also possible that this URLLC transmission uses a configured grant method (also known as semi-static scheduling of service transmission), meaning that this transmission uses previously configured information and does not require DCI scheduling, i.e., no grant information is needed; this grant method is also called configured grant). Due to the latency requirements of URLLC transmission, it is very likely that the URLLC transmission and the previously scheduled eMBB transmission will overlap in the time domain. For example, Figure 1 This is a schematic diagram illustrating temporal overlap between URLLC and eMBB transmissions, provided as an embodiment. Figure 1 As shown in (a), both eMBB and URLLC transmissions use dynamic authorization, resulting in temporal overlap between them. Figure 1 As shown in (b), the authorization method for eMBB transmission is dynamic authorization, while the authorization method for URLLC transmission is configuration authorization. In this case, the transmission times of eMBB and URLLC overlap. Figure 1 As shown in (c), the authorization method for eMBB transmission is configuration authorization, while the authorization method for URLLC transmission is dynamic authorization. In this case, the transmission of eMBB and URLLC overlaps in the time domain. Figure 1 (a) Figure 1 (b) and Figure 1As can be seen in (c), the URLLC transmission and the eMBB transmission overlap in the time domain. This is because the URLLC transmission has the characteristic of burstiness. When the base station schedules the eMBB transmission, it does not find the scheduling requirement of the URLLC transmission. However, after the eMBB transmission is scheduled, the transmission requirement of the URLLC transmission is found. Since the URLLC transmission cannot be delayed, it is scheduled to be transmitted immediately, which leads to the conflict between the two transmissions.
[0021] Some companies have proposed that for services with overlapping time domains, the physical layer can select or execute corresponding drop or puncturing transmissions based on the transmission priority. However, the physical layer in related technologies cannot identify which service type a transport block (TB) corresponds to, so it cannot identify the priority of a service transmission.
[0022] This application provides a method, apparatus, and computer-readable storage medium for determining transmission priorities. These methods are capable of determining transmission priorities to ensure the transmission of high-priority services when the preparation or transmission processes of at least two transmissions overlap. The method for determining transmission priorities mentioned in this application is applicable not only to dynamically authorized transmissions but also to configuration-authorized transmissions; this application does not impose any limitations on this application.
[0023] Figure 2 A flowchart illustrating a method for determining transmission priority in one embodiment is provided, as follows: Figure 2 As shown, the method provided in this embodiment is applicable to the sending end, and the method includes the following steps.
[0024] S110. The sending end determines the priority of the HARQ process.
[0025] Methods for the sender to determine the priority of the HARQ process may include: the sender's Media Access Control (MAC) layer determining the priority of the HARQ process and notifying the sender's physical layer of the priority of the HARQ process.
[0026] In one embodiment, the MAC layer of the transmitting end first determines the priority of the MAC PDU based on the highest priority of the logical channel (LCH) contained in the Media Access Control Protocol Data Unit (MAC PDU) carried by the HARQ process; then, the MAC layer of the transmitting end determines the priority of the HARQ process based on the priority of the MAC PDU.
[0027] Since the LCH is configured with a priority, the MAC PDU can obtain a corresponding priority based on the highest priority of the LCH it contains. For example, the MAC layer at the sending end can directly assign the highest priority of the LCH contained in the MAC PDU to the MAC PDU; or, the MAC layer at the sending end can map the highest priority of the LCH contained in the MAC PDU according to the first convention to obtain the priority of the MAC PDU.
[0028] Once a MAC PDU is configured with a priority, the HARQ process carrying that MAC PDU can obtain a corresponding priority based on the MAC PDU's priority. For example, the sending end's MAC layer can directly assign the MAC PDU's priority to the HARQ process; or, the sending end's MAC layer can map the MAC PDU's priority according to a second convention to obtain the HARQ process's priority.
[0029] The first and second agreed-upon mappings mentioned above can be the same mapping or different mappings. This application does not impose specific restrictions on this.
[0030] S120. The transmitting end transmits at least one of the service channel and control channel according to the priority of the HARQ process.
[0031] At the physical layer, when the sending end transmits a TB, a HARQ process is used to carry a TB (also called service transmission or service data; TB is the name of the MAC PDU in the MAC layer corresponding to the physical layer). The physical layer determines the priority of the TB carried by the HARQ process according to the priority of the HARQ process notified by the MAC layer.
[0032] In one embodiment, the transmitting end transmitting at least one of the service channel and control channel according to the priority of the HARQ process may include any one of the following three scenarios.
[0033] Scenario 1: The sending end determines the priority of service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process, and uses the priority of service transmission to determine the transmission of service transmission.
[0034] In one embodiment, the method by which the transmitting end determines the priority of service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process may include: the transmitting end directly assigning the priority of the HARQ process to the service transmission in the service channel carried by the HARQ process; or, the transmitting end mapping the priority of the HARQ process according to a third agreement to obtain the priority of service transmission in the service channel carried by the HARQ process.
[0035] Scenario 2: The sending end determines the priority of the Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process, and uses the priority of the HARQ-ACK codebook to determine the transmission of the HARQ-ACK codebook.
[0036] In one embodiment, the transmitting end determines the priority of the HARQ-ACK codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process. This includes: the transmitting end directly assigning the priority of the HARQ process to the HARQ-ACK codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process; or, the transmitting end mapping the priority of the HARQ process according to a third agreement to obtain the priority of the HARQ-ACK codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process.
[0037] Scenario 3: The transmitting end determines the priority of service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process, and determines the priority of the HARQ-ACK codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process. Then, it uses the priority of service transmission and the priority of HARQ-ACK codebook to determine the transmission of service transmission and HARQ-ACK codebook.
[0038] The aforementioned third contractual mapping may be the same as or different from the first and second contractual mappings. This application embodiment does not impose specific restrictions on this.
[0039] In this way, the sending end can select high-priority services for processing when at least two preparation or transmission processes overlap, thus ensuring the transmission of high-priority services.
[0040] In one embodiment, for at least two service transmissions, if the first service transmission and the second service transmission overlap in the time domain or have processing conflicts: the sending end discards the second service transmission, or cancels the transmission of the second service transmission, or partially discards the second service transmission, or partially transmits the second service transmission, wherein the sending end determines that the priority of the first service transmission is higher than the priority of the second service transmission based on the HARQ process priorities that respectively carry the first service transmission and the second service transmission.
[0041] In this embodiment, the time-domain processing conflict between the first service transmission and the second service transmission means that: a UE needs to process the first service transmission and the second service transmission simultaneously, but the UE has poor capabilities and can only process one service transmission; or a UE needs to prepare the first service transmission and the second service transmission simultaneously, but the UE has poor capabilities and can only prepare one service transmission.
[0042] In one embodiment, for at least two service transmissions, where the first service transmission and the second service transmission overlap in the time domain, and the priority of the HARQ process carrying the first service transmission is equal to the priority of the HARQ process carrying the second service transmission: Both the first and second service transmissions are granted dynamic authorization, with the first service transmission having a higher priority than the second service transmission, wherein the dynamic authorization of the first service transmission is later than the dynamic authorization of the second service transmission; or, both the first and second service transmissions are granted dynamic authorization and configuration authorization, with the first service transmission having a higher priority than the second service transmission; or, both the first and second service transmissions are granted configuration authorization, with the first service transmission having a higher priority than the second service transmission, wherein the transmission of the first service transmission occurs earlier than the transmission of the second service transmission.
[0043] In one embodiment, HARQ-ACKs corresponding to service transmissions with the same HARQ process priority form a HARQ-ACK codebook; or, HARQ-ACKs corresponding to service transmissions with the same priority form a HARQ-ACK codebook, wherein the priority of the service transmission is determined according to the priority of the HARQ process carrying the service transmission; or, HARQ-ACKs corresponding to service transmissions carried by HARQ processes with a priority difference not exceeding a preset level form a HARQ-ACK codebook; or, HARQ-ACKs corresponding to service transmissions with a priority difference not exceeding a preset level form a HARQ-ACK codebook, wherein the priority of the service transmission is determined according to the priority of the HARQ process carrying the service transmission.
[0044] In one embodiment, for at least two service transmissions, if the physical uplink control channel (PUCCH) time domains of the HARQ-ACK codebooks corresponding to the first service transmission and the HARQ-ACK codebooks corresponding to the second service transmission overlap, and the HARQ-ACK codebooks corresponding to the first service transmission and the second service transmission are allowed to be reused: the HARQ-ACK codebook corresponding to the first service transmission is placed before the HARQ-ACK codebook corresponding to the second service transmission, wherein the priority of the first service transmission is higher than the priority of the second service transmission; or the priority of the HARQ process carrying the first service transmission is higher than the priority of the HARQ process carrying the second service transmission.
[0045] In one embodiment, for at least two service transmissions, if the PUCCH time domain of the HARQ-ACK codebook corresponding to the first service transmission and the HARQ-ACK codebook corresponding to the second service transmission overlaps, and the priority of the HARQ process carrying the first service transmission is higher than the priority of the HARQ process carrying the second service transmission: the sending end cancels the PUCCH transmission of the HARQ-ACK codebook corresponding to the second service transmission.
[0046] The following are some exemplary embodiments to illustrate the method for determining transmission priority provided in this application and its technical effects.
[0047] In the first exemplary embodiment, the overall idea of the method for determining transmission priority provided in this application can be summarized as follows: the MAC layer at the sending end determines the priority of the HARQ process and notifies the physical layer of the HARQ process's priority. The physical layer uses the priority of the HARQ process to determine the priority of the service transmission carried by the HARQ process.
[0048] The steps for the MAC layer to determine the priority of the HARQ process are as follows: When generating a MAC PDU, the MAC layer determines the priority of the MAC PDU according to the highest priority of the LCH contained in the MAC PDU, and then determines the priority of the HARQ process carrying the MAC PDU according to the priority of the MAC PDU. For example, since the LCH is configured with a priority, the MAC PDU can obtain a corresponding priority based on the highest priority of the LCH it contains (e.g., directly assigning the highest priority of the LCH contained in the MAC PDU to the MAC PDU, or obtaining the priority of the MAC PDU by using a pre-defined mapping of the highest priority of the LCH). The priority of the MAC PDU can be directly assigned to the HARQ process carrying the MAC PDU, or the priority of the MAC PDU can be obtained by using a pre-defined mapping of the priority of the MAC PDU.
[0049] At the physical layer, when the sending end transmits a TB (Transaction Transfer), a HARQ process carries one TB (also called service transmission or service data; TB is the physical layer terminology corresponding to the MAC PDU in the MAC layer). The physical layer determines the priority of the TB carried by the HARQ process according to the priority of the HARQ process notified by the MAC layer. For example, the priority of the HARQ process can be directly used as the priority of the TB carried by that HARQ process, or the priority of the TB can be obtained through an agreed mapping. Here, which HARQ process carries which TB (the MAC layer calls it a MAC PDU) is determined and notified to the physical layer by the MAC layer, so the MAC layer knows the correspondence between the HARQ process and the TB carried by that HARQ process. The physical layer determines the priority of the TB carried by the HARQ process according to the priority of the HARQ process, including the initial transmission and retransmission of the TB. When the TB is successfully transmitted, the priority of the HARQ process becomes invalid. When the HARQ process transmits a new TB again, the MAC layer will reassign the priority of the HARQ process according to the highest priority of the LCH in the newly transmitted MAC PDU. When two HARQ processes have the same priority, if the data transfer objects (TBs) carried by the two HARQ processes overlap in the time domain during transmission, and it is necessary to determine the priority of the TBs carried by the two HARQ processes, then the retransmitted TB can be considered to have a higher priority. If both are initial transmissions, the later-scheduled TB is considered to have a higher priority; if both are retransmissions, the TB with more retransmissions has a higher priority. Alternatively, the sender needs to avoid time domain overlap between multiple transmissions with the same HARQ process priority. For example, when the sender plans a transmission, if it finds that it will overlap in the time domain with another transmission with the same HARQ process priority, the sender will postpone the planned transmission.
[0050] In this embodiment, when the physical layer transmits a TB, it always uses a HARQ process bound to the TB so that the TB can be HARQ merged according to the HARQ process during retransmission. That is, the retransmitted TB and the original TB use the same HARQ process and are indicated as retransmissions in the DCI so that the receiving end can perform HARQ merging.
[0051] After the physical layer obtains the priority of the HARQ process, when the physical layer performs data transmission, if multiple data transmission channels overlap in the time domain, the priority of multiple data transmissions (channels) can be determined according to the priority of the HARQ processes of these data transmissions. This ensures that high-priority data transmission is carried out, while low-priority data transmissions are dropped, canceled, or partially transmitted. In this way, the physical layer can determine the priority of data transmission carried by the HARQ process using the HARQ process priority.
[0052] In one embodiment, the problem solved by the method for determining transmission priority provided in this application can also be solved by another approach:
[0053] The MAC layer assigns a priority to a MAC PDU and notifies the physical layer of this priority. The physical layer introduces a priority indication field into the DCI information to indicate the priority of the service transmission corresponding to the DCI (i.e., the transmission of the MAC PDU at the physical layer). The priority indication field's value is determined according to the priority of the MAC PDU notified by the MAC layer, thus describing the priority of the service transmission corresponding to the DCI.
[0054] Here, the MAC layer determines the priority of a MAC PDU in the same manner as described above and notifies the physical layer of the determined priority. The physical layer converts this priority information into the priority of the service transmission when the MAC PDU is transmitted at the physical layer and notifies the UE in the DCI that schedules the service transmission. In other embodiments of this application, the priority of the service transmission indicated in the DCI can also be used for corresponding processing, for example, replacing the priority of the HARQ process in other embodiments.
[0055] In one embodiment, the present application embodiment may further include the following process:
[0056] At the MAC layer, the sending end establishes a mapping relationship between the priorities of the HARQ process and the logical channel (or MAC PDU), enabling the HARQ process to reflect the priority of the MAC PDU it carries. During the HARQ process processing at the MAC layer, the sending end stores the priority of the logical channel (or MAC PDU) associated with the HARQ process (here, the HARQ process carries the data in the logical channel (or MAC PDU)).
[0057] In the HARQ process handling at the MAC layer, the sending end notifies the physical layer of the HARQ process's priority. In other words, when the sending end generates a transport block (TB) for transmission, it notifies the physical layer of the HARQ process's priority during the HARQ process handling at the MAC layer. Here, the HARQ process is the one carrying the TB. This way, the physical layer learns the priority of the HARQ process and uses it in its service or control information transmissions.
[0058] The above method can also be used for retransmitted TB.
[0059] For a retransmitted TB, the HARQ process of the retransmitted TB has the same HARQ process priority as the original TB. Alternatively, for a retransmitted TB, considering that the TB is already a retransmission, the HARQ process priority of the retransmitted TB is set higher than the HARQ process priority of the original TB. Or, if two HARQ processes have the same priority, and one HARQ process carries a retransmitted TB while the other HARQ process carries an original TB, then the HARQ process carrying the retransmitted TB has a higher priority.
[0060] In the second exemplary embodiment, the second exemplary embodiment describes how to use HARQ process priority to solve the problem when there is time-domain overlap in the channels of multiple service transmissions for a UE.
[0061] The existence of time-domain overlap between multiple service transmission channels can occur in, but is not limited to, the following scenarios:
[0062] Scenario 1: There is time domain overlap between downlink service transmissions with dynamic authorization (including partial or complete time domain overlap, the same below).
[0063] Scenario 2: There is time domain overlap between uplink service transmissions with configuration authorization and uplink service transmissions with dynamic authorization.
[0064] Scenario 3: There is temporal overlap between dynamically authorized uplink service transmissions and dynamically authorized uplink service transmissions.
[0065] Scenario 4: There is time domain overlap between configuration-authorized uplink service transmissions and configuration-authorized uplink service transmissions.
[0066] In one embodiment, the aforementioned uplink service transmission can also be replaced by uplink control channel transmission, which further includes:
[0067] Scenario 5: There is time domain overlap between uplink control channel transmission and uplink service transmission with dynamic authorization.
[0068] Scenario 6: There is time domain overlap between uplink control channel transmission and configuration authorization uplink service transmission.
[0069] Scenario 7: There is time domain overlap between uplink control channel transmission and uplink control channel transmission.
[0070] It can also include the following scenarios:
[0071] Scenario 8: There is time domain overlap between downlink service transmissions with configuration authorization and downlink service transmissions with configuration authorization.
[0072] For scenarios 1-4 and 8 above, when there is temporal overlap in service transmissions, the priority of the HARQ process carrying the service can be directly used as the priority of the transmitted service to determine the service transmission priority. Consequently, high-priority service transmissions are transmitted normally, while low-priority service transmissions are either entirely canceled / dropped, or partially canceled / dropped (i.e., some low-priority service transmissions are punctured, for example, low-priority service transmissions at temporal overlap locations are punctured, thus allowing only partial transmission of low-priority services).
[0073] In scenarios 5 and 6 above, there is temporal overlap between uplink control channel transmission and uplink service transmission. In this case, the priority of the uplink control channel transmission is determined by the priority of the HARQ process of the service transmission corresponding to that uplink control channel. For example, if the uplink control channel transmission carries a HARQ-ACK for service A, then the priority of the uplink control channel transmission is determined by the priority of the HARQ process for service A. Thus, in scenarios 5 and 6 above, the priority of the two transmissions can still be determined by the priority of the HARQ process. Similarly, the high-priority transmission can be transmitted normally, while the low-priority transmission is canceled / dropped entirely, or the low-priority transmission is partially canceled / dropped (i.e., some low-priority service transmissions are punctured, for example, low-priority service transmissions at temporal overlap locations are punctured, so that low-priority service transmissions can only be partially transmitted).
[0074] In one embodiment, after distinguishing the priorities of the two transmissions, if the uplink control channel transmission has a high priority and the uplink service transmission has a low priority, then the uplink control information (UCI) in the uplink control channel transmission can also be carried in the uplink service transmission. In this case, according to the agreed rule A, the UCI is carried in the uplink service transmission and sent (New Radio Access Technology (NR) 38.212vf40 has a corresponding mechanism for this, but this mechanism is applicable when the two transmissions have the same priority; rule A here is more applicable when the uplink control channel transmission has a higher priority than the uplink service transmission), and the uplink control channel transmission is cancelled. If the priority of the uplink control channel transmission is lower than the priority of the uplink service transmission, the lower-priority transmission is discarded. Alternatively, according to the agreed rule B, the UCI in the uplink control channel transmission can be carried in the uplink service transmission and sent. Rule A here, compared to the mechanisms in related technologies, additionally includes: when calculating the resources used for uplink traffic transmission for UCI, if the maximum limit of uplink traffic transmission resources configured by the base station is exceeded (and not all uplink traffic transmission resources are used), then the actually calculated UCI resources are used as the resources for the final transmission of UCI. Rule B, compared to the mechanisms in related technologies, additionally includes: setting the UCI repetition factor beta value in uplink traffic transmission to be less than 1 or even equal to 0.
[0075] For scenario 7 above, the uplink control channel transmissions overlap in the time domain. The priority of the uplink control channel is still determined in the above manner, i.e., the priority of the HARQ process corresponding to the service transmission of the uplink control channel. For low-priority uplink control channels, the transmission is still handled by canceling the transmission of the low-priority uplink control channel entirely or partially. Alternatively, rule C is adopted, where the UCIs of the two uplink control channels are multiplexed into a new uplink control channel for transmission, and the original uplink control channels are discarded (if the new uplink control channel is one of the original uplink control channels, the remaining original uplink control channels are discarded). Rule C includes: when multiplexing in a PUCCH, the code rate of the multiplexed PUCCH is not higher than the code rate of the high-priority PUCCH among the original multiple PUCCHs. The end position of the multiplexed PUCCH is not later than the end position of the high-priority PUCCH among the original multiple PUCCHs.
[0076] In the third exemplary embodiment, for two transmission channels with overlapping time domains, if the transmission channel with higher priority among multiple transmission channels can be directly determined by the HARQ process priority method in the above embodiments, then the process is executed in the manner described in the above embodiments. If the two transmissions have the same priority (this includes those determined by the HARQ process priority in the above embodiments, as well as those determined by other methods, such as adding a bit field in the DCI to indicate the priority of the corresponding transmission channel, which is also being discussed), then the processing is carried out in the manner described in this exemplary embodiment.
[0077] Refer to scenarios 1-4 in the second exemplary implementation:
[0078] For scenarios 1 and 3, the base station and UE agree that: for a UE, when two dynamically authorized service transmissions overlap in the time domain and the two service transmissions have the same priority, the later service transmission of the dynamic authorization information is regarded as having a higher priority and is processed according to the higher priority service transmission in the above embodiment.
[0079] For scenario 2, the base station and UE agree that: for a UE, when the configured authorized uplink service transmission and the dynamically authorized uplink service transmission overlap in the time domain and the two service transmissions have the same priority, then: the dynamically authorized uplink service transmission is regarded as having a higher priority and is processed according to the high-priority service transmission in the above embodiment.
[0080] For scenario 4, the base station and UE agree that: for a UE, when the configured authorized uplink service transmission and the configured authorized uplink service transmission have time domain overlap and the two service transmissions have the same priority, then: the service transmission that starts transmitting first is regarded as having higher priority and is processed according to the high-priority service transmission in the above embodiment.
[0081] In the fourth exemplary embodiment, another use of the priority of the HARQ process is given, mainly to distinguish different service transmission types, thereby facilitating the formation of the HARQ-ACK codebook.
[0082] For example, it is used to distinguish between URLLC and eMBB service transmissions. When forming a HARQ-ACK codebook, HARQ-ACKs corresponding to the same type of service transmissions are allowed to form a single HARQ-ACK codebook; or, for service transmissions with different priorities, if the priority difference does not exceed P levels (P is a given value), the HARQ-ACKs corresponding to these service transmissions are allowed to form a single HARQ-ACK codebook. This is because service transmissions with similar priorities also have similar performance requirements, so they are allowed to form a single HARQ-ACK codebook.
[0083] For example, taking URLLC and eMBB service transmission types as examples, the HARQ process priority can also be set to two corresponding levels, one for URLLC and one for eMBB services. The acquisition of HARQ process priority is the same as in the previous embodiment. Since service transmission requirements always go from the MAC layer to the physical layer, when the MAC layer prepares the MAC PDU, the priority of the MAC PDU is determined according to the priority of the LCH contained in the MAC PDU, and the corresponding HARQ process carrying the MAC PDU is determined accordingly. The priority of the HARQ process carrying the MAC PDU is then determined based on the priority of the MAC PDU. For ease of labeling, the HARQ process can be set to two levels, since only two types of services need to be distinguished. In one embodiment, the priorities of the previous embodiment can also be used. In this case, it is only necessary to predefine which priorities correspond to URLLC services and which priorities correspond to eMBB services, that is, to establish a corresponding mapping table between HARQ process priority (i.e., MAC PDU priority) and service type. If more service types need to be distinguished, the above example can be extended, but the basic principle remains the same.
[0084] At the physical layer, the UE determines whether the HARQ-ACK corresponding to each service transmission belongs to a single HARQ-ACK codebook based on the priority of the HARQ process corresponding to each service transmission. HARQ-ACKs of service transmissions with the same HARQ process priority are allowed to be included in the same HARQ-ACK codebook. If the PUCCH time domains of the HARQ-ACK codebooks corresponding to two service transmissions overlap, and the HARQ-ACK codebooks of service transmissions with different HARQ process priorities are allowed to be multiplexed together and transmitted through a single PUCCH, the HARQ-ACK codebook corresponding to the higher priority is placed before the HARQ-ACK codebook corresponding to the lower priority. Alternatively, rule C set in scenario 7 of the second exemplary embodiment can be used. Only when rule C is satisfied will the HARQ-ACK codebooks corresponding to two service transmissions be multiplexed together. If rule C is not satisfied, they will not be multiplexed, and the lower priority HARQ-ACK codebook will be discarded.
[0085] In one embodiment, the base station and the UE agree to form a HARQ-ACK codebook for HARQ-ACKs of service transmissions with similar service transmission priorities. For example, a predefined method is used to specify which service transmission priorities correspond to which HARQ-ACKs are allowed to form a single HARQ-ACK codebook. The base station and the UE always form a single HARQ-ACK codebook for the HARQ-ACKs corresponding to multiple service transmissions with different priorities (but according to the predetermined rules, the HARQ-ACKs of these priority service transmissions are allowed to form a single HARQ-ACK codebook). This method can solve the problem of too many independent HARQ-ACK codebooks due to too many service transmission priorities. The service transmission priority here can be determined by the priority of the HARQ process carrying the service transmission, or the service transmission priority obtained through other means, or the priority of the HARQ process carrying the service transmission.
[0086] In the fifth exemplary embodiment, another use of the priority of the HARQ process is given.
[0087] In related technologies, a HARQ-ACK can be multiplexed within a single PUSCH for transmission. That is, for a UE, if the PUCCH resources carrying the HARQ-ACK overlap with the PUSCH resources, or if no PUCCH resources are configured, the HARQ-ACK will be multiplexed within the PUSCH for transmission. Currently, due to the introduction of URLLC service transmission, which requires high reliability, multiplexing a HARQ-ACK from an eMBB service transmission within a URLLC service transmission could potentially degrade the reliability of the URLLC service transmission. Therefore, methods are needed to protect the URLLC service transmission in this situation.
[0088] To address the above issues, the following solutions are proposed.
[0089] For a UE, when the HARQ-ACK codebook needs to be multiplexed for transmission in the PUSCH, the UE handles it as follows:
[0090] The priority of the HARQ-ACK codebook is determined by the priority of the HARQ process containing the corresponding PDSCH. The priority of the PUSCH is also determined by the priority of the HARQ process containing the PUSCH.
[0091] The UE determines the transmission of the HARQ-ACK codebook and PUSCH based on a comparison of the HARQ-ACK codebook and PUSCH priorities: When the PUSCH priority is higher than the HARQ-ACK codebook priority, the HARQ-ACK codebook is prohibited from being multiplexed in the PUSCH (at this time, the base station sets the beta value in the uplink grant corresponding to the PUSCH to 0). When the PUSCH priority is lower than the HARQ-ACK codebook priority, the HARQ-ACK codebook is multiplexed in the PUSCH for transmission.
[0092] For a base station, when the HARQ-ACK codebook is multiplexed and transmitted in the PUSCH multiplexing, the base station processes it as follows:
[0093] Configure the priority of the HARQ-ACK codebook, i.e., configure the priority of the HARQ process where the PDSCH corresponding to the HARQ-ACK codebook resides. Configure the priority of the PUSCH, i.e., configure the priority of the HARQ process where the PUSCH resides. The base station receives the HARQ-ACK codebook and PUSCH by comparing their priorities: when the configured PUSCH priority is higher than the HARQ-ACK codebook priority, the base station determines that the HARQ-ACK codebook is discarded and the PUSCH is transmitted (i.e., the base station believes that the UE did not multiplex the HARQ-ACK codebook in the PUSCH, but only sent the PUSCH). When the configured PUSCH priority is lower than the HARQ-ACK codebook priority, the base station determines that the HARQ-ACK codebook is multiplexed in the PUSCH for transmission.
[0094] In the sixth exemplary implementation, the sixth exemplary implementation addresses the problem of how the UE generates HARQ-ACK information for a set of time-overlapping PDSCHs when the UE is capable of simultaneously receiving and processing multiple time-domain overlapping Physical Downlink Shared Channels (PDSCHs) and the UE is configured with a semi-static HARQ-ACK codebook.
[0095] The method includes the following: Assuming that for a UE, the base station has configured candidate PDSCH resources for that UE, and there are M time-overlapping candidate PDSCHs in a time slot or sub-slot. Assuming the UE has the capability to simultaneously receive and process N time-overlapping PDSCHs. When the UE is configured with a semi-static HARQ-ACK codebook, the UE and the base station determine the HARQ-ACK information (or HARQ-ACK codebook information) corresponding to the M time-overlapping candidate PDSCHs according to the following rules:
[0096] If M≤N, the UE and the base station will determine that M HARQ-ACK messages will be generated;
[0097] If M > N, the UE and the base station determine that N HARQ-ACK messages are formed. In one embodiment, the PDSCH corresponding to the N HARQ-ACK messages includes the first N PDSCHs with higher priority among the M overlapping time-domain PDSCHs. For candidate PDSCHs with the same priority, the PDSCH with an earlier (or later) start symbol position is regarded as having higher priority.
[0098] The above method can be summarized as follows: The base station and the UE agree that if the UE is capable of simultaneously processing N time-domain overlapping PDSCHs, then for a set of M time-domain overlapping PDSCHs, the UE determines min(N,M) HARQ-ACK information or min(N,M) HARQ-ACK codebooks when using a semi-static HARQ-ACK codebook. Here, for the semi-static HARQ-ACK codebook, the number of HARQ-ACK information determined for a set of M time-domain overlapping PDSCHs is unrelated to the actual number of PDSCHs scheduled by the base station for the UE.
[0099] Figure 3 This is a schematic diagram of a device for determining transmission priority according to one embodiment. This device can be configured in a transmitting end, such as... Figure 3 As shown, it includes: a priority determination module 10, configured to determine the priority of the Hybrid Automatic Repeat Request (HARQ) process; and a transmission module 11, configured to transmit at least one of the service channel and control channel according to the priority of the HARQ process.
[0100] The device for determining transmission priority provided in this embodiment is used to implement... Figure 2 The method for determining transmission priority in the illustrated embodiment is similar in principle and technical effect to the device for determining transmission priority provided in this embodiment, and will not be described again here.
[0101] In one embodiment, the priority determination module 10 is further configured to determine the priority of service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process; the transmission module 11 is configured to determine the transmission of service transmission using the priority of service transmission; or, the priority determination module 10 is further configured to determine the priority of the hybrid automatic repeat request-acknowledgment information (HARQ-ACK) codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process; the transmission module 11 is configured to determine the transmission of the HARQ-ACK codebook using the priority of the HARQ-ACK codebook; or, the priority determination module 10 is further configured to determine the priority of service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process, and to determine the priority of the HARQ-ACK codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process; the transmission module 11 is configured to determine the transmission of service transmission and the transmission of the HARQ-ACK codebook using the priority of service transmission and the priority of the HARQ-ACK codebook.
[0102] In one embodiment, the priority determination module 10 is configured to determine the priority of the HARQ process by means of the Media Access Control (MAC) layer determining the priority of the HARQ process and notifying the physical layer of the sending end of the priority of the HARQ process.
[0103] In one embodiment, the priority determination module 10 is configured to determine the priority of the HARQ process by the Media Access Control (MAC) layer in the following manner: the MAC layer determines the priority of the MAC PDU based on the highest priority of the Logical Channel (LCH) contained in the Media Access Control Protocol Data Unit (MAC PDU) carried by the HARQ process; the MAC layer determines the priority of the HARQ process based on the priority of the MAC PDU.
[0104] In one embodiment, the priority determination module 10 is configured to determine the priority of the MAC PDU based on the highest priority of the LCH contained in the MAC PDU carried by the HARQ process in the following manner: the MAC layer assigns the highest priority of the LCH contained in the MAC PDU to the MAC PDU; or, the MAC layer maps the highest priority of the LCH contained in the MAC PDU according to a first convention to obtain the priority of the MAC PDU.
[0105] In one embodiment, the priority determination module 10 is configured to enable the MAC layer to determine the priority of the HARQ process based on the priority of the MAC PDU in the following manner: the MAC layer assigns the priority of the MAC PDU to the HARQ process; or, the MAC layer maps the priority of the MAC PDU according to a second convention to obtain the priority of the HARQ process.
[0106] In one embodiment, the priority determination module 10 is configured to determine the priority of service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process in the following manner: assigning the priority of the HARQ process to the service transmission in the service channel carried by the HARQ process; or, mapping the priority of the HARQ process according to a third convention to obtain the priority of service transmission in the service channel carried by the HARQ process.
[0107] In one embodiment, the priority determination module 10 is configured to determine the priority of the HARQ-ACK codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process based on the priority of the HARQ process in the following manner: assigning the priority of the HARQ process to the HARQ-ACK codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process; or, mapping the priority of the HARQ process according to a third convention to obtain the priority of the HARQ-ACK codebook in the control channel corresponding to the service transmission in the service channel carried by the HARQ process.
[0108] In one embodiment, combined with Figure 3 , Figure 4 A schematic diagram of another device for determining transmission priority is provided in one embodiment, as shown below. Figure 4 As shown, the device also includes a processing module 12.
[0109] For at least two service transmissions, where the first and second service transmissions overlap in the time domain or have processing conflicts:
[0110] The processing module 12 is configured to discard the second service transmission, cancel the transmission of the second service transmission, partially discard the second service transmission, or partially transmit the second service transmission. The priority determination module is further configured to determine that the priority of the first service transmission is higher than the priority of the second service transmission based on the priority of the HARQ process that carries the first service transmission and the second service transmission respectively.
[0111] In one embodiment, for at least two service transmissions, where the first service transmission and the second service transmission overlap in the time domain, and the priority of the HARQ process carrying the first service transmission is equal to the priority of the HARQ process carrying the second service transmission: Both the first and second service transmissions are granted dynamic authorization, with the first service transmission having a higher priority than the second service transmission, wherein the dynamic authorization of the first service transmission is later than the dynamic authorization of the second service transmission; or, both the first and second service transmissions are granted dynamic authorization and configuration authorization, with the first service transmission having a higher priority than the second service transmission; or, both the first and second service transmissions are granted configuration authorization, with the first service transmission having a higher priority than the second service transmission, wherein the transmission of the first service transmission occurs earlier than the transmission of the second service transmission.
[0112] In one embodiment, HARQ-ACKs corresponding to service transmissions with the same HARQ process priority form a HARQ-ACK codebook; or, HARQ-ACKs corresponding to service transmissions with the same priority form a HARQ-ACK codebook, wherein the priority of the service transmission is determined according to the priority of the HARQ process carrying the service transmission; or, HARQ-ACKs corresponding to service transmissions carried by HARQ processes with a priority difference not exceeding a preset level form a HARQ-ACK codebook; or, HARQ-ACKs corresponding to service transmissions with a priority difference not exceeding a preset level form a HARQ-ACK codebook, wherein the priority of the service transmission is determined according to the priority of the HARQ process carrying the service transmission.
[0113] In one embodiment, for at least two service transmissions, if the physical uplink control channel (PUCCH) time domains of the HARQ-ACK codebooks corresponding to the first service transmission and the HARQ-ACK codebooks corresponding to the second service transmission overlap, and the HARQ-ACK codebooks corresponding to the first service transmission and the second service transmission are allowed to be reused: the HARQ-ACK codebook corresponding to the first service transmission is placed before the HARQ-ACK codebook corresponding to the second service transmission, wherein the priority of the first service transmission is higher than the priority of the second service transmission; or the priority of the HARQ process carrying the first service transmission is higher than the priority of the HARQ process carrying the second service transmission.
[0114] In one embodiment, reference Figure 4For at least two service transmissions, if the PUCCH time domain of the HARQ-ACK codebook corresponding to the first service transmission and the HARQ-ACK codebook corresponding to the second service transmission overlaps, and the priority of the HARQ process carrying the first service transmission is higher than the priority of the HARQ process carrying the second service transmission: the processing module 12 is configured to cancel the PUCCH transmission of the HARQ-ACK codebook corresponding to the second service transmission.
[0115] Figure 5 A schematic diagram of the structure of a base station is provided as an embodiment, such as... Figure 5 As shown, the base station includes a processor 40, a memory 41, and a communication interface 42; the number of processors 40 in the base station can be one or more. Figure 5 Taking a processor 40 as an example; the processor 40, memory 41, and communication interface 42 in the base station can be connected via a bus or other means. Figure 5 Taking the bus connection as an example, a bus can refer to one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus that uses any of the various bus architectures.
[0116] The memory 41, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the method for determining transmission priority in the embodiments of this application. The processor 40 executes at least one functional application and data processing of the base station by running the software programs, instructions, and modules stored in the memory 41, that is, it implements the above-described method for determining transmission priority.
[0117] The memory 41 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on the UE's usage. Furthermore, the memory 41 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 41 may include memory remotely located relative to the processor 40, and this remote memory can be connected to a base station via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0118] Communication interface 42 can be configured to receive and send data.
[0119] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method for determining transmission priority as provided in the embodiments of this application. This method may be, but is not limited to, the content disclosed in the above method embodiments.
[0120] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be—but is not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), electrically erasable, programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0121] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, the data signals carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.
[0122] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, radio frequency (RF), or any suitable combination thereof.
[0123] Computer program code for performing the operations of this disclosure can be written in one or more programming languages or a combination of programming languages, including object-oriented programming languages such as Java, Smalltalk, C++, Ruby, and Go, as well as conventional procedural programming languages such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0124] The above description is merely an exemplary embodiment of this application and is not intended to limit the scope of protection of this application.
[0125] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.
[0126] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.
[0127] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.
[0128] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, ROM, RAM, optical storage devices and systems (Digital Video Disc (DVD) or Compact Disc (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.
Claims
1. A method for determining information, characterized in that, Applied to user equipment and base stations, the method includes: The user equipment is configured as a semi-static HARQ-ACK codebook, and determines the HARQ-ACK information corresponding to a set of time-overlapping physical downlink shared channels (PDSCHs) according to preset rules. The preset rules include: the set of time-domain overlapping PDSCHs includes M time-domain overlapping PDSCHs, and min(N,M) HARQ-ACK messages are determined, where min(N,M) represents the minimum value between N and M, and N is the number of time-domain overlapping PDSCHs reported by the user equipment.
2. The method according to claim 1, characterized in that, Also includes: The priority of the HARQ process is determined, and the priority of the HARQ-ACK information in the control channel corresponding to the service transmission in the service channel carried by the HARQ process is determined according to the priority. The transmission of the HARQ-ACK information is determined based on the priority of the HARQ-ACK information.
3. The method according to claim 1, characterized in that, Also includes: The priority of the HARQ process is determined, and the priority of the service channel carried by the HARQ process and the priority of the HARQ-ACK information in the control channel corresponding to the service transmission in the service channel carried by the HARQ process are determined according to the priority. The transmission of the service transmission and the transmission of the HARQ-ACK information are determined based on the priority of the service transmission and the priority of the HARQ-ACK information.
4. The method according to claim 2, characterized in that, Determining the priority of the HARQ process includes: The priority of the HARQ process is determined at the Media Access Control (MAC) layer, and the priority is communicated to the physical layer.
5. The method according to claim 4, characterized in that, Determining the priority of the HARQ process at the Media Access Control (MAC) layer includes: The priority of the MAC PDU is determined at the MAC layer based on the highest priority of the logical channel LCH contained in the Media Access Control Protocol Data Unit (MAC PDU) carried by the HARQ process. The priority of the HARQ process is determined at the MAC layer based on the priority of the MAC PDU.
6. The method according to claim 5, characterized in that, The step of determining the priority of the HARQ process at the MAC layer based on the priority of the MAC PDU includes: The MAC layer assigns the priority of the MAC PDU to the HARQ process; or, After the priority of the MAC PDU is mapped and processed according to the second convention at the MAC layer, the priority of the HARQ process is obtained.
7. The method according to claim 3, characterized in that, The step of determining the priority of the service channel carried by the HARQ process based on the priority includes: The priority of the HARQ process is assigned to the service transmission in the service channel carried by the HARQ process; or, After mapping the priority of the HARQ process according to the third convention, the priority of service transmission in the service channel carried by the HARQ process is obtained.
8. The method according to claim 2, characterized in that, The step of determining the priority of the HARQ-ACK information in the control channel corresponding to the service transmission in the service channel carried by the HARQ process according to the priority includes: The priority of the HARQ process is assigned to the HARQ-ACK information in the control channel corresponding to the service transmission in the service channel carried by the HARQ process; or, After mapping the priority of the HARQ process according to the third convention, the priority of the HARQ-ACK information in the control channel corresponding to the service transmission in the service channel carried by the HARQ process is obtained.
9. The method according to claim 1, characterized in that, It also includes at least one of the following: The HARQ-ACK corresponding to the service transmission with the same HARQ process priority corresponds to one HARQ-ACK message. The HARQ-ACK corresponding to the service transmissions of the same priority corresponds to one HARQ-ACK message, wherein the priority of the service transmission is determined according to the priority of the HARQ process carrying the service transmission; A HARQ-ACK message corresponds to a service transmission whose priority difference does not exceed a preset level, wherein the priority of the service transmission is determined according to the priority of the HARQ process carrying the service transmission.
10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the information determination method as described in any one of claims 1-9.
Citation Information
Patent Citations
Method and apparatus for uplink power control when uplink transmissions overlap in time for at least one symbol duration
CN108781417A
Method and user equipment for transmitting ACK / NACK information, and method and base station for receiving ACK / NACK information
US20130272258A1