Information transmission method and apparatus, terminal, and network side device

Abstract

The present application relates to the technical field of communications, and discloses an information transmission method and apparatus, a terminal, and a network side device. The information transmission method in embodiments of the present application comprises: a terminal sends first information; and / or the terminal determines the first information, wherein the first information comprises at least one of the following: 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

Information transmission method, device, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202410076497.9 filed on January 18, 2024, the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] 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 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 / movement, 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, and is not beneficial to UE in the idle mode / inactive mode radio resource control idle state or inactive state (RRC_idle / inactive, for example, initial access / small data transmission (SDT)).

[0005] Therefore, the introduction of flexible resource objects (e.g., flexible cells) enables flexible and efficient utilization of adjacent non-contiguous spectrum from the perspectives of L1 / L2 / L3 signaling, processes, and cell management. This benefits both UEs in the connected and idle states, thereby improving user-perceived data rates, energy savings, system capacity, and coverage. It also simplifies network management complexity and improves energy efficiency. Furthermore, these narrow-bandwidth carriers cannot carry control channel elements (CCEs) with higher aggregation levels. For example, CCE AL 16 requires a maximum of 96 resource blocks (RBs). This hinders the transmission of control information at the cell edge and reduces coverage. Narrow-bandwidth carriers can lead to a higher probability of physical downlink control channel (PDCCH) collisions. Therefore, 6G and later communication systems will support flexible resource object configurations for multiple carriers, frequency parts, bands, and subbands. Implementing the transmission of control resources using flexible resource objects is an urgent issue. Summary of the Invention

[0006] The embodiments of the present application provide an information transmission method, apparatus, terminal, and network-side equipment to achieve transmission of control resources under flexible resource objects.

[0007] In a first aspect, a method for transmitting information is provided, the method comprising:

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

[0009] The terminal obtains the first information;

[0010] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0011] 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.

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

[0013] A first transmission module is configured to send first information; and / or

[0014] Obtaining first information;

[0015] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0016] 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.

[0017] In a third aspect, a method for transmitting information is provided, the method comprising:

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

[0019] The network side device sends the first information;

[0020] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0021] 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.

[0022] In a fourth aspect, an information transmission device is provided, which is applied to a network-side device, including:

[0023] A second transmission module is configured to receive the first information; and / or

[0024] Sending the first message;

[0025] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0026] 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.

[0027] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be 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.

[0028] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to send first information; and / or

[0029] Obtaining first information;

[0030] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0031] 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.

[0032] In the seventh aspect, a network side device is provided, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the third aspect are implemented.

[0033] In an eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive first information; and / or

[0034] Obtaining first information;

[0035] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0036] 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.

[0037] In a ninth aspect, a communication system is provided, comprising: a terminal and a network-side device, wherein 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.

[0038] In a tenth aspect, a readable storage medium is provided, on which a program or instruction is stored. 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.

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

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

[0041] In an embodiment of the present application, by sending and / or obtaining the allocation method of control resources related to at least one resource object and / or the scheduling relationship corresponding to the control resources, the configuration of control resources under flexible resource objects is achieved, thereby realizing the transmission of control resources and improving the performance of the communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0043] FIG2 is a flow chart of an information transmission method according to an embodiment of the present application;

[0044] FIG3 is a schematic diagram of a scheduling relationship under type A when only one frequency domain object in a resource object has a control resource or a control resource portion;

[0045] FIG4 is a schematic diagram of a scheduling relationship under type B when only one frequency domain object in a resource object has a control resource or a control resource portion;

[0046] FIG5 is a schematic diagram of a scheduling relationship under type A when there is a control resource on at least one frequency domain object in the resource object;

[0047] FIG6 is a schematic diagram of a scheduling relationship under type B when there is a control resource on at least one frequency domain object in the resource object;

[0048] FIG7 is a second schematic diagram of a scheduling relationship under type A when there is a control resource on at least one frequency domain object in the resource object;

[0049] FIG8 is a third schematic diagram of a scheduling relationship under type A when there is a control resource on at least one frequency domain object in the resource object;

[0050] FIG9 is a second schematic diagram of a scheduling relationship under type B when there is a control resource on at least one frequency domain object in the resource object;

[0051] FIG10 is a schematic diagram of a scheduling relationship under type A when there is a control resource portion on at least one frequency domain object in the resource object;

[0052] FIG11 is a schematic diagram of a scheduling relationship under type B in which a control resource portion can exist on at least one frequency domain object in a resource object;

[0053] FIG12 is a schematic diagram of a second scheduling relationship under type A when there is a control resource portion on at least one frequency domain object in the resource object;

[0054] FIG13 is a schematic diagram of a scheduling relationship under type A in which a control resource portion can exist on at least one frequency domain object in a resource object;

[0055] FIG14 is a schematic diagram of a second scheduling relationship under type B when there is a control resource portion on at least one frequency domain object in the resource object;

[0056] FIG15 is a second flow chart of the information transmission method according to an embodiment of the present application;

[0057] FIG16 is a schematic diagram of a module of an information transmission device according to an embodiment of the present application;

[0058] FIG17 is a schematic structural diagram of a terminal according to an embodiment of the present application;

[0059] FIG18 is a second schematic diagram of a module of an information transmission device according to an embodiment of the present application;

[0060] FIG19 is a schematic structural diagram of a network-side device according to an embodiment of the present application;

[0061] FIG20 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0062] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0063] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0064] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0065] It is worth noting that the technology described in the embodiments of the present 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 the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0066] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (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 (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (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 (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0067] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0068] The following first describes the technologies related to the embodiments of the present application.

[0069] 1. Bandwidth Part (BWP)

[0070] In New Radio (NR), the network configures a bandwidth workstation (BWP) and / or carrier for user equipment (UE) data transmission. The UE's bandwidth can change dynamically. For example, at the first moment, the UE's traffic volume is high, so the system configures a large bandwidth (BWP1) for the UE. At the second moment, the UE's traffic volume is low, so the system configures a small bandwidth (BWP2) to meet basic communication needs. At the third moment, the system detects large-scale frequency selective fading within the bandwidth where BWP1 resides, or that resources within the frequency range where BWP1 resides are relatively scarce, so it configures a new bandwidth (BWP3) for the UE.

[0071] Each BWP not only has different frequencies and bandwidths, but also can have different configurations. For example, each BWP can have different subcarrier spacing, cyclic prefix (CP) type, and SSB (PSS / SSS PBCH Block) period to suit different services.

[0072] BWP's technical advantages mainly include four aspects:

[0073] 1. UE does not need to support all bandwidths, but only needs to meet the minimum bandwidth requirements, which is conducive to the development of low-cost terminals;

[0074] 2. When the UE traffic volume is not large, the UE can switch to low-bandwidth operation, which can significantly reduce power consumption;

[0075] 3. 5G technology is forward compatible. When 5G adds new technologies, they can be directly run on the new BWP, ensuring the forward compatibility of the system;

[0076] 4. Adapt to business needs and dynamically configure BWP for the business.

[0077] 2. Control Resource Set (CORESET) and Search Space

[0078] CORESET describes the frequency domain characteristics of the physical downlink control channel (PDCCH) blind detection resources, and search space represents the time domain characteristics of the PDCCH blind detection resources, such as period and offset, the number of time slots monitored in each period, and the starting symbol in each time slot.

[0079] A set of PRBs in the CORESET frequency domain where the UE attempts to blindly detect DCI, where:

[0080] PRB can be continuous or discontinuous;

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

[0082] For example, for one symbol, the resource element group (REG) bundle size can be {2, 6};

[0083] 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.

[0084] A UE can be configured with one or more CORESETs. Each cell and each BWP can have a maximum of 3 CORESETs, where:

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

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

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

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

[0089] In each CORESET, the mapping of control channel elements (CCEs) to REGs can be interleaved or non-interleaved, but a CORESET can only have one mapping method.

[0090] The information transmission method, apparatus, terminal, and network-side equipment provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0091] As shown in FIG2 , an embodiment of the present application provides an information transmission method, including:

[0092] Step 201: The terminal sends a first message; and / or

[0093] The terminal obtains the first information.

[0094] 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 related to at least one resource object), and the resource object is associated with or includes at least one frequency domain object.

[0095] It should be noted that a resource object is associated with or includes at least one frequency domain object, which can be understood as a resource object being associated with or including one or more frequency domain objects. It should also be noted here that a resource object can be associated with or include multiple frequency domain objects, but sometimes it may actually only be associated with or include one frequency domain object. For example, the capability or design supports resource objects being associated with or including multiple frequency domain objects, but the network side device is only configured with one. In this case, the resource object is associated with or includes one frequency domain object.

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

[0097] Optionally, the frequency domain object includes one of the following: a frequency part (FP), a frequency band (band, which may also be referred to as a frequency segment), a carrier (carrier), and a subband (subband).

[0098] For example, an application scenario of the present application is that the first information is related to at least one cell associated with or including multiple FPs, or the first information is related to at least one cell associated with or including multiple FPs.

[0099] The first information includes at least one of the following:

[0100] A11. Control how resources are allocated;

[0101] Optionally, the allocation mode of the control resources may be understood as a mapping mode of the control resources, a configuration mode of the control resources, a usage mode of the control resources, etc. Optionally, the allocation mode of the control resources may be agreed upon in a protocol.

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

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

[0104] A112, control channel;

[0105] For example, the control channel is PDCCH.

[0106] A113, candidate control channel;

[0107] For example, the candidate control channel is a PDCCH candidate (PDCCH candidate), and the candidate PDCCH may also be referred to as a PDCCH candidate.

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

[0109] A115, Resource Element Group (REG);

[0110] A116. Search Space (SS).

[0111] A12, the scheduling relationship corresponding to the control resources;

[0112] Optionally, after sending the first information, the terminal may receive the first information actually configured for it by the network-side device, and then communicate with the network-side device based on the first information configured by the network-side device. Optionally, after sending the first information, the terminal may communicate with the network-side device based on the first information. Optionally, after determining the first information, the terminal may communicate with the network-side device based on the first information.

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

[0114] Optionally, in one implementation, 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:

[0115] A12101, dispatch BWP;

[0116] A12102, scheduling frequency domain objects;

[0117] A12103, dispatched BWP;

[0118] A12104, scheduled BWP set;

[0119] A12105, scheduled frequency domain object;

[0120] A12106, a set of scheduled frequency domain objects;

[0121] It should be noted that the above A12101-A12106 are applicable to situations within a resource object as well as situations between resource objects.

[0122] A12107, combination of the dispatching BWP and the dispatched BWP;

[0123] It should be noted that the combination of the scheduling BWP and the scheduled BWP can also be understood as a pairing of the scheduling BWP and the scheduled BWP, or a collection of the scheduling BWP and the scheduled BWP.

[0124] It should be noted that the control resource or the control resource portion (the control resource portion may be understood as part of the control resource) of the scheduling BWP may schedule the scheduled BWP.

[0125] Optionally, if the combination of the scheduling BWP and the scheduled BWP includes at least two scheduling BWPs and / or at least two scheduled BWPs, any combination of the scheduling BWP and the scheduled BWP is supported.

[0126] 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 control resources.

[0127] For example, there are BWP1 and BWP2 in a cell, and 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.

[0128] It should be noted that when the scheduling BWP and the scheduled BWP correspond to different resource objects, this situation applies to situations between resource objects, for example, between cells, where the aforementioned scheduling relationship of control resources exists. 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 BWP is the combination of the scheduling BWP of the scheduling resource object and the scheduled BWP of the scheduled resource object.

[0129] For example, the combination of the scheduling BWP of the scheduling resource object and the scheduled BWP of the scheduled resource object may be a combination of the scheduling BWP of the scheduling cell and the scheduled BWP of the scheduled cell.

[0130] A12108, combining a scheduling frequency domain object and a scheduled frequency domain object;

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

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

[0133] Optionally, if the combination of the scheduling frequency domain object and the scheduled frequency domain object includes at least two scheduling frequency domain objects and / or at least two scheduled frequency domain objects, any combination of the scheduling frequency domain object and the scheduled frequency domain object is supported.

[0134] Optionally, the scheduling frequency domain object and the scheduled frequency domain object are associated frequency domain objects.

[0135] It should be noted that when the scheduling frequency domain object and the resource object corresponding to the scheduled frequency domain object 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 resources.

[0136] For example, there are FP1 and FP2 in a cell, and 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.

[0137] It should be noted that when the resource objects corresponding to the scheduling frequency domain object and the scheduled frequency domain object are different, this situation applies to situations between resource objects, for example, between cells, where the above-mentioned scheduling relationship of control resources exists. 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 frequency domain object is the combination of the scheduling frequency domain object of the scheduling resource object and the scheduled frequency domain object of the scheduled resource object.

[0138] For example, the combination of the scheduling frequency domain object of the scheduling resource object and the scheduled frequency domain object of the scheduled resource object may be a combination of the scheduling frequency domain object of the scheduling cell and the scheduled frequency domain object of the scheduled cell.

[0139] A12109, a combination of a scheduling BWP and a scheduled frequency domain object;

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

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

[0142] Optionally, if the combination of the scheduling BWP and the scheduled frequency domain object includes at least two scheduling BWPs and / or at least two scheduled frequency domain objects, any combination of the scheduling BWP and the scheduled frequency domain object is supported.

[0143] 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.

[0144] 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 one resource object, for example, within one cell, there is the above-mentioned scheduling relationship of the control resources.

[0145] For example, there are FP1 and FP2 belonging to BWP1 in a cell. The network side device instructs 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.

[0146] It should be noted that when the scheduling BWP and the scheduled frequency domain object correspond to different resource objects, this situation applies to situations between resource objects, for example, between cells, where the above-mentioned scheduling relationship of control resources exists. 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.

[0147] For example, the combination of the scheduling BWP of the scheduling resource object and the scheduled frequency domain object of the scheduled resource object may be a combination of the scheduling BWP of the scheduling cell and the scheduled frequency domain object of the scheduled cell.

[0148] A12110, a combination of a scheduling frequency domain object and a scheduled BWP;

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

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

[0151] Optionally, if the combination of the scheduling frequency domain object and the scheduled BWP includes at least two scheduling FPs and / or at least two scheduled BWPs, any combination of scheduling FPs and scheduled BWPs is supported.

[0152] 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 one resource object, for example, within one cell, there is the above-mentioned scheduling relationship of the control resources.

[0153] 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 a BWP that can schedule the scheduled BWP.

[0154] For example, there are FP1 and FP2 belonging to BWP1 in a cell. The network side 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.

[0155] It should be noted that when the resource objects corresponding to the scheduling frequency domain object and the scheduled BWP are different, this situation applies to situations between resource objects, for example, between cells, where the above-mentioned scheduling relationship of control resources exists; optionally, in this case, one or more scheduled resource objects may exist. 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 scheduling resource object and the scheduled BWP of the scheduled resource object.

[0156] For example, the combination of the scheduling frequency domain object of the scheduling resource object and the scheduled BWP of the scheduled resource object may be a combination of the scheduling frequency domain object of the scheduling cell and the scheduled BWP of the scheduled cell.

[0157] 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:

[0158] Dispatch BWP;

[0159] Scheduling frequency domain objects;

[0160] Be dispatched BWP;

[0161] Scheduled BWP set;

[0162] The scheduled frequency domain object;

[0163] A set of scheduled frequency domain objects;

[0164] The combination of the scheduling BWP and the scheduled BWP;

[0165] A combination of a scheduling frequency domain object and a scheduled frequency domain object;

[0166] The combination of scheduling BWP and scheduled frequency domain objects;

[0167] The combination of a scheduled frequency domain object and a scheduled BWP.

[0168] Optionally, the first implementation method is applicable to the situation within a resource object.

[0169] 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:

[0170] Dispatch BWP;

[0171] Scheduling frequency domain objects;

[0172] Be dispatched BWP;

[0173] Scheduled BWP set;

[0174] The scheduled frequency domain object;

[0175] A set of scheduled frequency domain objects;

[0176] A combination of a scheduling BWP of a scheduling resource object and a scheduled BWP of a scheduled resource object;

[0177] A combination of a scheduling frequency domain object of a scheduling resource object and a scheduled frequency domain object of a scheduled resource object;

[0178] A combination of a scheduling BWP of a scheduling resource object and a scheduled frequency domain object of a scheduled resource object;

[0179] A combination of a scheduled frequency domain object of a scheduling resource object and a scheduled BWP of a scheduled resource object.

[0180] Optionally, the second implementation method is applicable to situations between resource objects.

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

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

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

[0184] The target information includes at least one of the following:

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

[0186] A22, resource pool identification;

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

[0188] A23, Transmitting Receiving Point (TRP);

[0189] A24, repetition configuration;

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

[0191] For example, one control resource is associated with one target information, for example, one control resource is associated with multiple target information, for example, multiple control resources are associated with one target information.

[0192] 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 is independently associated with different target information. For example, the number of repetitions associated with REG1 is 4, and the number of repetitions associated with REG2 is 8.

[0193] It should be noted here that the frequency domain objects mentioned in the embodiments of the present application may be configured frequency domain objects, all frequency domain objects, or activated frequency domain objects.

[0194] It should be noted that, optionally, the first information may be configured by the network side device for the terminal, that is, an optional implementation method 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 may also be actively sent by the terminal to the network side device. When the terminal sends the first information, optionally, in one implementation method, the terminal sends the first information including:

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

[0196] It should be noted that this situation 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.

[0197] 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.

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

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

[0200] B101, the number of resource objects;

[0201] B102, the number of resource objects containing multiple frequency domain objects;

[0202] Optionally, when the terminal reports its capability, the number of resource objects including multiple frequency domain objects can be understood as the number of resource objects including multiple frequency domain objects supported by the terminal, which can be a maximum number or a minimum number.

[0203] B103, Band combination;

[0204] It should be noted that the frequency band combination can also be called a bandwidth combination.

[0205] It should be noted that the frequency band combination is related to the number of resource objects, that is, the frequency band combination can implicitly indicate the number of resource objects including multiple frequency domain objects supported by the terminal.

[0206] For example, if it is reported that three Bandcombinations support one cell including multiple FPs, it is considered that the terminal supports a maximum of three cells including multiple FPs.

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

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

[0209] Among them, the type A is that multiple frequency domain objects are treated as multiple BWPs, that is, under type A, multiple frequency domain objects are regarded as independent BWPs, and the terminal can activate multiple BWPs simultaneously. The type B is that multiple frequency domain objects are treated as one BWP, that is, under type B, multiple frequency domain objects correspond to one BWP, and the terminal can only activate one BWP.

[0210] B105, type of frequency domain object;

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

[0212] Continuous frequency domain objects;

[0213] Non-continuous frequency-domain objects.

[0214] B106, the interval between frequency domain objects;

[0215] Optionally, the interval between the frequency domain objects may be a maximum interval, a minimum interval, or an interval supported by the terminal between the frequency domain objects.

[0216] B107, the number of frequency domain objects;

[0217] Optionally, the number of frequency domain objects may be a maximum number or a minimum number of frequency domain objects.

[0218] B108, the number of activated BWPs;

[0219] The number of activated BWPs may be a maximum number or a minimum number of activated BWPs.

[0220] B109, the number of frequency domain objects in a resource object or resource object set;

[0221] Optionally, the number may be a maximum number or a minimum number.

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

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

[0224] B1091, the number of frequency domain objects in a resource object or resource object set under type A;

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

[0226] B1092, the number of frequency domain objects in a resource object or resource object set under type B;

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

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

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

[0230] B1094. 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, and carrier type combination;

[0231] Optionally, the carrier type may include but is not limited to: frequency range 1 (FR1), frequency range 2 (FR2), frequency division duplex (FDD), time division duplex (TDD), licensed band, and unlicensed band.

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

[0233] B110, the number of activated BWPs in the resource object or resource object set;

[0234] Optionally, the number may be a maximum number or a minimum number.

[0235] Optionally, the number of activated BWPs in the resource object or resource object set may be understood as the number of activated BWPs supported in the resource object or resource object set.

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

[0237] B1101, the number of activated BWPs in a resource object or resource object set under type A;

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

[0239] B1102, the number of activated BWPs in a resource object or resource object set under type B;

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

[0241] B1103: The number of activated BWPs in the resource objects or resource object sets scheduled by the same scheduling resource object;

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

[0243] B1104. The number of activated 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, and carrier type combination;

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

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

[0246] B111, the number of frequency domain objects or BWPs with associated relationships;

[0247] Optionally, the number may be a maximum number or a minimum number.

[0248] B112: The number of frequency domain objects or BWPs used for scheduling;

[0249] Optionally, the number may be a maximum number or a minimum number.

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

[0251] B113: The number of frequency domain objects or BWPs to be scheduled;

[0252] Optionally, the number may be a maximum number or a minimum number.

[0253] Optionally, the number of frequency domain objects or BWPs to be scheduled may be understood as the number of frequency domain objects or BWPs that can be scheduled.

[0254] B114: The number of frequency domain objects or BWPs with scheduling relationships;

[0255] Optionally, the number may be a maximum number or a minimum number.

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

[0257] C11, frequency band;

[0258] C12, band combination;

[0259] C13, bandwidth, bandwidth can be carrier bandwidth such as channel bandwidth;

[0260] Optionally, the bandwidth may be a bandwidth supported by the terminal, a minimum supported bandwidth or a maximum supported bandwidth of the terminal, a bandwidth of the system, a minimum bandwidth or a maximum bandwidth of the system, or a preset bandwidth (eg, 20 MHz).

[0261] C14, Bandwidth combination;

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

[0263] C15, frequency range;

[0264] For example, low frequencies support more frequency domain objects, while high frequencies support fewer frequency domain objects.

[0265] C16, Carrier type.

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

[0267] D11. Control resources or control resource parts exist on only one frequency domain object in the resource object;

[0268] This situation can be understood as follows: for a given time unit or units, only one frequency domain object in a resource object has control resources or control resource portions. For example, for a given time unit or units, only one FP in a cell has control resources or control resource portions.

[0269] Optionally, the time unit may be seconds, frames, subframes, time slots, symbols, etc.

[0270] Optionally, in this case, the scheduling relationship corresponding to the control resource or the control resource portion may be that the control resource or the control resource portion is used to schedule any frequency domain object or BWP.

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

[0272] D111, the control resource or the control resource portion is used to schedule the frequency domain object or BWP where the control resource or the control resource portion is located;

[0273] D112. 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.

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

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

[0276] Optionally, the frequency domain object associated with the same second information or the same group of second information as the frequency domain object where the control resource or the control resource part is located can further refer to the frequency domain object that belongs to the same second information or the same group of second information as the frequency domain object where the control resource or the control resource part is located.

[0277] D1122, a frequency domain object associated with the same BWP or the same BWP group as the frequency domain object where the scheduling control resource is located;

[0278] Optionally, the frequency domain object associated with the same BWP or the same BWP group as the frequency domain object where the scheduling control resource 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 scheduling control resource is located.

[0279] It should be noted that this situation is preferably applicable to type B, which is equivalent to there being only one activated BWP in the entire cell, and only a portion of the resources in the BWP are used for CORESET.

[0280] Optionally, the target control resource exists on no more than one frequency domain object in the resource object, 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.

[0281] Optionally, the target control resource may be a control resource used for access.

[0282] For example, as shown in Figure 3, with the resource object being a cell and the frequency domain object being an FP, for type A, where 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 Carrier Allocation (CA). The CORESET of BWP1 can schedule its own BWP or FP as well as other BWPs or FPs in the same cell as its own FP.

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

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

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

[0286] Optionally, in this case, the scheduling relationship corresponding to the control resource or the control resource portion may be that the control resource or the control resource portion is used to schedule any frequency domain object or BWP.

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

[0288] 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;

[0289] 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;

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

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

[0292] Optionally, the frequency domain object associated with the same third information or the same group of third information as the frequency domain object where the second target object is located may further refer to a frequency domain object that belongs to the same third information or the same group of third information as the frequency domain object where the second target object is located.

[0293] D1222: Associating a frequency domain object with the same BWP or the same BWP group as the frequency domain object used for scheduling the second target object;

[0294] Optionally, the 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 may further refer to a frequency domain object belonging to the same BWP or the same BWP group as the frequency domain object used to schedule the second target object.

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

[0296] Different situations of the second target object are described below.

[0297] 1. The second target is to control resources

[0298] It should be noted that this situation can be understood as, for a given one or more time units, a resource object can have at least one frequency domain object with control resources. For example, for a given one or more time units, a cell can have at least one FP with control resources.

[0299] Optionally, the time unit may be seconds, frames, subframes, time slots, symbols, etc.

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

[0301] It should be noted that this scheduling relationship is more suitable for type A, that is, self-scheduling within multiple cells.

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

[0303] 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.

[0304] It should be noted that this scheduling relationship is more suitable for type B, that is, self-scheduling within a cell.

[0305] For example, as shown in Figure 5, with the resource object being a cell and the frequency domain object being an FP, for type A, where one FP corresponds to one BWP, the above scheduling relationship is implemented similarly to self-scheduling under CA. The CORESET of BWP1 can schedule its FP and / or BWP1, and the CORESET of BWP2 can schedule its FP and / or BWP2.

[0306] For example, as shown in Figure 6, with the resource object being a cell and the frequency domain object being an FP, for type B, where multiple FPs correspond to one BWP, the above scheduling relationship is implemented similarly to intra-cell self-scheduling. The CORESET for FP1 can schedule the FP it is in, and the CORESET for FP2 can schedule the FP it is in.

[0307] For example, as shown in Figure 7, with the resource object being a cell and the frequency domain object being an FP, for type A, where one FP corresponds to one BWP, the above scheduling relationship is implemented similarly to self-scheduling under CA. At most, one FP or BWP can be scheduled by a CORESET of multiple FPs. For example, a CORESET of another BWP1 can schedule its own FP or BWP1 and other FPs or BWPs, and a CORESET of BWP2 can schedule its own FP or BWP2.

[0308] For example, as shown in Figure 8, taking the resource object as a cell and the frequency domain object as an FP, for type A, where one frequency part corresponds to one BWP, the above scheduling relationship is implemented similarly to self-scheduling under CA. The CORESET of BWP1 can schedule its FP or BWP1 and other FPs and / or BWPs, and the CORESET of BWP2 can schedule its FP or BWP2 and other FPs and / or BWPs.

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

[0310] 2. The second target object is the control resource part

[0311] It should be noted that this situation can be understood as follows: for a given time unit or units, a resource object can have at least one frequency domain object with a control resource portion. For example, for a given time unit or units, a cell can have at least one FP with a control resource portion.

[0312] Optionally, the time unit may be seconds, frames, subframes, time slots, symbols, etc.

[0313] A 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.

[0314] It should be noted that this scheduling relationship is more suitable for type B.

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

[0316] 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.

[0317] It should be noted that this scheduling relationship is more suitable for type B, that is, self-scheduling within a cell.

[0318] For example, as shown in Figure 10, with the resource object being a cell and the frequency domain object being an FP, for type A, where one frequency part corresponds to one BWP, the above scheduling relationship is implemented similarly to self-scheduling under CA. In Figure 10, CORESET part 1 (P1) can only schedule BWP1, and CORESET part 2 (P2) can only schedule BWP2.

[0319] For example, as shown in Figure 11, with the resource object being a cell and the frequency domain object being a FP, for type B, where multiple frequency parts correspond to one BWP, the above scheduling relationship is implemented similarly to intra-cell self-scheduling. In Figure 11, CORESET part 1 (P1) can only schedule its own FP, and CORESET part 2 (P2) can only schedule its own FP.

[0320] For example, as shown in Figure 12, with the resource object being a cell and the frequency domain object being a FP, for type A, where one frequency part corresponds to one BWP, the above scheduling relationship is implemented similarly to self-scheduling under CA. At most, one FP or BWP can be scheduled by a core set with multiple FPs. For example, in the figure above, core set part 1 (P1) can schedule both BWP1 and BWP2, and core set part 2 (P2) can schedule BWP2.

[0321] For example, as shown in Figure 13, with the resource object being a cell and the frequency domain object being an FP, for type A, where one frequency part corresponds to one BWP, the above scheduling relationship is implemented similarly to self-scheduling under CA. In Figure 13, CORESET part 1 (P1) can schedule BWP1 and BWP2, and CORESET part 2 (P2) can schedule BWP1 and BWP2.

[0322] For example, as shown in Figure 14, taking the resource object as a cell and the frequency domain object as an FP, for type B, i.e., multiple frequency parts correspond to one BWP, the above scheduling relationship is implemented similarly to intra-cell self-scheduling. In Figure 14, CORESET part 1 (P1) can schedule the BWP where the CORESET is located.

[0323] It should be noted that the two diagonal filled boxes in Figures 10 to 14 belong to different parts of the same CORESET or to two CORESET parts. The grid-filled box part is the middle interval or guard interval (guradband) between two BWPs and 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 guradband part (this CORESET part may be available in other BWPs, or technically available, or not actually considered to be available for scheduling). No restrictions are imposed here.

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

[0325] Optionally, in one implementation, the terminal determines a specific implementation of the first information, including:

[0326] The first information is determined according to at least one of the following, where the first information includes an allocation mode of the control resources and / or a scheduling relationship corresponding to the control resources:

[0327] E11, network side equipment indication;

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

[0329] That is to say, in this case, the first information is sent by the network side device to the terminal.

[0330] E12, the scheduling relationship corresponding to the control resources;

[0331] E13. Control how resources are allocated;

[0332] For example, if the allocation mode of the control resource is D12 and the second target object is the control resource, the scheduling relationship is the second scheduling relationship.

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

[0334] For example, for type A, the allocation method of the control resources and / or the scheduling relationship corresponding to the control resources correspond to the situation shown in FIG. 8 .

[0335] For example, for type B, the allocation method of the control resources and / or the scheduling relationship corresponding to the control resources correspond to the situation shown in FIG. 14 .

[0336] E15, the number of frequency domain objects;

[0337] It should be noted that this number can be a maximum number or a minimum number.

[0338] Optionally, the number of frequency domain objects may be, for example, the number of activated frequency domain objects.

[0339] For example, if there is at most one frequency domain object or an activated frequency domain object, the control resource allocation method and / or the scheduling relationship corresponding to type B is used.

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

[0341] E16, the number of activated BWPs;

[0342] It should be noted that this number can be a maximum number or a minimum number.

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

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

[0345] Optionally, the terminal may determine an allocation mode of available control resources and a scheduling relationship corresponding to the control resources based on any one of the above E11-E16.

[0346] Optionally, the terminal may determine the allocation manner of the control resources based on any one of the above E11-E12 and E14-E16.

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

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

[0349] As shown in FIG15 , an embodiment of the present application provides an information transmission method, including:

[0350] Step 1501: The network side device receives the first information; and / or

[0351] The network-side device sends the first information.

[0352] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0353] 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.

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

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

[0356] Optionally, the method further includes:

[0357] 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:

[0358] The number of resource objects;

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

[0360] frequency band combination;

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

[0362] The type of frequency domain object;

[0363] the spacing between frequency domain objects;

[0364] The number of frequency domain objects;

[0365] The number of activated bandwidth parts BWP;

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

[0367] The number of activated BWPs in a resource object or resource object collection;

[0368] The number of frequency domain objects or BWPs with associated relationships;

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

[0370] The number of frequency domain objects or BWPs to be scheduled;

[0371] The number of frequency domain objects or BWPs with scheduling relationships;

[0372] Wherein, the type A is a plurality of frequency domain objects as a plurality of BWPs;

[0373] The type B is a plurality of frequency domain objects as a BWP.

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

[0375] Continuous frequency domain objects;

[0376] Non-continuous frequency-domain objects.

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

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

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

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

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

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

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

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

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

[0386] The number of activated 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, and carrier type combination.

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

[0388] frequency band;

[0389] frequency band combination;

[0390] bandwidth;

[0391] Bandwidth combination;

[0392] Frequency range;

[0393] Carrier type.

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

[0395] There is a control resource or a control resource portion on only one frequency domain object in the resource object;

[0396] There can be a second target object on at least one frequency domain object in the resource objects, and the second target object includes at least one of the following: a control resource and a control resource part.

[0397] Optionally, when the allocation manner of the control resource includes that the control resource or the control resource portion exists 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:

[0398] 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;

[0399] The control resource or the control resource portion is used to schedule the frequency domain object or BWP to which the control resource or the control resource portion is associated.

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

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

[0402] A frequency domain object that is associated with the same BWP or the same BWP group as the frequency domain object used to schedule control resources.

[0403] Optionally, when the allocation manner of the control resource includes that a second target object can exist on at least one frequency domain object in the resource object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0404] 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;

[0405] 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;

[0406] The second target object on the frequency domain object can be used to schedule the frequency domain objects or BWPs having a scheduling relationship.

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

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

[0409] The frequency domain object is associated with the same BWP or the same BWP group as the frequency domain object used for scheduling the second target object.

[0410] Optionally, the method further includes:

[0411] The first information is determined according to at least one of the following, where the first information includes an allocation mode of the control resources and / or a scheduling relationship corresponding to the control resources:

[0412] Control the scheduling relationship corresponding to resources;

[0413] Control how resources are allocated;

[0414] Resource object type, the resource object type including at least one of the following: Type A and Type B, the Type A is a plurality of frequency domain objects as a plurality of BWPs, the Type B is a plurality of frequency domain objects as a BWP;

[0415] The number of frequency domain objects;

[0416] The number of activated BWPs.

[0417] 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:

[0418] Dispatch BWP;

[0419] Scheduling frequency domain objects;

[0420] Be dispatched BWP;

[0421] Scheduled BWP set;

[0422] The scheduled frequency domain object;

[0423] A set of scheduled frequency domain objects;

[0424] The combination of the scheduling BWP and the scheduled BWP;

[0425] A combination of a scheduling frequency domain object and a scheduled frequency domain object;

[0426] The combination of scheduling BWP and scheduled frequency domain objects;

[0427] The combination of a scheduled frequency domain object and a scheduled BWP.

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

[0429] The control resource comprises 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

[0430] The resource object includes a cell.

[0431] 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, sending and receiving point TRP, and repetition configuration.

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

[0433] It should be noted that all 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 achieve the same technical effects, so they will not be repeated here.

[0434] The information transmission method provided in the embodiment of the present application can be executed by an information transmission device. In the embodiment of the present application, the information transmission device provided in the embodiment of the present application is described by taking the information transmission device executing the communication processing method as an example.

[0435] As shown in FIG16 , an information transmission device 1600 according to an embodiment of the present application, applied to a terminal, includes:

[0436] The first transmission module 1601 is configured to send first information; and / or

[0437] Obtaining first information;

[0438] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0439] 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.

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

[0441] First terminal capability information for at least one resource object is sent, where the first terminal capability information includes: first information supported by the terminal.

[0442] Optionally, the device further includes:

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

[0444] The number of resource objects;

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

[0446] frequency band combination;

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

[0448] The type of frequency domain object;

[0449] the spacing between frequency domain objects;

[0450] The number of frequency domain objects;

[0451] The number of activated bandwidth parts BWP;

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

[0453] The number of activated BWPs in a resource object or resource object collection;

[0454] The number of frequency domain objects or BWPs with associated relationships;

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

[0456] The number of frequency domain objects or BWPs to be scheduled;

[0457] The number of frequency domain objects or BWPs with scheduling relationships;

[0458] Wherein, the type A is a plurality of frequency domain objects as a plurality of BWPs;

[0459] The type B is a plurality of frequency domain objects as a BWP.

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

[0461] Continuous frequency domain objects;

[0462] Non-continuous frequency-domain objects.

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

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

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

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

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

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

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

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

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

[0472] The number of activated 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, and carrier type combination.

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

[0474] frequency band;

[0475] frequency band combination;

[0476] bandwidth;

[0477] Bandwidth combination;

[0478] Frequency range;

[0479] Carrier type.

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

[0481] There is a control resource or a control resource portion on only one frequency domain object in the resource object;

[0482] There can be a second target object on at least one frequency domain object in the resource objects, and the second target object includes at least one of the following: a control resource and a control resource part.

[0483] Optionally, when the allocation manner of the control resource includes that the control resource or the control resource portion exists 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:

[0484] 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;

[0485] The control resource or the control resource portion is used to schedule the frequency domain object or BWP to which the control resource or the control resource portion is associated.

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

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

[0488] A frequency domain object that is associated with the same BWP or the same BWP group as the frequency domain object used to schedule control resources.

[0489] Optionally, when the allocation manner of the control resource includes that a second target object can exist on at least one frequency domain object in the resource object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0490] 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;

[0491] 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;

[0492] The second target object on the frequency domain object can be used to schedule the frequency domain objects or BWPs having a scheduling relationship.

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

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

[0495] The frequency domain object is associated with the same BWP or the same BWP group as the frequency domain object used for scheduling the second target object.

[0496] Optionally, the first transmission module is configured to include:

[0497] The first information is determined according to at least one of the following, where the first information includes an allocation mode of the control resources and / or a scheduling relationship corresponding to the control resources:

[0498] Network side device indication;

[0499] Control the scheduling relationship corresponding to resources;

[0500] Control how resources are allocated;

[0501] Resource object type, the resource object type including at least one of the following: Type A and Type B, the Type A is a plurality of frequency domain objects as a plurality of BWPs, the Type B is a plurality of frequency domain objects as a BWP;

[0502] The number of frequency domain objects;

[0503] The number of activated BWPs.

[0504] 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:

[0505] Dispatch BWP;

[0506] Scheduling frequency domain objects;

[0507] Be dispatched BWP;

[0508] Scheduled BWP set;

[0509] The scheduled frequency domain object;

[0510] A set of scheduled frequency domain objects;

[0511] The combination of the scheduling BWP and the scheduled BWP;

[0512] A combination of a scheduling frequency domain object and a scheduled frequency domain object;

[0513] The combination of scheduling BWP and scheduled frequency domain objects;

[0514] The combination of a scheduled frequency domain object and a scheduled BWP.

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

[0516] The control resource comprises 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

[0517] The resource object includes a cell.

[0518] 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, sending and receiving point TRP, and repetition configuration.

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

[0520] It should be noted that the device embodiment is a device corresponding to the above method. All implementation methods in the above method embodiment are applicable to the device embodiment and can achieve the same technical effects, which will not be repeated here.

[0521] The measurement switching device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiments of the present application.

[0522] An embodiment of the present application further provides a terminal, comprising a processor and a communication interface, wherein the communication interface is used to send first information; and / or

[0523] Obtaining first information;

[0524] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0525] 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.

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

[0527] First terminal capability information for at least one resource object is sent, where the first terminal capability information includes: first information supported by the terminal.

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

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

[0530] The number of resource objects;

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

[0532] frequency band combination;

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

[0534] The type of frequency domain object;

[0535] the spacing between frequency domain objects;

[0536] The number of frequency domain objects;

[0537] The number of activated bandwidth parts BWP;

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

[0539] The number of activated BWPs in a resource object or resource object collection;

[0540] The number of frequency domain objects or BWPs with associated relationships;

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

[0542] The number of frequency domain objects or BWPs to be scheduled;

[0543] The number of frequency domain objects or BWPs with scheduling relationships;

[0544] Wherein, the type A is a plurality of frequency domain objects as a plurality of BWPs;

[0545] The type B is a plurality of frequency domain objects as a BWP.

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

[0547] Continuous frequency domain objects;

[0548] Non-continuous frequency-domain objects.

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

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

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

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

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

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

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

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

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

[0558] The number of activated 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, and carrier type combination.

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

[0560] frequency band;

[0561] frequency band combination;

[0562] bandwidth;

[0563] Bandwidth combination;

[0564] Frequency range;

[0565] Carrier type.

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

[0567] There is a control resource or a control resource portion on only one frequency domain object in the resource object;

[0568] There can be a second target object on at least one frequency domain object in the resource objects, and the second target object includes at least one of the following: a control resource and a control resource part.

[0569] Optionally, when the allocation manner of the control resource includes that the control resource or the control resource portion exists 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:

[0570] 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;

[0571] The control resource or the control resource portion is used to schedule the frequency domain object or BWP to which the control resource or the control resource portion is associated.

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

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

[0574] A frequency domain object that is associated with the same BWP or the same BWP group as the frequency domain object used to schedule control resources.

[0575] Optionally, when the allocation manner of the control resource includes that a second target object can exist on at least one frequency domain object in the resource object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0576] 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;

[0577] 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;

[0578] The second target object on the frequency domain object can be used to schedule the frequency domain objects or BWPs having a scheduling relationship.

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

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

[0581] The frequency domain object is associated with the same BWP or the same BWP group as the frequency domain object used for scheduling the second target object.

[0582] Optionally, the processor is configured to:

[0583] The first information is determined according to at least one of the following, where the first information includes an allocation mode of the control resources and / or a scheduling relationship corresponding to the control resources:

[0584] Network side device indication;

[0585] Control the scheduling relationship corresponding to resources;

[0586] Control how resources are allocated;

[0587] Resource object type, the resource object type including at least one of the following: Type A and Type B, the Type A is a plurality of frequency domain objects as a plurality of BWPs, the Type B is a plurality of frequency domain objects as a BWP;

[0588] The number of frequency domain objects;

[0589] The number of activated BWPs.

[0590] 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:

[0591] Dispatch BWP;

[0592] Scheduling frequency domain objects;

[0593] Be dispatched BWP;

[0594] Scheduled BWP set;

[0595] The scheduled frequency domain object;

[0596] A set of scheduled frequency domain objects;

[0597] The combination of the scheduling BWP and the scheduled BWP;

[0598] A combination of a scheduling frequency domain object and a scheduled frequency domain object;

[0599] The combination of scheduling BWP and scheduled frequency domain objects;

[0600] The combination of a scheduled frequency domain object and a scheduled BWP.

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

[0602] The control resource comprises 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

[0603] The resource object includes a cell.

[0604] 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, sending and receiving point TRP, and repetition configuration.

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

[0606] Preferably, an embodiment of the present application further provides a terminal comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When executed by the processor, the program or instruction implements the various processes of the above-described communication processing method embodiment and can achieve the same technical effect. To avoid repetition, they are not described here. Specifically, Figure 17 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0607] The terminal 1700 includes but is not limited to: 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 at least some of the components of the processor 1710.

[0608] Those skilled in the art will appreciate that the terminal 1700 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1710 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG17 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0609] It should be understood that in an embodiment of the present application, the input unit 1704 may include a graphics processing unit (GPU) 17041 and a microphone 17042, and 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 a touch panel 17071 and at least one of 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. 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 repeated here.

[0610] In the embodiment of the present application, after receiving downlink data from the access network device, the radio frequency unit 1701 can transmit the data to the processor 1710 for processing. In addition, the radio frequency unit 1701 can send uplink data to the 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.

[0611] The memory 1709 can be used to store software programs or instructions and 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, wherein the first storage area may store an operating system, applications 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 volatile and 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0612] Processor 1710 may include one or more processing units. Optionally, processor 1710 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1710.

[0613] The radio frequency unit 1701 is used for:

[0614] Sending a first message; and / or

[0615] Obtaining first information;

[0616] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0617] 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.

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

[0619] First terminal capability information for at least one resource object is sent, where the first terminal capability information includes: first information supported by the terminal.

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

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

[0622] The number of resource objects;

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

[0624] frequency band combination;

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

[0626] The type of frequency domain object;

[0627] the spacing between frequency domain objects;

[0628] The number of frequency domain objects;

[0629] The number of activated bandwidth parts BWP;

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

[0631] The number of activated BWPs in a resource object or resource object collection;

[0632] The number of frequency domain objects or BWPs with associated relationships;

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

[0634] The number of frequency domain objects or BWPs to be scheduled;

[0635] The number of frequency domain objects or BWPs with scheduling relationships;

[0636] Wherein, the type A is a plurality of frequency domain objects as a plurality of BWPs;

[0637] The type B is a plurality of frequency domain objects as a BWP.

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

[0639] Continuous frequency domain objects;

[0640] Non-continuous frequency-domain objects.

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

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

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

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

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

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

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

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

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

[0650] The number of activated 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, and carrier type combination.

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

[0652] frequency band;

[0653] frequency band combination;

[0654] bandwidth;

[0655] Bandwidth combination;

[0656] Frequency range;

[0657] Carrier type.

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

[0659] There is a control resource or a control resource portion on only one frequency domain object in the resource object;

[0660] There can be a second target object on at least one frequency domain object in the resource objects, and the second target object includes at least one of the following: a control resource and a control resource part.

[0661] Optionally, when the allocation manner of the control resource includes that the control resource or the control resource portion exists 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:

[0662] 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;

[0663] The control resource or the control resource portion is used to schedule the frequency domain object or BWP to which the control resource or the control resource portion is associated.

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

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

[0666] A frequency domain object that is associated with the same BWP or the same BWP group as the frequency domain object used to schedule control resources.

[0667] Optionally, when the allocation manner of the control resource includes that a second target object can exist on at least one frequency domain object in the resource object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0668] 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;

[0669] 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;

[0670] The second target object on the frequency domain object can be used to schedule the frequency domain object or BWP that has a real scheduling relationship.

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

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

[0673] The frequency domain object is associated with the same BWP or the same BWP group as the frequency domain object used for scheduling the second target object.

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

[0675] The first information is determined according to at least one of the following, where the first information includes an allocation mode of the control resources and / or a scheduling relationship corresponding to the control resources:

[0676] Network side device indication;

[0677] Control the scheduling relationship corresponding to resources;

[0678] Control how resources are allocated;

[0679] Resource object type, the resource object type including at least one of the following: Type A and Type B, the Type A is a plurality of frequency domain objects as a plurality of BWPs, the Type B is a plurality of frequency domain objects as a BWP;

[0680] The number of frequency domain objects;

[0681] The number of activated BWPs.

[0682] 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:

[0683] Dispatch BWP;

[0684] Scheduling frequency domain objects;

[0685] Be dispatched BWP;

[0686] Scheduled BWP set;

[0687] The scheduled frequency domain object;

[0688] A set of scheduled frequency domain objects;

[0689] The combination of the scheduling BWP and the scheduled BWP;

[0690] A combination of a scheduling frequency domain object and a scheduled frequency domain object;

[0691] The combination of scheduling BWP and scheduled frequency domain objects;

[0692] The combination of a scheduled frequency domain object and a scheduled BWP.

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

[0694] The control resource comprises 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

[0695] The resource object includes a cell.

[0696] 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, sending and receiving point TRP, and repetition configuration.

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

[0698] An embodiment of the present application also provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned information transmission method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0699] The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0700] As shown in FIG18 , an information transmission apparatus 1800 according to an embodiment of the present application, applied to a network-side device, includes:

[0701] The second transmission module 1801 is configured to receive first information; and / or

[0702] Sending the first message;

[0703] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0704] 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.

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

[0706] First terminal capability information for at least one resource object sent by a terminal is received, where the first terminal capability information includes: first information supported by the terminal.

[0707] Optionally, the device further includes:

[0708] 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:

[0709] The number of resource objects;

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

[0711] frequency band combination;

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

[0713] The type of frequency domain object;

[0714] the spacing between frequency domain objects;

[0715] The number of frequency domain objects;

[0716] The number of activated bandwidth parts BWP;

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

[0718] The number of activated BWPs in a resource object or resource object collection;

[0719] The number of frequency domain objects or BWPs with associated relationships;

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

[0721] The number of frequency domain objects or BWPs to be scheduled;

[0722] The number of frequency domain objects or BWPs with scheduling relationships;

[0723] Wherein, the type A is a plurality of frequency domain objects as a plurality of BWPs;

[0724] The type B is a plurality of frequency domain objects as a BWP.

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

[0726] Continuous frequency domain objects;

[0727] Non-continuous frequency-domain objects.

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

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

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

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

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

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

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

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

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

[0737] The number of activated 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, and carrier type combination.

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

[0739] frequency band;

[0740] frequency band combination;

[0741] bandwidth;

[0742] Bandwidth combination;

[0743] Frequency range;

[0744] Carrier type.

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

[0746] There is a control resource or a control resource portion on only one frequency domain object in the resource object;

[0747] There can be a second target object on at least one frequency domain object in the resource objects, and the second target object includes at least one of the following: a control resource and a control resource part.

[0748] Optionally, when the allocation manner of the control resource includes that the control resource or the control resource portion exists 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:

[0749] 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;

[0750] The control resource or the control resource portion is used to schedule the frequency domain object or BWP to which the control resource or the control resource portion is associated.

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

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

[0753] A frequency domain object that is associated with the same BWP or the same BWP group as the frequency domain object used to schedule control resources.

[0754] Optionally, when the allocation manner of the control resource includes that a second target object can exist on at least one frequency domain object in the resource object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0755] 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;

[0756] 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;

[0757] The second target object on the frequency domain object can be used to schedule the frequency domain objects or BWPs having a scheduling relationship.

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

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

[0760] The frequency domain object is associated with the same BWP or the same BWP group as the frequency domain object used for scheduling the second target object.

[0761] Optionally, the device further includes:

[0762] a determining module, configured to determine first information according to at least one of the following, the first information including an allocation mode of control resources and / or a scheduling relationship corresponding to the control resources:

[0763] Control the scheduling relationship corresponding to resources;

[0764] Control how resources are allocated;

[0765] Resource object type, the resource object type including at least one of the following: Type A and Type B, the Type A is a plurality of frequency domain objects as a plurality of BWPs, the Type B is a plurality of frequency domain objects as a BWP;

[0766] The number of frequency domain objects;

[0767] The number of activated BWPs.

[0768] 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:

[0769] Dispatch BWP;

[0770] Scheduling frequency domain objects;

[0771] Be dispatched BWP;

[0772] Scheduled BWP set;

[0773] The scheduled frequency domain object;

[0774] A set of scheduled frequency domain objects;

[0775] The combination of the scheduling BWP and the scheduled BWP;

[0776] A combination of a scheduling frequency domain object and a scheduled frequency domain object;

[0777] The combination of scheduling BWP and scheduled frequency domain objects;

[0778] The combination of a scheduled frequency domain object and a scheduled BWP.

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

[0780] The control resource comprises 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

[0781] The resource object includes a cell.

[0782] 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, sending and receiving point TRP, and repetition configuration.

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

[0784] The embodiment of the present application further provides a network-side device, comprising a processor and a communication interface, wherein the communication interface is configured to receive first information; and / or

[0785] Sending the first message;

[0786] The first information includes at least one of the following: an allocation method of control resources and a scheduling relationship corresponding to the control resources;

[0787] 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.

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

[0789] Terminal capability information for at least one resource object sent by a terminal is received, where the terminal capability information includes: first information supported by the terminal.

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

[0791] The receiving terminal sends second terminal capability information, where the second terminal capability information includes at least one of the following:

[0792] The number of resource objects;

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

[0794] frequency band combination;

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

[0796] The type of frequency domain object;

[0797] the spacing between frequency domain objects;

[0798] The number of frequency domain objects;

[0799] The number of activated bandwidth parts BWP;

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

[0801] The number of activated BWPs in a resource object or resource object collection;

[0802] The number of frequency domain objects or BWPs with associated relationships;

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

[0804] The number of frequency domain objects or BWPs to be scheduled;

[0805] The number of frequency domain objects or BWPs with scheduling relationships;

[0806] Wherein, the type A is a plurality of frequency domain objects as a plurality of BWPs;

[0807] The type B is a plurality of frequency domain objects as a BWP.

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

[0809] Continuous frequency domain objects;

[0810] Non-continuous frequency-domain objects.

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

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

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

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

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

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

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

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

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

[0820] The number of activated 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, and carrier type combination.

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

[0822] frequency band;

[0823] frequency band combination;

[0824] bandwidth;

[0825] Bandwidth combination;

[0826] Frequency range;

[0827] Carrier type.

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

[0829] There is a control resource or a control resource portion on only one frequency domain object in the resource object;

[0830] There can be a second target object on at least one frequency domain object in the resource objects, and the second target object includes at least one of the following: a control resource and a control resource part.

[0831] Optionally, when the allocation manner of the control resource includes that the control resource or the control resource portion exists 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:

[0832] 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;

[0833] The control resource or the control resource portion is used to schedule the frequency domain object or BWP to which the control resource or the control resource portion is associated.

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

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

[0836] A frequency domain object that is associated with the same BWP or the same BWP group as the frequency domain object used to schedule control resources.

[0837] Optionally, when the allocation manner of the control resource includes that a second target object can exist on at least one frequency domain object in the resource object, the scheduling relationship corresponding to the control resource includes at least one of the following:

[0838] 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;

[0839] 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;

[0840] The second target object on the frequency domain object can be used to schedule the frequency domain objects or BWPs having a scheduling relationship.

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

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

[0843] The frequency domain object is associated with the same BWP or the same BWP group as the frequency domain object used for scheduling the second target object.

[0844] Optionally, the processor is configured to:

[0845] The first information is determined according to at least one of the following, where the first information includes an allocation mode of the control resources and / or a scheduling relationship corresponding to the control resources:

[0846] Control the scheduling relationship corresponding to resources;

[0847] Control how resources are allocated;

[0848] Resource object type, the resource object type including at least one of the following: Type A and Type B, the Type A is a plurality of frequency domain objects as a plurality of BWPs, the Type B is a plurality of frequency domain objects as a BWP;

[0849] The number of frequency domain objects;

[0850] The number of activated BWPs.

[0851] 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:

[0852] Dispatch BWP;

[0853] Scheduling frequency domain objects;

[0854] Be dispatched BWP;

[0855] Scheduled BWP set;

[0856] The scheduled frequency domain object;

[0857] A set of scheduled frequency domain objects;

[0858] The combination of the scheduling BWP and the scheduled BWP;

[0859] A combination of a scheduling frequency domain object and a scheduled frequency domain object;

[0860] The combination of scheduling BWP and scheduled frequency domain objects;

[0861] The combination of a scheduled frequency domain object and a scheduled BWP.

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

[0863] The control resource comprises 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

[0864] The resource object includes a cell.

[0865] 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, sending and receiving point TRP, and repetition configuration.

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

[0867] Specifically, an embodiment of the present application also provides a network-side device. As shown in Figure 19, 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. Antenna 1901 is connected to radio frequency device 1902. In the uplink direction, radio frequency device 1902 receives information via antenna 1901 and sends the received information to baseband device 1903 for processing. In the downlink direction, baseband device 1903 processes the information to be transmitted and sends it to radio frequency device 1902. Radio frequency device 1902 processes the received information and sends it through antenna 1901.

[0868] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 1903 , which includes a baseband processor.

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

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

[0871] Specifically, the network side device 1900 of the embodiment of the present application also includes: instructions or programs stored in the memory 1905 and can be run on the processor 1904. The processor 1904 calls the instructions or programs in the memory 1905 to execute the methods executed by each module shown in Figure 18 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0872] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned information transmission method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0873] The processor is the processor in the network-side device described in the above embodiment. The readable storage medium can be non-volatile or non-transient. The readable storage medium can include a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0874] Optionally, as shown in Figure 20, an embodiment of the present application further provides a communication device 2000, including a processor 2001 and a memory 2002, wherein the memory 2002 stores a program or instruction that can be run on the processor 2001. For example, when the communication device 2000 is a terminal, the program or instruction is executed by the processor 2001 to implement the various steps of the above-mentioned information transmission method embodiment, and can achieve the same technical effect. When the communication device 2000 is a network-side device, the program or instruction is executed by the processor 2001 to implement the various steps of the above-mentioned information transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0875] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned information transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0876] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0877] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned information transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0878] An embodiment of the present application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the above-mentioned information transmission method, and the network-side device can be used to execute the steps of the above-mentioned information transmission processing method.

[0879] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising 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 the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

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

[0881] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. An information transmission method, wherein, 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 includes 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, 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 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, the type A is that multiple frequency-domain objects are multiple BWP; The type B is that multiple frequency-domain objects are one BWP.

4. The method according to claim 3, 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, 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, the allocation method of the control resources includes at least one of the following: There is only one control resource or a part of the control resource on a 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: control resource, part of the control resource.

7. The method according to claim 6, 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 there is a control resource or a part of the control resource, 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, 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, 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 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.

10. The method according to claim 9, 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, the terminal determines the first information including: Determining the first information according to at least one of the following, and the first information includes the allocation method of the control resource and / or the scheduling relationship corresponding to the control resource: Indicated by the network-side device; The scheduling relationship corresponding to the control resource; The allocation method 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 active BWPs.

12. The method according to any one of claims 1-11, 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, wherein the frequency-domain object includes one of the following: frequency portion, 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, wherein 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.

15. An information transmission method, wherein, Comprising: The network-side device receives first information; and / or The network-side device sends first information; wherein the first information includes at least one of the following: allocation mode of the control resource, 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.

16. The method according to claim 15, wherein the network-side device receives the first information, including: The network-side device receives first terminal capability information sent by the 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, further comprising: The network-side device receives second terminal capability information sent by the terminal, and the second terminal capability information includes at least one of the following: Number of resource objects; 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; Type of frequency-domain object; Interval between frequency-domain objects; Number of frequency-domain objects; Number of activated bandwidth parts BWPs; Number of frequency-domain objects in a resource object or a set of resource objects; Number of activated BWPs in a resource object or a set of resource objects; Number of frequency-domain objects or BWPs having an association relationship; Number of frequency-domain objects or BWPs used for scheduling; Number of frequency-domain objects or BWPs as scheduled; Number of frequency-domain objects or BWPs having a scheduling relationship; wherein the type A is multiple frequency-domain objects as multiple BWPs; the type B is multiple frequency-domain objects as one BWP.

18. The method according to claim 17, wherein the number of frequency-domain objects in the resource object or the set of resource objects includes at least one of the following: Number of frequency-domain objects in a resource object or a set of resource objects of type A; Number of frequency-domain objects in a resource object or a set of resource objects of type B; 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, 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.

19. The method according to claim 17, where the number of activated bandwidth parts (BWPs) in a resource object or a set of resource objects includes at least one of the following: The number of activated BWPs in a resource object or a set of resource objects of type A; The number of activated BWPs in a resource object or a set of resource objects of type B; The number of activated BWPs in a resource object or a set of resource objects scheduled by the same scheduling resource object; 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.

20. The method according to any one of claims 15 - 19, where the allocation method of the control resource includes at least one of the following: There is a control resource or a control resource part 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, where the second target object includes at least one of the following: control resource, control resource part.

21. The method according to claim 20, in the case where the allocation method of the control resource includes that there is a control resource or a control resource part on only one frequency-domain object in the resource object, the scheduling relationship corresponding to the control resource or the control resource part includes at least one of the following: 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; 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.

22. The method according to claim 21, where 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 part 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, 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 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, where the associated frequency-domain object includes at least one of the following: A frequency-domain object associated with the same third piece of information or the same set of third pieces of information as the frequency-domain object where the second target object is located, where the third piece of 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, further comprising: Determining 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: The scheduling relationship corresponding to the control resources; The allocation method of the control resources; 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; The number of frequency-domain objects; The number of activated BWPs.

26. An information transmission device, applied to a terminal, wherein, Including: A first transmission module, configured to send the first information; and / or Determine the first information; where 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.

27. For the device according to claim 26, the first transmission module is configured to: 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.

28. A terminal, wherein, Including a processor and a memory, where 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 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, wherein, Including: A second transmission module, configured to receive the first information; and / or Send the first information; where 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. For the device according to claim 29, the second transmission module is configured to: Receive terminal capability information for at least one resource object sent by a receiving terminal, where the terminal capability information includes: The first information supported by the terminal.

31. A network-side device, wherein, Including a processor and a memory, where 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 information transmission method according to any one of claims 15 to 25 are implemented.

32. A readable storage medium, wherein, The program or instruction is stored on the readable storage medium, and when the program or instruction is executed by the processor, the steps of the information transmission method according to any one of claims 1-25 are implemented.

Images