Resource Allocation Method and Device

Abstract

The embodiments of the present application provide a method and apparatus for configuring resources based on unlicensed frequency bands, which can solve the problem of configuring the fixed frame period (FFP) of terminal devices operating in unlicensed frequency bands in the prior art. The method includes a network device sending fixed frame period (FFP) configuration information to a terminal device, where the FFP configuration information is used to indicate the FFP configuration of the terminal device. The FFP is the period for the terminal device to transmit signals, and the FFP includes a channel occupancy time (COT) and an idle period. The channel occupancy time (COT) is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular, to a resource allocation method and device in an unlicensed frequency band. Background Art

[0002] In the fifth generation (5G) mobile communication system, wireless devices are supported to communicate within an unlicensed frequency band. In this mode, multiple different wireless devices need to share the same frequency domain resources. th In this system, different wireless devices need to occupy the shared frequency domain resources according to rules. For example, taking 10 milliseconds (ms) as an access period, wireless device A needs to detect the channel occupancy situation before this access period, that is, perform a clear channel assessment (CCA). If wireless device A detects a wireless signal or a strong wireless signal energy on the channel during CCA, then wireless device A confirms that the channel detected during the current access period cannot be used, or the detected channel is occupied by other wireless devices, and wireless device A will not send information during this access period; if wireless device A does not detect a wireless signal or a strong wireless signal energy on the channel during CCA, then wireless device A can send a signal during the subsequent channel occupancy time (COT).

[0003] Different from the current resource transmission based on time slots in the NR system, the impact of the access period needs to be considered in the unlicensed frequency band. However, the prior art still does not provide a corresponding solution. Therefore, how to configure the access period and the channel occupancy time COT of the terminal device by the network device remains a technical problem to be solved urgently.

[0004] Summary of the Invention Embodiments of this application provide a resource allocation method and device to enable a terminal device in an unlicensed frequency band to obtain the configuration of a fixed frame period (FFP) including COT and an idle period for access.

[0005]

[0006] ​In a first aspect, the present application provides a method for resource allocation, which is executed by a network device. In this method, the network device sends FFP configuration information to a terminal device, and the FFP configuration information is used to indicate the FFP configuration of the terminal device. The FFP is a period for the terminal device to transmit signals, and the FFP includes a channel occupancy time (COT) and an idle period. The channel occupancy time COT is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT.

[0007] In a second aspect, the present application further provides a method for resource allocation, which is executed by a terminal device. In this method, the terminal device receives the FFP configuration information from the network device, parses the FFP configuration information, and obtains the FFP configuration. The FFP configuration information is used to indicate the FFP configuration of the terminal device. The FFP is a period for the terminal device to transmit signals, and the FFP includes a channel occupancy time (COT) and an idle period. The channel occupancy time COT is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT.

[0008] Through the above method, the network device can configure the FFP of the terminal device and send it to the terminal device. Thus, the terminal device can compete for a channel according to the FFP configuration information indicated by the network device and perform transmission after competing for the channel.

[0009] Exemplarily, the FFP configuration information may be carried in a radio resource control (RRC) signaling.

[0010] In a possible design, the FFP configuration information includes one or more of the following:

[0011] The time domain offset of the FFP relative to a system frame or relative to the FFP of the network device, which is used to indicate the start boundary of the FFP of the terminal device;

[0012] The duration of the COT;

[0013] The duration of the idle period of the FFP;

[0014] The duration of the FFP;

[0015] The physical uplink shared channel (PUSCH) start and length indication value (SLIV), which is used to indicate the configuration of the PUSCH in the COT.

[0016] Optionally, the time domain offset unit of the FFP relative to the system frame or relative to the network device FFP is a symbol.

[0017] Optionally, the duration of the COT complies with the following rule:

[0018] COT duration = L×repK×symbol_length;

[0019] The L represents the number of symbols in the PUSCH in the COT, the rep_K represents the number of PUSCHs in a COT, and the symbol_length represents the length of the symbol in the PUSCH.

[0020] In a possible design, the network device also sends FFP scheduling information to the terminal device. Correspondingly, the terminal device receives the FFP scheduling information. The FFP scheduling information is used to schedule the terminal device to perform transmission on the FFP configured by the FFP configuration information.

[0021] Exemplarily, the FFP scheduling information and the FFP configuration information may be sent in different signaling. The FFP configuration information is carried in the RRC signaling, and the FFP scheduling information is carried in the downlink control information (DCI).

[0022] In the case of scheduling one FFP, the FFP scheduling information may include a first offset, and the first offset is used to indicate the offset of the start boundary of the FFP scheduled by the network device relative to the start boundary of the time domain resource where the network device sends the FFP scheduling information.

[0023] In the case of scheduling multiple FFP, the FFP scheduling information may include the number of transmissions and a second offset. The number of transmissions is used to indicate the number of FFP scheduled by the network device, and the second offset is used to indicate the offset of the start boundary of the first FFP scheduled by the network device relative to the start boundary of the time domain resource where the network device sends the FFP scheduling information.

[0024] Exemplarily, the FFP scheduling information and the FFP configuration information may be sent in different signaling, or both the FFP configuration information and the FFP scheduling information are carried in the RRC signaling.

[0025] The FFP scheduling information includes the time domain resource period and the bitmap of the time domain resource pattern. The time domain resource period is used to indicate a time domain resource period to the terminal device. Among them, a plurality of FFP are included in one time domain resource period, and the bitmap of the time domain resource pattern is used to indicate whether each of the plurality of FFP can be used by the terminal device for transmission. When not used for the terminal device to perform transmission, the FFP may be used by the network device in the unlicensed frequency band or by other terminal devices.

[0026] Optionally, the FFP scheduling information may also not include the bitmap of the time-domain resource pattern, but only include the time-domain resource period. In this case, multiple FFPs in the time-domain resource period scheduled by the network device are used by the terminal device.

[0027] In a third aspect, the present application provides a communication device for resource allocation, and the communication device has the function of implementing the method in the first aspect and any possible implementation manners thereof. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0028] In a fourth aspect, the present application provides a communication device for resource allocation, and the communication device has the function of implementing the method in the second aspect and any possible implementation manners thereof. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0029] In a fifth aspect, the present application provides a communication device. The structure of the communication device includes a memory, a processor, and a communication module; the memory is used for storing a computer-readable program; the processor calls the instruction stored in the memory and executes the method executed by the terminal device in the first aspect above; the communication module is used for receiving data and / or sending data under the control of the processor. The communication module may be a transceiver, a communication interface, or an input / output interface.

[0030] Optionally, the communication device may be a network device or a chip.

[0031] In a sixth aspect, the present application provides a communication device. The structure of the communication device includes a memory, a processor, and a communication module; the memory is used for storing a computer-readable program; the processor calls the instruction stored in the memory and executes the method executed by the terminal device in the second aspect above; the communication module is used for receiving data and / or sending data under the control of the processor. The communication module may be a transceiver, a communication interface, or an input / output interface.

[0032] Optionally, the communication device may be a terminal device or a chip.

[0033] In a seventh aspect, the present application provides a computer-readable storage medium. Computer instructions are stored in the computer-readable storage medium. When the computer instructions run on a computer, the computer is enabled to execute the method in the first aspect or any possible implementation manner of the first aspect.

[0034] In an eighth aspect, the present application provides a computer-readable storage medium storing computer instructions, which, when run on a computer, cause the computer to execute the method in the second aspect or any possible implementation manner of the second aspect.

[0035] In a ninth aspect, the present application provides a chip including a processor. The processor is configured to read and execute a computer program stored in a memory to execute the method in the first aspect or any possible implementation manner of the first aspect.

[0036] Optionally, the chip further includes a memory, which is connected to the processor through a circuit or wire, and the memory is used to store a computer program.

[0037] Further optionally, the chip further includes a communication interface or an input / output interface.

[0038] In a tenth aspect, the present application provides a chip including a processor. The processor is configured to read and execute a computer program stored in a memory to execute the method in the second aspect or any possible implementation manner of the second aspect.

[0039] Optionally, the chip further includes a memory, which is connected to the processor through a circuit or wire, and the memory is used to store a computer program.

[0040] Further optionally, the chip further includes a communication interface or an input / output interface.

[0041] In an eleventh aspect, the present application further provides a computer program product including computer program code, which, when run on a computer, causes the computer to execute the method in the first aspect and any possible implementation manner thereof.

[0042] In a twelfth aspect, the present application further provides a computer program product including computer program code, which, when run on a computer, causes the computer to execute the method in the second aspect and any possible implementation manner thereof.

[0043] The technical solution of the present application provides a method for a network device to configure FFP for a terminal device in an unlicensed frequency band. At the same time, it also provides flexible scheduling of transmission resources of the network device for the terminal device, especially flexible scheduling of the uplink transmission of the terminal device, which can meet the requirements of different service types and scenarios and improve communication efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application;

[0045] Figure 2 Schematic diagram of the FBE-based channel detection mechanism in the embodiments of the present application;

[0046] Figure 3 Flowchart of the resource allocation method in an embodiment of the present application;

[0047] Figure 4 Schematic diagram of the time domain offset of the terminal device FFP relative to the network device FFP0 in an embodiment of the present application;

[0048] Figure 5 Schematic diagram of feedback HARQ in FFP in another embodiment of the present application;

[0049] Figure 6 Schematic diagram of the network device scheduling the terminal device for transmission in yet another embodiment of the present application;

[0050] Figure 7 Schematic diagram of the network device scheduling the terminal device for transmission in yet another embodiment of the present application;

[0051] Figure 8 Schematic diagram of the time domain resource period configured by the network device in an embodiment of the present application;

[0052] Figure 9 Schematic diagram of the modules of the communication device in an embodiment of the present application;

[0053] Figure 10 Schematic diagram of the modules of the communication device in another embodiment of the present application;

[0054] Figure 11 Simplified structural schematic diagram of the communication device in an embodiment of the present application;

[0055] Figure 12 Simplified structural schematic diagram of the communication device in another embodiment of the present application. Detailed implementation manners

[0056] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0057] The technical solutions of the present application are mainly applied to wireless communication systems operating in unlicensed frequency bands, for example, the unlicensed system of new radio (NR) (hereinafter referred to as NR-U). In addition, it can also be applied to other communication systems where one communication device needs to indicate the channel access type to another communication device.

[0058] Hereinafter, some terms in the present application will be explained to facilitate the understanding of those skilled in the art.

[0059] A network device is a device that connects a terminal device to a wireless network in a communication system. As a node in a radio access network, the network device can also be referred to as a base station, or as a radio access network (RAN) node (or device).

[0060] Currently, some examples of network devices are: gNB, transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), access point (AP), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), or baseband unit (BBU), Enterprise LTE Discrete Spectrum Aggregation (eLTE-DSA) base station, etc.

[0061] In addition, in a network architecture, the network device may include a centralized unit (CU) node and a distributed unit (DU) node. This architecture splits the protocol layers of the eNB in a Long Term Evolution (LTE) system, with the functions of some protocol layers being centrally controlled by the CU and the functions of the remaining or all protocol layers being distributed in the DU, with the CU centrally controlling the DU.

[0062] A terminal device is a device that provides voice and / or data connectivity to a user. A terminal device can also be referred to as user equipment (UE), terminal, mobile station (MS), mobile terminal (MT), etc.

[0063] For example, the terminal device can be a handheld device with wireless connection function, various vehicle-mounted devices, roadside units, etc. Currently, some examples of terminal devices are: mobile phone, tablet computer, laptop, palmtop computer, mobile internet device (MID), point of sale (POS), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, various smart meters (smart water meter, smart electricity meter, smart gas meter), eLTE-DSA UE, device with integrated access and backhaul (IAB) capability, vehicle-mounted electronic control unit (ECU), etc., in-vehicle computer, vehicle-mounted cruise system, telematics box (T-BOX), etc.

[0064] A bandwidth part (BWP) is a continuous segment of frequency resources within a carrier used by a cell managed by a network device. For example, a BWP can include K consecutive subcarriers, or the frequency resources where M non-overlapping consecutive resource blocks (RBs) are located, or the frequency resources where N non-overlapping consecutive resource block groups (RBGs) are located; K, M, and N are all integers greater than 0. The BWP can also be referred to as bandwidth resource, bandwidth region, frequency domain resource, partial frequency resource, or other names, which are not restricted in this application.

[0065] "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0066] In this application, "a plurality of" refers to two or more. "At least one" refers to one or more. Additionally, it can be understood that in the description of this application, terms such as "first" and "second" are only used for the purpose of distinguishing descriptions, and cannot be construed as indicating or implying relative importance, nor can they be construed as indicating or implying an order.

[0067] See Figure 1 , Figure 1 which is an example of the architecture of a communication system applicable to the embodiments of this application. As Figure 1 shown, a network device and terminal devices UE1 to UE6 form a communication system. In this communication system, UE1 to UE6 can send uplink data to the network device, and the network device needs to receive the uplink data sent by UE1 to UE6 and send it to UE1 to UE6. In addition, UE4 to UE6 can also form a communication system. In this communication system, the network device can send downlink information to UE1, UE2, and UE5. UE5 can also send downlink information to UE4 and UE6.

[0068] In the unlicensed band, the transmitting node needs to use the unlicensed band through a contention-based manner. Referring to the definition of the European Telecommunications Standards Institute (ETSI), the channel access types in the unlicensed band mainly include load-based equipment (LBE) and frame-based equipment (FBE). Or rather, there are two channel detection mechanisms on the unlicensed band, namely the frame structure-based (i.e., FBE-based) channel detection mechanism and the load-based (LBE-based) channel detection mechanism.

[0069] The load-based channel detection mechanism means that when traffic arrives at the device, it triggers an initial CCA detection. If the device initially detects through CCA that the channel state is idle, it can immediately occupy the channel, and the channel occupancy time is pre-configured. If the device initially detects through CCA that the channel state is busy, it needs to generate a defer period. If the channel state is detected as busy during the defer period, it continues to generate a defer period until the channel state is detected as idle during a certain defer period and then enters the extended channel idle assessment (ECCA).

[0070] ECCA refers to generating a random number N of channel detection backoffs for CCA detection time between (1, q), where q is pre-configured. If during this period, the channel state is detected as busy during the CCA detection time, a postponement duration also needs to be generated until the channel is detected as idle within a certain postponement duration, and then the ECCA process continues. After the device detects the channel as idle for N times of CCA detection time, it can occupy the channel, and the channel occupancy time is also pre-set.

[0071] The channel detection mechanism based on FBE means: setting a period, and performing a listen before talk (LBT) channel detection at a fixed position in each period. For example, the CCA mechanism can be used for channel detection. The channel detection time is also called the channel clear assessment (CCA) detection time. If a device detects that the channel state is idle during the CCA detection time, the device can immediately occupy the channel and obtain the channel occupancy time. The channel occupancy time is a pre-configured fixed value. During the channel occupancy time, the device can transmit. When the device needs to transmit after exceeding the channel occupancy time, it performs channel detection again. If the device detects that the channel state is not idle during the CCA detection time, the device cannot occupy the channel during this period and continues to perform the LBT channel detection at the fixed position in the next period.

[0072] See Figure 2, which is a schematic diagram of a channel detection mechanism based on FBE. The initiating device transmits based on FBE frames, and the transmission period of FBE frames is called the fixed frame period (FFP). One fixed frame period can be regarded as one FBE frame, that is, in the FBE mode, the initiating device transmits based on FBE frames. One FFP consists of two parts: the channel occupancy period (COT) and the idle period. The duration of the FFP is between 1 ms and 10 ms. Among them, the COT is used for the FBE initiating device to send signals, and the idle period is used for the FBE initiating device to perform CCA. For the first FFP, the initiating device will back off for a period of time before the start of the COT and perform CCA. If the evaluated channel state is idle, the initiating device can send signals during the subsequent channel occupancy time. In some embodiments, the initiating device can share the signal transmission opportunity with another or multiple devices during the COT, and these devices are called responding devices. If the interval between the time points when the initiating device and the responding device send signals is less than 16 μs, the responding device does not perform CCA, otherwise the responding device needs to perform CCA for a duration of not less than 9 μs.

[0073] The parameters of the FFP are configured relative to the initiating device and can be understood as being bound to the initiating device. In other words, for different initiating devices, the configuration of the FFP can be different. The initiating device can be a network device or a terminal device.

[0074] In the NR system, the length of the system frame is 10 ms, and the range of the system frame number (SFN) is 0 to 1023. One system frame includes 10 subframes, each subframe has a length of 1 ms, and the subframe numbers within one system frame are 0 to 9. Each subframe includes several time slots, and the number of time slots included in each subframe is related to the subcarrier spacing (SCS).

[0075] Considering that in the FBE mode, the device (network device or terminal device) transmits signals based on a fixed frame format. This application provides a method for uplink resource configuration based on the FBE mode, such as Figure 3 Any one or more steps in the shown process can form the solution to be protected by this application. For example, taking the network device as the execution entity, S410 and S420 can form a solution; taking the terminal device as the execution entity, S430 and S440 can form a solution. The method includes:

[0076] S410, the network device determines the FFP configuration information of the terminal device. The FFP configuration information is used to indicate the FFP configuration of the terminal device.

[0077] As can be seen from the previous description, COT and Idle Period are included in FFP. The network device determines (or configures) the duration of the COT and the duration of the idle period of the terminal device. The FFP configuration information is used to indicate the duration of the COT and the duration of the idle period of the terminal device. The COT is used for the terminal device to transmit signals. Among them, the signals transmitted by the terminal device can be terminal signal receiving signals or terminal device sending signals.

[0078] In some embodiments, the network device may not indicate the duration of the idle period, but indicate the duration of the FFP. Through the duration of the FFP and the duration of the COT, the terminal device can obtain the duration of the idle period.

[0079] The network device can determine the configuration parameters of FFP according to the quality of service (QoS) of the service to be transmitted, different service types (for example: enhanced mobile broadband (eMBB) service, or ultra-reliable low-latency communication (URLLC) service, massive machine-type communications (mMTC) service, etc.), such as: the duration of the COT, the duration of the idle period, or the duration of the FFP. Not limited to the above examples, the network device can also determine the FFP configuration information based on other factors.

[0080] When the uplink service demand changes, the network device can reconfigure FFP and send the reconfigured FFP configuration information to the terminal device, so as to reconfigure the FFP of the terminal device. Exemplarily, the change in uplink service demand may refer to a change in the quality of service of the uplink service. The network device can reconfigure the FFP configuration information according to the different QoS of different services; or the change in uplink service demand may refer to a change in the type of the uplink service. Since different service types have different requirements for latency and throughput, etc., the base station can reconfigure the FFP configuration information based on different service types and perform RRC reconfiguration. Thus, the service demand can be met and a more flexible configuration can be achieved.

[0081] S420, the network device sends the FFP configuration information to the terminal device.

[0082] Among them, the FFP configuration information can be carried in radio resource control signaling. Specifically, the content included in the FFP configuration information can be reflected in the fields of the RRC signaling. For example, a FBE ConfiguredGrantConfig can be added to the RRC signaling.

[0083] S430, the terminal device receives the FFP configuration information from the network device.

[0084] S440, the terminal device parses the FFP configuration information and obtains the FFP configuration.

[0085] Different from the authorized frequency band, when the terminal device transmits on the unlicensed frequency band, it will first compete for the channel and start transmitting after competing for the channel. In the embodiments of the present application, the terminal device obtains the FFP configuration information from the network device, can know the configuration of the FFP to perform subsequent actions, and solves the technical problem of the FFP configuration of the terminal device in the FBE mode. Moreover, when the service type changes, the network device can reconfigure the FFP of the terminal device to meet the requirements of different service types and improve the communication efficiency.

[0086] The following gives an exemplary description of the FFP configuration information, which may include one or more of the following fields:

[0087] 1) The time domain offset of the FFP of the terminal device relative to the system frame or relative to the FFP of the network device. This field is used to indicate the starting position of the FFP of the terminal device and can be expressed as "TimeDomainoffset". Optionally, this field is used to indicate the time domain offset of the starting boundary of the FFP of the terminal device relative to the starting boundary of system frame 0, or this field is used to indicate the time domain offset of the starting boundary of the FFP of the terminal device relative to the starting boundary of the FFP0 of the network device. Exemplarily, the offset can be in units of symbols. For example, when the value of this field is 1, it means that the FFP is offset by 1 symbol in the time domain relative to the starting boundary of system frame 0 or relative to the starting boundary of the FFP0 of the network device; or, the offset can be an absolute time value. For example, when the value of this field is 1, the FFP is offset by 1 ms in the time domain relative to the starting boundary of system frame 0 or relative to the starting boundary of the FFP0 of the network device. It can be understood that the time domain offset can be a positive number, meaning that the starting boundary of the FFP of the terminal device is after system frame 0 or after the starting boundary of the FFP0 of the network device; or the time domain offset can be a negative number, meaning that the starting boundary of the FFP of the terminal device is before the starting boundary of system frame 0 or before the starting boundary of the FFP0 of the network device. As Figure 4 shown, the starting boundary of the FFP of the terminal device is before the starting boundary of the FFP0 of the network device.

[0088] For the terminal device, after obtaining the time domain offset of the FFP relative to system frame 0 or relative to the network device's FFP, the starting position of the FFP can be known. In other words, it can be known when the FFP starts. It can be understood that the starting boundary of system frame 0 or the network device's FFP0 is only an exemplary reference starting point for confirming the starting position of the terminal device's FFP. In other embodiments, this reference starting point can also be located in a system frame other than system frame 0, or an FFP other than the network device's FFP0. This reference starting point can also be the ending boundary of the system frame or the network device's FFP, or a certain time point in system frame 0 or the network device's FFP0.

[0089] 2) The duration of the channel occupancy time (COT) of the FFP. This field is used to indicate the time length of the COT in the terminal device's FFP and can be expressed as "COT duration". Exemplarily, the time length of the COT can be in units of symbols. For example, when the value of this field is 5, it means the time length of the COT can be 5 symbols; or, the time length of the COT can be an absolute time value. For example, when the value of this field is 5, it means the time length of the COT can be 5 ms. It can be understood that this absolute time value can be in other time units. For the terminal device, according to this field, the duration of the COT in the FFP can be obtained from the network device. In different embodiments, the COT is used for the terminal device to send signals and can also be used for the terminal device to receive signals. Or it can be said that the COT is used for the terminal device to perform uplink transmission, and the COT can also be used for the terminal device to perform downlink transmission.

[0090] 3) The duration of the idle period. This field is used to indicate the duration of the idle period in the FFP and can be expressed as "IdlePeriod". Exemplarily, the duration of the idle period can be in units of symbols. For example, when the value of this field is 2, it means the duration of the idle period is 2 symbols; or, the duration of the idle period can be an absolute time value. For example, when the value of this field is 2, it means the duration of the idle period is 2 ms. It can be understood that this absolute time value can be in other time units. For the terminal device, according to this field, the duration of the idle period in the FFP can be obtained from the network device. This idle period can be used for the terminal device to perform channel sensing before transmission.

[0091] 4) The FFP duration of the terminal device. This field is used to indicate the duration of the FFP. Exemplarily, the duration of the FFP can be in units of symbols. For example, when the value of this field is 140, it means the duration of the FFP is 140 symbols; or, the duration of the FFP can be an absolute time value. For example, when the value of this field is 10, it means the duration of the FFP is 10 ms. It can be understood that this absolute time value can be in other time units. For the terminal device, the duration of the FFP can be obtained from the network device according to this field. In some embodiments, even when the duration of the idle period is not included in the FFP configuration information, the terminal device can obtain the duration of the idle period based on the duration of the FFP and the duration of the COT.

[0092] 5) The start and length indicator value (SLIV) of the physical uplink shared channel (PUSCH). This field is used to indicate the starting symbol offset S of the PUSCH signal and the number of symbols L included in the PUSCH. In other words, this field is used to indicate when the terminal device starts to transmit the PUSCH and the duration for which the PUSCH lasts. Exemplarily, the initial value of S is 0, which means that when LBT is successful, the terminal device will immediately transmit the PUSCH in the COT. The value range of L is 1 to 4, indicating that the length of the PUSCH can be 1 to 4 symbols. The terminal device can perform consecutive transmissions of one or more PUSCHs in the COT. For the network device, one PUSCH represents a complete demodulation unit. In some embodiments, the PUSCH is transmitted continuously, and the subsequent PUSCH is transmitted right next to the first PUSCH. For the terminal device, by obtaining the start and SLIV of the PUSCH from the network device, it can know how to transmit the PUSCH in the COT.

[0093] In another embodiment, the FFP configuration information may further include self - contained hybrid automatic repeat request (HARQ) resource configuration. This field can be expressed as "Self - contain HARQ resource configuration". As Figure 5As shown in the figure, the network device configures a period of time-domain resources in the COT of the terminal device. This time-domain resource is used for the terminal device to receive the HARQ information sent by the network device. The HARQ information is used to indicate the demodulation result of the PUSCH sent in the current COT, which is an acknowledgement (ACK) or a negative acknowledgement (NACK). Optionally, this time-domain resource can also be used to feedback the downlink feedback indication (DFI) information of the terminal device. The DCI is used to feedback the demodulation result of the PUSCH.

[0094] Thus, the terminal device can receive the feedback from the network device in advance and determine whether retransmission is required according to the feedback result, which can improve the communication efficiency.

[0095] It can be understood that the FFP configuration information may include more or fewer fields. For example, in the case where the network device does not configure parameters regarding the BWP (such as frequency-domain resource indication information), the FFP configuration information may carry the following information:

[0096] 1) The bandwidth part (BWP) index identifier (ID) of the terminal device, which is used to indicate the BWP index ID allocated to the terminal device for FFP. The BWP of the terminal device refers to a continuous bandwidth resource allocated by the network side to the terminal device. Different terminal devices can be configured with different BWPs, and the channel resources of the terminal device are allocated and scheduled within the BWP;

[0097] 2) The subcarrier spacing of the BWP of the terminal device. This subcarrier spacing can determine the symbol length. For example, if the PUSCH occupies several symbols, the length of the PUSCH can be determined;

[0098] 3) The frequency-domain resource position indication of the BWP of the terminal device. This frequency-domain resource position indication can be expressed as "FrequencyDomainAllocation".

[0099] In some embodiments, the network device schedules the terminal device to trigger the terminal device to perform transmission. This method can be referred to as scheduled uplink (SUL), which refers to the mechanism in which the network device dynamically schedules the terminal device to perform uplink transmission, and the terminal device sends an uplink signal according to the scheduling of the network device. In one scheduling, the network device can schedule multiple PUSCHs. A further description of the Figure 3 shown method is provided.

[0100] In S410, the network device further determines first FFP scheduling information, where the first FFP scheduling information is used to schedule the terminal device to perform transmission based on the FFP configured according to the first FFP configuration information.

[0101] In S420, the network device sends the first FFP scheduling information to the terminal device.

[0102] In S430, the terminal device receives the first FFP scheduling information from the network device and attempts to perform transmission according to the FFP scheduling information. This is because, in the unlicensed band, the terminal device will first perform LBT and perform transmission after competing for the channel. After obtaining the FFP scheduling information from the network device, the terminal device performs transmission according to the time domain position indicated by the FFP scheduling information.

[0103] Exemplarily, the FFP configuration information and the first FFP scheduling information can be carried in different signaling. For example, the FFP configuration information is carried in the RRC signaling, while the first FFP scheduling information is carried in the DCI.

[0104] After completing the FFP configuration of the terminal device through the FFP configuration information, the terminal device already knows the structure of the FFP and knows how to perform transmission, but will perform transmission after the network device allocates time domain resources. In other words, the transmission of the terminal device requires the scheduling of the network device. The network device sends DCI to the terminal device to trigger the terminal device to perform LBT and perform transmission after competing for the channel.

[0105] In one design, the network device schedules transmission resources for the terminal device, and the transmission resources are one FFP in the time domain. It can be seen that the transmission resources are time domain resources. It can be understood that the network device schedules the terminal device to perform transmission in one FFP. The first FFP scheduling information may include a first offset, where the first offset is used to indicate the offset of the start boundary of the time domain resources of the terminal device scheduled by the network device relative to the start boundary of the time domain resources when the network device sends the first FFP scheduling information, or it can also be said that the first offset is used to indicate the offset of the start boundary of the time domain resources of the terminal device scheduled by the network device relative to the start boundary of the time domain resources when the network device sends DCI. Exemplarily, the unit of the first offset can be a symbol, or the unit of the first offset can be an FFP, and the first offset can be expressed as "TimeoffsetToGrant".

[0106] Optionally, the first offset can also be used to indicate the offset of the start boundary of the COT scheduled by the network device relative to the start boundary of the time domain resources when the network device sends the first FFP scheduling information. In this case, the transmission resources allocated by the network device can be one COT. In other words, the network device schedules the terminal device to perform transmission in one COT.

[0107] Therefore, after receiving the first FFP scheduling information, the terminal device can obtain the time-domain resources allocated by the network device, complete LBT before the start position of the time-domain resources, and perform transmission after competing for the channel.

[0108] For example, please refer to Figure 6 , the network device sends DCI to the terminal device within a period of time-domain resources. Optionally, the DCI can be an uplink grant (UL grant). In Figure 6 's example, the network device schedules an FFP, and the terminal device determines the FFP for transmission according to the first offset confirmation included in the DCI, completes LBT before the start boundary of the FFP, and performs transmission after competing for the channel.

[0109] In the case of scheduling an FFP, more flexible scheduling can be achieved. On the other hand, since the network device sends less FFP scheduling information to the terminal device, the signaling overhead can also be reduced.

[0110] In another design, the network device schedules the time-domain resources of the terminal device, and the time-domain resources include multiple FFPs in the time domain. It can be understood that the network device schedules the terminal device to perform transmission in multiple FFPs. The first FFP scheduling information may include the number of transmissions and a second offset. The number of transmissions is used to indicate the number of FFPs scheduled by the network device and can be expressed as "Times of UL transmission". The second offset is used to indicate the offset of the start boundary of the first FFP among the multiple FFPs scheduled by the network device relative to the start boundary of the time-domain resources when the network device sends the FFP scheduling information, or the second offset is used to indicate the offset of the time-domain resources of the terminal device scheduled by the network device relative to the start boundary of the time-domain resources when the network device sends the first FFP scheduling information. Exemplarily, the unit of the second offset can be a symbol, or the unit of the second offset can be an FFP, and the second offset can be expressed as "TimeoffsetToGrant".

[0111] Optionally, the number of transmissions is used to indicate the number of COTs allocated by the network device, which can be expressed as "Times of UL transmission". The second offset is used to indicate the offset of the start boundary of the first COT among multiple COTs scheduled by the network device relative to the start boundary of the time domain resource in which the network device sends the FFP scheduling information. It can be understood that the second offset is used to indicate the offset of the start boundary of the transmission resource allocated by the network device to the terminal device. In this case, the transmission resources allocated by the network device can also be multiple COTs. In other words, the network device schedules the terminal device to transmit in multiple COTs. Exemplarily, the unit of the second offset can be a symbol, or the unit of the second offset can be a COT, and the second offset can be expressed as TimeoffsetToGrant.

[0112] Since the network device schedules the terminal device for multiple FFP or COT, even if the terminal device fails in LBT before an FFP or COT and does not compete for the channel, it still has the opportunity to perform LBT again. Please refer to Figure 7 , the network device sends DCI to the terminal device within a time domain resource. The network device schedules two FFP: FFP_1 and FFP_2. The terminal device obtains the allocated time domain resources from the DCI and performs LBT before the start boundary of FFP_1. The LBT fails, and the terminal device cannot transmit. The terminal device can perform LBT before the start boundary of FFP_2, that is, within the Idle Period of FFP_1. The LBT is successful, and the terminal device competes for the channel to transmit.

[0113] It can be seen that in the case of scheduling multiple FFP or COT, due to multiple transmission opportunities, even if the LBT fails, the terminal device still performs LBT in the next FFP, thus shortening the access time of the terminal device.

[0114] In some other embodiments, the network device may be configured to carry second FFP configuration information in the signaling carrying the FFP configuration information, that is, the FFP configuration information and the second FFP scheduling information can be carried in the same signaling, such as in the RRC signaling. This method can be referred to as automatic uplink (AUL), which refers to the mechanism by which the network device semi-statically schedules the periodic uplink transmission of the terminal device. After receiving the activation signaling, the terminal device can periodically send uplink signals in the pre-configured time domain resources until it receives the deactivation signaling. That is, the terminal device starts to send uplink signals after receiving the activation signaling and stops sending after receiving the deactivation signaling. The time domain resources may include multiple FFP, and the number of PUSCHs transmitted in the COT of multiple FFP is configurable. The number of PUSCHs transmitted in the COT of different FFP may be the same or different.

[0115] The second FFP scheduling information may include an Automatic Uplink (AUL) time domain resource pattern period, the unit of this period being the length of an FFP. What the automatic uplink time domain period indicates is the number of FFPs. For example, when the value of this field is N, it means that there are N FFPs in one time domain resource period, where N is a positive integer greater than or equal to 1.

[0116] When the FFP configuration information and the FFP scheduling information are carried in the same signaling, the terminal device can configure the structure of the FFP and schedule the terminal device for transmission through one signaling, which can save signaling overhead.

[0117] Optionally, the FFP scheduling information may further include an AUL time domain resource pattern bit map, which is used to indicate which FFPs in the AUL time domain resource period are used for uplink transmission. The bit value corresponding to a certain FFP is used to indicate whether the corresponding FFP is a valid uplink transmission. For example, when the bit is 1, it means that the corresponding FFP is a valid uplink transmission, and when the bit is 0, it means that the corresponding FFP is prohibited from being used for uplink transmission; or when the bit is 0, it means that the corresponding FFP is a valid uplink transmission, and when the bit is 1, it means that the corresponding FFP is prohibited from being used for uplink transmission. In some embodiments, the network device may allocate the time domain resources corresponding to the FFPs prohibited from being used for uplink transmission to other terminal devices or use them by itself. That is to say, the network device schedules other terminal devices or transmits by itself on the time domain resources where the FFPs prohibited from being used for uplink transmission are located. It can be understood that, not limited to uplink transmission, FFPs can also be used for downlink transmission.

[0118] Please refer to Figure 8 , which is a schematic diagram of an AUL time domain resource period. The start boundary of this AUL time domain resource period has an offset relative to system frame 0, and this offset is indicated by TimeDomainOffset in the FFP configuration information. This AUL time domain resource period includes N FFPs, denoted as FFP_1, FFP_2... FFP_N, and each FFP includes a COT and an idle period. In Figure 8In the example, the AUL time-domain resource pattern bitmap is 010101...01, and the bit values 0 and 1 are set cyclically. Here, 0 indicates that the corresponding FFP is prohibited from being used for uplink transmission, and 1 indicates that the corresponding FFP is valid for uplink transmission. Taking FFP_1 and FFP_2 as examples, where FFP_1 corresponds to the first bit in the bitmap, and this bit is 0, indicating that FFP_1 is prohibited from being used for transmission, so the terminal device does not perform uplink transmission on FFP_1; FFP_2 corresponds to the second bit in the bitmap, and this bit is 1, indicating that FFP_2 is valid for uplink transmission, so the terminal device performs LBT before the start of the COT of FFP_2 and performs uplink transmission when the LBT is successful.

[0119] In yet another embodiment, the network device can also configure and schedule the FFP using the fields in the ConfiguredGrantConfig in the RRC signaling. In this case, the network device reinterprets the RRC signaling, and the terminal device reinterprets the fields in the RRC signaling. Exemplarily, the terminal device reinterprets the following fields in the RRC signaling:

[0120] 1) TimeDomainOffset, which is used to represent the offset of the FFP of the terminal device relative to the system frame or relative to the FFP of the network device. In ConfiguredGrantConfig, TimeDomainOffset is used to indicate the offset of the transmission resources scheduled by the network device relative to the start of system frame 0, and this offset is in units of time slots. In this embodiment, this offset can be the offset of the start boundary of the FFP relative to the start boundary of system frame 0 or relative to the start boundary of the network device's FFP0. Exemplarily, this offset can be in units of symbols. For example, when the value of this field is 1, it means that the FFP is offset by 1 symbol in the time domain relative to the start boundary of system frame 0 or relative to the start boundary of the network device's FFP0; or, this offset can be an absolute time value. For example, when the value of this field is 1, the FFP is offset by 1 ms in the time domain relative to the start boundary of system frame 0 or relative to the start boundary of the network device's FFP0. It can be understood that this time-domain offset can be a positive number, meaning that the start boundary of the terminal device's FFP is after system frame 0 or after the start boundary of the network device's FFP0; or this time-domain offset can be a negative number, meaning that the start boundary of the terminal device's FFP is before the start boundary of system frame 0 or before the start boundary of the network device's FFP0.

[0121] 2) Time Domain Allocation, which is used to indicate the configuration of the time domain resources of the terminal device that includes the SLIV. In ConfiguredGrantConfig, Time Domain Allocation indicates the configuration of the uplink configured grant including the SLIV in the time domain. In this embodiment, in other words, this field is used to indicate when the terminal device starts to transmit the PUSCH and the duration of the PUSCH. Exemplarily, the initial value of S is 0, which means that when the LBT is successful, the terminal device will immediately transmit the PUSCH in the COT. The value range of L is 1 to 4, indicating that the length of the PUSCH can be 1 to 4 symbols.

[0122] 3) Rep_K, which is used to indicate the number of PUSCHs in the COT of the terminal device's FFP. In this embodiment, based on the following rules, the terminal device can obtain the duration of the COT:

[0123] COT duration = L×Rep_K×symbol_length,

[0124] where L represents the number of symbols in a PUSCH, Rep_K represents the number of PUSCHs in a COT, and symbol_length represents the symbol length corresponding to the subcarrier spacing of the terminal device's BWP.

[0125] Combining the time domain offset and the duration of the COT, the terminal device can obtain the idle duration. Specifically, when the start boundaries of two adjacent COTs are determined, if the duration of the COT is known at this time, the idle duration can be obtained. According to the periodicity in the RRC signaling's ConfiguredGrantConfig, the terminal device can also obtain the time domain resources scheduled by the network device for the terminal device, that is, the time domain resource period.

[0126] After the above re-interpretation, the terminal device can obtain the configuration of the FFP, such as: the start boundary, the duration of the COT, the duration of the idle period, and how the PUSCH is transmitted in the COT.

[0127] Re-interpreting some fields in the ConfiguredGrantConfig as above can save signaling overhead, especially in the scenario where the network device operates based on the FBE mode. It can be understood that the cell corresponding to the network device is a cell based on the FBE mode. In an FBE cell, the network device can use the ConfiguredGrantConfig in the RRC signaling for FFP configuration. When the terminal device discovers that the current cell is an FBE cell, it will re-interpret some fields in the RRC signaling to obtain the FFP configuration.

[0128] The method for resource allocation provided in the application has been described in detail above. Next, a device for resource allocation provided in the application will be introduced.

[0129] See Figure 9 , Figure 9 which is a schematic block diagram of a communication device 500 for resource allocation provided in the application. As Figure 9 shown, the communication device 500 includes a processing unit 510 and a sending unit 520.

[0130] The processing unit 510 is configured to determine the fixed frame period (FFP) configuration information of a terminal device. The FFP is the period used by the terminal device to transmit signals, and the FFP includes a channel occupancy time (COT) and an idle period. The channel occupancy time COT is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT.

[0131] The sending unit 520 is configured to send the fixed frame period (FFP) configuration information to the terminal device.

[0132] The FFP configuration information can refer to the description in the foregoing embodiments and will not be elaborated here.

[0133] In one embodiment, the processing unit 510 is further configured to determine first FFP scheduling information for scheduling the terminal device to transmit in the FFP configured with the FFP configuration information; the sending unit 520 is further configured to send the first FFP scheduling information to the terminal device. The FFP configuration information and the first FFP scheduling information are carried in different signaling. For example, the FFP configuration information is carried in RRC signaling, while the first FFP scheduling information is carried in DCI. The first scheduling information can refer to the description in the foregoing embodiments and will not be elaborated here.

[0134] In another embodiment, the processing unit 510 may configure the second FFP configuration information to be further carried in the signaling carrying the FFP configuration information. The second FFP scheduling information is used to schedule the terminal device to transmit in the FFP configured with the FFP configuration information. For example, the FFP configuration information and the second configuration information are carried in RRC signaling and sent by the sending unit 520. The second configuration information can refer to the description in the foregoing embodiments and will not be elaborated here.

[0135] Optionally, the device 500 may be a chip or an integrated circuit.

[0136] Optionally, the processing unit 510 may be a processor.

[0137] Optionally, the sending unit 520 may be a transceiver, which may include a transmitter and a receiver, and has both receiving and sending functions.

[0138] Optionally, the sending unit 520 may also be an input / output interface, or an input / output circuit.

[0139] Optionally, the sending unit 520 may be a communication interface. For example, an input / output interface, an input interface circuit, and an output interface circuit, etc.

[0140] The apparatus 500 may correspond to the network device in the method embodiment of resource configuration provided in this application. Each unit included in the apparatus 500 is respectively used to implement the corresponding operations and / or processes executed by the network device in each method embodiment.

[0141] For example, the processing unit 510 is used to execute the operations and / or steps implemented inside the terminal device in each method embodiment. For example, the processing unit 510 is used to determine the FFP configuration of the terminal device.

[0142] The sending unit 520 is used to send FFP configuration information, first FFP scheduling information, or second FFP scheduling information, etc. to the terminal device.

[0143] See Figure 10 , Figure 10 which is a schematic block diagram of the communication apparatus 600 for resource configuration provided in this application. As Figure 10 shown, the apparatus 600 includes a processing unit 620 and a transceiver unit 610.

[0144] The transceiver unit 610 is used to receive FFP configuration information from the network device, where the FFP configuration information is used to indicate the FFP configuration of the terminal device, the FFP is the period for the terminal device to transmit signals, the FFP includes a channel occupancy time (COT) and an idle period, the channel occupancy time COT is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT;

[0145] The processing unit 620 is used to parse the FFP configuration information and obtain the FFP configuration.

[0146] The FFP configuration information can be referred to the description in the foregoing embodiments and will not be elaborated here. In one embodiment, the transceiver unit 610 is further configured to receive first FFP scheduling information from a network device, where the first FFP scheduling information is used to schedule the terminal device to perform transmission on the FFP configured with the FFP configuration information. The FFP configuration information and the first FFP scheduling information are carried in different signaling. For example, the FFP configuration information is carried in RRC signaling, while the first FFP scheduling information is carried in DCI. The first scheduling information can be referred to the description in the foregoing embodiments and will not be elaborated here.

[0147] In another embodiment, the transceiver unit 610 is further configured to receive second FFP scheduling information from a network device, where the second FFP scheduling information is used to schedule the terminal device to perform transmission on the FFP configured with the FFP configuration information. For example, the FFP configuration information and the second configuration information are carried in RRC signaling and received by the transceiver unit 610. The second configuration information can be referred to the description in the foregoing embodiments and will not be elaborated here.

[0148] Optionally, the apparatus 600 may be a chip or an integrated circuit.

[0149] Optionally, the transceiver unit 610 may be a transceiver, and the transceiver may include a transmitter and a receiver, and has both receiving and sending functions.

[0150] Optionally, the transceiver unit 610 may also be an input / output interface, or an input / output circuit.

[0151] Optionally, the transceiver unit 610 may be a communication interface. For example, an input / output interface, an input interface circuit, and an output interface circuit, etc.

[0152] Optionally, the processing unit 620 may be a processor.

[0153] The apparatus 600 may correspond to the network device in the method embodiment of resource configuration provided in this application. Each unit included in the apparatus 600 is respectively configured to implement the corresponding operations and / or processes performed by the terminal device in each method embodiment.

[0154] The transceiver unit 610 is configured to perform the steps of receiving messages and / or information from the network device in each method embodiment. For example, the transceiver unit 610 is configured to receive an FFP configuration message, first FFP scheduling information, or second FFP scheduling information, etc. from the network device.

[0155] The processing unit 620 is configured to perform the operations and / or steps implemented inside the terminal device in each method embodiment. For example, the processing unit 620 is configured to determine the FFP configuration of the terminal device according to the FFP configuration message. For example, the duration of the FFP, the COT, and the proportion of the idle period, etc.

[0156] In the embodiments of the present application, the chip may be a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or may also be a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0157] The present application further provides a network device 700, which will be described below in conjunction with Figure 11 for illustration.

[0158] Refer to Figure 11 , Figure 11 which is a schematic structural diagram of the communication device 700 provided by the present application. The communication device 700 is used to implement the functions of the network device in the method embodiments, and it may be a network device or a chip. The communication device 700 includes: a processor 701, a communication module 702, and a memory 703, where:

[0159] The processor 701 is configured to read the program in the memory 703 and execute the following processes:

[0160] The processor 701 is used to determine the fixed frame period (FFP) configuration information of the terminal device. The FFP is the period used by the terminal device to transmit signals, and the FFP includes a channel occupancy time (COT) and an idle period. The channel occupancy time COT is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT;

[0161] The processor 701 is used to control the communication module 702 to send the fixed frame period FFP configuration information to the terminal device.

[0162] The communication module 702 is used to receive signals and / or send signals.

[0163] In one embodiment, the processor 701 is further configured to determine first FFP scheduling information for scheduling the terminal device to perform transmission on the FFP configured by the FFP configuration information; the processor 701 is further configured to control the communication module 702 to send the first FFP scheduling information to the terminal device. The FFP configuration information and the first FFP scheduling information are carried in different signaling. For example, the FFP configuration information is carried in RRC signaling, while the first FFP scheduling information is carried in DCI. The first scheduling information may refer to the description of the foregoing embodiments and will not be elaborated herein.

[0164] In another embodiment, the processor 701 may be configured to further carry second FFP configuration information in the signaling carrying the FFP configuration information, where the second FFP scheduling information is used to schedule the terminal device to perform transmission on the FFP configured by the FFP configuration information. For example, the FFP configuration information and the second configuration information are sent by the communication module 702 in RRC signaling. The second configuration information may refer to the description of the foregoing embodiments and will not be elaborated herein.

[0165] The processor 701, the communication module 702, and the memory 703 are interconnected via a bus; the bus may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc.

[0166] Among them, in Figure 11 the bus architecture may include any number of interconnected buses and bridges, specifically various circuits represented by one or more processors represented by the processor 701 and the memory represented by the memory 703 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and will not be further described herein. The bus interface provides an interface. The communication module 702 may be multiple components, that is, including a transmitter and a communication unit, providing a unit for communicating with various other devices on the transmission medium. Alternatively, the communication module 702 may be a single component, for example, it may be a transceiver or a communication interface on the chip. The processor 701 is responsible for managing the bus architecture and general processing, and the memory 703 may store data used by the processor 701 when performing operations.

[0167] Optionally, the processor 701 may be a central processing unit, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD).

[0168] See Figure 12 , Figure 12 is a schematic structural diagram of a communication device 800 provided by this application. The communication device 800 is used to implement the functions of the network device in the method embodiments, and it may be a network device or a chip. The communication device 800 includes: a processor 801, a communication module 802, and a memory 803, where:

[0169] The processor 801 is configured to read the program in the memory 803 and execute the following processes:

[0170] The processor 801 is configured to receive FFP configuration information from a network device through the communication module 802. The FFP configuration information is used to indicate the FFP configuration of the terminal device. The FFP is the period for the terminal device to transmit signals, and the FFP includes a channel occupancy time (COT) and an idle period. The channel occupancy time COT is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT;

[0171] The processor 801 is configured to parse the FFP configuration information and obtain the FFP configuration.

[0172] The communication module 802 is configured to receive signals and / or send signals.

[0173] The FFP configuration information may refer to the description in the foregoing embodiments and will not be elaborated herein. In one embodiment, the communication module 802 is further configured to receive first FFP scheduling information from a network device. The first FFP scheduling information is used to schedule the terminal device to transmit during the FFP configured by the FFP configuration information. The FFP configuration information and the first FFP scheduling information are carried in different signaling. For example, the FFP configuration information is carried in RRC signaling, while the first FFP scheduling information is carried in DCI. The first scheduling information may refer to the description in the foregoing embodiments and will not be elaborated herein.

[0174] In another embodiment, the communication module 802 is further configured to receive second FFP scheduling information from a network device. The second FFP scheduling information is used to schedule the terminal device to transmit during the FFP configured by the FFP configuration information. For example, the FFP configuration information and the second configuration information are carried in RRC signaling and received by the communication module 802. The second configuration information may refer to the description in the foregoing embodiments and will not be elaborated herein.

[0175] The processor 801, communication module 802, and memory 803 are interconnected via a bus; the bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc.

[0176] Among them, in Figure 12 the bus architecture can include any number of interconnected buses and bridges, specifically, various circuits represented by one or more processors represented by the processor 801 and the memory represented by the memory 803 are linked together. The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, etc., which are well known in the art, so they will not be further described herein. The bus interface provides an interface. The communication module 802 can be multiple components, that is, including a transmitter and a communication unit, providing a unit for communicating with various other devices on the transmission medium. Alternatively, the communication module 702 can be a single component, for example, it can be a transceiver or a communication interface on the chip. The processor 701 is responsible for managing the bus architecture and general processing, and the memory 803 can store the data used by the processor 801 when performing operations.

[0177] Optionally, the processor 801 can be a central processing unit, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD).

[0178] In addition, the present application provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions run on a computer, the computer is caused to execute the corresponding operations and / or processes performed by the network device in each method embodiment.

[0179] The present application provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions run on a computer, the computer is caused to execute the corresponding operations and / or processes performed by the terminal device in each method embodiment.

[0180] The present application further provides a computer program product, the computer program product includes computer program code. When the computer program code runs on a computer, the computer is caused to execute the corresponding operations and / or processes performed by the network device in the resource configuration method provided by the present application.

[0181] The present application also provides a computer program product, which includes computer program code. When the computer program code runs on a computer, it causes the computer to execute the corresponding operations and / or processes performed by the terminal device in the resource configuration method provided by the present application.

[0182] The present application also provides a chip, which includes a processor. The processor is used to call and run the computer program stored in the memory to execute the corresponding operations and / or processes performed by the network device in the resource configuration method provided by the present application.

[0183] Optionally, the chip further includes a memory, and the memory is connected to the processor. The processor is used to read and execute the computer program in the memory.

[0184] Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive signals and / or data that need to be processed, and the processor obtains the signals and / or data from the communication interface and processes them.

[0185] The present application also provides a chip, which includes a processor. The processor is used to call and run the computer program stored in the memory to execute the corresponding operations and / or processes performed by the terminal device in the resource configuration method provided by the present application.

[0186] Optionally, the chip further includes a memory, and the memory is connected to the processor. The processor is used to read and execute the computer program in the memory.

[0187] Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive signals and / or data that need to be processed, and the processor obtains the signals and / or data from the communication interface and processes them.

[0188] Optionally, the communication interface in the above embodiments may be an input / output interface, which may specifically include an input interface and an output interface. Alternatively, the communication interface may be an input / output circuit, which may specifically include an input circuit and an output circuit.

[0189] The memories involved in the above embodiments may be physically independent units, or the memory may also be integrated with the processor.

[0190] In the above embodiments, the processor may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the technical solution of the present application. For example, the processor may be a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, etc. The processor may distribute the control and signal processing functions of the terminal device or the network device among these devices according to their respective functions. In addition, the processor may have the function of operating one or more software programs, and the software programs may be stored in the memory. The functions of the processor may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0191] The memory may be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (RAM), or other types of dynamic storage devices that can store information and instructions. It may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer.

[0192] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0193] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0194] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of devices or units can be in electrical, mechanical, or other forms.

[0195] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0196] In addition, in each embodiment of this application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0197] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the part of the technical solution of this application that contributes to the prior art or part of this technical solution can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of this application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0198] The above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed in this application should be covered by the protection scope of this application. The protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A method for resource allocation in an unlicensed frequency band, characterized in that, it includes: The network device sends fixed frame period (FFP) configuration information to the terminal device. The FFP configuration information is used to indicate the FFP configuration of the terminal device. The FFP is the period for the terminal device to transmit signals. The FFP includes channel occupancy time (COT) and idle period. The channel occupancy time COT is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT; the FFP configuration information includes: the duration of the COT, the start and length indication value (SLIV) of the physical uplink shared channel (PUSCH); wherein, the SLIV is used to indicate the start symbol offset of the PUSCH signal and the number of symbols in the PUSCH; the SLIV is used to indicate the transmission mode of the PUSCH in the COT; the duration of the COT is determined based on the number of symbols in the PUSCH in one COT.

2. The method according to claim 1, characterized in that, the FFP configuration information further includes one or more of the following: The time domain offset of the FFP relative to the system frame or relative to the FFP of the network device, which is used to indicate the start boundary of the FFP of the terminal device; The duration of the idle period of the FFP; The duration of the FFP.

3. The method according to claim 1, characterized in that, the network device also sends FFP scheduling information to the terminal device. The FFP scheduling information is used to schedule the terminal device to transmit in the FFP configured by the FFP configuration information.

4. The method according to claim 3, characterized in that, the FFP scheduling information includes a first offset, and the first offset is used to indicate the offset of the start boundary of the FFP scheduled by the network device relative to the start boundary of the time domain resource when the network device sends the FFP scheduling information.

5. The method according to claim 3, characterized in that, the FFP scheduling information includes the number of transmissions and a second offset. The number of transmissions is used to indicate the number of FFPs scheduled by the network device, and the second offset is used to indicate the offset of the start boundary of the first FFP scheduled by the network device relative to the start boundary of the time domain resource when the network device sends the FFP scheduling information.

6. The method according to claim 3, characterized in that, the FFP scheduling information includes a time domain resource period and a bitmap of the time domain resource pattern. The time domain resource period is used to indicate a time domain resource period to the terminal device. Among them, one time domain resource period contains multiple FFPs, and the bitmap of the time domain resource pattern is used to indicate whether each of the multiple FFPs can be used for the terminal device to transmit.

7. The method according to claim 2, characterized in that, the time domain offset unit of the FFP relative to the system frame or relative to the FFP of the network device is a symbol.

8. The method according to claim 2, characterized in that, the duration of the COT conforms to the following rules: COT duration = L×rep_K×symbol_length; Wherein, L represents the number of symbols in PUSCH within the COT, rep_K represents the number of PUSCH within one COT, and symbol_length represents the length of the symbol in PUSCH.

9. The method according to any one of claims 1 to 8, characterized in that, the FFP configuration information is carried in the radio resource control (RRC) signaling.

10. The method according to claim 3, characterized in that, the FFP scheduling information is carried in the downlink control information (DCI).

11. The method according to any one of claims 3 to 6, characterized in that, the FFP configuration information and the FFP scheduling information are carried in the radio resource control (RRC) signaling.

12. A method for resource configuration in an unlicensed frequency band, characterized in that, comprising: A terminal device receives FFP configuration information from a network device, where the FFP configuration information is used to indicate the FFP configuration of the terminal device. The FFP is a period for the terminal device to transmit signals, and the FFP includes a channel occupancy time (COT) and an idle period. The COT is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT; the FFP configuration information includes: the duration of the COT, the start and length indication value (SLIV) of the physical uplink shared channel (PUSCH); wherein, the SLIV is used to indicate the starting symbol offset of the PUSCH signal and the number of symbols in the PUSCH; the SLIV is used to indicate the transmission mode of the PUSCH within the COT; the duration of the COT is determined based on the number of symbols in the PUSCH within one COT; Parse the FFP configuration information and obtain the FFP configuration.

13. The method according to claim 12, characterized in that, the FFP configuration information further includes one or more of the following: The time domain offset of the FFP relative to the system frame or relative to the FFP of the network device, which is used to indicate the starting boundary of the FFP of the terminal device; The duration of the idle period of the FFP; The duration of the FFP.

14. The method according to claim 12, characterized in that, the terminal device further receives FFP scheduling information from the network device, and the FFP scheduling information is used to schedule the terminal device to transmit within the FFP configured by the FFP configuration information.

15. The method according to claim 14, characterized in that, the FFP scheduling information includes a first offset, and the first offset is used to indicate the offset of the starting boundary of the FFP scheduled by the network device relative to the starting boundary of the time domain resource where the network device sends the FFP scheduling information.

16. The method according to claim 14, characterized in that, The FFP scheduling information includes the number of transmissions and a second offset. The number of transmissions is used to indicate the number of FFPs scheduled by the network device, and the second offset is used to indicate the offset of the start boundary of the first FFP scheduled by the network device relative to the start boundary of the time domain resource when the network device sends the FFP scheduling information.

17. The method according to claim 14, wherein, the FFP scheduling information includes a time domain resource period and a bitmap of the time domain resource pattern. The time domain resource period is used to indicate a time domain resource period to the terminal device. Among them, a time domain resource period contains multiple FFPs, and the bitmap of the time domain resource period pattern is used to indicate whether each of the multiple FFPs can be used by the terminal device for transmission.

18. The method according to claim 13, wherein, the time domain offset unit of the FFP relative to the system frame or relative to the FFP of the network device is a symbol.

19. The method according to claim 13, wherein, the duration of the COT conforms to the following rule: COT duration = L×rep_K×symbol_length; wherein L represents the number of symbols in the PUSCH in the COT, rep_K represents the number of PUSCHs in a COT, and symbol_length represents the length of the symbols in the PUSCH.

20. The method according to any one of claims 12 to 19, wherein, the FFP configuration information is carried in the radio resource control (RRC) signaling.

21. The method according to claim 14, wherein, the FFP scheduling information is carried in the downlink control information (DCI).

22. The method according to any one of claims 14 to 17, wherein, the FFP configuration information and the FFP scheduling information are carried in the RRC signaling.

23. A communication device, wherein, it includes a communication module. Among them, the communication module is used to send fixed frame period (FFP) configuration information to the terminal device. The FFP configuration information is used to indicate the FFP configuration of the terminal device. The FFP is a period for the terminal device to transmit signals. The FFP includes a channel occupancy time (COT) and an idle period. The channel occupancy time COT is used for the terminal device to transmit signals, and the idle period is used for the terminal device to perform LBT; the FFP configuration information includes: the duration of the COT, the start and length indication value (SLIV) of the physical uplink shared channel (PUSCH); wherein, the SLIV is used to indicate the start symbol offset of the PUSCH signal and the number of symbols in the PUSCH; the SLIV is used to indicate the transmission mode of the PUSCH in the COT; the duration of the COT is determined based on the number of symbols in the PUSCH in a COT.

24. The device according to claim 23, wherein, the FFP configuration information includes one or more of the following: The time-domain offset of the FFP relative to the system frame or relative to the FFP of the network device is used to indicate the start boundary of the FFP of the terminal device; The duration of the idle period of the FFP; The duration of the FFP.

25. The device according to claim 23, wherein, The communication module also sends FFP scheduling information to the terminal device, and the FFP scheduling information is used to schedule the terminal device to perform transmission in the FFP configured by the FFP configuration information.

26. The device according to claim 25, wherein, The FFP scheduling information includes a first offset, and the first offset is used to indicate the offset of the start boundary of the FFP scheduled by the communication device relative to the start boundary of the time-domain resource when the communication device sends the FFP scheduling information.

27. The device according to claim 25, wherein, The FFP scheduling information includes the number of transmissions and a second offset. The number of transmissions is used to indicate the number of FFPs scheduled by the communication device, and the second offset is used to indicate the offset of the start boundary of the first FFP scheduled by the communication device relative to the start boundary of the time-domain resource when the communication device sends the FFP scheduling information.

28. The device according to claim 25, wherein, The FFP scheduling information includes a time-domain resource period and a bitmap of the time-domain resource pattern. The time-domain resource period is used to indicate a time-domain resource period to the terminal device, where a time-domain resource period contains multiple FFPs, and the bitmap of the time-domain resource pattern is used to indicate whether each of the multiple FFPs can be used for the terminal device to perform transmission.

29. The device according to claim 24, wherein, The time-domain offset unit of the FFP relative to the system frame or relative to the network device FFP is a symbol.

30. The device according to claim 24, wherein, The duration of the COT conforms to the following rule: COT duration = L×rep_K×symbol_length; where L represents the number of symbols L in the PUSCH in the COT, rep_K represents the number of PUSCHs in a COT, and symbol_length represents the length of the symbols in the PUSCH.

31. The device according to any one of claims 23 to 30, wherein, The FFP configuration information is carried in the radio resource control (RRC) signaling.

32. The device according to claim 25, wherein, The FFP scheduling information is carried in the downlink control information (DCI).

33. The device according to any one of claims 25 to 28, wherein, The FFP configuration information and the FFP scheduling information are carried in the radio resource control (RRC) signaling.

34. The device according to any one of claims 23 to 30, wherein, The communication device is a chip.

35. The device according to any one of claims 23 to 30, wherein, The communication device is a network device.

36. A communication device, characterized in that, it includes a communication module and a processor, wherein: the communication module is used to receive FFP configuration information from a network device, the FFP configuration information is used to indicate the FFP configuration of the communication device, the FFP is the period for the communication device to transmit signals, the FFP includes a channel occupancy time (COT) and an idle period, the channel occupancy time COT is used for the communication device to transmit signals, and the idle period is used for the communication device to perform LBT; the FFP configuration information includes: the duration of the COT, the start and length indication value (SLIV) of the physical uplink shared channel (PUSCH); wherein, the SLIV is used to indicate the start symbol offset of the PUSCH signal and the number of symbols in the PUSCH; the SLIV is used to indicate the transmission mode of the PUSCH in the COT; the duration of the COT is determined based on the number of symbols in the PUSCH in one COT; the processor is used to parse the FFP configuration information and obtain the FFP configuration.

37. The device according to claim 36, characterized in that, the FFP configuration information includes one or more of the following: the time domain offset of the FFP relative to the system frame or relative to the FFP of the network device, which is used to indicate the start boundary of the FFP of the communication device; the duration of the idle period of the FFP; the duration of the FFP.

38. The device according to claim 36, characterized in that, the communication module also receives FFP scheduling information from the network device, and the FFP scheduling information is used to schedule the communication device to transmit in the FFP configured by the FFP configuration information.

39. The device according to claim 38, characterized in that, the FFP scheduling information includes a first offset, and the first offset is used to indicate the offset of the start boundary of the FFP scheduled by the network device relative to the start boundary of the time domain resource where the network device sends the FFP scheduling information.

40. The device according to claim 38, characterized in that, the FFP scheduling information includes the number of transmissions and a second offset, the number of transmissions is used to indicate the number of FFPs scheduled by the network device, and the second offset is used to indicate the offset of the start boundary of the first FFP scheduled by the network device relative to the start boundary of the time domain resource where the network device sends the FFP scheduling information.

41. The device according to claim 38, characterized in that, the FFP scheduling information includes a time domain resource period and a bitmap of the time domain resource pattern, the time domain resource period is used to indicate a time domain resource period to the communication device, wherein, one time domain resource period contains multiple FFPs, and the bitmap of the time domain resource period pattern is used to indicate whether each of the multiple FFPs can be used for the communication device to transmit.

42. The device according to claim 37, characterized in that, the time domain offset unit of the FFP relative to the system frame or relative to the FFP of the network device is a symbol.

43. The apparatus according to claim 37, wherein, the duration of the COT complies with the following rule: COT duration = L×rep_K×symbol_length; wherein L represents the number of symbols in PUSCH in the COT, rep_K represents the number of PUSCHs in one COT, and symbol_length represents the length of the symbol in PUSCH.

44. The apparatus according to any one of claims 36 to 43, wherein, the FFP configuration information is carried in radio resource control (RRC) signaling.

45. The apparatus according to claim 38, wherein, the FFP scheduling information is carried in downlink control information (DCI).

46. The apparatus according to any one of claims 38 to 41, wherein, the FFP configuration information and the FFP scheduling information are carried in RRC signaling.

47. The apparatus according to any one of claims 36 to 43, wherein, the communication apparatus is a chip.

48. The apparatus according to any one of claims 36 to 43, wherein, the communication apparatus is a terminal device.

49. A computer-readable storage medium, wherein, a software program is stored in the storage medium, and when the software program is read and executed by one or more processors, the method for resource configuration according to any one of claims 1 to 11 can be implemented.

50. A computer-readable storage medium, wherein, a software program is stored in the storage medium, and when the software program is read and executed by one or more processors, the method for resource configuration according to any one of claims 12 to 22 can be implemented.

51. A communication apparatus, wherein, it includes a unit for executing the method for resource configuration according to any one of claims 1 to 11.

52. A communication apparatus, wherein, it includes a unit for executing the method for resource configuration according to any one of claims 12 to 22.

53. A computer program product, wherein, computer program code is stored thereon, and when the computer program code runs on a communication apparatus, the communication apparatus is caused to execute the method for resource configuration according to any one of claims 1 to 11.

54. A computer program product, wherein, computer program code is stored thereon, and when the computer program code runs on a communication apparatus, the communication apparatus is caused to execute the method for resource configuration according to any one of claims 12 to 22.

Images