[go: up one dir, main page]

WO2021056209A1 - 无线通信的方法和设备 - Google Patents

无线通信的方法和设备 Download PDF

Info

Publication number
WO2021056209A1
WO2021056209A1 PCT/CN2019/107595 CN2019107595W WO2021056209A1 WO 2021056209 A1 WO2021056209 A1 WO 2021056209A1 CN 2019107595 W CN2019107595 W CN 2019107595W WO 2021056209 A1 WO2021056209 A1 WO 2021056209A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
harq process
terminal device
time
pusch
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
Application number
PCT/CN2019/107595
Other languages
English (en)
French (fr)
Inventor
付喆
林亚男
石聪
吴作敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2019/107595 priority Critical patent/WO2021056209A1/zh
Priority to CN201980095275.9A priority patent/CN113647182B/zh
Publication of WO2021056209A1 publication Critical patent/WO2021056209A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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

Definitions

  • the embodiments of the present application relate to the field of communication, and more specifically, to methods and devices for wireless communication.
  • IIoT Industrial Interest of Things
  • NR-U New Radio Unlicensed
  • PDU Media Access Control Protocol Data Unit
  • the network device may select the HARQ process id selected by the terminal device for the CG resource for dynamic scheduling, which will cause CG MAC PDU transmission problems, such as being flushed, resulting in QoS Problems that cannot be guaranteed.
  • a method and device for wireless communication are provided.
  • the HARQ process corresponding to the CG resource conflicts with the HARQ process corresponding to the DG resource, the service QoS requirement can be guaranteed.
  • a wireless communication method including:
  • the HARQ process used by the CG resource is switched from the first HARQ process to the second HARQ process.
  • a terminal device which is used to execute the method in the above-mentioned first aspect or its implementation manners.
  • the terminal device includes a functional module for executing the method in the foregoing first aspect or each of its implementation manners.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the foregoing first aspect or each of its implementation manners.
  • a chip which is used to implement the method in the above-mentioned first aspect or each of its implementation manners.
  • the chip includes: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method in the above-mentioned first aspect or each of its implementation manners.
  • a computer-readable storage medium for storing a computer program that enables a computer to execute the method in the above-mentioned first aspect or each of its implementation manners.
  • a computer program product including computer program instructions that cause a computer to execute the method in the first aspect or its implementation manners.
  • a computer program which when run on a computer, causes the computer to execute the method in the first aspect or its implementation manners.
  • the The second HARQ process normally sends the data carried on the CG resource, thereby ensuring service QoS requirements.
  • Figure 1 is an example of the application scenario of this application.
  • FIG. 2 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.
  • Fig. 3 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • Fig. 4 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • Fig. 5 is a schematic block diagram of a chip of an embodiment of the present application.
  • Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • the communication system 100 may include a terminal device 110 and a network device 120.
  • the network device 120 may communicate with the terminal device 110 through an air interface.
  • the terminal device 110 and the network device 120 support multi-service transmission.
  • LTE Long Term Evolution
  • TDD Time Division Duplex
  • Universal Mobile Communication System Universal Mobile Telecommunication System
  • UMTS Universal Mobile Telecommunication System
  • 5G communication system also known as New Radio (NR) communication system
  • future communication system etc.
  • the network device 120 may be an access network device that communicates with the terminal device 110.
  • the access network device can provide communication coverage for a specific geographic area, and can communicate with the terminal device 110 (for example, UE) located in the coverage area.
  • the network equipment 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) equipment, Either the base station (gNB) in the NR system, or the wireless controller in the Cloud Radio Access Network (CRAN), or the network device 120 can be a relay station, an access point, a vehicle-mounted device, or a wearable Equipment, hubs, switches, bridges, routers, or network equipment in the future evolution of the Public Land Mobile Network (PLMN).
  • Evolutional Node B, eNB or eNodeB in a Long Term Evolution (LTE) system
  • NG RAN Next Generation Radio Access Network
  • gNB base station
  • CRAN Cloud Radio Access Network
  • PLMN Public Land Mobile Network
  • the terminal device 110 may be any terminal device, which includes, but is not limited to, a terminal device connected to the network device 120 or other terminal devices in a wired or wireless connection.
  • the terminal device 110 may refer to an access terminal, user equipment (User Equipment, UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication Equipment, user agent, 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 future evolution networks, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device 110 may be used for device-to-device (D2D) communication.
  • D2D device-to-device
  • the wireless communication system 100 may also include a core network device 130 that communicates with a base station.
  • the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, an Access and Mobility Management Function (Access and Mobility Management Function). , AMF), for example, authentication server function (Authentication Server Function, AUSF), for example, user plane function (User Plane Function, UPF), for example, session management function (Session Management Function, SMF).
  • the core network device 130 may also be an Evolved Packet Core (EPC) device of the LTE network, for example, a session management function + a data gateway (Session Management Function+Core Packet Gateway, SMF+PGW-) of the LTE network.
  • EPC Evolved Packet Core
  • SMF+PGW-C can simultaneously realize the functions that SMF and PGW-C can realize.
  • the aforementioned core network equipment may also be called by other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited in the embodiment of the present application.
  • Each functional unit in the communication system 100 may also establish a connection through a next generation network (NG) interface to achieve communication.
  • NG next generation network
  • the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (abbreviated as N1); access Network equipment, such as the next generation wireless access base station (gNB), can establish a user plane data connection with UPF through NG interface 3 (abbreviated as N3); access network equipment can establish control plane signaling with AMF through NG interface 2 (abbreviated as N2) Connection; UPF can establish control plane signaling connection with SMF through NG interface 4 (abbreviated as N4); UPF can exchange user plane data with the data network via NG interface 6 (abbreviated as N6); AMF can communicate with SMF via NG interface 11 (abbreviated as N11) SMF establishes control plane signaling connection; SMF can establish control plane signaling connection with PCF through NG interface 7 (abbreviated as N7).
  • N1 next generation wireless access base station
  • Figure 1 exemplarily shows a base station, a core network device and two terminal devices.
  • the wireless communication system 100 may include multiple base station devices and the coverage of each base station may include other numbers of terminals.
  • Equipment this embodiment of the application does not limit this.
  • the communication device may include a network device 120 and a terminal device 110 having communication functions, and the network device 120 and the terminal device 110 may be the above-mentioned devices, 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 the embodiment of the present application.
  • the following exemplarily describes a network to which the communication system 100 used in the embodiment of the present application is applicable.
  • the communication system 100 may be applicable to the fifth-generation mobile communication technology (5-Generation, 5G) Industrial Internet (IIoT).
  • 5G fifth-generation mobile communication technology
  • IIoT Industrial Internet
  • 5G IIoT can support the transmission of services such as Industrial Automation (Factory Automation), Transport Industry (Transport Industry), and Intelligent Power (Electrical Power Distribution) in 5G systems.
  • Industrial Automation Fluctory Automation
  • Transport Industry Transport Industry
  • Intelligent Power Electronic Power Distribution
  • 5G IIoT may have resource conflicts.
  • the resource conflict includes a conflict between a data channel and a data channel, which may include a conflict between a DG resource and a DG resource, a conflict between a DG resource and a CG resource, and a conflict between a CG resource and a CG resource.
  • MAC Media Access Control
  • PDU Protocol Data Unit
  • the communication system 100 may be applicable to an NR-U network.
  • the terminal device 110 or the network device 120 may be applicable to the NR-U network.
  • NR works in an unlicensed frequency band.
  • the NR-U network includes but is not limited to the following working scenarios:
  • Scenario A Carrier aggregation scenario. That is, the primary cell (PCell) works on the licensed spectrum, and the secondary cell (SCell) aggregates and works on the unlicensed spectrum by means of carrier aggregation.
  • PCell primary cell
  • SCell secondary cell
  • Scenario B Dual connection working scenario. That is, the PCell works on the licensed spectrum, and the primary and secondary cell (Primary Secondary Cell, PSCell) works on the NR unlicensed spectrum.
  • the PCell works on the licensed spectrum
  • the primary and secondary cell Primary Secondary Cell, PSCell
  • Scene C Independent work scene. That is, NR works as an independent cell in the unlicensed spectrum.
  • Scenario D NR single cell scenario. That is, the uplink (UL) works in the licensed spectrum, and the downlink (DL) works in the unlicensed spectrum.
  • Scenario E Dual-connection working scenario, PCell works in NR licensed spectrum, PSCell works in NR unlicensed spectrum.
  • the working frequency band (Band) of NR-U can be 5GHz unlicensed spectrum and 6GHz unlicensed spectrum.
  • the design of NR-U needs to ensure fairness with other systems that are already working on these unlicensed spectrums, such as WiFi.
  • the impact on systems that have been deployed on unlicensed spectrum cannot exceed the impact between these systems.
  • the energy detection mechanism can be used to ensure the fair coexistence between systems on the unlicensed spectrum, such as the LBT mechanism.
  • the network device or terminal device needs to listen for a period of time according to regulations before transmitting data on the unlicensed spectrum. If the listening result indicates that the channel is idle, the transmitting end can transmit data to the receiving end. If the listening result indicates that the channel is in an occupied state, the transmitting end needs to back off for a period of time according to regulations before continuing to listen to the channel until the channel listening result is idle before transmitting data to the receiving end.
  • Channel access can be performed through the following four channel access mechanisms (category):
  • the transmitting end (TX) can quickly transmit after the switching time (switching gap) within the channel occupation time (Channel Occupancy Time, COT).
  • Switching gap may refer to the conversion time when the transmission data is received. For example, the switching gap may not exceed 16 us.
  • the time for the terminal device to listen to the channel is determined, such as 25us.
  • the transmission side randomly selects a random value in the contention window to determine the time to listen to the channel.
  • the transmission side randomly selects a random value in the contention window to determine the time to listen to the channel, and the contention window is variable.
  • the network device when the network device transmits data to the terminal device, it needs to be within the Maximum Channel Occupancy Time (MCOT) if the network device does not preempt the channel. In other words, if it is outside the MCOT time, the terminal device will not receive the scheduling data from the network device to the terminal device.
  • MCOT Maximum Channel Occupancy Time
  • the terminal device For the uplink transmission initiated by the terminal device, it includes but not limited to the following categories:
  • Scheduling Request (SR) is used to request uplink resources.
  • Physical Random Access Channel Physical Random Access Channel
  • RACH Random Access Channel
  • Physical Uplink Shared Channel includes uplink data transmission based on CG resources and uplink data transmission based on DG resources.
  • the physical layer signaling includes acknowledgement/non-acknowledgement (ACK/NACK) and channel state information (CSI).
  • ACK/NACK acknowledgement/non-acknowledgement
  • CSI channel state information
  • the terminal device On the unlicensed frequency band, the terminal device needs to use LBT to monitor whether the channel is available before transmitting SR, PRACH or PUSCH. If it is not available, that is, LBT fails, the terminal device needs to wait until the next transmission opportunity to perform LBT again. If LBT failure is detected, it needs to notify the MAC layer of LBT failure information.
  • terminal equipment can use automatic uplink transmission (AUL) to transmit data carried on CG resources.
  • AUL automatic uplink transmission
  • the network device may configure multiple HARQ processes available for CG resources for the terminal device, for example, identification (ID) of multiple HARQ processes.
  • ID identification
  • the identification of the HARQ process may also be referred to as the process number of the HARQ process.
  • the terminal device can select the HARQ process id used by itself, and when the corresponding CG resource transmits the data carried on the CG resource, it can inform the network device of the HARQ process id of its choice.
  • the terminal equipment can also perform uplink transmission based on dynamic scheduling.
  • the terminal device when the terminal device receives scheduling information for dynamically scheduling DG resources, and the scheduling information is PDCCH scrambled by C-RNTI, the first HARQ process used for the DG resources, if the first HARQ process is used before The HARQ process is CG resources (including CG resources used for retransmission or new transmission), and the terminal device considers that the New Data Indicator (NDI) is reversed, that is, the scheduling information is used to schedule the newly transmitted data.
  • NDI New Data Indicator
  • the terminal device starts or restarts the configured grant timer (configured GrantTimer, CG timer), and the terminal device compares the scheduling information with the information of the first HARQ process (such as the process of the first HARQ process). Number) to the HARQ entity.
  • the configured grant timer Configured GrantTimer, CG timer
  • the terminal device compares the scheduling information with the information of the first HARQ process (such as the process of the first HARQ process). Number) to the HARQ entity.
  • the terminal device For each HARQ process included in the HARQ entity, if the scheduling information is new transmission scheduling information, the terminal device will call the multiplexing and assembly entity to generate MAC PDU, and use the first HARQ process to send the new transmission. Data, start or restart the CG timer. If the scheduling information is retransmission scheduling information, use the first HARQ process to send retransmission data, and start or restart the CG timer.
  • the terminal device may also set the HARQ process id used by the DG resource to the HARQ process id used by the CG resource.
  • the terminal device receives scheduling information for scheduling DG resources sent by the network device, and the HARQ process used by the DG resources is the first HARQ process, if the CG resources and the DG resources do not overlap in the time domain (for example, PDCCH scheduling resources, CG resources, and resources indicated in a random access response (Random Access Response, RAR) do not overlap), the terminal device may set the first HARQ process id to the HARQ process used by the CG resource id. If the CG timer used for the first HARQ process is not running, it is considered that the NDI is reversed, and the scheduling information information and corresponding HARQ information (such as the HARQ process) are sent to the HARQ entity.
  • the HARQ process used by the DG resources is the first HARQ process
  • the network device is not sure which HARQ process the terminal device has selected before receiving the CG resource, when the network device schedules a DG resource before receiving the data transmitted on the CG resource, it will be The identifier of the HARQ process occupied by the CG resource is assigned to the DG resource.
  • the first HARQ process used by the DG resource may have been occupied by the CG resource.
  • the media interface corresponding to the CG resource that has not yet been air-transmitted or that has been air-transmitted will be saved in the HARQ process.
  • the Media Access Control (MAC) protocol data unit (Protocol Data Unit, PDU) is flushed, causing data packet loss and affecting service quality (Quality of service, QoS) requirements.
  • the network device will not know the HARQ process selected by the terminal device Identifier (id). At this time, the network device may select the HARQ process id selected by the terminal device for the CG resource for dynamic scheduling, which will cause CG MAC PDU transmission problems, such as being flushed, causing QoS problems that cannot be guaranteed.
  • LBT Listen Before Talk
  • the dynamically scheduled resource may be received or another resource is available, and the HARQ process of the received or available resource and the HARQ of the resource that has not completed transmission The process is the same.
  • the terminal device determines the CG resource, if grant 1 is available, the corresponding HARQ process is HARQ process id 1.
  • the terminal device receives the dynamic scheduling DG scheduled by the network, such as grant 2, and the HARQ process corresponding to grant 2 is also HARQ process id 1.
  • the present application provides a wireless communication method and device.
  • the service QoS requirements can be guaranteed.
  • FIG. 2 shows a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application.
  • the method 200 may be executed interactively by a terminal device and a network device.
  • the method 200 may be applicable to IIoT and/or NR-U communication networks.
  • the terminal device shown in FIG. 2 may be the terminal device shown in FIG. 1, and the network device shown in FIG. 2 may be the access network device shown in FIG. 1.
  • the method 200 may include:
  • S210 The terminal device receives scheduling information for scheduling DG resources sent by the network device.
  • the HARQ entity of the terminal device can identify the first HARQ process associated with the DG resource based on the scheduling information, and proceed according to the instructions of the scheduling information Initial transmission/retransmission of data.
  • the terminal device switches the HARQ process used by the CG resource from the first HARQ process to the second HARQ process.
  • the terminal device may use the first HARQ process to send the data carried on the DG resource, and at the same time, the terminal device may also use the second HARQ process to send the data carried on the CG resource .
  • the The second HARQ process normally sends the data carried on the CG resource, thereby ensuring service QoS requirements.
  • DC resources may include resources dynamically scheduled by network devices.
  • the DC resources may include resources scheduled by the network equipment through the PDCCH.
  • CG resources can include two types, Type1 and Type2.
  • CG Type1 may be configured by Radio Resource Control (RRC).
  • RRC Radio Resource Control
  • the terminal device may store the resource indicated by the RRC configuration uplink grant (rrc-ConfiguredUplinkGrant) in the configuration grant configuration (ConfiguredGrantConfig IE) as an uplink CG resource.
  • CG Type 2 can activate/deactivate uplink CG resources according to the physical downlink control channel (Physical Downlink Control Channel, PDCCH) instructions scrambled by the configured scheduling radio network temporary identifier (Configured Scheduling RNTI, CS-RNTI).
  • PDCCH Physical Downlink Control Channel
  • Configured Scheduling RNTI Configured Scheduling RNTI
  • MAC Media Access Control
  • the terminal device may set the identifier of the HARQ process used by the CG resource as the identifier of the second HARQ process, so as to implement the HARQ process used by the CG resource from the first HARQ process.
  • the HARQ process is switched to the second HARQ process.
  • the terminal device may send the information of the second HARQ process (such as the process number of the HARQ process) to the HARQ entity, or copy/transfer the information of the first HARQ process to the second HARQ process in.
  • the information of the second HARQ process such as the process number of the HARQ process
  • the method 200 may further include at least one of the following:
  • the terminal device saves the CG media access control MAC protocol data unit PDU to the HARQ buffer pool of the second HARQ process;
  • the terminal device starts or restarts the CG timer of the second HARQ process.
  • the terminal device stops the CG timer of the first HARQ process.
  • the terminal device may first select the second HARQ process, and then set the identifier of the HARQ process used by the CG resource as the identifier of the second HARQ process.
  • the terminal device may also save the CG media access control MAC protocol data unit PDU to the second HARQ
  • the HARQ buffer pool of the process delete the data in the first HARQ buffer pool, start or restart the CG timer of the second HARQ process, and stop the CG timer of the first HARQ process.
  • the terminal device can directly switch the HARQ process used by the CG resource from the first HARQ process to the second HARQ process, This application does not limit this.
  • the first preset condition includes at least one of the following:
  • the MAC PDU corresponding to the CG resource has been packaged
  • the MAC PDU corresponding to the CG resource has been delivered to the physical layer
  • the MAC PDU corresponding to the CG resource is in an untransmitted state
  • the MAC PDU corresponding to the CG resource is in an unfinished transmission state
  • the MAC PDU corresponding to the CG resource is in a transmitting state
  • the priority of the CG resource is higher than the first threshold
  • the data carried on the CG resource is higher than the third threshold
  • the priority of the MAC control element CE carried on the CG resource is higher than the fourth threshold
  • the DG resource is used to transmit newly transmitted data or retransmitted data
  • the scheduling information is used to schedule newly transmitted data or retransmitted data
  • the scheduling information is the physical downlink control channel PDCCH scrambled by using the cell radio network temporary identifier C-RNTI;
  • the MAC entity determines that the physical uplink shared channel PUSCH of the CG resource listens first and then says that the LBT fails;
  • the transport block size TBS indicated by the scheduling information is different from the size of the CG;
  • the receiving time of the scheduling information does not meet the processing delay of the previous CG transmission.
  • the time between the time corresponding to the CG resource and the time corresponding to the scheduling information is less than the second threshold.
  • the first threshold includes the priority of the DG resource.
  • the first threshold may be a specific value, which may be a predetermined value, or a value configured by a network device, or a value selected by the terminal device itself, or a value predefined by the terminal device. This application does not specifically limit the value determined or selected by multiple values or multiple values configured by the network device.
  • the first threshold may be a value randomly selected by the terminal device among multiple values or a value selected based on a preset criterion.
  • the third threshold includes the priority of the data carried on the DG resource.
  • the fourth threshold includes the priority of the MAC CE carried on the DG resource.
  • the third threshold and/or the fourth threshold may be a specific value, which may be a predetermined value, a value configured by the network device, or a value selected by the terminal device itself, or it may be The value determined or selected by the terminal device in multiple predefined values or multiple values configured by the network device is not specifically limited in this application.
  • the third threshold and/or the fourth threshold may be a value randomly selected by the terminal device from a plurality of values or a value selected based on a preset criterion.
  • the terminal device when the terminal device receives the information indicating the PUSCH LBT failure of the CG resource through the MAC entity, it determines that the PUSCH of the CG resource listens first and then says that the LBT fails.
  • the MAC entity of the terminal device receives the information used to indicate the PUSCH LBT failure of the CG resource, which can be used to determine that the PUSCH of the CG resource listens first and then says that the LBT fails.
  • the terminal device MAC entity determines that the PUSCH LBT of the CG resource fails. For example, when the PUSCH LBT success indication of the CG resource is not received, it determines that the PUSCH of the CG resource first listens to the LBT failure Or, when the physical layer indicates that the PUSCH of the CG resource is not transmitted or is not successfully transmitted, it is determined that the PUSCH of the CG resource is heard first and then said that the LBT has failed.
  • the terminal device determines that the receiving time of the scheduling information does not meet the processing delay of the previous CG transmission
  • the target time period includes at least one of the following time periods:
  • the moment corresponding to the CG resource includes at least one of the following moments:
  • the start time when the terminal device sends the PUSCH is the start time when the terminal device sends the PUSCH.
  • the time corresponding to the scheduling information includes at least one of the following times:
  • the start time domain symbol position of the scheduling information
  • the starting time at which the terminal device receives the scheduling information
  • the second threshold includes at least one of the following:
  • the demodulation time of the PUSCH demodulation reference signal DMRS is the demodulation time of the PUSCH demodulation reference signal DMRS.
  • the second threshold is a pre-configured threshold, or the second threshold is a threshold configured by a network device.
  • the second threshold may be a specific value, which may be a predetermined value, or a value configured by a network device, or a value selected by the terminal device itself, or a value preset by the terminal device.
  • This application does not specifically limit a value determined or selected by multiple values or multiple values configured by the network device.
  • the second threshold may be a value randomly selected by the terminal device from a plurality of values or a value selected based on a preset criterion.
  • the second HARQ process includes an HARQ process that satisfies a second preset condition.
  • the second preset condition includes at least one of the following conditions:
  • the second HARQ process belongs to a HARQ process other than the first HARQ process configured for the CG resource;
  • the buffer pool of the second HARQ process is empty
  • the second HARQ process is not occupied by DG resources
  • the CG timer of the second HARQ process is not running
  • the CG index corresponding to the second HARQ process is the same as the CG index corresponding to the first HARQ process.
  • the second HARQ process may also be any HARQ process other than the first HARQ process, which is not specifically limited in this application.
  • first preset condition and second preset condition are only exemplary descriptions, and those skilled in the art can set different conditions according to actual needs, and their inventive concepts should all belong to the inventive concepts protected by this application.
  • the method 200 may further include:
  • the terminal device sends the data carried on the CG resource to the network device on the CG resource, where the data carried on the CG resource includes the information of the second HARQ process.
  • the network equipment sends scheduling information for scheduling dynamically authorized DG resources to the terminal equipment; the network equipment receives the data carried on the DG resources on the DG resources.
  • the network device receives data carried on the CG resource on the CG resource, and the data carried on the CG resource includes information about the second HARQ process.
  • the second HARQ process is the HARQ process selected by the terminal device.
  • the following is an example of the behavior of the terminal device when the method 200 is applied to IIoT or NR-U.
  • the terminal device receives the CG resource configured by the network device through RRC, where the CG index (index) corresponding to the CG resource is 1, and the HARQ processes configured for it are HARQ process id1 and id2.
  • the terminal device determines that the configured CG resource is available.
  • the resource of the selected or determined CG index1, namely grant1 corresponds to the HARQ process id of 1 (that is, the first HARQ process).
  • the terminal device packages MAC PDU1 for the CG resource group, and submits the MAC PDU1 to the PHY.
  • the MAC PDU1 will be transmitted to the network side through the air interface PUSCH at time t3 (t3>t1).
  • the terminal device receives the DG resource of the newly transmitted data scheduled by the network device through the PDCCH scrambled by the C-RNTI, which corresponds to grant2, and the HARQ process indicated by it is HARQ process id 1.
  • the transmission time of the grant2 on the air interface is t4, where t4 ⁇ t3, or t4>t3, or the time domains of time t4 and t3 overlap.
  • the HARQ process id 1 has been occupied by CG resources (HARQ process id 1 is the conflicting HARQ process, that is, the HARQ corresponding to the conflict between the CG resource and the HARQ process of the DG resource), such as the difference between the CG resource and the DG resource
  • All HARQ processes are HARQ process id1.
  • the terminal device switches the HARQ process of the CG resource from HARQ process id 1 to HARQ process id 2, or the terminal device switches the HARQ process id of the CG resource.
  • the HARQ process ID is set to HARQ process id 2.
  • the first preset condition may include at least one of the following conditions:
  • the MAC PDU corresponding to the CG resource has been packaged
  • the MAC PDU corresponding to the CG resource has been delivered to the physical layer
  • the MAC PDU corresponding to the CG resource is in an untransmitted state
  • the MAC PDU corresponding to the CG resource is in an unfinished transmission state
  • the MAC PDU corresponding to the CG resource is in a transmitting state
  • the priority of the CG resource is higher than the first threshold
  • the data carried on the CG resource is higher than the third threshold
  • the priority of the MAC control element CE carried on the CG resource is higher than the fourth threshold
  • the DG resource is used to transmit newly transmitted data or retransmitted data
  • the scheduling information is used to schedule newly transmitted data or retransmitted data
  • the scheduling information is the physical downlink control channel PDCCH scrambled by using the cell radio network temporary identifier C-RNTI;
  • the transport block size TBS indicated by the scheduling information is different from the size of the CG;
  • the receiving time of the scheduling information does not meet the processing delay of the previous CG transmission.
  • the time between the time corresponding to the CG resource and the time corresponding to the scheduling information is less than the second threshold.
  • the terminal device will select HARQ process id 2 as the HARQ process used by the CG resource, and the CG resource Set the HARQ process ID to HARQ process id 2, save CG MAC PDU1 in the HARQ buffer of HARQ process id 2, delete the data in the buffer pool of HARQ process id 1, start or restart the CG timer corresponding to HARQ process id 2, and stop Corresponds to the CG timer of HARQ process id 1.
  • the terminal device can operate in accordance with the existing protocol.
  • the MAC PDU is grouped for the DG resource, and the grouped MAC PDU is stored in the first HARQ process.
  • the terminal device packages the grant2 corresponding to the DG resource, and saves the MAC PDU2 of the package in the buffer pool of HARQ process id 1).
  • the terminal device will submit grant2 and HARQ information (such as HARQ process id1) to the corresponding HARQ process, and package MAC PDU2 for grant2.
  • grant2 and HARQ information such as HARQ process id1
  • the scenario where the HARQ process conflicts between the CG and the DG is defined to avoid the priority of the DG resource always being higher than the CG resource; when the HARQ process corresponding to the two resources conflict (IIoT or NR-U scenario) , That is, if the DG resource scheduled by DCI is received when the first HARQ process is already occupied by CG resources, the HARQ process can be replaced by the HARQ process of the CG resource, and the CG MAC PDU can be saved in the new HARQ buffer conflicting resources to resolve the HARQ process
  • the problem of data packet loss caused by conflicts can effectively ensure the normal transmission of untransmitted CG data and ensure service QoS.
  • the terminal device receives the CG resource configured by the network device through RRC, where the CG index corresponding to the CG resource is 1, and the configured HARQ processes are HARQ process id1 and id2.
  • the terminal device determines that the configured CG resource is available.
  • the resource of CG index1 selected or determined by the terminal device namely grant1 corresponds to HARQ process id 1.
  • the terminal device packages MAC PDU1 for the CG resource group, and delivers the MAC PDU1 to the PHY.
  • the MAC PDU1 will be transmitted to the network side through the air interface PUSCH at time t2 (t2>t1).
  • the terminal device executes LBT, and finds that CG PUSCH LBT fails at time t2 or before time t2.
  • the physical layer of the terminal device timely informs the MAC layer of the terminal device of the failure information of CG PUSCH LBT.
  • the terminal device receives the newly transmitted DG resource scheduled by the PDCCH scrambled by the network device through the C-RNTI, corresponding to grant2, and the HARQ process indicated by it is HARQ process id 1.
  • the sending time of the grant2 on the air interface is t4, and t4>t3.
  • HARQ process id 1 has been occupied by CG resources (HARQ process id 1 is the conflicting HARQ process, that is, the corresponding HARQ when the HARQ process of the CG resource and the DG resource conflict), such as the HARQ process of the CG resource and the DG resource All are HARQ process id1.
  • the terminal device switches the HARQ process of the CG resource from HARQ process id 1 to HARQ process id 2, or the terminal device switches the HARQ process of the CG resource
  • the identifier is set to HARQ process id 2.
  • the first preset condition may include at least one of the following conditions:
  • the MAC PDU corresponding to the CG resource has been packaged
  • the MAC PDU corresponding to the CG resource has been delivered to the physical layer
  • the MAC PDU corresponding to the CG resource is in an untransmitted state
  • the MAC PDU corresponding to the CG resource is in an unfinished transmission state
  • the MAC PDU corresponding to the CG resource is in a transmitting state
  • the priority of the CG resource is higher than the first threshold
  • the data carried on the CG resource is higher than the third threshold
  • the priority of the MAC control element CE carried on the CG resource is higher than the fourth threshold
  • the DG resource is used to transmit newly transmitted data or retransmitted data
  • the scheduling information is used to schedule newly transmitted data or retransmitted data
  • the scheduling information is the physical downlink control channel PDCCH scrambled by using the cell radio network temporary identifier C-RNTI;
  • the MAC entity determines that the physical uplink shared channel PUSCH of the CG resource listens first and then says that the LBT fails;
  • the transport block size TBS indicated by the scheduling information is different from the size of the CG;
  • the receiving time of the scheduling information does not meet the processing delay of the previous CG transmission.
  • the time between the time corresponding to the CG resource and the time corresponding to the scheduling information is less than the second threshold.
  • the terminal device MAC receives the failure indication of CG grant1LBT, it receives the new transmission of grant2 scheduled by DCI.
  • the HARQ process of grant2 and grant1 are the same, and both are HARQ process id1.
  • the terminal device selects HARQ process id2 as the second HARQ process and sets CG
  • the HARQ process identifier of the resource is set to HARQ process id2, the CG MAC PDU stored in HARQ process id1 is put into the buffer of HARQ process id2, and the CG timer of HARQ process id2 is started.
  • the terminal device can operate in accordance with the existing protocol.
  • the MAC PDU is grouped for the DG resource, and the grouped MAC PDU is stored in the first HARQ process.
  • the terminal device packages the grant2 corresponding to the DG resource, and saves the MAC PDU2 of the package in the buffer pool of HARQ process id 1).
  • the terminal device will submit grant2 and HARQ information (such as HARQ process id1) to the corresponding HARQ process, and package MAC PDU2 for grant2.
  • grant2 and HARQ information such as HARQ process id1
  • the scenario where the HARQ process conflicts between the CG and the DG is defined to avoid the priority of the DG resource always being higher than the CG resource; when the HARQ process corresponding to the two resources conflict (NR-U scenario), that is If the DG resource scheduled by DCI is received when the first HARQ process is already occupied by CG resources, the CG MAC PDU can be saved in the new HARQ buffer by changing the HARQ process of the CG resource to resolve the conflicting resources of the HARQ process.
  • the problem of data packet loss caused can effectively ensure the normal transmission of untransmitted CG data and ensure service QoS.
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not be implemented in this application.
  • the implementation process of the example constitutes any limitation.
  • FIG. 3 is a schematic block diagram of a terminal device 300 according to an embodiment of the present application.
  • the terminal device 300 may include:
  • the communication unit 310 is configured to receive scheduling information for scheduling dynamically authorized DG resources sent by a network device;
  • the processing unit 320 is configured to change the HARQ process used by the CG resource from the HARQ process used by the CG resource when the HARQ process of the first hybrid automatic repeat request used by the DG resource has been occupied by the configured authorized CG resource The first HARQ process is switched to the second HARQ process.
  • the processing unit 320 is specifically configured to:
  • the identifier of the HARQ process used by the CG resource is set as the identifier of the second HARQ process.
  • processing unit 320 is further configured to perform at least one of the following actions:
  • the processing unit 320 is specifically configured to:
  • the HARQ process used by the CG resource is switched from the first HARQ process to the second HARQ process.
  • the first preset condition includes at least one of the following:
  • the MAC PDU corresponding to the CG resource has been packaged
  • the MAC PDU corresponding to the CG resource has been delivered to the physical layer
  • the MAC PDU corresponding to the CG resource is in an untransmitted state
  • the MAC PDU corresponding to the CG resource is in an unfinished transmission state
  • the MAC PDU corresponding to the CG resource is in a transmitting state
  • the priority of the CG resource is higher than the first threshold
  • the data carried on the CG resource is higher than the third threshold
  • the priority of the MAC control element CE carried on the CG resource is higher than the fourth threshold
  • the DG resource is used to transmit newly transmitted data or retransmitted data
  • the scheduling information is used to schedule newly transmitted data or retransmitted data
  • the scheduling information is the physical downlink control channel PDCCH scrambled by using the cell radio network temporary identifier C-RNTI;
  • the MAC entity determines that the physical uplink shared channel PUSCH of the CG resource listens first and then says that the LBT fails;
  • the transport block size TBS indicated by the scheduling information is different from the size of the CG;
  • the receiving time of the scheduling information does not meet the processing delay of the previous CG transmission.
  • the time between the time corresponding to the CG resource and the time corresponding to the scheduling information is less than the second threshold.
  • the first threshold includes the priority of the DG resource.
  • the third threshold includes the priority of the data carried on the DG resource
  • the fourth threshold includes the priority of the MAC CE carried on the DG resource level.
  • the processing unit 320 is further configured to:
  • the MAC entity receives the information used to indicate the PUSCH LBT failure of the CG resource.
  • the processing unit 320 is further configured to:
  • the scheduling information is received within the target time period, it is determined that the receiving time of the scheduling information does not meet the processing delay of the previous CG transmission;
  • the target time period includes at least one of the following time periods:
  • the moment corresponding to the CG resource includes at least one of the following moments:
  • the start time when the terminal device sends the PUSCH is the start time when the terminal device sends the PUSCH.
  • the time corresponding to the scheduling information includes at least one of the following times:
  • the start time domain symbol position of the scheduling information
  • the starting time at which the terminal device receives the scheduling information
  • the second threshold includes at least one of the following:
  • the demodulation time of the PUSCH demodulation reference signal DMRS is the demodulation time of the PUSCH demodulation reference signal DMRS.
  • the second threshold is a pre-configured threshold, or the second threshold is a threshold configured by a network device.
  • the second HARQ process includes an HARQ process that satisfies a second preset condition.
  • the second preset condition includes at least one of the following conditions:
  • the second HARQ process belongs to a HARQ process other than the first HARQ process configured for the CG resource;
  • the buffer pool of the second HARQ process is empty
  • the second HARQ process is not occupied by DG resources
  • the CG timer of the second HARQ process is not running
  • the CG index corresponding to the second HARQ process is the same as the CG index corresponding to the first HARQ process.
  • the communication unit 310 is further configured to:
  • the data carried on the CG resource is sent on the CG resource, and the data carried on the CG resource includes the information of the second HARQ process.
  • the terminal device is suitable for industrial Internet IIoT and/or new air interface-unlicensed communication network.
  • the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment.
  • the terminal device 300 shown in FIG. 3 may correspond to the corresponding main body in the method 200 that executes the embodiment of the present application, and the foregoing and other operations and/or functions of the various units in the terminal device 300 are used to implement the operations and/or functions shown in FIG. 2 respectively.
  • the corresponding process in each method of the method will not be repeated here.
  • the functional module can be implemented in the form of hardware, can also be implemented in the form of software instructions, or can be implemented in a combination of hardware and software modules.
  • the steps of the method embodiments in the embodiments of the present application can be completed by hardware integrated logic circuits in the processor and/or instructions in the form of software.
  • the steps can be directly embodied as hardware
  • the execution of the decoding processor is completed, or the execution is completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium in the field, such as a random access memory, a flash memory, a read only memory, a programmable read only memory, an electrically erasable programmable memory, and a register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps in the foregoing method embodiment in combination with its hardware.
  • processing unit and the communication unit referred to above may be implemented by a processor and a transceiver, respectively.
  • FIG. 4 is a schematic structural diagram of a communication device 400 according to an embodiment of the present application.
  • the communication device 400 may include a processor 410.
  • the processor 410 may call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the communication device 400 may further include a memory 420.
  • the memory 420 may be used to store instruction information, and may also be used to store codes and instructions executed by the processor 410.
  • the processor 410 may call and run a computer program from the memory 420 to implement the method in the embodiment of the present application.
  • the memory 420 may be a separate device independent of the processor 410, or may be integrated in the processor 410.
  • the communication device 400 may further include a transceiver 430.
  • the processor 410 may control the transceiver 430 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
  • the transceiver 430 may include a transmitter and a receiver.
  • the transceiver 430 may further include an antenna, and the number of antennas may be one or more.
  • the various components in the communication device 400 are connected by a bus system, where in addition to a data bus, the bus system also includes a power bus, a control bus, and a status signal bus.
  • the communication device 400 may be the terminal device of the embodiment of the application, and the communication device 400 may implement the corresponding process implemented by the terminal device in each method of the embodiment of the application, that is, the communication device 400 of the embodiment of the application
  • the communication device 400 may correspond to the terminal device 300 in the embodiment of the present application, and may correspond to a corresponding subject in executing the method 200 according to the embodiment of the present application.
  • the communication device 400 may be a network device in an embodiment of the present application, and the communication device 400 may implement corresponding processes implemented by the network device in each method in the embodiments of the present application.
  • the communication device 400 in the embodiment of the present application may correspond to the network device 400 in the embodiment of the present application, and may correspond to the corresponding subject that executes the method 200 according to the embodiment of the present application.
  • the communication device 400 in the embodiment of the present application may correspond to the network device 400 in the embodiment of the present application, and may correspond to the corresponding subject that executes the method 200 according to the embodiment of the present application.
  • it will not be omitted here. Go into details.
  • an embodiment of the present application also provides a chip.
  • the chip may be an integrated circuit chip with signal processing capability, and can implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the chip may also be called a system-level chip, a system-on-chip, a system-on-a-chip, or a system-on-chip.
  • the chip can be applied to various communication devices, so that the communication device installed with the chip can execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • FIG. 5 is a schematic structural diagram of a chip 500 according to an embodiment of the present application.
  • the chip 500 includes a processor 510.
  • processor 510 may call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 500 may further include a memory 520.
  • the processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.
  • the memory 520 may be used to store instruction information, and may also be used to store codes and instructions executed by the processor 510.
  • the memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.
  • the chip 500 may further include an input interface 530.
  • the processor 510 can control the input interface 530 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 500 may further include an output interface 540.
  • the processor 510 can control the output interface 540 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip 500 can be applied to the network equipment in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application, and can also implement the various methods of the embodiments of the present application.
  • the corresponding process implemented by the terminal device in the above will not be repeated here.
  • the various components in the chip 500 are connected by a bus system, where in addition to the data bus, the bus system also includes a power bus, a control bus, and a status signal bus.
  • the processor may include, but is not limited to:
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • FPGA Field Programmable Gate Array
  • the processor may be used to implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed 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 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 storage includes but is not limited to:
  • 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 random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM static random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Synchronous Link Dynamic Random Access Memory
  • SLDRAM Direct Rambus RAM
  • the embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium stores one or more programs, and the one or more programs include instructions.
  • the portable electronic device can execute the implementation shown in method 200. Example method.
  • the computer-readable storage medium can 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 causes 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 the sake of brevity, I won’t repeat it here.
  • the embodiments of the present application also provide a computer program product, including a computer program.
  • the computer program product can 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 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 product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, in order to It's concise, so I won't repeat it here.
  • a computer program is also provided in the embodiment of the present application.
  • the computer program When the computer program is executed by a computer, the computer can execute the method of the embodiment shown in method 200.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, it causes the computer 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.
  • an embodiment of the present application also provides a communication system.
  • the communication system may include the aforementioned terminal equipment and network equipment to form the communication system 100 as shown in FIG. 1.
  • the terms "system” in this article can also be referred to as “network management architecture” or “network system”.
  • the technical solutions of the embodiments of the present application are essentially or the part that contributes to the prior art or the part of the technical solutions can be embodied in the form of a software product, and the computer software product is stored in a storage medium.
  • Including several instructions 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 method described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.
  • the division of units or modules or components in the device embodiments described above is only a logical function division, and there may be other divisions in actual implementation.
  • multiple units or modules or components can be combined or integrated.
  • To another system, or some units or modules or components can be ignored or not executed.
  • the aforementioned units/modules/components described as separate/display components may or may not be physically separated, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units/modules/components may be selected according to actual needs to achieve the objectives of the embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

提供了一种无线通信的方法和设备，所述方法包括：接收网络设备发送的用于调度动态授权DG资源的调度信息；在所述DG资源使用的第一混合自动重传请求HARQ进程已被配置授权CG资源占用的情况下，将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。基于以上技术方案，通过将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程，在CG资源对应的HARQ进程和DG资源对应的HARQ进程发生冲突时，能够通过所述第二HARQ进程正常发送所述CG资源上承载的数据，进而保证业务QoS需求。

Description

无线通信的方法和设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及无线通信的方法和设备。
背景技术
配置授权(Configured，grant，CG)和动态授权(Dynamic，grant，DG)两种授权(grant)的混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)进程冲突时是需要进一步研究(For Further Study，FFS)的。
按照现有协议，不论DG资源和CG资源在时域是否有重叠，DG资源的优先级永远高于CG资源；当两个资源对应的HARQ进程冲突时，将会发生以下问题：
针对工业互联网(Industrial interest of Things，IIoT)或新空口-非授权(New Radio Unlicensed,NR-U)通信网络，若CG资源已经组包或组好的包已经发送给物理层(PHY)，一旦DG资源到达，将把保存在该HARQ进程中的尚未进行空口传输或已经进行空口传输的CG资源对应的媒体接入控制(Media Access Control，MAC)协议数据单元(Protocol Data Unit，PDU)冲洗(flush)掉，造成数据包丢失，影响业务服务质量(Quality of service，QoS)需求。
针对NR-U场景，若CG资源已经组包或组好的包已经发送给PHY，但是由于先听后说(Listen Before Talk，LBT)失败导致CG资源不能发给网络设备，网络设备将不能知道终端设备选择的HARQ进程标识(id)，此时，网络设备可能选择终端设备为该CG资源选择的HARQ进程id进行动态调度，进而会造成CG MAC PDU的传输问题，比如被flush掉，造成QoS不能保证的问题。
因此，CG资源对应的HARQ进程和DG资源对应的HARQ进程发生冲突时，如何保证业务QoS需求是本领域急需解决的技术问题。
发明内容
提供了一种无线通信的方法和设备，CG资源对应的HARQ进程和DG资源对应的HARQ进程发生冲突时，能够保证业务QoS需求。
第一方面，提供了一种无线通信的方法，包括：
接收网络设备发送的用于调度动态授权DG资源的调度信息；
在所述DG资源使用的第一混合自动重传请求HARQ进程已被配置授权CG资源占用的情况下，将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
第二方面，提供了一种终端设备，用于执行上述第一方面或其各实现方式中的方法。具体地，所述终端设备包括用于执行上述第一方面或其各实现方式中的方法的功能模块。
第三方面，提供了一种终端设备，包括处理器和存储器。所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行上述第一方面或其各实现方式中的方法。
第四方面，提供了一种芯片，用于实现上述第一方面或其各实现方式中的方法。具体地，所述芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如上述第一方面或其各实现方式中的方法。
第五方面，提供了一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行上述第一方面或其各实现方式中的方法。
第六方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行上述第一方面或其各实现方式中的方法。
第七方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述 第一方面或其各实现方式中的方法。
基于以上技术方案，通过将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程，在CG资源对应的HARQ进程和DG资源对应的HARQ进程发生冲突时，能够通过所述第二HARQ进程正常发送所述CG资源上承载的数据，进而保证业务QoS需求。
附图说明
图1是本申请应用场景的示例。
图2是本申请实施例的无线通信的方法的示意性流程图。
图3是本申请实施例的终端设备的示意性框图。
图4是本申请实施例的通信设备的示意性框图。
图5是本申请实施例的芯片的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1是本申请实施例的一个应用场景的示意图。
如图1所示，通信系统100可以包括终端设备110和网络设备120。网络设备120可以通过空口与终端设备110通信。终端设备110和网络设备120之间支持多业务传输。
应理解，本申请实施例仅以通信系统100进行示例性说明，但本申请实施例不限定于此。也就是说，本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(Long Term Evolution，LTE)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、5G通信系统(也称为新无线(New Radio，NR)通信系统)，或未来的通信系统等。
在图1所示的通信系统100中，网络设备120可以是与终端设备110通信的接入网设备。接入网设备可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备110(例如UE)进行通信。
网络设备120可以是长期演进(Long Term Evolution，LTE)系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是下一代无线接入网(Next Generation Radio Access Network，NG RAN)设备，或者是NR系统中的基站(gNB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备120可以为中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
终端设备110可以是任意终端设备，其包括但不限于与网络设备120或其它终端设备采用有线或者无线连接的终端设备。
例如，所述终端设备110可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进网络中的终端设备等。
终端设备110可以用于设备到设备(Device to Device，D2D)的通信。
无线通信系统100还可以包括与基站进行通信的核心网设备130，该核心网设备130 可以是5G核心网(5G Core，5GC)设备，例如，接入与移动性管理功能(Access and Mobility Management Function，AMF)，又例如，认证服务器功能(Authentication Server Function，AUSF)，又例如，用户面功能(User Plane Function，UPF)，又例如，会话管理功能(Session Management Function，SMF)。可选地，核心网络设备130也可以是LTE网络的分组核心演进(Evolved Packet Core，EPC)设备，例如，会话管理功能+核心网络的数据网关(Session Management Function+Core Packet Gateway，SMF+PGW-C)设备。应理解，SMF+PGW-C可以同时实现SMF和PGW-C所能实现的功能。在网络演进过程中，上述核心网设备也有可能叫其它名字，或者通过对核心网的功能进行划分形成新的网络实体，对此本申请实施例不做限制。
通信系统100中的各个功能单元之间还可以通过下一代网络(next generation，NG)接口建立连接实现通信。
例如，终端设备通过NR接口与接入网设备建立空口连接，用于传输用户面数据和控制面信令；终端设备可以通过NG接口1(简称N1)与AMF建立控制面信令连接；接入网设备例如下一代无线接入基站(gNB)，可以通过NG接口3(简称N3)与UPF建立用户面数据连接；接入网设备可以通过NG接口2(简称N2)与AMF建立控制面信令连接；UPF可以通过NG接口4(简称N4)与SMF建立控制面信令连接；UPF可以通过NG接口6(简称N6)与数据网络交互用户面数据；AMF可以通过NG接口11(简称N11)与SMF建立控制面信令连接；SMF可以通过NG接口7(简称N7)与PCF建立控制面信令连接。
图1示例性地示出了一个基站、一个核心网设备和两个终端设备，可选地，该无线通信系统100可以包括多个基站设备并且每个基站的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备均可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备120和终端设备110，网络设备120和终端设备110可以为上文所述的设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
下面对本申请实施例使用的通信系统100适用的网络进行示例性说明。
在本申请的一些实施例中，所述通信系统100可以适用于第五代移动通信技术(5-Generation，5G)工业互联网(Industrial interest of Things，IIoT)。
5G IIoT可支持工业自动化(Factory automation)，传输自动化(Transport Industry)，智能电力(Electrical Power Distribution)等业务在5G系统的传输。
然而，5G IIoT有可能会出现资源冲突。
其中，所述资源冲突包括数据信道和数据信道的冲突，其可以包括DG资源和DG资源之间的冲突，DG资源和CG资源之间的冲突，CG资源和CG资源之间的冲突。
例如，当多个授权(grant)资源之间发生冲突时，特别是DG和CG之间冲突时，有可能出现两个grant所使用的HARQ进程相同的情况。例如，若CG资源已经组包或组好的包已经发送给物理层(PHY)，一旦DG资源到达，将把保存在该HARQ进程中的尚未进行空口传输或已经进行空口传输的CG资源对应的媒体接入控制(Media Access Control，MAC)协议数据单元(Protocol Data Unit，PDU)冲洗(flush)掉，造成数据包丢失，影响业务服务质量(Quality of service，QoS)需求。
因此，CG资源对应的HARQ进程和DG资源对应的HARQ进程发生冲突时，如何 保证业务QoS需求是本领域急需解决的技术问题。
在本申请的另一些实施例中，所述通信系统100可以适用于NR-U网络。
换言之，所述终端设备110或网络设备120可以适用于NR-U网络。NR工作在非授权频段。
其中，所述NR-U网络包括但不限于以下几种工作场景：
场景A：载波聚合场景。即，主小区(PCell)工作在授权频谱上，辅小区(SCell)通过载波聚合方式聚合工作在非授权频谱上。
场景B：双连接工作场景。即，PCell工作在授权频谱上，主辅小区(Primary Secondary Cell，PSCell)工作在NR非授权频谱上。
场景C：独立工作场景。即，NR作为一个独立小区工作在非授权频谱。
场景D：NR单小区场景。即，上行(UL)工作在授权频谱，下行(DL)工作在非授权频谱。
场景E：双连接工作场景，PCell工作在NR授权频谱，PSCell工作在NR非授权频谱。
例如，NR-U的工作频带(Band)可以为5GHz非授权频谱和6GHz非授权频谱。在非授权频谱上，NR-U的设计需要保证与其他已经工作在这些非授权频谱上的系统之间的公平性，比如WiFi等。例如，对于已经部署在非授权频谱上的系统(比如WiFi)的影响不能超过这些系统之间的影响。
可以通过能量检测机制，保证在非授权频谱上各系统之间的公平性共存，例如LBT机制。
具体实现中，网络设备或者终端设备(传输端)在非授权频谱上传输数据之前，需要先按照规定侦听一段时间。如果侦听的结果表示该信道为空闲状态，则传输端可以给接收端传输数据。如果侦听的结果表示该信道为占用状态，则传输端需要根据规定回退一段时间再继续侦听信道，直到信道侦听结果为空闲状态，才能向接收端传输数据。
可以通过以下四种信道接入机制(category)进行信道接入：
直接传输机制：
传输端(TX)可以在信道占用时间(Channel Occupancy Time，COT)内的转换时间(switching gap)之后迅速传输。Switching gap可以指接收到传输数据的转换时间，例如，所述Switching gap可以不超过16us。
不需要随机回退(back-off)的LBT机制：
终端设备侦听信道的时间是确定的，比如25us。
随机back-off的LBT机制(竞争窗口固定)：
在LBT流程中，传输侧随机的在竞争窗口中取一个随机值来决定侦听信道的时间。
随机back-off的LBT机制(竞争窗口不固定)：
在LBT流程中，传输侧随机的在竞争窗口中取一个随机值来决定侦听信道的时间，竞争窗口是可变的。
由此可见，对终端设备而言，网络设备给终端设备传输数据时需要在最大信道占用时间(Maximum Channel Occupancy Time，MCOT)内，如果网络设备没有抢占到信道。换言之，若在MCOT时间之外，终端设备是不会收到网络设备给该终端设备的调度数据。
对于终端设备发起的上行传输，包括但不限于如下几类：
调度请求(Scheduling Request，SR)，用于请求上行资源。
物理随机接入信道(Physical Random Access Channel，PRACH)，由随机接入信道(Random Access Channel，RACH)触发终端设备向网络设备发送消息1(msg1)。
物理上行共享信道(Physical Uplink Shared Channel，PUSCH)，包括基于CG资源的上行数据传输以及基于DG资源的上行数据传输。
物理层信令，包括确认/非确认(ACK/NACK)和信道状态信息(Channel State  Information，CSI)。
在非授权频带上，终端设备传输SR，PRACH或者PUSCH之前都需要先用LBT来侦听信道是否可用，如果不可以用，即LBT失败，则终端设备需要等到下一个传输机会再次执行LBT。若检测到LBT失败，需要通知给MAC层LBT失败的信息。
在NR-U中，终端设备可以采用自动上行传输(AUL)的方式传输CG资源上承载的数据。例如，网络设备可以为终端设备配置CG资源可用的多个HARQ进程，例如多个HARQ进程的标识(Identification，id)。HARQ进程的标识也可称为HARQ进程的进程号。
此时，对每个CG资源，终端设备可以自行选择使用的HARQ进程id，并在对应的CG资源传输CG资源上承载的数据时，可以将自己选择的HARQ进程id告诉给网络设备。
于此同时，终端设备也可以基于动态调度进行上行传输。
例如，终端设备收到用于动态调度DG资源的调度信息，且所述调度信息为C-RNTI加扰的PDCCH时，针对所述DG资源使用的第一HARQ进程，若之前使用所述第一HARQ进程的是CG资源(包括用于重传或新传的CG资源)，所述终端设备认为新数据指示(New Data Indicator，NDI)翻转，即所述调度信息用于调度新传数据。
此时，所述终端设备启动或重启配置授权定时器(configuredGrantTimer，CG timer)，且所述终端设备将所述调度信息和所述第一HARQ进程的信息(如所述第一HARQ进程的进程号)发给HARQ实体。
对于HARQ实体包括的每个HARQ进程来说，若所述调度信息为新传调度信息，终端设备会调用复用组包实体(Multiplexing and assembly entity)生成MAC PDU，使用第一HARQ进程发送新传数据，启动或重启CG timer。若所述调度信息为重传调度信息，使用所述第一HARQ进程发送重传数据，启动或重启CG timer。
此外，所述终端设备也可以将所述DG资源使用的HARQ进程id设置为所述CG资源使用的HARQ进程id。
例如，终端设备接收到网络设备发送的用于调度DG资源的调度信息，且所述DG资源使用的HARQ进程为第一HARQ进程，若CG资源和所述DG资源在时域上不重叠(例如PDCCH调度的资源、CG资源和随机接入响应(Random Access Response，RAR)中指示的资源不重叠)，所述终端设备可以将所述第一HARQ进程id设置为所述CG资源使用的HARQ进程id。若用于所述第一HARQ进程的CG timer未运行时，认为NDI翻转，且将所述调度信息信息和相应HARQ信息(如HARQ进程)发给HARQ实体。
但是，由于网络设备在收到该CG资源之前并不确定终端设备自己选择的是哪个HARQ进程，因此，网络设备在收到CG资源上传输的数据之前调度一个DG资源时，会将已经被所述CG资源占用的HARQ进程的标识指定给所述DG资源。
即，所述DG资源使用的第一HARQ进程有可能已被CG资源占用。
此时，会存在如下问题：
若CG资源已经组包或组好的包已经发送给物理层(PHY)，一旦DG资源到达，将把保存在该HARQ进程中的尚未进行空口传输或已经进行空口传输的CG资源对应的媒体接入控制(Media Access Control，MAC)协议数据单元(Protocol Data Unit，PDU)冲洗(flush)掉，造成数据包丢失，影响业务服务质量(Quality of service，QoS)需求。
若CG资源已经组包或组好的包已经发送给PHY，但是由于先听后说(Listen Before Talk，LBT)失败导致CG资源不能发给网络设备，网络设备将不能知道终端设备选择的HARQ进程标识(id)，此时，网络设备可能选择终端设备为该CG资源选择的HARQ进程id进行动态调度，进而会造成CG MAC PDU的传输问题，比如被flush掉，造成QoS不能保证的问题。
基于以上分析可知，不论IIoT还是NR-U，都有可能出现两个grant HARQ进程冲突 的情况。
即，在一个资源未传输或未完成传输时，可能又收到动态调度的资源或者又有一个资源可用的情况，且该后收到或可用的资源的HARQ进程与未完成传输的资源的HARQ进程相同。
例如，在t1时刻终端设备确定CG资源，如grant 1可用，对应的HARQ进程为HARQ process id 1。在t2时刻(t2>t1)，终端设备收到网络调度的动态调度DG，如grant 2，且该grant2对应的HARQ进程同样为HARQ process id 1。
此时，若CG资源(grant1)尚未传输或未完成传输，如何保证业务QoS需求是本领域急需解决的技术问题。
本申请提供了一种无线通信的方法和设备，CG资源对应的HARQ进程和DG资源对应的HARQ进程发生冲突时，能够保证业务QoS需求。
图2示出了根据本申请实施例的无线通信的方法200的示意性流程图，该方法200可以由终端设备和网络设备交互执行。所述方法200可以适用于IIoT和/或NR-U通信网络。图2中所示的终端设备可以是如图1所示的终端设备，图2中所示的网络设备可以是如图1所示的接入网设备。
如图2所示，所述方法200可包括：
S210，终端设备接收网络设备发送的用于调度DG资源的调度信息。
S220，在所述DG资源使用的第一HARQ进程已被CG资源占用的情况下，所述终端设备将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
例如，所述终端设备接收到调度信息时，所述终端设备的HARQ实体可基于所述调度信息可识别出与所述DG资源相关联的第一HARQ进程，并根据所述调度信息的指示进行数据的初传/重传。
进一步地，若所述DG资源使用的第一HARQ进程已被CG资源占用，所述终端设备将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
换言之，所述终端设备可以使用所述第一HARQ进程发送所述DG资源上承载的数据，于此同时，所述终端设备还可以利用所述第二HARQ进程发送所述CG资源上承载的数据。
基于以上技术方案，通过将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程，在CG资源对应的HARQ进程和DG资源对应的HARQ进程发生冲突时，能够通过所述第二HARQ进程正常发送所述CG资源上承载的数据，进而保证业务QoS需求。
为了便于对本申请方案的理解，下面对CG资源和DC资源进行介绍。
DC资源可以包括网络设备动态调度的资源。
例如，所述DC资源可以包括网络设备通过PDCCH调度的资源。
CG资源可以包括Type1和Type2两种类型。
CG Type1可以由无线资源控制(Radio Resource Control，RRC)配置，例如所述终端设备可以将配置授权配置(ConfiguredGrantConfig IE)中由RRC配置上行授权(rrc-ConfiguredUplinkGrant)指示的资源存储为上行CG资源。
CG Type2可以根据配置调度无线网络临时标识(Configured Scheduling RNTI，CS-RNTI)加扰的物理下行控制信道(Physical Downlink Control Channel，PDCCH)指令激活/去激活上行CG资源。
对于同一个服务小区，可以通过RRC信令可为媒体接入控制(Media Access Control，MAC)实体配置Type1或Type2的CG资源。
在S220中，作为示例，所述终端设备可以将所述CG资源使用的HARQ进程的标识设置为所述第二HARQ进程的标识，以实现将所述CG资源使用的HARQ进程从所述 第一HARQ进程切换为第二HARQ进程。
换言之，所述终端设备可以将所述第二HARQ进程的信息(如HARQ进程的进程号)发给HARQ实体，或者，将所述第一HARQ进程的信息复制/转移到所述第二HARQ进程中。
在本申请的一些实施例中，所述方法200还可包括以下中的至少一项：
所述终端设备选择所述第二HARQ进程；
所述终端设备将CG媒体接入控制MAC协议数据单元PDU保存至所述第二HARQ进程的HARQ缓冲池；
所述终端设备删除所述第一HARQ缓冲池中的数据；
所述终端设备启动或重启所述第二HARQ进程的CG定时器；以及
所述终端设备停止所述第一HARQ进程的CG定时器。
例如，所述终端设备可以先选择所述第二HARQ进程，然后将所述CG资源使用的HARQ进程的标识设置为所述第二HARQ进程的标识。
又例如，所述终端设备将所述CG资源使用的HARQ进程的标识设置为所述第二HARQ进程的标识之后，还可以将CG媒体接入控制MAC协议数据单元PDU保存至所述第二HARQ进程的HARQ缓冲池，删除所述第一HARQ缓冲池中的数据，启动或重启所述第二HARQ进程的CG定时器，以及停止所述第一HARQ进程的CG定时器。
在S220中，作为示例，若所述DG资源使用的第一HARQ进程已被所述CG资源占用，且满足第一预设条件，将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
当然，若所述DG资源使用的第一HARQ进程已被所述CG资源占用，所述终端设备可以直接将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程，本申请对此不做限定。
在本申请的一些实施例中，所述第一预设条件包括以下中的至少一项：
所述CG资源对应的MAC PDU已经组包；
所述CG资源对应的MAC PDU已经递交到物理层；
所述CG资源对应的MAC PDU处于未传输状态；
所述CG资源对应的MAC PDU处于未完成传输状态；
所述CG资源对应的MAC PDU处于正在传输状态；
所述CG资源的优先级高于第一门限；
承载在所述CG资源上的数据高于第三门限；
承载在所述CG资源上的MAC控制元素CE的优先级高于第四门限；
所述DG资源用于传输新传数据或重传数据；
所述调度信息用于调度新传数据或重传数据；
所述调度信息为采用小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；
MAC实体确定所述CG资源的物理上行共享信道PUSCH先听后说LBT失败；
所述调度信息指示的传输块大小TBS和所述CG的大小不同；
所述调度信息的接收时刻不满足前一次CG传输的处理时延；以及
所述CG资源对应的时刻到调度信息对应的时刻之间的时间小于第二门限。
在本申请的一些实施例中，所述第一门限包括所述DG资源的优先级。
应理解，所述第一门限可以是具体的数值，其可以是预定于的数值，也可以是网络设备配置的数值，也可以是终端设备自己选择的值，还可以是终端设备在预定义的多个数值或网络设备配置的多个数值确定或选取的数值，本申请对此不做具体限定。
例如，所述第一门限可以是终端设备在多个数值中随机选择的或基于预设准则选取的数值。
在本申请的一些实施例中，所述第三门限包括述承载在所述DG资源上的数据的优先级。
在本申请的一些实施例中，所述第四门限包括承载在所述DG资源上的MAC CE的优先级。
应理解，所述第三门限和/或第四门限可以是具体的数值，其可以是预定于的数值，也可以是网络设备配置的数值，也可以是终端设备自己选择的值，还可以是终端设备在预定义的多个数值或网络设备配置的多个数值确定或选取的数值，本申请对此不做具体限定。
例如，所述第三门限和/或第四门限可以是终端设备在多个数值中随机选择的或基于预设准则选取的数值。
在本申请的一些实施例中，终端设备通过MAC实体收到用于指示所述CG资源的PUSCH LBT失败的信息时，确定所述CG资源的PUSCH先听后说LBT失败。
换言之，终端设备的MAC实体收到用于指示所述CG资源的PUSCH LBT失败的信息可以用于确定所述CG资源的道PUSCH先听后说LBT失败。
或者，在本申请的一些实施例中，终端设备MAC实体确定CG资源的PUSCH LBT失败，如未收到CG资源的PUSCH LBT成功指示时，确定所述CG资源的道PUSCH先听后说LBT失败，或者，收到物理层指示CG资源的PUSCH未传输或未成功传输时，确定所述CG资源的道PUSCH先听后说LBT失败。
在本申请的一些实施例中，若在目标时间段内收到所述调度信息，所述终端设备确定所述调度信息的接收时刻不满足前一次CG传输的处理时延；
其中所述目标时间段包括以下时间段的至少一项：
终端设备发送物理上行共享信道PUSCH的开始时刻至终端设备接收PDCCH的开始时刻之间的时间段；终端设备发送物理上行共享信道PUSCH的结束时刻至终端设备接收PDCCH的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDCCH对应的解调参考信号DMRS的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDSCH的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDSCH的开始时刻之间的时间段。
在本申请的一些实施例中，所述CG资源对应的时刻包括以下时刻中的至少一项：
终端设备发送物理上行共享信道PUSCH的结束时刻；
终端设备发送PUSCH中的上行控制信息UCI的结束时刻；
终端设备发送PUSCH对应的至少一列DMRS的结束时刻；以及
终端设备发送PUSCH的开始时刻。
在本申请的一些实施例中，所述调度信息对应的时刻包括以下时刻中的至少一项：
所述调度信息的起始时域符号位置；
所述调度信息的结束时域符号位置；
终端设备接收所述调度信息的起始时刻；以及
终端设备接收所述调度信息的结束时刻；
在本申请的一些实施例中，所述第二门限包括以下中的至少一项：
物理上行共享信道PUSCH中的上行控制信息UCI的解调时间；
PUSCH的处理时间；以及
PUSCH解调参考信号DMRS的解调时间。
在本申请的一些实施例中，所述第二门限为预配置阈值，或所述第二门限为网络设备配置的阈值。
例如，所述第二门限可以是具体的数值，其可以是预定于的数值，也可以是网络设备配置的数值，也可以是终端设备自己选择的值，还可以是终端设备在预定义的多个数 值或网络设备配置的多个数值确定或选取的数值，本申请对此不做具体限定。
例如，所述第二门限可以是终端设备在多个数值中随机选择的或基于预设准则选取的数值。
在本申请的一些实施例中，所述第二HARQ进程包括满足第二预设条件的HARQ进程。
在本申请的一些实施例中，所述第二预设条件包括以下条件中的至少一项：
所述第二HARQ进程属于为所述CG资源配置的除所述第一HARQ进程之外的HARQ进程；
所述第二HARQ进程的缓冲池为空；
所述第二HARQ进程未被DG资源占用；
所述第二HARQ进程的CG定时器未运行；以及
所述第二HARQ进程对应的CG索引与第一HARQ进程对应的CG索引相同。
当然，第二HARQ进程还可以为所述第一HARQ进程之外的任一HARQ进程，本申请对此不做具体限定。
应理解，上述第一预设条件和第二预设条件仅为示例性说明，本领域技术人员可以根据实际需求设置不同的条件，其发明构思均应属于本申请所保护的发明构思。
如图2所示，所述方法200还可包括：
S230，终端设备在所述CG资源上向网络设备发送所述CG资源上承载的数据，所述CG资源上承载的数据包括所述第二HARQ进程的信息。
换言之，网络设备向终端设备发送用于调度动态授权DG资源的调度信息；所述网络设备在所述DG资源上接收所述DG资源上承载的数据。
此外，所述网络设备在所述CG资源上接收所述CG资源上承载的数据，所述CG资源上承载的数据包括第二HARQ进程的信息。其中，所述第二HARQ进程为终端设备选择的HARQ进程。
下面就所述方法200适用于IIoT或NR-U时，对终端设备的行为进行举例说明。
终端设备接收到网络设备通过RRC配置的CG资源，其中，所述CG资源对应的CG索引(index)为1，为其配置的HARQ进程为HARQ process id1和id2。
在t1时刻，终端设备确定配置的CG资源可用，此时选择或确定的CG index1的资源，即grant1，对应的HARQ process id为1(即第一HARQ进程)。终端设备对该CG资源组包MAC PDU1，并将该MAC PDU1递交到PHY。
需要说明的是，该MAC PDU1将在t3时刻(t3>t1)通过空口PUSCH传输给网络侧。
在t2时刻(t2>t1)，终端设备收到网络设备通过C-RNTI加扰的PDCCH调度的新传数据的DG资源，其对应grant2，其指示的HARQ进程为HARQ process id 1。
需要说明的是，该grant2在空口的发送时刻为t4，其中t4<t3，或者，t4>t3,或者t4和t3时刻时域重叠。
这种情况下，所述HARQ process id 1已经被CG资源占用(HARQ process id 1为冲突的HARQ进程，即CG资源和DG资源的HARQ进程冲突时对应的HARQ)，如CG资源和DG资源的HARQ进程均为HARQ process id1，在满足上述第一预设条件时，所述终端设备将CG资源的HARQ进程从HARQ process id 1切换至HARQ process id 2，或者说所述终端设备将CG资源的HARQ进程标识设置为HARQ process id 2。
例如，所述第一预设条件可以包括以下条件中的至少一项：
所述CG资源对应的MAC PDU已经组包；
所述CG资源对应的MAC PDU已经递交到物理层；
所述CG资源对应的MAC PDU处于未传输状态；
所述CG资源对应的MAC PDU处于未完成传输状态；
所述CG资源对应的MAC PDU处于正在传输状态；
所述CG资源的优先级高于第一门限；
承载在所述CG资源上的数据高于第三门限；
承载在所述CG资源上的MAC控制元素CE的优先级高于第四门限；
所述DG资源用于传输新传数据或重传数据；
所述调度信息用于调度新传数据或重传数据；
所述调度信息为采用小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；
所述调度信息指示的传输块大小TBS和所述CG的大小不同；
所述调度信息的接收时刻不满足前一次CG传输的处理时延；以及
所述CG资源对应的时刻到调度信息对应的时刻之间的时间小于第二门限。
例如，若grant1对应的MAC PDU1已经组包且未在空口传输，且grant1或grant1中的数据的优先级高，则终端设备将选择HARQ process id 2为CG资源使用的HARQ进程，将CG资源的HARQ进程标识设置为HARQ process id 2，将CG MAC PDU1保存在HARQ process id 2的HARQ buffer中，删除HARQ process id 1的缓冲池中的数据，启动或重启对应HARQ process id 2的CG timer，停止对应HARQ process id 1的CG timer。
否则，终端设备可以按照现有协议进行操作。
即，对DG资源组包MAC PDU，并且将组包的MAC PDU存入第一HARQ进程。(例如，终端设备对DG资源对应的grant2进行组包，并将组包的MAC PDU2保存在HARQ process id 1的缓冲池中)。
例如，若grant1对应的MAC PDU1已经在空口传输或完成一次PUSCH传输，则终端设备将grant2和HARQ信息(如HARQ process id1)递交到对应的HARQ进程中，并对grant2组包MAC PDU2。
本实施例中，对CG和DG的HARQ进程冲突的场景进行了定义，避免了DG资源的优先级永远高于CG资源；当两个资源对应的HARQ进程冲突时(IIoT或NR-U场景)，即若在第一HARQ进程已经被CG资源占用时收到DCI调度的DG资源，可以通过更换CG资源的HARQ进程，将CG MAC PDU保存在新的HARQ buffer中的冲突资源，解决了HARQ进程冲突的引发的数据包丢失的问题，能够有效保证未传输的CG数据正常传输，保证了业务QoS。
下面就所述方法200适用于NR-U网络时，对终端设备的行为进行举例说明。
终端设备接收到网络设备通过RRC配置的CG资源，其中，所述CG资源对应的CG index为1，配置的HARQ进程为HARQ process id1和id2。
在t1时刻，终端设备确定配置的CG资源可用，此时，所述终端设备选择或确定的CG index1的资源，即grant1，对应的HARQ process id为1。所述终端设备对该CG资源组包MAC PDU1，并将该MAC PDU1递交到PHY。
需要说明的是，该MAC PDU1将在t2时刻(t2>t1)通过空口PUSCH传输给网络侧。
终端设备执行LBT，在t2时刻或t2时刻之前发现CG PUSCH LBT失败。终端设备的物理层将CG PUSCH LBT失败的信息及时通知给终端设备的MAC层。
在t3时刻(t3>t2)，终端设备收到网络设备通过C-RNTI加扰的PDCCH调度的新传的DG资源，对应grant2，其指示的HARQ进程为HARQ process id 1。
需要说明的是，该grant2在空口的发送时刻为t4，t4>t3。
这种情况下，HARQ process id 1已经被CG资源占用(HARQ process id 1为冲突的HARQ进程，即CG资源和DG资源的HARQ进程冲突时对应的HARQ)，如CG资源和DG资源的HARQ进程均为HARQ process id1，在满足上述第一预设条件时，所述终端设备将CG资源的HARQ进程从HARQ process id 1切换至HARQ process id 2，或者说所述终端设备将CG资源的HARQ进程标识设置为HARQ process id 2。
例如，所述第一预设条件可以包括以下条件中的至少一项：
所述CG资源对应的MAC PDU已经组包；
所述CG资源对应的MAC PDU已经递交到物理层；
所述CG资源对应的MAC PDU处于未传输状态；
所述CG资源对应的MAC PDU处于未完成传输状态；
所述CG资源对应的MAC PDU处于正在传输状态；
所述CG资源的优先级高于第一门限；
承载在所述CG资源上的数据高于第三门限；
承载在所述CG资源上的MAC控制元素CE的优先级高于第四门限；
所述DG资源用于传输新传数据或重传数据；
所述调度信息用于调度新传数据或重传数据；
所述调度信息为采用小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；
MAC实体确定所述CG资源的物理上行共享信道PUSCH先听后说LBT失败；
所述调度信息指示的传输块大小TBS和所述CG的大小不同；
所述调度信息的接收时刻不满足前一次CG传输的处理时延；以及
所述CG资源对应的时刻到调度信息对应的时刻之间的时间小于第二门限。
例如，若CG grant1的MAC PDU已经组包，并存在HARQ process id1的buffer中。当终端设备MAC收到CG grant1LBT失败指示后，收到DCI调度的grant2的新传，grant2和grant1的HARQ进程相同，都为HARQ process id1，终端设备选择HARQ process id2为第二HARQ进程，将CG资源的HARQ进程标识设置为HARQ process id 2，将保存在HARQ process id1中的CG MAC PDU放入HARQ process id2的buffer中，启动HARQ process id2的CG timer。
否则，终端设备可以按照现有协议进行操作。
即，对DG资源组包MAC PDU，并且将组包的MAC PDU存入第一HARQ进程。(例如，终端设备对DG资源对应的grant2进行组包，并将组包的MAC PDU2保存在HARQ process id 1的缓冲池中)。
例如，若grant1对应的MAC PDU1已经在空口传输或完成一次PUSCH传输，则终端设备将grant2和HARQ信息(如HARQ process id1)递交到对应的HARQ进程中，并对grant2组包MAC PDU2。
本实施例中，对CG和DG的HARQ进程冲突的场景进行了定义，避免了DG资源的优先级永远高于CG资源；当两个资源对应的HARQ进程冲突时(NR-U场景)，即若在第一HARQ进程已经被CG资源占用时收到DCI调度的DG资源，可以通过更换CG资源的HARQ进程，将CG MAC PDU保存在新的HARQ buffer中的冲突资源，解决了HARQ进程冲突的引发的数据包丢失的问题，能够有效保证未传输的CG数据正常传输，保证了业务QoS。
以上结合附图详细描述了本申请的优选实施方式，但是，本申请并不限于上述实施方式中的具体细节，在本申请的技术构思范围内，可以对本申请的技术方案进行多种简单变型，这些简单变型均属于本申请的保护范围。
例如，在上述具体实施方式中所描述的各个具体技术特征，在不矛盾的情况下，可以通过任何合适的方式进行组合，为了避免不必要的重复，本申请对各种可能的组合方式不再另行说明。
又例如，本申请的各种不同的实施方式之间也可以进行任意组合，只要其不违背本申请的思想，其同样应当视为本申请所公开的内容。
应理解，在本申请的各种方法实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文结合图2详细描述了本申请的方法实施例，下文结合图3至图7，详细描述本申请的装置实施例。
图3是本申请实施例的终端设备300的示意性框图。
请参见图3，所述终端设备300可以包括：
通信单元310，用于接收网络设备发送的用于调度动态授权DG资源的调度信息；
处理单元320，在所述DG资源使用的第一混合自动重传请求HARQ进程已被配置授权CG资源占用的情况下，所述处理单元320用于将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
在本申请的一些实施例中，所述处理单元320具体用于：
将所述CG资源使用的HARQ进程的标识设置为所述第二HARQ进程的标识。
在本申请的一些实施例中，所述处理单元320还用于执行以下行为中的至少一项：
选择所述第二HARQ进程；
将CG媒体接入控制MAC协议数据单元PDU保存至所述第二HARQ进程的HARQ缓冲池；
删除所述第一HARQ缓冲池中的数据；
启动或重启所述第二HARQ进程的CG定时器；以及
停止所述第一HARQ进程的CG定时器。
在本申请的一些实施例中，所述处理单元320具体用于：
若所述DG资源使用的第一HARQ进程已被所述CG资源占用，且满足第一预设条件，将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
在本申请的一些实施例中，所述第一预设条件包括以下中的至少一项：
所述CG资源对应的MAC PDU已经组包；
所述CG资源对应的MAC PDU已经递交到物理层；
所述CG资源对应的MAC PDU处于未传输状态；
所述CG资源对应的MAC PDU处于未完成传输状态；
所述CG资源对应的MAC PDU处于正在传输状态；
所述CG资源的优先级高于第一门限；
承载在所述CG资源上的数据高于第三门限；
承载在所述CG资源上的MAC控制元素CE的优先级高于第四门限；
所述DG资源用于传输新传数据或重传数据；
所述调度信息用于调度新传数据或重传数据；
所述调度信息为采用小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；
MAC实体确定所述CG资源的物理上行共享信道PUSCH先听后说LBT失败；
所述调度信息指示的传输块大小TBS和所述CG的大小不同；
所述调度信息的接收时刻不满足前一次CG传输的处理时延；以及
所述CG资源对应的时刻到调度信息对应的时刻之间的时间小于第二门限。
在本申请的一些实施例中，所述第一门限包括所述DG资源的优先级。
在本申请的一些实施例中，所述第三门限包括承载在所述DG资源上的数据的优先级，和/或，所述第四门限包括承载在所述DG资源上的MAC CE的优先级。
在本申请的一些实施例中，所述处理单元320还用于：
通过MAC实体收到用于指示所述CG资源的PUSCH LBT失败的信息。
在本申请的一些实施例中，所述处理单元320还用于：
若在目标时间段内收到所述调度信息，确定所述调度信息的接收时刻不满足前一次CG传输的处理时延；
其中所述目标时间段包括以下时间段的至少一项：
终端设备发送物理上行共享信道PUSCH的开始时刻至终端设备接收PDCCH的开始时刻之间的时间段；终端设备发送物理上行共享信道PUSCH的结束时刻至终端设备接收PDCCH的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDCCH对应的解调参考信号DMRS的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDSCH的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDSCH的开始时刻之间的时间段。
在本申请的一些实施例中，所述CG资源对应的时刻包括以下时刻中的至少一项：
终端设备发送物理上行共享信道PUSCH的结束时刻；
终端设备发送PUSCH中的上行控制信息UCI的结束时刻；
终端设备发送PUSCH对应的至少一列解调参考信号(Demodulation Reference Signal，DMRS)的结束时刻；以及
终端设备发送PUSCH的开始时刻。
在本申请的一些实施例中，所述调度信息对应的时刻包括以下时刻中的至少一项：
所述调度信息的起始时域符号位置；
所述调度信息的结束时域符号位置；
终端设备接收所述调度信息的起始时刻；以及
终端设备接收所述调度信息的结束时刻；
在本申请的一些实施例中，所述第二门限包括以下中的至少一项：
物理上行共享信道PUSCH中的上行控制信息UCI的解调时间；
PUSCH的处理时间；以及
PUSCH解调参考信号DMRS的解调时间。
在本申请的一些实施例中，所述第二门限为预配置阈值，或所述第二门限为网络设备配置的阈值。
在本申请的一些实施例中，所述第二HARQ进程包括满足第二预设条件的HARQ进程。
在本申请的一些实施例中，所述第二预设条件包括以下条件中的至少一项：
所述第二HARQ进程属于为所述CG资源配置的除所述第一HARQ进程之外的HARQ进程；
所述第二HARQ进程的缓冲池为空；
所述第二HARQ进程未被DG资源占用；
所述第二HARQ进程的CG定时器未运行；以及
所述第二HARQ进程对应的CG索引与第一HARQ进程对应的CG索引相同。
在本申请的一些实施例中，所述通信单元310还用于：
在所述CG资源上发送所述CG资源上承载的数据，所述CG资源上承载的数据包括所述第二HARQ进程的信息。
在本申请的一些实施例中，所述终端设备适用于工业互联网IIoT和/或新空口-非授权通信网络。
应理解，装置实施例与方法实施例可以相互对应，类似的描述可以参照方法实施例。具体地，图3所示的终端设备300可以对应于执行本申请实施例的方法200中的相应主体，并且终端设备300中的各个单元的前述和其它操作和/或功能分别为了实现图2中的各个方法中的相应流程，为了简洁，在此不再赘述。
上文从功能模块的角度描述了本申请实施例的通信设备。
应理解，该功能模块可以通过硬件形式实现，也可以通过软件形式的指令实现，还可以通过硬件和软件模块组合实现。
具体地，本申请实施例中的方法实施例的各步骤可以通过处理器中的硬件的集成逻 辑电路和/或软件形式的指令完成，结合本申请实施例公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。
可选地，软件模块可以位于随机存储器，闪存、只读存储器、可编程只读存储器、电可擦写可编程存储器、寄存器等本领域的成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法实施例中的步骤。
例如，上文涉及的处理单元和通信单元可分别由处理器和收发器实现。
图4是本申请实施例的通信设备400示意性结构图。
请参见图4，所述通信设备400可包括处理器410。
其中，处理器410可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
请继续参见图4，通信设备400还可以包括存储器420。
其中，该存储器420可以用于存储指示信息，还可以用于存储处理器410执行的代码、指令等。其中，处理器410可以从存储器420中调用并运行计算机程序，以实现本申请实施例中的方法。存储器420可以是独立于处理器410的一个单独的器件，也可以集成在处理器410中。
请继续参见图4，通信设备400还可以包括收发器430。
其中，处理器410可以控制该收发器430与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。收发器430可以包括发射机和接收机。收发器430还可以进一步包括天线，天线的数量可以为一个或多个。
应当理解，该通信设备400中的各个组件通过总线系统相连，其中，总线系统除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
还应理解，该通信设备400可为本申请实施例的终端设备，并且该通信设备400可以实现本申请实施例的各个方法中由终端设备实现的相应流程，也就是说，本申请实施例的通信设备400可对应于本申请实施例中的终端设备300，并可以对应于执行根据本申请实施例的方法200中的相应主体，为了简洁，在此不再赘述。类似地，该通信设备400可为本申请实施例的网络设备，并且该通信设备400可以实现本申请实施例的各个方法中由网络设备实现的相应流程。也就是说，本申请实施例的通信设备400可对应于本申请实施例中的网络设备400，并可以对应于执行根据本申请实施例的方法200中的相应主体，为了简洁，在此不再赘述。
此外，本申请实施例中还提供了一种芯片。
例如，芯片可能是一种集成电路芯片，具有信号的处理能力，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。所述芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。可选地，该芯片可应用到各种通信设备中，使得安装有该芯片的通信设备能够执行本申请实施例中的公开的各方法、步骤及逻辑框图。
图5是根据本申请实施例的芯片500的示意性结构图。
请参见图5，所述芯片500包括处理器510。
其中，处理器510可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
请继续参见图5，所述芯片500还可以包括存储器520。
其中，处理器510可以从存储器520中调用并运行计算机程序，以实现本申请实施例中的方法。该存储器520可以用于存储指示信息，还可以用于存储处理器510执行的代码、指令等。存储器520可以是独立于处理器510的一个单独的器件，也可以集成在处理器510中。
请继续参见图5，所述芯片500还可以包括输入接口530。
其中，处理器510可以控制该输入接口530与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
请继续参见图5，所述芯片500还可以包括输出接口540。
其中，处理器510可以控制该输出接口540与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
应理解，所述芯片500可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，也可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
还应理解，该芯片500中的各个组件通过总线系统相连，其中，总线系统除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
所述处理器可以包括但不限于：
通用处理器、数字信号处理器(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)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。
应注意，本文描述的存储器旨在包括这些和其它任意适合类型的存储器。
本申请实施例中还提供了一种计算机可读存储介质，用于存储计算机程序。该计算机可读存储介质存储一个或多个程序，该一个或多个程序包括指令，该指令当被包括多个应用程序的便携式电子设备执行时，能够使该便携式电子设备执行方法200所示实施例的方法。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例中还提供了一种计算机程序产品，包括计算机程序。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例中还提供了一种计算机程序。当该计算机程序被计算机执行时，使得计算机可以执行方法200所示实施例的方法。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
此外，本申请实施例还提供了一种通信系统，所述通信系统可以包括上述涉及的终端设备和网络设备，以形成如图1所示的通信系统100，为了简洁，在此不再赘述。需要说明的是，本文中的术语“系统”等也可以称为“网络管理架构”或者“网络系统”等。
还应当理解，在本申请实施例和所附权利要求书中使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请实施例。
例如，在本申请实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”、“上述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
所属领域的技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的范围。
如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。
例如，以上所描述的装置实施例中单元或模块或组件的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如，多个单元或模块或组件可以结合或者可以集成到另一个系统，或一些单元或模块或组件可以忽略，或不执行。
又例如，上述作为分离/显示部件说明的单元/模块/组件可以是或者也可以不是物理上分开的，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元/模块/组件来实现本申请实施例的目的。
最后，需要说明的是，上文中显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
以上内容，仅为本申请实施例的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应以权利要求的保护范围为准。

Claims (41)

  1. 一种无线通信的方法，其特征在于，包括：
    接收网络设备发送的用于调度动态授权DG资源的调度信息；
    在所述DG资源使用的第一混合自动重传请求HARQ进程已被配置授权CG资源占用的情况下，将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
  2. 根据权利要求1所述的方法，其特征在于，所述将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程，包括：
    将所述CG资源使用的HARQ进程的标识设置为所述第二HARQ进程的标识。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述DG资源使用的第一混合自动重传请求HARQ进程已被配置授权CG资源占用的情况下，所述方法还包括以下中的至少一项：
    选择所述第二HARQ进程；
    将CG媒体接入控制MAC协议数据单元PDU保存至所述第二HARQ进程的HARQ缓冲池；
    删除所述第一HARQ缓冲池中的数据；
    启动或重启所述第二HARQ进程的CG定时器；以及
    停止所述第一HARQ进程的CG定时器。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述在所述DG资源使用的第一混合自动重传请求HARQ进程已被配置授权CG资源占用的情况下，将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程，包括：
    在所述DG资源使用的第一HARQ进程已被所述CG资源占用，且满足第一预设条件的情况下，将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
  5. 根据权利要求4所述的方法，其特征在于，所述第一预设条件包括以下中的至少一项：
    所述CG资源对应的MAC PDU已经组包；
    所述CG资源对应的MAC PDU处于未传输状态；
    所述CG资源的优先级高于第一门限；
    所述调度信息为采用小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；
    MAC实体确定所述CG资源的物理上行共享信道PUSCH先听后说LBT失败；以及
    所述CG资源对应的时刻到调度信息对应的时刻之间的时间小于第二门限。
  6. 根据权利要求5所述的方法，其特征在于，所述第一门限包括所述DG资源的优先级。
  7. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    通过MAC实体收到用于指示所述CG资源的PUSCH LBT失败的信息。
  8. 根据权利要求5所述的方法，其特征在于，所述CG资源对应的时刻包括以下时刻中的至少一项：
    终端设备发送物理上行共享信道PUSCH的结束时刻；
    终端设备发送PUSCH中的上行控制信息UCI的结束时刻；
    终端设备发送PUSCH对应的至少一列解调参考信号DMRS的结束时刻；以及
    终端设备发送PUSCH的开始时刻。
  9. 根据权利要求5所述的方法，其特征在于，所述调度信息对应的时刻包括以下时刻中的至少一项：
    所述调度信息的起始时域符号位置；
    所述调度信息的结束时域符号位置；
    终端设备接收所述调度信息的起始时刻；以及
    终端设备接收所述调度信息的结束时刻。
  10. 根据权利要求5所述的方法，其特征在于，所述第二门限包括以下中的至少一项：
    物理上行共享信道PUSCH中的上行控制信息UCI的解调时间；
    PUSCH的处理时间；以及
    PUSCH解调参考信号DMRS的解调时间。
  11. 根据权利要求5所述的方法，其特征在于，所述第二门限为预配置阈值，或所述第二门限为网络设备配置的阈值。
  12. 根据权利要求5至10中任一项所述的方法，其特征在于，所述第一预设条件还包括以下中的至少一项：
    所述CG资源对应的MAC PDU已经递交到物理层；
    所述CG资源对应的MAC PDU处于未完成传输状态；
    所述CG资源对应的MAC PDU处于正在传输状态；
    承载在所述CG资源上的数据高于第三门限；
    承载在所述CG资源上的MAC控制元素CE的优先级高于第四门限；
    所述DG资源用于传输新传数据或重传数据；
    所述调度信息用于调度新传数据或重传数据；
    所述调度信息指示的传输块大小TBS和所述CG的大小不同；以及
    所述调度信息的接收时刻不满足前一次CG传输的处理时延。
  13. 根据权利要求12所述的方法，其特征在于，所述第三门限包括承载在所述DG资源上的数据的优先级，和/或，所述第四门限包括承载在所述DG资源上的MAC CE的优先级。
  14. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    若在目标时间段内收到所述调度信息，确定所述调度信息的接收时刻不满足前一次CG传输的处理时延；
    其中所述目标时间段包括以下时间段的至少一项：
    终端设备发送物理上行共享信道PUSCH的开始时刻至终端设备接收PDCCH的开始时刻之间的时间段；终端设备发送物理上行共享信道PUSCH的结束时刻至终端设备接收PDCCH的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDCCH对应的解调参考信号DMRS的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDSCH的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDSCH的开始时刻之间的时间段。
  15. 根据权利要求1至14中任一项所述的方法，其特征在于，所述第二HARQ进程包括满足第二预设条件的HARQ进程。
  16. 根据权利要求15所述的方法，其特征在于，所述第二预设条件包括以下条件中的至少一项：
    所述第二HARQ进程属于为所述CG资源配置的除所述第一HARQ进程之外的HARQ进程；
    所述第二HARQ进程的缓冲池为空；
    所述第二HARQ进程未被DG资源占用；
    所述第二HARQ进程的CG定时器未运行；以及
    所述第二HARQ进程对应的CG索引与第一HARQ进程对应的CG索引相同。
  17. 根据权利要求1至16中任一项所述的方法，其特征在于，所述方法还包括：
    在所述CG资源上发送所述CG资源上承载的数据，所述CG资源上承载的数据包括所述第二HARQ进程的信息。
  18. 根据权利要求1至17中任一项所述的方法，其特征在于，所述方法适用于工业互联网IIoT和/或新空口-非授权通信网络。
  19. 一种终端设备，其特征在于，包括：
    通信单元，用于接收网络设备发送的用于调度动态授权DG资源的调度信息；
    处理单元，在所述DG资源使用的第一混合自动重传请求HARQ进程已被配置授权CG资源占用的情况下，所述处理单元用于将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
  20. 根据权利要求19所述的终端设备，其特征在于，所述处理单元具体用于：
    将所述CG资源使用的HARQ进程的标识设置为所述第二HARQ进程的标识。
  21. 根据权利要求19或20所述的终端设备，其特征在于，所述处理单元还用于执行以下行为中的至少一项：
    选择所述第二HARQ进程；
    将CG媒体接入控制MAC协议数据单元PDU保存至所述第二HARQ进程的HARQ缓冲池；
    删除所述第一HARQ缓冲池中的数据；
    启动或重启所述第二HARQ进程的CG定时器；以及
    停止所述第一HARQ进程的CG定时器。
  22. 根据权利要求19至21中任一项所述的终端设备，其特征在于，所述处理单元具体用于：
    若所述DG资源使用的第一HARQ进程已被所述CG资源占用，且满足第一预设条件，将所述CG资源使用的HARQ进程从所述第一HARQ进程切换为第二HARQ进程。
  23. 根据权利要求22所述的终端设备，其特征在于，所述第一预设条件包括以下中的至少一项：
    所述CG资源对应的MAC PDU已经组包；
    所述CG资源对应的MAC PDU处于未传输状态；
    所述CG资源的优先级高于第一门限；
    所述调度信息为采用小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；
    MAC实体确定所述CG资源的物理上行共享信道PUSCH先听后说LBT失败；以及
    所述CG资源对应的时刻到调度信息对应的时刻之间的时间小于第二门限。
  24. 根据权利要求23所述的终端设备，其特征在于，所述第一门限包括所述DG资源的优先级。
  25. 根据权利要求23所述的终端设备，其特征在于，所述处理单元还用于：
    通过MAC实体收到用于指示所述CG资源的PUSCH LBT失败的信息。
  26. 根据权利要求23所述的终端设备，其特征在于，所述CG资源对应的时刻包括以下时刻中的至少一项：
    终端设备发送物理上行共享信道PUSCH的结束时刻；
    终端设备发送PUSCH中的上行控制信息UCI的结束时刻；
    终端设备发送PUSCH对应的至少一列DMRS的结束时刻；以及
    终端设备发送PUSCH的开始时刻。
  27. 根据权利要求23所述的终端设备，其特征在于，所述调度信息对应的时刻包括以下时刻中的至少一项：
    所述调度信息的起始时域符号位置；
    所述调度信息的结束时域符号位置；
    终端设备接收所述调度信息的起始时刻；以及
    终端设备接收所述调度信息的结束时刻。
  28. 根据权利要求23所述的终端设备，其特征在于，所述第二门限包括以下中的至少一项：
    物理上行共享信道PUSCH中的上行控制信息UCI的解调时间；
    PUSCH的处理时间；以及
    PUSCH解调参考信号DMRS的解调时间。
  29. 根据权利要求23所述的终端设备，其特征在于，所述第二门限为预配置阈值，或所述第二门限为网络设备配置的阈值。
  30. 根据权利要求23至29中任一项所述的终端设备，其特征在于，所述第一预设条件还包括以下中的至少一项：
    所述CG资源对应的MAC PDU已经递交到物理层；
    所述CG资源对应的MAC PDU处于未完成传输状态；
    所述CG资源对应的MAC PDU处于正在传输状态；
    承载在所述CG资源上的数据高于第三门限；
    承载在所述CG资源上的MAC控制元素CE的优先级高于第四门限；
    所述DG资源用于传输新传数据或重传数据；
    所述调度信息用于调度新传数据或重传数据；
    所述调度信息指示的传输块大小TBS和所述CG的大小不同；以及
    所述调度信息的接收时刻不满足前一次CG传输的处理时延。
  31. 根据权利要求30所述的终端设备，其特征在于，所述第三门限包括承载在所述DG资源上的数据的优先级，和/或，所述第四门限包括承载在所述DG资源上的MAC CE的优先级。
  32. 根据权利要求30所述的终端设备，其特征在于，所述处理单元还用于：
    若在目标时间段内收到所述调度信息，确定所述调度信息的接收时刻不满足前一次CG传输的处理时延；
    其中所述目标时间段包括以下时间段的至少一项：
    终端设备发送物理上行共享信道PUSCH的开始时刻至终端设备接收PDCCH的开始时刻之间的时间段；终端设备发送物理上行共享信道PUSCH的结束时刻至终端设备接收PDCCH的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDCCH对应的解调参考信号DMRS的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDSCH的结束时刻之间的时间段；终端设备发送PUSCH中的上行控制信息UCI的结束时刻至终端设备接收PDSCH的开始时刻之间的时间段。
  33. 根据权利要求19至32中任一项所述的终端设备，其特征在于，所述第二HARQ进程包括满足第二预设条件的HARQ进程。
  34. 根据权利要求33所述的终端设备，其特征在于，所述第二预设条件包括以下条件中的至少一项：
    所述第二HARQ进程属于为所述CG资源配置的除所述第一HARQ进程之外的HARQ进程；
    所述第二HARQ进程的缓冲池为空；
    所述第二HARQ进程未被DG资源占用；
    所述第二HARQ进程的CG定时器未运行；以及
    所述第二HARQ进程对应的CG索引与第一HARQ进程对应的CG索引相同。
  35. 根据权利要求19至34中任一项所述的终端设备，其特征在于，所述通信单元还用于：
    在所述CG资源上发送所述CG资源上承载的数据，所述CG资源上承载的数据包括所述第二HARQ进程的信息。
  36. 根据权利要求19至35中任一项所述的终端设备，其特征在于，所述终端设备适用于工业互联网IIoT和/或新空口-非授权通信网络。
  37. 一种终端设备，其特征在于，包括：
    处理器、存储器和收发器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行权利要求1至18中任一项所述的方法。
  38. 一种芯片，其特征在于，包括：
    处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至18中任一项所述的方法。
  39. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至18中任一项所述的方法。
  40. 一种计算机程序产品，其特征在于，包括计算机程序指令，所述计算机程序指令使得计算机执行如权利要求1至18中任一项所述的方法。
  41. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至18中任一项所述的方法。
PCT/CN2019/107595 2019-09-24 2019-09-24 无线通信的方法和设备 Ceased WO2021056209A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/107595 WO2021056209A1 (zh) 2019-09-24 2019-09-24 无线通信的方法和设备
CN201980095275.9A CN113647182B (zh) 2019-09-24 2019-09-24 无线通信的方法和设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/107595 WO2021056209A1 (zh) 2019-09-24 2019-09-24 无线通信的方法和设备

Publications (1)

Publication Number Publication Date
WO2021056209A1 true WO2021056209A1 (zh) 2021-04-01

Family

ID=75165581

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/107595 Ceased WO2021056209A1 (zh) 2019-09-24 2019-09-24 无线通信的方法和设备

Country Status (2)

Country Link
CN (1) CN113647182B (zh)
WO (1) WO2021056209A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022252163A1 (zh) * 2021-06-02 2022-12-08 Oppo广东移动通信有限公司 数据传输方法及相关装置
WO2024159547A1 (zh) * 2023-02-03 2024-08-08 北京小米移动软件有限公司 自适应处理传输时机的方法、装置和计算机存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119014084A (zh) * 2022-09-29 2024-11-22 Oppo广东移动通信有限公司 用于侧行通信的方法及终端设备
WO2024119448A1 (zh) * 2022-12-08 2024-06-13 Oppo广东移动通信有限公司 用于无线传输的处理方法、装置、设备、存储介质及产品
CN118784164A (zh) * 2023-04-07 2024-10-15 华为技术有限公司 Harq进程标识配置方法、装置、系统、介质及程序
WO2025236474A1 (en) * 2024-05-15 2025-11-20 Huawei Technologies Co., Ltd. Method, apparatus and system for multiplexing transmission in wireless communication system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108541360A (zh) * 2015-12-07 2018-09-14 康普技术有限责任公司 控制无线电接入网络中的数据传输
WO2018211364A1 (en) * 2017-05-15 2018-11-22 Telefonaktiebolaget Lm Ericsson (Publ) Methods of sharing harq process ids between semi-persistent scheduling and dynamic grants
US20190075589A1 (en) * 2017-09-07 2019-03-07 Comcast Cable Communications, Llc Configured Grant and Dynamic Grant Transmission
CN110115061A (zh) * 2016-12-28 2019-08-09 株式会社Ntt都科摩 用户装置及数据发送方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109586854B (zh) * 2017-09-28 2020-11-17 华为技术有限公司 数据传输方法及装置
US10904904B2 (en) * 2018-01-11 2021-01-26 Telefonaktiebolaget Lm Ericsson (Publ) Methods and devices for controlling override of configured grant
CN110167180B (zh) * 2018-02-11 2021-04-27 维沃移动通信有限公司 一种传输方法和设备
US10756852B2 (en) * 2018-02-15 2020-08-25 Ofinno, Llc Control element trigger

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108541360A (zh) * 2015-12-07 2018-09-14 康普技术有限责任公司 控制无线电接入网络中的数据传输
CN110115061A (zh) * 2016-12-28 2019-08-09 株式会社Ntt都科摩 用户装置及数据发送方法
WO2018211364A1 (en) * 2017-05-15 2018-11-22 Telefonaktiebolaget Lm Ericsson (Publ) Methods of sharing harq process ids between semi-persistent scheduling and dynamic grants
US20190075589A1 (en) * 2017-09-07 2019-03-07 Comcast Cable Communications, Llc Configured Grant and Dynamic Grant Transmission

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "Leftover issues for CG/CG and CG/DG prioritization", 3GPP DRAFT; R2-1905748 LEFTOVER ISSUES FOR CGCG AND CGDG PRIORITIZATION, vol. RAN WG2, 3 May 2019 (2019-05-03), Reno USA, pages 1 - 4, XP051710102 *
CATT: "Prioritization rules for CG&DG and CG&CG collisions", 3GPP DRAFT; R2-1903143-PRIORITIZATION RULES FOR CG&DG AND CG&CG COLLISIONS, vol. RAN WG2, 29 March 2019 (2019-03-29), Xi’an, China, pages 1 - 5, XP051692421 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022252163A1 (zh) * 2021-06-02 2022-12-08 Oppo广东移动通信有限公司 数据传输方法及相关装置
US12028852B2 (en) 2021-06-02 2024-07-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method and related apparatuses
WO2024159547A1 (zh) * 2023-02-03 2024-08-08 北京小米移动软件有限公司 自适应处理传输时机的方法、装置和计算机存储介质

Also Published As

Publication number Publication date
CN113647182B (zh) 2024-05-31
CN113647182A (zh) 2021-11-12

Similar Documents

Publication Publication Date Title
US11589384B2 (en) Data transmission method, terminal device, and network device
CN113647182B (zh) 无线通信的方法和设备
CN113518469B (zh) 指示信道接入的方法及装置
US20250056612A1 (en) Resource determining method and apparatus
WO2021035535A1 (zh) 无线通信的方法、终端设备和网络设备
CN113647171B (zh) 无线通信的方法和设备
US11528714B2 (en) Data transmission method and apparatus
US20230269036A1 (en) Communication method and apparatus
CN109996334A (zh) 信息指示方法、终端设备及网络设备
CN115843115A (zh) 侧行通信的方法及装置
CN116261220A (zh) Cg配置方法、装置、设备及介质
US20250227726A1 (en) Communication method, apparatus, and system
CN116491205A (zh) 上行传输方法、装置、终端及存储介质
CN117377097A (zh) 信息传输方法及装置
WO2021026841A1 (zh) 调度请求传输的方法和设备
WO2020192602A1 (zh) 重传数据的发送方法及数据重传资源的发送方法、装置、存储介质和电子装置
WO2022087836A1 (zh) 传输方法和终端设备
CN109600860B (zh) 随机接入方法、装置、设备、存储介质和程序产品
TW202037126A (zh) 確定上行控制訊息傳輸資源個數的方法、裝置及程式
WO2020124534A1 (zh) 数据传输的方法和设备
CN114731666B (zh) 传输资源确定方法及相关装置
CN115836574B (zh) 上行传输控制方法、装置、终端及存储介质
WO2022021411A1 (zh) Harq进程确定方法、装置、设备及介质
CN115915462A (zh) 信道接入优先级capc的确定方法和网络侧设备
WO2021163858A1 (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: 19946475

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19946475

Country of ref document: EP

Kind code of ref document: A1