WO2021026847A1 - 无线通信的方法和设备 - Google Patents
无线通信的方法和设备 Download PDFInfo
- Publication number
- WO2021026847A1 WO2021026847A1 PCT/CN2019/100671 CN2019100671W WO2021026847A1 WO 2021026847 A1 WO2021026847 A1 WO 2021026847A1 CN 2019100671 W CN2019100671 W CN 2019100671W WO 2021026847 A1 WO2021026847 A1 WO 2021026847A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- priority
- harq process
- authorized resource
- deprioritized
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1854—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1887—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1896—ARQ related signaling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1874—Buffer management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
- H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
- H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
Definitions
- the embodiments of the present application relate to the field of communications, and in particular to a method and device for wireless communication.
- NR New Radio
- NR New Radio
- eMBB enhanced mobile ultra-broadband
- UL grant uplink authorization
- URLLC Latency Communication
- the service on another UL grant may be called a de-prioritized service or de-prioritized data. Therefore, how to schedule the retransmission of the de-prioritized data to avoid data loss is an urgent problem to be solved.
- the embodiment of the present application provides a wireless communication method and device, which is beneficial to reduce the waste of resources scheduled by the network device, and can transmit the data to be transmitted of the terminal device to the network device as soon as possible.
- a wireless communication method including: a terminal device receives a retransmission schedule of a first automatic retransmission HARQ process requested by a network device; the terminal device processes the deprioritized data according to the first information, wherein, the de-prioritized data corresponds to the first HARQ process, and the first information includes at least one of the following: whether the de-prioritized data is packaged before receiving the retransmission schedule; and Whether the de-prioritized data is delivered to the first HARQ process before the retransmission scheduling.
- a wireless communication device which is used to execute the foregoing first aspect or any possible implementation of the first aspect.
- the device includes a unit for executing the foregoing first aspect or the method in any possible implementation manner of the first aspect.
- a wireless communication device in a third aspect, includes a processor and a memory.
- the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation modes.
- a chip is provided, which is used to implement the method in the first aspect or its implementation manners.
- the chip includes a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the method in the first aspect or its implementation manners.
- a computer-readable storage medium for storing a computer program that enables a computer to execute the method in the first aspect or its implementation manners.
- a computer program product including computer program instructions that cause a computer to execute the method in each implementation manner of the first aspect.
- a computer program which when running on a computer, causes the computer to execute the method in the first aspect or its implementation manners.
- the terminal device when the terminal device receives the retransmission schedule of the HARQ process in which the deprioritized data is located, the terminal device can be based on the packetization situation and/or of the deprioritized data before receiving the retransmission schedule.
- the de-priority data is submitted to the HARQ process, and the de-priority data is processed, for example, the de-priority data is packaged and/or transmitted, which is beneficial to reduce the waste of resources for network equipment scheduling, and can transfer the terminal equipment
- the data to be transmitted is transmitted to the network device as soon as possible, which is conducive to meeting the transmission requirements of services with high delay requirements and improving user experience.
- Fig. 1 is a schematic diagram of an application scenario provided by an embodiment of the present application.
- FIG. 2 is a schematic diagram of a wireless communication method provided by an embodiment of the present application.
- Fig. 3 is a schematic diagram of transmitting deprioritized data according to a specific embodiment.
- Fig. 4 is a schematic diagram of transmitting deprioritized data according to another specific embodiment.
- Fig. 5 is a schematic block diagram of a wireless communication device provided by an embodiment of the present application.
- Fig. 6 is a schematic block diagram of a communication device according to another embodiment of the present application.
- FIG. 7 is a schematic block diagram of a chip provided by an embodiment of the present application.
- GSM Global System of Mobile Communication
- CDMA Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- GSM Global System of Mobile Communication
- GPRS General Packet Radio Service
- LTE Long Term Evolution
- FDD Frequency Division Duplex
- TDD Time Division Duplex
- UMTS Universal Mobile Telecommunication System
- WiMAX Worldwide Interoperability for Microwave Access
- the communication system 100 applied in the embodiment of the present application is shown in FIG. 1.
- the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or called a communication terminal or terminal).
- the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area.
- the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.
- BTS Base Transceiver Station
- NodeB, NB base station
- LTE Long Term Evolutional Node B
- eNB evolved base station
- CRAN Cloud Radio Access Network
- the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches
- the communication system 100 also includes at least one terminal device 120 located within the coverage area of the network device 110.
- the "terminal equipment” used here includes but is not limited to connection via wired lines, such as via public switched telephone networks (PSTN), digital subscriber lines (Digital Subscriber Line, DSL), digital cables, and direct cable connections ; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and/or another terminal device that is set to receive/send communication signals; and/or Internet of Things (IoT) equipment.
- PSTN public switched telephone networks
- DSL Digital Subscriber Line
- DSL Digital Subscriber Line
- DSL Digital Subscriber Line
- DSL Digital Subscriber Line
- DSL Digital Subscriber Line
- DSL Digital Subscriber Line
- DSL Digital Subscriber Line
- DSL Digital Subscriber Line
- DSL Digital Subscriber Line
- DSL Digital Subscriber Line
- DSL
- a terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
- mobile terminals include, but are not limited to, satellites or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio phone transceivers Electronic device.
- PCS Personal Communications System
- GPS Global Positioning System
- Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device.
- the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of PLMN, etc.
- SIP Session Initiation Protocol
- WLL Wireless Local Loop
- PDA Personal Digital Assistant
- direct terminal connection (Device to Device, D2D) communication may be performed between the terminal devices 120.
- the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
- NR New Radio
- Figure 1 exemplarily shows one network device and two terminal devices.
- the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.
- the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
- network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
- the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
- the communication device may include a network device 110 and a terminal device 120 with communication functions, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here.
- the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the application.
- FIG. 2 is a schematic flowchart of a wireless communication method 200 according to an embodiment of this application.
- the method 200 may be executed by the terminal device in the communication system shown in FIG. 1.
- the method 200 includes at least part of the following content:
- the terminal device receives the retransmission schedule of the first automatically requested retransmission HARQ process by the network device;
- the terminal device processes the deprioritized data according to the first information, where the deprioritized data corresponds to the first HARQ process, and the first information includes at least one of the following: Whether the deprioritized data is packaged before the retransmission scheduling; and whether the deprioritized data is delivered to the first HARQ process before the retransmission scheduling is received.
- the deprioritized data in the embodiment of the present application is generated under resource conflicts.
- the first uplink resource conflicts with the second uplink resource if only the data on the second uplink resource is transmitted Data, the data carried on the second uplink resource can be called priority (prioritized) data, and the priority data of the grouping can also be called prioritized media access control (Media Access Control, MAC) PDU protocol data unit (Protocol Data Unit).
- MAC Media Access Control
- PDU PDU protocol data unit
- the data that is carried or that can be carried on the first uplink resource that has not been transmitted can be called deprioritized data
- the deprioritized data of the group packet can also be called deprioritized MAC PDU.
- de-prioritized data may also be referred to as low-priority data, low-priority MAC PDU.
- the depriority data corresponding to the first HARQ process may be that the depriority data is sent on the first HARQ process, or in other words, the depriority data is It is transmitted using the first HARQ process.
- the depriority data corresponding to the first HARQ process may be depriority data sent on the first HARQ process, or in other words, the first HARQ process is used. De-prioritized data transmitted by the HARQ process.
- the conflict between the first uplink resource and the second uplink resource may mean that the first uplink resource and the second uplink resource at least partially overlap in the time domain.
- the start time of the first uplink resource and the second uplink resource may be the same, and the end time may be different, or the start time of the first uplink resource and the second uplink resource may be different, and the end time It may be the same, or the start time of the first uplink resource and the second uplink resource may be different, the end time may also be different, and the middle part may overlap, or the first uplink resource and the second
- the start time of the uplink resources can be the same, and the end time can also be the same, which is not limited in the embodiment of the present application.
- the first uplink resource can be a configured grant (CG) resource, a dynamic grant (DG) resource, an uplink shared channel (Uplink Shared Channel, UL-SCH) uplink grant, or an uplink Uplink resources such as uplink authorization of control information (Uplink Control Information, UCI), which are not limited in the embodiment of the present application.
- CG configured grant
- DG dynamic grant
- UCI uplink Control Information
- the second uplink resource may be an uplink resource such as a CG resource, a DG resource, an uplink grant of UL-SCH, or an uplink grant of UCI, which is not limited in the embodiment of the present application.
- the following takes the conflict between CG resources and DG resources as an example, but the application is not limited to this.
- the CG resource is a semi-statically scheduled resource.
- the network device configures the CG resource for the terminal device, it can be configured and activated (for example, for type 1 CG resources (Type-1CG)), or through Dynamic signaling such as DCI activates the CG resource (for example, for type 2 CG resources (Type-2CG), after the CG resource is activated, the terminal device can use the CG resource for transmission, and the CG resource can be a periodic resource , The terminal device can use the CG resource for transmission multiple times.
- Type-1CG type 1 CG resources
- Dynamic signaling such as DCI activates the CG resource
- the terminal device can use the CG resource for transmission, and the CG resource can be a periodic resource ,
- the terminal device can use the CG resource for transmission multiple times.
- the DG resource is a dynamically scheduled resource. After the network device configures the DG resource for the terminal device, the terminal device can use the DG resource for transmission.
- the DG resource is usually a single-use resource. After the device configures the DG resource, the terminal device usually can only use the DG resource for a single transmission.
- the terminal device may not package the deprioritized data (denoted as embodiment 1) or may also perform the deprioritization data Group packet (marked as embodiment 2), further, in the case of receiving the retransmission scheduling of the HARQ process where the deprioritization data is located by the network device, the terminal device may deprioritize according to the HARQ process corresponding Whether the data is packaged, the de-prioritized data is processed. For example, if the de-prioritized data is not packaged, the terminal device may package the de-prioritized data, and further perform packet processing on the de-prioritized data.
- the de-priority data can be transmitted in a new transmission mode; for another example, if the de-priority data has been packaged, the terminal device can transmit the de-priority data of the package, for example, The de-prioritized data is transmitted in a new transmission or retransmission manner.
- the terminal device determines to transmit the second data on the second authorized resource. If the terminal device receives the first authorized resource scheduled by the network device before the second authorized resource, the first authorized resource is used to transmit the first data, If there is a conflict between the first authorized resource and the second authorized resource, the terminal device may not package the first data, and only transmit the second data during transmission, then the second data is priority data, The first data is de-prioritized data. Wherein, the first authorized resource corresponds to a first HARQ process, and the second authorized resource corresponds to a second HARQ process.
- first authorized resource and the second authorized resource may correspond to the first uplink resource and the second uplink resource described above, and the specific implementation can refer to the specific implementation above, which will not be repeated here.
- the terminal device may not package the de-prioritized data under any circumstances. As another example, the terminal device may not package the de-prioritized data under certain conditions.
- the terminal device may be based on whether the priority data is packaged, the transmission status of the priority data, the priority of the priority data, the priority of the second authorized resource, the priority of the deprioritized data At least one of the priority and the priority of the first authorized resource determines whether to package the deprioritized data.
- the priority data here is the priority data corresponding to the de-priority data
- the priority data corresponding to the de-priority data is the data that is preferentially transmitted when a resource conflict occurs, and the de-priority data is not transmitted due to resource conflict The data.
- the transmission situation of the priority data may include whether the priority data is transmitted to the physical layer and/or whether the priority data is transmitted (or whether the priority data is transmitted over the air interface).
- the terminal device may not package the de-priority data
- the terminal device may not package the de-priority data if the priority data has been packaged before the first time, and the priority of the de-prioritized data is lower than the priority of the priority data, or the priority of the de-prioritized data is lower than the first time A priority threshold.
- the terminal device may not package the de-priority data
- the terminal device may not package the de-priority data
- the terminal device may not package the de-prioritized data
- the terminal device may not package the de-priority data if the priority data has been sent before the first time, and the priority of the depriority data is lower than the priority of the priority data, or the priority of the depriority data is lower than the first Priority threshold;
- the terminal device may not package the de-priority data
- SR scheduling Request
- the terminal device may not package the de-priority data
- the terminal device may not group the de-prioritized data
- the terminal device may not group the de-priority data.
- the first priority threshold may be predefined, or may also be configured by a network device.
- the second priority threshold may be predefined, or may also be configured by a network device.
- the terminal device Before the terminal device obtains the first authorized resource of the deprioritized data, for example, before the terminal device receives the first authorized resource configured by the network device; or,
- the priority of the first authorized resource is higher than the priority of the second authorized resource, or the priority of the data that the first authorized resource can carry is higher than the priority of the data that the second authorized resource can carry
- the priority of, the first authorized resource may not be packaged.
- not packaging the first authorized resource may include not packaging the data on the first authorized resource , That is, the de-prioritized data is not packaged, and the two have the same meaning and can be replaced with each other.
- grouping the first authorized resource may include grouping the data on the first authorized resource, that is, de-prioritizing The data is packaged, and the two have the same meaning and can be replaced with each other.
- whether to package the deprioritized data may also include whether to package the deprioritized resource (ie, the first authorized resource).
- the MAC layer of the terminal device may not submit the information of the first authorized resource to the first HARQ process, and/or not indicate the physical layer Use the first authorized resource to transmit data.
- the terminal device may de-prioritize data corresponding to the first HARQ process before receiving the retransmission schedule Whether to be packaged, the de-prioritized data is transmitted.
- the terminal device may group the deprioritized data, and further may group Deprioritized data (ie, deprioritized MAC PDU) is transmitted, for example, deprioritized MAC PDU can be newly transmitted.
- Deprioritized data ie, deprioritized MAC PDU
- the de-prioritized data of the first HARQ process is not packaged, and it can also be understood that the buffer of the first HARQ process is empty.
- the terminal device may receive a Physical Downlink Control Channel (PDCCH) sent by a network device, and the PDCCH may include an uplink grant (UL grant) scheduled by the network device.
- PDCCH Physical Downlink Control Channel
- the uplink authorization corresponds to the first HARQ process
- the terminal device may scramble the PDCCH according to the radio network temporary identifier (Radio Network Temporary Identity, RNTI) and/or the new data indication in the PDCCH (New Data Indicator, NDI), which determines whether the scheduling of the first HARQ process by the network device is retransmission scheduling or initial transmission scheduling.
- RNTI Radio Network Temporary Identity
- NDI New Data Indicator
- the PDCCH is scrambled by the Configured Scheduling-RNTI (CS-RNTI), and the NDI is 1, it can be determined that the scheduling of the first HARQ process is retransmission scheduling .
- CS-RNTI Configured Scheduling-RNTI
- the PDCCH is scrambled by a configured scheduling radio network temporary identifier (Configured Scheduling-RNTI, CS-RNTI), it may be determined that the scheduling of the first HARQ process is retransmission scheduling.
- a configured scheduling radio network temporary identifier Configured Scheduling-RNTI, CS-RNTI
- the PDCCH is scrambled by a cell radio network temporary identity (Cell-RNTI, C-RNTI) and the NDI is not overturned, it may be determined that the scheduling of the first HARQ process is retransmission scheduling.
- Cell-RNTI cell radio network temporary identity
- the PDCCH is scrambled by the cell radio network temporary identifier (Cell-RNTI, C-RNTI) and the corresponding HARQ process is empty, it may be determined that the scheduling of the first HARQ process is retransmission scheduling .
- Cell-RNTI cell radio network temporary identifier
- the PDCCH is scrambled by the cell radio network temporary identity (Cell-RNTI, C-RNTI), and the corresponding HARQ process is the HARQ process corresponding to the unused resources due to resource conflicts, it is determined to The scheduling of the first HARQ process is retransmission scheduling.
- Cell-RNTI cell radio network temporary identity
- C-RNTI cell radio network temporary identity
- the PDCCH is scrambled by the cell radio network temporary identifier (Cell-RNTI, C-RNTI), and the corresponding HARQ process is the HARQ process corresponding to the deprioritized data, it may be determined that the first HARQ process is The scheduling is retransmission scheduling.
- Cell-RNTI cell radio network temporary identifier
- C-RNTI cell radio network temporary identifier
- the terminal device determines whether the deprioritization data is stored according to whether the deprioritization data is stored in the first HARQ process or whether the authorized resource corresponding to the depriority data is used Be grouped.
- the buffer of the first HARQ process is empty, it can be determined that the de-prioritized data is not packaged
- the buffer of the first HARQ process does not store the de-prioritized data, it may be determined that the de-prioritized data is not packaged;
- the first authorized resource is not used, and it can be determined that the de-prioritized data is not packaged.
- the unused first authorized resource may include that the first authorized resource is ignored, or there is no data transmission on the first authorized resource, or an authorized resource in a resource conflict scenario, that is, the first authorized resource.
- Authorized resources may be unused due to resource conflicts with other authorized resources.
- the buffer of the first HARQ process is not empty, it can be determined that the deprioritized data is packaged; or, if the buffer of the first HARQ process stores the deprioritized data, it can be determined that the The de-prioritized data is packaged; or, before the retransmission schedule is received, the first authorized resource is used, and it can be determined that the de-prioritized data is packaged.
- the terminal device may group the deprioritized data, and group the package To prioritize data for transmission.
- the buffer of the first HARQ process is empty.
- the terminal device grouping the deprioritized data may include the multiplexing and assembly entity of the terminal device grouping the deprioritized data to obtain a deprioritized MAC PDU, for example , Performing packet header processing on the de-prioritized data.
- the terminal device transmitting the deprioritized data of the group packet may include at least one of the following: the MAC layer of the terminal device obtains a deprioritized MAC PDU from the multiplexing group packet entity, and the MAC layer of the terminal device At least one of the deprioritized MAC PDU, the uplink grant of the retransmission scheduling, and the HARQ information (for example, redundancy version (Redundancy Version, RV)) of the uplink grant is delivered to the first HARQ process.
- the MAC layer of the terminal device obtains a deprioritized MAC PDU from the multiplexing group packet entity
- the MAC layer of the terminal device At least one of the deprioritized MAC PDU, the uplink grant of the retransmission scheduling, and the HARQ information (for example, redundancy version (Redundancy Version, RV)) of the uplink grant is delivered to the first HARQ process.
- the MAC layer of the terminal device instructs the first HARQ process to trigger a new transmission, and further, the deprioritized MAC PDU is processed using the first HARQ process Make a new pass.
- the uplink grant for retransmission scheduling is configured authorized resource
- the first HARQ process is the HARQ process for configuring authorized resource
- the uplink grant scheduled for retransmission is dynamic authorized resource and the first
- the HARQ process is the HARQ process corresponding to the configured authorized resource.
- the terminal device may also start or restart the configured authorization timer corresponding to the first HARQ process when it starts to transmit the deprioritized MAC PDU, and the configured authorization timer runs During this period, the deprioritized MAC PDU saved in the first HARQ process is not flushed, which helps prevent the loss of the deprioritized data.
- the terminal device when the terminal device receives the retransmission schedule of the HARQ process of the deprioritized data by the network device, the unpacked deprioritized data can be packaged, and further follow the new transmission mode.
- the transmission of the de-prioritized data of the group packet is beneficial to reducing the waste of resources scheduled by the network equipment, and the data to be transmitted of the terminal equipment can be transmitted to the network equipment as soon as possible, which is conducive to satisfying the requirements of services with high delay requirements. Transmission needs to improve user experience.
- the terminal device determines to transmit the second data on the second authorized resource, if the terminal device receives the first authorized resource scheduled by the network device before the second authorized resource, the first authorized resource is used to transmit the first data If there is a conflict between the first authorized resource and the second authorized resource, the terminal device may package the first data, and when transmitting, only the second data is transmitted, then the second data is priority data , The first data is de-prioritized data.
- the first authorized resource corresponds to a first HARQ process
- the first authorized resource corresponds to a second HARQ process.
- the specific implementation of the first authorized resource and the second authorized resource can refer to the specific implementation above, which will not be repeated here.
- the terminal device may package the de-prioritized data under any circumstances.
- the terminal device may group the de-prioritized data under certain conditions.
- the terminal device may be based on whether the priority data is packaged, the transmission status of the priority data, the priority of the priority data, the priority of the second authorized resource, the priority of the deprioritized data At least one of the priority and the priority of the first authorized resource determines whether to package the deprioritized data.
- the transmission situation of the priority data may include whether the priority data is transmitted to the physical layer and/or whether the priority data is transmitted (or whether the priority data is transmitted over the air interface).
- the terminal device may group the de-priority data.
- the terminal device may group the de-priority data
- the terminal device may group the de-priority data
- the terminal device may group the de-priority data
- the terminal device can group the de-priority data
- the terminal device may package the de-priority data
- SR scheduling Request
- the terminal device may group the de-priority data
- the terminal device may group the de-prioritized data
- the terminal device may group the de-priority data.
- the terminal device may also be packaged, sent to the physical layer, or transmitted after the priority data, and/or, the priority of the deprioritized data is high In the case where the priority of the priority data or the priority of the deprioritized data is higher than a specific priority threshold, the deprioritized data is packaged.
- the terminal device may also package the priority data, or be sent to the physical layer, or be transmitted, and/or the priority of the first authorized resource In a case where the priority of the second authorized resource is higher, or the priority of the first authorized resource is higher than a specific priority threshold, the deprioritized data is packaged.
- the priority of the first authorized resource is higher than the priority of the second authorized resource, or the priority of the data that the first authorized resource can carry is higher than the priority of the second authorized resource
- the priority of the data may be packaged for the first authorized resource, that is, the deprioritized data on the first authorized resource may be packaged.
- the terminal device may package the de-priority data.
- the second time before may refer to one of the following:
- the terminal device Before the terminal device obtains the first authorized resource of the deprioritized data, for example, before the terminal device receives the first authorized resource configured by the network device; or,
- whether to package the deprioritized data may also include whether to package the deprioritized resource (ie, the first authorized resource).
- the MAC layer of the terminal device may submit the information of the first authorized resource to the first HARQ process, and/or not instruct the physical layer to use all the resources.
- the first authorized resource transmits data, that is, the transmission of the de-prioritized data is not performed.
- the terminal device receives the retransmission schedule for the first HARQ process of the network device, it should be understood that, in this embodiment 2, it is determined that the network device schedules the first HAQR process as the retransmission schedule
- the network device schedules the first HAQR process as the retransmission schedule
- the terminal device may also determine the depriority according to whether the first HARQ process stores the depriority data or whether the authorized resource corresponding to the depriority data is used. Whether the data is packaged.
- the buffer of the first HARQ process does not store the de-prioritized data, it may be determined that the de-prioritized data is not packaged;
- the first authorized resource is not used, and it can be determined that the de-prioritized data is not packaged;
- the buffer of the first HARQ process is empty, it may be determined that the de-prioritized data is not packaged
- the buffer of the first HARQ process is empty and the first authorized resource is not used before the retransmission schedule is received, it may be determined that the deprioritized data is not packaged.
- the unused first authorized resource may include that the first authorized resource is ignored, or there is no data transmission on the first authorized resource, or an authorized resource in a resource conflict scenario, that is, the first authorized resource.
- Authorized resources may be unused due to resource conflicts with other authorized resources.
- the de-priority data is stored in the buffer of the first HARQ process, it may be determined that the de-priority data is packaged; or, before the retransmission schedule is received, the first authorized resource is Use, it can be determined that the de-prioritized data is packaged; or, if the buffer of the first HARQ process is not empty and the first authorized resource is used before the retransmission schedule is received, it can be determined The deprioritized data is packaged; or, if the buffer of the first HARQ process is not empty, it may be determined that the deprioritized data is packaged.
- the terminal device may transmit the packaged deprioritized data.
- the terminal device may transmit the de-prioritized data according to whether the de-prioritized data packet of the group packet is delivered to the first HARQ process before receiving the retransmission scheduling, for example, a new transmission or The deprioritized data is transmitted in a retransmission manner.
- the terminal device may deprioritize the MAC PDU Make a new pass.
- the terminal device may perform the deprioritized MAC PDU Retransmission.
- the terminal device when the deprioritization data has been packaged, it can be considered that the depriority data has been delivered to the first HARQ process.
- the terminal device can directly The deprioritized data in a HARQ process is newly transmitted or retransmitted without determining whether the deprioritized data is delivered to the first HARQ process.
- the new transmission of the deprioritized data by the terminal device may include at least one of the following: the MAC layer of the terminal device may obtain a deprioritized MAC PDU from a multiplexing grouping entity. Further, The MAC layer of the terminal device may deliver at least one of the deprioritized MAC PDU, the uplink grant of the retransmission scheduling, and the HARQ information of the uplink grant to the first HARQ process. In the case that the deprioritized MAC PDU is delivered to the first HARQ process, the MAC layer of the terminal device may instruct the first HARQ process to trigger a new transmission. Further, the first HARQ process may be used to The deprioritized MAC PDU is newly transmitted.
- the retransmission of the de-prioritized data by the terminal device may include at least one of the following: the MAC layer of the terminal device may assign the uplink authorization for the retransmission scheduling and the At least one item of the HARQ information of the uplink authorization is delivered to the first HARQ process. Further, the MAC layer of the terminal device may instruct the first HARQ process to trigger retransmission, and further, the terminal device may use the first HARQ process to retransmit the deprioritized MAC PDU.
- the uplink grant scheduled for retransmission is configured authorized resource, that is, the first HARQ process is the HARQ process configured with authorized resource, or the uplink grant scheduled for retransmission is a dynamic authorized resource and the first HARQ process
- a HARQ process is the HARQ process corresponding to the configured authorized resource.
- the terminal device may also start or restart the configured authorization timer corresponding to the first HARQ process when it starts to transmit the deprioritized MAC PDU, where the authorization timer is configured During the operation, the deprioritized MAC PDU stored in the first HARQ process is not flushed, which helps prevent the loss of the deprioritized data.
- the terminal device can transmit the deprioritized data of the group packet according to the new transmission or retransmission mode when receiving the retransmission scheduling of the HARQ process of the deprioritized data by the network device, It is beneficial to reduce the waste of resources scheduled by the network equipment, and can transmit the data to be transmitted from the terminal equipment to the network equipment as soon as possible, which is beneficial to meet the transmission requirements of services with high delay requirements and improve user experience.
- the terminal device has packaged the de-prioritized data before the retransmission scheduling of the network device, which is beneficial to avoid the package delay caused by the package grouping after the retransmission scheduling is received, and the user experience is improved.
- the network device may configure CG resources for the terminal device.
- the configuration information of the CG resources may include at least one of the following:
- the period of the CG resource for example, 1 time slot
- the identifier (Identify, ID) of the CG resource for example, the ID can be 1;
- the configured grant timer (configuredGrantTimer) of the HARQ process of the CG resource for example, the duration of the timer may be 3, which means 3 time slots, or the length of 3 CG cycles.
- the HARQ process number corresponding to the CG resource for example, the HARQ process number can be 2, 3, and 4.
- the network device instructs the activation of the CG resource with the CG identifier 1 through Downlink Control Information (DCI). After that, the terminal device uses the CG resource for data transmission.
- DCI Downlink Control Information
- the terminal device determines that there are configured and activated CG resources at time t 3 , and the terminal device can package the data to be transmitted at time t 1 to obtain MAC PDU1.
- the MAC PDU1 may include Data in a logical channel (Logical Channel, LCH) corresponding to the URLLC service, where time t 1 is earlier than time t 3 .
- LCH Logical Channel
- the terminal device receives a DG resource scheduled by the network device through DCI.
- the DG resource is only used to transmit low-priority services, such as eMBB services
- the DG resources and The HARQ process of the CG resource whose ID is 1 is different.
- the DG resource corresponds to HARQ process 1
- the CG resource corresponds to HARQ process 2.
- the terminal device may perform priority (intra-UE prioritization) the user to determine the priority data DG transmission resources, e.g. Since MAC PDU1 carries URLLC services and DG resources can only carry low-priority services, it can be considered that the priority of the CG resource with ID 1 is higher than the priority of the DG resource, and MAC PDU1 is transmitted first. Then the terminal device can perform at least one of the following operations:
- the terminal device may not package the data to be transmitted on the DG resource, that is, it does not generate MAC PDU2. Then the MAC PDU2 is not saved in the HARQ process 1.
- the terminal device may not submit the DG resource to the HARQ process 1.
- the terminal device may not instruct the physical layer to use the DG resource for data transmission.
- the terminal device can determine whether the deprioritized data using the HARQ process 1 is packaged, or in other words, determine whether there is packaged deprioritized data.
- the specific determination method can be combined with the relevant description above, and will not be repeated here.
- the terminal device may perform at least one of the following operations:
- the multiplexing grouping entity of the terminal device groups the de-prioritized data to obtain MAC PDU2;
- the MAC layer of the terminal device obtains the MAC PDU2 from the multiplexing grouping entity
- the MAC layer of the terminal device delivers at least one of the MAC PDU2, the uplink grant information for the retransmission scheduling, and the HARQ information for the uplink grant to the HARQ process 1;
- the MAC layer of the terminal device instructs the HARQ process 1 to trigger a new transmission.
- the terminal device may enable or restart the configuration corresponding to the HARQ process 1 when starting to transmit the MAC PDU2 Authorization timer.
- the network device may configure CG resources for the terminal device.
- the configuration information of the CG resources may include at least one of the following:
- the period of the CG resource for example, 1 time slot
- the identifier (Identify, ID) of the CG resource for example, the ID can be 1;
- the configured grant timer (configuredGrantTimer) of the HARQ process of the CG resource for example, the duration of the timer may be 3, which means 3 time slots, or the length of 3 CG cycles.
- the HARQ process number corresponding to the CG resource for example, the HARQ process number can be 2, 3, and 4.
- the network device instructs the activation of the CG resource with the CG identifier 1 through Downlink Control Information (DCI). After that, the terminal device uses the CG resource for data transmission.
- DCI Downlink Control Information
- the terminal device determines that there are configured and activated CG resources at time t 3.
- the terminal device can group the data to be transmitted at time t 1 to obtain MAC PDU1, optionally, the MAC PDU1 It may include data in a logical channel (Logical Channel, LCH) corresponding to the URLLC service, where time t 1 is earlier than time t 3 .
- LCH Logical Channel
- the terminal device receives a DG resource scheduled by the network device through DCI.
- the DG resource is only used to transmit low-priority services, such as eMBB services
- the DG resources and The HARQ process of the CG resource whose ID is 1 is different.
- the DG resource corresponds to HARQ process 1
- the CG resource corresponds to HARQ process 2.
- the terminal device may perform priority (intra-UE prioritization) the user to determine the priority data DG transmission resources, e.g. Since MAC PDU1 carries URLLC services and DG resources can only carry low-priority services, it can be considered that the priority of the CG resource with ID 1 is higher than the priority of the DG resource, and MAC PDU1 is transmitted first. Then the terminal device can perform at least one of the following operations:
- the terminal device can package the data to be transmitted on the DG resource, that is, generate MAC PDU2. Then the MAC PDU2 is stored in the HARQ process 1.
- the terminal device may submit the DG resource to the HARQ process 1.
- the terminal device may not instruct the physical layer to use the DG resource for data transmission.
- the terminal device can determine whether the deprioritized data using the HARQ process 1 is packaged, or in other words, determine whether there is packaged deprioritized data.
- the specific determination method can be combined with the relevant description above, and will not be repeated here.
- the terminal device may perform at least one of the following operations:
- the MAC layer of the terminal device obtains the deprioritized MAC PDU from the multiplexing grouping entity
- the MAC layer of the terminal device delivers at least one of the MAC PDU2, the uplink grant information for the retransmission scheduling, and the HARQ information for the uplink grant to the HARQ process 1;
- the MAC layer of the terminal device instructs the HARQ process 1 to trigger a new transmission.
- the terminal device may perform at least one of the following operations:
- the MAC layer of the terminal device submits at least one of the uplink grant information of the retransmission scheduling and the HARQ information of the uplink grant to the HARQ process 1;
- the MAC layer of the terminal device instructs the HARQ process 1 to trigger retransmission.
- the terminal device may enable or restart the configuration corresponding to the HARQ process 1 when starting to transmit the MAC PDU2 Authorization timer.
- FIG. 5 shows a schematic block diagram of a wireless communication device 500 according to an embodiment of the present application. As shown in FIG. 5, the device 500 includes:
- the communication module 510 is configured to receive the retransmission schedule of the first automatic retransmission HARQ process requested by the network device;
- the processing module 520 is configured to process de-prioritized data according to first information, where the de-prioritized data corresponds to the first HARQ process, and the first information includes at least one of the following:
- the de-prioritized data is delivered to the first HARQ process before receiving the retransmission schedule.
- the processing module 520 is specifically configured to:
- de-prioritized data is not packaged before receiving the retransmission schedule, group the de-prioritized data into a package;
- the processing module 520 is specifically configured to:
- the use of the first HARQ process is triggered according to whether the de-prioritized data is delivered to the first HARQ process before the retransmission schedule is received. Whether the HARQ process newly transmits or retransmits the de-prioritized data.
- the processing module 520 is specifically configured to:
- the deprioritized data is not delivered to the first HARQ process before the retransmission schedule is received, triggering the use of the first HARQ process to newly transmit the deprioritized data.
- the processing module 520 is specifically configured to:
- the deprioritized data has been delivered to the first HARQ process before the retransmission schedule is received, triggering the use of the first HARQ process to retransmit the deprioritized data.
- the processing module 520 is specifically configured to perform at least one of the following:
- the processing module 520 is specifically configured to perform at least one of the following:
- the processing module 520 is further configured to:
- the configuration authorization timer of the first HARQ process is started or restarted when starting to transmit the deprioritized data.
- the processing module 520 is further configured to:
- the retransmission scheduling is configured to schedule the physical downlink control channel PDCCH scrambled by the temporary radio network identifier CS-RNTI, determine that the first HARQ process is the HARQ process corresponding to the configured authorized resource; or
- the retransmission scheduling is scheduled by the PDCCH scrambled by the cell C-RNTI, and the first HARQ process is the HARQ process corresponding to the configured authorized resource, it is determined that the first HARQ process is the HARQ process corresponding to the configured authorized resource.
- the processing module 520 before the communication module receives the retransmission schedule of the first automatic HARQ process request retransmission by the network device, is further configured to:
- the second information it is determined whether to package the de-priority data, wherein the second information includes at least one of the following: whether the priority data corresponding to the de-priority data is packaged, the priority data Whether it is sent to the physical layer, whether the priority data is transmitted, and the priority of the deprioritized data and the priority of the first authorized resource of the deprioritized data, where the first authorized resource is
- the device can be used to transmit the deprioritized data before receiving the retransmission schedule.
- the processing module 520 is specifically configured to:
- the de-prioritized data is not packaged:
- the prioritized data has been packaged before the first time, and the priority of the de-prioritized data is lower than the priority of the prioritized data;
- the priority data has been packaged before the first time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the priority data;
- the priority data has been sent to the physical layer before the first time, and the priority of the de-prioritized data is lower than the priority of the priority data;
- the priority data has been sent to the physical layer before the first time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the priority data;
- the priority data has been sent before the first time, and the priority of the de-prioritized data is lower than the priority of the priority data;
- the priority data has been sent before the first time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the priority data;
- the scheduling request SR has been sent to the physical layer before the first time, and the priority of the deprioritized data is lower than the priority of the SR;
- the SR has been sent to the physical layer before the first time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the SR;
- the SR has been sent before the first time, and the priority of the deprioritized data is lower than the priority of the SR;
- the SR has been sent before the first time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the SR
- the first time before is one of the following:
- the processing module 520 is specifically configured to:
- the MAC layer does not instruct the physical layer to use the first authorized resource to transmit the deprioritized data
- the first authorized resource may be used to transmit the deprioritized data before the device receives the retransmission schedule.
- the processing module 520 is specifically configured to:
- the prioritized data has been packaged before the second time, and the priority of the de-prioritized data is lower than the priority of the prioritized data;
- the priority data has been packaged before the second time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the priority data;
- the priority data has been sent to the physical layer before the second time, and the priority of the deprioritized data is lower than the priority of the priority data;
- the priority data has been sent to the physical layer before the second time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the priority data;
- the priority data has been sent before the second time, and the priority of the de-prioritized data is lower than the priority of the priority data;
- the priority data has been sent before the second time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the priority data;
- the scheduling request SR has been sent to the physical layer before the second time, and the priority of the deprioritized data is lower than the priority of the SR;
- the SR has been sent to the physical layer before the second time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the SR;
- the SR has been sent before the second time, and the priority of the de-prioritized data is lower than the priority of the SR;
- the SR has been sent before the second time, and the priority of the first authorized resource is lower than the priority of the authorized resource corresponding to the SR;
- the second time is one of the following:
- the processing module 520 is further configured to:
- the MAC layer When the deprioritized data is packaged, the MAC layer does not instruct the physical layer to use the first authorized resource to transmit the deprioritized data;
- the first authorized resource may be used to transmit the deprioritized data before the device receives the retransmission schedule.
- the communication module is specifically configured to:
- the uplink grant scheduled by the PDCCH scrambled by the CS-RNTI is received, and the new data in the PDCCH indicates that the NDI is 1, wherein the HARQ process corresponding to the uplink grant is the first HARQ process.
- the communication module is specifically configured to:
- the processing module 520 is further configured to:
- the processing module 520510 is further configured to:
- the buffer of the first HARQ process does not store the deprioritized data, determine that the deprioritized data is not packaged;
- the authorized resource corresponding to the deprioritized data is not used before the retransmission schedule is received, it is determined that the deprioritized data is not packaged;
- the buffer of the first HARQ process stores the deprioritization data, determining that the depriority data has been packaged;
- the authorized resource corresponding to the de-prioritized data is used before the retransmission schedule is received, it is determined that the de-prioritized data has been packaged.
- the aforementioned communication module may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
- the above processing module may be one or more processors.
- the device 500 may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the device 500 are to implement the method 200 shown in FIG. For the sake of brevity, the corresponding process of the terminal device will not be repeated here.
- FIG. 6 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application.
- the communication device 600 shown in FIG. 6 includes a processor 610, and the processor 610 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
- the communication device 600 may further include a memory 620.
- the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
- the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
- the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
- the transceiver 630 may include a transmitter and a receiver.
- the transceiver 630 may further include an antenna, and the number of antennas may be one or more.
- the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, details are not repeated here. .
- the communication device 600 may specifically be a mobile terminal/terminal device of an embodiment of the application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the application.
- I won’t repeat it here.
- FIG. 7 is a schematic structural diagram of a chip of an embodiment of the present application.
- the chip 700 shown in FIG. 7 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
- the chip 700 may further include a memory 720.
- the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
- the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
- the chip 700 may further include an input interface 730.
- the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
- the chip 700 may further include an output interface 740.
- the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
- the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
- the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
- the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
- the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.
- the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
- the steps of the foregoing method embodiments may be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
- the aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
- DSP Digital Signal Processor
- ASIC application specific integrated circuit
- FPGA ready-made programmable gate array
- the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
- the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
- the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
- the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
- the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
- the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
- the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
- the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
- RAM random access memory
- SRAM static random access memory
- DRAM dynamic random access memory
- DRAM synchronous dynamic random access memory
- SDRAM double data rate synchronous dynamic random access memory
- Double Data Rate SDRAM DDR SDRAM
- ESDRAM enhanced synchronous dynamic random access memory
- Synchlink DRAM SLDRAM
- DR RAM Direct Rambus RAM
- the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.
- the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
- the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
- the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
- I will not repeat it here.
- the embodiments of the present application also provide a computer program product, including computer program instructions.
- the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For brevity, I won't repeat them here.
- the embodiment of the present application also provides a computer program.
- the computer program can be applied to the network device in the embodiment of the present application.
- the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- I won’t repeat it here.
- the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
- the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.
- the disclosed system, device, and method may be implemented in other ways.
- the device embodiments described above are only illustrative.
- the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
- the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
- each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
- the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
- the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
一种无线通信的方法和设备,该方法包括:终端设备接收网络设备对第一自动请求重传HARQ进程的重传调度;所述终端设备根据第一信息,对去优先数据进行处理,其中,所述去优先数据对应所述第一HARQ进程,所述第一信息包括以下中的至少一项:在接收到所述重传调度之前所述去优先数据是否被组包;以及在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程。
Description
本申请实施例涉及通信领域,具体涉及一种无线通信的方法和设备。
在新无线(New Radio,NR)系统中,需要支持多种业务的传输,例如,工业自动化(Factory automation)业务,传输自动化(Transport Industry),智能电力等业务,这样,可能存在给同一终端配置的资源在时域上发生冲突的情况。例如,基站在一个上行授权(UL grant)上调度传输增强移动超宽带(Enhance Mobile Broadband,eMBB)业务后,又调度在另一UL grant上调度传输高可靠低时延通信(Ultra-Reliable and Low Latency Communication,URLLC),若这两个UL grant在时域上有重叠,只能传输一个UL grant上的业务,则该业务可称为优先业务,或优先数据,该传输可以称为优先传输,对应地,另一UL grant上的业务可称为去优先业务,或去优先数据,因此,如何对该去优先数据进行重传调度以避免数据的丢失是一项亟需解决的问题。
发明内容
本申请实施例提供一种无线通信的方法和设备,有利于降低对网络设备调度的资源的浪费,并且能够将终端设备的待传输的数据尽快传输至网络设备。
第一方面,提供了一种无线通信的方法,包括:终端设备接收网络设备对第一自动请求重传HARQ进程的重传调度;所述终端设备根据第一信息,对去优先数据进行处理,其中,所述去优先数据对应所述第一HARQ进程,所述第一信息包括以下中的至少一项:在接收到所述重传调度之前所述去优先数据是否被组包;以及在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程。
第二方面,提供了一种无线通信的设备,用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地,该设备包括用于执行上述第一方面或第一方面的任一可能的实现方式中的方法的单元。
第三方面,提供了一种无线通信的设备,该设备包括:包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,执行上述第一方面或其各实现方式中的方法。
第四方面,提供了一种芯片,用于实现上述第一方面或其各实现方式中的方法。
具体地,该芯片包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有该芯片的设备执行如上述第一方面或其各实现方式中的方法。
第五方面,提供了一种计算机可读存储介质,用于存储计算机程序,该计算机程序使得计算机执行上述第一方面或其各实现方式中的方法。
第六方面,提供了一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行上述第一方面其各实现方式中的方法。
第七方面,提供了一种计算机程序,当其在计算机上运行时,使得计算机执行上述第一方面或其各实现方式中的方法。
基于上述技术方案,终端设备可以在接收到网络设备对去优先数据所在的HARQ进程的重传调度时,可以根据接收到所述重传调度之前,所述去优先数据的组包情况和/或去优先数据是否递交至HARQ进程,对所述去优先级数据进行处理,例如,对去优先数据进行组包和/或传输,有利于降低对网络设备调度的资源的浪费,并且能够将终端设备的待传输的数据尽快传输至网络设备,有利于满足对时延要求较高的业务的传输需求,提升用户体验。
图1是本申请实施例提供的一种应用场景的示意性图。
图2是本申请实施例提供的一种无线通信的方法的示意性图。
图3是根据一具体实施例的传输去优先数据的示意性图。
图4是根据另一具体实施例的传输去优先数据的示意性图。
图5是本申请实施例提供的一种无线通信的设备的示意性框图。
图6是本申请另一实施例提供的一种通信设备的示意性框图。
图7是本申请实施例提供的一种芯片的示意性框图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统,例如:全球移动通讯(Global System of Mobile communication,GSM)系统、码分多址(Code Division Multiple Access,CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access,WCDMA)系统、通用分组无线业务(General Packet Radio Service,GPRS)、长期演进(Long Term Evolution,LTE)系统、LTE频分双工(Frequency Division Duplex,FDD)系统、LTE时分双工(Time Division Duplex,TDD)、通用移动通信系统(Universal Mobile Telecommunication System,UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access,WiMAX)通信系统或5G系统等。
示例性的,本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110,网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖,并且可以与位于该覆盖区域内的终端设备进行通信。可选地,该网络设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station,BTS),也可以是WCDMA系统中的基站(NodeB,NB),还可以是LTE系统中的演进型基站(Evolutional Node B,eNB或eNodeB),或者是云无线接入网络(Cloud Radio Access Network,CRAN)中的无线控制器,或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network,PLMN)中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端设备120。作为在此使用的“终端设备”包括但不限于经由有线线路连接,如经由公共交换电话网络(Public Switched Telephone Networks,PSTN)、数字用户线路(Digital Subscriber Line,DSL)、数字电缆、直接电缆连接;和/或另一数据连接/网络;和/或经由无线接口,如,针对蜂窝网络、无线局域网(Wireless Local Area Network,WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器;和/或另一终端设备的被设置成接收/发送通信信号的装置;和/或物联网(Internet of Things,IoT)设备。被设置成通过无线接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话;可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System,PCS)终端;可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System,GPS)接收器的PDA;以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端设备可以指接入终端、用户设备(User Equipment,UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、无线本地环路(Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
可选地,终端设备120之间可以进行终端直连(Device to Device,D2D)通信。
可选地,5G系统或5G网络还可以称为新无线(New Radio,NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端设备,可选地,该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备,本申请实施例对此不做限定。
可选地,该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体,本申请实施例对此不作限定。
应理解,本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例,通信设备可包括具有通信功能的网络设备110和终端设备120,网络设备110和终端设备120可以为上文所述的具体设备,此处不再赘述;通信设备还可包括通信系统100中的其他设备,例如网络控制器、移动管理实体等其他网络实体,本申请实施例中对此不做限定。
应理解,本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
图2为本申请实施例提供的一种无线通信的方法200的示意性流程图。该方法200可以由图1所示的通信系统中的终端设备执行,如图2所示,该方法200包括至少部分如下内容:
S210,终端设备接收网络设备对第一自动请求重传HARQ进程的重传调度;
S220,所述终端设备根据第一信息,对去优先数据进行处理,其中,所述去优先数据对应所述第一HARQ进程,所述第一信息包括以下中的至少一项:在接收到所述重传调度之前所述去优先数据是否被组包;以及在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程。
应理解,本申请实施例中的去优先(deprioritized)数据是在资源冲突的情况下产生的,例如,当第一上行资源和第二上行资源冲突时,若只传输了第二上行资源上的数据,则承载在该第二上行资源上的数据可称为优先(prioritized)数据,组包的优先数据也可以称为prioritized媒体接入控制(Media Access Control,MAC)PDU协议数据单元(Protocol Data Unit,PDU),承载或能够承载在第一上行资源上未被传输的数据可称为去优先(deprioritized)数据,组包的去优先数据也可以称为deprioritized MAC PDU。
应理解,在本申请实施例中,去优先数据也可以称为低优先数据,低优先MAC PDU。
需要说明的是,在本申请实施例中,所述去优先数据对应所述第一HARQ进程可以为所述去优先数据在所述第一HARQ进程上发送,或者说,所述去优先数据是使用所述第一HARQ进程传输的。
还需要说明的是,在本申请实施例中,所述第一HARQ进程对应的所述去优先数据可以为在所述第一HARQ进程上发送的去优先数据,或者说,使用所述第一HARQ进程传输的去优先数据。
可选地,所述第一上行资源和第二上行资源冲突可以指所述第一上行资源和所述第二上行资源在时域上至少部分重叠。例如,所述第一上行资源和所述第二上行资源的起始时刻可以相同,结束时刻可以不同,或者所述第一上行资源和所述第二上行资源的起始时刻可以不同,结束时刻可以相同,或者,所述第一上行资源和所述第二上行资源的起始时刻可以不同,结束时刻也可以不同,中间部分可以存在重叠,或者,所述第一上行资源和所述第二上行资源的起始时刻可以相同,结束时刻也可以相同,本申请实施例对此不作限定。
可选地,所述第一上行资源可以为配置授权(Configured Grant,CG)资源,动态授权(Dynamic Grant,DG)资源,上行共享信道(Uplink Shared Channel,UL-SCH)的上行授权,或上行控制信息(Uplink Control Information,UCI)的上行授权等上行资源,本申请实施例对此不作限定。
可选地,所述第二上行资源可以为CG资源,DG资源,UL-SCH的上行授权,或UCI的上行授权等上行资源,本申请实施例对此不作限定。以下以CG资源和DG资源发生冲突为例进行说明,但本申请并不限于此。
在本申请实施例中,CG资源为半静态调度的资源,网络设备给终端设备配置该CG资源之后,可以配置即激活(例如对于类型1的CG资源(Type-1CG)),也可以再通过动态信令例如DCI激活该CG资源(例如对于类型2的CG资源(Type-2CG),在该CG资源激活之后,该终端设备可以使用该CG资源进行传输,该CG资源可以为周期性的资源,该终端设备可以多次使用该CG资源进行传输。
在本申请实施例中,DG资源为动态调度的资源,网络设备给终端设备配置该DG资源之后,该终端设备可以使用该DG资源进行传输,该DG资源通常为单次使用的资源,在网络设备配置该DG资源之后,终端设备通常只能使用该DG资源进行单次传输。
可选地,在本申请实施例中,在发生资源冲突的情况下,所述终端设备可以不对所述去优先数据进行组包(记为实施例1)或者也可以对所述去优先数据进行组包(记为实施例2),进一步地,在接收到网络设备对所述去优先数据所在的HARQ进程的重传调度的情况下,所述终端设备可以根据所述HARQ进程对应的去优先数据是否被组包,对所述去优先数据进行处理,例如,若所述去优先数据未组包,所述终端设备可以对所述去优先数据进行组包,进一步对组包的所述去优先数据进行传输,例如可以采用新传方式传输所述去优先数据;又例如,若所述去优先数据已组包,所述终端设备可以对组包的所述去优先数据进行传输,例如可以采用新传或重传方式传输所述去优先数据。
以下,结合该实施例1和实施例2两种具体情况对所述去优先数据的传输方式进行具体说明。
实施例1:
终端设备确定在第二授权资源上传输第二数据,在所述第二授权资源之前若所述终端设备接收到网络设备调度的第一授权资源,该第一授权资源用于传输第一数据,若第一授权资源和第二授权资源存在冲突,所述终端设备可以不对所述第一数据进行组包,在传输时,只传输所述第二数据,则所述第二数据为优先数据,所述第一数据为去优先数据。其中,该第一授权资源对应第一HARQ进程,所述第二授权资源对应第二HARQ进程。
这里,所述第一授权资源和所述第二授权资源可以对应于前文所述的第一上行资源和第二上行资源,具体实现可以参考上文的具体实现,这里不再赘述。
作为一个示例,所述终端设备可以任何情况都不对所述去优先数据进行组包。作为另一示例,所 述终端设备可以在特定条件下,不对所述去优先数据进行组包。
例如,所述终端设备可以根据所述优先数据是否被组包,所述优先数据的传输情况,所述优先数据的优先级,所述第二授权资源的优先级,所述去优先数据的优先级和所述第一授权资源的优先级中的至少之一确定是否对所述去优先数据进行组包。
应理解,这里的优先数据为该去优先数据对应的优先数据,所述去优先数据对应的优先数据为当发生资源冲突时,被优先传输的数据,该去优先数据为由于资源冲突未被传输的数据。
可选地,所述优先数据的传输情况可以包括所述优先数据是否被传输至物理层和/或所述优先数据是否被传输(或者说,所述优先数据是否被空口传输)。
作为一个示例,若在第一时间之前,所述优先数据已发送至物理层或已经组包,所述终端设备可以不对所述去优先数据进行组包;
作为一个示例,若在第一时间之前所述优先数据已组包完成,并且所述去优先数据的优先级低于所述优先数据的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以不对所述去优先数据进行组包。
作为另一个示例,若在第一时间之前所述优先数据已组包完成,并且所述第一授权资源的优先级低于所述第二授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以不对所述去优先数据进行组包;
作为另一个示例,若在第一时间之前,所述优先数据已发送至物理层,并且所述去优先数据的优先级低于所述优先数据的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以不对所述去优先数据进行组包;
作为另一个示例,若在第一时间之前,所述优先数据已发送至物理层,并且所述第一授权资源的优先级低于所述第二授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以不对所述去优先数据进行组包;
作为另一个示例,若在第一时间之前所述优先数据已发送,并且所述去优先数据的优先级低于所述优先数据的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以不对所述去优先数据进行组包;
作为另一个示例,若在第一时间之前所述优先数据已发送,并且所述第一授权资源的优先级低于所述第二授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以不对所述去优先数据进行组包;
作为另一个示例,若在第一时间之前调度请求(Scheduling Request,SR)已发送至物理层,并且所述去优先数据的优先级低于所述SR的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以不对所述去优先数据进行组包;
作为另一个示例,若在第一时间之前SR已发送至物理层,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以不对所述去优先数据进行组包;
作为另一个示例,若在第一时间之前SR已发送,并且所述去优先数据的优先级低于所述SR的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以不对所述去优先数据进行组包;
作为另一个示例,若在第一时间之前SR已发送,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以不对所述去优先数据进行组包。
可选地,在一些实施例中,所述第一优先级门限可以预定义的,或者也可以是网络设备配置的。
可选地,在一些实施例中,所述第二优先级门限可以预定义的,或者也可以是网络设备配置的。
需要说明的是,所述第一时间之前可以指以下中的一种:
所述终端设备获取所述去优先数据的第一授权资源之前,例如,所述终端设备接收到网络设备配置的所述第一授权资源之前;或者,
所述去优先数据的第一授权资源可用之前,所述第一授权资源的起始时域位置之前;或者,
在所述去优先数据的第一授权资源上有待传输数据之前,或者说,有能承载在所述去优先数据的第一授权资源上的数据之前。
当然,若所述第一授权资源的优先级高于所述第二授权资源的优先级,或者所述第一授权资源能承载的数据的优先级高于所述第二授权资源能承载的数据的优先级,可以不对所述第一授权资源进行组包。
应理解,在本申请实施例中,当有能承载所述第一授权资源上的数据时,不对所述第一授权资源 进行组包可以包括不对所述第一授权资源上的数据进行组包,即不对所述去优先数据进行组包,二者的含义相同,可以相互替换。
对应地,当有能承载所述第一授权资源上的数据时,对所述第一授权资源进行组包可以包括对所述第一授权资源上的数据进行组包,即对所述去优先数据进行组包,二者的含义相同,可以相互替换。
应理解,在本申请实施例中,是否对去优先数据进行组包,也可以包括是否对去优先的资源(即第一授权资源)进行组包。
在不对去优先数据进行组包的情况下,进一步地,所述终端设备的MAC层还可以不将所述第一授权资源的信息递交至所述第一HARQ进程,和/或不指示物理层使用所述第一授权资源传输数据。
进一步地,若所述终端设备接收到对网络设备所述第一HARQ进程的重传调度,所述终端设备可以根据在接收到所述重传调度之前所述第一HARQ进程对应的去优先数据是否被组包,对所述去优先数据进行传输。
例如,若在接收到所述重传调度之前所述第一HARQ进程的去优先数据未被组包,所述终端设备可以对所述去优先数据进行组包,进一步可以对组包的所述去优先数据(即deprioritized MAC PDU)进行传输,例如,可以对deprioritized MAC PDU进行新传。
在一些情况下,所述第一HARQ进程的去优先数据未被组包,也可以理解为所述第一HARQ进程的缓存(buffer)为空。
可选地,在本申请实施例中,所述终端设备可以接收网络设备发送的物理下行控制信道(Physical Downlink Control Channel,PDCCH),所述PDCCH可以包括网络设备调度的上行授权(UL grant)的信息,所述上行授权对应第一HARQ进程,所述终端设备可以根据加扰所述PDCCH的无线网络临时标识符(Radio Network Temporary Identity,RNTI)和/或所述PDCCH中的新数据指示(New Data Indicator,NDI),确定网络设备对所述第一HARQ进程的调度是重传调度还是初传调度。
例如,若所述PDCCH是由配置调度无线网络临时标识(Configured Scheduling-RNTI,CS-RNTI)加扰的,并且所述NDI为1,可以确定对所述第一HARQ进程的调度为重传调度。
又例如,若所述PDCCH是由配置调度无线网络临时标识(Configured Scheduling-RNTI,CS-RNTI)加扰的,可以确定对所述第一HARQ进程的调度为重传调度。
又例如,若所述PDCCH是由小区无线网络临时标识(Cell-RNTI,C-RNTI)加扰的,且NDI未翻转,可以确定对所述第一HARQ进程的调度为重传调度。
又例如,若所述PDCCH是由小区无线网络临时标识(Cell-RNTI,C-RNTI)加扰的,且对应的HARQ进程为空,可以确定对所述第一HARQ进程的调度为重传调度。
又例如,若所述PDCCH是由小区无线网络临时标识(Cell-RNTI,C-RNTI)加扰的,且对应的HARQ进程为由于资源冲突导致未使用的资源所对应的HARQ进程,确定对所述第一HARQ进程的调度为重传调度。
又例如,若所述PDCCH是由小区无线网络临时标识(Cell-RNTI,C-RNTI)加扰的,且对应的HARQ进程为去优先数据对应的HARQ进程,可以确定对所述第一HARQ进程的调度为重传调度。
可选地,在本申请实施例中,所述终端设备根据所述第一HARQ进程是否保存有所述去优先数据或所述去优先数据对应的授权资源是否被使用确定所述去优先数据是否被组包。
例如,若所述第一HARQ进程的缓存为空,可以确定所述去优先数据未被组包;
又例如,若所述第一HARQ进程的缓存未保存所述去优先数据,可以确定所述去优先数据未被组包;
又例如,在接收到所述重传调度之前,所述第一授权资源未被使用,可以确定所述去优先数据未被组包。
可选地,所述第一授权资源未被使用可以包括所述第一授权资源被忽略,或所述第一授权资源上没有数据传输,或者资源冲突场景中的一个授权资源,即该第一授权资源可以是由于与其他授权资源发生资源冲突导致未被使用的。
对应地,若所述第一HARQ进程的缓存不为空,可以确定所述去优先数据被组包;或者,若所述第一HARQ进程的缓存保存有所述去优先数据,可以确定所述去优先数据被组包;或者,在接收到所述重传调度之前,所述第一授权资源被使用,可以确定所述去优先数据被组包。
进一步地,在接收到对所述第一HARQ进程的重传调度,并且所述去优先数据未组包的情况下,所述终端设备可以对所述去优先数据进行组包,并对组包的去优先数据进行传输。
在一些情况下,所述去优先数据未组包,也可以理解为所述第一HARQ进程的buffer为空。
具体地,所述终端设备对所述去优先数据进行组包可以包括所述终端设备的复用组包实体(Multiplexing and assembly entity)对所述去优先数据进行组包,得到deprioritized MAC PDU,例如, 对所述去优先数据进行加包头处理。
进一步地,所述终端设备对组包的去优先数据进行传输可以包括如下中的至少一项:所述终端设备的MAC层从复用组包实体获取deprioritized MAC PDU,所述终端设备的MAC层将所述deprioritized MAC PDU,所述重传调度的上行授权和所述上行授权的HARQ信息(例如,冗余版本(Redundancy Version,RV))中的至少一项递交至所述第一HARQ进程。在所述deprioritized MAC PDU递交至所述第一HARQ进程后,所述终端设备的MAC层指示所述第一HARQ进程触发新传,进一步地,使用所述第一HARQ进程对所述deprioritized MAC PDU进行新传。
在一些实施例中,若重传调度的上行授权为配置授权资源,即所述第一HARQ进程为配置授权资源的HARQ进程,或者,重传调度的上行授权为动态授权资源且所述第一HARQ进程为对应配置授权资源的HARQ进程,所述终端设备还可以在开始传输所述deprioritized MAC PDU时,开启或重启所述第一HARQ进程对应的配置授权定时器,在该配置授权定时器运行期间该第一HARQ进程中保存的deprioritized MAC PDU不被冲掉(flush),有利于防止所述去优先数据的丢失。
因此,在该实施例1中,所述终端设备可以在接收到网络设备对去优先数据的HARQ进程的重传调度时,对未组包的去优先数据进行组包,并进一步按照新传方式传输组包的所述去优先数据,有利于降低对网络设备调度的资源的浪费,并且能够将终端设备的待传输的数据尽快传输至网络设备,有利于满足对时延要求较高的业务的传输需求,提升用户体验。
实施例2:
若终端设备确定在第二授权资源上传输第二数据,在所述第二授权资源之前若所述终端设备接收到网络设备调度的第一授权资源,该第一授权资源用于传输第一数据,若第一授权资源和第二授权资源存在冲突,所述终端设备可以对所述第一数据进行组包,在传输时,只传输所述第二数据,则所述第二数据为优先数据,所述第一数据为去优先数据。其中,该第一授权资源对应第一HARQ进程,所述第一授权资源对应第二HARQ进程。
这里,所述第一授权资源和所述第二授权资源的具体实现可以参考上文的具体实现,这里不再赘述。
作为一个示例,所述终端设备可以任何情况下都对所述去优先数据进行组包。作为另一示例,所述终端设备可以在特定条件下,对所述去优先数据进行组包。
例如,所述终端设备可以根据所述优先数据是否被组包,所述优先数据的传输情况,所述优先数据的优先级,所述第二授权资源的优先级,所述去优先数据的优先级和所述第一授权资源的优先级中的至少之一确定是否对所述去优先数据进行组包。
可选地,所述优先数据的传输情况可以包括所述优先数据是否被传输至物理层和/或所述优先数据是否被传输(或者说,所述优先数据是否被空口传输)。
作为一个示例,若在第二时间之前所述优先数据已组包完成,并且所述去优先数据的优先级低于所述优先数据的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以对所述去优先数据进行组包。
作为另一个示例,若在第二时间之前所述优先数据已组包完成,并且所述第一授权资源的优先级低于所述第二授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以对所述去优先数据进行组包;
作为另一个示例,若在第二时间之前,所述优先数据已发送至物理层,并且所述去优先数据的优先级低于所述优先数据的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以对所述去优先数据进行组包;
作为另一个示例,若在第二时间之前,所述优先数据已发送至物理层,并且所述第一授权资源的优先级低于所述第二授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以对所述去优先数据进行组包;
作为另一个示例,若在第二时间之前所述优先数据已发送,并且所述去优先数据的优先级低于所述优先数据的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以对所述去优先数据进行组包;
作为另一个示例,若在第二时间之前所述优先数据已发送,并且所述第一授权资源的优先级低于所述第二授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以对所述去优先数据进行组包;
作为另一个示例,若在第二时间之前调度请求(Scheduling Request,SR)已发送至物理层,并且所述去优先数据的优先级低于所述SR的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以对所述去优先数据进行组包;
作为另一个示例,若在第二时间之前SR已发送至物理层,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以对所述去优先数据进行组包;
作为另一个示例,若在第二时间之前SR已发送,并且所述去优先数据的优先级低于所述SR的优先级,或所述去优先数据的优先级低于第一优先级门限,所述终端设备可以对所述去优先数据进行组包;
作为另一个示例,若在第二时间之前SR已发送,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级,或所述第一授权资源的优先级低于第二优先级门限,所述终端设备可以对所述去优先数据进行组包。
可选地,在另一些实施例中,所述终端设备也可以在所述优先数据已组包,或被发送至物理层,或被传输,和/或,所述去优先数据的优先级高于优先数据的优先级,或者所述去优先数据的优先级高于特定优先级门限的情况下,对所述去优先数据进行组包。
可选地,在另一些实施例中,所述终端设备也可以在所述优先数据已组包,或被发送至物理层,或被传输,和/或,所述第一授权资源的优先级高于第二授权资源的优先级,或者所述去第一授权资源的优先级高于特定优先级门限的情况下,对所述去优先数据进行组包。
例如,若所述第一授权资源的优先级高于所述第二授权资源的优先级,或者,所述第一授权资源能承载的数据的优先级高于所述第二授权资源能承载的数据的优先级,可以对所述第一授权资源进行组包,即对所述第一授权资源上的去优先数据进行组包。
又例如,若在第二时间之前,所述去优先数据对应的优先数据已发送至物理层或已经组包,所述终端设备可以对所述去优先数据进行组包。
需要说明的是,在本申请实施例中,所述第二时间之前可以指以下中的一种:
所述终端设备获取所述去优先数据的第一授权资源之前,例如,所述终端设备接收到网络设备配置的所述第一授权资源之前;或者,
所述去优先数据的第一授权资源可用之前;或者,
在所述去优先数据的第一授权资源上有待传输数据之前,或者说,有能承载在所述去优先数据的第一授权资源上的数据之前。
应理解,在本申请实施例中,是否对去优先数据进行组包,也可以包括是否对去优先的资源(即第一授权资源)进行组包。
在对去优先数据进行组包的情况下,进一步地,所述终端设备的MAC层可以将所述第一授权资源的信息递交至所述第一HARQ进程,和/或不指示物理层使用所述第一授权资源传输数据,即不进行所述去优先数据的传输。
进一步地,若所述终端设备接收到对网络设备所述第一HARQ进程的重传调度,应理解,在该实施例2中,确定网络设备对所述第一HAQR进程的调度为重传调度的确定方式可以参考实施例1的相关描述,这里不再赘述。
可选地,在该实施例2中,所述终端设备也可以根据所述第一HARQ进程是否保存有所述去优先数据或所述去优先数据对应的授权资源是否被使用确定所述去优先数据是否被组包。
例如,若所述第一HARQ进程的缓存未保存所述去优先数据,可以确定所述去优先数据未被组包;
又例如,在接收到所述重传调度之前,所述第一授权资源未被使用,可以确定所述去优先数据未被组包;
又例如,若所述第一HARQ进程的缓存为空,可以确定所述去优先数据未被组包;
又例如,若所述第一HARQ进程的缓存为空,且在接收到所述重传调度之前,所述第一授权资源未被使用,可以确定所述去优先数据未被组包。
可选地,所述第一授权资源未被使用可以包括所述第一授权资源被忽略,或所述第一授权资源上没有数据传输,或者资源冲突场景中的一个授权资源,即该第一授权资源可以是由于与其他授权资源发生资源冲突导致未被使用的。
对应地,若所述第一HARQ进程的缓存保存有所述去优先数据,可以确定所述去优先数据被组包;或者,在接收到所述重传调度之前,所述第一授权资源被使用,可以确定所述去优先数据被组包;或者,若所述第一HARQ进程的缓存不为空,且在接收到所述重传调度之前,所述第一授权资源被使用,可以确定所述去优先数据被组包;或者,若所述第一HARQ进程的缓存不为空,可以确定所述去优先数据被组包。
进一步地,在接收到所述第一HARQ进程的重传调度,并且所述去优先数据已组包的情况下, 所述终端设备可以对组包的去优先数据进行传输。
具体地,所述终端设备可以根据在接收到所述重传调度之前组包的去优先数据包是否递交至所述第一HARQ进程,对所述去优先数据进行传输,例如可以采用新传或重传方式传输所述去优先数据。
例如,若在接收到所述重传调度之前对组包的所述去优先数据(即deprioritized MAC PDU)未递交至或未保存在所述第一HARQ进程,所述终端设备可以对deprioritized MAC PDU进行新传。
例如,若在接收到所述重传调度之前对组包的所述去优先数据(即deprioritized MAC PDU)已递交至或保存在所述第一HARQ进程,所述终端设备可以对deprioritized MAC PDU进行重传。
在另一些实施例中,在所述去优先数据已组包的情况下,可以认为所述去优先数据已被递交至所述第一HARQ进程,此情况下,所述终端设备可以直接对第一HARQ进程中的去优先数据进行新传或重传,而不必判断所述去优先数据是否被递交至所述第一HARQ进程。
作为一个具体实施例,所述终端设备对所述去优先数据进行新传可以包括以下中的至少一项:所述终端设备的MAC层可以从复用组包实体获取deprioritized MAC PDU,进一步地,所述终端设备的MAC层可以将所述deprioritized MAC PDU,所述重传调度的上行授权和所述上行授权的HARQ信息中的至少一项递交至所述第一HARQ进程。在所述deprioritized MAC PDU递交至所述第一HARQ进程的情况下,所述终端设备的MAC层可以指示所述第一HARQ进程触发新传,进一步地,可以使用所述第一HARQ进程对所述deprioritized MAC PDU进行新传。
作为另一个具体实施例,所述终端设备可以对所述去优先数据进行重传可以包括如下中的至少一项:所述终端设备的MAC层可以将所述重传调度的上行授权和所述上行授权的HARQ信息中的至少一项递交至所述第一HARQ进程。进一步地,所述终端设备的MAC层可以指示所述第一HARQ进程触发重传,更进一步地,所述终端设备可以使用所述第一HARQ进程对所述deprioritized MAC PDU进行重传。
在该实施例2中,若重传调度的上行授权为配置授权资源,即所述第一HARQ进程为配置授权资源的HARQ进程,或者,重传调度的上行授权为动态授权资源且所述第一HARQ进程为对应配置授权资源的HARQ进程,所述终端设备还可以在开始传输所述deprioritized MAC PDU时,开启或重启所述第一HARQ进程对应的配置授权定时器,在该配置授权定时器运行期间该第一HARQ进程中保存的deprioritized MAC PDU不被冲掉(flush),有利于防止所述去优先数据的丢失。
因此,在该实施例2中,所述终端设备可以在接收到网络设备对去优先数据的HARQ进程的重传调度时,可以按照新传或重传方式传输组包的所述去优先数据,有利于降低对网络设备调度的资源的浪费,并且能够将终端设备的待传输的数据尽快传输至网络设备,有利于满足对时延要求较高的业务的传输需求,提升用户体验。并且在网络设备重传调度之前终端设备已对去优先数据进行组包,有利于避免在接收到重传调度之后再进行组包所带来的组包延迟,提升用户体验。
以下,结合图3和图4所示的具体实施例,对本申请实施例的无线通信的方法进行详细描述。
在图3所示的示例中,网络设备可以为终端设备配置CG资源,可选地,该CG资源的配置信息可以包括如下中的至少一项:
CG资源的周期,例如,1个时隙;
CG资源的标识(Identify,ID),例如,ID可以为1;
CG资源的HARQ进程的配置授权定时器(configuredGrantTimer),例如,该定时器的时长可以为3,表示3个时隙,或3个CG周期的长度。
CG资源对应的HARQ进程号,例如,HARQ进程号可以为2,3,4。
进一步地,网络设备通过下行控制信息(Downlink Control Information,DCI)指示CG标识为1的CG资源激活。此后,终端设备使用该CG资源进行数据传输。
在时刻t
1,终端设备确定在时刻t
3有配置且激活的CG资源,该终端设备可以在时刻t
1对待传输的数据进行组包,得到MAC PDU1,可选地,所述MAC PDU1可以包括URLLC业务对应的逻辑信道(Logical Channel,LCH)中的数据,其中,时刻t
1早于时刻t
3。
进一步地,在时刻t
1之后的时刻t
2,终端设备接收到网络设备通过DCI所调度的一个DG资源,若该DG资源仅用于传输低优先级业务,例如,eMBB业务,该DG资源和ID为1的CG资源的HARQ进程不同,如DG资源对应HARQ进程1,CG资源对应HARQ进程2。
当该DG资源和ID为1的CG资源存在重叠时,例如,在时刻t
3发生重叠,所述终端设备可以执行用户内优先(intra-UE prioritization),确定优先传输DG资源上的数据,例如,由于MAC PDU1中承载的是URLLC业务,DG资源仅能承载低优先级业务,则可以认为ID为1的CG资源的优先级高于该DG资源的优先级,优先传输MAC PDU1。则所述终端设备可以执行如下操作中至少一个:
1,所述终端设备可以不对DG资源上的待传输的数据进行组包,即不生成MAC PDU2。则该 HARQ进程1中没有保存该MAC PDU2。
2,所述终端设备可以不将所述DG资源递交至所述HARQ进程1。
3,所述终端设备可以不指示物理层使用所述DG资源进行数据传输。
其后,若所述终端设备接收到所述网络设备对所述HARQ进程1的重传调度。所述终端设备可以判断使用所述HARQ进程1的去优先数据是否被组包,或者说,判断是否存在组包的去优先数据,具体确定方式可以结合前文的相关描述,这里不再赘述。
进一步地,若使用所述HARQ进程1的去优先数据未组包,所述终端设备可以执行如下操作中的至少一项:
1、终端设备的复用组包实体对所述去优先数据进行组包,得到MAC PDU2;
2、终端设备的MAC层从所述复用组包实体获取所述MAC PDU2;
3、所述终端设备的MAC层将所述MAC PDU2,所述重传调度的上行授权的信息,所述上行授权的HARQ信息中的至少一项递交至所述HARQ进程1;
4、所述终端设备的MAC层指示所述HARQ进程1触发新传。
可选地,在一些实施例中,若所述去优先数据是调度在CG资源上传输的,所述终端设备可以在开始传输所述MAC PDU2时,开启或重启所述HARQ进程1对应的配置授权定时器。
在图4所示的示例中,网络设备可以为终端设备配置CG资源,可选地,该CG资源的配置信息可以包括如下中的至少一项:
CG资源的周期,例如,1个时隙;
CG资源的标识(Identify,ID),例如,ID可以为1;
CG资源的HARQ进程的配置授权定时器(configuredGrantTimer),例如,该定时器的时长可以为3,表示3个时隙,或3个CG周期的长度。
CG资源对应的HARQ进程号,例如,HARQ进程号可以为2,3,4。
进一步地,网络设备通过下行控制信息(Downlink Control Information,DCI)指示CG标识为1的CG资源激活。此后,终端设备使用该CG资源进行数据传输。
在某一时刻t
1,终端设备确定在时刻t
3有配置且激活的CG资源,该终端设备可以在时刻t
1对待传输的数据进行组包,得到MAC PDU1,可选地,所述MAC PDU1可以包括URLLC业务对应的逻辑信道(Logical Channel,LCH)中的数据,其中,时刻t
1早于时刻t
3。
进一步地,在时刻t
1之后的时刻t
2,终端设备接收到网络设备通过DCI所调度的一个DG资源,若该DG资源仅用于传输低优先级业务,例如,eMBB业务,该DG资源和ID为1的CG资源的HARQ进程不同,如DG资源对应HARQ进程1,CG资源对应HARQ进程2。
当该DG资源和ID为1的CG资源存在重叠时,例如,在时刻t
3发生重叠,所述终端设备可以执行用户内优先(intra-UE prioritization),确定优先传输DG资源上的数据,例如,由于MAC PDU1中承载的是URLLC业务,DG资源仅能承载低优先级业务,则可以认为ID为1的CG资源的优先级高于该DG资源的优先级,优先传输MAC PDU1。则所述终端设备可以执行如下操作中至少一个:
1,所述终端设备可以对DG资源上的待传输的数据进行组包,即生成MAC PDU2。则该HARQ进程1中保存有该MAC PDU2。
2,所述终端设备可以将所述DG资源递交至所述HARQ进程1。
3,所述终端设备可以不指示物理层使用所述DG资源进行数据传输。
其后,若所述终端设备接收到所述网络设备对所述HARQ进程1的重传调度。所述终端设备可以判断使用所述HARQ进程1的去优先数据是否被组包,或者说,判断是否存在组包的去优先数据,具体确定方式可以结合前文的相关描述,这里不再赘述。
作为一个实施例,若使用所述HARQ进程1的去优先数据已组包,所述终端设备可以执行如下操作中的至少一项:
1、终端设备的MAC层从所述复用组包实体获取所述deprioritized MAC PDU
2、所述终端设备的MAC层将所述MAC PDU2,所述重传调度的上行授权的信息,所述上行授权的HARQ信息中的至少一项递交至所述HARQ进程1;
3、所述终端设备的MAC层指示所述HARQ进程1触发新传。
作为另一个实施例,若使用所述HARQ进程1的去优先数据已组包,所述终端设备可以执行如下操作中的至少一项:
1、所述终端设备的MAC层将所述重传调度的上行授权的信息和所述上行授权的HARQ信息中的至少一项递交至所述HARQ进程1;
2、所述终端设备的MAC层指示所述HARQ进程1触发重传。
可选地,在一些实施例中,若所述去优先数据是调度在CG资源上传输的,所述终端设备可以在开始传输所述MAC PDU2时,开启或重启所述HARQ进程1对应的配置授权定时器。
上文结合图2至图4,详细描述了本申请的方法实施例,下文结合图5至图7,详细描述本申请的装置实施例,应理解,装置实施例与方法实施例相互对应,类似的描述可以参照方法实施例。
图5示出了根据本申请实施例的无线通信的设备500的示意性框图。如图5所示,该设备500包括:
通信模块510,用于接收网络设备对第一自动请求重传HARQ进程的重传调度;
处理模块520,用于根据第一信息,对去优先数据进行处理,其中,所述去优先数据对应所述第一HARQ进程,所述第一信息包括以下中的至少一项:
在接收到所述重传调度之前所述去优先数据是否被组包;以及
在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程。
可选地,在一些实施例中,所述处理模块520具体用于:
若在接收到所述重传调度之前所述去优先数据未组包,将所述去优先数据进行组包;
触发使用所述第一HARQ进程新传所述去优先数据。
可选地,在一些实施例中,所述处理模块520具体用于:
若在接收到所述重传调度之前所述去优先数据已组包,根据在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程,触发使用所述第一HARQ进程新传还是重传所述去优先数据。
可选地,在一些实施例中,所述处理模块520具体用于:
若在接收到所述重传调度之前所述去优先数据未递交至所述第一HARQ进程,触发使用所述第一HARQ进程新传所述去优先数据。
可选地,在一些实施例中,所述处理模块520具体用于:
若在接收到所述重传调度之前所述去优先数据已递交至所述第一HARQ进程,触发使用所述第一HARQ进程重传所述去优先数据。
可选地,在一些实施例中,所述处理模块520具体用于执行以下中的至少一项:
获取组包的所述去优先数据;
将组包的所述去优先数据,所述重传调度的上行授权,所述上行授权的HARQ信息中的至少一项递交至所述第一HARQ进程;
指示所述第一HARQ进程对组包的所述去优先数据进行新传。
可选地,在一些实施例中,所述处理模块520具体用于执行以下中的至少一项:
将所述重传调度的上行授权和/或所述上行授权的HARQ信息递交至所述第一HARQ进程;
指示所述第一HARQ进程对组包的所述去优先数据进行重传。
可选地,在一些实施例中,所述处理模块520还用于:
若所述第一HARQ进程为配置授权资源对应的HARQ进程,在开始传输所述去优先数据时,开启或重启所述第一HARQ进程的配置授权定时器。
可选地,在一些实施例中,所述处理模块520还用于:
若所述重传调度是配置调度无线网络临时标识CS-RNTI加扰的物理下行控制信道PDCCH调度的,确定所述第一HARQ进程为配置授权资源对应的HARQ进程;或
若所述重传调度为小区C-RNTI加扰的PDCCH调度的,且所述第一HARQ进程为对应配置授权资源的HARQ进程,确定所述第一HARQ进程为配置授权资源对应的HARQ进程。
可选地,在一些实施例中,在所述通信模块接收网络设备对第一自动请求重传HARQ进程的重传调度之前,所述处理模块520还用于:
根据第二信息,确定是否对所述去优先数据进行组包,其中,所述第二信息包括以下中的至少一项:所述去优先数据对应的优先数据是否被组包,所述优先数据是否被发送给物理层,所述优先数据是否被传输,以及,所述去优先数据的优先级和所述去优先数据的第一授权资源的优先级,其中,所述第一授权资源在所述设备接收到所述重传调度之前可用于传输所述去优先数据。
可选地,在一些实施例中,所述处理模块520具体用于:
在满足以下条件中的至少一个时,不对所述去优先数据进行组包:
在第一时间之前所述优先数据已组包完成,并且所述去优先数据的优先级低于所述优先数据的优先级;
在第一时间之前所述优先数据已组包完成,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;
在第一时间之前所述优先数据已发送至物理层,并且所述去优先数据的优先级低于所述优先数据的优先级;
在第一时间之前所述优先数据已发送至物理层,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;
在第一时间之前所述优先数据已发送,并且所述去优先数据的优先级低于所述优先数据的优先级;
在第一时间之前所述优先数据已发送,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;
在第一时间之前调度请求SR已发送至物理层,并且所述去优先数据的优先级低于所述SR的优先级;
在第一时间之前SR已发送至物理层,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级;
在第一时间之前SR已发送,并且所述去优先数据的优先级低于所述SR的优先级;以及,
在第一时间之前SR已发送,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级
其中,所述第一时间之前为以下中的一种:
所述设备接收所述网络设备配置的所述第一授权资源的时间之前;
所述第一授权资源的起始时域位置之前;
在所述第一授权资源上有待传输数据之前。
可选地,在一些实施例中,所述处理模块520具体用于:
在不组包所述去优先数据的情况下,不将所述去优先数据和/或用于传输所述去优先数据的第一授权资源递交至所述第一授权资源对应的HARQ进程;和/或
在不组包所述去优先数据的情况下,在MAC层不指示物理层使用所述第一授权资源传输所述去优先数据;
其中,所述第一授权资源在所述设备接收到所述重传调度之前可用于传输所述去优先数据。
可选地,在一些实施例中,所述处理模块520具体用于:
在满足以下条件中的至少一个时,对所述去优先数据进行组包处理:
在第二时间之前所述优先数据已组包完成,并且所述去优先数据的优先级低于所述优先数据的优先级;
在第二时间之前所述优先数据已组包完成,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;
在第二时间之前所述优先数据已发送至物理层,并且所述去优先数据的优先级低于所述优先数据的优先级;
在第二时间之前所述优先数据已发送至物理层,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;
在第二时间之前所述优先数据已发送,并且所述去优先数据的优先级低于所述优先数据的优先级;
在第二时间之前所述优先数据已发送,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;
在第二时间之前调度请求SR已发送至物理层,并且所述去优先数据的优先级低于所述SR的优先级;
在第二时间之前SR已发送至物理层,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级;
在第二时间之前SR已发送,并且所述去优先数据的优先级低于所述SR的优先级;以及,
在第二时间之前SR已发送,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级;
其中,所述第二时间为以下中的一种:
所述设备接收所述网络设备配置的所述第一授权资源的时间之前;
所述第一授权资源的起始时域位置之前;
在所述第一授权资源上有待传输数据之前。
可选地,在一些实施例中,所述处理模块520还用于:
在组包所述去优先数据的情况下,不将所述去优先数据和/或用于传输所述去优先数据的第一授 权资源递交至所述第一授权资源对应的HARQ进程;和/或
在组包所述去优先数据的情况下,在MAC层不指示物理层使用所述第一授权资源传输所述去优先数据;
其中,所述第一授权资源在所述设备接收到所述重传调度之前可用于传输所述去优先数据。
可选地,在一些实施例中,所述通信模块具体用于:
接收通过CS-RNTI加扰的PDCCH调度的上行授权,且所述PDCCH中的新数据指示NDI为1,其中,所述上行授权对应的HARQ进程为所述第一HARQ进程。
可选地,在一些实施例中,所述通信模块具体用于:
接收通过C-RNTI加扰PDCCH调度的上行授权,其中,所述上行授权对应的HARQ进程为所述第一HARQ进程。
可选地,在一些实施例中,所述处理模块520还用于:
根据以下中的至少一项,确定所述去优先数据是否被组包:
所述第一HARQ进程的缓存是否为空;
所述第一HARQ进程的缓存是否保存所述去优先数据;以及,
在接收到所述重传调度之前,所述去优先数据对应的授权资源是否被使用。
可选地,在一些实施例中,所述处理模块520510还用于:
若所述第一HARQ进程中的缓存为空,确定所述去优先数据未组包;或
若所述第一HARQ进程的缓存未保存所述去优先数据,确定所述去优先数据未组包;或
若在接收到所述重传调度之前,所述去优先数据对应的授权资源未被使用,确定所述去优先数据未组包;或
若所述第一HARQ进程中的缓存不为空,确定所述去优先数据已组包;或
若所述第一HARQ进程的缓存保存有所述去优先数据,确定所述去优先数据已组包;或
若在接收到所述重传调度之前,所述去优先数据对应的授权资源被使用,确定所述去优先数据已组包。
可选地,在一些实施例中,上述通信模块可以是通信接口或收发器,或者是通信芯片或者片上系统的输入输出接口。上述处理模块可以是一个或多个处理器。
应理解,根据本申请实施例的设备500可对应于本申请方法实施例中的终端设备,并且设备500中的各个单元的上述和其它操作和/或功能分别为了实现图2所示方法200中终端设备的相应流程,为了简洁,在此不再赘述。
图6是本申请实施例提供的一种通信设备600示意性结构图。图6所示的通信设备600包括处理器610,处理器610可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图6所示,通信设备600还可以包括存储器620。其中,处理器610可以从存储器620中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器620可以是独立于处理器610的一个单独的器件,也可以集成在处理器610中。
可选地,如图6所示,通信设备600还可以包括收发器630,处理器610可以控制该收发器630与其他设备进行通信,具体地,可以向其他设备发送信息或数据,或接收其他设备发送的信息或数据。
其中,收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线,天线的数量可以为一个或多个。
可选地,该通信设备600具体可为本申请实施例的网络设备,并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该通信设备600具体可为本申请实施例的移动终端/终端设备,并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
图7是本申请实施例的芯片的示意性结构图。图7所示的芯片700包括处理器710,处理器710可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图7所示,芯片700还可以包括存储器720。其中,处理器710可以从存储器720中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器720可以是独立于处理器710的一个单独的器件,也可以集成在处理器710中。
可选地,该芯片700还可以包括输入接口730。其中,处理器710可以控制该输入接口730与其他设备或芯片进行通信,具体地,可以获取其他设备或芯片发送的信息或数据。
可选地,该芯片700还可以包括输出接口740。其中,处理器710可以控制该输出接口740与其他设备或芯片进行通信,具体地,可以向其他设备或芯片输出信息或数据。
可选地,该芯片可应用于本申请实施例中的网络设备,并且该芯片可以实现本申请实施例的各个 方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该芯片可应用于本申请实施例中的移动终端/终端设备,并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
应理解,本申请实施例的处理器可能是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor,DSP)、专用集成电路(Application Specific Integrated Circuit,ASIC)、现成可编程门阵列(Field Programmable Gate Array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。
可以理解,本申请实施例中的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(Static RAM,SRAM)、动态随机存取存储器(Dynamic RAM,DRAM)、同步动态随机存取存储器(Synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)。应注意,本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解,上述存储器为示例性但不是限制性说明,例如,本申请实施例中的存储器还可以是静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synch link DRAM,SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)等等。也就是说,本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质,用于存储计算机程序。
可选的,该计算机可读存储介质可应用于本申请实施例中的网络设备,并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备,并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
本申请实施例还提供了一种计算机程序产品,包括计算机程序指令。
可选的,该计算机程序产品可应用于本申请实施例中的网络设备,并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机程序产品可应用于本申请实施例中的移动终端/终端设备,并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的,该计算机程序可应用于本申请实施例中的网络设备,当该计算机程序在计算机上运行时,使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机程序可应用于本申请实施例中的移动终端/终端设备,当该计算机程序在计算机上运行时,使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤, 能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,)ROM、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应所述以权利要求的保护范围为准。
Claims (41)
- 一种无线通信的方法,其特征在于,包括:终端设备接收网络设备对第一自动请求重传HARQ进程的重传调度;所述终端设备根据第一信息,对去优先数据进行处理,其中,所述去优先数据对应所述第一HARQ进程,所述第一信息包括以下中的至少一项:在接收到所述重传调度之前所述去优先数据是否被组包;以及在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程。
- 根据权利要求1所述的方法,其特征在于,所述终端设备根据第一信息,对去优先数据进行处理,包括:若在接收到所述重传调度之前所述去优先数据未组包,将所述去优先数据进行组包;触发使用所述第一HARQ进程新传所述去优先数据。
- 根据权利要求1所述的方法,其特征在于,所述终端设备根据第一信息,对去优先数据进行处理,包括:若在接收到所述重传调度之前所述去优先数据已组包,根据在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程,触发使用所述第一HARQ进程新传还是重传所述去优先数据。
- 根据权利要求3所述的方法,其特征在于,所述根据在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程,触发使用所述第一HARQ进程新传还是重传所述去优先数据,包括:若在接收到所述重传调度之前所述去优先数据未递交至所述第一HARQ进程,触发使用所述第一HARQ进程新传所述去优先数据。
- 根据权利要求3所述的方法,其特征在于,所述根据在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程,触发使用所述第一HARQ进程新传还是重传所述去优先数据,包括:若在接收到所述重传调度之前所述去优先数据已递交至所述第一HARQ进程,触发使用所述第一HARQ进程重传所述去优先数据。
- 根据权利要求2或4所述的方法,其特征在于,所述触发使用所述第一HARQ进程新传所述去优先数据,包括以下中的至少一项:获取组包的所述去优先数据;将组包的所述去优先数据,所述重传调度的上行授权,所述上行授权的HARQ信息中的至少一项递交至所述第一HARQ进程;指示所述第一HARQ进程对组包的所述去优先数据进行新传。
- 根据权利要求5所述的方法,其特征在于,所述触发使用所述第一HARQ进程重传所述去优先数据,包括:将所述重传调度的上行授权和/或所述上行授权的HARQ信息递交至所述第一HARQ进程;指示所述第一HARQ进程对组包的所述去优先数据进行重传。
- 根据权利要求1至7中任一项所述的方法,其特征在于,所述方法还包括:若所述第一HARQ进程为配置授权资源对应的HARQ进程,在开始传输所述去优先数据时,开启或重启所述第一HARQ进程的配置授权定时器。
- 根据权利要求8所述的方法,其特征在于,所述方法还包括:若所述重传调度是配置调度无线网络临时标识CS-RNTI加扰的物理下行控制信道PDCCH调度的,确定所述第一HARQ进程为配置授权资源对应的HARQ进程;或若所述重传调度为小区C-RNTI加扰的PDCCH调度的,且所述第一HARQ进程为对应配置授权资源的HARQ进程,确定所述第一HARQ进程为配置授权资源对应的HARQ进程。
- 根据权利要求1至9中任一项所述的方法,其特征在于,在所述终端设备接收网络设备对第一自动请求重传HARQ进程的重传调度之前,所述方法还包括:所述终端设备根据第二信息,确定是否对所述去优先数据进行组包,其中,所述第二信息包括以下中的至少一项:所述去优先数据对应的优先数据是否被组包,所述优先数据是否被发送给物理层,所述优先数据是否被传输,以及,所述去优先数据的优先级和所述去优先数据的第一授权资源的优先级,其中,所述第一授权资源在所述终端设备接收到所述重传调度之前可用于传输所述去优先数据。
- 根据权利要求10所述的方法,其特征在于,所述终端设备根据第二信息,确定是否对所述去优先数据进行组包,包括:所述终端设备在满足以下条件中的至少一个时,不对所述去优先数据进行组包:在第一时间之前所述优先数据已组包完成,并且所述去优先数据的优先级低于所述优先数据的优先级;在第一时间之前所述优先数据已组包完成,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第一时间之前所述优先数据已发送至物理层,并且所述去优先数据的优先级低于所述优先数据的优先级;在第一时间之前所述优先数据已发送至物理层,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第一时间之前所述优先数据已发送,并且所述去优先数据的优先级低于所述优先数据的优先级;在第一时间之前所述优先数据已发送,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第一时间之前调度请求SR已发送至物理层,并且所述去优先数据的优先级低于所述SR的优先级;在第一时间之前SR已发送至物理层,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级;在第一时间之前SR已发送,并且所述去优先数据的优先级低于所述SR的优先级;以及,在第一时间之前SR已发送,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级,其中,所述第一时间之前为以下中的一种:所述终端设备接收所述网络设备配置的所述第一授权资源的时间之前;所述第一授权资源的起始时域位置之前;在所述第一授权资源上有待传输数据之前。
- 根据权利要求1至11中任一项所述的方法,其特征在于,所述方法还包括:在不组包所述去优先数据的情况下,所述终端设备不将所述去优先数据和/或用于传输所述去优先数据的第一授权资源递交至所述第一授权资源对应的HARQ进程;和/或在不组包所述去优先数据的情况下,所述终端设备的MAC层不指示物理层使用所述第一授权资源传输所述去优先数据;其中,所述第一授权资源在所述终端设备接收到所述重传调度之前可用于传输所述去优先数据。
- 根据权利要求10所述的方法,其特征在于,所述终端设备根据第二信息,确定是否对所述去优先数据进行组包处理,包括:所述终端设备在满足以下条件中的至少一个时,对所述去优先数据进行组包处理:在第二时间之前所述优先数据已组包完成,并且所述去优先数据的优先级低于所述优先数据的优先级;在第二时间之前所述优先数据已组包完成,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第二时间之前所述优先数据已发送至物理层,并且所述去优先数据的优先级低于所述优先数据的优先级;在第二时间之前所述优先数据已发送至物理层,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第二时间之前所述优先数据已发送,并且所述去优先数据的优先级低于所述优先数据的优先级;在第二时间之前所述优先数据已发送,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第二时间之前调度请求SR已发送至物理层,并且所述去优先数据的优先级低于所述SR的优先级;在第二时间之前SR已发送至物理层,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级;在第二时间之前SR已发送,并且所述去优先数据的优先级低于所述SR的优先级;以及,在第二时间之前SR已发送,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级;其中,所述第二时间为以下中的一种:所述终端设备接收所述网络设备配置的所述第一授权资源的时间之前;所述第一授权资源的起始时域位置之前;在所述第一授权资源上有待传输数据之前。
- 根据权利要求1至10中任一项或13所述的方法,其特征在于,所述方法还包括:在组包所述去优先数据的情况下,所述终端设备不将所述去优先数据和/或用于传输所述去优先数据的第一授权资源递交至所述第一授权资源对应的HARQ进程;和/或在组包所述去优先数据的情况下,所述终端设备的MAC层不指示物理层使用所述第一授权资源传输所述去优先数据;其中,所述第一授权资源为在所述终端设备接收到所述重传调度之前可用于传输所述去优先数据的授权资源。
- 根据权利要求1至14中任一项所述的方法,其特征在于,所述终端设备接收网络设备对第一自动请求重传HARQ进程的重传调度,包括:所述终端设备接收通过CS-RNTI加扰的PDCCH调度的上行授权,且所述PDCCH中的新数据指示NDI为1,其中,所述上行授权对应的HARQ进程为所述第一HARQ进程。
- 根据权利要求1至14中任一项所述的方法,其特征在于,所述终端设备接收网络设备对第一自动请求重传HARQ进程的重传调度,包括:所述终端设备接收通过C-RNTI加扰PDCCH调度的上行授权,其中,所述上行授权对应的HARQ进程为所述第一HARQ进程。
- 根据权利要求1至16中任一项所述的方法,其特征在于,所述方法还包括:所述终端设备根据以下中的至少一项,确定所述去优先数据是否被组包:所述第一HARQ进程的缓存是否为空;所述第一HARQ进程的缓存是否保存所述去优先数据;以及,在接收到所述重传调度之前,所述去优先数据对应的授权资源是否被使用。
- 根据权利要求17所述的方法,其特征在于,所述终端设备根据以下中的至少一项,确定所述去优先数据是否被组包,包括:若所述第一HARQ进程中的缓存为空,确定所述去优先数据未组包;或若所述第一HARQ进程的缓存未保存所述去优先数据,确定所述去优先数据未组包;或若在接收到所述重传调度之前,所述去优先数据对应的授权资源未被使用,确定所述去优先数据未组包;或若所述第一HARQ进程中的缓存不为空,确定所述去优先数据已组包;或若所述第一HARQ进程的缓存保存有所述去优先数据,确定所述去优先数据已组包;或若在接收到所述重传调度之前,所述去优先数据对应的授权资源被使用,确定所述去优先数据已组包。
- 一种无线通信的设备,其特征在于,包括:通信模块,用于接收网络设备对第一自动请求重传HARQ进程的重传调度;处理模块,用于根据第一信息,对去优先数据进行处理,其中,所述去优先数据对应所述第一HARQ进程,所述第一信息包括以下中的至少一项:在接收到所述重传调度之前所述去优先数据是否被组包;以及在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程。
- 根据权利要求19所述的设备,其特征在于,所述处理模块具体用于:若在接收到所述重传调度之前所述去优先数据未组包,将所述去优先数据进行组包;触发使用所述第一HARQ进程新传所述去优先数据。
- 根据权利要求19所述的设备,其特征在于,所述处理模块具体用于:若在接收到所述重传调度之前所述去优先数据已组包,根据在接收到所述重传调度之前所述去优先数据是否递交至所述第一HARQ进程,触发使用所述第一HARQ进程新传还是重传所述去优先数据。
- 根据权利要求21所述的设备,其特征在于,所述处理模块具体用于:若在接收到所述重传调度之前所述去优先数据未递交至所述第一HARQ进程,触发使用所述第一HARQ进程新传所述去优先数据。
- 根据权利要求21所述的设备,其特征在于,所述处理模块具体用于:若在接收到所述重传调度之前所述去优先数据已递交至所述第一HARQ进程,触发使用所述第 一HARQ进程重传所述去优先数据。
- 根据权利要求20或22所述的设备,其特征在于,所述处理模块具体用于执行以下中的至少一项:获取组包的所述去优先数据;将组包的所述去优先数据,所述重传调度的上行授权,所述上行授权的HARQ信息中的至少一项递交至所述第一HARQ进程;指示所述第一HARQ进程对组包的所述去优先数据进行新传。
- 根据权利要求23所述的设备,其特征在于,所述处理模块具体用于执行以下中的至少一项:将所述重传调度的上行授权和/或所述上行授权的HARQ信息递交至所述第一HARQ进程;指示所述第一HARQ进程对组包的所述去优先数据进行重传。
- 根据权利要求19至25中任一项所述的设备,其特征在于,所述处理模块还用于:若所述第一HARQ进程为配置授权资源对应的HARQ进程,在开始传输所述去优先数据时,开启或重启所述第一HARQ进程的配置授权定时器。
- 根据权利要求26所述的设备,其特征在于,所述处理模块还用于:若所述重传调度是配置调度无线网络临时标识CS-RNTI加扰的物理下行控制信道PDCCH调度的,确定所述第一HARQ进程为配置授权资源对应的HARQ进程;或若所述重传调度为小区C-RNTI加扰的PDCCH调度的,且所述第一HARQ进程为对应配置授权资源的HARQ进程,确定所述第一HARQ进程为配置授权资源对应的HARQ进程。
- 根据权利要求19至27中任一项所述的设备,其特征在于,在所述通信模块接收网络设备对第一自动请求重传HARQ进程的重传调度之前,所述处理模块还用于:根据第二信息,确定是否对所述去优先数据进行组包,其中,所述第二信息包括以下中的至少一项:所述去优先数据对应的优先数据是否被组包,所述优先数据是否被发送给物理层,所述优先数据是否被传输,以及,所述去优先数据的优先级和所述去优先数据的第一授权资源的优先级,其中,所述第一授权资源在所述设备接收到所述重传调度之前可用于传输所述去优先数据。
- 根据权利要求28所述的设备,其特征在于,所述处理模块具体用于:在满足以下条件中的至少一个时,不对所述去优先数据进行组包:在第一时间之前所述优先数据已组包完成,并且所述去优先数据的优先级低于所述优先数据的优先级;在第一时间之前所述优先数据已组包完成,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第一时间之前所述优先数据已发送至物理层,并且所述去优先数据的优先级低于所述优先数据的优先级;在第一时间之前所述优先数据已发送至物理层,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第一时间之前所述优先数据已发送,并且所述去优先数据的优先级低于所述优先数据的优先级;在第一时间之前所述优先数据已发送,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第一时间之前调度请求SR已发送至物理层,并且所述去优先数据的优先级低于所述SR的优先级;在第一时间之前SR已发送至物理层,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级;在第一时间之前SR已发送,并且所述去优先数据的优先级低于所述SR的优先级;以及,在第一时间之前SR已发送,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级其中,所述第一时间之前为以下中的一种:所述设备接收所述网络设备配置的所述第一授权资源的时间之前;所述第一授权资源的起始时域位置之前;在所述第一授权资源上有待传输数据之前。
- 根据权利要求19至29中任一项所述的设备,其特征在于,所述处理模块具体用于:在不组包所述去优先数据的情况下,不将所述去优先数据和/或用于传输所述去优先数据的第一授权资源递交至所述第一授权资源对应的HARQ进程;和/或在不组包所述去优先数据的情况下,在MAC层不指示物理层使用所述第一授权资源传输所述去优先数据;其中,所述第一授权资源在所述设备接收到所述重传调度之前可用于传输所述去优先数据。
- 根据权利要求28所述的设备,其特征在于,所述处理模块具体用于:在满足以下条件中的至少一个时,对所述去优先数据进行组包处理:在第二时间之前所述优先数据已组包完成,并且所述去优先数据的优先级低于所述优先数据的优先级;在第二时间之前所述优先数据已组包完成,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第二时间之前所述优先数据已发送至物理层,并且所述去优先数据的优先级低于所述优先数据的优先级;在第二时间之前所述优先数据已发送至物理层,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第二时间之前所述优先数据已发送,并且所述去优先数据的优先级低于所述优先数据的优先级;在第二时间之前所述优先数据已发送,并且所述第一授权资源的优先级低于所述优先数据对应的授权资源的优先级;在第二时间之前调度请求SR已发送至物理层,并且所述去优先数据的优先级低于所述SR的优先级;在第二时间之前SR已发送至物理层,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级;在第二时间之前SR已发送,并且所述去优先数据的优先级低于所述SR的优先级;以及,在第二时间之前SR已发送,并且所述第一授权资源的优先级低于所述SR对应的授权资源的优先级;其中,所述第二时间为以下中的一种:所述设备接收所述网络设备配置的所述第一授权资源的时间之前;所述第一授权资源的起始时域位置之前;在所述第一授权资源上有待传输数据之前。
- 根据权利要求19至28中任一项或31所述的设备,其特征在于,所述处理模块还用于:在组包所述去优先数据的情况下,不将所述去优先数据和/或用于传输所述去优先数据的第一授权资源递交至所述第一授权资源对应的HARQ进程;和/或在组包所述去优先数据的情况下,在MAC层不指示物理层使用所述第一授权资源传输所述去优先数据;其中,所述第一授权资源在所述设备接收到所述重传调度之前可用于传输所述去优先数据。
- 根据权利要求19至32中任一项所述的设备,其特征在于,所述通信模块具体用于:接收通过CS-RNTI加扰的PDCCH调度的上行授权,且所述PDCCH中的新数据指示NDI为1,其中,所述上行授权对应的HARQ进程为所述第一HARQ进程。
- 根据权利要求19至32中任一项所述的设备,其特征在于,所述通信模块具体用于:接收通过C-RNTI加扰PDCCH调度的上行授权,其中,所述上行授权对应的HARQ进程为所述第一HARQ进程。
- 根据权利要求19至34中任一项所述的设备,其特征在于,所述处理模块还用于:根据以下中的至少一项,确定所述去优先数据是否被组包:所述第一HARQ进程的缓存是否为空;所述第一HARQ进程的缓存是否保存所述去优先数据;以及,在接收到所述重传调度之前,所述去优先数据对应的授权资源是否被使用。
- 根据权利要求35所述的设备,其特征在于,所述处理模块还用于:若所述第一HARQ进程中的缓存为空,确定所述去优先数据未组包;或若所述第一HARQ进程的缓存未保存所述去优先数据,确定所述去优先数据未组包;或若在接收到所述重传调度之前,所述去优先数据对应的授权资源未被使用,确定所述去优先数据未组包;或若所述第一HARQ进程中的缓存不为空,确定所述去优先数据已组包;或若所述第一HARQ进程的缓存保存有所述去优先数据,确定所述去优先数据已组包;或若在接收到所述重传调度之前,所述去优先数据对应的授权资源被使用,确定所述去优先数据已组包。
- 一种终端设备,其特征在于,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求1至18中任一项所述的方法。
- 一种芯片,其特征在于,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至18中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求1至18中任一项所述的方法。
- 一种计算机程序产品,其特征在于,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至18中任一项所述的方法。
- 一种计算机程序,其特征在于,所述计算机程序使得计算机执行如权利要求1至18中任一项所述的方法。
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP19941018.4A EP3986067A4 (en) | 2019-08-14 | 2019-08-14 | Wireless communication method and device |
| CN201980092607.8A CN113455079B (zh) | 2019-08-14 | 2019-08-14 | 无线通信的方法和设备 |
| PCT/CN2019/100671 WO2021026847A1 (zh) | 2019-08-14 | 2019-08-14 | 无线通信的方法和设备 |
| US17/565,704 US12199772B2 (en) | 2019-08-14 | 2021-12-30 | Method for wireless communication, terminal device, and non-transitory computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2019/100671 WO2021026847A1 (zh) | 2019-08-14 | 2019-08-14 | 无线通信的方法和设备 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US17/565,704 Continuation US12199772B2 (en) | 2019-08-14 | 2021-12-30 | Method for wireless communication, terminal device, and non-transitory computer-readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2021026847A1 true WO2021026847A1 (zh) | 2021-02-18 |
Family
ID=74570343
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2019/100671 Ceased WO2021026847A1 (zh) | 2019-08-14 | 2019-08-14 | 无线通信的方法和设备 |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US12199772B2 (zh) |
| EP (1) | EP3986067A4 (zh) |
| CN (1) | CN113455079B (zh) |
| WO (1) | WO2021026847A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US12199772B2 (en) | 2019-08-14 | 2025-01-14 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method for wireless communication, terminal device, and non-transitory computer-readable storage medium |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021091311A1 (ko) * | 2019-11-06 | 2021-05-14 | 삼성전자 주식회사 | 무선통신시스템에서 논리 채널 제한을 적용하는 방법 및 장치 |
| US20240195535A1 (en) * | 2021-03-30 | 2024-06-13 | Nokia Techonologies Oy | Harq process selection |
| WO2023003206A1 (en) * | 2021-07-22 | 2023-01-26 | Lg Electronics Inc. | Method and apparatus for transmitting uplink control information multiplexed data by ue in wireless communication system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108811175A (zh) * | 2017-05-05 | 2018-11-13 | 华硕电脑股份有限公司 | 无线通信系统中传送数据复制的方法和设备 |
| WO2018231978A1 (en) * | 2017-06-15 | 2018-12-20 | Sharp Laboratories Of America, Inc. | Procedure, base station and user equipment for uplink transmission without grant |
| CN109729596A (zh) * | 2017-10-27 | 2019-05-07 | 华为技术有限公司 | 一种数据发送、接收方法及设备 |
| WO2019098663A1 (en) * | 2017-11-14 | 2019-05-23 | Lg Electronics Inc. | Method and apparatus for deprioritizing duplicated packet transmission in wireless communication system |
| WO2019139361A1 (en) * | 2018-01-11 | 2019-07-18 | Lg Electronics Inc. | Method and apparatus for transmitting signals based on configured grant in wireless communication system |
| US20190245657A1 (en) * | 2016-07-12 | 2019-08-08 | Lg Electronics Inc. | Uplink signal transmission method and user equipment |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102171962B (zh) * | 2011-04-13 | 2013-04-24 | 华为技术有限公司 | 高速上行分组接入的数据流传输方法及终端设备 |
| WO2014160722A1 (en) * | 2013-03-25 | 2014-10-02 | Altiostar Networks, Inc. | Transmission control protocol in long term evolution radio access network |
| WO2017196400A1 (en) * | 2016-05-12 | 2017-11-16 | Intel IP Corporation | Systems, methods and devices for non-adaptive retransmission using semi-persistent scheduling resources |
| JP7582951B2 (ja) * | 2019-01-09 | 2024-11-13 | インターデイジタル パテント ホールディングス インコーポレイテッド | 超高信頼送信の拡張制御シグナリングのための方法、装置およびシステム |
| EP3986067A4 (en) | 2019-08-14 | 2022-06-29 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Wireless communication method and device |
-
2019
- 2019-08-14 EP EP19941018.4A patent/EP3986067A4/en not_active Withdrawn
- 2019-08-14 WO PCT/CN2019/100671 patent/WO2021026847A1/zh not_active Ceased
- 2019-08-14 CN CN201980092607.8A patent/CN113455079B/zh active Active
-
2021
- 2021-12-30 US US17/565,704 patent/US12199772B2/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190245657A1 (en) * | 2016-07-12 | 2019-08-08 | Lg Electronics Inc. | Uplink signal transmission method and user equipment |
| CN108811175A (zh) * | 2017-05-05 | 2018-11-13 | 华硕电脑股份有限公司 | 无线通信系统中传送数据复制的方法和设备 |
| WO2018231978A1 (en) * | 2017-06-15 | 2018-12-20 | Sharp Laboratories Of America, Inc. | Procedure, base station and user equipment for uplink transmission without grant |
| CN109729596A (zh) * | 2017-10-27 | 2019-05-07 | 华为技术有限公司 | 一种数据发送、接收方法及设备 |
| WO2019098663A1 (en) * | 2017-11-14 | 2019-05-23 | Lg Electronics Inc. | Method and apparatus for deprioritizing duplicated packet transmission in wireless communication system |
| WO2019139361A1 (en) * | 2018-01-11 | 2019-07-18 | Lg Electronics Inc. | Method and apparatus for transmitting signals based on configured grant in wireless communication system |
Non-Patent Citations (4)
| Title |
|---|
| HUAWEI, HISILICON: "Further discussion on transmission of de-prioritized data due to intra-UE prioritization", 3GPP DRAFT; R2-1906507 FURTHER DISCUSSION ON DEPRIORITIZED DATA TRANSMISSION DUE TO INTRA-UE PRIORITIZATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, United States; 20190513 - 20190517, 3 May 2019 (2019-05-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051710821 * |
| HUAWEI, HISILICON: "Prioritization between configured and dynamic grants", 3GPP DRAFT; R2-1906505 PRIORITIZATION BETWEEN CONFIGURED AND DYNAMIC GRANTS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, United States; 20190513 - 20190517, 3 May 2019 (2019-05-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051710819 * |
| INTERDIGITAL: "Resource Conflicts for Data-only Intra-UE Prioritization", 3GPP DRAFT; R2-1906407 (R16 NR_IIOT SI AI1173 IMPACT OF UL PRIO), 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 3 May 2019 (2019-05-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 4, XP051710722 * |
| See also references of EP3986067A4 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US12199772B2 (en) | 2019-08-14 | 2025-01-14 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method for wireless communication, terminal device, and non-transitory computer-readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113455079A (zh) | 2021-09-28 |
| EP3986067A4 (en) | 2022-06-29 |
| EP3986067A1 (en) | 2022-04-20 |
| CN113455079B (zh) | 2023-05-26 |
| US12199772B2 (en) | 2025-01-14 |
| US20220123873A1 (en) | 2022-04-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112655262B (zh) | 资源分配的方法、终端设备和网络设备 | |
| US12022478B2 (en) | Wireless communication method and communication device | |
| CN112740587B (zh) | 无线通信方法、终端设备和网络设备 | |
| WO2020107479A1 (zh) | 一种传输数据的方法、终端设备和网络设备 | |
| US12082211B2 (en) | Wireless communication method, terminal device and network device | |
| US12199772B2 (en) | Method for wireless communication, terminal device, and non-transitory computer-readable storage medium | |
| WO2020191778A1 (zh) | 重传资源配置方法、设备、芯片及计算机程序 | |
| CN113133054B (zh) | 传输数据的方法和终端设备 | |
| WO2020191636A1 (zh) | 通信方法、终端设备和网络设备 | |
| WO2020087289A1 (zh) | 一种资源配置方法、网络设备及终端设备 | |
| WO2020227868A1 (zh) | 传输数据的方法、终端设备和网络设备 | |
| WO2020107489A1 (zh) | 一种无线通信方法和通信设备 | |
| WO2020051919A1 (zh) | 一种资源确定及配置方法、装置、终端、网络设备 | |
| WO2020037655A1 (zh) | 一种反馈信息长度的确定方法及装置、通信设备 | |
| WO2021026841A1 (zh) | 调度请求传输的方法和设备 | |
| TW202037126A (zh) | 確定上行控制訊息傳輸資源個數的方法、裝置及程式 | |
| TW202019221A (zh) | 一種回饋資源配置方法、終端設備及網路設備 | |
| WO2021031128A1 (zh) | 传输数据的方法、终端设备和网络设备 | |
| WO2021068224A1 (zh) | 无线通信方法、终端设备和网络设备 | |
| WO2020056719A9 (zh) | 一种信息传输时间的确定方法、终端设备及网络设备 | |
| CN113328838B (zh) | 一种资源确定方法、设备及存储介质 | |
| WO2021088004A1 (zh) | 一种信道处理方法及装置、终端设备 | |
| WO2021146950A1 (zh) | 一种确定重传资源的方法及装置、终端设备 | |
| WO2021073021A1 (zh) | 传输数据的方法、终端设备和网络设备 | |
| WO2021203230A1 (zh) | 上行控制信息传输方法及装置、终端设备 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19941018 Country of ref document: EP Kind code of ref document: A1 |
|
| ENP | Entry into the national phase |
Ref document number: 2019941018 Country of ref document: EP Effective date: 20220113 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| WWW | Wipo information: withdrawn in national office |
Ref document number: 2019941018 Country of ref document: EP |