Method, apparatus and computer storage medium for adaptive handling of transmission occasions

Abstract

A method, device and computer storage medium for adaptively processing a transmission occasion, the method comprising: receiving configuration information of at least one configured grant (CG) resource sent by a network device; determining a physical uplink shared channel (PUSCH) transmission occasion according to the configuration information; and adaptively processing the PUSCH transmission occasion in a case where the CG resource is not suitable for a first service. The present disclosure can meet transmission requirements of different services by adaptively processing the PUSCH transmission occasion.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method, apparatus, and computer storage medium for adaptively processing transmission timing. Background Technology

[0002] In wireless communication systems, to reduce uplink latency, the 3rd Generation Partnership Project (3GPP) introduced uplink unlicensed scheduling. The resources used in uplink unlicensed scheduling can be configured grant (CG) resources. For example, CG resources can include configured grant Physical Uplink Shared Channel (PUSCH) transmission resources with a CG. Network devices can pre-configure the CG resources used for uplink transmission for terminal devices. Terminal devices can then autonomously use these CG resources for uplink transmission without requiring scheduling from the network device, thereby saving scheduling time and reducing uplink latency. Summary of the Invention

[0003] To overcome the problems existing in related technologies, this disclosure provides a method, apparatus and computer storage medium for adaptively processing transmission timing.

[0004] According to a first aspect of the present disclosure, a method for adaptively processing transmission timing is provided, executed by a terminal device, the method comprising:

[0005] Receive configuration information for at least one set of authorized CG resources sent by the network device;

[0006] Determine the timing of Physical Uplink Shared Channel (PUSCH) transmission based on the configuration information;

[0007] When CG resources are not compatible with the primary service, the timing of PUSCH transmission is adaptively adjusted.

[0008] According to a second aspect of the present disclosure, a method for adaptively processing transmission timing is provided, performed by a network device, the method comprising:

[0009] At least one set of configuration information for authorized CG resources is sent to the terminal device. The configuration information is used by the terminal device to determine the timing of Physical Uplink Shared Channel (PUSCH) transmission and to adaptively process the PUSCH transmission timing if the CG resources are not compatible with the first service.

[0010] According to a third aspect of the present disclosure, a terminal device is provided, comprising:

[0011] The receiving module is configured to receive configuration information for at least one set of authorized CG resources sent by the network device;

[0012] The processing module is configured to determine the timing of PUSCH transmission based on configuration information; and to adaptively process the PUSCH transmission timing when CG resources are not compatible with the first service.

[0013] According to a fourth aspect of the present disclosure, a network device is provided, comprising:

[0014] The sending module is configured with at least one set of configuration information for authorized CG resources. The configuration information is used by the terminal device to determine the PUSCH transmission timing and to adaptively handle the PUSCH transmission timing when the CG resources are not compatible with the first service.

[0015] According to a fifth aspect of the present disclosure, a communication device is provided, comprising:

[0016] processor;

[0017] Memory used to store processor-executable instructions;

[0018] The processor is configured to execute the executable instructions to implement the adaptive processing transmission timing method provided in the first aspect of this disclosure.

[0019] According to a sixth aspect of the present disclosure, a communication device is provided, comprising:

[0020] processor;

[0021] Memory used to store processor-executable instructions;

[0022] The processor is configured to execute the executable instructions to implement the adaptive processing transmission timing method provided in the second aspect of this disclosure.

[0023] According to a seventh aspect of the present disclosure, a communication system is provided, comprising:

[0024] A terminal device that performs the adaptive processing transmission timing method provided in the first aspect of this disclosure;

[0025] A network device that performs the adaptive processing transmission timing method provided in the second aspect of this disclosure.

[0026] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the steps of the method provided in the first or second aspect of the present disclosure.

[0027] The technical solution provided by the embodiments of this disclosure can have the following beneficial effects: by receiving at least one set of configuration information of authorized CG resources sent by a network device, and on this basis, determining the transmission timing of the Physical Uplink Shared Channel (PUSCH) according to the configuration information, in the case where the CG resources are not compatible with the first service, this disclosure can adaptively process the PUSCH transmission timing, thus meeting the transmission requirements of different services and making full use of time and frequency resources.

[0028] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0029] The above and / or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which:

[0030] Figure 1 This is a schematic diagram of a communication system according to one embodiment.

[0031] Figure 2 This is an example diagram illustrating the relationship between XR services and PUSCH transmission timing according to one embodiment.

[0032] Figure 3 This is a flowchart illustrating an adaptive method for processing transmission timing according to one embodiment.

[0033] Figure 4 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment.

[0034] Figure 5 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment.

[0035] Figure 6 This is a flowchart illustrating an adaptive method for processing transmission timing according to yet another embodiment.

[0036] Figure 7 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment.

[0037] Figure 8 This is a flowchart illustrating an adaptive method for processing transmission timing according to yet another embodiment.

[0038] Figure 9This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment.

[0039] Figure 10 This is an example diagram illustrating an adaptive processing method for transmission timing that utilizes an extension of the PUSCH transmission timing, according to yet another embodiment.

[0040] Figure 11 This is another example diagram illustrating an adaptive processing method for transmission timing, according to yet another embodiment, which utilizes an extension of the PUSCH transmission timing.

[0041] Figure 12 This is a flowchart illustrating an adaptive method for processing transmission timing according to yet another embodiment.

[0042] Figure 13 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment.

[0043] Figure 14 This is a flowchart illustrating an adaptive method for processing transmission timing according to yet another embodiment.

[0044] Figure 15 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment.

[0045] Figure 16 This is an example diagram illustrating the PUSCH transmission timing within an uplink unlicensed transmission cycle in an adaptive processing transmission timing method according to another embodiment.

[0046] Figure 17 This is an example diagram of a sub-timing in the PUSCH transmission timing in an adaptive processing transmission timing method according to another embodiment.

[0047] Figure 18 This is a flowchart illustrating an adaptive method for processing transmission timing according to yet another embodiment.

[0048] Figure 19 This is a flowchart illustrating an adaptive method for processing transmission timing according to one embodiment.

[0049] Figure 20 This is a block diagram illustrating a terminal device according to one embodiment.

[0050] Figure 21 This is a block diagram of a network device according to one embodiment.

[0051] Figure 22 This is a block diagram illustrating a communication device according to one embodiment.

[0052] Figure 23 This is a block diagram illustrating a communication device according to one embodiment. Detailed Implementation

[0053] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0054] It should be noted that all actions involving the acquisition of signals, information, or data in this disclosure are carried out in compliance with the relevant data protection laws and policies of the country where the location is situated, and with authorization from the owner of the relevant device.

[0055] In the description of this disclosure, terms such as "first" and "second" are used to distinguish similar objects and should not be construed as indicating a specific order or sequence. Furthermore, unless otherwise stated, in the description with reference to the accompanying drawings, the same reference numerals in different drawings denote the same elements.

[0056] In the description of this disclosure, unless otherwise stated, "multiple" means two or more, and other quantifiers are similar; "at least one," "one or more," or similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one can represent any number; as another example, one or more of a, b, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple; "and / or" is a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural.

[0057] Although operations or steps are described in a specific order in the accompanying drawings in the embodiments of this disclosure, it should not be construed as requiring these operations or steps to be performed in the specific order or serial order shown, or requiring all of the shown operations or steps to be performed to obtain the desired result. In the embodiments of this disclosure, these operations or steps may be performed serially; they may be performed in parallel; or a portion of these operations or steps may be performed.

[0058] To facilitate understanding, let me first introduce the terminology used in this disclosure.

[0059] 1) Physical Uplink Shared Channel (PUSCH);

[0060] PUSCH is used to carry uplink higher-layer / physical layer control signaling and user data.

[0061] 2) Downlink Control Information (DCI);

[0062] DCI is control information transmitted on the Physical Downlink Control Channel (PDCCH) and related to the Physical Uplink and Downlink Shared Channels (PUSCH, PDSCH). The DCI control signaling includes resource block allocation information and modulation scheme, among other related content.

[0063] 3) Configure authorized resources / uplink unauthorized resources;

[0064] For ease of description, uplink unlicensed resource configuration will be referred to as CG resource configuration below. During uplink communication between a UE (User Equipment) and a network device, the network device needs to authorize uplink resources to the UE, and the UE can use the uplink resources to transmit data to the network device. However, in uplink unlicensed transmission technology, the UE can use uplink resources shared by multiple UEs for uplink transmission without requesting uplink resources from the network device or authorizing uplink resources from the network device.

[0065] There are two unlicensed transmission methods on the PUSCH: one is that the network device configures all parameters of the CG resource configuration to the UE via higher-layer signaling; the other is that the network device indicates the activation of the CG resource configuration in dynamic signaling, where dynamic signaling can be DCI signaling. For example, in the unlicensed transmission process, some parameters are configured to the UE by the network device via higher-layer signaling, while other scheduling-related CG resources are configured to the UE by the network device activating DCI. Here, the higher-layer signaling can be RRC (Radio Resource Control) signaling.

[0066] 4) Band Width Part (BWP);

[0067] BWP is a subset of the UE channel bandwidth. It flexibly adjusts the receiving and transmitting bandwidth of the terminal device through adaptive bandwidth adjustment in NR (New Radio), ensuring that the receiving and transmitting bandwidth of the terminal device does not need to be as large as the cell bandwidth. A terminal device can only activate one UL (uplink) BWP and one DL (downlink) BWP simultaneously. Each BWP can be configured with one SCS (Sub-Carrier Spacing).

[0068] 5) RRC;

[0069] RRC is a system for managing, controlling, and scheduling wireless resources through specific strategies and methods.

[0070] In related technologies, a BWP can be configured and activated with up to 12 sets of uplink unlicensed transport configurations, each of which can be identified by an index.

[0071] XR (Extended Reality) services utilize technologies such as computers and artificial intelligence, along with wearable devices, to create a combined real and virtual environment that allows for human-computer interaction. It includes AR (Augmented Reality), VR (Virtual Reality), and MR (Mixed Reality) services. XR services are characterized by their cyclical nature, high throughput requirements, and low latency requirements.

[0072] The implementation environment of the embodiments of this disclosure is described below.

[0073] The technical solutions of this disclosure can be applied to various communication systems. These communication systems may include one or more of 4G (4th Generation), 5G (5th Generation), and other future wireless communication systems (such as 6G). The communication system may also include one or more of the following: Public Land Mobile Network (PLMN), Device-to-Device (D2D) communication systems, Machine-to-Machine (M2M) communication systems, Internet of Things (IoT) communication systems, Vehicle-to-Everything (V2X) communication systems, or other communication systems.

[0074] Figure 1This is a schematic diagram illustrating a communication system according to an exemplary embodiment, such as... Figure 1 As shown, the communication system may include terminal device 11 and network device 12. This communication system can be used to support 4G network access technologies, such as Long Term Evolution (LTE) access technology, or 5G network access technologies, such as New Radio Access Technology (New RAT), or other future wireless communication technologies. It should be noted that in this communication system, the number of network device 12 and terminal device 11 can both be one or more. Figure 1 The number of network devices 12 and terminal devices 11 in the communication system shown is merely an adaptive example, and this disclosure does not limit this.

[0075] Figure 1 The network device 12 can be used to support the access of the terminal device 11. For example, the network device 12 can be an evolved Node B (eNB or eNodeB) in LTE; the network device 12 can also be a next-generation Node B (gNB or gNodeB) in 5G network; the network device 12 can also be a radio access network (NG-RAN) device in 5G network; the network device 12 can also be a base station, broadband network gateway (BNG), aggregation switch, or non-3GPP (3rd Generation Partnership Project) access device in a future evolved Public Land Mobile Network (PLMN).

[0076] Optionally, the network device 12 in this disclosure embodiment may include various forms of base stations, such as: macro base stations, micro base stations (also known as small stations), relay stations, access points, 5G base stations or future base stations, satellites, Transmitting and Receiving Points (TRPs), Transmitting Points (TPs), mobile switching centers, and devices that perform base station functions in device-to-device (D2D), machine-to-machine (M2M), Internet of Things (IoT), vehicle-to-everything (V2X), or other communications. This disclosure embodiment does not specifically limit these types of devices. For ease of description, in all embodiments of this disclosure, the apparatus providing wireless communication functions for the terminal device 11 is collectively referred to as network device 12 or base station.

[0077] Figure 1 The terminal device 11 can be an electronic device that provides voice or data connectivity. For example, the terminal device 11 can also be called User Equipment (UE), Subscriber Unit, Mobile Station, Station, Terminal, etc. For example, the terminal device 11 may include smartphones, smart wearable devices, smart speakers, smart tablets, wireless modems, Wireless Local Loop (WLL) stations, PDAs (Personal Digital Assistants), CPEs (Customer Premise Equipment), etc. With the development of wireless communication technology, any device that can access a communication system, communicate with network devices in a communication system, communicate with other objects through a communication system, or allow direct communication between two or more devices can be the terminal device 11 in this embodiment. For example, terminals and vehicles in intelligent transportation, home appliances in smart homes, electricity meter reading instruments, voltage monitoring instruments, environmental monitoring instruments in smart grids, video monitoring instruments in smart security networks, cash registers, etc. In this embodiment of the disclosure, terminal device 11 can communicate with network device 12. Multiple terminal devices 11 can also communicate with each other. Terminal device 11 can be statically fixed or mobile, and this disclosure does not limit this.

[0078] In some embodiments of this disclosure, the terminal device and network device described above can support uplink unlicensed scheduling. The resources used for uplink unlicensed scheduling can be configured licensed CG resources. The network device can pre-configure the CG resources used for uplink transmission for the terminal device. The terminal device can autonomously use the CG resources for uplink transmission without the need for scheduling by the network device, thereby saving scheduling time and reducing uplink service latency.

[0079] Due to the flexibility of XR services, there may be a mismatch between the XR service and the configured grant push-ch occasion (CG push-hoccasion) resources when transmitting the time-domain resources required for XR service transmission. The first scenario is where the CG push-ch occasion resources can meet the transmission requirements of the XR service and there are idle resources. This situation leads to resource waste, as detailed below. Figure 2 As shown in 101; the second scenario is that the CG PUSCH occasion resources cannot fully meet the transmission requirements of XR services, meaning that additional resources are needed outside of the CG PUSCH occasion to transmit XR services. This situation will increase the latency of XR service transmission, as detailed below. Figure 2 102 shown.

[0080] Figure 3 This is a flowchart illustrating an adaptive method for processing transmission timing according to one embodiment. Figure 3 As shown, this method can be executed by a terminal device and includes the following steps.

[0081] In step S110, at least one set of configuration information for authorized CG resources is received from the network device.

[0082] In some implementations, the CG resource can be a transmission resource, through which the terminal device can transmit data to the network device. The CG resource is the transmission resource required by the terminal device when performing uplink transmission.

[0083] In this embodiment of the disclosure, the terminal device can receive at least one set of configuration information for configuring CG resources sent by the network device. The configuration information may include at least one of the following: time domain offset, FDRA (Frequency Domain Resource Allocation) field, TDRA (Time Domain Resource Allocation) field, periodicity, periodicityExt, physical layer priority index (phy-PriorityIndex), resource block size (rbg-Size), uplink shared channel retransmission type indicator (pusch-RepTypeIndicator), repeated redundant version (repK-RV), repK (repetition count), resource allocation (resourceAllocation), transmission timing offset, transmission timing idle indicator, number of transmission timings, time reference system frame number (timeReferenceSFN), frequency hopping configuration (frequencyHopping), frequency hopping configuration offset (frequencyHoppingOffset), modulation and coding scheme (MCS), and number of HARQ (Hybrid Automatic Repeat Request) processes.

[0084] In some implementations, the network device can send configuration information to the terminal device via higher-layer signaling. For example, the terminal device can receive RRC signaling carrying configuration information sent by the network device. Optionally, the terminal device can also receive configuration information sent by the network device via dynamic signaling. For example, the terminal device can receive DCI signaling carrying configuration information sent by the network device.

[0085] In some implementations, CG resources may include at least one of the following information: uplink unlicensed transmission period, number of HARQ (Hybrid Automatic Repeat Request) processes, power control, number of repetitions (repK), redundant versions of the repetitions (repK-RV), time-domain resources, frequency-domain resources, modulation and coding scheme, antenna ports, channel sounding reference signal (SRS) resource indication, demodulation reference signal (DM-RS), and PUSCH transmission timing, etc. Here, the uplink unlicensed transmission period can be configured by higher-layer signaling and can support up to 14*40960 symbols.

[0086] In some implementations, the network device can configure at least one set of CG resources for the terminal device on a BWP via RRC signaling. The terminal device can perform uplink transmission within the uplink unlicensed transmission period configured by the network device, that is, the terminal device can perform uplink transmission at the PUSCH transmission time configured in the CG resources.

[0087] In other implementations, the network device can configure partial information of at least one set of CG resources for the terminal device on a BWP via RRC signaling, and then notify the terminal device of the remaining resources of the CG resource via dynamic signaling. After the network device activates the CG resource via dynamic signaling, the terminal device can perform uplink transmission within the period configured by the network device.

[0088] In step S120, the timing of Physical Uplink Shared Channel (PUSCH) transmission is determined based on the configuration information.

[0089] In some implementations, the terminal device can determine the PUSCH transmission timing based on the configuration information. Specifically, the terminal device can determine the PUSCH transmission timing based on the parameters in the configuration information. Here, the PUSCH transmission timing can be a configured authorized PUSCH transmission timing (CG PUSCH occasion).

[0090] In some implementations, the PUSCH transmission timing determined based on the configuration information may include at least one of the following: time domain resources corresponding to the uplink unlicensed transmission period, frequency domain resources corresponding to the uplink unlicensed transmission period, non-idle time domain resources corresponding to the uplink unlicensed transmission period, non-idle frequency domain resources corresponding to the uplink unlicensed transmission period, idle time domain resources corresponding to the uplink unlicensed transmission period, idle frequency domain resources corresponding to the uplink unlicensed transmission period, radio frames corresponding to the uplink unlicensed transmission period, resource windows corresponding to the uplink unlicensed transmission period, time slots corresponding to the uplink unlicensed transmission period, continuous time domain symbols corresponding to the uplink unlicensed transmission period, and non-continuous time domain symbols corresponding to the uplink unlicensed transmission period.

[0091] In step S130, if the CG resources are not compatible with the first service, the timing of PUSCH transmission is adaptively processed.

[0092] As an optional approach, after receiving configuration information for at least one set of CG resources from the terminal device, the terminal device can determine whether the CG resources are compatible with the first service. Specifically, the terminal device can determine whether the PUSCH transmission timing resource in the CG resources is compatible with the first service. If it is determined that the CG resources are not compatible with the first service, the terminal device can adaptively handle the PUSCH transmission timing.

[0093] Here, the mismatch between CG resources and the first service can mean that the CG resources cannot meet the transmission requirements of the first service. For example, the inability of CG resources to meet the transmission requirements of the first service can mean that the PUSCH transmission timing resources cannot meet the transmission requirements of the XR service, that is, additional resources are required outside of the PUSCH transmission timing.

[0094] Optionally, the mismatch between CG resources and the first service can also be that the CG resources can satisfy the transmission of the first service, but there are idle resources, which would lead to a waste of idle resources. Therefore, in this embodiment of the disclosure, the mismatch between CG resources and the first service can be that the CG resources can satisfy the transmission of the first service, and there are no idle resources.

[0095] This disclosure specifies that by receiving configuration information of at least one set of CG resources sent by a network device, and determining the PUSCH transmission timing based on the configuration information, this disclosure can adaptively process the PUSCH transmission timing when the CG resources are not compatible with the first service, thereby meeting the transmission requirements of different services and making full use of time and frequency resources.

[0096] Figure 4 This is a flowchart illustrating an adaptive method for handling transmission timing according to another embodiment. (See attached flowchart.) Figure 4 As shown, this method can be executed by a terminal device and includes the following steps.

[0097] In step S210, at least one set of configuration information for authorized CG resources is received from the network device.

[0098] In step S220, the timing of Physical Uplink Shared Channel (PUSCH) transmission is determined based on the configuration information.

[0099] The specific implementation methods of steps S210 and S220 have been described in detail in the above embodiments, and will not be repeated here.

[0100] In step S230, if it is determined that the CG resource does not meet the first service transmission requirement, the PUSCH transmission timing is adaptively processed.

[0101] As an alternative approach, if it is determined that the CG resources do not meet the transmission requirements of the first service, the timing of PUSCH transmission can be adaptively adjusted.

[0102] In this embodiment of the disclosure, the failure of CG resources to meet the transmission requirements of the first service may be due to the first service requiring transmission being outside the range of the PUSCH transmission timing. For example, the failure of CG resources to meet the transmission requirements of the first service may be due to the PUSCH transmission timing resources not being able to fully meet the transmission requirements of the first service, the first service requiring transmission being outside the range of the PUSCH transmission timing, the uplink unlicensed transmission resources based on the first MCS being lower than the resources corresponding to the PUSCH transmission timing, the channel sounding reference signal resources not being able to meet the transmission requirements of the first service, the PUSCH transmission timing resources not being able to fully meet the retransmission requirements of the first service, or at least one first service requiring retransmission being outside the range of the PUSCH transmission timing, etc.

[0103] As described above, CG resources can include time-domain resources, frequency-domain resources, etc. After receiving configuration information of at least one set of CG resources sent by the network device, the terminal device can also first obtain the time-domain resources, frequency-domain resources, etc. corresponding to the CG resource.

[0104] In one specific implementation, the terminal device can determine whether the time-domain resources corresponding to the CG resource are less than the time-domain resources required for the first service transmission. If it is determined that the time-domain resources corresponding to the CG resource are less than the time-domain resources required for the first service transmission, the terminal device can adaptively process the PUSCH transmission timing.

[0105] In another specific implementation, the terminal device can determine whether the frequency domain resources corresponding to the CG resources are less than the frequency domain resources required for the first service transmission. If it is determined that the frequency domain resources corresponding to the CG resources are less than the frequency domain resources required for the first service transmission, the terminal device can adaptively process the PUSCH transmission timing.

[0106] In another specific implementation, the terminal device can determine whether the time-domain resources corresponding to the CG resources are less than the time-domain resources required for the first service transmission, and whether the frequency-domain resources corresponding to the CG resources are less than the frequency-domain resources required for the first service transmission. If it is determined that the time-domain resources corresponding to the CG resources are less than the time-domain resources required for the first service transmission, and the frequency-domain resources corresponding to the CG resources are determined to be less than the frequency-domain resources required for the first service transmission, the terminal device can adaptively process the PUSCH transmission timing.

[0107] In another specific implementation, when the first service arrives, the terminal device can also determine whether the remaining time-domain resources of the CG resource are less than the time-domain resources required for the transmission of the first service. If it is determined that the remaining time-domain resources of the CG resource are less than the time-domain resources required for the transmission of the first service, the terminal device can adaptively process the PUSCH transmission timing.

[0108] Optionally, when the first service arrives, the terminal device can also determine whether the remaining frequency domain resources of the CG resource are less than the frequency domain resources required for the transmission of the first service. If it is determined that the remaining frequency domain resources of the CG resource are less than the frequency domain resources required for the transmission of the first service, the terminal device can adaptively process the PUSCH transmission timing.

[0109] In another specific implementation, upon arrival of the first service, the terminal device can also determine whether the quotient of the remaining time-domain resources of the CG resource and the time-domain resources corresponding to the entire CG resource is less than a first threshold. If it is determined that the quotient of the remaining time-domain resources of the CG resource and the time-domain resources corresponding to the entire CG resource is less than the first threshold, the terminal device can adaptively process the PUSCH transmission timing. Here, the first threshold can be configured by the network device to the terminal device, reported by the terminal device to the network device, or predefined by the protocol. The value range of the first threshold can be 0 to 1.

[0110] Optionally, upon arrival of the first service, the terminal device can also determine whether the quotient of the remaining frequency domain resources of the CG resource and the frequency domain resources corresponding to the entire CG resource is less than a second threshold. If it is determined that the quotient of the remaining frequency domain resources of the CG resource and the frequency domain resources corresponding to the entire CG resource is less than the second threshold, the terminal device can adaptively process the PUSCH transmission timing. The acquisition of the second threshold is similar to that of the first threshold, and will not be elaborated here.

[0111] This disclosure embodiment can also determine whether the CG resource meets the first service transmission requirement in other ways. The specific method or parameter used to determine whether the CG resource meets the first service transmission requirement is not explicitly limited here, and can be selected according to the actual situation.

[0112] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with other embodiments or implementation methods and various optional solutions related to adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0113] This disclosure specifies that if a terminal device determines that CG resources cannot meet the transmission requirements of the first service, it can adaptively process the PUSCH transmission timing, thereby meeting the low latency and high throughput requirements of the first service.

[0114] Figure 5 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment. For example... Figure 5 As shown, this method can be executed by a terminal device and includes the following steps.

[0115] In step S310, at least one set of configuration information for authorized CG resources is received from the network device.

[0116] In step S320, the timing of Physical Uplink Shared Channel (PUSCH) transmission is determined based on the configuration information.

[0117] The specific implementation methods of steps S310 and S320 have been described in detail in the above embodiments, and will not be repeated here.

[0118] In step S330, if it is determined that the CG resource does not meet the requirements for the transmission of the first service, the first service is abandoned.

[0119] As an alternative approach, upon receiving configuration information for at least one set of CG resources, determining the PUSCH transmission timing based on this configuration information, and confirming that the CG resources cannot satisfy the transmission of the first service, the terminal device may abandon the first service. In other words, the terminal device can discard the first service if it determines that the CG resources cannot satisfy the transmission of the first service.

[0120] As an example, if the terminal device determines that the PUSCH transmission timing resources cannot fully meet the XR service, or determines that the XR service it needs to transmit exceeds the range of PUSCH transmission timing, the terminal device can drop the XR service.

[0121] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with other embodiments or implementation methods and various optional solutions related to adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0122] This disclosure specifies that if a terminal device determines that CG resources do not meet the requirements for the transmission of the first service, it can abandon the transmission of the first service, thereby meeting the requirements of low latency and high throughput for the first service.

[0123] Figure 6 This is a flowchart illustrating an adaptive method for handling transmission timing according to yet another embodiment. For example... Figure 6 As shown, this method can be executed by a terminal device and includes the following steps.

[0124] In step S410, at least one set of configuration information for authorized CG resources is received from the network device.

[0125] In step S420, the timing of Physical Uplink Shared Channel (PUSCH) transmission is determined based on the configuration information.

[0126] The specific implementation methods of steps S410 and S420 have been described in detail in the above embodiments, and will not be repeated here.

[0127] In step S430, if it is determined that the CG resources do not meet the requirements for the transmission of the first service, the transmission of the first service is postponed.

[0128] As an optional approach, upon receiving configuration information for at least one set of CG resources, determining the PUSCH transmission timing based on this configuration information, and confirming that the CG resources cannot satisfy the transmission of the first service, the terminal device may postpone the transmission of the first service. In other words, the terminal device may postpone the transmission of the first service if it determines that the CG resources cannot satisfy the transmission of the first service.

[0129] As an example, if the terminal device determines that the PUSCH transmission timing resources cannot fully meet the needs of XR services, or if it determines that the XR services it needs to transmit exceed the range of PUSCH transmission timings, the terminal device can postpone sending XR services.

[0130] In step S440, the first service is sent during the next PUSCH transmission opportunity.

[0131] In some implementations, after the transmission of the first service is delayed, the terminal device can transmit the first service in the next PUSCH transmission opportunity, that is, the first service can be delayed until the next PUSCH transmission opportunity.

[0132] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with other embodiments or implementation methods and various optional solutions related to adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0133] This disclosure specifies that if a terminal device determines that the CG resources do not meet the requirements for the transmission of the first service, it can postpone the transmission of the first service and transmit the first service in the next PUSCH transmission opportunity, thereby ensuring the reliability of the transmission of the first service.

[0134] Figure 7 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment. For example... Figure 7 As shown, this method can be executed by a terminal device and includes the following steps.

[0135] In step S510, at least one set of configuration information for authorized CG resources is received from the network device.

[0136] In step S520, the timing of Physical Uplink Shared Channel (PUSCH) transmission is determined based on the configuration information.

[0137] The specific implementation methods of steps S510 and S520 have been described in detail in the above embodiments, and will not be repeated here.

[0138] In step S530, if it is determined that the CG resource does not meet the requirements for the first service transmission, the first service is partially transmitted during the PUSCH transmission timing.

[0139] As an optional approach, upon receiving configuration information for at least one set of CG resources, determining the PUSCH transmission timing based on this configuration information, and confirming that the CG resources cannot satisfy the transmission of the first service, the terminal device may partially transmit the first service during the PUSCH transmission timing. In other words, the terminal device may transmit a portion of the first service when it determines that the CG resources cannot satisfy the transmission of the first service.

[0140] As an example, if the terminal device determines that the PUSCH transmission timing resources cannot fully meet the XR service, or determines that the XR service it needs to transmit exceeds the range of PUSCH transmission timing, the terminal device may send part of the XR service.

[0141] In one specific implementation, when transmitting the first service, the terminal device determines that the entire first service needs to be mapped onto the first resource. However, during the PUSCH transmission, only the second resource is available. Here, the second resource is smaller than the first resource, meaning the CG resource cannot meet the transmission requirements of the first service. To ensure the timeliness of the first service transmission, this embodiment can map the first service onto the second resource according to the mapping order of the first resource, and only send a portion of the service on the second resource, i.e., partially send the first service within the second resource.

[0142] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with other embodiments or implementation methods and various optional solutions related to adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0143] This disclosure specifies that if a terminal device determines that the CG resources do not meet the requirements for the transmission of the first service, it can partially transmit the first service during the PUSCH transmission, thereby meeting the requirements of low latency and high throughput for the first service.

[0144] Figure 8 This is a flowchart illustrating an adaptive method for handling transmission timing according to yet another embodiment. For example... Figure 8 As shown, this method can be executed by a terminal device and includes the following steps.

[0145] In step S610, at least one set of configuration information for authorized CG resources is received from the network device.

[0146] In step S620, the timing of Physical Uplink Shared Channel (PUSCH) transmission is determined based on the configuration information.

[0147] The specific implementation methods of steps S610 and S620 have been described in detail in the above embodiments, and will not be repeated here.

[0148] In step S630, if it is determined that the CG resources do not meet the requirements for the transmission of the first service, the first service is rate-adapted using the modulation and coding scheme MCS.

[0149] As an optional approach, upon receiving configuration information for at least one set of CG resources, determining the PUSCH transmission timing based on this configuration information, and confirming that the CG resources cannot satisfy the transmission of the first service, the terminal device can utilize the Modulation and Coding Scheme (MCS) to perform rate adaptation for the first service. In other words, if the terminal device determines that the CG resources cannot satisfy the transmission of the first service, it can proactively increase the MCS to ensure that the first service can be fully transmitted.

[0150] As an example, if the terminal device determines that the PUSCH transmission timing resources cannot fully meet the needs of XR services, or determines that the XR services it needs to transmit are beyond the range of PUSCH transmission timings, the terminal device can perform rate matching for the first service.

[0151] In this embodiment, the terminal device can gradually increase the MCS (Mean Cross Section) until the CG (Copycat Section) resources can carry the first service. For example, an XR service requires 16 RBs (Resource Blocks) in the time domain. The terminal device has a fixed MCS0 based on its calculation configuration. Since the CG resources are fixed, when the number of first services to be sent increases, in order to allow the CG resources to send more data, the terminal device can increase the MCS bitrate to obtain MCS2. After the bitrate is increased, the information carried on one RB will increase, that is, with the CG resources remaining unchanged, the amount of information sent by each RB increases, thus achieving rate adaptation.

[0152] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with other embodiments or implementation methods and various optional solutions related to adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0153] This disclosure specifies that if a terminal device determines that CG resources do not meet the requirements for the transmission of the first service, it can use modulation and coding scheme (MCS) to perform rate adaptation for the first service, thereby meeting the requirements of low latency and high throughput for the first service.

[0154] Figure 9 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment. For example... Figure 9 As shown, this method can be executed by a terminal device and includes the following steps.

[0155] In step S710, at least one set of configuration information for authorized CG resources is received from the network device.

[0156] In step S720, the timing of Physical Uplink Shared Channel (PUSCH) transmission is determined based on the configuration information.

[0157] The specific implementation methods of steps S710 and S720 have been described in detail in the above embodiments, and will not be repeated here.

[0158] In step S730, first information is obtained.

[0159] In this embodiment of the disclosure, the first information may include at least one of the following: the start symbol (start point symbol) of the extension timing; the starting physical resource block (PRB) of the extension timing; the time domain length of the extension timing; the frequency domain length of the extension timing; the effective duration of the extension timing; the extended time domain length of the extension timing; and the extended frequency domain length of the extension timing. Here, the time domain length of the extension timing can be the total time domain length of the extension timing, the frequency domain length of the extension timing can be the total frequency domain length of the extension timing, the extended time domain length of the extension timing can be the extended time domain length, and the extended frequency domain length of the extension timing is the extended frequency domain length.

[0160] In some implementations, the first information may also be referred to as extended occasion. This extended occasion may be agreed upon by a protocol or configured by the network device to the terminal device through RRC signaling, DCI signaling, or MACCE (MAC Control Element) signaling.

[0161] In step S740, if it is determined that the CG resource does not meet the first service transmission requirement, the PUSCH transmission timing is extended using the first information.

[0162] As an alternative approach, if it is determined that CG resources do not meet the requirements for the first service transmission, the terminal device can extend the PUSCH transmission timing using the first information. This extension can be performed on top of the existing PUSCH transmission timing.

[0163] In this embodiment of the disclosure, the starting point of the extended occasion can be the ending point of the PUSCH transmission timing. For example... Figure 10 As shown, the starting point of the PUSCH transmission is 7021, and the ending point is 7022. The starting point of the extended occasion is 7021, and the ending point is 7023. Therefore, the starting point of the extended occasion can be the ending point of the PUSCH transmission.

[0164] Alternatively, the extension in this embodiment can also directly override the PUSCH transmission timing. In this case, the starting point of the extended occasion can be the starting point of the PUSCH transmission timing. Figure 11 As shown, the starting point of the extended occasion is 7021, which can be the starting point of the PUSCH transmission, and the ending point of the extended occasion is 7024. For example, if the original CG PUSCHoccasion has 10 symbols and the extended occasion has 14 symbols, then the final extension is 4 symbols.

[0165] As an alternative approach, after extending the PUSCH transmission timing using the first information, the terminal device can use extended occasion for service transmission.

[0166] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with other embodiments or implementation methods and various optional solutions related to adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0167] This disclosure specifies that if a terminal device determines that CG resources do not meet the requirements for the transmission of the first service, it can use the first information to extend the PUSCH transmission timing, thereby ensuring the transmission of the first service.

[0168] Figure 12 This is a flowchart illustrating an adaptive method for handling transmission timing according to yet another embodiment. For example... Figure 12 As shown, this method can be executed by a terminal device and includes the following steps.

[0169] In step S810, the first information sent by the network device is received.

[0170] In this embodiment of the disclosure, the first information can be directly configured by the network device. At this time, the first information is fixed. When it is determined that the CG resources do not meet the first service transmission, the terminal device can directly use the first information configured by the network device to extend the PUSCH transmission timing.

[0171] For example, if it is determined at the first moment that CG resources cannot meet the first service transmission, the PUSCH transmission timing can be extended using the first extended occasion sent by the network device. Similarly, if it is determined at the second moment that CG resources cannot meet the first service transmission, the PUSCH transmission timing can also be extended using the same first extended occasion sent by the network device.

[0172] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with the embodiments or implementation methods and various alternative solutions involved in the method for adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0173] This disclosure specifies that a terminal device can directly receive first information from a network device, thereby improving the convenience of information acquisition.

[0174] Figure 13 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment. For example... Figure 13 As shown, this method can be executed by a terminal device and includes the following steps.

[0175] In step S910, if it is determined that the terminal device has the timing extension capability, the first information is determined according to the relationship between the PUSCH transmission timing and the first service.

[0176] In this embodiment of the disclosure, the network device can pre-configure the timing extension capability for the terminal device, that is, the terminal device can receive capability indication information sent by the network device. For example, the capability indication information can be 1 bit. After receiving the capability indication information, the terminal device can support the timing extension capability.

[0177] In some implementations, the terminal device can report the timing extension capability to the network device, and the network device can then query the terminal device for the timing extension capability.

[0178] If it is determined that CG resources do not meet the requirements for the first service transmission, the terminal device can utilize this timing extension capability to extend the PUSCH transmission timing. Therefore, if it is determined that the terminal device has timing extension capability, the terminal device can determine the first information based on the relationship between the PUSCH transmission timing and the first service.

[0179] As an example, if it is determined that the XR service to be transmitted exceeds the range of PUSCH transmission timing and exceeds 3 symbols, then it needs to be extended by 3 symbols, and the first information can include 3 symbols.

[0180] It should be noted that, provided that the terminal device has the capability for time-domain expansion, the terminal device can flexibly expand its resources, whether in the frequency domain, time domain, or time domain.

[0181] It should also be noted that the use of "or" to separate multiple embodiments or features, even if some of the features are not feasible, will not affect the other solutions. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with the embodiments or implementation methods involved in the method for adaptive processing of transmission timing for terminal devices, and their various optional solutions, which will not be elaborated further here.

[0182] This disclosure specifies that, when it is determined that the terminal device has timing extension capability, the terminal device can determine the first information based on the relationship between the PUSCH transmission timing and the first service, thereby improving the flexibility of resource allocation.

[0183] Figure 14 This is a flowchart illustrating an adaptive method for handling transmission timing according to yet another embodiment. For example... Figure 14 As shown, this method can be executed by a terminal device and includes the following steps.

[0184] In step S1010, the second information sent by the network device is received.

[0185] In this embodiment of the disclosure, the terminal device can receive second information sent by the network device. The second information may include at least one of a duration extension threshold and a frequency domain length threshold. Here, the duration extension threshold and the frequency domain length threshold can be referred to as extension boundaries. After receiving the second information, the terminal device can flexibly extend the PUSCH transmission timing within these extension boundaries.

[0186] In this embodiment of the disclosure, the second information can be transmitted through RRC signaling, DCI signaling, or MACCE signaling, similar to the first information.

[0187] In step S1020, the first information is determined by combining the PUSCH transmission timing with the first service within the duration extension threshold and / or frequency domain length threshold.

[0188] In some implementations, after receiving the second information sent by the network device, the terminal device can determine the first information by combining the PUSCH transmission timing with the first service within the duration extension threshold and / or frequency domain length threshold in the second information.

[0189] For example, if the duration extension threshold is 7 symbols, and the terminal device determines that 3 symbols are missing when it is determined that CG resources do not meet the first service transmission requirement, then the first information can include 3 symbols. As another example, if the terminal device determines that 5 symbols are missing when it is determined that CG resources do not meet the first service transmission requirement, then the first information can include 5 symbols.

[0190] Optionally, when the missing time-frequency resources exceed the duration extension threshold and / or frequency domain length threshold, embodiments of this disclosure may combine other methods to transmit the first service. For example, the remaining first service may be rate-adapted using a modulation and coding scheme (MCS), or the remaining first service may be abandoned.

[0191] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with the embodiments or implementation methods and various alternative solutions involved in the method for adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0192] This disclosure specifies that a terminal device can receive second information from a network device, including a duration extension threshold and / or a frequency domain length threshold, and determine the first information by combining the PUSCH transmission timing with the first service within the duration extension threshold and / or frequency domain length threshold. This not only improves the flexibility of resource allocation but also reduces service conflicts.

[0193] Figure 15 This is a flowchart illustrating an adaptive method for processing transmission timing according to another embodiment. For example... Figure 15 As shown, this method can be executed by a terminal device and includes the following steps.

[0194] In step S1110, at least one set of configuration information for authorized CG resources is received from the network device.

[0195] In step S1120, the timing of Physical Uplink Shared Channel (PUSCH) transmission is determined based on the configuration information.

[0196] The specific implementation methods of steps S1110 and S1120 have been described in detail in the above embodiments and will not be repeated here.

[0197] In step S1130, if it is determined that the CG resources meet the requirements for the first service transmission and there are idle resources, idle information is sent to the network device.

[0198] As an optional approach, after receiving configuration information for at least one set of CG resources from the network device, if the terminal device determines that the CG resources satisfy the first service transmission and that there are idle resources, it can send idle information to the network device. Here, the idle information is used to notify the network device of the idle status of the PUSCH transmission timing in the terminal device.

[0199] As described above, the configuration information can include the uplink unlicensed transmission period. Additionally, the idle information can include a first indication field, which can be used to indicate the idle state of the PUSCH transmission timing within the uplink unlicensed transmission period, as detailed below. Figure 16 As shown.

[0200] Here, the first indicator field can be an N-bit bitmap (resource unit bitmap), where each bit corresponds to a PUSCH transmission opportunity. If the length of the uplink unlicensed transmission cycle is M time-domain symbols, then N can be used to divide the M time-domain symbols into N PUSCH transmission opportunities. Each bit of the first indicator field can be indicated by 1 or 0, where 1 or 0 represents whether the indicated PUSCH transmission opportunity is idle.

[0201] Optionally, the idle information may further include a second indication field, wherein the second indication field can be used to indicate the idle state of a sub-timeframe contained within a PUSCH transmission timeframe, as detailed below. Figure 17 As shown.

[0202] Here, the second indicator field can be an N-bit bitmap (resource unit bitmap), where each bit corresponds to a sub-occasion. If at least one PUSCH transmission occurs at a time of M time-domain symbols, then N can be used to divide the M time-domain symbols into N sub-occasions. Each bit in the second indicator field can be indicated by 1 or 0, where 1 or 0 represents whether the indicated sub-occasion is idle.

[0203] In this embodiment of the disclosure, the first indication field and the second indication field may be referred to as the occasion indication field.

[0204] Optionally, the idle information may further include an idle pattern indication field, which indicates at least one idle pattern. The idle pattern indicates whether a sub-occasion is idle within at least one PUSCH transmission period. Additionally, the idle pattern may include one or more elements, which may be sent by the network device to the terminal device.

[0205] Here, the number of free patterns can be predefined by the protocol or configured by the network device via RRC signaling. For example, the network device configures four free patterns for the terminal device, and each free pattern indication field can contain 2 bits. For instance, 00 represents the first pattern, 10 represents the second, and so on. The terminal device can use the free information indication 10 to index to the second free pattern.

[0206] Optionally, the idle information may further include a third indication field, which indicates the idle status of the next PUSCH transmission opportunity. This third indication field may also be referred to as a skip indication field, which indicates whether the nearest PUSCH transmission opportunity is idle, i.e., indicates the idle status of the next PUSCH transmission opportunity.

[0207] For example, the third indication field may carry a 1-bit indication that can be used to indicate whether the next CG PUSCHoccasion is idle or not idle.

[0208] For example, the third indication field may not carry a 1-bit indication; as long as the network device receives the third indication field, it can determine that the next CG PUSCH occasion is idle.

[0209] It should be noted that the idle information in this embodiment can be sent based on UCI (Uplink Control Information).

[0210] It should also be noted that the use of "or" to separate multiple embodiments or features, even if some of the features are not feasible, will not affect the other solutions. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with the embodiments or implementation methods involved in the method for adaptive processing of transmission timing for terminal devices, and their various optional solutions, which will not be elaborated further here.

[0211] This disclosure specifies that when a terminal device determines that CG resources meet the requirements for the transmission of the first service and that there are idle resources, it can send idle information to the network device. This can make full use of CG resources, that is, to re-enable idle resources and reduce resource waste.

[0212] Figure 18 This is a flowchart illustrating an adaptive method for handling transmission timing according to yet another embodiment. For example... Figure 18 As shown, this method can be executed by a terminal device and includes the following steps.

[0213] In step S1210, idle information is sent to the network device before the first duration.

[0214] In this embodiment of the disclosure, the terminal device can send idle information to the network device in advance, wherein the end time of the first duration can be the start time of the PUSCH transmission. In other words, the terminal device can send the idle information for a first duration before the start of the PUSCH transmission. The purpose of sending the idle information before the first duration is to ensure that the network device has sufficient time to re-allocate idle resources.

[0215] In some embodiments, the first duration may be sent by the network device to the terminal device.

[0216] Optionally, the terminal device may define a first duration capability, which is used to send a first duration. That is, the terminal device can send the first duration to the network device through the first duration capability. Based on this, the network device can query the terminal device for the first duration capability.

[0217] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with the embodiments or implementation methods and various alternative solutions involved in the method for adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0218] This disclosure specifies that the terminal device can send idle information to the network device before a first duration, thus ensuring that the network device has enough time to reclaim idle resources.

[0219] Figure 19 This is a flowchart illustrating an adaptive method for processing transmission timing according to one embodiment. Figure 19 As shown, this method can be executed by a network device and includes the following steps.

[0220] In step S1310, at least one set of configuration information for authorized CG resources is sent to the terminal device.

[0221] In this embodiment of the disclosure, the configuration information is used by the terminal device to determine the PUSCH transmission timing and to adaptively process the PUSCH transmission timing when the CG resources are not compatible with the first service.

[0222] Here, the configuration information may include at least one of the following: timeDomainOffset, FDRA (Frequency Domain Resource Allocation), TDRA (Time Domain Resource Allocation), periodicity, periodicityExt, physical layer priority index (phy-PriorityIndex), resource block size (rbg-Size), uplink shared channel retransmission type indicator (pusch-RepTypeIndicator), duplicated redundancy version (repK-RV), repK (repetition count), resource allocation, transmission timing offset, transmission timing idle indicator, number of transmission timings, time reference system frame number (timeReferenceSFN), frequency hopping configuration (frequencyHopping), frequency hopping configuration offset (frequencyHoppingOffset), modulation and coding scheme (MCS), and number of HARQ (Hybrid Automatic Repeat Request) processes.

[0223] In some implementations, network devices can send configuration information to terminal devices via higher-layer signaling. For example, a network device can send RRC signaling carrying configuration information to a terminal device. Optionally, network devices can also send configuration information to terminal devices via dynamic signaling. For example, a network device can send DCI signaling carrying configuration information to a terminal device.

[0224] In this embodiment of the disclosure, the PUSCH transmission timing may include at least one of the following information: time domain resources corresponding to the uplink unlicensed transmission period, frequency domain resources corresponding to the uplink unlicensed transmission period, non-idle time domain resources corresponding to the uplink unlicensed transmission period, non-idle frequency domain resources corresponding to the uplink unlicensed transmission period, idle time domain resources corresponding to the uplink unlicensed transmission period, idle frequency domain resources corresponding to the uplink unlicensed transmission period, radio frame corresponding to the uplink unlicensed transmission period, resource window corresponding to the uplink unlicensed transmission period, time slot corresponding to the uplink unlicensed transmission period, continuous time domain symbols corresponding to the uplink unlicensed transmission period, and non-continuous time domain symbols corresponding to the uplink unlicensed transmission period, etc.

[0225] In other implementations, the network device may receive the first service partially transmitted by the terminal device during the PUSCH transmission.

[0226] In other implementations, the network device may send first information to the terminal device, wherein the first information is used to extend the timing of PUSCH transmission.

[0227] In other implementations, the network device may receive timing extension capabilities sent by the terminal device, and based on this, the network device may query the terminal device for the timing extension capabilities.

[0228] In other embodiments, the first information may include at least one of the following: the start symbol of the extension timing; the start physical resource block (PRB) of the extension timing; the time domain length of the extension timing; the frequency domain length of the extension timing; the effective duration of the extension timing; the extended time domain length of the extension timing; and the extended frequency domain length of the extension timing.

[0229] In other embodiments, the network device may send second information to the terminal device, wherein the second information may include at least one of a duration extension threshold and a frequency domain length threshold, and the second information may be used to adaptively extend the PUSCH transmission timing within the duration extension threshold and / or the frequency domain length threshold.

[0230] In other embodiments, the network device may receive idle information sent by the terminal device. Here, the idle information includes at least one of the following: a first indication field, which indicates the idle state of a PUSCH transmission opportunity within an uplink unlicensed transmission period; a second indication field, which indicates the idle state of a sub-opportunity included within a PUSCH transmission opportunity; and a third indication field, which indicates the idle state of the next PUSCH transmission opportunity.

[0231] In other implementations, the network device may send a first duration to the terminal device. Optionally, the network device may also receive a first duration from the terminal device, where the first duration may be sent by the terminal device through its defined first duration capability. Based on this, the network device may query the terminal device for the first duration capability.

[0232] It should be noted that the multiple embodiments or features separated by "or" do not affect other solutions even if some of the features are not feasible. Furthermore, unless contradictory, the embodiments of this disclosure can be combined with the embodiments or implementation methods and various alternative solutions involved in the method for adaptive processing of transmission timing for terminal devices, which will not be elaborated further here.

[0233] This disclosure specifies that a network device can send configuration information of at least one set of CG resources to a terminal device. The configuration information is used by the terminal device to determine the PUSCH transmission timing and to adaptively process the PUSCH transmission timing when the CG resources are not compatible with the first service. This can meet the transmission requirements of different services and make full use of time and frequency resources.

[0234] Figure 20 This is a block diagram illustrating a terminal device 1400 according to one embodiment. (Refer to...) Figure 20 The terminal device 1400 may include a receiving module 1410 and a processing module 1420.

[0235] The receiving module 1410 is configured to receive configuration information for at least one set of authorized CG resources sent by the network device;

[0236] The processing module 1420 is configured to determine the timing of Physical Uplink Shared Channel (PUSCH) transmission based on configuration information; and to adaptively process the PUSCH transmission timing in the event that the CG resources are not compatible with the first service.

[0237] In some implementations, the processing module 1420 may also be configured to adaptively process the PUSCH transmission timing when it is determined that the CG resource does not satisfy the first service transmission.

[0238] In some implementations, the situation where the CG resource fails to satisfy the first service transmission includes at least one of the following: the time-domain resources corresponding to the CG resource are less than the time-domain resources required for the first service transmission; the frequency-domain resources corresponding to the CG resource are less than the frequency-domain resources required for the first service transmission; the time-domain resources and frequency-domain resources corresponding to the CG resource are less than the time-domain resources and frequency-domain resources required for the first service transmission; when the first service arrives, the remaining time-domain resources of the CG resource are less than the time-domain resources required for the first service transmission; when the first service arrives, the quotient of the remaining time-domain resources of the CG resource and the time-domain resources corresponding to the entire CG resource is less than a first threshold.

[0239] In some implementations, the processing module 1420 may also be configured to abandon the first service if it is determined that the CG resource does not satisfy the first service transmission.

[0240] In some implementations, the processing module 1420 may also be configured to postpone the transmission of the first service if it is determined that the CG resource does not satisfy the first service transmission; and to transmit the first service in the next PUSCH transmission opportunity.

[0241] In some implementations, the processing module 1420 may also be configured to partially transmit the first service during the PUSCH transmission timing if it is determined that the CG resource does not satisfy the first service transmission.

[0242] In some implementations, the processing module 1420 may also be configured to perform rate adaptation of the first service using modulation and coding scheme (MCS) when it is determined that the CG resource does not meet the requirements for the transmission of the first service.

[0243] In some implementations, the processing module 1420 may also be configured to acquire first information; and, if it is determined that the CG resource does not satisfy the first service transmission, to extend the PUSCH transmission timing using the first information.

[0244] In some implementations, the first information includes at least one of the following: the start symbol of the extension timing; the start physical resource block (PRB) of the extension timing; the time domain length of the extension timing; the frequency domain length of the extension timing; the effective duration of the extension timing; the extended time domain length of the extension timing; and the extended frequency domain length of the extension timing.

[0245] In some implementations, the receiving module 1410 may also be configured to receive the first information sent by the network device.

[0246] In some implementations, the processing module 1420 may also be configured to determine the first information based on the relationship between the PUSCH transmission timing and the first service, provided that the terminal device has timing extension capabilities.

[0247] In some embodiments, the receiving module 1410 may also be configured to receive second information sent by the network device, the second information including at least one of a duration extension threshold and a frequency domain length threshold; the processing module 1420 may also be configured to determine the first information in conjunction with the PUSCH transmission timing and the first service within the duration extension threshold and / or the frequency domain length threshold.

[0248] In some embodiments, the terminal device 1400 may further include a sending module configured to send idle information to the network device when it is determined that the CG resource satisfies the first service transmission and that idle resources exist. The idle information is used to notify the network device of the idle status of the PUSCH transmission timing.

[0249] In some implementations, the CG resource includes an uplink unlicensed transmission period, and the idle information includes at least one of the following: a first indication field, which indicates the idle state of the PUSCH transmission opportunity within the uplink unlicensed transmission period; a second indication field, which indicates the idle state of a sub-opportunity included within the PUSCH transmission opportunity; and a third indication field, which indicates the idle state of the next PUSCH transmission opportunity.

[0250] In some implementations, the sending module is further configured to send the idle information to the network device before a first duration, the end of which is the start of the PUSCH transmission timing.

[0251] This disclosure specifies that by receiving configuration information of at least one set of CG resources sent by a network device, wherein the CG resources include PUSCH transmission timing, if the CG resources are not compatible with the first service, this disclosure can adaptively process the PUSCH transmission timing, thereby meeting the transmission requirements of different services and making full use of time and frequency resources.

[0252] Figure 21 This is a block diagram illustrating a network device 1500 according to one embodiment. (Refer to...) Figure 21 The network device 1500 may include a transmitting module 1510.

[0253] The sending module 1510 is configured to send configuration information of at least one set of authorized CG resources to the terminal device. The configuration information is used by the terminal device to determine the PUSCH transmission timing and to adaptively process the PUSCH transmission timing if the CG resources are not compatible with the first service.

[0254] In some implementations, the receiving module may also be configured to receive the first service partially transmitted by the terminal device during the PUSCH transmission.

[0255] In some implementations, the sending module may also be configured to send first information to the terminal device, the first information being used to extend the timing of the PUSCH transmission.

[0256] In some implementations, the sending module may also be configured to send second information to the terminal device, the second information including at least one of a duration extension threshold and a frequency domain length threshold, the second information being used to adaptively extend the PUSCH transmission timing within the duration extension threshold and / or the frequency domain length threshold.

[0257] In some implementations, the CG resource includes an uplink unlicensed transmission period, and the idle information includes at least one of the following: a first indication field, which indicates the idle state of the PUSCH transmission opportunity within the uplink unlicensed transmission period; a second indication field, which indicates the idle state of a sub-opportunity included within the PUSCH transmission opportunity; and a third indication field, which indicates the idle state of the next PUSCH transmission opportunity.

[0258] This disclosure specifies that a network device can send configuration information of at least one set of CG resources to a terminal device. The configuration information is used by the terminal device to determine the PUSCH transmission timing and to adaptively process the PUSCH transmission timing when the CG resources are not compatible with the first service. This can meet the transmission requirements of different services and make full use of time and frequency resources.

[0259] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0260] This disclosure also provides a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the steps of the adaptive processing transmission timing method provided in this disclosure.

[0261] This disclosure also provides a communication system that may include a terminal device and a network device. The terminal device can perform the steps of the method for adaptively processing transmission timing described in the above embodiments. Additionally, the network device can perform the steps of the method for adaptively processing transmission timing described in the above embodiments.

[0262] Figure 22 This is a block diagram illustrating a communication device 1600 according to one embodiment. The communication device 1600 can be a terminal device. For example, the communication device 1600 can be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, smart car, etc.

[0263] Reference Figure 22 The communication device 1600 may include one or more of the following components: a processing component 1602, a memory 1604, a power supply component 1606, a multimedia component 1608, an audio component 1610, an input / output interface 1612, a sensor component 1614, and a communication component 1616.

[0264] Processing component 1602 typically controls the overall operation of communication device 1600, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 1602 may include one or more processors 1620 to execute instructions to complete all or part of the steps of the adaptive processing transmission timing method described above. Furthermore, processing component 1602 may include one or more modules to facilitate interaction between processing component 1602 and other components. For example, processing component 1602 may include a multimedia module to facilitate interaction between multimedia component 1608 and processing component 1602.

[0265] Memory 1604 is configured to store various types of data to support the operation of communication device 1600. Examples of this data include instructions for any application or method operating on communication device 1600, contact data, phonebook data, messages, pictures, videos, etc. Memory 1604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0266] Power supply component 1606 provides power to various components of communication device 1600. Power supply component 1606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to communication device 1600.

[0267] Multimedia component 1608 includes a screen that provides an output interface between the communication device 1600 and the user. In one embodiment, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In one embodiment, multimedia component 1608 includes a front-facing camera and / or a rear-facing camera. When the communication device 1600 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0268] Audio component 1610 is configured to output and / or input audio signals. For example, audio component 1610 includes a microphone (MIC) configured to receive external audio signals when communication device 1600 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1604 or transmitted via communication component 1616. In one embodiment, audio component 1610 also includes a speaker for outputting audio signals.

[0269] Input / output interface 1612 provides an interface between processing component 1602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, start buttons, and lock buttons.

[0270] Sensor assembly 1614 includes one or more sensors for providing status assessments of various aspects of communication device 1600. For example, sensor assembly 1614 may detect the on / off state of communication device 1600, the relative positioning of components such as the display and keypad of communication device 1600, changes in position of communication device 1600 or a component of communication device 1600, the presence or absence of user contact with communication device 1600, the orientation or acceleration / deceleration of communication device 1600, and temperature changes of communication device 1600. Sensor assembly 1614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1614 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In one embodiment, sensor assembly 1614 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0271] Communication component 1616 is configured to facilitate wired or wireless communication between communication device 1600 and other devices. Communication device 1600 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 1616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 1616 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0272] In an exemplary embodiment, the communication device 1600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above-described method for adaptively processing transmission timing.

[0273] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1604 including instructions, which can be executed by a processor 1620 of a communication device 1600 to complete the aforementioned adaptive processing transmission timing method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0274] The aforementioned device can be a standalone electronic device or a part of a standalone electronic device. For example, in one embodiment, the device can be an integrated circuit (IC) or a chip, wherein the integrated circuit can be a single IC or a collection of multiple ICs. The chip can include, but is not limited to, the following types: GPU (Graphics Processing Unit), CPU (Central Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), and SoC (System on Chip). The aforementioned integrated circuit or chip can be used to execute executable instructions (or code) to implement the aforementioned adaptive processing transmission timing method. The executable instructions can be stored in the integrated circuit or chip or obtained from other devices or equipment. For example, the integrated circuit or chip includes a processor, memory, and an interface for communicating with other devices. The executable instruction can be stored in the memory, and when the executable instruction is executed by the processor, the above-mentioned adaptive processing transmission timing method is implemented; or, the integrated circuit or chip can receive the executable instruction through the interface and transmit it to the processor for execution, so as to implement the above-mentioned adaptive processing transmission timing method.

[0275] In another exemplary embodiment, a computer program product is also provided, the computer program product comprising a computer program executable by a programmable device, the computer program having a code portion for performing the above-described method of adaptive processing transmission timing when executed by the programmable device.

[0276] Figure 23 This is a block diagram illustrating a communication device 1700 according to an exemplary embodiment. The communication device 1700 can be a network device. For example, the communication device 1700 can be provided as a server. (Refer to...) Figure 23 The communication device 1700 includes a processing component 1722, which further includes one or more processors, and memory resources represented by memory 1732 for storing instructions, such as application programs, that can be executed by the processing component 1722. The application programs stored in memory 1732 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 1722 is configured to execute instructions to perform an adaptive processing transmission timing method.

[0277] The communication device 1700 may further include a power supply component 1726 configured to perform power management of the communication device 1700, a wired or wireless network interface 1750 configured to connect the communication device 1700 to a network, and an input / output interface 1758. The communication device 1700 can operate on an operating system, such as Windows Server, stored in memory 1732. TM Mac OS X TM Unix TM Linux TM FreeBSD TM Or similar.

[0278] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of this disclosure. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0279] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A method for adaptively processing transmission timing, characterized in that, Executed by the terminal device, including: Receive configuration information for at least one set of authorized CG resources sent by the network device; The timing of Physical Uplink Shared Channel (PUSCH) transmission is determined based on the configuration information. In the event that the CG resources are not compatible with the first service, the timing of the PUSCH transmission is adaptively adjusted. The adaptive processing of the PUSCH transmission timing when the CG resources are incompatible with the first service includes: If it is determined that the CG resource does not satisfy the first service transmission, adaptive processing is performed on the PUSCH transmission timing; and / or, If it is determined that the CG resource satisfies the first service transmission and there is idle resource, idle information is sent to the network device before the first duration. The idle information is used to notify the network device of the idle status of the PUSCH transmission opportunity. The end time of the first duration is the start time of the PUSCH transmission opportunity. The adaptive processing of the PUSCH transmission timing when it is determined that the CG resource does not satisfy the first service transmission further includes: Obtain first information; if it is determined that the CG resource does not meet the first service transmission, use the first information to extend the PUSCH transmission timing; the starting point of the extended PUSCH transmission timing is the ending point of the PUSCH transmission timing. The acquisition of the first information also includes: Receive second information sent by the network device, the second information including at least one of a duration extension threshold and a frequency domain length threshold; determine the first information in conjunction with the PUSCH transmission timing and the first service within the duration extension threshold and / or frequency domain length threshold; The method further includes: The first service is transmitted using the extended PUSCH transmission timing. When the missing time-frequency resources are greater than the duration extension threshold and / or the frequency domain length threshold, the remaining first service is rate-adapted using MCS, or the remaining first service is abandoned.

2. The method according to claim 1, characterized in that, The situation where the CG resource fails to meet the first service transmission requirement includes at least one of the following: The temporal domain resources corresponding to the CG resources are less than the temporal domain resources required for the transmission of the first service. The frequency domain resources corresponding to the CG resources are less than the frequency domain resources required for the transmission of the first service. The time-domain and frequency-domain resources corresponding to the CG resources are less than the time-domain and frequency-domain resources required for the transmission of the first service. When the first service arrives, the remaining time domain resources of the CG resource are less than the time domain resources required for the transmission of the first service. When the first service arrives, the quotient of the remaining temporal resources of the CG resource and the temporal resources corresponding to the entire CG resource is less than a first threshold.

3. The method according to claim 1, characterized in that, The first information includes at least one of the following: The starting symbol for the extension timing; The initial physical resource block (PRB) for the expansion timing; The time domain length of the extended timing; The frequency domain length of the extended timing; The effective duration of the extended opportunity; The extended time domain length of the extended timing; and The length of the extended frequency domain when the extension is initiated.

4. The method according to claim 1, characterized in that, The CG resources include an uplink unlicensed transmission period, and the idle information includes at least one of the following: A first indication field is used to indicate the idle state of the PUSCH transmission timing during the uplink unlicensed transmission period; The second indication field is used to indicate the idle state of the sub-times included within the PUSCH transmission time; The third indication field is used to indicate the idle state of the next PUSCH transmission opportunity.

5. A method for adaptively processing transmission timing, characterized in that, Performed by network devices, including: Send at least one set of configuration information for authorized CG resources to the terminal device. The configuration information is used by the terminal device to determine the timing of Physical Uplink Shared Channel (PUSCH) transmission and to adaptively process the PUSCH transmission timing if the CG resources are not compatible with the first service. The method further includes: The terminal device receives idle information sent by the terminal device. The idle information is sent by the terminal device to the network device before a first duration when it determines that the CG resource satisfies the first service transmission and that there is idle resource. The idle information is used to notify the network device of the idle status of the PUSCH transmission opportunity. The end time of the first duration is the start time of the PUSCH transmission opportunity. And / or, Send second information to the terminal device, the second information including at least one of a duration extension threshold and a frequency domain length threshold, the second information being used to adaptively extend the PUSCH transmission timing within the duration extension threshold and / or the frequency domain length threshold; the starting point of the extended PUSCH transmission timing is the ending point of the PUSCH transmission timing; The method further includes: The terminal device receives the first service transmitted using the extended PUSCH transmission timing.

6. The method according to claim 5, characterized in that, The method further includes: Send first information to the terminal device, the first information being used to extend the timing of the PUSCH transmission.

7. The method according to claim 6, characterized in that, The first information includes at least one of the following: The starting symbol for the extension timing; The initial physical resource block (PRB) for the expansion timing; The time domain length of the extended timing; The frequency domain length of the extended timing; The effective duration of the extended opportunity; The extended time domain length of the extended timing; and The length of the extended frequency domain when the extension is initiated.

8. The method according to claim 5, characterized in that, The CG resources include an uplink unlicensed transmission period, and the idle information includes at least one of the following: A first indication field is used to indicate the idle state of the PUSCH transmission timing during the uplink unlicensed transmission period; The second indication field is used to indicate the idle state of the sub-times included within the PUSCH transmission time; The third indication field is used to indicate the idle state of the next PUSCH transmission opportunity.

9. A terminal device, characterized in that, include: The receiving module is configured to receive configuration information for at least one set of authorized CG resources sent by the network device; The processing module is configured to determine the PUSCH transmission timing based on the configuration information; and to perform adaptive processing on the PUSCH transmission timing when the CG resources are not compatible with the first service. The adaptive processing of the PUSCH transmission timing when the CG resources are incompatible with the first service includes: If it is determined that the CG resource does not satisfy the first service transmission, adaptive processing is performed on the PUSCH transmission timing; and / or, If it is determined that the CG resource satisfies the first service transmission and there is idle resource, idle information is sent to the network device before the first duration. The idle information is used to notify the network device of the idle status of the PUSCH transmission opportunity. The end time of the first duration is the start time of the PUSCH transmission opportunity. The adaptive processing of the PUSCH transmission timing when it is determined that the CG resource does not satisfy the first service transmission further includes: Obtain first information; if it is determined that the CG resource does not meet the first service transmission, use the first information to extend the PUSCH transmission timing; the starting point of the extended PUSCH transmission timing is the ending point of the PUSCH transmission timing. The acquisition of the first information also includes: Receive second information sent by the network device, the second information including at least one of a duration extension threshold and a frequency domain length threshold; determine the first information in conjunction with the PUSCH transmission timing and the first service within the duration extension threshold and / or frequency domain length threshold; The terminal device is further configured to send the first service using the extended PUSCH transmission timing, and when the missing time-frequency resources are greater than the duration extension threshold and / or the frequency domain length threshold, to perform rate adaptation on the remaining first service using MCS, or to abandon the remaining first service.

10. A network device, characterized in that, include: The sending module is configured to send at least one set of configuration information for authorized CG resources to the terminal device. The configuration information is used by the terminal device to determine the timing of the Physical Uplink Shared Channel (PUSCH) transmission and to adaptively process the PUSCH transmission timing if the CG resources are not compatible with the first service. The network device is further configured to receive idle information sent by the terminal device; the idle information is sent by the terminal device to the network device before a first duration when it determines that the CG resource satisfies the first service transmission and that there is idle resource; the idle information is used to notify the network device of the idle status of the PUSCH transmission opportunity; the end time of the first duration is the start time of the PUSCH transmission opportunity. And / or, Send second information to the terminal device, the second information including at least one of a duration extension threshold and a frequency domain length threshold, the second information being used to adaptively extend the PUSCH transmission timing within the duration extension threshold and / or the frequency domain length threshold; the starting point of the extended PUSCH transmission timing is the ending point of the PUSCH transmission timing; The network device is also configured to receive the first service sent by the terminal device using the extended PUSCH transmission timing.

11. A communication device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the executable instructions to implement the method as described in any one of claims 1 to 4.

12. A communication device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the executable instructions to implement the method as described in any one of claims 5 to 8.

13. A communication system, characterized in that, It includes the terminal device as described in claim 9 and the network device as described in claim 10.

14. A computer-readable storage medium having computer program instructions stored thereon, characterized in that, When the program instructions are executed by the processing device, they implement the steps of the method according to any one of claims 1 to 8.

Images