WO2025119359A1 - 控制信道的传输方法、装置、设备及存储介质 - Google Patents

控制信道的传输方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2025119359A1
WO2025119359A1 PCT/CN2024/137572 CN2024137572W WO2025119359A1 WO 2025119359 A1 WO2025119359 A1 WO 2025119359A1 CN 2024137572 W CN2024137572 W CN 2024137572W WO 2025119359 A1 WO2025119359 A1 WO 2025119359A1
Authority
WO
WIPO (PCT)
Prior art keywords
frequency domain
coreset
domain units
terminal
frequency
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/137572
Other languages
English (en)
French (fr)
Inventor
鲁智
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2025119359A1 publication Critical patent/WO2025119359A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present application belongs to the field of wireless communication technology, and specifically relates to a control channel transmission method, device, equipment and storage medium.
  • the spectrum resources of the new radio (NR) system include the Sub-6GHz band, of which the band below 3GHZ is called Sub-3GHz and the rest is called C-band.
  • the Sub-3GHz band is allocated to mobile operators in a fragmented manner.
  • the spectrum resources owned by mobile operators are relatively scattered, that is, the bandwidth of the spectrum resources is narrow and the spectrum is not continuous. How to efficiently and flexibly use these scattered, narrow-bandwidth spectrum resources to provide users with large-capacity and large-bandwidth services is one of the problems that the NR system needs to solve.
  • the embodiments of the present application provide a control channel transmission method, apparatus, device and storage medium, which can provide users with large-capacity and large-bandwidth services by utilizing scattered, narrow-bandwidth spectrum resources.
  • a control channel transmission method which is executed by a terminal, and the method includes: the terminal obtains configuration information of M frequency domain units, M is less than or equal to the number P of frequency domain units configured in a service cell of the terminal; the terminal obtains frequency domain resources of a control resource set CORESET on the M frequency domain units; the terminal determines at least one CORESET for receiving a physical downlink control channel PDCCH based on the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • a control channel transmission method which is executed by a network side device, and the method includes: the network side device sends configuration information of M frequency domain units to a terminal, M is less than or equal to the number P of frequency domain units configured for a service cell of the terminal; the network side device sends the frequency domain resources of the CORESET on the M frequency domain units to the terminal; the network side device sends a downlink control channel PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • a control channel transmission device including: an acquisition module, used to acquire configuration information of M frequency domain units, M is less than or equal to the number P of frequency domain units configured in the service cell of the terminal; the acquisition module is also used to acquire the frequency domain resources of the CORESET on the M frequency domain units; a determination module is used to determine at least one CORESET for receiving the PDCCH based on the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • a control channel transmission device comprising: a sending module, used to send configuration information of M frequency domain units to a terminal, M being less than or equal to the number P of frequency domain units configured for a service cell of the terminal; the sending module, used to send the frequency domain resources of a CORESET on the M frequency domain units to the terminal; and a processing module, used to send a PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • a terminal 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.
  • a terminal comprising a processor and a communication interface, wherein the processor is used to obtain configuration information of M frequency domain units, M is less than or equal to the number P of frequency domain units configured by the service cell of the terminal, and to obtain the frequency domain resources of the CORESET on the M frequency domain units; according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET, at least one CORESET for receiving a physical downlink control channel PDCCH is determined, and the communication interface is used to receive the PDCCH on the at least one CORESET.
  • a network side device which includes 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 second aspect are implemented.
  • a network side device including a processor and a communication interface, wherein the processor is used to determine at least one CORESET for sending PDCCH based on the configuration information of M frequency domain units and the frequency domain resources of CORESET, M is less than or equal to the number P of frequency domain units configured by the service cell of the terminal, and the communication interface is used to send the configuration information of M frequency domain units to the terminal, send the frequency domain resources of the CORESET on the M frequency domain units to the terminal, and send PDCCH to the terminal through the at least one CORESET.
  • a readable storage medium on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.
  • a wireless communication system including: 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 second aspect.
  • a chip comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.
  • a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the program/program product is executed by at least one processor to implement the steps of the control channel transmission method as described in the first aspect or the second aspect.
  • the network side device can reduce the common signaling overhead and achieve load balancing of each uplink UL/DL carrier by configuring CORESET on some frequency domain units of the service cell of the terminal.
  • the terminal obtains a CORESET for receiving PDCCH by combining all or part of the CORESET cross-frequency domain units on M frequency domain units, so that the CORESET for receiving PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.
  • FIG1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG2 is a flow chart of a control channel transmission method provided in Embodiment 1 of the present application.
  • FIG3 is a schematic diagram showing the position of the starting RB of the BWP relative to the frequency domain starting point of the carrier where the BWP is located;
  • FIG4 is a schematic diagram of frequency reference points of each frequency domain unit of a terminal
  • FIG5 is a schematic diagram of configuring CORESET for all frequency domain units of a serving cell of a terminal
  • FIG6 is a schematic diagram of configuring CORESET of some frequency domain units of a serving cell of a terminal
  • FIG7 is a flow chart of a control channel transmission method provided in Embodiment 2 of the present application.
  • FIG8 is a schematic diagram of a cascade connection of a CORESET of multiple frequency domain units
  • FIG9 is another schematic diagram of cascading a plurality of frequency domain units of CORESET
  • FIG10 is another schematic diagram of a cascade connection of a CORESET of multiple frequency domain units
  • FIG11 is a schematic diagram of the cascade connection of CORESET of frequency domain units of multiple terminals
  • FIG12 is a flowchart of a control channel transmission method provided in Embodiment 3 of the present application.
  • FIG13 is a schematic diagram of a CORESET of a frequency domain unit of a terminal
  • FIG14 is a flow chart of a control channel transmission method provided in Embodiment 4 of the present application.
  • FIG15 is a signaling flow chart of a control channel transmission method provided in Embodiment 5 of the present application.
  • FIG16 is a schematic diagram of the structure of a control channel transmission device provided in Embodiment 6 of the present application.
  • FIG17 is a schematic diagram of the structure of a control channel transmission device provided in Embodiment 7 of the present application.
  • FIG18 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG19 is a schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.
  • FIG20 is a schematic diagram of the hardware structure of a network-side device for implementing an embodiment of the present application.
  • first, second, etc. of the present 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 one type, and the number of objects is not limited, for example, the first object can be one or more.
  • “or” in the present application represents at least one of the connected objects.
  • “A or B” covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B.
  • the character "/" generally indicates that the objects associated with each other are in an "or” relationship.
  • indication in this application can be 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, operations to be performed, or request results in the sent indication;
  • an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies.
  • the following description describes the NR system for example purposes, and the NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th Generation (6G) communication system.
  • 6G 6th Generation
  • FIG1 shows a block diagram of a wireless communication system applicable to the embodiment of the present application.
  • the wireless communication system includes a terminal 11 and a network side device 12 .
  • the terminal 11 can 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 (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), a flight vehicle (flight vehicle), a vehicle user equipment (VUE), a shipborne equipment, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC
  • 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.
  • 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.
  • WLAN wireless Local Area Network
  • AP Access Point
  • WiFi wireless Fidelity
  • the base station may be called Node B (Node B, NB), Evolved Node B (Evolved Node B, eNB), the next generation Node B (the next generation Node B, gNB), New Radio Node B (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 (home evolved Node B, HNB), home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field.
  • the base station is not limited to specific technical vocabulary. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.
  • PDCCH Physical Downlink Control Channel
  • PDCCH is a downlink control channel, which carries the downlink control information (DCI) of the physical uplink shared channel (PUSCH) and the physical downlink shared channel (PDSCH).
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • BWP is a collection of multiple consecutive resource blocks (RB) in a carrier.
  • the network side can dynamically configure the system bandwidth of the terminal according to different service types, which can save network resources while reducing terminal power consumption.
  • BWP's technical advantages are mainly in four aspects:
  • the terminal 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.
  • the terminal can switch to low bandwidth operation, which can significantly reduce power consumption.
  • 3.5G technology is forward compatible.
  • the new technologies can be directly run on the new BWP, ensuring the forward compatibility of the system.
  • the network side can dynamically adjust the bandwidth of the terminal according to the size of the business volume. For example, at the first moment, the business volume of the terminal is large, and the network side configures a large bandwidth (BWP1) for the terminal; at the second moment, the business volume of the terminal is small, and the network side configures a small bandwidth (BWP2) for the terminal to meet basic communication needs; at the third moment, the network side finds that there is a large-scale frequency selective fading in the bandwidth where BWP1 is located, or the resources in the frequency range where BWP1 is located are relatively scarce, so a new bandwidth (BWP3) is configured for the terminal.
  • BWP1 bandwidth
  • BWP2 small bandwidth
  • BWP3 new bandwidth
  • the frequency points and widths of multiple BWPs configured by the network side for the terminal are different.
  • other configuration parameters of multiple BWPs can also be different.
  • SCS subcarrier spacing
  • CP cyclic prefix
  • SSB synchronization broadcast block
  • the synchronization signal includes the primary synchronization signal (PSS) and the secondary synchronization signal (SSS).
  • the broadcast signal includes the physical broadcast channel (PBCH) data and the PBCH demodulation reference signal (DMRS) signal.
  • PBCH physical broadcast channel
  • DMRS PBCH demodulation reference signal
  • CORESET is a set of physical resources used to carry PDCCH or DCI.
  • CORESET-related parameters include:
  • a resource element consists of a subcarrier in the frequency domain and an orthogonal frequency-division multiplexing (OFDM) symbol in the time domain.
  • OFDM orthogonal frequency-division multiplexing
  • RB Resource Block
  • a resource element group (RE group, REG) consists of one RB (12 REs) in the frequency domain and one OFDM symbol in the time domain.
  • Resource element group sets are composed of multiple REGs, and their number is determined by the Radio Resource Control (RRC) parameter reg-bundle-size.
  • RRC Radio Resource Control
  • the bundle size can be ⁇ 2,3,6 ⁇ , which is related to the number of CORESET symbols.
  • Control-channel element consists of 6 REGs.
  • Aggregation level indicates how many CCEs are allocated to PDCCH.
  • Currently supported aggregation levels are ⁇ 1, 2, 4, 8, 16 ⁇ .
  • CORESET describes the frequency domain characteristics of PDCCH blind detection resources.
  • PDCCH blind detection resources also include time domain characteristics.
  • the frequency domain characteristics of PDCCH are described by the search space (SS).
  • the search space is used to describe the starting symbol, detection period, etc. of PDCCH.
  • a CORESET can be composed of multiple PRBs in the frequency domain and 1/2/3 OFDM symbols in the time domain.
  • the number and position of PRBs occupied by the CORESET can be flexibly deployed by the network side.
  • the CORESET has the following features:
  • the PRBs occupied by CORESET can be continuous or discontinuous;
  • a CORESET can occupy one or more consecutive symbols in the time domain, and the number of symbols can be: ⁇ 1, 2, 3 ⁇ ;
  • the REG bundle size can be ⁇ 2, 6 ⁇ ;
  • the REG bundle size can be equal to the number of time domain symbols or 6;
  • a terminal can be configured with one or more CORESETs, with a maximum of 3 CORESETs per BWP per cell;
  • a CORESET can be associated with two search spaces: Common Search Space and UE-specific Search Space.
  • Each BWP can be configured with up to 3 CORESETs
  • Each BWP can be configured with up to 10 search spaces
  • Multiple CORESETs configured in a terminal can overlap in the frequency domain or time domain;
  • mapping mode of CCE to REG can be interleaved or non-interleaved, but a CORESET can only have one mapping mode.
  • NR systems Compared with LTE/LTE-A systems, NR systems pursue greater bandwidth and throughput. NR systems need to use fragmented Sub-3GHz spectrum to provide users with large bandwidth and capacity to meet the growing business-oriented (To Business, ToB) and user-oriented (ToCustomer, ToC) services in the future. Cells that use these fragmented continuous or discontinuous spectrums are called flexible serving cells. The purpose of flexible serving cells is to be able to use these fragmented spectrums efficiently and flexibly.
  • control channel transmission method provided by the embodiments of the present application through some embodiments and their application scenarios in conjunction with the accompanying drawings.
  • the following embodiments may be combined with each other, and the same or similar concepts and processes may not be repeated in some embodiments.
  • Fig. 2 is a flow chart of a control channel transmission method provided in Embodiment 1 of the present application, and the method is applied in a terminal. As shown in Fig. 2, the method provided in this embodiment includes the following steps.
  • a terminal obtains configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal.
  • the frequency domain unit may be a BWP, a carrier or a frequency band.
  • a frequency band may include multiple carriers, and a carrier may include multiple BWPs. It is understood that the configuration information of different types of frequency domain units may be different.
  • the configuration information of the M frequency domain units includes at least one of the following:
  • the index (or identification) of each frequency domain unit in the M frequency domain units is the index (or identification) of each frequency domain unit in the M frequency domain units.
  • Part or all of the configuration information in the M frequency domain units may be configured by the network side device and sent to the terminal.
  • the terminal may determine it based on other information.
  • the configuration information of the above frequency domain units is required so that the terminal can receive data, such as PDSCH or PUSCH. Since this application emphasizes the processing of CORESET, the P frequency domain units are not described in detail.
  • the bandwidth of the terminal's frequency domain unit is not necessarily equal to the channel bandwidth.
  • the channel bandwidth is 100 MHz
  • the bandwidth of the BWP allocated to the terminal by the network side is 20 MHz. If the terminal does not use the full bandwidth of the channel bandwidth, then the terminal needs to determine the starting frequency of the frequency domain unit allocated to it based on the frequency reference point.
  • the frequency reference point may be Point A, where Point A is a common reference point for the entire resource grid.
  • the frequency reference points of the M frequency domain units include at least one of the following:
  • CD-SSB Cell-Defining Synchronization Signal Block
  • the CD-SSB when the frequency domain unit is a BWP, even if the CD-SSB is not in a BWP (initialBWP), the CD-SSB may be associated with the BWP.
  • the frequency domain unit is a carrier/band
  • a similar definition may be adopted.
  • a carrier/band without an associated CD-SSB may be defined, which means that there is no CD-SSB on the carrier/band.
  • the frequency reference point of the frequency domain unit can be determined based on some acquired parameters of the frequency domain unit.
  • the network side device can configure the frequency reference point for the frequency domain unit, wherein the frequency reference points of different frequency domain units may be different.
  • the network side device indicates or configures the frequency reference point (for example, pointA) for at least one frequency domain unit in the following way.
  • its frequency reference point may not need to be configured by the network side device, and may be determined based on the lowest frequency domain position of the SSB frequency, the subcarrier offset k_ssb parameter, and offsetToPoint A. For example, it may be calculated using the following formula:
  • the frequency reference point of point A the lowest frequency domain position of the SSB associated BWP - k_ssb*u - offsetToPoint A*12*u.
  • u is the subcarrier spacing, which is 15kHz for FR1 and 60kHz for FR2.
  • the subcarrier offset k_ssb parameter and offsetToPoint A can be notified by the network side device in the Master Information Block (MIB) message.
  • MIB Master Information Block
  • the network side equipment can configure a frequency domain reference point for each carrier.
  • the network side equipment can configure the frequency domain reference point for each carrier through the System Information Block (SIB) message.
  • SIB System Information Block
  • the network side device configures the position of the starting RB and the size of the BWP for each BWP, where the position of the starting RB refers to the starting RB relative to the frequency domain starting point of the carrier where the BWP is located.
  • the carrier frequency domain starting point is provided by offsetToCarrier, which is an offset value relative to pointA. This parameter is notified in the SIB.
  • FIG. 3 is a schematic diagram of the position of the starting RB of the BWP relative to the frequency domain starting point of the carrier where the BWP is located.
  • the figure includes three BWPs: BWP i, BWP j and BWP k.
  • BWP i, BWP j and BWP k are respectively located on three different carriers: carrier p, carrier q and carrier m.
  • the positions of Point A of the carriers where the three BWPs are located are different.
  • the positions of the starting RBs of the three BWPs are and
  • the size of the 3 BWPs can be expressed as and The subscripts i, j, and k are used to distinguish different BWPs.
  • the frequency reference point of the frequency domain unit associated with CD-SSB can be obtained based on SSB, and the frequency reference points of other frequency domain units can be configured to be the same.
  • Figure 4 is a schematic diagram of the frequency reference points of each frequency domain unit of the terminal. Referring to Figure 4, the frequency reference points of carrier q and carrier p are the same, carrier m is the carrier where CD-SSB is located, and the frequency reference point of carrier m is different from the frequency reference points of carrier p and carrier q.
  • the frequency reference point of the carrier where CD-SSB is located may also be the same as the frequency reference points of other carriers.
  • the terminal obtains frequency domain resources of the CORESET on M frequency domain units.
  • the service cell of the terminal is configured with P frequency domain units.
  • the network side device in this embodiment can configure CORESET on all or part of the P frequency domain units.
  • M is equal to P
  • the network side configures CORESET on all frequency domain units of the service cell.
  • M is less than P
  • the network side configures CORESET on part of the frequency domain units of the service cell.
  • Figure 5 is a schematic diagram of configuring CORESET for all frequency domain units of the service cell of the terminal
  • Figure 6 is a schematic diagram of configuring CORESET for some frequency domain units of the service cell of the terminal.
  • the service cell of the terminal is configured with three frequency domain units: frequency domain unit A, frequency domain unit B, and frequency domain unit C.
  • the three frequency domain units can be BWP, carrier or frequency band.
  • all three frequency domain units are configured with CORESET
  • frequency domain units B and C are configured with CORESET
  • frequency domain unit A is not configured with CORESET.
  • each frequency domain unit can be the same or different
  • the number of CORESETs configured on each frequency domain unit can be the same or different
  • multiple CORESETs in each frequency domain unit can overlap in the frequency domain or time domain.
  • the public signaling overhead can be reduced and load balancing of each uplink (UL)/downlink (DL) carrier can be achieved.
  • the frequency domain resources of a CORESET can be continuous or discontinuous.
  • Each CORESET has a CORESET identity (ID), which uniquely identifies a CORESET among all BWPs in a service cell.
  • ID CORESET identity
  • the terminal can obtain the frequency domain resources of CORESET on the frequency domain unit through the frequencyDomainResources parameter.
  • the frequency domain resources of CORESET can be indicated by a 45-bit bitmap.
  • Each bit can indicate an RB group (for example, 6 PRBs). The value of each bit is 0 or 1. 1 indicates that the RB group corresponding to the bit is the frequency domain resource of CORESET, and 0 indicates that the RB group corresponding to the bit is not the frequency domain resource of CORESET.
  • the RB group corresponding to the first bit (Most Significant Bit, MBS) of the frequencyDomainResources field is the first RB group on the corresponding frequency domain unit, not the first RB group on the corresponding CORESET.
  • the commonRB sequence number corresponding to the first RB of the first RB group on the BWP is: The value of m is 6. Indicates the position of the starting RB of BWPi.
  • any one of the M frequency domain units can be used to send downlink control information to improve flexibility.
  • the network side device can only send downlink control information on the CORESET of the frequency domain unit C.
  • the downlink control information includes system information and paging information, etc.
  • the system information includes SSB, system information block (System Information Block, SIB), remaining minimum system information (Remaining Minimum System Information, RMSI) and other system information (Other System Information, OSI), etc.
  • the downlink control information includes necessary information, such as the frequency of each carrier, SCS, random access channel (Random Access Channel, RACH) resources, etc.
  • the terminal can receive the PDCCH of MSG2 in the random access process on a subset of the frequency domain unit (a frequency domain unit).
  • the terminal determines at least one CORESET for receiving the PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • the method of the embodiment of the present application can be used before or after the RRC connection is established.
  • the CORESET configuration information involved in this article can be notified through the SIB.
  • the CORESET configuration information involved in this article can be notified through an RRC message.
  • One or more CORESETs can be configured on each frequency domain unit. Assuming that N1 CORESETs are configured on M frequency domain units, the value of N1 is greater than or equal to M, that is, M frequency domain units include at least M CORESETs.
  • the terminal can combine all or part of the CORESETs on the M frequency domain units across frequency domain units according to predefined rules or instructions from network-side devices to obtain a CORESET for receiving PDCCH, so that the CORESET for receiving PDCCH has a larger bandwidth.
  • a CORESET with a larger bandwidth can support a higher aggregation level.
  • aggregation level AL 16 needs to occupy 96 RBs (16 CCEs).
  • a narrow bandwidth carrier usually cannot carry CCEs with a higher aggregation level.
  • the method of this embodiment combines CORESETs on multiple frequency domain units across frequency domain units, so that the terminal can support a higher aggregation level and increase the coverage capability of PDCCH.
  • a CORESET with a larger bandwidth can also reduce the conflict probability of PDCCH and increase the transmission reliability of PDCCH.
  • the terminal determines the order of CORESETs on the M frequency domain units, and cascades to form at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units, and the cascaded CORESET is used to receive the PDCCH.
  • the CORESETs on M frequency domain units can be cascaded across frequency domain units to form one or more cascaded CORESETs, each cascaded CORESET includes one or more CORESETs, and the bandwidth of the cascaded CORESET is usually larger than that of the non-cascaded CORESET, so that PDCCH can be received on a larger bandwidth.
  • the network can instruct the terminal to cascade a subset of the CORESETs, that is, the CORESETs on a frequency domain unit can partially participate in the cascade, and can partially not participate in the cascade, depending on the flexible configuration of the network.
  • the network does not need to consider the capabilities of the terminal, that is, the network does not need to consider the capabilities of the terminal when configuring M frequency domain units for the terminal device.
  • the PDCCH carried or sent on the cascaded CORESET is used to schedule data of the P frequency domain units, or, it is described as the control information in the PDCCH carried or sent on the cascaded CORESET is used to control data transmission on the P frequency domain units. Since CORESET is configured only on some frequency domain units among the P frequency domain units, the common signaling overhead can be reduced.
  • the network may notify the CORESET configuration and the CORESET cascade configuration through the SIB message.
  • the CORESET configuration includes the frequency domain resources of the CORESET.
  • the CORESET cascade configuration is used to instruct the terminal to perform cascading.
  • the CORESET cascade configuration includes information required for the terminal to perform cascading, including but not limited to the identifier of the cascaded CORESET and the index of the CORESET used for cascading.
  • the network After the RRC connection is established, the network notifies the CORESET configuration and CORESET cascade configuration through the RRC message.
  • CORESET 0 if the network configures a CORESET that receives SIB information, such as CORESET 0, then the CORESET configuration of each frequency domain unit and the CORESET cascade configuration need to be determined according to the MIB message and predefined rules.
  • CORESET 0 usually only needs one configuration, which is common to all terminals.
  • M frequency domain units are frequency domain units of the frequency band combination supported by the terminal, and the terminal determines that the CORESET of each frequency domain unit in the M frequency domain units is used to receive the PDCCH.
  • the CORESETs on different frequency domain units can be cascaded or not.
  • the terminal can simultaneously use the CORESETs of multiple frequency domain units capable of frequency band combination to receive the PDCCH, which is equivalent to increasing the bandwidth of the CORESET.
  • the terminal can be in any of the following states: idle state, inactive state, or RRC connected state.
  • the network needs to consider the capability of the terminal, that is, the network needs to consider the capability of the terminal when configuring M frequency domain units for the terminal device.
  • the frequency domain unit of the frequency band combination supported by the terminal can also be described as a frequency domain unit related to the frequency band combination (bandcombination) capability of the terminal.
  • the frequency band combination is also called the frequency band merging.
  • the frequency band combination capability is used to indicate the number of frequency bands supported by the terminal at the same time.
  • a terminal may support one or more frequency bands at the same time, and different terminals have different frequency band combination capabilities.
  • the frequency domain units on all frequency bands supported by the terminal constitute the frequency domain unit of the frequency band combination supported by the terminal.
  • the frequency band combination supported by terminal 1 is frequency band A and frequency band C
  • the frequency domain unit of the frequency band combination supported by terminal 1 is the frequency domain unit on frequency band A and frequency band C supported by terminal 1.
  • the network Before the RRC connection is established, the network does not obtain the terminal's capability information.
  • the network can pre-indicate the CORESET configuration and CORESET cascade configuration corresponding to a certain frequency band combination capability in the SIB based on prior information, such as the frequency bands where each frequency domain unit of the serving cell supports frequency band combinations. For example, if the serving cell supports different terminal types such as UE capabilities A, B, and C, the network can perform CORESET configuration and CORESET cascade configuration for at least one terminal capability.
  • the network After the RRC connection is established, the network has obtained the capability information of the terminal.
  • the network can configure the CORESET configuration and CORESET cascade configuration corresponding to a certain terminal type in the RRC message according to the terminal capability information and the frequency band combination capabilities supported by different terminals.
  • the CORESET configuration and CORESET cascade configuration of each frequency domain unit needs to be determined according to the MIB message and predefined rules.
  • M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, and the terminal cascades CORESETs on different frequency domain units
  • M is usually less than P.
  • the PDCCH carried or sent on the cascaded CORESET is used to schedule data of the M frequency domain units, or, the control information in the PDCCH carried or sent on the cascaded CORESET is described as being used to control data transmission on the M frequency domain units.
  • the network can also configure a CORESET of Q frequency domain units, where Q is less than or equal to M, and the CORESET of these Q frequency domain units or the cascaded CORESET formed by the cascade of these Q frequency domain units can schedule data of the M frequency domain units.
  • the terminal obtains configuration information of M frequency domain unit combinations according to the terminal capability, where M is less than or equal to the number P of frequency domain units configured in the service cell of the terminal, obtains the frequency domain resources of the CORESET on the M frequency domain unit combinations, and determines at least one CORESET for receiving the PDCCH according to the configuration information of the M frequency domain unit combinations and the frequency domain resources of the CORESET.
  • the terminal capability can be matched, the public signaling overhead can be reduced, and the load balance of each uplink UL/DL carrier can be achieved.
  • the CORESET for receiving the PDCCH can be obtained by cascading all or part of the CORESET cross-frequency domain unit combinations on the M frequency domain unit combinations, so that the CORESET for receiving the PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases the PDCCH coverage capability and transmission reliability, and increases network flexibility.
  • Embodiment 2 of the present application provides a control channel transmission method, and the implementation methods recorded in Embodiment 1 can be applied to Embodiment 2, and can achieve the same technical effect.
  • This embodiment is illustrated by taking the terminal cascading the CORESET of M frequency domain units as an example.
  • Figure 7 is a flow chart of the control channel transmission method provided in Embodiment 2 of the present application. As shown in Figure 7, the method provided in this embodiment includes the following steps.
  • a terminal obtains configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal.
  • the M frequency domain units may be any M frequency domain units in a service cell of the terminal, that is, the M frequency domain units are frequency domain units irrelevant to the frequency band combination capability of the terminal.
  • the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.
  • Band combination capability is a concept introduced in the carrier aggregation (CA) technology.
  • Band combination capability is used to indicate the number of bands supported by a terminal at the same time.
  • a terminal may support one or more bands at the same time.
  • Different terminals have different band combination capabilities. For example, terminal 1 only supports band A and band C, so the band combination supported by terminal 1 is band A and band C.
  • Terminal 2 only supports band B and band C, so the band combination supported by terminal 2 is band B and band C.
  • Terminal 3 only supports band C, so the band combination supported by terminal 3 is band C.
  • the network side device can configure the frequency domain unit for cascading for the terminal according to the band combination capability of the terminal, that is, the network side device only configures CORESET on the frequency domain unit on the frequency band supported by the terminal, and does not configure the frequency domain unit and CORESET on the frequency band not supported by the terminal.
  • the terminal device only cascades the CORESET on the frequency band it supports.
  • the terminal obtains frequency domain resources of the CORESET on M frequency domain units.
  • the terminal determines the order of CORESETs on M frequency domain units.
  • the terminal arranges the CORESETs on the M frequency domain units in ascending or descending order according to the starting frequencies of the CORESETs on the M frequency domain units, and cascades them according to a predefined cascading rule or as instructed by the network.
  • the terminal arranges the CORESETs on the M frequency domain units in ascending or descending order according to the starting frequencies of the M frequency domain units, and cascades them according to a predefined cascading rule and as instructed by the network.
  • the terminal cascades the CORESETs on the M frequency domain units to form at least one cascaded CORESET, where the cascaded CORESET is used to receive the PDCCH.
  • the M frequency domain units are any M frequency domain units in the serving cell of the terminal, or the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, the following two methods can be used to cascade the CORESETs of the M frequency domain units.
  • the terminal cascades to form at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units and a predefined cascading rule.
  • the predefined cascading rule may be sent by the network side device to the terminal, or may be pre-agreed between the network side device and the terminal.
  • the predefined cascading rule may be: cascading all CORESETs configured on the network side to form a cascaded CORESET. Then the terminal cascades the CORESETs on the M frequency domain units to form a cascaded CORESET according to the predefined rule and the order of the CORESETs on the M frequency domain units.
  • the terminal sorts the CORESETs on the M frequency domain units, and the order of the CORESETs on the M frequency domain units can represent the order of the CCEs in the cascaded CORESET.
  • Figure 8 is a schematic diagram of a cascade of CORESETs of multiple frequency domain units.
  • Figure 8 takes the frequency domain unit as BWP as an example.
  • the service cell of the terminal is configured with three BWPs: BWP i, BWP j and BWP k.
  • BWP i is located on carrier p of frequency band A
  • BWP j is located on carrier q of frequency band B
  • BWP k is located on carrier m of frequency band C.
  • a CORESET is configured on each BWP.
  • the terminal sorts the CORESETs of the three BWPs and cascades them to form a cascaded CORESETm.
  • the CCEs in the cascaded CORESETm are numbered 0-5, and the order of the CCE numbers in the cascaded CORESETm corresponds to the starting frequency order of the three BWPs, or the starting frequency order of the CORESETs in the three BWPs.
  • FIG9 is another schematic diagram of cascading CORESETs of multiple frequency domain units.
  • the difference between FIG9 and FIG8 is that in FIG9, no CORESET is configured for BWPi, that is, the network side device only configures CORESET for some BWPs in the BWP configured in the serving cell of the terminal, rather than configuring CORESET for all BWPs.
  • the CCEs in the cascaded CORESETm in FIG9 are numbered 0-4.
  • the predefined cascading rule may also be: selecting a CORESET with the same CORESET number from each frequency domain unit to cascade to form a cascaded CORESET.
  • FIG 10 is another cascade diagram of CORESETs of multiple frequency domain units.
  • the terminal first sorts the three BWPs according to their starting frequencies.
  • a CORESET with the same serial number is selected from the three BWPs each time according to the CORESET serial number from small to large or from large to small to form a cascaded CORESET.
  • first cascade CORESET number 1 the terminal selects CORESET number 1 from BWP i, BWP j and BWP k: CORESETi_1, CORESETj_1 and CORESET k_1, CORESETi_1, CORESETj_1 and CORESET k_1 are cascaded to form cascade CORESET A.
  • the terminal cascades to form at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units and the cascade indication information sent by the network side device.
  • the cascade indication information includes the identifier of the cascaded CORESET and the index of the CORESET participating in the cascade in the M frequency domain units.
  • the network side device may send the cascade indication information and the configuration information of the M frequency domain units to the terminal together, or may send the cascade indication information and the configuration information of the M frequency domain units to the terminal separately through different messages.
  • the cascade indication information includes a cascade CORESET identifier: cascade CORESET m, and the index of each CORESET participating in the cascade.
  • the cascade indication information includes three cascade CORESET identifiers: cascade CORESET A, cascade CORESET B and cascade CORESET C, and the index of the CORESET participating in the cascade corresponding to each cascade CORESET identifier.
  • the index of the CORESET participating in the cascade corresponding to cascade CORESET A is: CORESETi_1, CORESETj_1 and CORESET k_1.
  • the terminal needs to notify the network side of the frequency bands it supports before cascading, and then send or receive in the frequency domain units on the frequency bands it supports according to the frequency bands it supports.
  • the network side directly notifies the corresponding configuration of the terminal of at least one capability level according to the candidate terminal capability level.
  • the terminal can determine the frequency bands it supports based on its own frequency band combination capability, such as before the RRC connection is established.
  • the network side device indicates to the terminal the configuration corresponding to the frequency bands supported by the terminal, such as after the RRC connection is established.
  • the network side device can carry the frequency band combination information in the cascade indication information, and the frequency band combination information is used to indicate the frequency band combination of the frequency domain units related to the frequency band combination capability of the terminal.
  • the frequency band combination information includes a combination identifier, and the combination identifier is used to indicate that the frequency bands supported by the terminal are combined.
  • the frequency band combination information also includes the identifier of the combined frequency band. For example, if the terminal supports frequency band A and frequency band C, then the frequency band combination information also includes the identifier or frequency information of frequency band A and frequency band C.
  • FIG11 is a schematic diagram of the cascade of CORESETs of frequency domain units of multiple terminals.
  • terminal 1 only supports frequency band A and frequency band C
  • terminal 2 only supports frequency band B and frequency band C
  • terminal 3 only supports frequency band C.
  • the network side device configures CORESETi1 of frequency band A and CORESET k1 of frequency band C for terminal 1, configures CORESET j1 of frequency band B and CORESET k2 of frequency band C for terminal 2, and configures CORESET k3 of frequency band C for terminal 3 according to the frequency band combination capability of each terminal.
  • Terminal 1 can see CORESET i of band A and CORESET k1 of band C through the configuration parameters on the network side, and can cascade CORESET i and CORESET k1 into a cascade CORESET m.
  • Terminal 1 receives PDCCH on cascade CORESET m.
  • Terminal 2 can see CORESET j1 of band B and CORESET k2 of band C through the configuration parameters on the network side, and can cascade CORESET j1 and CORESET k2 into a cascade CORESET n.
  • Terminal 2 receives PDCCH on cascade CORESET n.
  • Terminal 3 can see CORESET k3 on band C through the configuration parameters on the network side, and Terminal 3 receives PDCCH on (cascaded) CORESET n k3.
  • any one of the M frequency domain units is used to send downlink control information to improve flexibility.
  • the network side device only sends SSB on the frequency domain unit of frequency band C.
  • the terminal can receive PDCCH on the CORESET of any frequency domain unit.
  • the CORESETs of multiple frequency domain units may not be cascaded.
  • the terminal does not expect at least one of the following configuration parameters of the cascaded CORESETs to be different:
  • QCL Quasi-Colocation
  • TCI Transmission Configuration Indication
  • the terminal does not expect at least one of the following configuration parameters of the cascaded CORESET to be different, which can be understood as the UE expects at least one of the following configuration parameters of the cascaded CORESET to be the same.
  • the mapping type of CCE to REG is an interleaved type or a non-interleaved type.
  • the mapping type of CCE to REG used in the cascaded CORESET is an interleaved type, it can provide diversity gain and enhance the reliability of PDCCH transmission.
  • the TCI field existence indication is used to indicate whether a TCL field exists in the DCI.
  • the network tester can configure the search space for the cascaded CORESET.
  • the search space type associated with the cascaded CORESET can be a public search space or a dedicated search space.
  • a cascaded CORESET may include one or more CORESETs, and the search space associated with the cascaded CORESET refers to the search space of each CORESET included in the cascaded CORESET.
  • the search space of each CORESET included in the cascaded CORESET can be the same or different.
  • the search space associated with the cascaded CORESET should meet predefined requirements, for example, requirements related to monitoring PDCCH capabilities based on time slots or spans.
  • the method of this embodiment can be used before or after the RRC connection is established.
  • the CORESET configuration information can be notified through the SIB.
  • the network side device may not be able to obtain the capabilities of the terminal, so the network side device needs to configure and cascade the CORESET on the frequency domain unit according to the prior information of the terminal capabilities supported by the frequency domain unit.
  • the CORESET configuration information can be notified through the RRC message.
  • the network side device has obtained the terminal capabilities and can configure one or more CORESETs on a frequency domain unit. Therefore, the network side device can configure the frequency domain unit related to the frequency band combination capability of the terminal according to the terminal capabilities.
  • the terminal obtains configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in the service cell of the terminal.
  • the terminal obtains frequency domain resources of CORESET on the M frequency domain units, determines the order of CORESET on the M frequency domain units, and cascades to form at least one cascade CORESET according to the order of CORESET on the M frequency domain units.
  • the cascade CORESET is used to receive PDCCH. By configuring CORESET on all or part of the frequency domain units of the service cell of the terminal, and cascading the configured CORESET cross-band units to form a cascade CORESET, PDCCH is received on the cascade CORESET.
  • the cascade CORESET has a larger bandwidth, reduces the probability of PDCCH conflict, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.
  • Embodiment 3 of the present application provides a control channel transmission method.
  • the implementation methods described in Embodiment 1 and Embodiment 2 can be applied to Embodiment 3 and can achieve the same technical effect.
  • FIG12 is a flow chart of the control channel transmission method provided in Embodiment 3 of the present application. As shown in FIG12, the method provided in this embodiment includes the following steps.
  • the terminal obtains configuration information of M frequency domain units, where the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, and M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal.
  • the terminal obtains frequency domain resources of CORESET on M frequency domain units.
  • S303 The terminal determines a CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for receiving a PDCCH.
  • the CORESETs on the M frequency domain units of the frequency band combination supported by the terminal are not cascaded. Instead, the CORESETs on the M frequency domain units of the frequency band combination supported by the terminal are used as independent CORESETs.
  • the terminal can use the CORESETs on the M frequency domain units to receive PDCCH at the same time, which is equivalent to increasing the frequency domain range of the CORESET used to receive PDCCH, thereby increasing transmission reliability and network flexibility. Furthermore, the probability of PDCCH conflict can be reduced and the PDCCH coverage capability can be improved.
  • FIG13 is a schematic diagram of the CORESET of the frequency domain unit of the terminal, assuming that the frequency band combination capability of the terminal is: terminal 1 only supports frequency band A and frequency band C, terminal 2 only supports frequency band B and frequency band C, and terminal 3 only supports frequency band C. Then, the CORESET determined by terminal 1 for receiving PDCCH is CORESETi1 on frequency band A and CORESETk1 on frequency band C, the CORESET determined by terminal 2 for receiving PDCCH is CORESET j1 on frequency band B and CORESETk1 on frequency band C, and the CORESET determined by terminal 3 for receiving PDCCH is CORESETk1 on frequency band C.
  • Figure 13 takes the example of only one CORESET on each frequency band. Of course, there can be multiple CORESETs on each frequency band.
  • the terminal can select all or part of the multiple CORESETs for receiving PDCCH according to predefined rules, or determine all or part of the multiple CORESETs for receiving PDCCH according to the indication of the network side device.
  • the network side device can indicate the index of the CORESET used to receive PDCCH.
  • the number of CORESETs on any frequency domain unit in the frequency domain unit of the frequency band combination supported by the terminal is not greater than the maximum number of CORESETs supported by the terminal, that is, the terminal does not expect the number of CORESETs on any frequency domain unit to be greater than the CORESET number capability supported by the terminal, and the CORESET number capability supported by the terminal is the maximum number of CORESETs supported by the terminal. It can be understood that the maximum number of CORESETs supported by the terminal on different types of frequency domain units may be different. Taking BWP as an example, a maximum of 3 CORESETs are configured on BWP, and the maximum number of CORESETs supported by the terminal is 3.
  • the terminal obtains configuration information of M frequency domain units, where the M frequency domain units are frequency domain units of the frequency band combination supported by the terminal, M is less than or equal to the number P of frequency domain units configured by the service cell of the terminal, obtains the frequency domain resources of the CORESET on the M frequency domain units, and determines the CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for receiving PDCCH.
  • the terminal can use the CORESET on the M frequency domain units to receive PDCCH at the same time, which is equivalent to increasing the frequency domain range of the CORESET used to receive PDCCH, thereby increasing transmission reliability and network flexibility, and further, can reduce the probability of PDCCH conflict and improve PDCCH coverage capability.
  • Embodiment 4 of the present application provides a control channel transmission method, which is executed by a network side device.
  • FIG14 is a flowchart of the control channel transmission method provided by Embodiment 4 of the present application. As shown in FIG14 , the method provided by this embodiment includes the following steps.
  • a network-side device sends configuration information of M frequency domain units to a terminal, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal.
  • the configuration information of the M frequency domain units includes at least one of the following:
  • the index of each frequency domain unit in the M frequency domain units is the index of each frequency domain unit in the M frequency domain units.
  • the value of M is less than or equal to P, that is, the network side device can configure CORESET only on some frequency domain units of the serving cell, making the configuration of CORESET more flexible.
  • the M frequency domain units can be any M frequency domain units in the serving cell of the terminal, or they can be frequency domain units of the frequency band combination supported by the terminal.
  • the network-side device sends frequency domain resources of CORESET on M frequency domain units to the terminal.
  • the network side device may send the configuration information of the M frequency domain units and the frequency domain resources of the CORESET to the terminal through the same message, or may send the configuration information of the M frequency domain units and the frequency domain resources of the CORESET to the terminal through different messages.
  • One or more CORESETs can be configured on a frequency domain unit, and the frequency domain resources or time domain resources of multiple CORESETs in a frequency domain unit can overlap.
  • the network side device sends a PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • the network side device sends the configuration information of M frequency domain units and the frequency domain resources of CORESET to the terminal, so that the terminal combines all or part of the CORESET cross-frequency domain units on the M frequency domain units to determine the CORESET for receiving the PDCCH. Similarly, the network side device also needs to combine all or part of the CORESET cross-frequency domain units on the M frequency domain units according to the configuration information of the M frequency domain units and the frequency domain resources of CORESET to determine at least one CORESET for sending the PDCCH.
  • the network side device determines the order of CORESETs on the M frequency domain units, cascades to form at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units, and sends the PDCCH on the cascaded CORESET.
  • the method for the network side device to sort the CORESETs on the M frequency domain units refers to the method for sorting the terminals in the aforementioned embodiment, which will not be repeated here.
  • the network side device can cascade to form at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units and a predefined cascade rule.
  • the predefined rule can be negotiated by the network side device and the terminal, or determined by the network side device and sent to the terminal. Subsequently, the network side device and the terminal cascade the CORESETs on the M frequency domain units according to the predefined cascade rule.
  • the network side device determines several cascaded CORESETs and the CORESETs participating in the cascade in the M frequency domain units based on some information, and the network side device generates cascade indication information, which includes the identifier of the cascaded CORESET and the index of the CORESET participating in the cascade in the M frequency domain units.
  • the terminal side device can cascade the CORESETs on the M frequency domain units according to the cascade indication information, and send the cascade indication information to the terminal, so that the terminal performs cascade according to the cascade indication information.
  • the network side device may cascade the CORESETs on the M frequency domain units.
  • the specific method for cascading by the network side device refers to the method for cascading by the terminal in the aforementioned embodiment, which will not be repeated here.
  • the cascade indication information also includes frequency band combination information, which is used to indicate the frequency band combination of frequency domain units related to the frequency band combination capability of the terminal.
  • the network side device may not cascade the CORESETs on the M frequency domain units, that is, the network side device may determine the CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for sending PDCCH, and accordingly, the network side device sends PDCCH to the terminal on the CORESET of the M frequency domain units. In this way, the network side device only sends PDCCH on the frequency domain units of the frequency band combination supported by the terminal.
  • the network side device sends downlink control information on some frequency domain units among the M frequency domain units.
  • the network side device sends downlink control information on only any one frequency domain unit among the M frequency domain units.
  • the network side device sends configuration information of M frequency domain units to the terminal, where M is less than or equal to the number P of frequency domain units configured in the service cell of the terminal, sends frequency domain resources of CORESET on the M frequency domain units to the terminal, and sends PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of CORESET.
  • the network side device can reduce the common signaling overhead and achieve load balancing of each uplink UL/DL carrier by configuring CORESET on some frequency domain units of the service cell of the terminal.
  • the network side device combines all or part of the CORESET cross-frequency domain units on the M frequency domain units to obtain a CORESET for sending PDCCH, so that the CORESET for sending PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases the PDCCH coverage capability and transmission reliability, and increases network flexibility.
  • Embodiment 5 of the present application provides a control channel transmission method.
  • This embodiment is used to describe the signaling interaction between the terminal and the network side device during the transmission of the control channel.
  • Figure 15 is a signaling flow chart of a control channel transmission method provided by Embodiment 5 of the present application. As shown in Figure 15, the method provided by this embodiment includes the following steps.
  • a network-side device sends configuration information of M frequency domain units to a terminal.
  • M is less than or equal to the number P of frequency domain units configured for the service cell of the terminal.
  • S502 The network-side device sends frequency domain resources of CORESET on M frequency domain units to the terminal.
  • the network-side device determines at least one CORESET for sending the PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • the terminal device determines at least one CORESET for receiving the PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • steps S503 and S504 There is no sequential order for executing steps S503 and S504, and they can also be executed simultaneously.
  • the network side device sends a PDCCH on the determined at least one CORESET.
  • the terminal receives the PDCCH on the determined at least one CORESET.
  • the control channel transmission method provided in the embodiment of the present application can be executed by a control channel transmission device .
  • the control channel transmission device provided in the embodiment of the present application is described by taking a control channel transmission method executed by a control channel transmission device as an example.
  • FIG16 is a schematic diagram of the structure of a control channel transmission device provided in Embodiment 6 of the present application.
  • the device can be used in a terminal.
  • the control channel transmission device 100 provided in this embodiment includes the following modules.
  • An acquisition module 11 is used to acquire configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal;
  • the acquisition module 11 is further used to acquire the frequency domain resources of the CORESET on the M frequency domain units;
  • the determination module 12 is used to determine at least one CORESET for receiving the PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • the determining module 12 is specifically configured to:
  • At least one cascaded CORESET is formed by cascading, and the cascaded CORESET is used to receive the PDCCH.
  • the determining module 12 is specifically configured to:
  • the CORESETs on the M frequency domain units are arranged in ascending order or descending order.
  • the determining module 12 is specifically configured to:
  • the M frequency domain units are arranged in ascending order or descending order according to the starting frequencies of the M frequency domain units.
  • the determining module 12 is specifically configured to:
  • At least one cascaded CORESET is formed by cascading.
  • the determining module is specifically configured to:
  • At least one cascade CORESET is cascaded to form the cascade, and the cascade indication information includes the identifier of the cascade CORESET and the index of the CORESET participating in the cascade in the M frequency domain units.
  • the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.
  • the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal;
  • the cascade indication information also includes frequency band combination information, where the frequency band combination information is used to indicate the frequency band combination of the frequency domain units related to the frequency band combination capability of the terminal.
  • the terminal does not expect at least one of the following configuration parameters of the cascaded CORESET to be different:
  • the CCE to REG mapping type used in the cascaded CORESET is an interleaved type.
  • the search spaces of the CORESETs included in the cascaded CORESET are the same or different.
  • the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal;
  • the determining module 12 is specifically used to determine the CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for receiving the PDCCH.
  • the number of CORESETs on any frequency domain unit of the frequency domain units of the frequency band combination supported by the terminal is not greater than the maximum number of CORESETs supported by the terminal.
  • the configuration information of the M frequency domain units includes at least one of the following:
  • the frequency reference points of the M frequency domain units include at least one of the following:
  • any one frequency domain unit among the M frequency domain units is used to send downlink control information.
  • the M frequency domain units include at least one of the following units: a BWP, a carrier, or a frequency band.
  • the network-side device can reduce the common signaling overhead and achieve load balancing of each uplink UL/DL carrier by configuring CORESET on some frequency domain units of the terminal's service cell.
  • the terminal obtains a CORESET for receiving PDCCH by combining all or part of the CORESET cross-frequency domain units on M frequency domain units, so that the CORESET for receiving PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.
  • Embodiment 7 of the present application provides a transmission device for a control channel, which can be used in a network side device.
  • FIG17 is a structural diagram of a transmission device for a control channel provided in Embodiment 7 of the present application. As shown in FIG17 , the transmission device 200 for a control channel provided in this embodiment includes the following modules.
  • a sending module 21, configured to send configuration information of M frequency domain units to a terminal, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal;
  • the sending module 21 is used to send the frequency domain resources of the CORESET on the M frequency domain units to the terminal;
  • the processing module 22 is configured to send the PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.
  • processing module 22 is specifically configured to:
  • the PDCCH is sent on the cascaded CORESET.
  • the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.
  • the sending module 21 is further configured to:
  • the cascade indication information includes an identifier of the cascaded CORESET and an index of the CORESET participating in the cascade in the M frequency domain units.
  • the cascade indication information when the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, the cascade indication information also includes frequency band combination information, and the frequency band combination information is used to indicate the frequency band combination of the frequency domain units related to the frequency band combination capability of the terminal.
  • the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal;
  • the processing module 22 is specifically used for:
  • the PDCCH is sent to the terminal on the CORESET of the M frequency domain units.
  • the network side equipment can reduce the common signaling overhead and achieve load balancing of each uplink UL/DL carrier by configuring CORESET on some frequency domain units of the service cell of the terminal.
  • the network side equipment combines all or part of the CORESET cross-frequency domain units on M frequency domain units to obtain the CORESET used to send PDCCH, so that the CORESET used to send PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.
  • the transmission device of the control channel in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip.
  • the electronic device can be a terminal, or it can be other devices other than a terminal.
  • the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
  • the transmission device of the control channel provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 15 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application further provides a communication device 300, including a processor 31 and a memory 32, and the memory 32 stores a program or instruction that can be run on the processor 31.
  • the communication device 300 is a terminal
  • the program or instruction is executed by the processor 31 to implement the various steps of the above-mentioned method embodiments of FIG2-FIG13, and can achieve the same technical effect.
  • the communication device 300 is a network side device
  • the program or instruction is executed by the processor 31 to implement the various steps of the above-mentioned method embodiment of FIG14, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application also provides a terminal, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps in the method embodiment shown in Figures 2-13.
  • This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the terminal embodiment and can achieve the same technical effect.
  • Figure 19 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 400 includes but is not limited to: a radio frequency unit 41, a network module 42, an audio output unit 43, an input unit 44, a sensor 45, a display unit 46, a user input unit 47, an interface unit 48, a memory 49 and at least some of the components of the processor 410.
  • the terminal 400 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor x 10 through a power management system, so as to implement functions such as managing charging, discharging, and power consumption management through the power management system.
  • a power source such as a battery
  • the terminal structure shown in FIG19 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.
  • the input unit 44 may include a graphics processing unit (GPU) 441 and a microphone 442, and the graphics processor 441 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 46 may include a display panel 461, and the display panel 461 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc.
  • the user input unit 47 includes a touch panel 471 and at least one of other input devices 472.
  • the touch panel 471 is also called a touch screen.
  • the touch panel 471 may include two parts: a touch detection device and a touch controller.
  • Other input devices 472 may include, but are not limited to, a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
  • the RF unit 41 can transmit the data to the processor 410 for processing; in addition, the RF unit 41 can send uplink data to the network side device.
  • the RF unit 41 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
  • the memory 49 can be used to store software programs or instructions and various data.
  • the memory 49 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, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc.
  • the memory 49 may include a volatile memory or a non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM).
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • DRRAM direct memory bus random access memory
  • the processor 410 may include one or more processing units; optionally, the processor 410 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 410.
  • the processor 410 is used to obtain configuration information of M frequency domain units, M is less than or equal to the number P of frequency domain units configured in the service cell of the terminal; obtain the frequency domain resources of the control resource set CORESET on the M frequency domain units; and determine at least one CORESET for receiving PDCCH based on the configuration information of the M frequency domain units and the frequency domain resources of CORESET.
  • the public signaling overhead can be reduced and the load balance of each uplink UL/DL carrier can be achieved.
  • a CORESET for receiving PDCCH is obtained, so that the CORESET for receiving PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.
  • the embodiment of the present application also provides a network side device, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method embodiment shown in Figure 14.
  • the network side device embodiment corresponds to the above-mentioned network side device method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the network side device embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a network side device.
  • the network side device 500 includes: an antenna 51, a radio frequency device 52, a baseband device 53, a processor 54 and a memory 55.
  • the antenna 51 is connected to the radio frequency device 52.
  • the radio frequency device 52 receives information through the antenna 51 and sends the received information to the baseband device 53 for processing.
  • the baseband device 53 processes the information to be sent and sends it to the radio frequency device 52.
  • the radio frequency device 52 processes the received information and sends it out through the antenna 51.
  • the method executed by the network-side device in the above embodiment may be implemented in the baseband device 53, which includes a baseband processor.
  • the baseband device 53 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 20, one of which is, for example, a baseband processor, which is connected to the memory 55 through a bus interface to call the program in the memory 55 and execute the network side device operations shown in the above method embodiment.
  • the network side device may also include a network interface 56, which is, for example, a Common Public Radio Interface (CPRI).
  • CPRI Common Public Radio Interface
  • the network side device 500 of the embodiment of the present application also includes: instructions or programs stored in the memory 55 and executable on the processor 54.
  • the processor 54 calls the instructions or programs in the memory 55 to execute the methods executed by the modules shown in Figure 17 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • the various processes of the method embodiments shown in Figures 2 to 14 above are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.
  • the readable storage medium may be a non-transient readable storage medium.
  • 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 method embodiments shown in Figures 2 to 14 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • 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.
  • 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 control channel transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • 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 method shown in Figures 2 to 13 as described above, and the network side device can be used to execute the steps of the method shown in Figure 14 as described above.

Landscapes

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

Abstract

本申请公开了一种控制信道的传输方法、装置、设备及存储介质，属于通信技术领域，本申请实施例的控制信道的传输方法包括：终端获取M个频域单元的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P，获取M个频域单元上的CORESET的频域资源，根据M个频域单元的配置信息和CORESET的频域资源，确定用于接收PDCCH的至少一个CORESET。

Description

控制信道的传输方法、装置、设备及存储介质
相关申请的交叉引用
本申请要求于2023年12月08日提交中国专利局、申请号为202311691178.0、发明名称为“控制信道的传输方法、装置、设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请属于无线通信技术领域，具体涉及一种控制信道的传输方法、装置、设备及存储介质。
背景技术
新无线(new radio，NR)系统的频谱资源包括Sub-6GHz频段，其中，3GHZ以下的频段称为Sub-3GHz，其余频段称为C-band。Sub-3GHz频段被碎片化地分配给移动运营商，移动运营商拥有的频谱资源较零散，即频谱资源的带宽较窄且频谱不连续。如何高效、灵活的利用这些零散的、窄带宽的频谱资源向用户提供大容量和大带宽业务是NR系统需要解决的问题之一。
发明内容
本申请实施例提供一种控制信道的传输方法、装置、设备及存储介质，能够利用零散的、窄带宽的频谱资源向用户提供大容量和大带宽业务。
第一方面，提供了一种控制信道的传输方法，由终端执行，该方法包括：终端获取M个频域单元的配置信息，M小于或等于所述终端的服务小区配置的频域单元的数量P；所述终端获取所述M个频域单元上的控制资源集CORESET的频域资源；所述终端根据所述M个频域单元的配置信息和CORESET的频域资源，确定用于接收物理下行控制信道PDCCH的至少一个CORESET。
第二方面，提供了一种控制信道的传输方法，由网络侧设备执行，该方法包括：网络侧设备向终端发送M个频域单元的配置信息，M小于或等于所述终端的服务小区配置的频域单元的数量P；所述网络侧设备向所述终端发送所述M个频域单元上的CORESET的频域资源；所述网络侧设备根据所述M个频域单元的配置信息和CORESET的频域资源，在至少一个CORESET上发送下行控制信道PDCCH。
第三方面，提供了一种控制信道的传输装置，包括：获取模块，用于获取M个频域单元的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P；所述获取模块，还用于获取所述M个频域单元上的CORESET的频域资源；确定模块，用于根据所述M个频域单元的配置信息和CORESET的频域资源，确定用于接收PDCCH的至少一个CORESET。
第四方面，提供了一种控制信道的传输装置，包括：发送模块，用于向终端发送M个频域单元的配置信息，M小于或等于所述终端的服务小区配置的频域单元的数量P；所述发送模块，用于向所述终端发送所述M个频域单元上的CORESET的频域资源；处理模块，用于根据所述M个频域单元的配置信息和CORESET的频域资源，在至少一个CORESET上发送PDCCH。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述处理器用于获取M个频域单元的配置信息，M小于或等于所述终端的服务小区配置的频域单元的数量P，以及获取所述M个频域单元上的CORESET的频域资源；根据所述M个频域单元的配置信息和CORESET的频域资源，确定用于接收物理下行控制信道PDCCH的至少一个CORESET，所述通信接口用于在所述至少一个CORESET上接收PDCCH。
第七方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述处理器用于根据M个频域单元的配置信息和CORESET的频域资源，确定用于发送PDCCH的至少一个CORESET，M小于或等于终端的服务小区配置的频域单元的数量P，所述通信接口用于向向终端发送M个频域单元的配置信息，向所述终端发送所述M个频域单元上的CORESET的频域资源，以及通过所述至少一个CORESET向所述终端发送PDCCH。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十方面，提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的方法的步骤，所述网络侧设备可用于执行如第二方面所述的方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述程序/程序产品被至少一个处理器执行以实现如第一方面或者第二方面所述的控制信道的传输方法的步骤。
在本申请实施例中，网络侧设备通过在终端的服务小区的部分频域单元上配置CORESET，可以减少公共信令开销，达到各上行UL/DL载波的负载平衡，终端通过对M个频域单元上的全部或者部分CORESET跨频域单元进行组合，得到用于接收PDCCH的CORESET，使得用于接收PDCCH的CORESET具有更大的带宽，降低了PDCCH冲突概率，增加了PDCCH覆盖能力及传输可靠性，增加网络灵活性。
附图说明
图1示出本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例一提供的控制信道的传输方法的流程图；
图3为BWP的起始RB相对于BWP所在载波的频域起始点的位置示意图；
图4为终端的各频域单元的频率参考点的示意图；
图5为终端的服务小区的全部频域单元配置CORESET的示意图；
图6为终端的服务小区的部分频域单元配置CORESET的示意图；
图7为本申请实施例二提供的控制信道的传输方法的流程图；
图8为多个频域单元的CORESET的一种级联示意图；
图9为多个频域单元的CORESET的另一种级联示意图；
图10为多个频域单元的CORESET的另一种级联示意图；
图11为多个终端的频域单元的CORESET的级联示意图；
图12为本申请实施例三提供的控制信道的传输方法的流程图；
图13为终端的频域单元的CORESET的一种示意图；
图14为本申请实施例四提供的控制信道的传输方法的流程图；
图15为本申请实施例五提供的一种控制信道的传输方法的信令流程图；
图16为本申请实施例六提供的一种控制信道的传输装置的结构示意图；
图17为本申请实施例七提供的一种控制信道的传输装置的结构示意图；
图18为本申请实施例提供的一种通信设备的结构示意图；
图19为实现本申请实施例的一种终端的硬件结构示意图；
图20为实现本申请实施例的一种网络侧设备的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，本申请中的“或”表示所连接对象的至少其中之一。例如“A或B”涵盖三种方案，即，方案一：包括A且不包括B；方案二：包括B且不包括A；方案三：既包括A又包括B。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的术语“指示”既可以是一个直接的指示(或者说显式的指示)，也可以是一个间接的指示(或者说隐含的指示)。其中，直接的指示可以理解为，发送方在发送的指示中明确告知了接收方具体的信息、需要执行的操作或请求结果等内容；间接的指示可以理解为，接收方根据发送方发送的指示确定对应的信息，或者进行判断并根据判断结果确定需要执行的操作或请求结果等。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)或其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了NR系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统以外的系统，如第6代(6thGeneration，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)、虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、飞行器(flight vehicle)、车载设备(Vehicle User Equipment，VUE)、船载设备、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备。可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。其中，车载设备也可以称为车载终端、车载控制器、车载模块、车载部件、车载芯片或车载单元等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网(Radio Access Network,RAN)设备、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AP)或无线保真(Wireless Fidelity，WiFi)节点等。其中，基站可被称为节点B(Node B，NB)、演进节点B(Evolved Node B，eNB)、下一代节点B(the next generation Node B，gNB)、新空口节点B(New Radio Node B，NR Node B)、接入点、中继站(Relay Base Station，RBS)、服务基站(ServingBase Station，SBS)、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(homeevolved Node B)、发送接收点(Transmission Reception Point，TRP)或所属领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
为了更好的理解本申请各实施例，首先对以下内容进行介绍：
(1)物理下行控制信道(Physical Downlink Control Channel，PDCCH)
PDCCH是下行控制信道，PDCCH上承载着上行物理共享信道(Physical Uplink SharedChannel，PUSCH)和下行共享物理信道(Physical Downlink Share Channel，PDSCH)的下行控制信息(Downlink Control Information，DCI)。在LTE系统中，PDCCH在频域上占据全部带宽，在时域上占据每个子帧的前1-3个符号。在NR系统中，PDCCH若沿用LTE的方式，继续占据全部带宽，会造成资源的浪费，而且会对终端提出很高的要求，所以NR系统中PDCCH的频域资源位于带宽部分(Band Width Part，BWP)内，而且时域也不是占据固定的一些时隙。NR系统中的PDCCH时频资源主要由：控制资源集(Control Resource set，CORESET)和搜索空间(Search Space)决定。
(2)BWP
BWP为一个载波内连续多个资源块(Resource Block，RB)的集合，在NR系统中，网络侧可以根据不同业务类型对终端工作的系统带宽进行动态配置，在降低终端功耗的同时也可以节省网络资源。
示例性的，BWP的技术优势主要有四个方面：
1.终端无需支持全部带宽，只需要满足最低带宽要求即可，有利于低成本终端的开发。
2.当终端业务量不大时，终端可以切换到低带宽运行，可以非常明显的降低功耗。
3.5G技术前向兼容，当5G添加新的技术时，可以直接将新技术在新的BWP上运行，保证了系统的前向兼容。
4.适应业务需要，为业务动态配置BWP。
示例性的，网络侧可以根据业务量的大小动态调整终端的带宽，例如，第一时刻，终端的业务量较大，网络侧给终端配置了一个大带宽(BWP1)；第二时刻，终端的业务量较小，网络侧给终端配置了一个小带宽(BWP2)，满足基本的通信需求即可；第三时刻，网络侧发现BWP1所在带宽内有大范围频率选择性衰落，或者BWP1所在频率范围内资源较为紧缺，于是给终端配置了一个新的带宽(BWP3)。
网络侧为终端配置的多个BWP的频点和宽度不一样，可选的，多个BWP的其他配置参数也可以不同，例如，各BWP的子载波间隔(Subcarrier Spacing，SCS)、循环前缀(Cyclic Prefix，CP)类型、同步广播块(Synchronization Signal/PBCH，SSB)周期等都可以差异化配置。其中，SSB包括同步信号和广播信号，同步信号包括主同步信号(Primary Synchronization Signal，PSS)和辅同步信号(Secondary Synchronization Signal，SSS)，广播信号包括物理广播信道(Physical Broadcast Channel，PBCH)Data和PBCH解调参考信号(Demodulation Reference Signal，DMRS)信号。
(3)CORESET
NR系统中，为了提高资源利用率，降低终端盲检复杂度，引入了CORESET的概念，使得PDCCH不再占据整个带宽。
CORESET是一组物理资源，用于承载PDCCH或者DCI，CORESET相关的参数包括：
资源元素(Resource Element，RE)，由频域上一个子载波，时域上一个正交频分复用(Orthogonal Frequency-Division Multiplexing，OFDM)符号组成。
资源块(Resource Block，RB)，由12个RE组成。
资源元素组(RE group，REG)，频域上一个RB(12个RE)，时域上一个OFDM符号组成。
资源元素组集合(REG Bundles)，由多个REG组成，其数量由无线资源控制(Radio Resource Control，RRC)参数reg-bundle-size确定，bundle size可以是{2,3,6}，与CORESET符号数有关。
控制信道元素(Control-channel element，CCE)，由6个REG组成。
聚合等级(Aggregation Leve，AL)，表示为PDCCH分配了几个CCE，目前支持的聚合等级有{1,2,4,8,16}。
CORESET描述了PDCCH盲检资源的频域特性，PDCCH盲检资源还包括时域特性，PDCCH的频域特性由搜索空间(Search Space，SS)描述，搜索空间用于描述PDCCH的起始符号、检测周期等。
一个CORESET可以由频域上的多个PRB和时域上的1/2/3个OFDM符号组成，CORESET占用的PRB个数和位置可以由网络侧灵活部署。示例性的，CORESET具有如下特征：
CORESET占用的PRB可以连续或不连续；
一个CORESET可以占用时域一个或多个连续的符号，符号数的取值可以为：{1,2,3}；
当CORESET在时域上占用一个符号时，REG bundle size可以是{2，6}；
当CORESET在时域上占用2/3个符号时，REG bundle size可以是等于时域符号数或6；
一个终端可以配置一个或多个CORESET，每个小区每个BWP最多3个CORESET；
一个CORESET可以关联两种搜索空间：公共搜索空间(Common Search Space)和UE专用搜索空间(UE-specific Search Space)；
每个BWP最多配置3个CORESET；
每个BWP最多配置10个搜索空间；
一个终端配置的多个CORESET可以在频域或时域内重叠；
在每个CORESET内，CCE到REG的映射(mapping)方式可以是交织(interleaved)或非交织(non-interleaved)，但一个CORESET只能有一种映射方式。
与LTE/LTE-A系统相比，NR系统追求更大的带宽和吞吐量，NR系统需要使用Sub-3GHz的零散频谱，为用户提供大带宽和大容量，以满足未来不断增长的面向企业(To Business，ToB)和面向用户(ToCustomer，ToC)业务。将使用这些零散的连续或者不连续的频谱的小区称为灵活的服务小区(flexible serving cell)，灵活的服务小区的目的是能够高效、灵活的利用这些零散的频谱。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的控制信道的传输方法进行详细地说明。下述实施例之间可以相互结合，对于相同或相似的概念、过程可能在某些实施例不再赘述。
实施例一
图2是本申请实施例一提供的控制信道的传输方法的流程图，该方法应用于在终端。如图2所示，本实施例提供的方法包括以下步骤。
S101、终端获取M个频域单元的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P。
可选的，该频域单元可以为BWP、载波或者频段(band)。一个频段可以包含多个载波，一个载波可以包含多个BWP。可以理解，不同类型的频域单元的配置信息可能不同。
示例性的，该M个频域单元的配置信息包括以下至少之一：
M个频域单元的频率参考点；
M个频域单元中的每个频域单元相对于该频率参考点的频率偏移值(offsetToCarrier)；
M个频域单元中的每个频域单元的SCS；
M个频域单元中的每个频域单元的CP；
M个频域单元中的每个频域单元的起始RB和大小；
M个频域单元中每个频域单元的索引(或者标识)。
该M个频域单元中的部分或者全部配置信息可以由网络侧设备配置并发送给终端，对于网络侧设备没有配置的信息，终端可以根据其他信息确定。
需要注意的是，对于服务小区配置的P个频域单元，都需要上述频域单元的配置信息，从而使终端能够接收数据，例如PDSCH或者PUSCH。由于本申请强调的是CORESET的处理，所以未对P个频域单元做具体的描述。
在NR系统中，终端的频域单元的带宽不一定等于信道带宽，例如，信道带宽为100MHz，而网络侧分配给终端的BWP的带宽为20MHz，如果终端使用的不是信道带宽的全带宽，那么终端需要根据频率参考点确定分配给自己的频域单元的起始频率。
在NR系统中，该频率参考点可以为PointA，Point A为整个资源栅格的公共参考点。可选的，该M个频域单元的频率参考点包括以下至少之一：
M个频域单元中没有关联小区定义同步信号块(Cell-Defining Synchronization Signal Block，CD-SSB)的频域单元的频率参考点；
M个频域单元中没有关联CD-SSB的频域单元一个公共频率参考点；
M个频域单元中的每个频域单元的频率参考点；
M个频域单元的一个公共频率参考点。
本申请实施例中对于频域单元为BWP的情况，即使CD-SSB不在一个BWP(initialBWP)内，但是CD-SSB可能是与该BWP关联的。对于频域单元为载波/band的情况，可以采用类似定义。可选地，可以定义没有关联CD-SSB的载波/band，指该载波/band上没有CD-SSB。
该M个频域单元中的一些频域单元关联有CD-SSB，另一些没有关联CD-SSB，其中，对于关联有CD-SSB的频域单元，可以根据该频域单元的一些已获取的参数确定该频域单元的频率参考点；对于没有关联CD-SSB的频域单元，可以由网络侧设备为该频域单元配置频率参考点，其中，不同频域单元的频率参考点可以不同。
以频域单元为BWP，系统采用时分双工(Time Division Duplexing，TDD)为例，网络侧设备对至少一个频域单元通过下述方式指示或配置频率参考点(例如pointA)。
对于关联CD-SSB的DL BWP，其频率参考点可以不用网络侧设备配置，其可以根据SSB所在频率的最低频域位置，子载波偏移k_ssb参数，以及offsetToPoint A确定，示例性，采用如下公式计算：
point A的频率参考点＝SSB关联BWP的最低频域位置-k_ssb*u-offsetToPoint A*12*u。
其中，u为子载波间隔，对于FR1是15kHz，对于FR2是60kHz，子载波偏移k_ssb参数和offsetToPoint A可以由网络侧设备在主信息块(MasterInformationBlock，MIB)消息中通知。
对于没有关联CD-SSB的DL BWP，网络侧设备可以为每个载波配置一个频域参考点，网络侧设备可以通过系统信息块(System Information Block，SIB)消息为每个载波配置频域参考点。
当频域单元为BWP时，网络侧设备为每个BWP配置起始RB的位置和BWP的大小，其中，起始RB的位置是指相对于BWP所在载波的频域起始点的起始RB，载波频域起始点由offsetToCarrier提供，为相对于pointA的偏移值，该参数在SIB中通知。
参考图3，图3为BWP的起始RB相对于BWP所在载波的频域起始点的位置示意图，图中共包括3个BWP：BWP i、BWP j和BWP k，BWP i、BWP j和BWP k分别位于三个不同的载波上：载波p、载波q和载波m，图中3个BWP所在的载波的Point A的位置不同，3个BWP的起始RB的位置为和3个BWP的大小可以表示为和其中，下标i、j和k用于区分不同的BWP。
可选的，CD-SSB关联的频域单元的频率参考点可以根据SSB获得，其他频域单元的频率参考点可以配置为相同。示例性的，图4为终端的各频域单元的频率参考点的示意图，参考图4，载波q和载波p的频率参考点相同，载波m为CD-SSB所在的载波，载波m的频率参考点不同于载波p、载波q的频率参考点。可选地，CD-SSB所在的载波的频率参考点与其他载波的频率参考点也可以相同。
S102、终端获取M个频域单元上的CORESET的频域资源。
终端的服务小区配置了P个频域单元，不同于现有技术需要在每个频域单元上配置CORESET，本实施例中网络侧设备可以在该P个频域单元中的全部或者部分频域单元上配置CORESET。当M等于P时，网络侧在服务小区的全部频域单元上配置CORESET，当M小于P时，网络侧在服务小区的部分频域单元上配置CORESET。
图5为终端的服务小区的全部频域单元配置CORESET的示意图，图6为终端的服务小区的部分频域单元配置CORESET的示意图。参考图5和图6，该终端的服务小区配置了3个频域单元：频域单元A、频域单元B和频域单元C，该3个频域单元可以为BWP、载波或者频段，图5中为3个频域单元都配置了CORESET，图6中为频域单元B和C配置了CORESET，频域单元A没有配置CORESET。
可以理解，图5和图6只是一种示意图并不构成限定，各频域单元的带宽可以相同也可以不同，各频域单元上配置的CORESET的数量可以相同也可以不同，每个频域单元内的多个CORESET可以在频域或者时域上重叠。
通过在终端的服务小区的部分频域单元上配置CORESET，可以减少公共信令开销，达到各上行(UpLink，UL)/下行(Down Link，DL)载波的负载平衡。
一个CORESET的频域资源可以连续，也可以不连续。每个CORESET具有CORESET标识(identity，ID)，CORESET ID在一个服务小区内的所有BWP中唯一标识一个CORESET。
终端可以通过frequencyDomainResources参数获取频域单元上的CORESET的频域资源，例如，可以通过45比特(bit)的bitmap方式指示CORESET的频域资源，每个bit可以指示一个1个RB group(例如6个PRB)，每个bit的取值为0或1，1表示bit对应的RB group是CORESET的频域资源，0表示bit对应的RB group不是CORESET的频域资源。
frequencyDomainResources字段的第一个bit(最高有效位，Most Significant Bit，MBS)对应的RB group是对应频域单元上的第一个RB group，而不是对应CORESET上的第一个RB group。
当频域单元为BWP时，BWP上的第一个RB group的第一RB对应的commonRB序号为：其中，m的取值为6，表示BWPi的起始RB的位置。可选的，M个频域单元中的任意一个频域单元可以用于发送下行控制信息以提高灵活性。示例性的，图5和图6所示的频段单元中，网络侧设备可以只在频域单元C的CORESET上发送下行控制信息。
该下行控制信息包括系统信息和寻呼(paging)信息等，系统信息包括SSB、系统信息块(System Information Block，SIB)、剩余最少系统信息(Remaining Minimum System Information，RMSI)and其它系统信息(Other System Information，OSI)等。该下行控制信息中包括必要的信息，例如每个载波的频率、SCS、随机接入信道(Random Access Channel，RACH)资源等，相应的，终端可以在频域单元的一个子集(一个频域单元)上接收随机接入过程中MSG2的PDCCH。
S103、终端根据M个频域单元的配置信息和CORESET的频域资源，确定用于接收PDCCH的至少一个CORESET。
本申请实施例的方法可用于RRC连接建立之前或RRC连接建立之后。对于RRC连接建立之前，本文涉及的CORESET配置信息可以通过SIB通知。对于RRC连接建立之后，本文涉及的CORESET配置信息可以通过RRC消息通知。
每个频域单元上可以配置一个或者多个CORESET，假设M个频域单元上共配置了N1个CORESET，则N1的取值大于或等于M，即M个频域单元至少包括M个CORESET。终端可以根据预定义的规则或者网络侧设备的指示，对M个频域单元上的全部或者部分CORESET跨频域单元进行组合，得到用于接收PDCCH的CORESET，使得用于接收PDCCH的CORESET具有更大的带宽。
更大的带宽的CORESET能够支持更高聚合等级，例如，聚合等级AL 16需要占据96个RB(16个CCE)，窄带宽的载波通常无法承载较高聚合等级的CCE，本实施例的方法通过对多个频域单元上的CORESET进行跨频域单元组合，使得终端能够支持更高聚合等级，增加了PDCCH的覆盖能力，更大的带宽的CORESET还能够降低PDCCH的冲突概率，增加PDCCH传输可靠性。
一种实现方式中，终端确定M个频域单元上的CORESET的顺序，根据M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET，该级联CORESET用于接收PDCCH。
该方式中可以对M个频域单元上的CORESET进行跨频域单元级联，形成一个或者多个级联CORESET，每个级联CORESET包括一个或者多个CORESET，该级联CORESET的带宽通常大于未级联的CORESET，从而能够在更大的带宽上接收PDCCH。值得注意的是，如果一个频域单元配置有多个CORESET，网络可以指示终端对CORESET的子集进行级联，即一个频域单元上的CORESET可以部分参与级联，可以部分不参与级联，取决于网络的灵活配置。
在该实现方式中，网络不需要考虑终端的能力，即网络在为终端设备配置M个频域单元时不需要考虑终端的能力。
该实现方式中，当M小于P时，即只在P个频域单元中的M个频域单元上配置了CORESET的情况下，该级联CORESET上承载或者发送的PDCCH用于调度该P个频域单元的数据，或者，描述为该级联CORESET上承载或者发送的PDCCH中的控制信息用于控制该P个频域单元上的数据传输。由于只在P个频域单元中部分频域单元上配置CORESET，从而能够减少公共信令开销。
对于RRC连接建立之前，网络可以通过SIB消息中通知CORESET配置及CORESET级联配置，CORESET配置包括CORESET的频域资源，CORESET级联配置用于指示终端进行级联，CORESET级联配置中包括终端进行级联所需的信息，包括但不限于级联CORESET的标识，用于级联的CORESET的索引。
对于RRC连接建立之后，网络通过RRC消息中通知CORESET配置及CORESET级联配置。
可选地，如果网络对接收SIB信息的CORESET,例如CORESET 0进行配置，那么各频域单元的CORESET配置及CORESET级联配置需要根据MIB消息及预定义的规则确定。CORESET 0通常只需进行一个配置，对于所有终端是公共的。
另一种实现方式中，M个频域单元为终端支持的频段组合的频域单元，终端确定M个频域单元中的每个频域单元的CORESET用于接收PDCCH，该方式中不同频域单元上的CORESET可以级联，也可以不进行级联，相比于现有技术中每个频域单元上的CORESET独立接收PDCCH，终端可以同时使用能够进行频段组合的多个频域单元的CORESET接收PDCCH，相当于增加了CORESET的带宽。需要明确的是，本申请实施例中终端可以处于以下任意一个状态：空闲(idle)态、非激活(INACTIVATE)态或者RRC连接态。
该实现方式中，网络需要考虑终端的能力，即网络在为终端设备配置M个频域单元时需要考虑终端的能力。
其中，终端支持的频段组合的频域单元也可以描述为与终端的频段组合(bandcombination)能力相关的频域单元，频段组合也称为频段合并，频段组合能力用于指示终端同时支持的频段数量，一个终端可能同时支持一个或者多个频段，不同的终端的频段组合能力不同。终端支持的所有频段上的频域单元构成终端支持的频段组合的频域单元，例如，终端1支持频段A和频段C，则终端1支持的频段组合为频段A和频段C，终端1支持的频段组合的频域单元为终端1支持的频段A和频段C上的频域单元。
对于RRC连接建立之前，网络没有获得终端的能力信息，网络可以根据先验信息，例如该服务小区的各频域单元所在频段支持频段组合，在SIB中预先指示某一个频段组合能力对应的CORESET配置及CORESET级联配置。例如，该服务小区支持UE能力A，B，C等不同终端类型，网络可以针对至少一个终端能力进行CORESET配置及CORESET级联配置。
对于RRC连接建立之后，网络已经获得终端的能力信息，网络可以根据终端能力信息，根据不同终端支持的频段组合能力，在RRC消息中配置某一个终端类型对应的CORESET配置及CORESET级联配置。
可选地，如果网络对CORESET 0进行配置，那么各频域单元的CORESET配置及CORESET级联配置需要根据MIB消息及预定义的规则确定。CORESET 0的数量可能有多个，即等于网络指示的频段组合的频域单元的数量，对于支持频域单元合并的终端是公共的。
当M个频域单元为终端支持的频段组合的频域单元，且终端对不同频域单元上的CORESET级联的情况下，根据终端的频段组合能力可知终端通常只支持部分频段，即终端只支持部分频段上的频域单元，所以M通常小于P，当M小于P时，该级联CORESET上承载或者发送的PDCCH用于调度该M个频域单元的数据，或者，描述为该级联CORESET上承载或者发送的PDCCH中的控制信息用于控制该M个频域单元上的数据传输。不失一般性地，网络也可以配置Q个频域单元的CORESET，Q小于等于M，这Q个频域单元的CORESET或者这Q个频域单元级联形成的级联CORESET可以调度M个频域单元的数据。
本实施例中，终端根据终端能力获取M个频域单元组合的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P，获取M个频域单元组合上的CORESET的频域资源，根据M个频域单元组合的配置信息和CORESET的频域资源，确定用于接收PDCCH的至少一个CORESET。通过在终端的服务小区的部分频域单元上配置CORESET，可以匹配终端能力，减少公共信令开销，达到各上行UL/DL载波的负载平衡，可以通过对M个频域单元组合上的全部或者部分CORESET跨频域单元组合进行级联，得到用于接收PDCCH的CORESET，使得用于接收PDCCH的CORESET具有更大的带宽，降低了PDCCH冲突概率，增加了PDCCH覆盖能力及传输可靠性，增加网络灵活性。
实施例二
在实施例一的基础上，本申请实施例二提供一种控制信道的传输方法，实施例一中记载的实现方式均可应用于实施例二中，并可达到相同的技术效果。本实施例以终端对M个频域单元的CORESET进行级联为例进行说明。图7为本申请实施例二提供的控制信道的传输方法的流程图，如图7所示，本实施例提供的方法包括以下步骤。
S201、终端获取M个频域单元的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P。
一种实现方式中，该M个频域单元可以是终端的服务小区中的任意M个频域单元，即M个频域单元为与终端的频段组合能力不相关的频域单元。
另一种实现方式中，该M个频域单元为终端支持的频段组合的频域单元。
频段组合能力是载波聚合(Carrier Aggregation，CA)技术中引入的一个概念，频段组合能力用于指示终端同时支持的频段数量，一个终端可能同时支持一个或者多个频段，不同的终端的频段组合能力不同，例如，终端1只支持频段A和频段C，则终端1支持的频段组合为频段A和频段C，终端2只支持频段B和频段C，则终端2支持的频段组合为频段B和频段C，终端3只支持频段C，则终端3支持的频段组合为频段C。相应的，网络侧设备可以根据终端的频段组合能力为终端配置用于级联的频域单元，即网络侧设备只在终端支持的频段上的频域单元上配置CORESET，不在终端不支持的频段上配置频域单元和CORESET。对应的，终端设备只对自己支持的频段上的CORESET进行级联。
S202、终端获取M个频域单元上的CORESET的频域资源。
S203、终端确定M个频域单元上的CORESET的顺序。
第一种实现方式中，终端根据M个频域单元上CORESET的起始频率，对M个频域单元上CORESET进行升序或者降序排列，并根据预定义的级联规则或者按照网络指示进行级联。
第二种实现方式中，终端根据M个频域单元的起始频率，对M个频域单元上CORESET进行升序或者降序排列，并根据预定义的级联规则按照网络指示进行级联。
S204、终端根据M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET，该级联CORESET用于接收PDCCH。
当该M个频域单元是终端的服务小区中的任意M个频域单元，或者，该M个频域单元为终端支持的频段组合的频域单元时，都可以采用如下两种方式对M个频域单元的CORESET进行级联。
第一种实现方式中，终端根据M个频域单元上的CORESET的顺序，以及预定义的级联规则，级联形成至少一个级联CORESET。
该预定义的级联规则可以是网络侧设备发送给终端的，也可以是网络侧设备和终端预先约定好的。
示例性的，该预定义的级联规则可以为：将网络侧配置的所有CORESET级联形成一个级联CORESET。则终端根据该预定义的规则和M个频域单元上的CORESET的顺序，将M个频域单元上的CORESET级联形成一个级联CORESET。
由于级联CORESET内的CCE需要排序，因此，终端对M个频域单元上的CORESET进行排序，M个频域单元上的CORESET的顺序即可表示级联CORESET内的CCE的顺序。
图8为多个频域单元的CORESET的一种级联示意图，参考图8，图8以频域单元为BWP为例，终端的服务小区配置了三个BWP：BWP i、BWP j和BWP k，BWP i位于频段A的载波p上，BWP j位于频段B的载波q上，BWP k位于频段C的载波m上，每个BWP上配置了一个CORESET，终端对三个BWP的CORESET进行排序后级联形成一个级联CORESETm，该级联CORESETm内的CCE编号为0-5，级联CORESETm内的CCE编号的顺序与三个BWP的起始频率顺序，或者三个BWP内的CORESET的起始频率顺序对应。
图9为多个频域单元的CORESET的另一种级联示意图，图9与图8的区别为：图9中没有为BWPi配置CORESET，即网络侧设备只对终端的服务小区配置的BWP中的部分BWP配置了CORESET，而不是对所有BWP配置了CORESET。图9中级联CORESETm内的CCE编号为0-4。
示例性的，该预定义的级联规则还可以为：从每个频域单元中选择一个CORESET序号相同的CORESET级联形成一个级联CORESET。
参考图10，图10为多个频域单元的CORESET的另一种级联示意图，该方式中，终端先按照三个BWP的起始频率对三个BWP进行排序，在进行级联时，根据CORESET序号从小到大或者从大到小，每次从三个BWP中选择一个序号相同的CORESET进行级联形成一个级联CORESET。
例如，先对CORESET序号1进行级联，则终端分别从BWP i、BWP j和BWP k中选择序号为1的CORESET：CORESETi_1，CORESETj_1和CORESET k_1，CORESETi_1，CORESETj_1和CORESET k_1级联形成级联CORESET A。然后，终端分别从BWP i、BWP j和BWP k中选择序号为2的CORESET：CORESETj_2和CORESET k_2，CORESETj_2和CORESET k_2级联形成级联CORESET B，该过程中BWP i中没有序号为2的CORESET，所以不用级联BWPi的CORESET。最后，终端分别从BWP i、BWP j和BWP k中选择序号为3的CORESET：CORESET k_3，CORESET k_3级联形成级联CORESET C，该过程中BWP i和BWP j中没有序号为3的CORESET。所以级联CORESET C就是CORESET k_3，此时，相当于不级联。
第二种实现方式中，终端根据M个频域单元上的CORESET的顺序，以及网络侧设备发送的级联指示信息，级联形成至少一个级联CORESET，该级联指示信息包括级联CORESET的标识和M个频域单元中参与级联的CORESET的索引。
可选的，网络侧设备可以将该级联指示信息和M个频域单元的配置信息一起发送给终端，也可以通过不同的消息将该级联指示信息和M个频域单元的配置信息分别发送给终端。
以图8和9所示级联示意图为例，该级联指示信息中包括一个级联CORESET标识：级联CORESET m，以及参与级联的各CORESET的索引。
以图10所示级联示意图为例，该级联指示信息中包括三个级联CORESET标识：级联CORESET A、级联CORESET B和级联CORESET C，以及每个级联CORESET标识对应的参与级联的CORESET的索引，示例性的，级联CORESET A对应的参与级联的CORESET的索引为：CORESETi_1，CORESETj_1和CORESET k_1。
当该M个频域单元为终端支持的频段组合的频域单元时，终端在级联之前，需要通知网络侧自己支持的频段，进而根据自己支持的频段，在自己支持的频段上的频域单元进行发送或接收。或者，网络侧根据候选终端能力等级，直接通知至少一个能力等级的终端对应的配置。一种方式中，终端可以根据自己的频段组合能力确定自己支持的频段，例如RRC连接建立之前。另一种方式中，网络侧设备向终端指示终端支持的频段对应的配置，例如RRC连接建立之后。
后一种方式中，网络侧设备可以将频段组合信息携带在级联指示信息中，该频段组合信息用于指示将与终端的频段组合能力相关的频域单元的频段组合，示例性的，该频段组合信息中包括一个组合标识，该组合标识用于指示将终端支持的频段进行组合，可选的，频段组合信息中还包括组合的频段的标识，例如，终端支持频段A和频段C，则该频段组合信息中还包括频段A和频段C的标识或者频率信息。
图11为多个终端的频域单元的CORESET的级联示意图，参考图11，终端1只支持频段A和频段C，终端2只支持频段B和频段C，终端3只支持频段C，则网络侧设备根据各终端的频段组合能力，为终端1配置频段A的CORESETi1和频段C的CORESET k1，为终端2配置频段B的CORESET j1和频段C的CORESET k2，为终端3配置频段C的CORESET k3。
终端1通过网络侧的配置参数能够看到频段A的CORESET i和频段C的CORESET k1，可以将CORESET i和CORESET k1级联成一个级联CORESET m，终端1在级联CORESET m接收PDCCH。终端2通过网络侧的配置参数能够看到频段B的CORESET j1和频段C的CORESET k2，可以将CORESET j1和CORESET k2级联成一个级联CORESET n，终端2在级联CORESET n接收PDCCH。终端3通过网络侧的配置参数能够看到频段C上的CORESET k3，终端3在(级联)CORESET n k3上接收PDCCH。
可选的，M个频域单元中的任意一个频域单元用于发送下行控制信息，以提高灵活性。示例性的，图8-图11所示频段上，网络侧设备只在频段C的频域单元上发送SSB。终端可以在任何频域单元的CORESET上接收PDCCH，此时，多个频域单元的CORESET可以不级联。
可选的，终端不期望级联CORESET的以下配置参数中的至少一个不同：
起始符号；
持续符号数；
CCE到REG的映射类型；
准共址关系(Quasi-Colocation，QCL)；
传输配置指示(Transmission Configuration Indication，TCI)域存在的指示；
PDCCH-DMRS的扰码标识(ScramblingID)；
关联的搜索空间类型；
SCS；
CP。
终端不期望级联CORESET的以下配置参数中的至少一个不同，可以理解为UE期望级联CORESET的以下配置参数中的至少一个相同。
CCE到REG的映射类型为交织类型或者非交织类型，当级联CORESET内采用的CCE到REG的映射类型为交织类型时，能够提供分集增益，增强PDCCH传输可靠性。
TCI域存在的指示用于指示DCI中是否存在TCL字段。
网络测可以对级联CORESET配置搜索空间，级联CORESET关联的搜索空间类型可以为公共搜索空间或者专用搜索空间。
一个级联CORESET中可能包括一个或者多个CORESET，级联CORESET关联的搜索空间是指级联CORESET包括的各CORESET的搜索空间。其中，级联CORESET包括的各CORESET的搜索空间可以相同或者不同。当级联CORESET关联的搜索空间不同时，级联CORESET关联的搜索空间应该满足预定义的要求，例如，基于时隙或span监测PDCCH能力相关的要求。
本实施例的方法可用于RRC连接建立之前或RRC连接建立之后。在RRC连接建立之前，CORESET配置信息可以通过SIB通知，在RRC连接建立之前，网络侧设备可能无法获取终端的能力，所以网络侧设备需要根据频域单元支持的终端能力的先验信息，对频域单元上的CORESET进行配置及级联配置。
而在RRC连接建立之后，CORESET配置信息可以通过RRC消息通知，此时，网络侧设备已经获得终端能力，可以在一个频域单元上配置一个或者多个CORESET，所以网络侧设备可以根据终端的能力配置与终端的频段组合能力相关的频域单元。
本实施例中，终端获取M个频域单元的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P，终端获取M个频域单元上的CORESET的频域资源，确定M个频域单元上的CORESET的顺序，根据M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET，该级联CORESET用于接收PDCCH。通过在终端的服务小区的全部或者部分频域单元上配置CORESET，并对配置的CORESET跨频段单元进行级联形成级联CORESET，在级联CORESET上接收PDCCH，级联CORESET具有更大的带宽，降低了PDCCH冲突概率，增加了PDCCH覆盖能力及传输可靠性，增加网络灵活性。
实施例三
本申请实施例三提供一种控制信道的传输方法，实施例一和实施例二中记载的实现方式均可应用于实施例三中，并可达到相同的技术效果。图12为本申请实施例三提供的控制信道的传输方法的流程图，如图12所示，本实施例提供的方法包括以下步骤。
S301、终端获取M个频域单元的配置信息，其中，M个频域单元为终端支持的频段组合的频域单元，M小于或等于终端的服务小区配置的频域单元的数量P。
S302、终端获取M个频域单元上的CORESET的频域资源。
S303、终端确定M个频域单元中的每个频域单元的CORESET作为独立的CORESET用于接收PDCCH。
不同于实施例二中的方案，本实施例中，对于终端支持的频段组合的M个频域单元上的CORESET不进行级联，而是将终端支持的频段组合的M个频域单元上的CORESET作为独立的CORESET，终端可以同时使用该M个频域单元上的CORESET接收PDCCH，相当于增大了用于接收PDCCH的CORESET的频域范围，从而增加了及传输可靠性，增加网络灵活性，进一步地，可以降低了PDCCH冲突概率，改进PDCCH覆盖能力。
参考图13，图13为终端的频域单元的CORESET的一种示意图，假设终端的频段组合能力为：终端1只支持频段A和频段C，终端2只支持频段B和频段C，终端3只支持频段C。那么，终端1确定的用于接收PDCCH的CORESET为频段A上的CORESETi1和频段C上的CORESETk1，终端2确定的用于接收PDCCH的CORESET为频段B上的CORESET j1和频段C上的CORESETk1，终端3确定的用于接收PDCCH的CORESET为频段C上的CORESETk1。
图13以每个频段上只有一个CORESET为例，当然，每个频段上可以有多个CORESET，当终端支持的频段上有多个CORESET时，终端可以根据预定义的规则选择该多个CORESET中的全部或者部分用于接收PDCCH，或者根据网络侧设备的指示确定该多个CORESET中的全部或者部分用于接收PDCCH，例如，网络侧设备可以指示用于接收PDCCH的CORESET的索引。
可选的，终端支持的频段组合的频域单元中任何一个频域单元上的CORESET数不大于终端支持的最大CORESET数，即终端不期望任何一个频域单元上的CORESET数大于终端支持的CORESET数能力，终端支持的CORESET数能力即终端支持的最大CORESET数。可以理解，不同类型频域单元上终端支持的最大CORESET数可能不同，以BWP为例，BWP上最多配置3个CORESET，则终端支持的最大CORESET数为3。
本实施例中，终端获取M个频域单元的配置信息，其中，M个频域单元为终端支持的频段组合的频域单元，M小于或等于终端的服务小区配置的频域单元的数量P，获取M个频域单元上的CORESET的频域资源，确定M个频域单元中的每个频域单元的CORESET作为独立的CORESET用于接收PDCCH。该实施例中终端可以同时使用该M个频域单元上的CORESET接收PDCCH，相当于增大了用于接收PDCCH的CORESET的频域范围，从而增加了及传输可靠性，增加网络灵活性，进一步地，可以降低了PDCCH冲突概率，改进PDCCH覆盖能力。
实施例四
本申请实施例四提供一种控制信道的传输方法，由网络侧设备执行，图14为本申请实施例四提供的控制信道的传输方法的流程图，如图14所示，本实施例提供的方法包括以下步骤。
S401、网络侧设备向终端发送M个频域单元的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P。
该M个频域单元的配置信息包括以下至少之一：
M个频域单元的频率参考点；
M个频域单元中的每个频域单元相对于所述频率参考点的频率偏移值；
M个频域单元中的每个频域单元的SCS；
M个频域单元中的每个频域单元的CP；
M个频域单元中的每个频域单元的起始RB和大小；
M个频域单元中每个频域单元的索引。
M的取值小于或者等于P，即网络侧设备可以只在服务小区的部分频域单元上配置CORESET，使得CORESET的配置更加灵活。该M个频域单元可以是终端的服务小区中的任意M个频域单元，也可以为终端支持的频段组合的频域单元。
S402、网络侧设备向终端发送M个频域单元上的CORESET的频域资源。
可选的，网络侧设备可以通过同一个消息向终端发送M个频域单元的配置信息和CORESET的频域资源，也可以通过不同的消息向终端发送M个频域单元的配置信息和CORESET的频域资源。
一个频域单元上可以配置一个或者多个CORESET，一个频域单元内的多个CORESET频域资源或者时域资源可以重叠。
S403、网络侧设备根据M个频域单元的配置信息和CORESET的频域资源，在至少一个CORESET上发送PDCCH。
网络侧设备通过将M个频域单元的配置信息和CORESET的频域资源发送给终端，使得终端对M个频域单元上的全部或者部分CORESET跨频域单元进行组合，确定用于接收PDCCH的CORESET，同样，网络侧设备也需要根据M个频域单元的配置信息和CORESET的频域资源，对M个频域单元上的全部或者部分CORESET跨频域单元进行组合，确定用于发送PDCCH的至少一个CORESET。
一种实现方式中，网络侧设备确定M个频域单元上的CORESET的顺序，根据M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET，网络侧设备在级联CORESET上发送PDCCH。
网络侧设备对M个频域单元上的CORESET的排序方法参照前述实施例中终端的排序方法，这里不再赘述。
网络侧设备可以根据M个频域单元上的CORESET的顺序，以及预定义的级联规则，级联形成至少一个级联CORESET，该预定义的规则可以由网络侧设备和终端协商好，或者，由网络侧设备确定并发送给终端，后续网络侧设备和终端都根据该预定义的级联规则对M个频域单元上的CORESET进行级联。
或者，网络侧设备根据一些信息确定形成几个级联CORESET以及M个频域单元中参与级联的CORESET，网络侧设备生成级联指示信息，该级联指示信息包括级联CORESET的标识和M个频域单元中参与级联的CORESET的索引。终端侧设备可以根据该级联指示信息对M个频域单元上的CORESET进行级联，并将该级联指示信息发送给终端，以使得终端根据该级联指示信息进行级联。
当该M个频域单元为终端支持的频段组合的频域单元时，可选的，网络侧设备可以对M个频域单元上的CORESET进行级联，网络侧设备级联使用的具体方法参照前述实施例中终端级联使用的方法，这里不再赘述。可选的，该级联指示信息中还包括频段组合信息，该频段组合信息用于指示将与终端的频段组合能力相关的频域单元的频段组合。当M个频域单元为终端支持的频段组合的频域单元，可选的，网络侧设备对M个频域单元上的CORESET可以不级联，即网络侧设备可以确定M个频域单元中的每个频域单元的CORESET作为独立的CORESET用于发送PDCCH，相应的，网络侧设备在M个频域单元的CORESET上向终端发送PDCCH。该方式中，网络侧设备只在终端支持的频段组合的频域单元上发送PDCCH。
可选的，网络侧设备在M个频域单元中的部分频域单元上发送下行控制信息，例如，网络侧设备只在M个频域单元中的任意一个频域单元上发送下行控制信息。
本实施例中，网络侧设备向终端发送M个频域单元的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P，向终端发送M个频域单元上的CORESET的频域资源，根据M个频域单元的配置信息和CORESET的频域资源，在至少一个CORESET上发送PDCCH。网络侧设备通过在终端的服务小区的部分频域单元上配置CORESET，可以减少公共信令开销，达到各上行UL/DL载波的负载平衡，网络侧设备对M个频域单元上的全部或者部分CORESET跨频域单元进行组合，得到用于发送PDCCH的CORESET，使得用于发送PDCCH的CORESET具有更大的带宽，降低了PDCCH冲突概率，增加了PDCCH覆盖能力及传输可靠性，增加网络灵活性。
实施例五
在上述实施例的基础上，本申请实施例五提供一种控制信道的传输方法，本实施例用于描述控制信道的传输过程中终端和网络侧设备之间的信令交互，图15为本申请实施例五提供的一种控制信道的传输方法的信令流程图。如图15所示，本实施例提供的方法包括以下步骤。
S501、网络侧设备向终端发送M个频域单元的配置信息。
其中，M小于或等于终端的服务小区配置的频域单元的数量P。
S502、网络侧设备向终端发送M个频域单元上的CORESET的频域资源。
S503、网络侧设备根据M个频域单元的配置信息和CORESET的频域资源，确定用于发送PDCCH的至少一个CORESET。
S504、终端设备根据M个频域单元的配置信息和CORESET的频域资源，确定用于接收PDCCH的至少一个CORESET。
其中，步骤S503和S504在执行时并没有先后顺序，也可以同时执行。
S505、网络侧设备在确定的至少一个CORESET上发送PDCCH。
S506、终端在确定的至少一个CORESET上接收PDCCH。
本实施例的具体实现方式参照前述实施例的描述，这里不再赘述。
实施例六
本申请实施例提供的控制信道的传输方法，执行主体可以为控制信道的传输装置。本申请实施例中以控制信道的传输装置执行控制信道的传输的方法为例，说明本申请实施例提供的控制信道的传输装置。
图16为本申请实施例六提供的一种控制信道的传输装置的结构示意图，所述装置可以应用在终端中，如图16所示，本实施例提供的控制信道的传输装置100包括以下模块。
获取模块11，用于获取M个频域单元的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P；
所述获取模块11，还用于获取所述M个频域单元上的CORESET的频域资源；
确定模块12，用于根据所述M个频域单元的配置信息和CORESET的频域资源，确定用于接收PDCCH的至少一个CORESET。
在一种可选实现方式中，所述确定模块12具体用于：
确定所述M个频域单元上的CORESET的顺序；
根据所述M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET，所述级联CORESET用于接收所述PDCCH。
在一种可选实现方式中，所述确定模块12具体用于：
根据所述M个频域单元上CORESET的起始频率或者所述M个频域单元的起始频率，对所述M个频域单元上CORESET进行升序或者降序排列。
在另一种可选实现方式中，所述确定模块12具体用于：
根据所述M个频域单元的起始频率，对所述M个频域单元进行升序或者降序排列。
在一种可选实现方式中，所述确定模块12具体用于：
根据所述M个频域单元上的CORESET的顺序，以及预定义的级联规则，级联形成至少一个级联CORESET。
在另一种可选实现方式中，所述确定模块具体用于：
根据所述M个频域单元上的CORESET的顺序，以及网络侧设备发送的级联指示信息，级联形成至少一个级联CORESET，所述级联指示信息包括级联CORESET的标识和所述M个频域单元中参与级联的CORESET的索引。
在一种可选实现方式中，所述M个频域单元为所述终端支持的频段组合的频域单元。
在一种可选实现方式中，所述M个频域单元为所述终端支持的频段组合的频域单元；
所述级联指示信息中还包括频段组合信息，所述频段组合信息用于指示将与所述终端的频段组合能力相关的频域单元的频段组合。
在一种可选实现方式中，所述终端不期望所述级联CORESET的以下配置参数中的至少一个不同：
起始符号；
持续符号数；
CCE到REG的映射类型；
QCL；
TCI域存在的指示；
PDCCH-DMRS-ScramblingID；
关联的搜索空间类型；
SCS；
CP。
在一种可选实现方式中，所述级联CORESET内采用的CCE到REG的映射类型为交织类型。
在一种可选实现方式中，所述级联CORESET中包括的各CORESET的搜索空间相同或者不同。
在一种可选实现方式中，所述M个频域单元为所述终端支持的频段组合的频域单元；
所述确定模块12具体用于：确定所述M个频域单元中的每个频域单元的CORESET作为独立的CORESET用于接收PDCCH。
在一种可选实现方式中，所述终端支持的频段组合的频域单元中的任意一个频域单元上的CORESET数不大于所述终端支持的最大CORESET数。
在一种可选实现方式中，所述M个频域单元的配置信息包括以下至少之一：
所述M个频域单元的频率参考点；
所述M个频域单元中的每个频域单元相对于所述频率参考点的频率偏移值；
所述M个频域单元中的每个频域单元的SCS；
所述M个频域单元中的每个频域单元的CP；
所述M个频域单元中的每个频域单元的起始资源块RB和大小；
所述M个频域单元中每个频域单元的索引。
在一种可选实现方式中，所述M个频域单元的频率参考点包括以下至少之一：
所述M个频域单元中没有关联CD-SSB的频域单元的频率参考点；
所述M个频域单元中没有关联CD-SSB的频域单元一个公共频率参考点；
所述M个频域单元中的每个频域单元的频率参考点；
所述M个频域单元的一个公共频率参考点。
在一种可选实现方式中，所述M个频域单元中的任意一个频域单元用于发送下行控制信息。
在一种可选实现方式中，所述M个频域单元包括以下单元中的至少一个：BWP、载波或者频段。
网络侧设备通过在终端的服务小区的部分频域单元上配置CORESET，可以减少公共信令开销，达到各上行UL/DL载波的负载平衡，终端通过对M个频域单元上的全部或者部分CORESET跨频域单元进行组合，得到用于接收PDCCH的CORESET，使得用于接收PDCCH的CORESET具有更大的带宽，降低了PDCCH冲突概率，增加了PDCCH覆盖能力及传输可靠性，增加网络灵活性。
实施例七
本申请实施例七提供一种控制信道的传输装置，所述控制信道的传输装置可以应用在网络侧设备中，图17为本申请实施例七提供的一种控制信道的传输装置的结构示意图，如图17所示，本实施例提供的控制信道的传输装置200包括以下模块。
发送模块21，用于向终端发送M个频域单元的配置信息，M小于或等于所述终端的服务小区配置的频域单元的数量P；
所述发送模块21，用于向所述终端发送所述M个频域单元上的CORESET的频域资源；
处理模块22，用于根据所述M个频域单元的配置信息和CORESET的频域资源，在至少一个CORESET上发送PDCCH。
在一种可选实现方式中，所述处理模块22具体用于：
确定所述M个频域单元上的CORESET的顺序；
根据所述M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET；
在所述级联CORESET上发送所述PDCCH。
在一种可选实现方式中，所述M个频域单元为所述终端支持的频段组合的频域单元。
在一种可选实现方式中，所述发送模块21还用于：
向所述终端发送级联指示信息，所述级联指示信息包括级联CORESET的标识和所述M个频域单元中参与级联的CORESET的索引。
在一种可选实现方式中，当所述M个频域单元为所述终端支持的频段组合的频域单元时，所述级联指示信息中还包括频段组合信息，所述频段组合信息用于指示将与所述终端的频段组合能力相关的频域单元的频段组合。
在一种可选实现方式中，所述M个频域单元为所述终端支持的频段组合的频域单元；
所述处理模块22具体用于：
确定所述M个频域单元中的每个频域单元的CORESET作为独立的CORESET用于发送PDCCH；
在所述M个频域单元的CORESET上向所述终端发送所述PDCCH。
网络侧设备通过在终端的服务小区的部分频域单元上配置CORESET，可以减少公共信令开销，达到各上行UL/DL载波的负载平衡，网络侧设备对M个频域单元上的全部或者部分CORESET跨频域单元进行组合，得到用于发送PDCCH的CORESET，使得用于发送PDCCH的CORESET具有更大的带宽，降低了PDCCH冲突概率，增加了PDCCH覆盖能力及传输可靠性，增加网络灵活性。
本申请实施例中的控制信道的传输装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的控制信道的传输装置能够实现图2至图15的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
如图18所示，本申请实施例还提供一种通信设备300，包括处理器31和存储器32，存储器32上存储有可在所述处理器31上运行的程序或指令，例如，该通信设备300为终端时，该程序或指令被处理器31执行时实现上述图2-图13方法实施例的各个步骤，且能达到相同的技术效果。该通信设备300为网络侧设备时，该程序或指令被处理器31执行时实现上述图14方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如图2-图13所示方法实施例中的步骤。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图19为实现本申请实施例的一种终端的硬件结构示意图。
该终端400包括但不限于：射频单元41、网络模块42、音频输出单元43、输入单元44、传感器45、显示单元46、用户输入单元47、接口单元48、存储器49以及处理器410等中的至少部分部件。
本领域技术人员可以理解，终端400还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器x 10逻辑相连，从而通过电源管理系统实现管理充电、放电以及功耗管理等功能。图19中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元44可以包括图形处理单元(Graphics Processing Unit，GPU)441和麦克风442，图形处理器441对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元46可包括显示面板461，可以采用液晶显示器、有机发光二极管等形式来配置显示面板461。用户输入单元47包括触控面板471以及其他输入设备472中的至少一种。触控面板471，也称为触摸屏。触控面板471可包括触摸检测装置和触摸控制器两个部分。其他输入设备472可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元41接收来自网络侧设备的下行数据后，可以传输给处理器410进行处理；另外，射频单元41可以向网络侧设备发送上行数据。通常，射频单元41包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器49可用于存储软件程序或指令以及各种数据。存储器49可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器49可以包括易失性存储器或非易失性存储器。其中，非易失性存储器可以是只读存储器(Read-OnlyMemory，ROM)、可编程只读存储器(ProgrammableROM，PROM)、可擦除可编程只读存储器(ErasablePROM，EPROM)、电可擦除可编程只读存储器(ElectricallyEPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器49包括但不限于这些和任意其它适合类型的存储器。
处理器410可包括一个或多个处理单元；可选的，处理器410集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器410中。
其中，处理器410，用于获取M个频域单元的配置信息，M小于或等于所述终端的服务小区配置的频域单元的数量P；获取所述M个频域单元上的控制资源集CORESET的频域资源；根据所述M个频域单元的配置信息和CORESET的频域资源，确定用于接收PDCCH的至少一个CORESET。
通过在终端的服务小区的部分频域单元上配置CORESET，可以减少公共信令开销，达到各上行UL/DL载波的负载平衡，通过对M个频域单元上的全部或者部分CORESET跨频域单元进行组合，得到用于接收PDCCH的CORESET，使得用于接收PDCCH的CORESET具有更大的带宽，降低了PDCCH冲突概率，增加了PDCCH覆盖能力及传输可靠性，增加网络灵活性。
可以理解，本实施例中提及的各实现方式的实现过程可以参照方法实施例图2-图13的相关描述，并达到相同或相应的技术效果，为避免重复，在此不再赘述。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如图14所示的方法实施例的步骤。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图20所示，该网络侧设备500包括：天线51、射频装置52、基带装置53、处理器54和存储器55。天线51与射频装置52连接。在上行方向上，射频装置52通过天线51接收信息，将接收的信息发送给基带装置53进行处理。在下行方向上，基带装置53对要发送的信息进行处理，并发送给射频装置52，射频装置52对收到的信息进行处理后经过天线51发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置53中实现，该基带装置53包括基带处理器。
基带装置53例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图20所示，其中一个芯片例如为基带处理器，通过总线接口与存储器55连接，以调用存储器55中的程序，执行以上方法实施例中所示的网络侧设备操作。
该网络侧设备还可以包括网络接口56，该接口例如为通用公共无线接口(Common Public Radio Interface，CPRI)。
具体地，本申请实施例的网络侧设备500还包括：存储在存储器55上并可在处理器54上运行的指令或程序，处理器54调用存储器55中的指令或程序执行图17所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述图2-图14所示方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。在一些示例中，可读存储介质可以是非瞬态的可读存储介质。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述图2-图14所示方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述控制信道的传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种通信系统，包括：终端及网络侧设备，所述终端可用于执行如上所述的图2-图13所示方法的步骤，所述网络侧设备可用于执行如上所述的图14所示方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助计算机软件产品加必需的通用硬件平台的方式来实现，当然也可以通过硬件。该计算机软件产品存储在存储介质(如ROM、RAM、磁碟、光盘等)中，包括若干指令，用以使得终端或者网络侧设备执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式的实施方式，这些实施方式均属于本申请的保护之内。

Claims (30)

  1. 一种控制信道的传输方法，其中，包括：
    终端获取M个频域单元的配置信息，M小于或等于所述终端的服务小区配置的频域单元的数量P；
    所述终端获取所述M个频域单元上的控制资源集CORESET的频域资源；
    所述终端根据所述M个频域单元的配置信息和CORESET的频域资源，确定用于接收物理下行控制信道PDCCH的至少一个CORESET。
  2. 根据权利要求1所述的方法，其中，所述终端根据所述M个频域单元的配置信息和CORESET的频域资源，确定用于接收物理下行公共控制信道PDCCH的至少一个CORESET，包括：
    所述终端确定所述M个频域单元上的CORESET的顺序；
    所述终端根据所述M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET，所述级联CORESET用于接收所述PDCCH。
  3. 根据权利要求2所述的方法，其中，所述终端确定所述M个频域单元上的CORESET的顺序，包括：
    所述终端根据所述M个频域单元上CORESET的起始频率或者所述M个频域单元的起始频率，对所述M个频域单元上CORESET进行升序或者降序排列。
  4. 根据权利要求2或3所述的方法，其中，所述终端根据所述M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET包括：
    所述终端根据所述M个频域单元上的CORESET的顺序，以及预定义的级联规则或者网络侧设备发送的级联指示信息，级联形成至少一个级联CORESET，所述级联指示信息包括级联CORESET的标识和所述M个频域单元中参与级联的CORESET的索引。
  5. 根据权利要求2-4任一项所述的方法，其中，所述M个频域单元为所述终端支持的频段组合的频域单元。
  6. 根据权利要求4所述的方法，其中，所述M个频域单元为所述终端支持的频段组合的频域单元；
    所述级联指示信息中还包括频段组合信息，所述频段组合信息用于指示将与所述终端的频段组合能力相关的频域单元的频段组合。
  7. 根据权利要求2-6任一项所述的方法，其中，所述终端不期望所述级联CORESET的以下配置参数中的至少一个不同：
    起始符号；
    持续符号数；
    控制信道元素CCE到资源元素组REG的映射类型；
    准共址关系QCL；
    传输配置指示TCI域存在的指示；
    PDCCH-DMRS-ScramblingID；
    关联的搜索空间类型；
    子载波间隔SCS；
    循环前缀CP。
  8. 根据权利要求1所述的方法，其中，所述M个频域单元为所述终端支持的频段组合的频域单元；
    所述终端根据所述M个频域单元的配置信息和CORESET的频域资源，确定用于接收物理下行控制信道PDCCH的至少一个CORESET，包括：
    所述终端确定所述M个频域单元中的每个频域单元的CORESET作为独立的CORESET用于接收PDCCH。
  9. 根据权利要求1-8任一项所述的方法，其中，所述M个频域单元的配置信息包括以下至少之一：
    所述M个频域单元的频率参考点；
    所述M个频域单元中的每个频域单元相对于所述频率参考点的频率偏移值；
    所述M个频域单元中的每个频域单元的SCS；
    所述M个频域单元中的每个频域单元的CP；
    所述M个频域单元中的每个频域单元的起始资源块RB和大小；
    所述M个频域单元中每个频域单元的索引。
  10. 一种控制信道的传输方法，其中，包括：
    网络侧设备向终端发送M个频域单元的配置信息，M小于或等于所述终端的服务小区配置的频域单元的数量P；
    所述网络侧设备向所述终端发送所述M个频域单元上的控制资源集CORESET的频域资源；
    所述网络侧设备根据所述M个频域单元的配置信息和CORESET的频域资源，在至少一个CORESET上发送物理下行控制信道PDCCH。
  11. 根据权利要求10所述的方法，其中，所述网络侧设备根据所述M个频域单元的配置信息和CORESET的频域资源，在至少一个CORESET上发送下行控制信道PDCCH，包括：
    所述网络侧设备确定所述M个频域单元上的CORESET的顺序；
    所述网络侧设备根据所述M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET；
    所述网络侧设备在所述级联CORESET上发送所述PDCCH。
  12. 根据权利要求11所述的方法，其中，所述M个频域单元为所述终端支持的频段组合的频域单元。
  13. 根据权利要求11或12所述的方法，其中，还包括：
    所述网络侧设备向所述终端发送级联指示信息，所述级联指示信息包括级联CORESET的标识和所述M个频域单元中参与级联的CORESET的索引。
  14. 根据权利要求13所述的方法，其中，当所述M个频域单元为所述终端支持的频段组合的频域单元时，所述级联指示信息中还包括频段组合信息，所述频段组合信息用于指示将与所述终端的频段组合能力相关的频域单元的频段组合。
  15. 根据权利要求10所述的方法，其中，所述M个频域单元为所述终端支持的频段组合的频域单元；
    所述网络侧设备根据所述M个频域单元的配置信息和CORESET的频域资源，在至少一个CORESET上发送下行控制信道PDCCH，包括：
    所述网络侧设备确定所述M个频域单元中的每个频域单元的CORESET作为独立的CORESET用于发送PDCCH；
    所述网络侧设备在所述M个频域单元的CORESET上向所述终端发送所述PDCCH。
  16. 一种控制信道的传输装置，其中，包括：
    获取模块，用于获取M个频域单元的配置信息，M小于或等于终端的服务小区配置的频域单元的数量P；
    所述获取模块，还用于获取所述M个频域单元上的控制资源集CORESET的频域资源；
    确定模块，用于根据所述M个频域单元的配置信息和CORESET的频域资源，确定用于接收物理下行控制信道PDCCH的至少一个CORESET。
  17. 根据权利要求16所述的装置，其中，所述确定模块具体用于：
    确定所述M个频域单元上的CORESET的顺序；
    根据所述M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET，所述级联CORESET用于接收所述PDCCH。
  18. 根据权利要求17所述的装置，其中，所述确定模块具体用于：
    根据所述M个频域单元上CORESET的起始频率或者所述M个频域单元的起始频率，对所述M个频域单元上CORESET进行升序或者降序排列。
  19. 根据权利要求17或18所述的装置，其中，所述确定模块具体用于：
    根据所述M个频域单元上的CORESET的顺序，以及预定义的级联规则或者网络侧设备发送的级联指示信息，级联形成至少一个级联CORESET，所述级联指示信息包括级联CORESET的标识和所述M个频域单元中参与级联的CORESET的索引。
  20. 根据权利要求17-19任一项所述的装置，其中，所述M个频域单元为所述终端支持的频段组合的频域单元。
  21. 根据权利要求17-20任一项所述的装置，其中，所述终端不期望所述级联CORESET的以下配置参数中的至少一个不同：
    起始符号；
    持续符号数；
    控制信道元素CCE到资源元素组REG的映射类型；
    准共址关系QCL；
    传输配置指示TCI域存在的指示；
    PDCCH-DMRS-ScramblingID；
    关联的搜索空间类型；
    子载波间隔SCS；
    循环前缀CP。
  22. 根据权利要求17所述的装置，其中，所述M个频域单元为所述终端支持的频段组合的频域单元；
    所述确定模块具体用于：
    确定所述M个频域单元中的每个频域单元的CORESET作为独立的CORESET用于接收PDCCH。
  23. 一种控制信道的传输装置，其中，包括：
    发送模块，用于向终端发送M个频域单元的配置信息，M小于或等于所述终端的服务小区配置的频域单元的数量P；
    所述发送模块，用于向所述终端发送所述M个频域单元上的控制资源集CORESET的频域资源；
    处理模块，用于根据所述M个频域单元的配置信息和CORESET的频域资源，在至少一个CORESET上发送物理下行控制信道PDCCH。
  24. 根据权利要求23所述的装置，其中，所述处理模块具体用于：
    确定所述M个频域单元上的CORESET的顺序；
    根据所述M个频域单元上的CORESET的顺序，级联形成至少一个级联CORESET；
    在所述级联CORESET上发送所述PDCCH。
  25. 根据权利要求24所述的装置，其中，所述M个频域单元为所述终端支持的频段组合的频域单元。
  26. 根据权利要求24或25所述的装置，其中，所述发送模块还用于：
    向所述终端发送级联指示信息，所述级联指示信息包括级联CORESET的标识和所述M个频域单元中参与级联的CORESET的索引。
  27. 根据权利要求23所述的装置，其中，所述M个频域单元为所述终端支持的频段组合的频域单元；
    所述处理模块具体用于：
    确定所述M个频域单元中的每个频域单元的CORESET作为独立的CORESET用于发送PDCCH；
    在所述M个频域单元的CORESET上向所述终端发送所述PDCCH。
  28. 一种终端，其中，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至9任一项所述的控制信道的传输方法的步骤。
  29. 一种网络侧设备，其中，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求10至15任一项所述的控制信道的传输方法的步骤。
  30. 一种可读存储介质，其中，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1-9任一项所述的控制信道的传输方法，或者实现如权利要求10至15任一项所述的控制信道的传输方法的步骤。
PCT/CN2024/137572 2023-12-08 2024-12-06 控制信道的传输方法、装置、设备及存储介质 Pending WO2025119359A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202311691178.0A CN120129063A (zh) 2023-12-08 2023-12-08 控制信道的传输方法、装置、设备及存储介质
CN202311691178.0 2023-12-08

Publications (1)

Publication Number Publication Date
WO2025119359A1 true WO2025119359A1 (zh) 2025-06-12

Family

ID=95923962

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/137572 Pending WO2025119359A1 (zh) 2023-12-08 2024-12-06 控制信道的传输方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN120129063A (zh)
WO (1) WO2025119359A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110741705A (zh) * 2017-06-08 2020-01-31 Lg电子株式会社 无线通信系统中由终端执行的下行链路控制信道接收方法以及使用该方法的终端
CN110798866A (zh) * 2018-08-01 2020-02-14 展讯通信（上海）有限公司 下行控制信道资源的确定、获取方法及装置、基站、终端
WO2023131238A1 (zh) * 2022-01-06 2023-07-13 维沃移动通信有限公司 Pdcch资源确定方法、终端及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110741705A (zh) * 2017-06-08 2020-01-31 Lg电子株式会社 无线通信系统中由终端执行的下行链路控制信道接收方法以及使用该方法的终端
CN110798866A (zh) * 2018-08-01 2020-02-14 展讯通信（上海）有限公司 下行控制信道资源的确定、获取方法及装置、基站、终端
WO2023131238A1 (zh) * 2022-01-06 2023-07-13 维沃移动通信有限公司 Pdcch资源确定方法、终端及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Sub-band non-overlapping full duplex", 3GPP DRAFT; R1-2302770, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. e-Meeting; 20230417 - 20230426, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052352254 *

Also Published As

Publication number Publication date
CN120129063A (zh) 2025-06-10

Similar Documents

Publication Publication Date Title
JP7663713B2 (ja) サイドリンクフィードバックリソースの決定方法、端末及びネットワーク側機器
EP4274142A1 (en) Method for processing pdcch monitoring capabilities, terminal and network side device
WO2023280275A1 (zh) 传输方法、终端及网络侧设备
JP2023523451A (ja) 制御情報ｄｃｉ伝送方法及び関連機器
US20250227727A1 (en) Resource indication method, terminal, and network-side device
CN116471675A (zh) 传输确定方法、装置、设备及介质
EP4307824A1 (en) Terminal and communication method
WO2020194636A1 (ja) ユーザ装置
CN114071749A (zh) 物理下行控制信道的监听方法、装置和设备
WO2025157129A1 (zh) 频域资源的操作方法、终端、网络侧设备及存储介质
WO2025146101A1 (zh) 信息指示方法、装置、终端、网络侧设备及介质
CN115706971A (zh) Pdcch监测方法、相关设备及可读存储介质
US20230354064A1 (en) Signal configuration method and apparatus, device, and storage medium
WO2025119359A1 (zh) 控制信道的传输方法、装置、设备及存储介质
WO2023051638A1 (zh) Ue能力上报方法、联合调度方法、调度方法和设备
JP2024510829A (ja) 制御チャネルモニタリング方法、装置、端末及びネットワーク側機器
WO2025152904A1 (zh) 信息传输方法、装置、终端及网络侧设备
WO2025146048A1 (zh) 非授权频谱上的ssb传输方法、装置及设备
WO2025146174A1 (zh) 跳频传输方法及装置
WO2024160199A1 (zh) 旁链路传输方法、装置、终端及存储介质
WO2025108454A1 (zh) 通信方法、终端及网络侧设备
WO2025162347A1 (zh) Occ确定方法、装置、设备及存储介质
WO2024032786A1 (zh) 侧链路的功率控制方法及终端
WO2026040929A1 (zh) 通信方法、装置、终端、网络侧设备及存储介质
WO2025148948A1 (zh) 随机接入方法、装置、终端及网络侧设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24899992

Country of ref document: EP

Kind code of ref document: A1