Information transmission method and device, terminal and network side equipment

Abstract

The invention discloses an information transmission method and device, a terminal and network side equipment, and belongs to the technical field of communication, and the information transmission method comprises the steps that the terminal sends first information; and / or the terminal determines first information; wherein the first information comprises at least one of the following items: an allocation mode of control resources and a scheduling relationship corresponding to the control resources; the first information is related to at least one resource object, and the resource object is associated with or comprises at least one frequency domain object.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to an information transmission method, device, terminal and network side equipment. Background Art

[0002] In 4G and 5G, if fragmented spectrum is to be used, carrier aggregation (CA) is the traditional solution for operators and terminals to aggregate spectrum, that is, different continuous spectrums are used as one carrier. However, the existing CA mechanism regards each carrier as an independent service cell and assumes that each carrier is deployed independently. The independent management of each carrier will bring unnecessary overhead and efficiency loss (such as independent control signaling, public signaling, etc.). This also brings unnecessary processes and delays (such as synchronization, secondary cell (SCell) addition / release / activation / measurement / mobility, etc.). In addition, the CA mechanism is only beneficial to user equipment (UE) in the connected mode radio resource control connected state (RRC_connected), that is, the RRC connection with the network is completed, but not to UE in the idle mode / inactive mode radio resource control idle state or inactive state (RRC_idle / inactive, such as initial access / small data transmission (SDT)).

[0003] Therefore, the introduction of flexible resource objects (such as flexible cells) can flexibly and efficiently utilize adjacent non-contiguous spectrum from the perspective of L1 / L2 / L3 signaling, processes and cell management. It is beneficial to UEs in both CONNECTED and IDLE states, thereby improving user-perceived data rates, energy saving, system capacity and coverage. It also simplifies network management complexity and improves energy efficiency. In addition, these narrow-bandwidth carriers cannot carry control channel elements (CCE) with higher aggregation levels. For example, CCE AL 16 requires a maximum of 96 resource blocks (RB). This is not conducive to the transmission of control information at the edge of the cell and reduces coverage. Narrow-bandwidth carriers may bring a higher probability of conflict in the Physical Downlink Control Channel (PDCCH). Therefore, 6G and later communication systems will support the design of flexible resource objects to configure multiple carriers / frequency parts / bands / subbands; how to achieve the transmission of control resources under flexible resource objects is an urgent problem to be solved. Summary of the invention

[0004] An embodiment of the present application provides an information transmission method, apparatus, terminal, and network-side device to achieve the transmission of control resources under flexible resource objects.

[0005] In a first aspect, an information transmission method is provided. The method includes:

[0006] The terminal sends the first information; and / or

[0007] The terminal obtains the first information;

[0008] Wherein, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources;

[0009] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency-domain object.

[0010] In a second aspect, an information transmission apparatus is provided, which is applied to a terminal and includes:

[0011] A first transmission module for sending the first information; and / or

[0012] Obtain the first information;

[0013] Wherein, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources;

[0014] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency-domain object.

[0015] In a third aspect, an information transmission method is provided. The method includes:

[0016] The network-side device receives the first information; and / or

[0017] The network-side device sends the first information;

[0018] Wherein, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources;

[0019] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency-domain object.

[0020] In a fourth aspect, an information transmission apparatus is provided, which is applied to a network-side device and includes:

[0021] A second transmission module for receiving the first information; and / or

[0022] Send the first information;

[0023] Wherein, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources;

[0024] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency domain object.

[0025] In a fifth aspect, a terminal is provided, including a processor and a memory. The memory stores a program or instruction that can run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0026] In a sixth aspect, a terminal is provided, including a processor and a communication interface. Wherein, the communication interface is used to send the first information; and / or

[0027] Obtain the first information;

[0028] Wherein, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources;

[0029] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency domain object.

[0030] In a seventh aspect, a network-side device is provided, including a processor and a memory. The memory stores a program or instruction that can run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the third aspect are implemented.

[0031] In an eighth aspect, a network-side device is provided, including a processor and a communication interface. Wherein, the communication interface is used to receive the first information; and / or

[0032] Obtain the first information;

[0033] Wherein, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources;

[0034] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency domain object.

[0035] In a ninth aspect, a communication system is provided, including: a terminal and a network-side device. The terminal can be used to execute the steps of the method described in the first aspect, and the network-side device can be used to execute the steps of the method described in the third aspect.

[0036] In a tenth aspect, a readable storage medium is provided. The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect or the third aspect are implemented.

[0037] In an eleventh aspect, a chip is provided, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run programs or instructions to implement the steps of the method described in the first aspect or the third aspect.

[0038] In a twelfth aspect, a computer program / program product is provided. The computer program / program product is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect or the third aspect.

[0039] In the embodiments of the present application, by sending and / or obtaining the allocation method of control resources and / or the scheduling relationship corresponding to the control resources related to at least one resource object, the configuration of control resources under flexible resource objects is realized, and then the transmission of control resources is realized, improving the performance of the communication system. Description of the Drawings

[0040] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0041] Figure 2 is one of the schematic flowcharts of the information transmission method in the embodiments of the present application;

[0042] Figure 3 is a schematic diagram of the scheduling relationship under type A when there is only one frequency domain object in the resource object with control resources or partial control resources;

[0043] Figure 4 is a schematic diagram of the scheduling relationship under type B when there is only one frequency domain object in the resource object with control resources or partial control resources;

[0044] Figure 5 is one of the schematic diagrams of the scheduling relationship under type A when there can be at least one frequency domain object in the resource object with control resources;

[0045] Figure 6 is one of the schematic diagrams of the scheduling relationship under type B when there can be at least one frequency domain object in the resource object with control resources;

[0046] Figure 7 is the second schematic diagram of the scheduling relationship under type A when there can be at least one frequency domain object in the resource object with control resources;

[0047] Figure 8 is the third schematic diagram of the scheduling relationship under type A when there can be at least one frequency domain object in the resource object with control resources;

[0048] Figure 9 It is the second schematic diagram of the scheduling relationship under type B when there is control resource on at least one frequency-domain object in the resource object;

[0049] Figure 10 It is the first schematic diagram of the scheduling relationship under type A when there is a part of control resource on at least one frequency-domain object in the resource object;

[0050] Figure 11 It is the first schematic diagram of the scheduling relationship under type B when there is a part of control resource on at least one frequency-domain object in the resource object;

[0051] Figure 12 It is the second schematic diagram of the scheduling relationship under type A when there is a part of control resource on at least one frequency-domain object in the resource object;

[0052] Figure 13 It is the third schematic diagram of the scheduling relationship under type A when there is a part of control resource on at least one frequency-domain object in the resource object;

[0053] Figure 14 It is the second schematic diagram of the scheduling relationship under type B when there is a part of control resource on at least one frequency-domain object in the resource object;

[0054] Figure 15 It is the second schematic diagram of the process of the information transmission method in the embodiment of the present application;

[0055] Figure 16 It is the first schematic diagram of the module of the information transmission device in the embodiment of the present application;

[0056] Figure 17 It is the schematic diagram of the structure of the terminal in the embodiment of the present application;

[0057] Figure 18 It is the second schematic diagram of the module of the information transmission device in the embodiment of the present application;

[0058] Figure 19 It is the schematic diagram of the structure of the network-side device in the embodiment of the present application;

[0059] Figure 20 It is the schematic diagram of the structure of the communication device in the embodiment of the present application. Detailed implementation manners

[0060] Next, the technical solutions in the embodiments of the present application will be clearly described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art shall fall within the protection scope of the present application.

[0061] The terms "first", "second", etc. in this application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, so that the embodiments of this application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are usually of the same type, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "or" in this application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0062] The term "indicate" in this application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly tells the receiver specific information, operations to be performed, request results, etc. in the sent indication; an indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0063] It is worth pointing out that the technology described in the embodiments of this application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technology can be used not only in the above-mentioned systems and radio technologies, but also in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and the NR term is used in most of the following descriptions, but these technologies can also be applied to systems other than the NR system, such as the 6th generation (6th Generation, 6G) communication system.

[0064] Figure 1The block diagram of a wireless communication system to which the embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), a game console, a personal computer (PC), a teller machine or a self-service machine, etc. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle user equipment can also be referred to as a vehicle terminal, a vehicle controller, a vehicle module, a vehicle component, a vehicle chip or a vehicle unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. Among them, the access network device can also be referred to as a radio access network (RAN) device, a radio access network function or a radio access network unit. The access network device can include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home Node B (HNB), home evolved Node B, Transmission Reception Point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0065] The core network device may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), etc. It should be noted that in the embodiments of this application, only the core network devices in the NR system are taken as examples for introduction, and the specific types of core network devices are not limited.

[0066] The related technologies of the embodiments of this application are described as follows.

[0067] I. Bandwidth Part (BWP)

[0068] In New Radio (NR), the network configures Bandwidth Part (BWP) and / or carrier for User Equipment (UE) to perform data transmission. The bandwidth of the UE can change dynamically. For example, at the first moment, the traffic volume of the UE is large, and the system configures a large bandwidth (BWP1) for the UE; at the second moment, the traffic volume of the UE is small, and the system configures a small bandwidth (BWP2) for the UE to meet the basic communication requirements; at the third moment, the system discovers that there is a large range of frequency selective fading within the bandwidth where BWP1 is located, or the resources within the frequency range where BWP1 is located are relatively scarce, so a new bandwidth (BWP3) is configured for the UE.

[0069] Each BWP not only has different frequency points and bandwidths, but each BWP can correspond to different configurations. For example, the subcarrier spacing, Cyclic Prefix (CP) type, SSB (PSS / SSS PBCH Block) period, etc. of each BWP can be configured differently to adapt to different services.

[0070] The technical advantages of BWP are mainly in four aspects:

[0071] 1. The UE does not need to support the full bandwidth, only needs to meet the minimum bandwidth requirement, which is beneficial to the development of low-cost terminals;

[0072] 2. When the traffic volume of the UE is small, the UE can switch to operate at a low bandwidth, which can significantly reduce power consumption;

[0073] 3. 5G technology is forward compatible. When new technologies are added to 5G, the new technologies can be directly run on the new BWP, ensuring the forward compatibility of the system;

[0074] 4. Adapt to service needs and dynamically configure BWP for services.

[0075] II. Control Resource Set (CORESET) and Search Space

[0076] CORESET describes the frequency domain characteristics of the Physical Downlink Control Channel (PDCCH) blind detection resources, and the search space represents the time domain characteristics of the PDCCH blind detection resources, such as period and offset, the number of time slots monitored per period, and the starting symbol within each time slot.

[0077] A series of Physical Resource Blocks (PRBs) within the frequency domain of CORESET, the UE attempts to blindly detect Downlink Control Information (DCI) within these PRBs, where:

[0078] The PRB can be continuous or discontinuous;

[0079] A CORESET can occupy one or more consecutive symbols in the time domain: {1, 2, 3};

[0080] For example, when there is one symbol, the resource element group (REG) bundle size can be {2, 6};

[0081] For example, when there are 2 or 3 symbols, the REG bundle size can be equal to the number of time domain symbols or 6.

[0082] A UE can be configured with one or more CORESETs, with a maximum of 3 CORESETs per cell per BWP, where:

[0083] Each CORESET can be associated with two types of search spaces: CSS or USS;

[0084] Each BWP has a maximum of 3 coresets;

[0085] Each BWP has a maximum of 10 search spaces.

[0086] Multiple CORESETs configured for a UE can overlap in the frequency domain or time domain;

[0087] Within each CORESET, the mapping from control channel element (CCE) to REG can be interleaved or non - interleaved, but there can only be one mapping method for one CORESET.

[0088] Next, in conjunction with the accompanying drawings, through some embodiments and their application scenarios, the information transmission methods, devices, terminals, and network - side devices provided by the embodiments of the present application will be described in detail.

[0089] As Figure 2 shown, the embodiments of the present application provide an information transmission method, including:

[0090] Step 201, the terminal sends the first information; and / or

[0091] The terminal obtains the first information;

[0092] It should be noted that the first information is related to at least one resource object (it can also be understood that the first information is associated with at least one resource object), and the resource object is associated with or includes at least one frequency domain object.

[0093] It should be noted that a resource object being associated with or containing at least one frequency domain object can be understood as the resource object being associated with or containing one or more frequency domain objects. Here, it should also be noted that a resource object can be associated with or contain multiple frequency domain objects, but sometimes it may actually be associated with or contain only one frequency domain object. For example, in terms of capabilities or design, the resource object supports being associated with or containing multiple frequency domain objects, but the network-side device only configures one, in which case the resource object is associated with or contains one frequency domain object.

[0094] Optionally, the resource object includes a cell.

[0095] Optionally, the frequency domain object includes one of the following: frequency part (FP), band (which can also be referred to as frequency band), carrier, subband.

[0096] For example, an application scenario of this application is: the first information is related to at least one cell associated with or containing multiple FPs, or the first information is associated with at least one cell associated with or containing multiple FPs.

[0097] Among them, the first information includes at least one of the following:

[0098] A11, the allocation method of control resources;

[0099] Optionally, the allocation method of this control resource can be understood as the mapping method of control resources, the configuration method of control resources, the usage method of control resources, etc. Optionally, the allocation method of this control resource can be agreed upon by the protocol.

[0100] Optionally, this control resource includes one of the following:

[0101] A111, control resource set (CORESET);

[0102] A112, control channel;

[0103] For example, this control channel is PDCCH.

[0104] A113, candidate control channel;

[0105] For example, this candidate control channel is candidate PDCCH (PDCCH candidate), and this candidate PDCCH can also be referred to as PDCCH candidate.

[0106] A114, control channel element (CCE);

[0107] A115, resource element group (REG);

[0108] A116, search space (SS).

[0109] A12. Scheduling relationship corresponding to the control resource;

[0110] Optionally, after the terminal sends the first information, the terminal may receive the first information actually configured by the network device for it, and then communicate with the network device based on the first information configured by the network device. Optionally, after the terminal sends the first information, the terminal may communicate with the network device based on the first information. Optionally, after the terminal determines the first information, the terminal may communicate with the network device based on the first information.

[0111] For example, an actual usage process corresponding to this application is as follows: The terminal sends the allocation method of the CORESET and the scheduling relationship corresponding to the CORESET. The method of the CORESET and the scheduling relationship corresponding to the CORESET are related to at least one cell associated with or including multiple FPs. Then the terminal receives the allocation method of the CORESET actually configured by the network device for it and the scheduling relationship corresponding to the CORESET, and then communicates with the network device based on the allocation method of the CORESET configured by the network device and the scheduling relationship corresponding to the CORESET.

[0112] Optionally, in one implementation manner, the scheduling relationship corresponding to the control resource includes at least one of the following, or the scheduling relationship corresponding to the control resource is related to at least one of the following:

[0113] A12101. Scheduled BWP;

[0114] A12102. Scheduled frequency domain object;

[0115] A12103. Scheduled BWP;

[0116] A12104. Set of scheduled BWPs;

[0117] A12105. Scheduled frequency domain object;

[0118] A12106. Set of scheduled frequency domain objects;

[0119] It should be noted that the above A12101 - A12106 are applicable to both the situation within one resource object and the situation between resource objects.

[0120] A12107. Combination of scheduled BWP and scheduled BWP;

[0121] It should be noted that the combination of the scheduled BWP and the scheduled BWP can also be understood as the pairing of the scheduled BWP and the scheduled BWP, or the set of the scheduled BWP and the scheduled BWP.

[0122] It should be noted that the control resource or control resource part of the scheduling BWP (this control resource part can be understood as a part of the control resource) can schedule the scheduled BWP.

[0123] Optionally, if there are at least two scheduling BWPs and / or at least two scheduled BWPs in the combination of the scheduling BWP and the scheduled BWP, any combination method of the scheduling BWP and the scheduled BWP is supported.

[0124] It should be noted that when the resource objects corresponding to the scheduling BWP and the scheduled BWP are the same, this situation applies to the situation within one resource object. For example, within one cell, there is the above-mentioned scheduling relationship of the control resource.

[0125] For example, there are BWP1 and BWP2 in one cell. The network-side device configures or indicates that BWP1 is the scheduling BWP and BWP2 is the scheduled BWP. Then the CORESET or CORESET part of BWP1 can schedule BWP2.

[0126] It should be noted that when the resource objects corresponding to the scheduling BWP and the scheduled BWP are different, this situation applies to the situation between resource objects. For example, between cells, there is the above-mentioned scheduling relationship of the control resource; optionally, in this case, there can be one or more scheduled resource objects. In this case, the combination of the scheduling BWP and the scheduled BWP is the combination of the scheduling BWP of the scheduling resource object and the scheduled BWP of the scheduled resource object.

[0127] For example, the combination of the scheduling BWP of the scheduling resource object and the scheduled BWP of the scheduled resource object can be the combination of the scheduling BWP of the scheduling cell and the scheduled BWP of the scheduled cell.

[0128] A12108. The combination of the scheduling frequency-domain object and the scheduled frequency-domain object;

[0129] It should be noted that the combination of the scheduling frequency-domain object and the scheduled frequency-domain object can also be understood as the pairing of the scheduling frequency-domain object and the scheduled frequency-domain object, or the set of the scheduling frequency-domain object and the scheduled frequency-domain object.

[0130] It should be noted that the control resource or control resource part of the scheduling frequency-domain object can schedule the scheduled frequency-domain object.

[0131] Optionally, if there are at least two scheduling frequency-domain objects and / or at least two scheduled frequency-domain objects in the combination of the scheduling frequency-domain object and the scheduled frequency-domain object, any combination method of the scheduling frequency-domain object and the scheduled frequency-domain object is supported.

[0132] Optionally, the scheduled frequency-domain object and the scheduled frequency-domain object to be scheduled are associated frequency-domain objects.

[0133] It should be noted that when the resource objects corresponding to the scheduled frequency-domain object and the scheduled frequency-domain object to be scheduled are the same, this situation applies to the situation within one resource object. For example, within a cell, there is the above-mentioned scheduling relationship of control resources.

[0134] For example, in a cell, there are FP1 and FP2. The network-side device indicates or configures FP1 as the scheduling FP and FP2 as the scheduled FP, then the CORESET or part of the CORESET of FP1 can schedule FP2.

[0135] It should be noted that when the resource objects corresponding to the scheduled frequency-domain object and the scheduled frequency-domain object to be scheduled are different, this situation applies to the situation between resource objects. For example, between cells, there is the above-mentioned scheduling relationship of control resources. Optionally, in this case, there may be one or more scheduled resource objects. In this case, the combination of the scheduled frequency-domain object and the scheduled frequency-domain object to be scheduled is the combination of the scheduled frequency-domain object of the scheduled resource object and the scheduled frequency-domain object of the scheduled resource object.

[0136] For example, the combination of the scheduled frequency-domain object of the scheduled resource object and the scheduled frequency-domain object of the scheduled resource object can be the combination of the scheduled frequency-domain object of the scheduling cell and the scheduled frequency-domain object of the scheduled cell.

[0137] A12109, the combination of the scheduling BWP and the scheduled frequency-domain object;

[0138] It should be noted that the combination of the scheduling BWP and the scheduled frequency-domain object can also be understood as the pairing of the scheduling BWP and the scheduled frequency-domain object, or the set of the scheduling BWP and the scheduled frequency-domain object.

[0139] It should be noted that the CORESET or part of the CORESET of the scheduling BWP can schedule the scheduled FP.

[0140] Optionally, if there are at least two scheduling BWPs and / or at least two scheduled frequency-domain objects in the combination of the scheduling BWP and the scheduled frequency-domain object, any combination method of the scheduling BWP and the scheduled frequency-domain object is supported.

[0141] Optionally, the scheduling BWP and the scheduled FP are associated. For example, the scheduled FP belongs to the scheduling BWP, or the scheduled FP belongs to a BWP that can be scheduled by the scheduling BWP.

[0142] It should be noted that when the scheduling BWP is the same as the resource object corresponding to the scheduled frequency-domain object, this situation applies to the situation within a resource object. For example, within a cell, there is the above-mentioned scheduling relationship of control resources.

[0143] For example, in a cell, there are FP1 and FP2 belonging to BWP1. The network-side device indicates or configures BWP1 as the scheduling FP and FP2 as the scheduled FP. Then, the CORESET or part of the CORESET of BWP1 can schedule FP2.

[0144] It should be noted that when the scheduling BWP is different from the resource object corresponding to the scheduled frequency-domain object, this situation applies to the situation between resource objects. For example, between cells, there is the above-mentioned scheduling relationship of control resources; optionally, in this case, there may be one or more scheduled resource objects. In this case, the combination of the scheduling BWP and the scheduled frequency-domain object is the combination of the scheduling BWP of the scheduling resource object and the scheduled frequency-domain object of the scheduled resource object.

[0145] For example, the combination of the scheduling BWP of the scheduling resource object and the scheduled frequency-domain object of the scheduled resource object can be the combination of the scheduling BWP of the scheduling cell and the scheduled frequency-domain object of the scheduled cell.

[0146] A12110, the combination of the scheduling frequency-domain object and the scheduled BWP;

[0147] It should be noted that the combination of the scheduling frequency-domain object and the scheduled BWP can also be understood as the pairing of the scheduling frequency-domain object and the scheduled BWP, or the set of the scheduling frequency-domain object and the scheduled BWP.

[0148] It should be noted that the CORESET or part of the CORESET of the scheduling FP can schedule the scheduled BWP.

[0149] Optionally, if there are at least two scheduling FPs and / or at least two scheduled BWPs in the combination of the scheduling frequency-domain object and the scheduled BWP, any combination method of the scheduling FP and the scheduled BWP is supported.

[0150] It should be noted that when the scheduling frequency-domain object is the same as the resource object corresponding to the scheduled BWP, this situation applies to the situation within a resource object. For example, within a cell, there is the above-mentioned scheduling relationship of control resources.

[0151] Optionally, the scheduling FP and the scheduled BWP are associated. For example, the scheduling FP belongs to the scheduled BWP, or the scheduling FP belongs to the BWP that can schedule the scheduled BWP.

[0152] For example, in a cell, there are FP1 and FP2 belonging to BWP1. The network device indicates or configures FP1 as the scheduling FP and BWP1 as the scheduled FP. Then, the CORESET or part of the CORESET of FP1 can schedule BWP1.

[0153] It should be noted that when the scheduling frequency-domain object is different from the resource object corresponding to the scheduled BWP, this situation applies to the case between resource objects. For example, between cells, there is the above scheduling relationship of control resources; optionally, in this case, there may be one or more scheduled resource objects. In this case, the combination of the scheduling frequency-domain object and the scheduled BWP is the combination of the scheduling frequency-domain object of the scheduled resource object and the scheduled BWP of the scheduled resource object.

[0154] For example, the combination of the scheduling frequency-domain object of the scheduled resource object and the scheduled BWP of the scheduled resource object can be the combination of the scheduling frequency-domain object of the scheduling cell and the scheduled BWP of the scheduled cell.

[0155] Optionally, in the first implementation manner, the scheduling relationship corresponding to the control resource includes at least one of the following, or the scheduling relationship corresponding to the control resource is related to at least one of the following:

[0156] Scheduled BWP;

[0157] Scheduling frequency-domain object;

[0158] Scheduled BWP;

[0159] Set of scheduled BWPs;

[0160] Scheduled frequency-domain object;

[0161] Set of scheduled frequency-domain objects;

[0162] Combination of scheduled BWP and scheduled BWP;

[0163] Combination of scheduling frequency-domain object and scheduled frequency-domain object;

[0164] Combination of scheduled BWP and scheduled frequency-domain object;

[0165] Combination of scheduling frequency-domain object and scheduled BWP.

[0166] Optionally, this first implementation manner applies to the situation within one resource object.

[0167] Optionally, in the second implementation manner, the scheduling relationship corresponding to the control resource includes at least one of the following, or the scheduling relationship corresponding to the control resource is related to at least one of the following:

[0168] Scheduled BWP;

[0169] Scheduled frequency domain object;

[0170] Scheduled BWP;

[0171] Set of scheduled BWPs;

[0172] Scheduled frequency domain object;

[0173] Set of scheduled frequency domain objects;

[0174] Combination of the scheduled BWP of a scheduling resource object and the scheduled BWP of a scheduled resource object;

[0175] Combination of the scheduled frequency domain object of a scheduling resource object and the scheduled frequency domain object of a scheduled resource object;

[0176] Combination of the scheduled BWP of a scheduling resource object and the scheduled frequency domain object of a scheduled resource object;

[0177] Combination of the scheduled frequency domain object of a scheduling resource object and the scheduled BWP of a scheduled resource object.

[0178] Optionally, this second implementation is applicable to the case between resource objects.

[0179] It should be noted that, in the embodiments of the present application, by sending and / or obtaining the allocation method of control resources and / or the scheduling relationship corresponding to the control resources related to at least one resource object, the configuration of control resources under flexible resource objects is realized, and then the transmission of control resources is realized, improving the performance of the communication system.

[0180] It should also be noted that the control resources mentioned in the embodiments of the present application meet the following requirements:

[0181] One or more control resources are associated with one or more target information;

[0182] Wherein, the target information includes at least one of the following:

[0183] A21, Transmission Configuration Indication (TCI);

[0184] A22, Resource pool identifier;

[0185] For example, it can be a resource pool number or a resource pool index.

[0186] A23, Transmission and Reception Point (TRP);

[0187] A24, Repetition configuration;

[0188] Optionally, the repetition configuration may include but is not limited to at least one of the following: indication of whether to perform repetition, number of repetitions, etc.

[0189] For example, a control resource is associated with a target information. For example, a control resource is associated with multiple target information. For example, multiple control resources are associated with a target information.

[0190] Further optionally, the target information associated with at least two control resources is at least partially different. Optionally, in one case, it can be understood that the target information associated with each of the at least two control resources is at least partially different; for example, CORESET1 is associated with resource pool 1 and resource pool 2, and CORESET2 is associated with resource pool 2 and resource pool 3. Optionally, in another case, it can be understood that each of the at least two control resources independently associates with different target information. For example, the repetition times associated with REG1 is 4 times, and the repetition times associated with REG2 is 8 times.

[0191] It should be noted here that the frequency domain object mentioned in the embodiments of the present application can be a configured frequency domain object, can also be all frequency domain objects, or can be an activated frequency domain object.

[0192] It should be noted that, optionally, the first information can be configured by the network side device for the terminal. That is, an optional implementation manner for the terminal to obtain the first information is: the terminal receives the first information sent by the network side device. Optionally, the first information can also be actively sent by the terminal to the network side device. In the case where the terminal sends the first information, optionally, in one implementation manner, the terminal sending the first information includes:

[0193] The terminal sends the first terminal capability information for at least one resource object, and the first terminal capability information includes: the first information supported by the terminal.

[0194] It should be noted that this case refers to the reporting of the first information through the terminal's capability reporting. In this case, the first information can be understood as the first information supported by the terminal. For example, the allocation method of the control resources supported by the terminal, and / or the scheduling relationship corresponding to the control resources supported by the terminal.

[0195] It should be noted that by carrying the first information in the terminal capability information, there is no need to add new signaling, which can save signaling overhead.

[0196] Optionally, in one implementation manner, the method further includes:

[0197] The terminal sends the second terminal capability information, and the second terminal capability information includes at least one of the following:

[0198] B101. The number of resource objects;

[0199] B102. The number of resource objects containing multiple frequency-domain objects;

[0200] Optionally, when the terminal reports its capabilities, the number of resource objects containing multiple frequency-domain objects can be understood as the number of resource objects containing multiple frequency-domain objects supported by the terminal. This number can be the maximum number or the minimum number.

[0201] B103. Band combination;

[0202] It should be noted that this band combination can also be referred to as a bandwidth combination.

[0203] It should be noted that since the band combination is related to the number of resource objects, that is to say, the number of resource objects containing multiple frequency-domain objects supported by the terminal can be implicitly indicated by the band combination.

[0204] For example, if it is reported that one cell containing multiple FPs is supported in 3 Band combinations, it is considered that the terminal supports at most 3 cells containing multiple FPs.

[0205] B104. Resource object type, where the resource object type includes at least one of the following: type A, type B;

[0206] It should be noted that this resource object type can be understood as the resource object type supported by the terminal

[0207] Among them, type A is that multiple frequency-domain objects are used as multiple BWPs. That is to say, under type A, multiple frequency-domain objects are regarded as independent BWPs, and the terminal can activate multiple BWPs simultaneously. Type B is that multiple frequency-domain objects are used as one BWP. That is to say, under type B, multiple frequency-domain objects correspond to one BWP, and the terminal can only activate one BWP.

[0208] B105. Type of frequency-domain object;

[0209] Optionally, the type of frequency-domain object includes at least one of the following:

[0210] Continuous frequency-domain objects;

[0211] Discontinuous frequency-domain objects.

[0212] B106. Interval between frequency-domain objects;

[0213] Optionally, the interval between frequency-domain objects can be the maximum interval, the minimum interval, or the interval supported by the terminal for use.

[0214] B107. Number of frequency-domain objects;

[0215] Optionally, the number of frequency-domain objects can be the maximum number of frequency-domain objects or the minimum number of frequency-domain objects.

[0216] B108. The number of activated BWPs;

[0217] The number of activated BWPs can be the maximum number of activated BWPs or the minimum number of activated BWPs.

[0218] B109. The number of frequency-domain objects in a resource object or a set of resource objects;

[0219] Optionally, this number can be the maximum number or the minimum number.

[0220] Optionally, the number of frequency-domain objects in a resource object or a set of resource objects can be understood as the number of supported frequency-domain objects in a resource object or a set of resource objects, or the number of activated frequency-domain objects supported in a resource object or a set of resource objects, or the number of configured frequency-domain objects supported in a resource object or a set of resource objects, or the number of all supported frequency-domain objects in a resource object or a set of resource objects.

[0221] Optionally, the number of frequency-domain objects in a resource object or a set of resource objects includes at least one of the following:

[0222] B1091. The number of frequency-domain objects in a resource object or a set of resource objects of type A;

[0223] Optionally, the number of frequency-domain objects in a resource object or a set of resource objects of type A can be understood as the number of supported frequency-domain objects in a resource object or a set of resource objects of type A.

[0224] B1092. The number of frequency-domain objects in a resource object or a set of resource objects of type B;

[0225] Optionally, the number of frequency-domain objects in a resource object or a set of resource objects of type B can be understood as the number of supported frequency-domain objects in a resource object or a set of resource objects of type B.

[0226] B1093. The number of frequency-domain objects in a resource object or a set of resource objects that can be scheduled by the same scheduling resource object;

[0227] Optionally, the number of frequency-domain objects in a resource object or a set of resource objects that can be scheduled by the same scheduling resource object can be understood as the number of supported frequency-domain objects in a resource object or a set of resource objects that can be scheduled by the same scheduling resource object.

[0228] The number of frequency-domain objects in a resource object or a set of resource objects corresponding to a first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination;

[0229] Optionally, the carrier type may include, but is not limited to: Frequency Range 1 (FR1), Frequency Range 2 (FR2), Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), licensed frequency band, unlicensed frequency band.

[0230] Optionally, the number of frequency-domain objects in a resource object or a set of resource objects corresponding to the first target object can be understood as the number of supported frequency-domain objects in a resource object or a set of resource objects corresponding to the first target object.

[0231] B110. The number of activated BWPs in a resource object or a set of resource objects;

[0232] Optionally, this number can be the maximum number or the minimum number.

[0233] Optionally, the number of activated BWPs in a resource object or a set of resource objects can be understood as the number of supported activated BWPs in a resource object or a set of resource objects.

[0234] Optionally, the number of activated BWPs in a resource object or a set of resource objects includes at least one of the following:

[0235] B1101. The number of activated BWPs in a resource object or a set of resource objects of type A;

[0236] Optionally, the number of activated BWPs in a resource object or a set of resource objects of type A can be understood as the number of supported activated BWPs in a resource object or a set of resource objects of type A.

[0237] B1102. The number of activated BWPs in a resource object or a set of resource objects of type B;

[0238] Optionally, the number of activated BWPs in a resource object or a set of resource objects of type B can be understood as the number of supported activated BWPs in a resource object or a set of resource objects of type B.

[0239] B1103. The number of activated BWPs in a resource object or a set of resource objects scheduled by the same scheduling resource object;

[0240] Optionally, the number of activated BWPs within the resource object or resource object set scheduled by the same scheduling resource object can be understood as the number of supported activated BWPs within the resource object or resource object set scheduled by the same scheduling resource object.

[0241] B1104. The number of activated BWPs within the resource object or resource object set corresponding to the first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination;

[0242] It should be noted that the frequency range includes, for example, FR1, FR2, FR2-1, FR2-2, FR2-3, etc.

[0243] Optionally, the number of activated BWPs within the resource object or resource object set corresponding to the first target object can be understood as the number of supported activated BWPs within the resource object or resource object set corresponding to the first target object.

[0244] B111. The number of frequency domain objects or BWPs with an association relationship;

[0245] Optionally, this number can be the maximum number or the minimum number.

[0246] B112. The number of frequency domain objects or BWPs used for scheduling;

[0247] Optionally, this number can be the maximum number or the minimum number.

[0248] Optionally, the number of frequency domain objects or BWPs used for scheduling can be understood as the number of frequency domain objects or BWPs that can be used for scheduling.

[0249] B113. The number of frequency domain objects or BWPs serving as the scheduled ones;

[0250] Optionally, this number can be the maximum number or the minimum number.

[0251] Optionally, the number of frequency domain objects or BWPs serving as the scheduled ones can be understood as the number of frequency domain objects or BWPs that can serve as the scheduled ones.

[0252] B114. The number of frequency domain objects or BWPs having a scheduling relationship;

[0253] Optionally, this number can be the maximum number or the minimum number.

[0254] Optionally, in one implementation, the first terminal capability information and / or the second terminal capability information are related to at least one of the following:

[0255] C11. Band

[0256] C12. Band combination

[0257] C13. Bandwidth, which can be carrier bandwidth such as channel bandwidth

[0258] Optionally, the bandwidth can be the bandwidth supported by the terminal, the minimum supported bandwidth or the maximum supported bandwidth of the terminal, the bandwidth of the system, the minimum bandwidth or the maximum bandwidth of the system, or a preset bandwidth (such as 20 MHz).

[0259] C14. Bandwidth combination

[0260] It should be noted that the bandwidth combination can be a combination of one or more of the bandwidths in C13 above.

[0261] C15. Frequency range

[0262] For example, there are more frequency domain objects supported by low frequencies and fewer frequency domain objects supported by high frequencies.

[0263] C16. Carrier type

[0264] Optionally, in one implementation, the allocation method of the control resources includes at least one of the following:

[0265] D11. There is only one control resource or part of the control resource on one frequency domain object in the resource object

[0266] This situation can be understood as that within a given one or more time units, there is one and only one frequency domain object in a resource object that has a control resource or part of the control resource. For example, within a given one or more time units, there is one and only one FP in a cell that has a control resource or part of the control resource.

[0267] Optionally, the time unit can be seconds, frames, sub - frames, time slots, symbols, etc.

[0268] Optionally, in this case, the scheduling relationship corresponding to the control resource or part of the control resource can be that the control resource or part of the control resource is used to schedule any frequency domain object or BWP.

[0269] Further optionally, in this case, the scheduling relationship corresponding to the control resource or part of the control resource includes at least one of the following:

[0270] D111. The control resource or the control resource part is used to schedule the frequency-domain object or BWP where the control resource or the control resource part is located.

[0271] D112. The control resource or the control resource part is used to schedule the frequency-domain object or BWP associated with the control resource or the control resource part.

[0272] Optionally, the associated frequency-domain object includes at least one of the following:

[0273] D1121. A frequency-domain object associated with the same second information or the same set of second information as the frequency-domain object where the control resource or the control resource part is located, and the second information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration.

[0274] Optionally, a frequency-domain object associated with the same second information or the same set of second information as the frequency-domain object where the control resource or the control resource part is located may further refer to a frequency-domain object belonging to the same second information or the same set of second information as the frequency-domain object where the control resource or the control resource part is located.

[0275] D1122. A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object where the control resource for scheduling is located.

[0276] Optionally, a frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object where the control resource for scheduling is located may further refer to a frequency-domain object belonging to the same BWP or the same BWP group as the frequency-domain object where the control resource for scheduling is located.

[0277] It should be noted that this case is preferably applicable to type B, which is equivalent to having only one active BWP in the entire cell, and only a part of the resources in the BWP are used for the CORESET.

[0278] Optionally, there is at most one frequency-domain object in the resource object where the target control resource exists, and the target control resource can be used to schedule the frequency-domain object or BWP where the target control resource is located, and / or the target control resource can be used to schedule the frequency-domain object or BWP associated with the frequency-domain object where the target control resource is located.

[0279] Optionally, the target control resource can be a control resource for access.

[0280] For example, as Figure 3As shown, taking the resource object as a cell and the frequency-domain object as an FP as an example, for type A, that is, one FP corresponds to one BWP, the implementation of the above scheduling relationship is similar to cross-carrier scheduling (CCS) and multi-cell scheduling under CA. The CORESET of BWP1 can schedule the BWP or FP where it is located, as well as other BWPs or FPs that belong to the same cell as its own FP.

[0281] For example, as Figure 4 shown, taking the resource object as a cell and the frequency-domain object as an FP as an example, for type B, that is, multiple FPs correspond to one BWP, the implementation of the above scheduling relationship is similar to in-cell self-scheduling. The CORESET of BWP1 can schedule the FP where it is located, as well as other FPs that belong to the same BWP as its own FP.

[0282] It should be noted that for Figure 3 and Figure 4 , only one FP in a cell can have a CORESET.

[0283] D12. There can be at least one second target object on at least one frequency-domain object in the resource object, and the second target object includes at least one of the following: control resource, control resource part;

[0284] Optionally, in this case, the scheduling relationship corresponding to the control resource or the control resource part can be that the control resource or the control resource part is used to schedule any frequency-domain object or BWP.

[0285] Further optionally, in this case, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0286] D121. The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP where the second target object is located;

[0287] D122. The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP associated with the second target object;

[0288] Optionally, the associated frequency-domain object includes at least one of the following:

[0289] D1221. The frequency-domain object associated with the same third information or the same set of third information as the frequency-domain object where the second target object is located, and the third information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0290] Optionally, a frequency-domain object associated with the same third information or the same set of third information as the frequency-domain object where the second target object is located may further refer to a frequency-domain object belonging to the same third information or the same set of third information as the frequency-domain object where the second target object is located.

[0291] D1222. A frequency-domain object associated with the same BWP or the same BWP set as the frequency-domain object where the second target object is scheduled;

[0292] Optionally, a frequency-domain object associated with the same BWP or the same BWP set as the frequency-domain object where the second target object is scheduled may further refer to a frequency-domain object belonging to the same BWP or the same BWP set as the frequency-domain object where the second target object is scheduled.

[0293] D123. The second target object on the frequency-domain object can be used to schedule a frequency-domain object or a BWP with a scheduling relationship.

[0294] The different cases of the second target object are described as follows.

[0295] I. The second target object is a control resource

[0296] It should be noted that in this case, it can be understood that within a given one or more time units, there can be at least one control resource on a frequency-domain object in a resource object. For example, within a given one or more time units, there can be at least one control resource on an FP in a cell.

[0297] Optionally, the time unit can be seconds, frames, sub-frames, time slots, symbols, etc.

[0298] The first scheduling relationship in this case is that the control resource on the frequency-domain object can be used to schedule the frequency-domain object where the control resource is located. For example, the CORESET on an FP can be used to schedule the FP where the CORESET is located.

[0299] It should be noted that this scheduling relationship is more applicable to type A, that is, self-scheduling within multiple cells.

[0300] The second scheduling relationship in this case is that the control resource on the frequency-domain object can be used to schedule the frequency-domain object or BWP where the control resource is located; and / or, the control resource on the frequency-domain object can be used to schedule the frequency-domain object or BWP associated with the control resource; and / or, the control resource on the frequency-domain object can be used to schedule a frequency-domain object or BWP with a scheduling relationship.

[0301] Further optionally, for type A, in this case, at most only one frequency domain object or BWP can be scheduled by the control resources of multiple frequency domain objects or multiple BWPs; optionally, at most only one frequency domain object or BWP can be scheduled by the control resources of at most two frequency domain objects or at most two BWPs.

[0302] It should be noted that such a scheduling relationship is more applicable to type B, that is, self-scheduling within a cell.

[0303] For example, as Figure 5 shown, taking the resource object as the cell and the frequency domain object as the FP as an example, for type A, that is, one FP corresponds to one BWP, the implementation of the above scheduling relationship is similar to self-scheduling under CA. The CORESET of BWP1 can schedule the FP where it is located and / or BWP1, and the CORESET of BWP2 can schedule the FP where it is located and / or BWP2.

[0304] For example, as Figure 6 shown, taking the resource object as the cell and the frequency domain object as the FP as an example, for type B, that is, multiple FPs correspond to one BWP, the implementation of the above scheduling relationship is similar to self-scheduling within the cell. The CORESET of FP1 can schedule the FP where it is located, and the CORESET of FP2 can schedule the FP where it is located.

[0305] For example, as Figure 7 shown, taking the resource object as the cell and the frequency domain object as the FP as an example, for type A, that is, one FP corresponds to one BWP, the implementation of the above scheduling relationship is similar to self-scheduling under CA. At most only one FP or BWP can be scheduled by the CORESETs of multiple FPs. For example, the CORESET of another BWP1 can schedule the FP where it is located or BWP1 and other FPs or BWPs, and the CORESET of BWP2 can schedule the FP where it is located or BWP2.

[0306] For example, as Figure 8 shown, taking the resource object as the cell and the frequency domain object as the FP as an example, for type A, that is, one freqpart corresponds to one BWP, the implementation of the above scheduling relationship is similar to self-scheduling under CA. The CORESET of BWP1 can schedule the FP where it is located or BWP1 and other FPs and / or BWPs, and the CORESET of BWP2 can schedule the FP where it is located or BWP2 and other FPs and / or BWPs.

[0307] For example, as Figure 9As shown, taking the resource object as a cell and the frequency-domain object as an FP as an example, for type B, if multiple FPs correspond to one BWP, the implementation of the above scheduling relationship is similar to intra-cell self-scheduling. The CORESET on the BWP can schedule the FP where it is located or the BWP and other FPs belonging to the same BWP.

[0308] II. The second target object is the control resource part

[0309] It should be noted that this situation can be understood as that within a given one or more time units, there can be at least one frequency-domain object in a resource object with a control resource part. For example, within a given one or more time units, there can be at least one FP in a cell with a control resource part.

[0310] Optionally, the time unit can be seconds, frames, sub-frames, time slots, symbols, etc.

[0311] One scheduling relationship in this case is that the control resource part on the frequency-domain object can be used to schedule the frequency-domain object where the control resource part is located. For example, the CORESET part on an FP can be used to schedule the FP where the CORESET part is located.

[0312] It should be noted that this scheduling relationship is more applicable to type B.

[0313] Another scheduling relationship in this case is that the control resource part on the frequency-domain object can be used to schedule the frequency-domain object or BWP where the control resource part is located; and / or, the control resource part on the frequency-domain object can be used to schedule the frequency-domain object or BWP associated with the control resource part; and / or, the control resource part on the frequency-domain object can be used to schedule the frequency-domain object or BWP with a scheduling relationship.

[0314] Further optionally, for type A, in this case, at most only one frequency-domain object or BWP can be scheduled by the control resource parts of multiple frequency-domain objects or multiple BWPs; optionally, at most only one frequency-domain object or BWP can be scheduled by the control resource parts of at most two frequency-domain objects or at most two BWPs.

[0315] It should be noted that this scheduling relationship is more applicable to type B, that is, intra-cell self-scheduling.

[0316] For example, as Figure 10 shown, taking the resource object as a cell and the frequency-domain object as an FP as an example, for type A, that is, one freq part corresponds to one BWP, the implementation of the above scheduling relationship is similar to self-scheduling under CA. Figure 10 The CORESET part 1 (P1) in it can only schedule BWP1, and the CORESET part 2 (P2) can only schedule BWP2.

[0317] For example, as Figure 11 shown, taking the resource object as a cell and the frequency-domain object as an FP as an example, for type B, that is, multiple freq parts correspond to one BWP, the implementation of the above scheduling relationship is similar to the in-cell self-scheduling. Figure 11 In CORESET part 1 (P1), it can only schedule the FP where it is located, and CORESET part 2 (P2) can only schedule the FP where it is located.

[0318] For example, as Figure 12 shown, taking the resource object as a cell and the frequency-domain object as an FP as an example, for type A, that is, one freq part corresponds to one BWP, the implementation of the above scheduling relationship is similar to the self-scheduling under CA. At most, only one FP or BWP can be scheduled by the CORESETs of multiple FPs. For example, in the above figure, CORESET part 1 (P1) can schedule BWP1 and BWP2, and CORESET part 2 (P2) can schedule BWP2.

[0319] For example, as Figure 13 shown, taking the resource object as a cell and the frequency-domain object as an FP as an example, for type A, that is, one freq part corresponds to one BWP, the implementation of the above scheduling relationship is similar to the self-scheduling under CA. Figure 13 In it, CORESET part 1 (P1) can schedule BWP1 and BWP2, and CORESET part 2 (P2) can schedule BWP1 and BWP2.

[0320] For example, as Figure 14 shown, taking the resource object as a cell and the frequency-domain object as an FP as an example, for type B, that is, multiple freq parts correspond to one BWP, the implementation of the above scheduling relationship is similar to the in-cell self-scheduling. Figure 14 In it, CORESET part 1 (P1) can schedule the BWP where this CORESET is located.

[0321] It should be noted that Figures 10 - 14 the two slash-filled boxes in it belong to different parts of the same CORESET or belong to two CORESET parts. The grid-filled box part is the middle interval or guard band part between the two BWPs, which can be considered not to belong to the CORESET or CORESET part, or the grid-filled box part is considered to be the CORESET or CORESET part that overlaps with the middle interval or guard band part (this CORESET part may be available in other BWPs, or unavailable, or not considered actually available for scheduling), and no restrictions are made here.

[0322] It should be noted that in all embodiments of this applicationFigures 3 - 14 The arrows in it indicate the scheduling relationship, and there is no limit on the number of arrows. If the angular relationship corresponding to the arrows is implemented through DCI, it can be that one DCI only supports the scheduling relationship of one arrow, or one DCI can support the scheduling relationships of multiple arrows simultaneously. For example, one DCI can schedule multiple FPs or BWPs simultaneously.

[0323] Optionally, in one implementation manner, the specific implementation for the terminal to determine the first information includes:

[0324] Determine the first information according to at least one of the following, where the first information includes the allocation manner of control resources and / or the scheduling relationship corresponding to the control resources:

[0325] E11. Indication by the network device;

[0326] For example, it can be RRC, MAC CE, or DCI;

[0327] That is to say, in this case, the first information is sent from the network-side device to the terminal.

[0328] E12. The scheduling relationship corresponding to the control resources;

[0329] E13. The allocation manner of the control resources;

[0330] For example, if the allocation manner of the control resources is D12 and the second target object is the control resources, the scheduling relationship is the second scheduling relationship.

[0331] E14. The resource object type, where the resource object type includes at least one of the following: type A, type B;

[0332] For example, for type A, the allocation manner of the control resources and / or the scheduling relationship corresponding to the control resources correspond to Figure 8 the situation shown.

[0333] For example, for type B, the allocation manner of the control resources and / or the scheduling relationship corresponding to the control resources correspond to Figure 14 the situation shown.

[0334] E15. The number of frequency-domain objects;

[0335] It should be noted that this number can be the maximum number or the minimum number.

[0336] Optionally, the number of the frequency-domain objects can be, for example, the number of active frequency-domain objects.

[0337] For example, if there is at most one frequency-domain object or active frequency-domain object, the allocation manner of the control resources corresponding to type B and / or the scheduling relationship corresponding to the control resources are used.

[0338] For example, if there are multiple frequency-domain objects or active frequency-domain objects, the allocation method of the control resources corresponding to type A and / or the scheduling relationship corresponding to the control resources are used.

[0339] E16. The number of activated BWPs;

[0340] It should be noted that this number can be the maximum number or the minimum number.

[0341] For example, if there is at most one activated BWP, the allocation method of the control resources corresponding to type B and / or the scheduling relationship corresponding to the control resources are used.

[0342] For example, if there are multiple activated BWPs, the allocation method of the control resources corresponding to type A and / or the scheduling relationship corresponding to the control resources are used.

[0343] Optionally, the terminal can determine the allocation method of the control resources that can be used and the scheduling relationship corresponding to the control resources based on any one of E11-E16 above.

[0344] Optionally, the terminal can determine the allocation method of the control resources based on any one of E11-E12, E14-E16 above;

[0345] Optionally, the terminal can determine the scheduling relationship corresponding to the control resources based on any one of E11, E13-E16 above.

[0346] It should be noted that the embodiments of the present application implement the configuration of control resources under flexible resource objects, and then implement the transmission of control resources, thereby solving the configuration of control resources for multiple frequency-domain objects in NR, which is beneficial to reducing the public signaling overhead, achieving the load balance of each UL / DL carrier, improving the PDCCH conflict probability, improving the PDCCH coverage ability and transmission reliability, and improving the network flexibility and energy efficiency.

[0347] As Figure 15 shown, the embodiments of the present application provide an information transmission method, including:

[0348] Step 1501, the network-side device receives the first information; and / or

[0349] The network-side device sends the first information;

[0350] Wherein, the first information includes at least one of the following: the allocation method of the control resources, the scheduling relationship corresponding to the control resources;

[0351] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency-domain object.

[0352] Optionally, the network-side device receives first information, including:

[0353] The network-side device receives first terminal capability information sent by a terminal for at least one resource object, where the first terminal capability information includes: first information supported by the terminal.

[0354] Optionally, the method further includes:

[0355] The network-side device receives second terminal capability information sent by the terminal, where the second terminal capability information includes at least one of the following:

[0356] The number of resource objects;

[0357] The number of resource objects including multiple frequency-domain objects;

[0358] Frequency band combination;

[0359] Resource object type, where the resource object type includes at least one of the following: type A, type B;

[0360] Type of frequency-domain object;

[0361] Interval between frequency-domain objects;

[0362] The number of frequency-domain objects;

[0363] The number of activated bandwidth parts (BWPs);

[0364] The number of frequency-domain objects within a resource object or a set of resource objects;

[0365] The number of activated BWPs within a resource object or a set of resource objects;

[0366] The number of frequency-domain objects or BWPs with an association relationship;

[0367] The number of frequency-domain objects or BWPs used for scheduling;

[0368] The number of frequency-domain objects or BWPs as scheduled ones;

[0369] The number of frequency-domain objects or BWPs with a scheduling relationship;

[0370] Wherein, type A is that multiple frequency-domain objects serve as multiple BWPs;

[0371] Type B is that multiple frequency-domain objects serve as one BWP.

[0372] Optionally, the type of the frequency-domain object includes at least one of the following:

[0373] Continuous frequency-domain objects;

[0374] Non - continuous frequency - domain objects.

[0375] Optionally, the number of frequency - domain objects in the resource object or resource object set includes at least one of the following:

[0376] The number of frequency - domain objects in a resource object or resource object set of type A;

[0377] The number of frequency - domain objects in a resource object or resource object set of type B;

[0378] The number of frequency - domain objects in a resource object or resource object set that can be scheduled by the same scheduling resource object;

[0379] The number of frequency - domain objects in a resource object or resource object set corresponding to a first target object, where the first target object includes at least one of the following: sub - carrier spacing, carrier type, frequency range, frequency band, CP, sub - carrier spacing combination, carrier type combination.

[0380] Optionally, the number of active bandwidth parts (BWPs) in the resource object or resource object set includes at least one of the following:

[0381] The number of active BWPs in a resource object or resource object set of type A;

[0382] The number of active BWPs in a resource object or resource object set of type B;

[0383] The number of active BWPs in a resource object or resource object set scheduled by the same scheduling resource object;

[0384] The number of active BWPs in a resource object or resource object set corresponding to a first target object, where the first target object includes at least one of the following: sub - carrier spacing, carrier type, frequency range, frequency band, CP, sub - carrier spacing combination, carrier type combination.

[0385] Optionally, the first terminal capability information and / or the second terminal capability information is / are related to at least one of the following:

[0386] Frequency band;

[0387] Frequency - band combination;

[0388] Bandwidth;

[0389] Bandwidth combination;

[0390] Frequency range;

[0391] Carrier type.

[0392] Optionally, the allocation method of the control resource includes at least one of the following:

[0393] There is only one frequency-domain object in the resource object on which there is a control resource or a control resource portion;

[0394] There can be at least one frequency-domain object in the resource object on which there is a second target object, and the second target object includes at least one of the following: a control resource, a control resource portion.

[0395] Optionally, when the allocation method of the control resource includes that there is only one frequency-domain object in the resource object on which there is a control resource or a control resource portion, the scheduling relationship corresponding to the control resource or the control resource portion includes at least one of the following:

[0396] The control resource or the control resource portion is used to schedule the frequency-domain object where the control resource or the control resource portion is located;

[0397] The control resource or the control resource portion is used to schedule the frequency-domain object or BWP associated with the control resource or the control resource portion.

[0398] Optionally, the associated frequency-domain object includes at least one of the following:

[0399] A frequency-domain object associated with the same second information or the same set of second information as the frequency-domain object where the control resource or the control resource portion is located, and the second information includes at least one of the following: an uplink-downlink configuration relationship, a frame structure configuration;

[0400] A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the control resource.

[0401] Optionally, when the allocation method of the control resource includes that there can be at least one frequency-domain object in the resource object on which there is a second target object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0402] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP where the second target object is located;

[0403] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP associated with the second target object;

[0404] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP having a scheduling relationship.

[0405] Optionally, the associated frequency-domain object includes at least one of the following:

[0406] A frequency-domain object associated with the same third information or the same set of third information as the frequency-domain object where the second target object is located, and the third information includes at least one of the following: an uplink-downlink configuration relationship, a frame structure configuration;

[0407] A frequency domain object associated with the same BWP or the same BWP group as the frequency domain object where the second target object is scheduled.

[0408] Optionally, the method further includes:

[0409] Determine first information according to at least one of the following, where the first information includes the allocation method of control resources and / or the scheduling relationship corresponding to the control resources:

[0410] The scheduling relationship corresponding to the control resources;

[0411] The allocation method of the control resources;

[0412] The resource object type, where the resource object type includes at least one of the following: type A, type B, where type A is multiple frequency domain objects as multiple BWPs, and type B is multiple frequency domain objects as one BWP;

[0413] The number of frequency domain objects;

[0414] The number of active BWPs.

[0415] Optionally, the scheduling relationship corresponding to the control resources includes at least one of the following, or the scheduling relationship corresponding to the control resources is related to at least one of the following:

[0416] The scheduled BWP;

[0417] The scheduled frequency domain object;

[0418] The BWP to be scheduled;

[0419] The set of BWPs to be scheduled;

[0420] The frequency domain object to be scheduled;

[0421] The set of frequency domain objects to be scheduled;

[0422] The combination of the scheduled BWP and the BWP to be scheduled;

[0423] The combination of the scheduled frequency domain object and the frequency domain object to be scheduled;

[0424] The combination of the scheduled BWP and the frequency domain object to be scheduled;

[0425] The combination of the scheduled frequency domain object and the BWP to be scheduled.

[0426] Optionally, the frequency domain object includes one of the following: frequency portion, frequency band, carrier, sub-band; and / or

[0427] The control resources include one of the following: a control resource set, a control channel, a candidate control channel, a control channel element, a resource element group, a search space; and / or

[0428] The resource object includes a cell.

[0429] Optionally, one or more control resources are associated with one or more target information, and the target information includes at least one of the following: Transmission Configuration Indication (TCI), resource pool identifier, Transmit Receive Point (TRP), repetition configuration.

[0430] Optionally, each control resource is associated with different target information.

[0431] It should be noted that all the descriptions about the network side device side in the above embodiments are applicable to the embodiments of the information transmission method applied to the network side device side, and can also achieve the same technical effects, which will not be elaborated here.

[0432] In the embodiment of the present application, the execution subject of the provided information transmission method may be an information transmission device. In the embodiment of the present application, taking the information transmission device executing the communication processing method as an example, the information transmission device provided by the embodiment of the present application is described.

[0433] As Figure 16 shown, the information transmission device 1600 in the embodiment of the present application is applied to a terminal and includes:

[0434] A first transmission module 1601, configured to send first information; and / or

[0435] Obtain the first information;

[0436] Wherein, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources;

[0437] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency domain object.

[0438] Optionally, the first transmission module 1601 is configured to:

[0439] Send first terminal capability information for at least one resource object, and the first terminal capability information includes: the first information supported by the terminal.

[0440] Optionally, the device further includes:

[0441] A sending module, configured to send second terminal capability information, and the second terminal capability information includes at least one of the following:

[0442] The number of resource objects;

[0443] The number of resource objects containing multiple frequency-domain objects;

[0444] Frequency band combination;

[0445] Resource object type, where the resource object type includes at least one of the following: type A, type B;

[0446] The type of frequency-domain object;

[0447] The interval between frequency-domain objects;

[0448] The number of frequency-domain objects;

[0449] The number of activated bandwidth parts (BWPs);

[0450] The number of frequency-domain objects within a resource object or a set of resource objects;

[0451] The number of activated BWPs within a resource object or a set of resource objects;

[0452] The number of frequency-domain objects or BWPs with an associated relationship;

[0453] The number of frequency-domain objects or BWPs used for scheduling;

[0454] The number of frequency-domain objects or BWPs being scheduled;

[0455] The number of frequency-domain objects or BWPs with a scheduling relationship;

[0456] Among them, the type A is multiple frequency-domain objects as multiple BWPs;

[0457] The type B is multiple frequency-domain objects as one BWP.

[0458] Optionally, the type of the frequency-domain object includes at least one of the following:

[0459] Continuous frequency-domain objects;

[0460] Non-continuous frequency-domain objects.

[0461] Optionally, the number of frequency-domain objects within a resource object or a set of resource objects includes at least one of the following:

[0462] The number of frequency-domain objects within a resource object or a set of resource objects of type A;

[0463] The number of frequency-domain objects within a resource object or a set of resource objects of type B;

[0464] The number of frequency-domain objects within a resource object or a set of resource objects that can be scheduled by the same scheduling resource object;

[0465] The number of frequency-domain objects in the resource object or resource object set corresponding to the first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0466] Optionally, the number of active bandwidth parts (BWPs) in the resource object or resource object set includes at least one of the following:

[0467] The number of active BWPs in a resource object or resource object set of type A;

[0468] The number of active BWPs in a resource object or resource object set of type B;

[0469] The number of active BWPs in a resource object or resource object set scheduled by the same scheduling resource object;

[0470] The number of active BWPs in the resource object or resource object set corresponding to the first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0471] Optionally, the first terminal capability information and / or the second terminal capability information is / are related to at least one of the following:

[0472] Frequency band;

[0473] Frequency band combination;

[0474] Bandwidth;

[0475] Bandwidth combination;

[0476] Frequency range;

[0477] Carrier type.

[0478] Optionally, the allocation method of the control resource includes at least one of the following:

[0479] There is only one frequency-domain object in the resource object with a control resource or a control resource part;

[0480] There can be at least one frequency-domain object in the resource object with a second target object, where the second target object includes at least one of the following: control resource, control resource part.

[0481] Optionally, in the case where the allocation method of the control resource includes that there is only one frequency-domain object in the resource object with a control resource or a control resource part, the scheduling relationship corresponding to the control resource or the control resource part includes at least one of the following:

[0482] The control resource or the control resource part is used to schedule the frequency-domain object where the control resource or the control resource part is located;

[0483] The control resource or the control resource part is used to schedule the frequency-domain object or BWP associated with the control resource or the control resource part.

[0484] Optionally, the associated frequency-domain object includes at least one of the following:

[0485] A frequency-domain object associated with the same second information or the same set of second information as the frequency-domain object where the control resource or the control resource part is located, and the second information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0486] A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the control resource.

[0487] Optionally, when the allocation method of the control resource includes that there can be at least one second target object on a frequency-domain object in the resource object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0488] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP where the second target object is located;

[0489] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP associated with the second target object;

[0490] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP having a scheduling relationship.

[0491] Optionally, the associated frequency-domain object includes at least one of the following:

[0492] A frequency-domain object associated with the same third information or the same set of third information as the frequency-domain object where the second target object is located, and the third information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0493] A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the frequency-domain object where the second target object is located.

[0494] Optionally, the first transmission module is used to include:

[0495] Determine first information according to at least one of the following, where the first information includes the allocation method of the control resource and / or the scheduling relationship corresponding to the control resource:

[0496] Network device indication;

[0497] The scheduling relationship corresponding to the control resource;

[0498] The allocation method of control resources;

[0499] Resource object types, where the resource object types include at least one of the following: type A, type B, where type A is multiple frequency-domain objects as multiple BWPs, and type B is multiple frequency-domain objects as one BWP;

[0500] The number of frequency-domain objects;

[0501] The number of activated BWPs.

[0502] Optionally, the scheduling relationship corresponding to the control resources includes at least one of the following, or the scheduling relationship corresponding to the control resources is related to at least one of the following:

[0503] Scheduled BWP;

[0504] Scheduled frequency-domain object;

[0505] Scheduled BWP;

[0506] Scheduled BWP set;

[0507] Scheduled frequency-domain object;

[0508] Scheduled frequency-domain object set;

[0509] Combination of scheduled BWP and scheduled BWP;

[0510] Combination of scheduled frequency-domain object and scheduled frequency-domain object;

[0511] Combination of scheduled BWP and scheduled frequency-domain object;

[0512] Combination of scheduled frequency-domain object and scheduled BWP.

[0513] Optionally, the frequency-domain object includes one of the following: frequency portion, frequency band, carrier, sub-band; and / or

[0514] The control resource includes one of the following: control resource set, control channel, candidate control channel, control channel element, resource element group, search space; and / or

[0515] The resource object includes a cell.

[0516] Optionally, one or more control resources are associated with one or more target information, and the target information includes at least one of the following: transmission configuration indication TCI, resource pool identifier, transmit receive point TRP, repetition configuration.

[0517] Optionally, each control resource is associated with different target information.

[0518] It should be noted that the device embodiment corresponds to the above method. All implementation manners in the above method embodiment are applicable to this device embodiment and can achieve the same technical effects, which will not be elaborated herein.

[0519] The measurement switching device in the embodiments of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or other devices other than the terminal. Exemplarily, the terminal may include, but is not limited to, the types of the terminal 11 listed above, and other devices may be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0520] The embodiments of the present application further provide a terminal, including a processor and a communication interface. The communication interface is used to send first information; and / or

[0521] acquire first information;

[0522] wherein the first information includes at least one of the following: the allocation manner of control resources, the scheduling relationship corresponding to the control resources;

[0523] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency domain object.

[0524] Optionally, the communication interface is used to:

[0525] send first terminal capability information for at least one resource object, where the first terminal capability information includes: the first information supported by the terminal.

[0526] Optionally, the communication interface is further used to:

[0527] send second terminal capability information, where the second terminal capability information includes at least one of the following:

[0528] the number of resource objects;

[0529] the number of resource objects including multiple frequency domain objects;

[0530] frequency band combination;

[0531] resource object type, where the resource object type includes at least one of the following: type A, type B;

[0532] the type of frequency domain object;

[0533] the interval between frequency domain objects;

[0534] the number of frequency domain objects;

[0535] The number of activated bandwidth parts (BWPs);

[0536] The number of frequency domain objects within a resource object or a set of resource objects;

[0537] The number of activated BWPs within a resource object or a set of resource objects;

[0538] The number of frequency domain objects or BWPs having an association relationship;

[0539] The number of frequency domain objects or BWPs used for scheduling;

[0540] The number of frequency domain objects or BWPs being scheduled;

[0541] The number of frequency domain objects or BWPs having a scheduling relationship;

[0542] Wherein, the type A is multiple frequency domain objects as multiple BWPs;

[0543] The type B is multiple frequency domain objects as one BWP.

[0544] Optionally, the type of the frequency domain object includes at least one of the following:

[0545] Continuous frequency domain objects;

[0546] Discontinuous frequency domain objects.

[0547] Optionally, the number of frequency domain objects within a resource object or a set of resource objects includes at least one of the following:

[0548] The number of frequency domain objects within a resource object or a set of resource objects under type A;

[0549] The number of frequency domain objects within a resource object or a set of resource objects under type B;

[0550] The number of frequency domain objects within a resource object or a set of resource objects that can be scheduled by the same scheduling resource object;

[0551] The number of frequency domain objects within a resource object or a set of resource objects corresponding to a first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0552] Optionally, the number of activated bandwidth parts (BWPs) within a resource object or a set of resource objects includes at least one of the following:

[0553] The number of activated BWPs within a resource object or a set of resource objects under type A;

[0554] The number of activated BWPs within a resource object or a set of resource objects of type B;

[0555] The number of activated BWPs within a resource object or a set of resource objects scheduled by the same scheduling resource object;

[0556] The number of activated BWPs within a resource object or a set of resource objects corresponding to a first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0557] Optionally, the first terminal capability information and / or the second terminal capability information is / are related to at least one of the following:

[0558] Frequency band;

[0559] Frequency band combination;

[0560] Bandwidth;

[0561] Bandwidth combination;

[0562] Frequency range;

[0563] Carrier type.

[0564] Optionally, the allocation method of the control resource includes at least one of the following:

[0565] There is only one frequency-domain object in the resource object with a control resource or a control resource part;

[0566] There can be at least one frequency-domain object in the resource object with a second target object, where the second target object includes at least one of the following: control resource, control resource part.

[0567] Optionally, in the case where the allocation method of the control resource includes that there is only one frequency-domain object in the resource object with a control resource or a control resource part, the scheduling relationship corresponding to the control resource or the control resource part includes at least one of the following:

[0568] The control resource or the control resource part is used to schedule the frequency-domain object where the control resource or the control resource part is located;

[0569] The control resource or the control resource part is used to schedule the frequency-domain object or BWP associated with the control resource or the control resource part.

[0570] Optionally, the associated frequency-domain object includes at least one of the following:

[0571] Frequency domain objects associated with the same second information or the same set of second information as the frequency domain object where the control resource or the control resource part is located, the second information including at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0572] Frequency domain objects associated with the same BWP or the same BWP group as the frequency domain object used for scheduling the control resource.

[0573] Optionally, when the allocation method of the control resource includes that there can be at least one second target object on the resource object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0574] The second target object on the frequency domain object can be used to schedule the frequency domain object or BWP where the second target object is located;

[0575] The second target object on the frequency domain object can be used to schedule the frequency domain object or BWP associated with the second target object;

[0576] The second target object on the frequency domain object can be used to schedule the frequency domain object or BWP with a scheduling relationship.

[0577] Optionally, the associated frequency domain objects include at least one of the following:

[0578] Frequency domain objects associated with the same third information or the same set of third information as the frequency domain object where the second target object is located, the third information including at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0579] Frequency domain objects associated with the same BWP or the same BWP group as the frequency domain object used for scheduling the frequency domain object where the second target object is located.

[0580] Optionally, the processor is configured to:

[0581] Determine first information according to at least one of the following, the first information including the allocation method of the control resource and / or the scheduling relationship corresponding to the control resource:

[0582] Network device indication;

[0583] The scheduling relationship corresponding to the control resource;

[0584] The allocation method of the control resource;

[0585] Resource object type, the resource object type including at least one of the following: type A, type B, where type A is multiple frequency domain objects as multiple BWPs, and type B is multiple frequency domain objects as one BWP;

[0586] The number of frequency domain objects;

[0587] The number of activated BWPs.

[0588] Optionally, the scheduling relationship corresponding to the control resource includes at least one of the following, or the scheduling relationship corresponding to the control resource is related to at least one of the following:

[0589] Scheduling a BWP;

[0590] Scheduling a frequency domain object;

[0591] The scheduled BWP;

[0592] The set of scheduled BWPs;

[0593] The scheduled frequency domain object;

[0594] The set of scheduled frequency domain objects;

[0595] The combination of the scheduled BWP and the scheduled BWP;

[0596] The combination of the scheduled frequency domain object and the scheduled frequency domain object;

[0597] The combination of the scheduled BWP and the scheduled frequency domain object;

[0598] The combination of the scheduled frequency domain object and the scheduled BWP.

[0599] Optionally, the frequency domain object includes one of the following: frequency portion, frequency band, carrier, subband; and / or

[0600] The control resource includes one of the following: control resource set, control channel, candidate control channel, control channel element, resource element group, search space; and / or

[0601] The resource object includes a cell.

[0602] Optionally, one or more control resources are associated with one or more target information, and the target information includes at least one of the following: transmission configuration indication TCI, resource pool identifier, transmit receive point TRP, repetition configuration.

[0603] Optionally, each control resource is associated with different target information.

[0604] Preferably, an embodiment of the present application further provides a terminal, including a processor, a memory, a program or instruction stored on the memory and executable on the processor, and when the program or instruction is executed by the processor, it implements each process of the communication processing method embodiment described above and can achieve the same technical effect. To avoid repetition, it will not be elaborated here. Specifically, Figure 17 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0605] The terminal 1700 includes, but is not limited to, at least some components such as a radio frequency unit 1701, a network module 1702, an audio output unit 1703, an input unit 1704, a sensor 1705, a display unit 1706, a user input unit 1707, an interface unit 1708, a memory 1709, and a processor 1710.

[0606] Those skilled in the art can understand that the terminal 1700 may further include a power source (such as a battery) for supplying power to each component. The power source can be logically connected to the processor 1710 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 17 The terminal structure shown does not limit the terminal. The terminal may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements, which will not be elaborated here.

[0607] It should be understood that in the embodiments of the present application, the input unit 1704 may include a graphics processing unit (GPU) 17041 and a microphone 17042. The graphics processor 17041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1706 may include a display panel 17061, and the display panel 17061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1707 includes at least one of a touch panel 17071 and other input devices 17072. The touch panel 17071 is also called a touch screen. The touch panel 17071 may include two parts: a touch detection device and a touch controller. The other input devices 17072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated here.

[0608] In the embodiments of the present application, after the radio frequency unit 1701 receives downlink data from an access network device, it can be transmitted to the processor 1710 for processing; in addition, the radio frequency unit 1701 can send uplink data to a network side device. Generally, the radio frequency unit 1701 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0609] The memory 1709 can be used to store software programs or instructions as well as various data. The memory 1709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area may store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1709 may include a volatile memory or a non-volatile memory, or the memory 1709 may include both a volatile memory and a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchronous link dynamic random access memory (Synch link DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DRRAM). The memory 1709 in the embodiments of the present application includes but is not limited to these and any other suitable types of memories.

[0610] The processor 1710 may include one or more processing units; optionally, the processor 1710 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to an operating system, a user interface, application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above modem processor may not be integrated into the processor 1710 either.

[0611] Among them, the radio frequency unit 1701 is used for:

[0612] Transmit the first information; and / or

[0613] Obtain the first information;

[0614] Among them, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources;

[0615] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency-domain object.

[0616] Optionally, the radio frequency unit 1701 is configured to:

[0617] Send first terminal capability information for at least one resource object, where the first terminal capability information includes: the first information supported by the terminal.

[0618] Optionally, the radio frequency unit 1701 is further configured to:

[0619] Send second terminal capability information, where the second terminal capability information further includes at least one of the following:

[0620] The number of resource objects;

[0621] The number of resource objects including multiple frequency-domain objects;

[0622] Frequency band combination;

[0623] Resource object type, where the resource object type includes at least one of the following: type A, type B;

[0624] The type of frequency-domain object;

[0625] The interval between frequency-domain objects;

[0626] The number of frequency-domain objects;

[0627] The number of activated bandwidth parts BWP;

[0628] The number of frequency-domain objects within a resource object or a set of resource objects;

[0629] The number of activated BWP within a resource object or a set of resource objects;

[0630] The number of frequency-domain objects or BWP with an association relationship;

[0631] The number of frequency-domain objects or BWP for scheduling;

[0632] The number of frequency-domain objects or BWP as being scheduled;

[0633] The number of frequency-domain objects or BWP with a scheduling relationship;

[0634] Wherein, the type A is that multiple frequency-domain objects are multiple BWP;

[0635] The type B is that multiple frequency-domain objects are one BWP.

[0636] Optionally, the type of the frequency-domain object includes at least one of the following:

[0637] Continuous frequency-domain objects;

[0638] Discontinuous frequency-domain objects.

[0639] Optionally, the number of frequency-domain objects in the resource object or the set of resource objects includes at least one of the following:

[0640] The number of frequency-domain objects in a resource object or a set of resource objects of type A;

[0641] The number of frequency-domain objects in a resource object or a set of resource objects of type B;

[0642] The number of frequency-domain objects in a resource object or a set of resource objects that can be scheduled by the same scheduling resource object;

[0643] The number of frequency-domain objects in the resource object or the set of resource objects corresponding to the first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0644] Optionally, the number of active bandwidth parts (BWPs) in the resource object or the set of resource objects includes at least one of the following:

[0645] The number of active BWPs in a resource object or a set of resource objects of type A;

[0646] The number of active BWPs in a resource object or a set of resource objects of type B;

[0647] The number of active BWPs in a resource object or a set of resource objects that are scheduled by the same scheduling resource object;

[0648] The number of active BWPs in the resource object or the set of resource objects corresponding to the first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0649] Optionally, the first terminal capability information and / or the second terminal capability information is / are related to at least one of the following:

[0650] Frequency band;

[0651] Frequency band combination;

[0652] Bandwidth;

[0653] Bandwidth combination;

[0654] Frequency range;

[0655] Carrier type.

[0656] Optionally, the allocation method of the control resource includes at least one of the following:

[0657] There is only one frequency-domain object in the resource object where the control resource or a part of the control resource exists;

[0658] There can be at least one frequency-domain object in the resource object where a second target object exists, and the second target object includes at least one of the following: control resource, part of the control resource.

[0659] Optionally, when the allocation method of the control resource includes that there is only one frequency-domain object in the resource object where the control resource or a part of the control resource exists, the scheduling relationship corresponding to the control resource or the part of the control resource includes at least one of the following:

[0660] The control resource or the part of the control resource is used to schedule the frequency-domain object where the control resource or the part of the control resource is located;

[0661] The control resource or the part of the control resource is used to schedule the frequency-domain object or BWP associated with the control resource or the part of the control resource.

[0662] Optionally, the associated frequency-domain object includes at least one of the following:

[0663] The frequency-domain object associated with the same second information or the same set of second information as the frequency-domain object where the control resource or the part of the control resource is located, and the second information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0664] The frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the control resource.

[0665] Optionally, when the allocation method of the control resource includes that there can be at least one frequency-domain object in the resource object where the second target object exists, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0666] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP where the second target object is located;

[0667] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP associated with the second target object;

[0668] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP having a scheduling relationship.

[0669] Optionally, the associated frequency-domain object includes at least one of the following:

[0670] Frequency domain objects associated with the same third information or the same set of third information as the frequency domain object where the second target object is located, where the third information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0671] Frequency domain objects associated with the frequency domain object used to schedule the frequency domain object where the second target object is located and associated with the same BWP or the same BWP group.

[0672] Optionally, the processor 1710 is configured to:

[0673] Determine first information according to at least one of the following, where the first information includes the allocation method of control resources and / or the scheduling relationship corresponding to the control resources:

[0674] Network device indication;

[0675] Scheduling relationship corresponding to the control resources;

[0676] Allocation method of the control resources;

[0677] Resource object type, where the resource object type includes at least one of the following: type A, type B, where type A is multiple frequency domain objects as multiple BWPs, and type B is multiple frequency domain objects as one BWP;

[0678] Number of frequency domain objects;

[0679] Number of active BWPs.

[0680] Optionally, the scheduling relationship corresponding to the control resources includes at least one of the following, or the scheduling relationship corresponding to the control resources is related to at least one of the following:

[0681] Scheduling BWP;

[0682] Scheduling frequency domain object;

[0683] Scheduled BWP;

[0684] Scheduled BWP set;

[0685] Scheduled frequency domain object;

[0686] Scheduled frequency domain object set;

[0687] Combination of scheduling BWP and scheduled BWP;

[0688] Combination of scheduling frequency domain object and scheduled frequency domain object;

[0689] Combination of scheduling BWP and scheduled frequency domain object;

[0690] Combination of scheduling frequency domain object and scheduled BWP.

[0691] Optionally, the frequency-domain object includes one of the following: frequency portion, frequency band, carrier, sub-band; and / or

[0692] The control resource includes one of the following: control resource set, control channel, candidate control channel, control channel element, resource element group, search space; and / or

[0693] The resource object includes a cell.

[0694] Optionally, one or more control resources are associated with one or more target information, and the target information includes at least one of the following: transmission configuration indication (TCI), resource pool identifier, transmit receive point (TRP), repetition configuration.

[0695] Optionally, each control resource is associated with different target information.

[0696] An embodiment of this application also provides a readable storage medium. A program or instruction is stored on the computer-readable storage medium. When the program or instruction is executed by a processor, each process of the information transmission method embodiment described above is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be elaborated here.

[0697] Among them, the computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc, etc.

[0698] Such as Figure 18 As shown, the information transmission device 1800 in the embodiment of this application is applied to a network-side device and includes:

[0699] A second transmission module 1801, configured to receive first information; and / or

[0700] Transmit the first information;

[0701] Among them, the first information includes at least one of the following: the allocation method of the control resource, the scheduling relationship corresponding to the control resource;

[0702] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency-domain object.

[0703] Optionally, the second transmission module 1801 is configured to:

[0704] Receive first terminal capability information sent by a terminal for at least one resource object, where the first terminal capability information includes: the first information supported by the terminal.

[0705] Optionally, the device further includes:

[0706] A receiving module, configured to receive second terminal capability information sent by a terminal, where the second terminal capability information includes at least one of the following:

[0707] The number of resource objects;

[0708] The number of resource objects including multiple frequency-domain objects;

[0709] Frequency band combination;

[0710] Resource object type, where the resource object type includes at least one of the following: type A, type B;

[0711] The type of frequency-domain object;

[0712] The interval between frequency-domain objects;

[0713] The number of frequency-domain objects;

[0714] The number of activated bandwidth parts (BWPs);

[0715] The number of frequency-domain objects in a resource object or a resource object set;

[0716] The number of activated BWPs in a resource object or a resource object set;

[0717] The number of frequency-domain objects or BWPs with an association relationship;

[0718] The number of frequency-domain objects or BWPs for scheduling;

[0719] The number of frequency-domain objects or BWPs as the scheduled ones;

[0720] The number of frequency-domain objects or BWPs with a scheduling relationship;

[0721] Wherein, the type A is that multiple frequency-domain objects serve as multiple BWPs;

[0722] The type B is that multiple frequency-domain objects serve as one BWP.

[0723] Optionally, the type of the frequency-domain object includes at least one of the following:

[0724] Continuous frequency-domain objects;

[0725] Discontinuous frequency-domain objects.

[0726] Optionally, the number of frequency-domain objects in the resource object or the resource object set includes at least one of the following:

[0727] The number of frequency-domain objects in a resource object or a resource object set of type A;

[0728] The number of frequency-domain objects in a resource object or a set of resource objects under type B;

[0729] The number of frequency-domain objects in a resource object or a set of resource objects that can be scheduled by the same scheduling resource object;

[0730] The number of frequency-domain objects in a resource object or a set of resource objects corresponding to a first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0731] Optionally, the number of activated bandwidth parts (BWPs) in the resource object or the set of resource objects includes at least one of the following:

[0732] The number of activated BWPs in a resource object or a set of resource objects under type A;

[0733] The number of activated BWPs in a resource object or a set of resource objects under type B;

[0734] The number of activated BWPs in a resource object or a set of resource objects that are scheduled by the same scheduling resource object;

[0735] The number of activated BWPs in a resource object or a set of resource objects corresponding to a first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0736] Optionally, the first terminal capability information and / or the second terminal capability information is / are related to at least one of the following:

[0737] Frequency band;

[0738] Frequency band combination;

[0739] Bandwidth;

[0740] Bandwidth combination;

[0741] Frequency range;

[0742] Carrier type.

[0743] Optionally, the allocation method of the control resource includes at least one of the following:

[0744] There is a control resource or a control resource part on only one frequency-domain object in the resource object;

[0745] There can be at least one frequency-domain object in the resource object on which there is a second target object, where the second target object includes at least one of the following: control resource, control resource part.

[0746] Optionally, in the case where the allocation method of the control resource includes that there is only one frequency-domain object in the resource object on which the control resource or the control resource part exists, the scheduling relationship corresponding to the control resource or the control resource part includes at least one of the following:

[0747] The control resource or the control resource part is used to schedule the frequency-domain object where the control resource or the control resource part is located;

[0748] The control resource or the control resource part is used to schedule the frequency-domain object or BWP associated with the control resource or the control resource part.

[0749] Optionally, the associated frequency-domain object includes at least one of the following:

[0750] A frequency-domain object associated with the same second information or the same set of second information as the frequency-domain object where the control resource or the control resource part is located, and the second information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0751] A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the control resource.

[0752] Optionally, in the case where the allocation method of the control resource includes that there can be at least one frequency-domain object in the resource object on which a second target object exists, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0753] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP where the second target object is located;

[0754] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP associated with the second target object;

[0755] The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP having a scheduling relationship.

[0756] Optionally, the associated frequency-domain object includes at least one of the following:

[0757] A frequency-domain object associated with the same third information or the same set of third information as the frequency-domain object where the second target object is located, and the third information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0758] A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the second target object.

[0759] Optionally, the device further includes:

[0760] A determination module, configured to determine first information according to at least one of the following, where the first information includes an allocation manner of control resources and / or a scheduling relationship corresponding to the control resources:

[0761] The scheduling relationship corresponding to the control resources;

[0762] The allocation manner of the control resources;

[0763] A resource object type, where the resource object type includes at least one of the following: type A, type B, where type A is multiple frequency-domain objects as multiple BWPs, and type B is multiple frequency-domain objects as one BWP;

[0764] The number of frequency-domain objects;

[0765] The number of activated BWPs.

[0766] Optionally, the scheduling relationship corresponding to the control resources includes at least one of the following, or the scheduling relationship corresponding to the control resources is related to at least one of the following:

[0767] The scheduled BWP;

[0768] The scheduled frequency-domain object;

[0769] The BWP to be scheduled;

[0770] The set of BWPs to be scheduled;

[0771] The frequency-domain object to be scheduled;

[0772] The set of frequency-domain objects to be scheduled;

[0773] The combination of the scheduled BWP and the BWP to be scheduled;

[0774] The combination of the scheduled frequency-domain object and the frequency-domain object to be scheduled;

[0775] The combination of the scheduled BWP and the frequency-domain object to be scheduled;

[0776] The combination of the scheduled frequency-domain object and the BWP to be scheduled.

[0777] Optionally, the frequency-domain object includes one of the following: frequency portion, frequency band, carrier, sub-band; and / or

[0778] The control resources include one of the following: control resource set, control channel, candidate control channel, control channel element, resource element group, search space; and / or

[0779] The resource object includes a cell.

[0780] Optionally, one or more control resources are associated with one or more pieces of target information, where the target information includes at least one of the following: Transmission Configuration Indicator (TCI), resource pool identifier, Transmission and Reception Point (TRP), and repetition configuration.

[0781] Optionally, each control resource is associated with different target information.

[0782] An embodiment of this application further provides a network-side device, including a processor and a communication interface. The communication interface is configured to receive first information; and / or

[0783] transmit the first information;

[0784] where the first information includes at least one of the following: the allocation method of control resources, and the scheduling relationship corresponding to the control resources;

[0785] The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency-domain object.

[0786] Optionally, the communication interface is configured to:

[0787] receive terminal capability information sent by a terminal for at least one resource object, where the terminal capability information includes: the first information supported by the terminal.

[0788] Optionally, the communication interface is further configured to:

[0789] receive second terminal capability information sent by the terminal, where the second terminal capability information includes at least one of the following:

[0790] the number of resource objects;

[0791] the number of resource objects including multiple frequency-domain objects;

[0792] frequency band combination;

[0793] resource object type, where the resource object type includes at least one of the following: type A, type B;

[0794] the type of frequency-domain object;

[0795] the interval between frequency-domain objects;

[0796] the number of frequency-domain objects;

[0797] the number of activated Bandwidth Parts (BWPs);

[0798] the number of frequency-domain objects in a resource object or a set of resource objects;

[0799] the number of activated BWPs in a resource object or a set of resource objects;

[0800] The number of frequency-domain objects or BWPs having an association relationship;

[0801] The number of frequency-domain objects or BWPs used for scheduling;

[0802] The number of frequency-domain objects or BWPs being scheduled;

[0803] The number of frequency-domain objects or BWPs having a scheduling relationship;

[0804] Wherein, the type A is multiple frequency-domain objects as multiple BWPs;

[0805] The type B is multiple frequency-domain objects as one BWP.

[0806] Optionally, the type of the frequency-domain object includes at least one of the following:

[0807] Continuous frequency-domain objects;

[0808] Discontinuous frequency-domain objects.

[0809] Optionally, the number of frequency-domain objects in the resource object or resource object set includes at least one of the following:

[0810] The number of frequency-domain objects in one resource object or resource object set under type A;

[0811] The number of frequency-domain objects in one resource object or resource object set under type B;

[0812] The number of frequency-domain objects in the resource object or resource object set that can be scheduled by the same scheduling resource object;

[0813] The number of frequency-domain objects in the resource object or resource object set corresponding to the first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0814] Optionally, the number of active bandwidth parts (BWPs) in the resource object or resource object set includes at least one of the following:

[0815] The number of active BWPs in one resource object or resource object set under type A;

[0816] The number of active BWPs in one resource object or resource object set under type B;

[0817] The number of active BWPs in the resource object or resource object set scheduled by the same scheduling resource object;

[0818] The number of activated BWPs within a resource object or a set of resource objects corresponding to a first target object, where the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

[0819] Optionally, the first terminal capability information and / or the second terminal capability information are related to at least one of the following:

[0820] Frequency band;

[0821] Frequency band combination;

[0822] Bandwidth;

[0823] Bandwidth combination;

[0824] Frequency range;

[0825] Carrier type.

[0826] Optionally, the allocation method of the control resource includes at least one of the following:

[0827] There is only one frequency-domain object in the resource object where the control resource or the control resource part exists;

[0828] There can be at least one frequency-domain object in the resource object where a second target object exists, and the second target object includes at least one of the following: control resource, control resource part.

[0829] Optionally, in the case where the allocation method of the control resource includes that there is only one frequency-domain object in the resource object where the control resource or the control resource part exists, the scheduling relationship corresponding to the control resource or the control resource part includes at least one of the following:

[0830] The control resource or the control resource part is used to schedule the frequency-domain object where the control resource or the control resource part is located;

[0831] The control resource or the control resource part is used to schedule the frequency-domain object or BWP associated with the control resource or the control resource part.

[0832] Optionally, the associated frequency-domain object includes at least one of the following:

[0833] A frequency-domain object associated with the same second information or the same set of second information as the frequency-domain object where the control resource or the control resource part is located, and the second information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0834] A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the control resource.

[0835] Optionally, when the allocation method of the control resource includes that there is at least one second target object on a frequency domain object in the resource object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0836] The second target object on the frequency domain object can be used to schedule the frequency domain object or BWP where the second target object is located;

[0837] The second target object on the frequency domain object can be used to schedule the frequency domain object or BWP associated with the second target object;

[0838] The second target object on the frequency domain object can be used to schedule the frequency domain object or BWP with a scheduling relationship.

[0839] Optionally, the associated frequency domain object includes at least one of the following:

[0840] A frequency domain object associated with the same third information or the same set of third information as the frequency domain object where the second target object is located, and the third information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration;

[0841] A frequency domain object associated with the same BWP or the same BWP group as the frequency domain object used to schedule the frequency domain object where the second target object is located.

[0842] Optionally, the processor is configured to:

[0843] Determine first information according to at least one of the following, where the first information includes the allocation method of the control resource and / or the scheduling relationship corresponding to the control resource:

[0844] The scheduling relationship corresponding to the control resource;

[0845] The allocation method of the control resource;

[0846] The resource object type, where the resource object type includes at least one of the following: type A, type B, type A is multiple frequency domain objects as multiple BWPs, and type B is multiple frequency domain objects as one BWP;

[0847] The number of frequency domain objects;

[0848] The number of active BWPs.

[0849] Optionally, the scheduling relationship corresponding to the control resource includes at least one of the following, or the scheduling relationship corresponding to the control resource is related to at least one of the following:

[0850] Scheduled BWP;

[0851] Scheduled frequency domain object;

[0852] Scheduled BWP;

[0853] Scheduled BWP set;

[0854] Scheduled frequency domain object;

[0855] Scheduled frequency domain object set;

[0856] Combination of scheduled BWP and scheduled BWP;

[0857] Combination of scheduled frequency domain object and scheduled frequency domain object;

[0858] Combination of scheduled BWP and scheduled frequency domain object;

[0859] Combination of scheduled frequency domain object and scheduled BWP.

[0860] Optionally, the frequency domain object includes one of the following: frequency part, frequency band, carrier, sub-band; and / or

[0861] The control resource includes one of the following: control resource set, control channel, candidate control channel, control channel element, resource element group, search space; and / or

[0862] The resource object includes a cell.

[0863] Optionally, one or more control resources are associated with one or more target information, and the target information includes at least one of the following: transmission configuration indication TCI, resource pool identifier, transmit receive point TRP, repetition configuration.

[0864] Optionally, each control resource is associated with different target information.

[0865] Specifically, the embodiments of the present application further provide a network-side device. As Figure 19 shown, the network-side device 1900 includes: an antenna 1901, a radio frequency device 1902, a baseband device 1903, a processor 1904, and a memory 1905. The antenna 1901 is connected to the radio frequency device 1902. In the uplink direction, the radio frequency device 1902 receives information through the antenna 1901 and sends the received information to the baseband device 1903 for processing. In the downlink direction, the baseband device 1903 processes the information to be sent and sends it to the radio frequency device 1902. After processing the received information, the radio frequency device 1902 sends it out through the antenna 1901.

[0866] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1903, and the baseband device 1903 includes a baseband processor.

[0867] The baseband device 1903 may include, for example, at least one baseband board, and a plurality of chips are arranged on the baseband board, such as Figure 19As shown, one of the chips, for example, a baseband processor, is connected to the memory 1905 through a bus interface to call the program in the memory 1905 and execute the operations of the network device shown in the above method embodiments.

[0868] The network-side device may further include a network interface 1906, which is, for example, a common public radio interface (CPRI).

[0869] Specifically, the network-side device 1900 in the embodiments of the present application further includes: instructions or programs stored on the memory 1905 and executable on the processor 1904. The processor 1904 calls the instructions or programs in the memory 1905 to execute Figure 18 the methods executed by the modules shown, and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0870] The embodiments of the present application further provide a readable storage medium, on which programs or instructions are stored. When the programs or instructions are executed by a processor, the various processes of the above information transmission method embodiments are implemented, and the same technical effects can be achieved. To avoid repetition, it will not be elaborated here.

[0871] Wherein, the processor is the processor in the network-side device described in the above embodiments. The readable storage medium may be non-volatile or non-transient. The readable storage medium may include computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disks or optical disks, etc.

[0872] Optionally, as Figure 20 shown, the embodiments of the present application further provide a communication device 2000, including a processor 2001 and a memory 2002. Programs or instructions that can run on the processor 2001 are stored on the memory 2002. For example, when the communication device 2000 is a terminal, when the programs or instructions are executed by the processor 2001, the various steps of the above information transmission method embodiments are implemented, and the same technical effects can be achieved. When the communication device 2000 is a network-side device, when the programs or instructions are executed by the processor 2001, the various steps of the above information transmission method embodiments are implemented, and the same technical effects can be achieved. To avoid repetition, it will not be elaborated here.

[0873] The embodiments of the present application further provide a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above information transmission method embodiments, and the same technical effects can be achieved. To avoid repetition, it will not be elaborated here.

[0874] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

[0875] The embodiments of the present application further provide a computer program / program product. The computer program / program product is stored in a storage medium and is executed by at least one processor to implement the various processes of the above information transmission method embodiments, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0876] The embodiments of the present application further provide a communication system, including: a terminal and a network-side device. The terminal can be used to execute the steps of the above information transmission method, and the network-side device can be used to execute the steps of the above information transmission processing method.

[0877] It should be noted that in this article, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of another identical element in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0878] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions for causing a terminal or a network-side device to execute the methods described in the various embodiments of the present application.

[0879] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Those of ordinary skill in the art, under the inspiration of the present application, without departing from the purpose of the present application and the scope protected by the claims, can also make many forms of embodiments, and these embodiments are all within the protection scope of the present application.

Claims

1. An information transmission method, characterized in that, Including: The terminal sends the first information; And / or The terminal obtains the first information; Wherein, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources; The first information is related to at least one resource object, and the resource object is associated with or contains at least one frequency-domain object.

2. The method according to claim 1, wherein The terminal sending the first information includes: The terminal sends first terminal capability information for at least one resource object, and the first terminal capability information includes: the first information supported by the terminal.

3. The method according to claim 1, wherein The method further includes: The terminal sends second terminal capability information, and the second terminal capability information includes at least one of the following: The number of resource objects; The number of resource objects containing multiple frequency-domain objects; Frequency band combination; Resource object type, and the resource object type includes at least one of the following: type A, type B; The type of frequency-domain object; The interval between frequency-domain objects; The number of frequency-domain objects; The number of activated bandwidth parts BWP; The number of frequency-domain objects in a resource object or a set of resource objects; The number of activated BWP in a resource object or a set of resource objects; The number of frequency-domain objects or BWP with an associated relationship; The number of frequency-domain objects or BWP used for scheduling; The number of frequency-domain objects or BWP as the scheduled ones; The number of frequency-domain objects or BWP with a scheduling relationship; Wherein, type A is that multiple frequency-domain objects are multiple BWP; Type B is that multiple frequency-domain objects are one BWP.

4. The method according to claim 3, wherein The number of frequency-domain objects in a resource object or a set of resource objects includes at least one of the following: The number of frequency-domain objects in a resource object or a set of resource objects of type A; The number of frequency-domain objects in a resource object or a set of resource objects of type B; The number of frequency-domain objects in a resource object or a set of resource objects that can be scheduled by the same scheduling resource object; The number of frequency-domain objects in a resource object or a set of resource objects corresponding to a first target object, and the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, cyclic prefix CP, subcarrier spacing combination, carrier type combination.

5. The method according to claim 3, wherein The number of activated bandwidth parts BWP in a resource object or a set of resource objects includes at least one of the following: The number of activated BWP in a resource object or a set of resource objects of type A; The number of activated BWP in a resource object or a set of resource objects of type B; The number of activated BWP in a resource object or a set of resource objects scheduled by the same scheduling resource object; The number of activated BWP in a resource object or a set of resource objects corresponding to a first target object, and the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

6. The method according to any one of claims 1-5, characterized in that, The allocation method of the control resources includes at least one of the following: There is only one frequency-domain object in the resource object with a control resource or a control resource part; There can be at least one frequency-domain object in the resource object with a second target object, and the second target object includes at least one of the following: control resource, control resource part.

7. The method according to claim 6, wherein In the case where the allocation mode of the control resource includes that there is only one frequency-domain object among the resource objects where the control resource or a part of the control resource exists, the scheduling relationship corresponding to the control resource or the part of the control resource includes at least one of the following: The control resource or the part of the control resource is used to schedule the frequency-domain object where the control resource or the part of the control resource is located; The control resource or the part of the control resource is used to schedule the frequency-domain object or BWP associated with the control resource or the part of the control resource.

8. The method according to claim 7, wherein The associated frequency-domain object includes at least one of the following: A frequency-domain object associated with the same second information or the same set of second information as the frequency-domain object where the control resource or the part of the control resource is located, and the second information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration; A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the control resource.

9. The method according to claim 6, wherein In the case where the allocation mode of the control resource includes that there can be at least one frequency-domain object among the resource objects where a second target object exists, the scheduling relationship corresponding to the control resource includes at least one of the following: The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP where the second target object is located; The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP associated with the second target object; The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP having a scheduling relationship.

10. The method according to claim 9, wherein The associated frequency-domain object includes at least one of the following: A frequency-domain object associated with the same third information or the same set of third information as the frequency-domain object where the second target object is located, and the third information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration; A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the frequency-domain object where the second target object is located.

11. The method according to any one of claims 1-10, characterized in that, The terminal determines the first information including: Determine the first information according to at least one of the following, and the first information includes the allocation mode of the control resource and / or the scheduling relationship corresponding to the control resource: Network device indication; The scheduling relationship corresponding to the control resource; The allocation mode of the control resource; Resource object type, and the resource object type includes at least one of the following: type A, type B, where type A is multiple frequency-domain objects as multiple BWPs, and type B is multiple frequency-domain objects as one BWP; The number of frequency-domain objects; The number of activated BWPs.

12. The method according to any one of claims 1-11, characterized in that, The scheduling relationship corresponding to the control resource includes at least one of the following, or the scheduling relationship corresponding to the control resource is related to at least one of the following: Scheduled BWP; Scheduled frequency-domain object; Scheduled BWP; Set of scheduled BWPs; Scheduled frequency-domain object; Set of scheduled frequency-domain objects; Combination of scheduled BWP and scheduled BWP; Combination of scheduled frequency-domain object and scheduled frequency-domain object; Combination of scheduled BWP and scheduled frequency-domain object; Combination of scheduled frequency-domain object and scheduled BWP.

13. The method according to any one of claims 1-12, characterized in that, The frequency-domain object includes one of the following: frequency part, frequency band, carrier, sub-band; and / or The control resource includes one of the following: control resource set, control channel, candidate control channel, control channel element, resource element group, search space; and / or The resource object includes a cell.

14. The method according to any one of claims 1-13, characterized in that, One or more control resources are associated with one or more target information, and the target information includes at least one of the following: Transmission Configuration Indicator (TCI), resource pool identifier, Transmit / Receive Point (TRP), repetition configuration.

15. An information transmission method, characterized in that, including: The network device receives first information; and / or The network device sends first information; wherein, the first information includes at least one of the following: the allocation method of the control resource, the scheduling relationship corresponding to the control resource; The first information is related to at least one resource object, and the resource object is associated with or contains at least one frequency domain object.

16. The method according to claim 15, wherein The network device receiving the first information includes: The network device receives first terminal capability information sent by a terminal for at least one resource object, and the first terminal capability information includes: the first information supported by the terminal.

17. The method according to claim 15, wherein further including: The network device receives second terminal capability information sent by the terminal, and the second terminal capability information includes at least one of the following: the number of resource objects; the number of resource objects containing multiple frequency domain objects; frequency band combination; resource object type, and the resource object type includes at least one of the following: type A, type B; the type of the frequency domain object; the interval between frequency domain objects; the number of frequency domain objects; the number of activated Bandwidth Parts (BWPs); the number of frequency domain objects within a resource object or a set of resource objects; the number of activated BWPs within a resource object or a set of resource objects; the number of frequency domain objects or BWPs having an association relationship; the number of frequency domain objects or BWPs used for scheduling; the number of frequency domain objects or BWPs serving as scheduled objects; the number of frequency domain objects or BWPs having a scheduling relationship; wherein, type A means multiple frequency domain objects serve as multiple BWPs; type B means multiple frequency domain objects serve as one BWP.

18. The method according to claim 17, wherein The number of frequency domain objects within the resource object or the set of resource objects includes at least one of the following: the number of frequency domain objects within a resource object or a set of resource objects of type A; the number of frequency domain objects within a resource object or a set of resource objects of type B; the number of frequency domain objects within a resource object or a set of resource objects that can be scheduled by the same scheduling resource object; the number of frequency domain objects within a resource object or a set of resource objects corresponding to a first target object, and the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, Cyclic Prefix (CP), subcarrier spacing combination, carrier type combination.

19. The method according to claim 17, wherein The number of activated Bandwidth Parts (BWPs) within the resource object or the set of resource objects includes at least one of the following: the number of activated BWPs within a resource object or a set of resource objects of type A; the number of activated BWPs within a resource object or a set of resource objects of type B; the number of activated BWPs within a resource object or a set of resource objects scheduled by the same scheduling resource object; the number of activated BWPs within a resource object or a set of resource objects corresponding to a first target object, and the first target object includes at least one of the following: subcarrier spacing, carrier type, frequency range, frequency band, CP, subcarrier spacing combination, carrier type combination.

20. The method according to any one of claims 15-19, characterized in that, The allocation method of the control resource includes at least one of the following: There is a control resource or a control resource portion on only one frequency-domain object in the resource object; There can be at least one frequency-domain object in the resource object on which there is a second target object, and the second target object includes at least one of the following: a control resource, a control resource portion; 21. The method according to claim 20, wherein When the allocation method of the control resource includes that there is a control resource or a control resource portion on only one frequency-domain object in the resource object, the scheduling relationship corresponding to the control resource or the control resource portion includes at least one of the following: The control resource or the control resource portion is used to schedule the frequency-domain object where the control resource or the control resource portion is located; The control resource or the control resource portion is used to schedule the frequency-domain object or BWP associated with the control resource or the control resource portion; 22. The method according to claim 21, wherein The associated frequency-domain object includes at least one of the following: A frequency-domain object associated with the same second information or the same set of second information as the frequency-domain object where the control resource or the control resource portion is located, and the second information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration; A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the control resource; 23. The method according to claim 20, wherein When the allocation method of the control resource includes that there can be at least one frequency-domain object in the resource object on which there is a second target object, the scheduling relationship corresponding to the control resource includes at least one of the following: The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP where the second target object is located; The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP associated with the second target object; The second target object on the frequency-domain object can be used to schedule the frequency-domain object or BWP having a scheduling relationship; 24. The method according to claim 23, wherein The associated frequency-domain object includes at least one of the following: A frequency-domain object associated with the same third information or the same set of third information as the frequency-domain object where the second target object is located, and the third information includes at least one of the following: uplink-downlink configuration relationship, frame structure configuration; A frequency-domain object associated with the same BWP or the same BWP group as the frequency-domain object used to schedule the frequency-domain object where the second target object is located; 25. The method according to any one of claims 15 - 24, characterized in that, It further includes: Determining first information according to at least one of the following, where the first information includes the allocation method of the control resource and / or the scheduling relationship corresponding to the control resource: The scheduling relationship corresponding to the control resource; The allocation method of the control resource; The resource object type, where the resource object type includes at least one of the following: type A, type B, type A is multiple frequency-domain objects as multiple BWPs, and type B is multiple frequency-domain objects as one BWP; The number of frequency-domain objects; The number of activated BWPs.

26. An information transmission device, applied to a terminal, is characterized in that It includes: A first transmission module for sending the first information; and / or Determining the first information; wherein, the first information includes at least one of the following: the allocation method of the control resource, the scheduling relationship corresponding to the control resource; The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency-domain object.

27. The device according to claim 26, characterized in that, The first transmission module is used for: Send first terminal capability information for at least one resource object, where the first terminal capability information includes: first information supported by the terminal.

28. A terminal, characterized in that, It includes a processor and a memory, and the memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, the steps of the information transmission method according to any one of claims 1 to 14 are implemented.

29. An information transmission device, applied to a network-side device, characterized in that, It includes: A second transmission module, configured to receive first information; And / or Send first information; Wherein, the first information includes at least one of the following: the allocation method of control resources, the scheduling relationship corresponding to the control resources; The first information is related to at least one resource object, and the resource object is associated with or includes at least one frequency domain object.

30. The device according to claim 29, wherein, The second transmission module is configured to: Receive terminal capability information for at least one resource object sent by a terminal, where the terminal capability information includes: first information supported by the terminal.

31. A network-side device, characterized in that, It includes a processor and a memory, and the memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, the steps of the information transmission method according to any one of claims 15 to 25 are implemented.

32. A readable storage medium, characterized in that, Programs or instructions are stored on the readable storage medium, and when the programs or instructions are executed by a processor, the steps of the information transmission method according to any one of claims 1-25 are implemented.

Images