WO2020224306A1 - 一种通信的方法和装置 - Google Patents

一种通信的方法和装置 Download PDF

Info

Publication number
WO2020224306A1
WO2020224306A1 PCT/CN2020/075799 CN2020075799W WO2020224306A1 WO 2020224306 A1 WO2020224306 A1 WO 2020224306A1 CN 2020075799 W CN2020075799 W CN 2020075799W WO 2020224306 A1 WO2020224306 A1 WO 2020224306A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
sib1
information
pbch block
time
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.)
Ceased
Application number
PCT/CN2020/075799
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to BR112021022042A priority Critical patent/BR112021022042A2/pt
Priority to MX2021013469A priority patent/MX2021013469A/es
Priority to JP2021565097A priority patent/JP7374221B2/ja
Priority to EP20801620.4A priority patent/EP3952553A4/en
Priority to KR1020217039231A priority patent/KR102763820B1/ko
Publication of WO2020224306A1 publication Critical patent/WO2020224306A1/zh
Priority to US17/517,385 priority patent/US20220061006A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium
    • H04B7/15542—Selecting at relay station its transmit and receive resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • 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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices
    • 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/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the present invention relates to communication technology, in particular to a communication method and device in a wireless communication system.
  • the base station establishes a connection with the core network through optical fiber.
  • the deployment cost of optical fiber is very high.
  • the wireless relay node (RN) establishes a connection with the core network through a wireless backhaul link, which can save part of the fiber deployment cost.
  • the wireless relay node establishes a wireless backhaul link with one or more upper-level nodes, and accesses the core network through the upper-level nodes.
  • the wireless relay node can provide services for multiple subordinate nodes.
  • the upper node of the relay node may be a base station or another relay node; the lower node of the relay node may be a terminal device or another wireless relay node.
  • In-band relay is a relay solution in which the backhaul link and the access link share the same frequency band. Since there is no additional spectrum resource, the in-band relay has the advantages of high spectrum efficiency and low deployment cost. In-band relay generally has a half-duplex constraint. Specifically, a relay node cannot send a downlink signal to its lower node when receiving a downlink signal sent by its upper node, and a relay node is receiving an uplink signal sent by its lower node. It cannot send an uplink signal to its superior node.
  • the relay solution supported by the new radio (NR) of the fifth generation mobile networks (5th generation mobile networks or 5G) radio access network (RAN) is called integrated access and Integrated access and backhaul (IAB), and integrated access and backhaul relay nodes are called IAB nodes (IAB nodes).
  • NR new radio
  • 5G fifth generation mobile networks
  • RAN radio access network
  • IAB nodes integrated access and backhaul relay nodes
  • the IAB node in NR includes two parts of functions, the mobile terminal (Mobile Termination, MT) function and the Distributed Unit (DU). Among them, MT is used for IAB nodes to communicate with upper-level nodes, and DU is used for IAB nodes to communicate with lower-level nodes.
  • the upper-level node can be an ordinary base station (such as gNB) or another IAB node; the lower-level node can be a terminal device. , Or another IAB node.
  • the link between the MT and the upper-level node is called the parent BackHaul link
  • the link between the DU and the lower-level IAB node is called the child BackHaul link
  • the DU and the subordinate terminal The link through which the device communicates is called an access link.
  • the lower-level backhaul link and the access link may be collectively referred to as the access link.
  • the access link and the backhaul link perform resource multiplexing in a time division, space division or frequency division manner. Taking time division multiplexing as an example, the backhaul link and the access link receive and send signals at different times.
  • IAB nodes need to frequently send and receive some cell-level signals or channels, for example, synchronization signal/physical broadcast channel (Synchronization signal/physical broadcast channel, SS/PBCH) block, system information (system information, SI) etc.
  • the upper-level node In order to achieve the purpose of avoiding resource conflicts, the upper-level node needs to know the time domain resources for the IAB node DU to send cell-level signals. Therefore, how the upper-level node obtains the time domain resources for the IAB node DU to send the cell-level signal is a problem that needs to be solved urgently.
  • the embodiments of the present application provide a communication method and device, so that the upper-level node can learn the time domain resources of the signal sent by the IAB node DU, and avoid conflicts with the MT transmission of the IAB node.
  • an embodiment of the present application provides a communication method, including: receiving configuration information from a first node or a third node, the configuration information indicating the time of the system information block 1SIB1 of the first node distributed unit DU Frequency information; based on the acquired time-frequency information of the SIB1 of the first node DU, determine the unavailable resources of the mobile terminal MT function of the first node; wherein the first node is an integrated access backhaul IAB node, and the second node The node is the superior node of the first node, and the third node is the donor node.
  • the second node determines the hard resource of the DU of the IAB node, and accordingly determines the hard resource as the MT unavailable resource of the IAB node. In this way, the MT of the IAB is prevented from scheduling on the hard resource, and resource conflict is avoided.
  • the configuration information specifically includes: synchronization signal/physical broadcast channel SS/PBCH BLOCK time domain information. Obtain the time domain information of SIB1 through the time domain information of SS/PBCH BLOCK, no additional signaling instructions are required, and signaling overhead can be reduced.
  • the time domain information of the synchronization signal/physical broadcast channel SS/PBCH BLOCK includes the period and offset of the SS/PBCH BLOCK.
  • the configuration information further includes the CORESET configuration of the search space occupied by the PDCCH of the SIB1, and the CORESET configuration includes one or more of the following information:
  • the second node stores one or more tables, and each of the one or more tables records the following information:
  • the configuration information further includes: subcarrier spacing of SS/PBCH BLOCK, and subcarrier spacing of SIB1.
  • the configuration information further includes: the minimum channel bandwidth occupied by the DU of the first node.
  • the method further includes:
  • the second node receives a first index, where the first index indicates a CORESET configuration occupied by the PDCCH of SIB1;
  • the CORESET configuration occupied by the PDCCH of SIB1 is determined from the first table.
  • the configuration information further includes: information indicating the period and offset of the SIB1.
  • the information indicating the period of the SIB1 is a multiple of the period of SS/PBCH and BLOCK.
  • the configuration information further includes: the time slot occupied by the PDCCH of the SIB1 of the first node DU.
  • determining the unavailable resources of the MT function of the first node mobile terminal specifically includes: The time-frequency resource occupied by the SIB1 of the DU is determined to be an unavailable resource of the MT function of the first node.
  • the configuration information is received through radio resource control RRC signaling or interface message F1-AP.
  • the method further includes: the second node receives time domain parameters of the physical downlink shared channel PDSCH of the first node DU-scheduled SIB1.
  • the time domain parameter includes Time domain resource assignment in the downlink control information.
  • a communication method which includes: a first node determines a distributed unit DU of an IAB node to determine time-frequency information of a system information block 1SIB1; and sends configuration information to a second node, where the configuration information indicates the Time-frequency information of the SIB1; where the first node is an integrated access backhaul IAB node or a Donor node, and the second node is an upper-level node of the first node.
  • the configuration information specifically includes: time domain information of a synchronization signal/physical broadcast channel SS/PBCH BLOCK.
  • the time domain information of the synchronization signal/physical broadcast channel SS/PBCH BLOCK includes the period and offset of the SS/PBCH BLOCK.
  • the configuration information further includes: CORESET configuration of the search space occupied by the PDCCH of the SIB1, and the CORESET configuration includes one or more of the following information:
  • the configuration information further includes: the subcarrier interval of SS/PBCH BLOCK, and the subcarrier interval of SIB1.
  • the configuration information further includes: the minimum channel bandwidth occupied by the DU of the first node.
  • the configuration information further includes: information indicating the period and offset of the SIB1.
  • the information indicating the period of the SIB1 is a multiple of the period of SS/PBCH and BLOCK.
  • the configuration information further includes: the time slot occupied by the PDCCH of the SIB1 of the first node DU.
  • the second configuration information includes: sending the configuration information through radio resource control RRC signaling or an interface message F1-AP.
  • the second configuration information further includes: the method further includes: the first node reports to the second node the time domain parameters of the physical downlink shared channel PDSCH of the DU scheduling SIB1.
  • the time domain parameter includes Time domain resource assignment in the downlink control information.
  • the upper-level node of the IAB node obtains the time domain resource of the SIB1 of the IAB node DU, and treats the time domain resource as the hard resource of the IAB node DU.
  • the IAB node MT cannot use the time domain resource for transmission and reception, which can avoid conflicts.
  • a node including: a transceiver unit, configured to receive configuration information from a first node or a third node, the configuration information indicating the time-frequency of the system information block 1SIB1 of the first node distributed unit DU Information; a processing unit for determining the unavailable resources of the MT function of the first node mobile terminal based on the acquired time-frequency information of the SIB1 of the first node DU; wherein the first node is the integrated access backhaul IAB Node, the third node is the Donor node.
  • the configuration information specifically includes: time domain information of a synchronization signal/physical broadcast channel SS/PBCH BLOCK.
  • the time domain information of the synchronization signal/physical broadcast channel SS/PBCH BLOCK includes the period and offset of the SS/PBCH BLOCK.
  • the configuration information further includes: a CORESET configuration of the search space occupied by the PDCCH of the SIB1, and the CORESET configuration includes one or more of the following information:
  • the configuration information further includes: subcarrier spacing of SS/PBCH BLOCK, and subcarrier spacing of SIB1.
  • the configuration information further includes: the minimum channel bandwidth occupied by the DU of the first node.
  • the node further includes a storage unit for storing one or more tables, and each of the one or more tables records the following information:
  • the transceiver unit is further configured to obtain the subcarrier interval of SIB1 and the subcarrier interval of SS/PBCH BLOCK; and, receive a first index, where the first index indicates a PDCCH of SIB1 CORESET configuration occupied;
  • the processing unit is further configured to determine a first table in the one or more tables based on the subcarrier interval of the SIB1 and the subcarrier interval of SS/PBCH BLOCK; and, based on the first index, from The CORESET configuration occupied by the PDCCH of SIB1 is determined in the first table.
  • the configuration information further includes: information indicating the period and offset of the SIB1.
  • the information indicating the period of the SIB1 is a multiple of the period of SS/PBCH and BLOCK.
  • the configuration information further includes the time slot occupied by the PDCCH of the SIB1 of the first node DU.
  • the processing unit is configured to determine the time-frequency resource occupied by the SIB1 of the first node DU as an unavailable resource of the MT function of the first node.
  • the transceiver unit is configured to receive the configuration information through radio resource control RRC signaling or an interface message F1-AP.
  • the transceiver unit is further configured to: receive the time domain parameters of the physical downlink shared channel PDSCH of the first node DU scheduling SIB1.
  • the time domain parameter includes Time domain resource assignment in the downlink control information.
  • the upper-level node of the IAB node obtains the time domain resource of the SIB1 of the IAB node DU, and treats the time domain resource as the hard resource of the IAB node DU.
  • the IAB node MT cannot use the time domain resource for transmission and reception, which can avoid conflicts.
  • a first node including: a processing unit for determining time-frequency information of the system information block 1SIB1 of the IAB node distributed unit DU; a transceiver unit for reporting configuration information to the second node, so The configuration information indicates the time-frequency information of the SIB1; wherein, the first node is an integrated access backhaul IAB node or a Donor node, and the second node is an upper node of the first node.
  • the configuration information specifically includes time domain information of a synchronization signal/physical broadcast channel SS/PBCH BLOCK.
  • the time domain information of the synchronization signal/physical broadcast channel SS/PBCH BLOCK includes the period and offset of the SS/PBCH BLOCK.
  • the configuration information further includes the CORESET configuration of the search space occupied by the PDCCH of the SIB1, and the CORESET configuration includes one or more of the following information:
  • the configuration information further includes: subcarrier spacing of SS/PBCH BLOCK, and subcarrier spacing of SIB1.
  • the configuration information further includes the minimum channel bandwidth occupied by the DU of the first node.
  • the configuration information further includes information indicating the period and offset of the SIB1.
  • the information indicating the period of the SIB1 is a multiple of the period of SS/PBCH and BLOCK.
  • the configuration information further includes the time slot occupied by the PDCCH of the SIB1 of the first node DU.
  • the transceiver unit sends the configuration information through radio resource control RRC signaling or an interface message F1-AP.
  • the transceiver unit is further configured to report the time domain parameters of the physical downlink shared channel PDSCH of the DU scheduling SIB1 to the second node.
  • the time domain parameter includes Time domain resource assignment in the downlink control information.
  • a device configured to implement the function of the communication method provided by any of the possible implementations of the first aspect.
  • the function can be implemented by hardware or Implement the corresponding software through hardware.
  • the hardware or software includes one or more units corresponding to the above functions.
  • the structure of the apparatus includes a processor, and the processor is configured to support the user equipment to execute the communication provided by the first aspect or any one of the possible implementation manners of the first aspect.
  • the device may further include a memory and a communication interface, the memory stores code and data, the memory is coupled with the processor, and the communication interface is coupled with the processor or the memory.
  • a device configured to implement the function of the communication method provided by the second aspect or any one of the possible implementation manners of the second aspect, and the function may be implemented by hardware Realization can also be realized by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the above functions.
  • the apparatus includes a processor in the structure, and the processor is configured to support the network device to execute the communication method provided in the second aspect or any one of the possible implementation manners of the second aspect.
  • the network device may further include a memory and a communication interface, the memory stores code required for processing and/or the baseband processor, the memory is coupled with the processor, and the communication interface is coupled with the memory or the processor.
  • a computer-readable storage medium stores instructions which, when run on a computer, cause the computer to execute the first aspect or the first aspect described above.
  • the communication method provided by any possible implementation manner, or the communication method provided by the foregoing second aspect or any possible implementation manner of the second aspect is implemented.
  • Another aspect of the present application provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the communication provided by the first aspect or any possible implementation of the first aspect.
  • a communication system in yet another aspect of the present application, includes a first node, a second node, and a third node.
  • the first node is the first node provided by the above aspects and is used to support the first node.
  • the node executes the communication method provided by the foregoing first aspect or any one of the possible implementations of the first aspect; and/or, the second node is the second node provided by the foregoing aspects, and is used to support the second node to perform the foregoing
  • the communication method provided by the second aspect or any possible implementation of the second aspect; and/or, the third node is the third node provided by the foregoing aspects, and is used to support the third node to perform the foregoing first aspect Or the communication method provided by any possible implementation of the first aspect.
  • FIG 1 is an IAB communication system provided by an embodiment of this application.
  • Figure 2 is a schematic diagram of a backhaul link and an access link provided by an embodiment of the application
  • FIG. 3 is a schematic diagram of hard resources and soft resources provided by an embodiment of the application.
  • Fig. 4 is a schematic diagram of resource allocation of IAB nodes MT and DU provided by an embodiment of the application;
  • Fig. 5 is a multiplexing pattern of SS/PBCH BLOCK and SIB1 provided by an embodiment of the application;
  • Fig. 6 is a schematic diagram of pattern 3 provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of pattern 2 provided by an embodiment of the application.
  • FIG. 8 is a schematic diagram of sending SIB1 according to an embodiment of the application.
  • FIG. 9 is a schematic diagram of pattern 1 provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram of interaction of a communication method provided by an embodiment of this application.
  • FIG. 11 is a schematic diagram of a possible structure of a node provided by an embodiment of this application.
  • FIG. 12 is a schematic diagram of a possible logical structure of a node provided by an embodiment of this application.
  • FIG. 1 is a schematic structural diagram of a communication system to which an embodiment of this application is applied.
  • the communication systems mentioned in the embodiments of this application include but are not limited to: narrowband-internet of things (NB-IoT) systems, car networking, and wireless local access network (WLAN) systems , LTE system, 5G mobile communication system, such as NR, device-to-device (D2D) communication system, or the next generation communication system after 5G.
  • NB-IoT narrowband-internet of things
  • WLAN wireless local access network
  • LTE Long Term Evolution
  • 5G mobile communication system such as NR
  • D2D device-to-device
  • An IAB system includes at least one base station 100, and one or more terminal devices (terminals) 101 served by the base station 100, one or more relay nodes IAB node, and one or more terminal devices served by the IAB node 110 111.
  • the base station 100 is generally called a donor next generation node B (DgNB), and the IAB node 110 is connected to the base station 100 through a wireless backhaul link 113.
  • the donor base station is also referred to as a donor node in this application, that is, a Donor node.
  • the base station 100 includes, but is not limited to: evolved node B (evolved node base, eNB), radio network controller (RNC), node B (node B, NB), base station controller (base station controller, BSC) , Base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home node B, HNB), baseband unit (baseband Unit, BBU), eLTE (evolved LTE, eLTE) base station, NR base station ( next generation node B, gNB) etc.
  • evolved node B evolved node base, eNB
  • RNC radio network controller
  • node B node B
  • base station controller base station controller
  • BSC base station controller
  • BTS base station controller
  • BTS base station controller
  • BTS base station controller
  • BTS base station controller
  • home base station for example, home evolved NodeB, or home node B, HNB
  • baseband unit baseband Unit
  • Terminal equipment includes but is not limited to: user equipment (UE), mobile station, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile equipment, terminal, wireless communication equipment, user agent, Station (ST), cell phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, wireless local access network (WLAN) Personal digital assistant (PDA), handheld devices with wireless communication functions, computing devices, other processing devices connected to wireless modems, in-vehicle devices, wearable devices, mobile stations in the future 5G network, and public Any of the terminal devices in the public land mobile network (PLMN) network.
  • the IAB node is a specific name of a relay node, which does not limit the solution of this application. It can be one of the above-mentioned base stations or terminal devices with a forwarding function, or it can be an independent device form.
  • the integrated access backhaul system can also include multiple other IAB nodes, such as IAB node 120 and IAB node 130.
  • IAB node 120 is connected to IAB node 110 through wireless backhaul link 123 to connect to the network, IAB node 130 It is connected to the IAB node 110 through the wireless backhaul link 133 to access the network.
  • the IAB node 120 serves one or more terminal devices 121, and the IAB node 130 serves one or more terminal devices 131.
  • IAB node 110 and IAB node 120 are both connected to the network through a wireless backhaul link.
  • the wireless backhaul links are all viewed from the perspective of the relay node.
  • the wireless backhaul link 113 is the backhaul link of IAB node 110
  • the wireless backhaul link 123 is IAB node 120. Backhaul link.
  • an IAB node such as 120
  • the relay node can be connected through multi-level wireless relay nodes To the network.
  • IAB node can generally refer to any node or device with a relay function.
  • the use of IAB node and relay node in this application should be understood to have the same meaning.
  • the IAB node may be a base station, a TRP, a module or a device installed on a mobile object.
  • the mobile object includes but is not limited to devices in the Internet of Things, such as cars, trains, and airplanes.
  • the lower-level node can be regarded as a terminal device of the upper-level node.
  • an IAB node in the integrated access backhaul system shown in Figure 1, an IAB node is connected to an upper-level node.
  • an IAB node such as 120
  • the IAB node 130 in the figure can also be connected to the IAB node 120 through the backhaul link 134, that is, both the IAB node 110 and the IAB node 120 are the upper nodes of the IAB node 130.
  • the name of the IAB node 110, 120, 130 does not limit the scenario or network where it is deployed, and can be any other name such as relay, RN, etc.
  • the use of IAB node in this application is only for the convenience of description.
  • the wireless links 102, 112, 122, 132, 113, 123, 133, 134 can be bidirectional links, including uplink and downlink transmission links.
  • the wireless backhaul links 113, 123, 133, 134 can be used by the upper node to provide services for the lower nodes, such as the upper 100 provides wireless backhaul service for the lower node 110.
  • the uplink and downlink of the backhaul link may be separated, that is, the uplink and the downlink are not transmitted through the same node.
  • the downlink transmission refers to higher-level nodes, such as node 100, and lower-level nodes, such as node 110, transmitting information or data
  • uplink transmission refers to lower-level nodes, such as node 110, and upper-level nodes, such as node 100, transmitting information or data.
  • the node is not limited to whether it is a network node or a terminal device.
  • the terminal device can act as a relay node to serve other terminal devices.
  • the wireless backhaul link can be an access link in some scenarios.
  • the backhaul link 123 can also be regarded as an access link for the node 110, and the backhaul link 113 is also the access link of the node 100. link.
  • the link 113 is referred to as a parent BH
  • the link 123 is referred to as a child BH
  • the link 112 is referred to as an access link.
  • the above-mentioned upper-level node may be a base station or a relay node
  • the lower-level node may be a relay node or a terminal device with a relay function.
  • the lower-level node may also be a terminal device.
  • the relay nodes shown in Figure 1, such as 110, 120, and 130, can exist in two forms: one is to exist as an independent access node and can independently manage the terminal equipment connected to the relay node.
  • Relay nodes usually have independent physical cell identifiers (PCI).
  • PCI physical cell identifiers
  • This type of relay usually requires complete protocol stack functions, such as radio resource control (RRC) functions.
  • RRC radio resource control
  • layer 3 relay another form of relay node and Donor node, such as Donor eNB, Donor gNB, belong to the same cell, and user management is managed by the donor base station, such as Donor node.
  • This kind of relay is usually called layer 2 relay.
  • Layer 2 relays usually exist as the DU of the base station DgNB under the NR control and bearer separation (central unit and distributed unit, CU-DU) architecture, and communicate with the CU through the F1-AP (F1 application protocol) interface or tunnel protocol .
  • the tunneling protocol may be, for example, the GTP (general packet radio service tunneling protocol, GTP) protocol, and the F1-AP may be an F1-AP enhanced interface, which will not be repeated.
  • a Donor node refers to a node that can access the core network through this node, or an anchor base station of the wireless access network, through which the anchor base station can access the network.
  • the anchor base station is responsible for receiving data from the core network and forwarding it to the relay node, or receiving data from the relay node and forwarding it to the core network.
  • Upper-level node A node that provides wireless backhaul link resources, such as 110, which is called the upper-level node of IAB node 120.
  • the superior node may also be referred to as an upstream node. It should be understood that the superior node is not limited to the direct superior node that provides wireless backhaul link resources, and includes all nodes that provide wireless backhaul link resources on the link that provides transmission to the donor base station.
  • the direct superior node refers to the node that directly provides transmission resources for the relay node.
  • IAB node 110 is the direct superior node of IAB node 120.
  • Lower-level nodes nodes that use backhaul link resources to transmit data to the network or receive data from the network are called lower-level nodes.
  • 120 is called a subordinate node of the relay node 110
  • the network is a network above the core network or other access networks, such as the Internet, a private network, etc.
  • the subordinate nodes are not limited to the direct subordinate nodes that provide wireless backhaul link resources for them, and include all nodes that provide wireless backhaul link resources on the links that provide transmission to the target node.
  • the direct subordinate node refers to the node that directly provides transmission resources for it.
  • IAB node 120 is the direct subordinate node of IAB node 110.
  • Access link the link between the UE and the IAB node, or between the UE and the IAB Donor.
  • the access link includes a wireless link used when a node communicates with its subordinate nodes.
  • the access link includes an uplink access link and a downlink access link.
  • the uplink access link is also referred to as the uplink transmission of the access link, and the downlink access link is also referred to as the downlink transmission of the access link.
  • Backhaul link the link between the IAB node and the IAB child node (IAB child node), or the link between the IAB node and the IAB parent node (IAB parent node).
  • the backhaul link includes the downlink transmission link of the IAB node and the IAB child node, or the IAB node and the IAB parent node; the backhaul link also includes the uplink transmission link of the IAB node and the IAB child node, or the IAB node and the IAB parent node. link.
  • the data transmission of the IAB node to the parent node of the IAB or the uplink transmission of the child node of the IAB is called the uplink transmission of the backhaul link.
  • the IAB node receives the data transmission of the IAB parent node, or the data transmission to the IAB child node is called the downlink transmission of the backhaul link.
  • the backhaul link between the IAB node and the IAB parent node is also called the parent BH, and the backhaul link between the IAB node and the IAB child node It is called the lower-level backhaul link (child BH).
  • the IAB node includes two main functions, one is a mobile-termination (MT) function, and the other is a distributed unit (DU) function.
  • the IAB node can perform uplink transmission and/or downlink transmission with the superior node on the MT.
  • the IAB node can perform uplink transmission and/or downlink transmission with subordinate nodes on the DU.
  • Figure 2 shows a schematic diagram of the upper and lower nodes of the IAB node.
  • the upper-level backhaul DL is the link for the upper-level node to send downlink signals to the IAB node
  • the upper-level backhaul UL is the link for the IAB node to send uplink signals to the upper-level node
  • the lower-level backhaul DL is the IAB node to the lower-level node
  • the lower-level backhaul UL is the link for the lower-level node to send the uplink signal to the IAB node
  • the access UL is the link for the terminal device to send the uplink signal to the IAB node
  • the access DL is the IAB node sending to the terminal device Downlink signal link.
  • Figure 3 is a schematic diagram of the resource configuration of an IAB node in NR.
  • Figure 3 takes time division duplex (TDD) as an example, where the MT resource of the IAB node can be configured as three types: downlink (D), uplink (U), and flexible (F) .
  • the F-type resources can be configured for uplink or downlink transmission, and whether it is used for uplink transmission or downlink transmission depends on the signaling configuration.
  • the DU resource of the IAB node can be configured as downlink, uplink, flexible and unavailable (Null, N) four types. Further, the DU's downlink, uplink, and flexible resources can also be divided into hard (hard, H) resources and soft (soft, S) resources. Among them, the hard resource of the DU indicates the resource that is always available to the DU. The soft resource of the DU indicates that whether the DU is available depends on the indication of the upper-level node (for example, the donor node). In FIG. 3, the upper-level node controls the use of the S resource on the IAB node DU through downlink control information (DCI) in the downlink time slot or subframe.
  • the H resources and S resources are semi-statically configured by the donor base station or upper-level node through RRC, or the donor base station is semi-statically configured through the F1-AP protocol.
  • the MT of the IAB node is connected to the DU of the upper node, and the DU of the IAB node is connected to the MT of the lower node.
  • the IAB node can obtain the resource configuration of its MT resource and DU resource respectively. For example, it may include the transmission direction (D/U/F) of the MT resource and the DU resource, the type of the DU resource (soft/hard), and the location of the NULL resource of the DU.
  • the hard resources of its DU correspond to MT resources (for example, the first and The MT resources corresponding to time slots 6, 7, and 8 are unavailable.
  • the time slot number in FIG. 3 may also be a subframe number or a symbol number. The following description mainly takes a time slot as an example, and will not be repeated.
  • the MT of the IAB node has a total of three types of resources, and the DU of the IAB node has a total of 7 types of resources.
  • the possible transceiver status of the MT of the IAB node and its corresponding DU are as follows The following Table 1 and Table 2 are shown, where Table 1 is the resource configuration situation under various possible resource type combinations of MT and DU in the time division multiplexing scenario.
  • Table 2 shows the resource configuration under various possible resource type combinations of MT and DU in a spatial division multiplexing (SDM) scenario.
  • SDM spatial division multiplexing
  • MT:Tx means that the MT should transmit after being scheduled
  • DU:Tx means DU can be transmitted
  • MT:Rx means that the MT is capable of receiving (if there is a signal that needs to be received);
  • DU:Rx means that the DU can schedule the uplink transmission of the lower node
  • MT:Tx/Rx means that MT should transmit or receive after being scheduled, but transmission and reception do not occur at the same time
  • DU:Tx/Rx means that DU can transmit or receive transmission from lower-level nodes, but transmission and reception do not occur at the same time;
  • IA means that the DU resource is explicitly or implicitly indicated as available
  • INA means that the DU resource is explicitly or implicitly indicated as unavailable
  • MT:NULL means that the MT does not send and does not have to have receiving capabilities
  • DU:NULL means that the DU does not send and does not receive transmissions from lower-level nodes.
  • This application mainly considers TDM scenarios, but the solution of this application can also be extended to scenarios such as SDM, frequency-division multiplexing (FDM), or full-duplex.
  • SDM single-division multiplexing
  • FDM frequency-division multiplexing
  • the MT resource corresponding to the DU hard resource is unavailable.
  • the MT does not perform physical downlink control channel (PDCCH) monitoring on these resources, that is, if the search space overlaps these resources, the MT of the IAB node abandons the overlapped search space monitoring.
  • PDCCH physical downlink control channel
  • the MT may also have other unavailable resources.
  • the upper-level node will continue to use dynamic signaling (for example, downlink control information (DCI)) to dynamically indicate to the IAB node the availability of soft-type resources of its DU resources, for example, the upper-level node uses
  • DCI downlink control information
  • the dedicated DCI or dedicated DCI field indicates the availability of the soft resources of the IAB node.
  • the information contained in the dynamic signaling is called indication information, and the above dedicated DCI or dedicated DCI field can be collectively referred to as indicating DCI .
  • the above dynamic indication can be achieved in a variety of ways.
  • this can be done through explicit instructions.
  • the upper-level node directly indicates the availability of the soft resource of the DU resource of the IAB node.
  • it may also indicate the transmission direction of some (for example, F-type) soft resources at the same time.
  • the upper-level node indicates whether the MT resource of the IAB node (for example, the available resource of the MT) is released (or whether it is available), and the IAB node determines the soft type resource of its DU resource according to the indication of the upper-level node for the above-mentioned MT resource. Availability.
  • the IAB node When the DU of the IAB node is configured as a hard resource, the IAB node usually performs complete transmission on the time slot configured as a hard resource.
  • the meaning of the complete transmission is that the IAB node considers that all symbols on the time slots configured as hard resources are available.
  • the hard resources of the IAB node can be regarded as resources that are always available.
  • the IAB node can always communicate with subordinate nodes on this resource, regardless of the MT scheduling configuration. In other words, the communication between the upper node and the IAB node MT should not affect the communication between the DU and the lower node or UE at the hard resource.
  • part of the periodic signals of the IAB node DU including but not limited to periodic CSI-RS, SRS, are configured by the Donor node and notified to the terminal equipment or subordinate nodes of the IAB node through RRC signaling.
  • the part of the periodic signal configured by the Donor node for the IAB node should be located in the hard resource of the IAB node DU.
  • FIG. 4 is a schematic diagram of the relationship between the Hard/Soft resources of the DU and the available or unavailable resources of the MT provided in an embodiment of the application. Take the symbol as an example in Figure 4. Among them, the H symbol represents Hard resources, the S symbol represents Soft resources, A represents available resources, and NA represents unavailable resources. It should be understood that FIG. 4 is only an example, where 0, 1, 2, 3, 4, 5, and 6 can represent symbols or time slots or subframes.
  • Fig. 4 shows 7 symbols, among which symbols 0 and 6 are Hard resources of DU, and symbol 0 and symbol 6 can always be used for DU.
  • symbols 0 and 6 are Hard resources of DU, and symbol 0 and symbol 6 can always be used for DU.
  • FIG 4 it is assumed that resources are allocated between the MT and the DU of the IAB node in a time-division multiplexing TDM manner.
  • symbols 0 and 6 are unavailable resources.
  • Symbols 1 to 5 in the figure are soft symbols of DU.
  • symbols 1 to 5 are available resources.
  • the IAB node DU should be able to send and receive cell-specific signals.
  • the upper-level node should not schedule the IAB node MT function.
  • Solution 1 When configuring resources, configure all resources for sending cell-specific signals or channels as hard resources;
  • Solution 2 When cell-specific signals or channels use non-hard resources, convert this resource to hard resource, or treat this resource as hard resource.
  • solution 1 may severely restrict the flexibility of resource allocation, so solution 2 is a better option.
  • the upper-level node needs to know the time domain resources for the IAB node DU to send cell-specific signals. Therefore, the problem to be solved by the present invention is how the upper-level node obtains the time domain resources for the IAB node DU to send cell-specific signals.
  • the cell-specific signal can be one of the following signals:
  • Synchronization signal/physical broadcast channel (SS/PBCH) block also referred to as SSB for short
  • SIB system information block
  • CSI-RS channel state information reference signal
  • RACH Random Access Channel
  • SRS sounding reference signal
  • SRS scheduling request
  • the embodiment of this application mainly introduces how an upper-level node obtains the time-frequency resources of SIB1 and SS/PBCH BLOCK sent by the IAB node DU.
  • the upper-level node learns the time-frequency resources of the cell-specific signal of the IAB node DU, it regards the resources occupied by the DU as the hard resource of the IAB node DU.
  • the MT of the IAB node no longer uses this resource for transmission.
  • the IAB node does not expect the upper-level node to schedule its MT on this resource, or the upper-level node scheduling the transmission of the IAB node MT does not affect the use of hard resources by the DU.
  • IAB node DU may send two types of SS/PBCH BLOCK, one is used for terminal equipment access SS/PBCH BLOCK, which can be called cell-defining SS/PBCH BLOCK or access SS/PBCH BLOCK (AC-SSB ), another type of SS/PBCH BLOCK used for IAB node mutual measurement, can be called backhaul SS/PBCH BLOCK (BH-SSB).
  • SS/PBCH BLOCK cell-defining SS/PBCH BLOCK or access SS/PBCH BLOCK
  • BH-SSB backhaul SS/PBCH BLOCK
  • the two SS/PBCH BLOCKs are in different time domain positions.
  • the DU of the IAB node will send the SS/PBCH BLOCK time-frequency information to the terminal device or lower-level node through an RRC message.
  • the RRC information is generally generated by the Donor node. Therefore, the Donor node can send the time domain information of the AC-SSB to the upper-level node; or the IAB node reports the time-frequency information of the AC-SSB to the upper-level node.
  • the SS/PBCH BLOCK period the index of the SS/PBCH sent within a half frame, and/or the offset of the SS/PBCH BLOCK relative to the starting position.
  • the upper-level node may assume that at least part of the parameters of the SS/PBCH and BLOCK sent by the IAB node DU (such as SS/PBCH BLOCK period, offset Quantity) is the same as itself. That is, the time-frequency resource of the AC-SSB of the IAB node DU is regarded as the same as the period of the SS/PBCH BLOCK of the upper-level node; or the time-frequency resource of the AC-SSB of the IAB node DU is regarded as the same as that of the upper-level node.
  • SS/PBCH and BLOCK have the same cycle and the same offset.
  • the upper-level node may assume that the IAB node will send all available resources of the SS/PBCH BLOCK in a half frame (actually, the IAB node may only send some available time-frequency resources).
  • the Donor node will send BH-SSB transmission configuration information (SS/PBCH block transmission configuration, STC) to each IAB node. Therefore, the Donor node may send the BH-SSB transmission configuration of the IAB node to the upper-level node of the IAB node, or the IAB node may report its own STC to the upper-level node.
  • the STC includes one or more of the following information: SS/PBCH BLOCK transmission period, offset, subcarrier spacing, SS/PBCH BLOCK index, SS/PBCH BLOCK frequency domain information.
  • the first node or the third node sends the time-frequency configuration information of SS/PBCH BLOCK to the second node, and the time-frequency configuration information of the SS/PBCH BLOCK includes the transmission period and offset of the SS/PBCH BLOCK.
  • the first node is an IAB node
  • the third node is a Donor node
  • the second node is an upper node of the IAB node.
  • the second node learns the time-frequency resource of the third node's DU to send the SS/PBCH BLOCK, and then does not send to the MT of the third node on the corresponding time-frequency resource Downlink signals to avoid conflicts.
  • the time-frequency configuration information of the SS/PBCH BLOCK also includes the subcarrier interval of the SS/PBCH BLOCK, the index of the SS/PBCH BLOCK in a half frame, and the frequency domain information of the SS/PBCH BLOCK.
  • the second node determines the time-frequency resource for sending SIB1 to the DU of the IAB node based on the time-frequency information of the SS/PBCH and BLOCK of the IAB node DU.
  • the MT function sends downlink signals to avoid conflicts between the MT function of the IAB node and the DU resource.
  • the BH-SSB sent by the IAB node DU may conflict with the SS/PBCH BLOCK received by the IAB node MT in the time domain. In order to avoid conflicts, two results may occur at this time.
  • the IAB node DU sends BH-SSB and is muted, or the IAB node MT receives SS/PBCH and the BLOCK is muted. For example, when the IAB node DU sends the BH-SSB to be silent, it means that the hard resources of the IAB node are occupied by some specific MT signals.
  • the priority of IAB node MT receiving SS/PBCH BLOCK is higher than IAB node DU sending SS/PBCH BLOCK. Therefore, when the receiving configuration of SS/PBCH BLOCK conflicts with the sending configuration of SS/PBCH BLOCK That is, when the configured SS/PBCH BLOCK of the IAB node MT receives and occupies the same time domain resources as the configured SS/PBCH BLOCK transmission of the IAB node DU, the IAB node DU does not send the SS/PBCH BLOCK. However, on these resources, the MT of the IAB node may not receive SS/PBCH and BLOCK. At this time, the IAB node can regard this part of the resource as the hard resource of the IAB node DU.
  • the terminal equipment transmits the remaining signals or channels.
  • the IAB node MT is configured to receive SS/PBCH and BLOCK resources, such as SMTC occupies resources
  • the upper-level node does not expect the IAB node MT to transmit the remaining signals. Therefore, when the IAB node MT does not When receiving SS/PBCH and BLOCK, the DU of the IAB node can use this resource.
  • the above is an introduction to how the upper-level node obtains the time domain resource of the IAB node DU to send the SS/PBCH BLOCK, and then how the upper-level node obtains the time domain resource of the SIB1.
  • the time-frequency resource of SIB1 obtained by the upper-level node includes two parts. The first part is: the upper-level node obtains the time-frequency resource of the PDCCH of the terminal device monitoring SIB1; the second part is: the time-frequency resource of the IAB node DU actually sending SIB1 (terminal device monitoring).
  • the time-frequency resource of the PDCCH of SIB1 can also be understood as: the IAB node DU may send all the time-frequency resources of SIB1.
  • SIBs are divided into multiple types. Among them, the system information sent by SIB1 is also called remaining minimum system information (RMSI), and the system information sent by SIBs other than SIB1 is called other system information (Other System Information). system information, OSI).
  • RMSI remaining minimum system information
  • OSI Operating System Information
  • SIB1-PDSCH The physical downlink share channel (PDSCH) of SIB1 represents the PDSCH carrying SIB1
  • CORESET control resource set
  • PDCCH Physical downlink control channel
  • CORESET is sometimes also referred to as SIB1-PDCCH. It should be understood that the meanings of both are the resources occupied by the PDCCH for scheduling SIB1-PDSCH).
  • Pattern 1 Both PDCCH and PDSCH of SIB1 are time-division multiplexed with SS/PBCH BLOCK;
  • Pattern 2 PDCCH and SS/PBCH BLOCK of SIB1 are time division multiplexed, while PDSCH and SS/PBCH BLOCK of SIB1 are frequency division multiplexed;
  • Pattern 3 Both PDCCH and PDSCH of SIB1 are frequency division multiplexed with SS/PBCH BLOCK.
  • the following takes a specific multiplexing pattern as an example to further explain how to obtain the time-frequency resource of SIB1 through the time-frequency resource of SS/PBCH BLOCK. It should be understood that the time-frequency resource of SIB1 includes the CORESET of SIB1 and the resource of PDSCH transmitting SIB1. I won't repeat them below.
  • the multiplexing pattern of SS/PBCH BLOCK and SIB1 is pattern 3
  • SIB1-PDCCH and SIB1-PDSCH are frequency division multiplexed with SS/PBCH BLOCK.
  • the upper-level node knows the time-frequency resource information of the SS/PBCH sent by the IAB node DU through the scheme described above, it can infer that the IAB node DU may send the time-frequency resource information of the SIB1-PDCCH.
  • each radio frame is 10ms in length, which is equivalent to sending SS/PBCH BLOCK every other radio frame
  • the starting position is radio frame 0
  • the time domain resources where SS/PBCH BLOCK is sent are radio frame 0, radio frame 2, radio frame 4...
  • the transmission of SS/PBCH and BLOCK is usually transmitted at the granularity of time slots or symbols.
  • a radio frame includes 10 subframes.
  • the symbol positions of SS/PBCH BLOCK in the time slot are as follows:
  • n For the 15KHz sub-carrier spacing, send according to ⁇ 2,8 ⁇ +14*n, where ⁇ 2,8 ⁇ represents the index of the first symbol of the SS/PBCH BLOCK, that is, the position. The following is the same and will not be repeated.
  • the position of the SS/PBCH Block in one synchronization signal period is traversed by the above formula for the above value of n, which is the same below, and will not be repeated.
  • n 0,1,2,3,5,6,7,8,10,11, 12,13,15,16,17,18.
  • n 0,1,2,3,5,6, 7,8.
  • the time domain resource for sending SS/PBCH BLOCK by the IAB node is also the time domain resource for sending SIB1.
  • the upper-level node can regard the time domain resource for sending SS/PBCH BLOCK as the time domain resource for the IAB node DU to send SIB1, and determine that the MT function of the IAB node is not available on this time domain resource. It can be a symbol or a time slot, which is not specifically limited in this application.
  • the period for the IAB node DU to actually send SIB1 may be 40 ms (twice the period of SS/PBCH and BLOCK).
  • the time domain resource for the IAB node DU to actually send the PDCCH of SIB1 can be determined according to the time domain information of the SS/PBCH BLOCK and the SIB1 period information.
  • the period of SIB1 can be a period of absolute time, for example, the period is 40ms; it can also be a period and offset of relative time, for example, the transmission period of SIB1-PDCCH is twice the period of SS/PBCH block.
  • the IAB node can use 2 to indicate the cycle, and the resulting cycle is 40ms.
  • the upper-level node regards the time domain resource of SS/PBCH BLOCK as the time domain resource for the IAB node DU to send SIB1, and determines that the MT function of the IAB node is not available on this subframe.
  • the upper-level node can first according to the configuration information of SS/PBCH BLOCK and CORESET of PDCCH of SIB1 , To determine the time domain position where the IAB node DU may send SIB1-PDCCH. According to the additional information instructions, it is determined that the IAB node DU actually sends the time domain resources of the SIB1.
  • the additional information indication may be SIB1-PDCCH period and offset information.
  • the period and offset can be the period and offset of absolute time, for example, the period is 40ms and the offset is 10ms; it can also be the period and offset of relative time, for example, the transmission period of SIB1-PDCCH It is a multiple of the SS/PBCH BLOCK period. For example, when the SS/PBCH BLOCK cycle is 20ms, the IAB node can use (4,1) to represent the cycle and offset, and the obtained cycle and offset are (80ms, 20ms).
  • the information used to indicate the SIB1-PDCCH cycle and offset may be sent by the Donor node to the upper-level node, or may be sent by the IAB node to the upper-level node. If sent by a Donor node, there are two possibilities. First, the period information is determined by the Donor node and sent to the IAB node and the upper node; second, the period information is determined by the IAB node and reported to the Donor node, and then the Donor node informs the upper node.
  • the period information may be configured, and the default offset is used, for example, the offset is 0 by default.
  • the period of the SS/PBCH BLOCK can be based on the SS/PBCH BLOCK set (SS/PBCH burst set) configuration
  • the period can also be a period based on the SS/PBCH BLOCK configuration, or a period based on the SS/PBCH BLOCK group configuration.
  • the SS/PBCH BLOCK set represents all SS/PBCH BLOCKs in a half frame.
  • the upper node assumes that all SIB1-PDCCHs corresponding to the SS/PBCH and BLOCK of the IAB node DU have the same period and offset.
  • each SS/PBCH BLOCK may have an independent period and offset; when the period is based on the SS/PBCH BLOCK group configuration, the SS/PBCH BLOCK in a group has The same period and offset, but different groups of SS/PBCH BLOCK have independent periods and offsets.
  • the additional period is configured based on the SS/PBCH BLOCK set or SS/PBCH BLOCK group
  • the additional offset is configured based on the SS/PBCH BLOCK group or SS/PBCH BLOCK.
  • the upper-level node may obtain the actual transmitted SS/PBCH BLOCK index of the IAB node AC-SSB through other signaling, and the SIB1 and SS/PBCH BLOCKB indexes are in a one-to-one correspondence. Therefore, for the SS/PBCH BLOCK index for which SS/PBCH BLOCK has not been sent, the upper-level node can assume that the IAB node DU does not send its corresponding SIB1.
  • the upper-level node After obtaining the actual SIB1-PDCCH cycle and offset, the upper-level node assumes that the IAB node DU uses this cycle and offset to send the SIB1-PDCCH.
  • the IAB node DU can use this period and offset to send SIB1-PDCCH, but the IAB node DU can also use other periods and offsets to send SIB1-PDCCH, but the IAB node DU should ensure that the transmission is not possible. It will conflict with the receiving and sending of its MT.
  • the resource location determined according to this period and offset is the resource location of the upper node assuming that the IAB node DU sends the SIB1-PDCCH, and it is not necessarily the actual resource location of the IAB node DU sending the SIB1-PDCCH.
  • the upper-level node determines the time domain position of the IAB node DU to send the SIB1-PDCCH according to the time domain position, period, and offset information of the SIB1-PDCCH to be sent every 40ms, but in fact the IAB node DU sends The time domain position of SIB1-PDCCH is sent every 80ms. (Assuming that the user equipment UE in Figure 8 detects SIB1-PDCCH every 20ms)
  • SIB1-PDCCH and SIB1-PDSCH are both time-division multiplexed with SS/PBCH BLOCK.
  • the SIB1-PDCCH monitoring period of pattern1 is 20ms instead of the SS/PBCH BLOCK period.
  • the terminal device determines the slot number of the SIB1-PDCCH, it will continuously monitor the PDCCH in two consecutive slots.
  • the IAB node DU may only send SIB1-PDCCH in one of the time slots. Therefore, the IAB node or the Donor node can also send the specific time slot information (for example, one of two consecutive time slots) of the IAB node DU to send the SIB1-PDCCH to the superior node.
  • the upper-level node regards these resources as hard resources of the IAB DU, and correspondingly, regards these resources as unavailable resources of the IAB MT function.
  • the upper-level node obtains the time-frequency resources of the SIB1-PDSCH of the IAB node DU.
  • the multiplexing patterns of SS/PBCH BLOCK and SIB1 are pattern2 and pattern3
  • the PDSCH and SS/PBCH BLOCK are both frequency-divided.
  • the time domain resources of the PDSCH of pattern2 and pattern3 can refer to the time domain resources of SS/PBCH BLOCK, so only Consider the case where the multiplexing pattern is pattern1.
  • the actual transmission position of SIB1-PDSCH is determined by the scheduling of SIB1-PDCCH.
  • the IAB node DU can schedule the SIB1-PDSCH to the hard resource indicated by the resource configuration.
  • the configured hard resources may not be enough to transmit all SIB1-PDSCH. In this case, an additional mechanism is needed to ensure the smooth transmission of SIB1-PDSCH.
  • the hard resources of the IAB DU account for no less than X% in the configuration period, and the value of X can be defined by the protocol, or can be requested by the IAB node from the superior node or the Donor node.
  • the IAB node or the Donor node informs the superior node that the IAB node schedules the time domain information of the SIB1-PDSCH.
  • the IAB node may report the time domain parameters used by the SIB1-PDCCH to schedule the SIB1-PDSCH, that is, the time domain resource assignment (Time Domain Resource Assignment) in the downlink control channel (downlink control information, DCI).
  • the upper-level node can determine the extra hard resource of the IAB node DU.
  • an embodiment of the present application provides a communication method 1000, including:
  • the first node is an integrated access backhaul IAB node
  • the second node is an upper node of the first node
  • the third node is a donor node.
  • the embodiment of the application obtains the time domain resource of SIB1 based on the time domain resource of SS/PBCH BLOCK, which saves signaling overhead compared to directly reporting the time domain resource of SIB1.
  • the configuration information includes SS/PBCH BLOCK time-frequency information
  • SS/PBCH BLOCK time-domain information includes SS/PBCH BLOCK transmission period, offset, SS/PBCH BLOCK index, SS/PBCH BLOCK frequency Domain information.
  • the Donor node or the IAB node sends the CORESET configuration of the PDCCH of the SIB1 to the superior node.
  • the configuration information includes: the CORESET configuration of the search space occupied by the PDCCH of the SIB1, and the CORESET configuration includes one or more of the following information:
  • the IAB node or the Donor node directly sends the CORESET configuration of SIB1-PDCCH to the upper node, so that the upper node can obtain the frequency domain information of SIB1 and the multiplexing pattern information of SIB1 and SS/PBCH BLOCK, and then obtain the time frequency domain information of SIB1 .
  • the CORESET configuration of SIB1-PDCCH is encapsulated in a main information block (main system information, MIB) and sent, and the corresponding parameter is pdcch-ConfigSIB1.
  • the upper-level node obtains the configuration information of the SIB1-PDCCH (pdcch-ConfigSIB1 and the subcarrier interval of the SIB1-PDCCH) through the MIB.
  • the configuration information the CORESET information of SIB1-PDCCH (including multiplexing patterns (pattern1,2,3), the number of RBs occupied by CORESET, the number of symbols occupied by CORESET, etc.) and monitoring opportunity (monitoring occasion) information (or Search space information)
  • the detection opportunity information includes the frame position, slot position, and symbol position occupied by the SIB1-PDCCH monitoring opportunity corresponding to each SSB.
  • the Donor node or the IAB node does not need to send the CORESET configuration of the SIB1 PDCCH to the IAB node, and look up the table through the table stored by the second node, and according to the subcarrier interval, index, minimum channel bandwidth and other information , Obtain the specific CORESET configuration of the PDCCH of SIB1.
  • the second node stores one or more tables, and each of the one or more tables records the following information:
  • the configuration information also includes the sub-carrier interval of SS/PBCH BLOCK and the sub-carrier interval of SIB1 (also referred to as the sub-carrier interval of the PDCCH scheduling SIB1, or the sub-carrier interval of the search space CORESET of scheduling SIB1).
  • the configuration information also includes: the minimum channel bandwidth occupied by the first node DU.
  • the second node determines the first table of the one or more tables based on the subcarrier interval of the SIB1 and the subcarrier interval of SS/PBCH BLOCK and/or the minimum channel bandwidth occupied by the first node DU;
  • the second node receives a first index, where the first index indicates a CORESET configuration occupied by the PDCCH of SIB1;
  • the CORESET configuration occupied by the PDCCH of the SIB1 is determined from the first table.
  • the CORESET configuration of SIB1 is obtained by storing the CORESET configuration table of SIB1, and the CORESET configuration of SIB1 is obtained according to the index information, which saves signaling overhead compared with directly sending the CORESET configuration of SIB1.
  • the upper-level node when the subcarrier spacing of the SS/PBCH BLOCK is the same, the tables corresponding to different minimum channel bandwidths are different. Therefore, the upper-level node also needs to know the minimum channel bandwidth occupied by the first node DU, where the minimum channel bandwidth is 5Mhz, 10Mhz, or 40Mhz.
  • the second node pre-stores one or more tables, and each of the one or more tables records a configuration index, frequency domain information of SIB1, and the SS/PBCH BLOCK and SIB1 complex Use pattern information; determine the frequency domain information of the SIB1 and the multiplexing pattern information of the SIB1 and SS/PBCH BLOCK according to the configuration index received from the Donor node or the IAB node and the one or more tables; The time domain information of the SS/PBCH BLOCK and the multiplexing pattern information of the SIB1 and the SS/PBCH BLOCK are used to obtain the time domain information of the SIB1.
  • the second node can pre-store the following tables from Table 13-1 to Table 13-11 (the following table is only an example, the table that may be stored in actual implementation is different from the values exemplified in this embodiment), based on The pre-stored table and the obtained configuration information of SIB1-PDCCH obtain the time domain position of SIB1.
  • the second node can obtain the multiplexing pattern of SS/PBCH BLOCK and SIB1 as 3.
  • the frequency domain information of SIB1 includes that the number of RBs of SIB1 is 24, the number of symbols of SIB1 is 2, and the RB offset is -20 or -21.
  • the terminal equipment can obtain the time domain of SIB1 according to the time domain position of SS/PBCH BLOCK position.
  • the time domain location information of SS/PBCH BLOCK can be obtained by referring to the above description, which will not be repeated here.
  • the frequency domain information of SIB1 includes that the number of RBs of SIB1 is 48, the number of symbols of SIB1 is 1, and the RB offset is -41 or -42.
  • the terminal equipment can obtain the PDSCH time domain position of SIB1 according to the time domain position of SS/PBCH BLOCK.
  • the time domain location information of SS/PBCH BLOCK can be obtained by referring to the above description, which will not be repeated here.
  • the time domain position of SIB1-PDCCH needs further instructions.
  • the PDCCH transmission cycle of SIB1 is twice the SS/PBCH BLOCK cycle
  • the offset can be the number of time slots offset in the time domain or the number of OFDM symbols.
  • the second node when the SS/PBCH BLOCK subcarrier interval is 15kHz, the CORESET subcarrier interval is 15kHz, and the minimum channel bandwidth is 5MHz or 10MHz, corresponding to Table 13-1, when the index is 0, the second node can obtain SS/PBCH
  • the multiplexing pattern of BLOCK and SIB1 is 1, and the frequency domain information of SIB1 includes the number of RBs is 24, the number of symbols is 2, and the frequency domain offset is 2RB.
  • the second node can be based on the time domain position of SS/PBCH BLOCK, and SIB1 relative to SS/PBCH BLOCK To determine the time domain position of SIB1.
  • time domain location information of SS/PBCH and BLOCK please refer to the above description, which will not be repeated here.
  • SIB1-PDCCH Due to the particularity of pattern1, for pattern1, after the terminal device determines the slot number of SIB1-PDCCH, it will continuously perform PDCCH monitoring in two consecutive slots.
  • IAB DU can only be used in one of them. SIB1-PDCCH is sent in the slot. Therefore, the IAB node or the superior node can also send the specific time slot in which the SIB1-PDCCH is sent to the superior node.
  • Table 13-1 Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 15,15 ⁇ kHz for frequency bands with minimum channel bandwidth 5MHz or 10MHz
  • Table 13-2 Set of resources blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 15,30 ⁇ kHz for frequency bands with minimum channel bandwidth 5MHz or 10MHz
  • Table 13-3 Set of resources blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 30,15 ⁇ kHz for frequency bands with minimum channel bandwidth 5MHz or 10MHz
  • Table 13-4 Set of resources blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 30,30 ⁇ kHz for frequency bands with minimum channel bandwidth 5MHz or 10MHz
  • Table 13-5 Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 30,15 ⁇ kHz for frequency bands with minimum channel bandwidth 40MHz
  • Table 13-6 Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 30,30 ⁇ kHz for frequency bands with minimum channel bandwidth 40MHz
  • Table 13-7 Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 120,60 ⁇ kHz
  • Table 13-8 Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 120,120 ⁇ kHz
  • Table 13-9 Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 240,60 ⁇ kHz
  • Table 13-10 Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when ⁇ SS/PBCH block,PDCCH ⁇ SCS is ⁇ 240,120 ⁇ kHz
  • the upper-level node obtains the time-frequency resource of the IAB node DU that may send SIB1, and further needs to obtain the time-frequency resource of the IAB node DU actually sending SIB1.
  • the information indication may be information about the period and offset of the SIB1-PDCCH (the offset is not necessary, and may only indicate the period of the SIB1-PDCCH).
  • the period and offset can be the period and offset of absolute time, for example, the period is 40ms and the offset is 10ms; it can also be the period and offset of relative time, for example, the transmission period of SIB1-PDCCH It is a multiple of the SS/PBCH BLOCK period. For example, when the SS/PBCH BLOCK cycle is 20ms, the IAB node can use (4,1) to represent the cycle and offset, and the obtained cycle and offset are (80ms, 20ms).
  • the information used to indicate the SIB1-PDCCH cycle and offset may be sent by the Donor node to the upper-level node, or may be sent by the IAB node to the upper-level node. If sent by a Donor node, there are two possibilities. First, the period information is determined by the Donor node and sent to the IAB node and the upper node; second, the period information is determined by the IAB node and reported to the Donor node, and then the Donor node informs the upper node.
  • the period information may be configured, and the default offset is used, for example, the offset is 0 by default.
  • the upper-level node obtains the time-domain resources of the SIB1 of the IAB node DU, and accordingly treats these time-domain resources as unavailable resources of the MT of the IAB node, that is, the upper-level node does not report the time domain resources to the IAB node
  • the MT sends downlink signals to avoid resource conflicts.
  • the methods and operations implemented by the IAB node or an upper-level node may also be implemented by components (for example, a chip or a circuit) that can be used for the IAB node or an upper-level node.
  • each network element such as the first node and the second node, includes hardware structures and/or software modules corresponding to each function in order to implement the above functions.
  • this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application can divide the first node and the second node into functional modules according to the foregoing method examples, for example, can be divided into various functional modules, or two or more functions can be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation. It should be understood that the second node may be an IAB node or a Donor node.
  • FIG. 11 is a schematic diagram of a possible structure of a node 1100 involved in the foregoing embodiment provided by this application.
  • the node 1100 includes a transceiving unit 1110 and a processing unit 1120.
  • the transceiving unit 1110 can communicate with the outside, and the processing unit 1120 is used for data processing.
  • the transceiver unit 1110 may also be referred to as a communication interface or a communication unit.
  • the node 1100 may be used to perform the actions performed by the IAB node in the above method embodiment, or may also perform the actions performed by the upper node of the IAB node in the above method embodiment.
  • the transceiver unit 1110 is configured to perform operations related to the transmission and reception of an IAB node or an upper-level node; the processing unit 1120 is configured to perform operations related to data processing of an IAB node or an upper-level node.
  • the transceiver unit 1110 is configured to: receive configuration information from a first node or a third node, the configuration information indicating time-frequency information of the system information block 1SIB1 of the first node distributed unit DU; processing The unit 1120 is configured to determine the unavailable resources of the MT function of the mobile terminal of the first node based on the acquired time-frequency information of the SIB1 of the first node DU.
  • the transceiver unit 1110 is configured to report configuration information to the second node, where the configuration information indicates the time-frequency information of the SIB1; wherein, the first node is an integrated access backhaul IAB node, and the first node is an integrated access backhaul IAB node.
  • the second node is an upper-level node of the first node.
  • the processing unit 1120 is configured to determine the time-frequency information of the system information block 1SIB1 of the distributed unit DU.
  • the configuration information may include SS/PBCH BLOCK time domain information, and the synchronization signal/physical broadcast channel SS/PBCH BLOCK time domain information includes the period and offset of the SS/PBCH BLOCK.
  • the configuration information further includes: the CORESET configuration of the search space occupied by the PDCCH of the SIB1, and the CORESET configuration includes one or more of the following information:
  • the node further includes a storage unit for storing one or more tables, and each of the one or more tables records the following information:
  • the transceiving unit is further configured to receive the subcarrier spacing of the SIB1 and the subcarrier spacing of SS/PBCH BLOCK, and a first index, where the first index indicates a type of SIB1 PDCCH occupied CORESET configuration;
  • the processing unit is configured to determine the first table in the one or more tables based on the subcarrier spacing of the SIB1 and the subcarrier spacing of the SS/PBCH BLOCK; and, based on the first index, from all The CORESET configuration occupied by the PDCCH of SIB1 is determined in the first table.
  • the configuration information further includes: the subcarrier interval of SS/PBCH BLOCK, and the subcarrier interval of SIB1.
  • the configuration information further includes: the minimum channel bandwidth occupied by the DU of the first node.
  • the configuration information further includes: information indicating the period and offset of the SIB1.
  • transceiver unit 1110 is further configured to send or receive the configuration information through radio resource control RRC signaling or interface message F1-AP.
  • the transceiver unit 1110 is further configured to report the time domain parameters of the physical downlink shared channel PDSCH of the DU scheduling SIB1 to the second node.
  • the time domain parameter includes the time domain resource assignment in the downlink control information.
  • processing unit 1120 in the above embodiment may be implemented by a processor or a processor-related circuit
  • transceiver unit 1110 may be implemented by a transceiver or a transceiver-related circuit.
  • an embodiment of the present application also provides a communication device 1200.
  • the communication device 1200 includes a processor 1210, a memory 1220, and a transceiver 1230.
  • the memory 1210 stores a program.
  • the processor 1210 is configured to execute the program stored in the memory 1220, and execute the program stored in the memory 1220 so that the processor 1210 uses In executing the relevant processing steps in the above method embodiment, the execution of the program stored in the memory 1220 enables the processor 1210 to control the transceiver 1230 to perform the receiving and sending related steps in the above method embodiment.
  • the communication device 1200 is configured to perform the actions performed by the first node, the second node, or the third node in the above method embodiment.
  • the execution of the program stored in the memory 1220 causes the processor 1210 is used to execute the processing steps on the first node or the second node or the third node in the above method embodiment, and execute the program stored in the memory 1220, so that the processor 1210 controls the transceiver 1230 to execute the above method embodiment
  • the chip When the communication device 1200 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input/output circuit or a communication interface
  • the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip.
  • the embodiment of the present application also provides a communication system, which includes the Donor node, the IAB node and the upper node of the IAB node in the above embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored.
  • the computer program When the computer program is executed by a computer, the computer realizes the method on the terminal device side or the method on the location management device side in the above method embodiment.
  • the embodiment of the present application also provides a computer program product containing instructions, which when executed by a computer causes the computer to implement the method on the terminal device side or the method on the location management device side in the foregoing method embodiments.
  • the nodes mentioned in the embodiments of this application include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through processes, for example, Linux operating system, Unix operating system, Android operating system, iOS operating system, or windows operating system.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the application do not specifically limit the specific structure of the execution subject of the methods provided in the embodiments of the application, as long as the program that records the codes of the methods provided in the embodiments of the application can be provided according to the embodiments of the application.
  • the method can be used for communication.
  • various aspects or features of the present application can be implemented as methods, devices, or products using standard programming and/or engineering techniques.
  • article of manufacture as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium.
  • computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks, or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
  • various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • machine-readable medium may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • processors mentioned in the embodiment of this application may be a central processing unit (Central Processing Unit, CPU), or may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), and application-specific integrated circuits ( Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

本申请实施例提供一种通信的方法及装置，包括：从第一节点或第三节点接收配置信息，所述配置信息指示所述第一节点分布式单元DU的SIB1的时频信息；基于获取的所述第一节点DU的SIB1的时频信息，确定所述第一节点移动终端MT功能的不可用资源；其中，第一节点为集成接入回传IAB节点，第二节点为所述第一节点的上级节点，第三节点为Donor节点。本申请提供的技术方案可以有效地避免IAB节点的MT功能和DU出现资源冲突。

Description

一种通信的方法和装置
本申请要求于2019年05月03日提交中国国家知识产权局、申请号为201910376533.2、申请名称为“一种通信的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术，具体涉及无线通信系统中一种通信的方法和装置。
背景技术
随着移动通信技术的不断发展，频谱资源日趋紧张。为了提高频谱利用率，未来的基站部署将会更加密集。此外，密集部署还可以避免覆盖空洞的出现。在传统蜂窝网络架构下，基站通过光纤与核心网建立连接。然而，光纤的部署成本非常高昂。无线中继节点(relay node,RN)通过无线回传链路与核心网建立连接，可节省部分光纤部署成本。
一般情况下，无线中继节点与一个或多个上级节点建立无线回传链路，并通过上级节点接入核心网。无线中继节点可为多个下级节点提供服务。中继节点的上级节点可以是基站，也可以是另一个中继节点；中继节点的下级节点可以是终端设备，也可以是另一个无线中继节点。
带内中继是回传链路与接入链路共享相同频段的中继方案，由于没有额外的频谱资源，带内中继具有频谱效率高及部署成本低等优点。带内中继一般具有半双工的约束，具体地，中继节点在接收其上级节点发送的下行信号时不能向其下级节点发送下行信号，而中继节点在接收其下级节点发送的上行信号时不能向其上级节点发送上行信号。第五代移动通信(5th generation mobile networks or 5th generation wireless systems，5G)无线接入网(radio access network,RAN)的新空口(new radio，NR)支持的中继方案被称为集成接入和回传(integrated access and backhaul,IAB)，而集成接入和回传的中继节点被称为IAB节点(IAB node)。
NR中的IAB节点包括两部分功能，移动终端(Mobile Termination，MT)功能与分布式单元(Distributed Unit,DU)。其中，MT用于IAB节点与上级节点通信，而DU用于IAB节点与下级节点通信，其中，上级节点可以是普通基站(如gNB)，也可以是另外的IAB节点；下级节点可以是终端设备，也可以是另外的IAB节点。
MT与上级节点通信的链路被称为上级回传链路(parent BackHaul link)，DU与下级IAB节点通信的链路被称为下级回传链路(child BackHaul link)，而DU与下属终端设备通信的链路被称为接入链路(access link)。在一些情况下，下级回传链路与接入链路可被统称为接入链路。
在IAB节点正常工作时，接入链路与回传链路以时分、空分或频分的方式进行资源复用。以时分复用为例，回传链路与接入链路在不同的时刻进行信号接收与发送。为了接入链路的正常工作，IAB节点需要频繁收发一些小区级的信号或信道，例如，同步信号/物理广播信道(Synchronization signal/physical broadcast channel，SS/PBCH)块、系统信息 (system information，SI)等。
当前，在新空口(New Radio，NR)标准的制订过程中提出了如下问题：如何避免IAB节点的DU的小区级信号的发送、接收与IAB节点的MT的传输冲突。
为达到避免资源冲突的目的，上级节点需要知道IAB节点DU发送小区级信号的时域资源。因此，上级节点如何获取IAB节点DU发送小区级信号的时域资源是当前亟需解决的问题。
发明内容
本申请的实施例提供一种通信方法及装置，使得上级节点可以获知IAB节点DU发送信号的时域资源，避免与IAB节点的MT传输冲突。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，本申请实施例提供一种通信的方法，包括：从第一节点或第三节点接收配置信息，所述配置信息指示所述第一节点分布式单元DU的系统信息块1SIB1的时频信息；基于获取的所述第一节点DU的SIB1的时频信息，确定所述第一节点移动终端MT功能的不可用资源；其中，第一节点为集成接入回传IAB节点，第二节点为所述第一节点的上级节点，第三节点为donor节点。
第二节点通过确定IAB节点的DU的硬资源，相应地，将该硬资源确定为IAB节点的MT不可用资源。如此一来，避免了IAB的MT在该硬资源上进行调度，避免了资源冲突。
在一种可能的实现方式中，所述配置信息具体包括：同步信号/物理广播信道SS/PBCH BLOCK的时域信息。通过SS/PBCH BLOCK的时域信息来获取SIB1的时域信息，不需要再额外的信令指示，可以减少信令开销。
在另一种可能的实现方式中，所述同步信号/物理广播信道SS/PBCH BLOCK的时域信息包括所述SS/PBCH BLOCK的周期以及偏移量。
在一种可能的实现方式中，所述配置信息还包括所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
在另一种可能的实现方式中，所述第二节点存储一个或多个表格，所述一个或多个表格中的每一个表格记录有如下信息：
索引，SS/PBCH BLOCK与SIB1的复用图案，SIB1的频域信息，SIB1的频域偏移量。
在另一种可能的实现方式中，所述配置信息还包括：SS/PBCH BLOCK的子载波间隔，以及，SIB1的子载波间隔。
在另一种可能的实现方式中，所述配置信息还包括：第一节点的DU所占用的最小信道带宽。
在另一种可能的实现方式中，所述方法还包括：
基于所述SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔，确定所述一个或多个表格中的第一表格；
所述第二节点接收第一索引，所述第一索引指示一种SIB1的PDCCH所占用的CORESET配置；
基于所述第一索引，从所述第一表格中确定SIB1的PDCCH所占用的CORESET配 置。
在另一种可能的实现方式中，所述配置信息还包括：指示所述SIB1的周期以及偏移量的信息。
在另一种可能的实现方式中，所述指示所述SIB1的周期的信息为SS/PBCH BLOCK的周期的倍数。
在另一种可能的实现方式中，所述配置信息还包括：第一节点DU的SIB1的PDCCH所占用的时隙。
在另一种可能的实现方式中，基于获取的所述第一节点DU的SIB1的时频信息，确定所述第一节点移动终端MT功能的不可用资源，具体包括：将所述第一节点DU的SIB1所占用的时频资源，确定为所述第一节点MT功能的不可用资源。
在另一种可能的实现方式中，通过无线资源控制RRC信令或者接口消息F1-AP接收所述配置信息。
在另一种可能的实现方式中，所述方法还包括：所述第二节点接收第一节点DU调度SIB1的物理下行共享信道PDSCH的时域参数。
在另一种可能的实现方式中，所述时域参数包括下行控制信息中的时域资源分配Time domain resource assignment。
第二方面，还提供一种通信的方法，包括：第一节点确定IAB节点的分布式单元DU确定系统信息块1SIB1的时频信息；向第二节点发送配置信息，所述配置信息指示所述SIB1的时频信息；其中，第一节点为集成接入回传IAB节点或Donor节点，第二节点为所述第一节点的上级节点。
一种可能的实现方式中，所述配置信息具体包括：同步信号/物理广播信道SS/PBCH BLOCK的时域信息。
另一种可能的实现方式中，所述同步信号/物理广播信道SS/PBCH BLOCK的时域信息包括所述SS/PBCH BLOCK的周期以及偏移量。
另一种可能的实现方式中，所述配置信息还包括：所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
另一种可能的实现方式中，所述配置信息还包括：SS/PBCH BLOCK的子载波间隔，以及，SIB1的子载波间隔。
在另一种可能的实现方式中，所述配置信息还包括：第一节点的DU所占用的最小信道带宽。
另一种可能的实现方式中，所述配置信息还包括：指示所述SIB1的周期以及偏移量的信息。
另一种可能的实现方式中，所述指示所述SIB1的周期的信息为SS/PBCH BLOCK的周期的倍数。
另一种可能的实现方式中，所述配置信息还包括：第一节点DU的SIB1的PDCCH所占用的时隙。
另一种可能的实现方式中，所述第二配置信息包括：通过无线资源控制RRC信令或者接口消息F1-AP发送所述配置信息。
另一种可能的实现方式中，所述第二配置信息还包括：所述方法还包括：所述第一节点向第二节点上报DU调度SIB1的物理下行共享信道PDSCH的时域参数。
另一种可能的实现方式中，所述时域参数包括下行控制信息中的时域资源分配Time domain resource assignment。
IAB节点的上级节点通过获取IAB节点DU的SIB1的时域资源，将该时域资源视为IAB节点DU的硬资源，对应地，IAB节点MT不可使用该时域资源进行收发，可以避免冲突。
第三方面，提供一种节点，包括：收发单元，用于从第一节点或第三节点接收配置信息，所述配置信息指示所述第一节点分布式单元DU的系统信息块1SIB1的时频信息；处理单元，用于基于获取的所述第一节点DU的SIB1的时频信息，确定所述第一节点移动终端MT功能的不可用资源；其中，第一节点为集成接入回传IAB节点，第三节点为Donor节点。
一种可能的实现方式，所述配置信息具体包括：同步信号/物理广播信道SS/PBCH BLOCK的时域信息。
另一种可能的实现方式，所述同步信号/物理广播信道SS/PBCH BLOCK的时域信息包括所述SS/PBCH BLOCK的周期以及偏移量。
另一种可能的实现方式，所述配置信息还包括：所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
另一种可能的实现方式，所述配置信息还包括：SS/PBCH BLOCK的子载波间隔，以及，SIB1的子载波间隔。
另一种可能的实现方式，所述配置信息还包括：第一节点的DU所占用的最小信道带宽。
另一种可能的实现方式，所述节点还包括存储单元，用于存储一个或多个表格，所述一个或多个表格中的每一个表格记录有如下信息：
索引，SS/PBCH BLOCK与SIB1的复用图案，SIB1的频域信息，SIB1的频域偏移量。
另一种可能的实现方式，所述收发单元，还用于获取SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔；以及，接收第一索引，所述第一索引指示一种SIB1的PDCCH所占用的CORESET配置；
所述处理单元，还用于基于所述SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔，确定所述一个或多个表格中的第一表格；以及，基于所述第一索引，从所述第一表格中确定SIB1的PDCCH所占用的CORESET配置。
另一种可能的实现方式，所述配置信息还包括：指示所述SIB1的周期以及偏移量的信息。
另一种可能的实现方式，所述指示所述SIB1的周期的信息为SS/PBCH BLOCK的周期的倍数。
另一种可能的实现方式，所述配置信息还包括第一节点DU的SIB1的PDCCH所占用的时隙。
另一种可能的实现方式，所述处理单元，用于将所述第一节点DU的SIB1所占用的 时频资源，确定为所述第一节点MT功能的不可用资源。
另一种可能的实现方式，所述收发单元，用于通过无线资源控制RRC信令或者接口消息F1-AP接收所述配置信息。
另一种可能的实现方式，所述收发单元，还用于：接收所述第一节点DU调度SIB1的物理下行共享信道PDSCH的时域参数。
另一种可能的实现方式，所述时域参数包括下行控制信息中的时域资源分配Time domain resource assignment。
IAB节点的上级节点通过获取IAB节点DU的SIB1的时域资源，将该时域资源视为IAB节点DU的硬资源，对应地，IAB节点MT不可使用该时域资源进行收发，可以避免冲突。
第四方面，还提供一种第一节点，包括：处理单元，用于确定IAB节点分布式单元DU的系统信息块1SIB1的时频信息；收发单元，用于向第二节点上报配置信息，所述配置信息指示所述SIB1的时频信息；其中，第一节点为集成接入回传IAB节点或Donor节点，第二节点为所述第一节点的上级节点。
一种可能的实现方式，所述配置信息具体包括同步信号/物理广播信道SS/PBCH BLOCK的时域信息。
另一种可能的实现方式，所述同步信号/物理广播信道SS/PBCH BLOCK的时域信息包括所述SS/PBCH BLOCK的周期以及偏移量。
另一种可能的实现方式，所述配置信息还包括所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
另一种可能的实现方式，所述配置信息还包括：SS/PBCH BLOCK的子载波间隔，以及，SIB1的子载波间隔。
另一种可能的实现方式，所述配置信息还包括第一节点的DU所占用的最小信道带宽。
另一种可能的实现方式，所述配置信息还包括指示所述SIB1的周期以及偏移量的信息。
另一种可能的实现方式，所述指示所述SIB1的周期的信息为SS/PBCH BLOCK的周期的倍数。
另一种可能的实现方式，所述配置信息还包括第一节点DU的SIB1的PDCCH所占用的时隙。
另一种可能的实现方式，所述收发单元，通过无线资源控制RRC信令或者接口消息F1-AP发送所述配置信息。
另一种可能的实现方式，所述收发单元，还用于向第二节点上报DU调度SIB1的物理下行共享信道PDSCH的时域参数。
另一种可能的实现方式，所述时域参数包括下行控制信息中的时域资源分配Time domain resource assignment。
在本申请的又一方面，提供了一种装置，所述装置用于实现上述第一方面的任一种可能的实现方式所提供的通信方法的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的单元。
在一种可能的实现方式中，所述装置的结构中包括处理器，该处理器被配置为支持该用户设备执行上述第一方面或第一方面的任一种可能的实现方式所提供的通信方法。可选的，所述装置还可以包括存储器和通信接口，该存储器中存储代码和数据，该存储器与处理器耦合，通信接口与处理器或存储器耦合。
在本申请的又一方面，提供了一种装置，所述装置用于实现上述第二方面或第二方面的任一种可能的实现方式所提供的通信方法的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的单元。
在一种可能的实现方式中，所述装置的结构中包括处理器，该处理器被配置为支持网络设备执行上述第二方面或第二方面的任一种可能的实现方式所提供的通信方法的功能。可选的，网络设备还可以包括存储器和通信接口，存储器中存储处理和/或基带处理器所需代码，存储器与处理器耦合，通信接口与存储器或处理器耦合。
本申请的又一方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得该计算机执行上述第一方面或第一方面的任一种可能的实现方式所提供的通信方法，或者执行上述第二方面或第二方面的任一种可能的实现方式所提供的通信方法。
本申请的又一方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得该计算机执行上述第一方面或第一方面的任一种可能的实现方式所提供的通信方法，或者执行上述第二方面或第二方面的任一种可能的实现方式所提供通信方法。
本申请的又一方面，提供一种通信系统，该通信系统包括第一节点、第二节点以及第三节点；其中，第一节点为上述各方面所提供的第一节点，用于支持第一节点执行上述第一方面或第一方面的任一种可能的实现方式所提供的通信方法；和/或，第二节点为上述各方面所提供的第二节点，用于支持第二节点执行上述第二方面或第二方面的任一种可能的实现方式所提供的通信方法；和/或，第三节点为上述各方面所提供的第三节点，用于支持第三节点执行上述第一方面或第一方面的任一种可能的实现方式所提供的通信方法。
可以理解，上述提供的通信方法的装置、计算机存储介质或者计算机程序产品均用于执行上文所提供的对应的方法，因此，其所能达到的有益效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
附图说明
图1为本申请实施例提供的IAB通信系统；
图2为本申请实施例提供的回传链路和接入链路的示意图；
图3为本申请实施例提供的hard资源和soft资源的示意图；
图4为本申请实施例提供的IAB节点MT和DU的资源分配示意图；
图5为本申请实施例提供的SS/PBCH BLOCK与SIB1的复用图案；
图6为本申请实施例提供的pattern 3的示意图；
图7为本申请实施例提供的pattern 2的示意图；
图8为本申请实施例提供的发送SIB1的示意图；
图9为本申请实施例提供的pattern 1的示意图；
图10为本申请实施例提供的一种通信方法交互示意图；
图11为本申请实施例提供的节点的一种可能的结构示意图；
图12为本申请实施例提供的节点的一种可能的逻辑结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例，基于本发明中的实施例，本领域技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B。本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。本申请实施例中的“包括A或B中的一个或多个”可以表示：包括A，包括A和B，包括B这三种情况。本申请实施例中的“包括A、B或C中的一个或多个”可以表示：包括A和B和C，包括A和B，包括A和C，包括B和C，包括A，包括B，包括C这7种情况。
应理解，本申请中所有节点、消息的名称仅仅是本申请为描述方便而设定的名称，在实际网络中的名称可能不同，不应理解本申请限定各种节点、消息的名称，相反，任何具有和本申请中用到的节点或消息具有相同或类似功能的名称都视作本申请的方法或等效替换，都在本申请的保护范围之内，以下不再赘述。
为了更好地理解本发明实施例公开的一种中继系统中资源确定的方法及装置，下面先对本发明实施例使用的网络架构进行描述。请参阅图1，图1为本申请实施例所适用的通信系统的结构示意图。
需要说明的是，本申请实施例提及的通信系统包括但不限于：窄带物联网(narrow band-internet of things，NB-IoT)系统、车联网、无线局域网(wireless local access network,WLAN)系统、LTE系统、5G移动通信系统，如NR、设备到设备(device to device，D2D)通信系统，或者，5G之后的下一代通信系统。
在图1所示的通信系统中，示出了集成接入和回传IAB系统结构图。一个IAB系统至少包括一个基站100，及基站100所服务的一个或多个终端设备(terminal)101，一个或多个中继节点IAB node，及该IAB node 110所服务的一个或多个终端设备111。通常基站100被称为宿主基站(donor next generation node B，DgNB)，IAB node 110通过无线回传链路113连接到基站100。宿主基站在本申请中也称为宿主节点，即，Donor节点。基站100包括但不限于：演进型节点B(evolved node base，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如，home evolved NodeB，或home node B，HNB)、基带单元(baseband Unit，BBU)、eLTE(evolved LTE,eLTE)基站、NR基站(next generation node B,gNB)等。终端设备包括但不限于：用户设备(user equipment，UE)、移动台、接入终端、用户单元、用户站、移动站、远方站、远程终端、移动设备、终端、无线通信设备、用户代理、无线局域网(wireless local access network,WLAN)中的站点(station，ST)、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备、连接到无线调制解调器的其 它处理设备、车载设备、可穿戴设备、未来5G网络中的移动台以及未来演进的公共陆地移动网络(public land mobile network,PLMN)网络中的终端设备等中的任意一种。IAB node是中继节点的特定的名称，不对本申请的方案构成限定，可以是一种具有转发功能的上述基站或者终端设备中的一种，也可以是一种独立的设备形态。
集成接入回传系统还可以包括多个其他IAB node，例如IAB node 120和IAB node 130，IAB node 120是通过无线回传链路123连接到IAB node 110以接入到网络的，IAB node 130是通过无线回传链路133连接到IAB node 110以接入到网络的，IAB node 120为一个或多个终端设备121服务，IAB node 130为一个或多个终端设备131服务。图1中，IAB node 110和IAB node 120都通过无线回传链路连接到网络。在本申请中，所述无线回传链路都是从中继节点的角度来看的，比如无线回传链路113是IAB node 110的回传链路，无线回传链路123是IAB node 120的回传链路。
如图1所示，一个IAB node，如120，可以通过无线回传链路，如123，连接另一个IAB node 110，从而连接到网络，而且，中继节点可以经过多级无线中继节点连接到网络。应理解，本申请中用IAB node仅仅出于描述的需要，并不表示本申请的方案仅用于NR的场景，在本申请中，IAB node可以泛指任何具有中继功能的节点或设备，本申请中的IAB node和中继节点的使用应理解具有相同的含义。比如，IAB节点可以为基站、传输接收点TRP，设置在移动物体上的模块或者装置，移动物体包括但不限于物联网中的设备，例如，汽车、火车、飞机等。
通常，下级节点可以被看作是上级节点的一个终端设备。应理解，图1所示的集成接入回传系统中，一个IAB node连接一个上级节点。但是在未来的中继系统中，为了提高无线回传链路的可靠性，一个IAB node，如120，可以有多个上级节点同时为一个IAB node提供服务。如图中的IAB node 130还可以通过回传链路134连接到IAB node 120，即，IAB node 110和IAB node 120都为IAB node 130的上级节点。IAB node 110,120，130的名称并不限制其所部署的场景或网络，可以是比如relay，RN等任何其他名称。本申请使用IAB node仅是方便描述的需要。
在图1中，无线链路102,112,122,132,113,123，133,134可以是双向链路，包括上行和下行传输链路，特别地，无线回传链路113,123，133,134可以用于上级节点为下级节点提供服务，如上级节点100为下级节点110提供无线回传服务。应理解，回传链路的上行和下行可以是分离的，即，上行链路和下行链路不是通过同一个节点进行传输的。所述下行传输是指上级节点，如节点100，向下级节点，如节点110,传输信息或数据，上行传输是指下级节点，如节点110，向上级节点，如节点100，传输信息或数据。所述节点不限于是网络节点还是终端设备，例如，在D2D场景下，终端设备可以充当中继节点为其他终端设备服务。无线回传链路在某些场景下又可以是接入链路，如回传链路123对节点110来说也可以被视作接入链路，回传链路113也是节点100的接入链路。对于节点110来说，链路113被称为上级回传链路(parent BH)，链路123被称为下级回传链路(child BH)，而链路112被称为接入链路。应理解，上述上级节点可以是基站，也可以是中继节点，下级节点可以是中继节点，也可以是具有中继功能的终端设备，如D2D场景下，下级节点也可以是终端设备。
图1所示的中继节点，如110,120，130，可以有两种存在的形态：一种是作为一个独 立的接入节点存在，可以独立管理接入到中继节点的终端设备，此时的中继节点通常具有独立的物理小区标识(physical cell identifier，PCI)，这种形态的中继通常需要有完全的协议栈功能，比如无线资源控制(radio resource control，RRC)的功能，这种中继通常被称为层3中继；而另一种形态的中继节点和Donor节点，如Donor eNB，Donor gNB，属于同一个小区，用户的管理是由宿主基站，如Donor节点来进行管理的，这种中继通常被称为层2中继。
层2中继在NR的控制和承载分离(central unit and distributed unit,CU-DU)架构下通常作为基站DgNB的DU而存在，通过F1-AP(F1 application protocol)接口或者隧道协议和CU进行通信。其中隧道协议可以是例如GTP(general packet radio service tunneling protocol,GTP)协议,F1-AP可以是F1-AP增强接口，不再赘述。
Donor节点是指通过该节点可以接入到核心网的节点，或者是无线接入网的一个锚点基站，通过该锚点基站可以接入到网络。锚点基站负责接收核心网的数据并转发给中继节点，或者接收中继节点的数据并转发给核心网。
为描述方便，以下解释本申请中用到的基本术语或概念。
上级节点：提供无线回传链路资源的节点，如110，称为IAB node 120的上级节点。上级节点也可以称为上游节点。应理解，上级节点不限于提供无线回传链路资源的直接上级节点，包括所有提供到宿主基站的传输的链路上提供无线回传链路资源的节点。直接上级节点是指为中继节点直接提供传输资源的节点，如，IAB node 110为IAB node 120的直接上级节点。
下级节点：使用回传链路资源向网络进行数据传输，或者接收来自网络的数据的节点称为下级节点。如，120则称为中继节点110下级节点，网络为核心网或者其他接入网之上的网络，如因特网，专网等。类似的，下级节点不限于为其提供无线回传链路资源的直接下级节点，包括所有提供到目标节点的传输的链路上提供无线回传链路资源的节点。直接下级节点是指为其直接提供传输资源的节点，如，IAB node 120为IAB node 110的直接下级节点。
接入链路：UE和IAB node，或UE和IAB宿主节点(IAB Donor)之间的链路。或者，接入链路包括某个节点和它的下级节点进行通信时所使用的无线链路。接入链路包括上行接入链路和下行接入链路。上行接入链路也被称为接入链路的上行传输，下行接入链路也被称为接入链路的下行传输。
回传链路：IAB node和IAB子节点(IAB child node)，或者IAB node和IAB父节点(IAB parent node)之间的链路。回传链路包括IAB节点和IAB子节点，或IAB节点和IAB父节点的下行传输的链路；回传链路还包括IAB节点和IAB子节点，或IAB节点和IAB父节点的上行传输的链路。IAB节点向IAB父节点进行数据传输，或者接收IAB子节点的上行传输被称为回传链路的上行传输。IAB节点接收IAB父节点的数据传输，或者向IAB子节点进行的数据传输被称为回传链路的下行传输。为了对UE和IAB节点进行区分，IAB节点与IAB父节点之间的回传链路被又称为上级回传链路(parent BH)，而IAB节点与IAB子节点之间的回传链路被称为下级回传链路(child BH)。
在NR中，IAB节点包括两个主要功能，一个是移动终端(mobile-termination,MT)功能，另一个是分布式单元(distributed unit，DU)功能。IAB节点在MT上可以和上级 节点进行上行传输和/或下行传输。IAB节点在DU上可以和下级节点进行上行传输和/或下行传输。
图2示出了IAB节点上下级节点示意图。如图2所示，上级回传DL为上级节点向IAB节点发送下行信号的链路；上级回传UL为IAB节点向上级节点发送上行信号的链路；下级回传DL为IAB节点向下级节点发送下行信号的链路；下级回传UL为下级节点向IAB节点发送上行信号的链路；接入UL为终端设备向IAB节点发送上行信号的链路；接入DL为IAB节点向终端设备发送下行信号的链路。
图3是NR中IAB节点的资源配置的示意图。图3以时分双工(time division duplex,TDD)为例，其中，IAB节点的MT资源可以被配置为下行(downlink，D)，上行(uplink，U)，灵活(Flexible，F)三种类型。其中F类型的资源可以被配置为上行或下行传输，具体用于上行传输还是下行传输依赖于信令配置。
IAB节点的DU资源可以被配置为下行，上行，灵活和不可用(Null,N)四种类型。进一步地，DU的下行，上行，灵活三种类型的资源还可以被分为硬(hard,H)资源和软(soft,S)资源。其中，DU的hard资源，表示DU始终可用的资源。DU的soft资源，表示DU是否可用需要依赖于上级节点(例如donor节点)的指示。图3中，上级节点通过在下行时隙或子帧上的下行控制信息(downlink control information,DCI)来对IAB节点DU上的S资源的使用进行控制。而H资源和S资源则是宿主基站或上级节点通过RRC进行半静态配置的，或者宿主基站通过F1-AP协议来进行半静态配置的。
IAB节点的MT与上级节点的DU相连接，而IAB节点的DU与下级节点的MT相连接。在经过半静态(例如，通过RRC信令)的资源配置以后，IAB节点可以分别得到其MT资源和DU资源的资源配置。例如，可以包括MT资源和DU资源的传输方向(D/U/F)，DU资源的类型(soft/hard)，DU的NULL资源的位置等。
结合图3以及下面的表1可以看出，对于IAB节点，其DU的hard资源(例如，第1、6、7、8时隙对应的DU资源)所对应的MT资源(例如，第1、6、7、8时隙对应的MT资源)为不可用。应理解，图3中的时隙编号也可以是子帧编号或符号编号，以下主要以时隙为例进行说明，不再赘述。
具体地，结合前面的介绍，IAB节点的MT共有三种类型的资源，而IAB节点的DU共有7种类型的资源，两两组合后，IAB节点的MT以及其对应的DU可能的收发状况如下面的表1和表2所示，其中表1为时分复用场景下的MT以及DU的各种可能的资源类型组合下的资源配置情况。表2为空分复用(spatial division multiplexing,SDM)场景下的MT以及DU的各种可能的资源类型组合下的资源配置情况。
表1
Figure PCTCN2020075799-appb-000001
Figure PCTCN2020075799-appb-000002
表2
Figure PCTCN2020075799-appb-000003
Figure PCTCN2020075799-appb-000004
在以上表1和表2中，各标识的含义如下：
“MT:Tx”表示MT在被调度后应进行传输；
“DU:Tx”表示DU可以进行传输；
“MT:Rx”表示MT有能力进行接收(如果有信号需要接收)；
“DU:Rx”表示DU可以调度下级节点的上行传输；
“MT:Tx/Rx”表示MT在被调度后应传输或接收，但传输和接收不同时发生；
“DU:Tx/Rx”表示DU可以进行传输或接收下级节点的传输，但传输和接收不同时发生；
“IA”表示DU资源被显式或隐式的指示为可用；
“INA”表示DU资源被显式或隐式的指示为不可用；
“MT:NULL”表示MT不进行发送且不必具有接收能力；
“DU:NULL”表示DU不进行发送且不接收下级节点的传输。
本申请主要考虑TDM的场景，但本申请方案也可扩展至SDM，频分多路复用(frequency-division multiplexing,FDM)或全双工等场景。对于TDM场景，DU的hard资源所对应的MT资源为不可用。
具体地，在MT的不可用资源上：
(1)MT不期望上级节点会在这些资源上对其进行调度；
(2)MT不在这些资源上进行参考信号的接收或发送；
(3)MT不在这些资源上进行物理下行控制信道(physical downlink control channel,PDCCH)监测，即如果搜索空间与这些资源出现重合，则IAB节点的MT放弃重合的搜索空间监测。
应理解，除了DU hard资源对应的MT不可用资源，MT还可能具有其余不可用资源。
在上述半静态配置完成后，上级节点会继续通过动态信令(例如，下行控制信息(downlink control information,DCI))为IAB节点动态指示其DU资源的soft类型资源的可用性，例如，上级节点采用专用的DCI或专用的DCI字段对IAB节点的soft资源的可用性加以指示，为了方便描述，将动态信令包含的信息称为指示信息，将上述专用的DCI或专用的DCI字段可以统称为指示DCI。
上述动态指示可以通过多种方式实现。
在一种实现中，可以通过显式指示的方式进行。
例如，上级节点直接指示IAB节点DU资源的soft类型资源的可用性，此外，还可以同时指示部分(例如F类型)soft资源的传输方向等。
在另一种实现中，可以通过隐式指示的方式进行。
例如，上级节点指示IAB节点的MT资源(例如MT的可用资源)是否被释放(或者说，是否可用)，IAB节点根据上级节点对上述MT资源的指示，确定自身的DU资源的soft类型资源的可用性。
当IAB节点的DU被配置为hard资源时，通常IAB节点在配置为hard资源的时隙上进行完整的传输。所述完整的传输的含义是IAB节点认为被配置为hard资源的时隙上的所有符号都是可用的。此外，IAB节点的hard资源可以被认为始终可用的资源。对于一个DU hard资源，IAB节点始终可以在此资源上与下级节点进行通信，而不用考虑MT的调度配置情况。或者说，上级节点与IAB节点MT之间的通信不应该影响DU在hard资源处与下级节点或UE的通信。
在一种实现中，IAB节点DU的部分周期信号，包括但不限于周期性CSI-RS，SRS，由Donor节点配置并通过RRC信令通知IAB节点的终端设备或下级节点。此时，Donor节点为IAB节点配置的这部分周期信号应位于IAB节点DU的hard资源。
图4为本申请实施例提供的DU的Hard/Soft资源与MT的可用或不可用资源的关系示意图。图4中以符号为例。其中，H符号表示Hard资源，S符号表示Soft资源，A表示可用资源，NA表示不可用资源。应理解，图4仅是一个示例，其中，0,1,2,3,4,5,6可以表示符号也可以表示时隙或子帧。
示例性的，图4给出了7个符号，其中，符号0和符号6为DU的Hard资源，DU始终可使用符号0和符号6。图4中假设IAB节点的MT和DU之间是以时分复用TDM方式进行资源分配的，则对于MT来说，符号0和符号6为不可用资源。图中的符号1至5为DU的soft符号，对于MT来说，符号1至符号5为可用资源。
在NR IAB目前的讨论中，提出了如下问题：如何避免IAB节点DU的小区级信号(cell-specific signal)或信道的收发与IAB节点MT功能的传输冲突。具体地，为了保证 接入链路的正常工作，IAB节点DU应能够对cell-specific信号进行收发，在IAB节点DU对cell-specific信号进行收发时，上级节点不应再调度IAB节点MT功能。
为解决上述冲突，可以有以下两个具体方案解决冲突：
方案1：在资源配置时，将所有发送cell-specific信号或信道的资源配置为hard资源；
方案2：当cell-specific信号或信道使用非hard资源时，将此资源转换为hard资源，或者，将此资源视为hard资源。
由于cell-specific信号可能具有较大的周期，方案1可能严重制约资源分配的灵活性，因此方案2是更优的选项。
对于方案2，为达到避免资源冲突的目的，上级节点需要知道IAB节点DU发送cell-specific信号的时域资源。因此，本发明要解决的问题是上级节点如何获取IAB节点DU发送cell-specific信号的时域资源。
其中，cell-specific信号可以是如下信号中一种：
同步信号/物理广播信道(Synchronization Signal/physical broadcast channel，SS/PBCH)块(也可以简称为SSB)、系统信息块(system information block，SIB)、信道状态信息参考信号(channel state information reference signal，CSI-RS)、随机接入信道(Random Access Channel，RACH)、探测参考信号(sounding reference signal，SRS)、调度请求(scheduling request，SR)。
本申请实施例主要介绍上级节点如何获取IAB节点DU发送SIB1和SS/PBCH BLOCK的时频资源，其他几种cell-specific信号可以参考本申请的方案。上级节点获知IAB节点DU的cell-specific信号的时频资源后，将DU所占用的资源视为IAB节点DU的hard资源。相应地，IAB节点的MT不再使用该资源进行传输。或者，IAB节点不期望上级节点在此资源对其MT进行调度，或者，上级节点调度IAB节点MT的传输不影响DU对hard资源的使用。
首先介绍上级节点如何获取IAB节点或下级节点的SS/PBCH BLOCK(也可以表示为SSB)的时域资源。
IAB节点DU可能发送两种类型的SS/PBCH BLOCK，一种用于终端设备接入的SS/PBCH BLOCK，可被称为cell-defining SS/PBCH BLOCK或者接入SS/PBCH BLOCK(AC-SSB)，另一种用于IAB节点相互测量的SS/PBCH BLOCK，可被称为回传SS/PBCH BLOCK(BH-SSB)。一般情况下，两种SS/PBCH BLOCK处于不同的时域位置。
对于AC-SSB，IAB节点的DU会通过RRC消息向终端设备或下级节点发送SS/PBCH BLOCK的时频信息。该RRC信息一般由Donor节点生成，因此，Donor节点可以将AC-SSB的时域信息发送至所述上级节点；或者，由IAB节点向上级节点上报AC-SSB的时频信息，该时频信息包括SS/PBCH BLOCK周期，半帧内发送SS/PBCH的索引，和/或SS/PBCH BLOCK相对于起始位置的偏移量等。
可选的，当上级节点未获取到IAB节点DU的AC-SSB的时频信息时，上级节点可以假设IAB节点DU发送的SS/PBCH BLOCK的至少部分参数(例如SS/PBCH BLOCK周期，偏移量)与自身相同。即，将IAB节点DU的AC-SSB的时频资源视为与该上级节点的SS/PBCH BLOCK的周期相同；或者，将IAB节点DU的AC-SSB的时频资源视为与该上级节点的SS/PBCH BLOCK的周期相同以及偏移量也相同。
可选的，上级节点可以假设IAB节点会在半帧内所有SS/PBCH BLOCK的可用资源进行发送(实际，IAB节点可能仅在部分可用时频资源进行发送)。
对于BH-SSB，Donor节点会向每个IAB节点发送BH-SSB的传输配置信息(SS/PBCH block transmission configuration，STC)。因此，Donor节点可以将IAB节点的BH-SSB传输配置发送给IAB节点的上级节点，或者，由IAB节点上报自身的STC给上级节点。其中，STC包括以下信息中的一项或多项：SS/PBCH BLOCK的发送周期、偏移量，子载波间隔，SS/PBCH BLOCK的索引，SS/PBCH BLOCK的频域信息。
综上所述，第一节点或第三节点向第二节点发送SS/PBCH BLOCK的时频配置信息，所述SS/PBCH BLOCK的时频配置信息包括SS/PBCH BLOCK的发送周期、偏移量。其中，第一节点为IAB节点，第三节点为Donor节点；第二节点为IAB节点的上级节点。
第二节点基于所述SS/PBCH BLOCK的时频配置信息，获知第三节点的DU发送SS/PBCH BLOCK的时频资源，进而在该对应的时频资源上，不向第三节点的MT发送下行信号，以避免冲突。
进一步地，所述SS/PBCH BLOCK的时频配置信息还包括SS/PBCH BLOCK的子载波间隔、SS/PBCH BLOCK在半帧内的索引、SS/PBCH BLOCK的频域信息。
在本实施例中，第二节点基于IAB节点DU的SS/PBCH BLOCK的时频信息，确定该IAB节点的DU发送SIB1的时频资源，进而，在该时频资源上，不向第三节点的MT功能发送下行信号，以避免IAB节点的MT功能和DU资源冲突。
需要说明的是，IAB节点DU发送BH-SSB可能与IAB节点MT接收SS/PBCH BLOCK在时域上发生冲突。为避免冲突，此时可能出现两种结果，IAB节点DU发送BH-SSB被静默，或者，IAB节点MT接收SS/PBCH BLOCK被静默。例如，当IAB节点DU发送BH-SSB被静默，表示，IAB节点的hard资源被某些特定的MT信号占用。
在一种可能的实现中，IAB节点MT接收SS/PBCH BLOCK的优先级高于IAB节点DU发送SS/PBCH BLOCK，因此，当SS/PBCH BLOCK的接收配置与SS/PBCH BLOCK的发送配置冲突时，即IAB节点MT被配置的SS/PBCH BLOCK接收与IAB节点DU被配置的SS/PBCH BLOCK发送占用相同时域资源时，IAB节点DU不进行SS/PBCH BLOCK的发送。然而，在这些资源上，IAB节点的MT也可能不进行SS/PBCH BLOCK的接收，此时，IAB节点可将这部分资源视作IAB节点DU的hard资源，即在这部分资源与下级节点或终端设备进行其余信号或信道的传输。
在另一种可能的实现中，在IAB节点MT被配置为接收SS/PBCH BLOCK的资源处，例如SMTC占用资源，上级节点不期望IAB节点MT进行其余信号的传输，因此，当IAB节点MT不进行SS/PBCH BLOCK接收时，IAB节点的DU可使用此资源。
上面是对上级节点如何获取IAB节点DU发送SS/PBCH BLOCK的时域资源的介绍，接下来介绍上级节点如何获取SIB1的时域资源。上级节点获取SIB1的时频资源包括两个部分，第一部分为：上级节点获取终端设备监测SIB1的PDCCH的时频资源；第二部分为：IAB节点DU实际发送SIB1的时频资源(终端设备监测SIB1的PDCCH的时频资源也可以理解为：IAB节点DU可能发送SIB1的所有时频资源。实际上，IAB节点DU可能不会在所有可用的SIB1的时频资源上发送SIB1，因此，还需要第二部分来确定实际发送SIB1的时域资源)。SIB分为多种类型，其中，SIB1发送的系统信息也被称为剩余最 小系统信息(Remaining minimum system information，RMSI)，而SIB1之外的SIB所发送的系统信息被称为其他系统信息(Other system information，OSI)。本申请实施例主要介绍上级节点如何获取SIB1的时频资源。
在NR中，SIB1与SS/PBCH BLOCK存在三种复用图案，分别称为pattern1，pattern2和pattern3。如图5所示。在图5中，SIB1-PDSCH：SIB1的物理下行共享信道(physical downlink share channel，PDSCH)表示承载SIB1的PDSCH，而CORESET(control resource set)表示调度SIB1-PDSCH的物理下行控制信道PDCCH所占用的资源(下文中，CORESET有时候也称为SIB1-PDCCH。应理解，两者所表达的含义都是调度SIB1-PDSCH的PDCCH所占用的资源)。
Pattern 1：SIB1的PDCCH和PDSCH均与SS/PBCH BLOCK时分复用；
Pattern 2：SIB1的PDCCH和SS/PBCH BLOCK时分复用，而SIB1的PDSCH和SS/PBCH BLOCK频分复用；
Pattern 3：SIB1的PDCCH和PDSCH均与SS/PBCH BLOCK频分复用。
下面以具体地复用图案为例，进一步说明如何通过SS/PBCH BLOCK的时频资源，获取SIB1的时频资源，应理解，SIB1的时频资源包括SIB1的CORESET和传输SIB1的PDSCH的资源，以下不再赘述。
(1)SS/PBCH BLOCK与SIB1的复用图案为pattern 3
如图6所示，当SS/PBCH BLOCK与SIB1的复用图案为pattern3时，SIB1-PDCCH与SIB1-PDSCH与SS/PBCH BLOCK频分复用。假设上级节点通过上文描述的方案获知IAB节点DU发送SS/PBCH的时频资源，则其可以推断出IAB节点DU可能发送SIB1-PDCCH的时频资源信息。
如图6所示，假设IAB节点DU发送SS/PBCH BLOCK的周期为20ms(每个无线帧长度为10ms，相当于每隔一个无线帧发送一次SS/PBCH BLOCK)，起始位置为无线帧0，那么，发送SS/PBCH BLOCK所在的时域资源为无线帧0，无线帧2，无线帧4…。但是，在NR中，SS/PBCH BLOCK的发送通常是以时隙或符号为粒度来进行发送的。一个无线帧包括10个子帧，对不同的波形参数(Numerology)，SS/PBCH BLOCK在时隙中的符号位置如下：
对15KHz子载波间隔，按照{2,8}+14*n进行发送，其中{2,8}表示SS/PBCH BLOCK的第一个符号的索引，即位置，以下相同，不再赘述。对小于3GHz或等于3GHz频段，n＝0,1，对大于3GHz且小于等于6GHz频段，n＝0,1,2,3。一个同步信号周期内的SS/PBCH Block的位置由上述公式遍历n的上述取值，以下相同，不再赘述。
对30KHz子载波间隔，按照{4,8,16,20}+28*n进行发送，对小于3GHz或等于3GHz频段，n＝0,对大于3GHz且小于等于6GHz频段，n＝0,1。
对30KHz子载波间隔，按照{2,8}+14*n进行发送，对小于3GHz或等于3GHz频段，n＝0,1，对大于3GHz且小于等于6GHz频段，n＝0,1,2,3。
对120KHz子载波间隔，按照{4,8,16,20}+28*n进行发送，对大于6GHz频段，n＝0,1,2,3,5,6,7,8,10,11,12,13,15,16,17,18。
对240KHz子载波间隔，按照{8,12,16,20,32,36,40,44}+56*n进行发送，对大于6GHz频段，n＝0,1,2,3,5,6,7,8。
由上可见，SS/PBCH BLOCK仅占用部分时隙的部分符号。由于SIB1和SS/PBCH BLOCK是频分复用，因此，IAB节点发送SS/PBCH BLOCK的时域资源，也是发送SIB1的时域资源。在这种情况下，上级节点可以将发送SS/PBCH BLOCK的时域资源视为IAB节点DU发送SIB1的时域资源，确定IAB节点MT功能在该时域资源上不可用，所述时域资源可以是符号或时隙，具体本申请不做限定。
可选地，另外一种情况如图6所示，IAB节点DU实际发送SIB1的周期可能为40ms(SS/PBCH BLOCK周期的两倍)。对于上级节点来说，IAB节点DU实际发送SIB1的PDCCH的时域资源可以根据SS/PBCH BLOCK的时域信息以及SIB1周期信息确定。其中，SIB1的周期可以是绝对时间的周期，例如，周期为40ms；也可以是相对时间的周期和偏移量，例如，SIB1-PDCCH的发送周期是SS/PBCH block周期的2倍。比如，当SS/PBCH BLOCK周期为20ms时，IAB节点可使用2表示周期，得到的周期为40ms。
比如，如图6所示，上级节点将SS/PBCH BLOCK的时域资源视为IAB节点DU发送SIB1的时域资源，确定IAB节点MT功能在该子帧上不可用。
应注意，对于pattern3，由于SIB1占用资源始终与SSB频分，因此即使SIB1占用资源不需要额外的DU hard资源，而SIB1采用更大的周期也不会减少DU hard资源。
(2)SS/PBCH BLOCK与SIB1的复用图案为pattern2
如图7所示，当SS/PBCH BLOCK与SIB1的复用图案为pattern2，SIB1的PDCCH与SS/PBCH BLOCK时分复用，上级节点可以首先根据SS/PBCH BLOCK的配置信息以及SIB1的PDCCH的CORESET，确定IAB节点DU可能发送SIB1-PDCCH的时域位置。再根据额外的信息指示，确定IAB节点DU实际发送SIB1的时域资源。
其中，所述的额外的信息指示可以是SIB1-PDCCH的周期以及偏移量的信息。例如，周期和偏移量可以是绝对时间的周期和偏移量，例如，周期为40ms，偏移量为10ms；也可以是相对时间的周期和偏移量，例如，SIB1-PDCCH的发送周期是SS/PBCH BLOCK周期的倍数。比如，当SS/PBCH BLOCK周期为20ms时，IAB节点可使用(4,1)表示周期和偏移量，得到的周期和偏移量为(80ms，20ms)。
进一步地，用于指示SIB1-PDCCH周期以及偏移量的信息，可以由Donor节点发送给该上级节点，也可以由IAB节点发送给该上级节点。如果由Donor节点发送，有两种可能。第一，周期信息由Donor节点确定，并发送给IAB节点和所述上级节点；第二，周期信息由IAB节点确定并上报至Donor节点，而后由Donor节点通知给上级节点。
可选的，还可以仅配置周期信息，而采用默认的偏移量，例如偏移量默认为0。
需要说明的是，当指示SIB1-PDCCH周期和偏移量的信息为SS/PBCH BLOCK周期的倍数时，该SS/PBCH BLOCK的周期可以是基于SS/PBCH BLOCK集合(SS/PBCH burst set)配置的周期，也可以是基于SS/PBCH BLOCK配置的周期，或者基于SS/PBCH BLOCK组配置的周期。
其中，SS/PBCH BLOCK集合表示半帧内所有的SS/PBCH BLOCK。当周期和偏移量是根据SS/PBCH集合配置时，上级节点假设IAB节点DU所有SS/PBCH BLOCK对应的SIB1-PDCCH均具有同样的周期和偏移。
当周期是基于SS/PBCH BLOCK配置时，每个SS/PBCH BLOCK可能具有独立的周期和偏移量；而当周期是基于SS/PBCH BLOCK组配置时，在一个组内的SS/PBCH BLOCK 具有同样的周期和偏移量，而不同组的SS/PBCH BLOCK具有独立的周期和偏移量。
另一种可能的配置是，额外的周期是基于SS/PBCH BLOCK set或SS/PBCH BLOCK组配置的，而额外的偏移量是根据SS/PBCH BLOCK组或SS/PBCH BLOCK配置的。
应注意，上级节点可能通过其余信令获取了IAB节点AC-SSB的实际发送SS/PBCH BLOCK索引，而SIB1与SS/PBCH BLOCKB索引是一一对应的。因此，对于未进行SS/PBCH BLOCK发送的SS/PBCH BLOCK索引，上级节点可假设IAB节点DU不发送其对应的SIB1。
在获取了实际的SIB1-PDCCH周期和偏移量后，上级节点假设IAB节点DU采用此周期和偏移量发送SIB1-PDCCH。一般情况下，IAB节点DU可采用此周期和偏移量来发送SIB1-PDCCH，但IAB节点DU也可以采用其他的周期和偏移量进行SIB1-PDCCH的发送，但IAB节点DU应保证发送不会和其MT的收发出现冲突。也就是说，按照此周期和偏移量所确定的资源位置是上级节点假设IAB节点DU发送SIB1-PDCCH的资源位置，不一定完全是IAB节点DU发送SIB1-PDCCH的实际资源位置。
如图8所示，上级节点根据SIB1-PDCCH的时域位置以及周期、偏移量信息，确定的IAB节点DU发送SIB1-PDCCH的时域位置为每40ms发送一次，但是实际上IAB节点DU发送SIB1-PDCCH的时域位置为每80ms发送一次。(假设图8中的用户设备UE每隔20ms检测一次SIB1-PDCCH)
(3)SS/PBCH BLOCK与SIB1的复用图案为pattern1
如图9所示，当SS/PBCH BLOCK与SIB1的复用图案为pattern1时，SIB1-PDCCH和SIB1-PDSCH均与SS/PBCH BLOCK时分复用。
pattern1的SIB1-PDCCH与pattern2的SIB1-PDCCH存在一些不同点。
首先，pattern1的SIB1-PDCCH的监测周期是20ms，而不是SS/PBCH BLOCK周期。
其次，对于pattern1，当终端设备确定了SIB1-PDCCH的时隙编号后，会连续在两个连续的时隙进行PDCCH监测。然而，在实际实现中，IAB节点DU可能仅在其中一个时隙发送SIB1-PDCCH。因此，IAB节点或Donor节点还可以向上级节点发送该IAB节点DU发送SIB1-PDCCH的具体时隙信息(例如，两个连续时隙之一)。在确定了IAB节点DU发送SIB1-PDCCH的资源后，上级节点将这些资源视作IAB DU的hard资源，对应地，将这些资源视为IAB MT功能的不可用资源。
接下来介绍上级节点如何获取IAB节点DU的SIB1-PDSCH的时频资源。
由于SS/PBCH BLOCK与SIB1的复用图案为pattern2和pattern3时，PDSCH均与SS/PBCH BLOCK频分，pattern2和pattern3的PDSCH的时域资源可以参考SS/PBCH BLOCK的时域资源，因此下文仅考虑复用图案为pattern1的情况。
在Pattern1中，SIB1-PDSCH的实际传输位置由SIB1-PDCCH的调度决定。在理想情况下，IAB节点DU可以把SIB1-PDSCH调度至资源配置所指示的hard资源。然而在实际中，所配置的hard资源可能不足以发送所有的SIB1-PDSCH，此时，需要额外的机制保障SIB1-PDSCH的顺利发送。
一种可能的解决方法是，在配置hard/soft资源时，需要满足一定的约束。例如，IAB DU的hard资源在配置周期内的占比不少于X％，X的取值可以由协议定义，也可以由IAB节点向上级节点或Donor节点请求。
另一种可能的解决方法是，IAB节点或Donor节点通知所述上级节点所述IAB节点调度SIB1-PDSCH的时域信息。例如，IAB节点可向上级节点上报SIB1-PDCCH调度SIB1-PDSCH采用的时域参数，即下行控制信道(downlink control information，DCI)中的时域资源分配(Time domain resource assignment)。在获取到SIB1-PDSCH的时域信息后，上级节点可确定出IAB节点DU的额外hard资源。
基于上述对三种复用图案的分析，如图10所示，本申请实施例提供一种通信的方法1000，包括：
1010、从第一节点或第三节点接收配置信息，所述配置信息指示所述第一节点分布式单元DU的系统信息块1SIB1的时频信息；
1020、基于获取的所述第一节点DU的SIB1的时频信息，确定所述第一节点移动终端MT功能的不可用资源；
其中，第一节点为集成接入回传IAB节点，第二节点为所述第一节点的上级节点，第三节点为donor节点。
本申请实施例是基于SS/PBCH BLOCK的时域资源获取SIB1的时域资源，相比直接上报SIB1的时域资源，更节省信令开销。
具体地，所述配置信息包括SS/PBCH BLOCK的时频信息，SS/PBCH BLOCK的时域信息包括SS/PBCH BLOCK的发送周期，偏移量，SS/PBCH BLOCK索引、SS/PBCH BLOCK的频域信息。
基于SS/PBCH BLOCK的时频信息，获取可能发送SIB1的时域信息可以由多种实现方式。比如，一种实现方式中，Donor节点或IAB节点将SIB1的PDCCH的CORESET配置发送给上级节点。此时，所述配置信息包括：所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
即IAB节点或者Donor节点直接将SIB1-PDCCH的CORESET配置发给上级节点，使得上级节点可以获取SIB1的频域信息以及SIB1与SS/PBCH BLOCK的复用图案信息，进而获得SIB1的时频域信息。其中，SIB1-PDCCH的CORESET配置被封装在主信息块(main system information，MIB)中发送，对应的参数是pdcch-ConfigSIB1。示例性地，上级节点通过MIB获得SIB1-PDCCH的配置信息(pdcch-ConfigSIB1和SIB1-PDCCH的子载波间隔)。根据配置信息，可分别确定SIB1-PDCCH的CORESET信息(包括复用图案(pattern1,2,3)，CORESET的占用的RB数目，CORESET占用的符号数目等)和监测机会(monitoring occasion)信息(或搜索空间信息)，检测机会信息包括每个SSB对应的SIB1-PDCCH监测机会所占用帧位置、时隙位置和符号位置。
另一种实现方式中，Donor节点或IAB节点不需要将SIB1的PDCCH的CORESET配置发送给IAB节点，通过第二节点存储的表格，以及根据子载波间隔、索引、最小信道带宽等信息来查表，获得SIB1的PDCCH的具体CORESET配置。如，所述第二节点存储一个或多个表格，所述一个或多个表格中的每一个表格记录有如下信息：
索引，SS/PBCH BLOCK与SIB1的复用图案，SIB1的频域信息，SIB1的频域偏移量。
所述配置信息还包括SS/PBCH BLOCK的子载波间隔以及SIB1的子载波间隔(也可以称为调度SIB1的PDCCH的子载波间隔，或者称为调度SIB1的搜索空间CORESET的 子载波间隔)。
所述配置信息还包括：第一节点DU所占用的最小信道带宽。
所述第二节点基于所述SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔和/或第一节点DU所占用的最小信道带宽，确定所述一个或多个表格中的第一表格；
所述第二节点接收第一索引，所述第一索引指示一种SIB1的PDCCH所占用的CORESET配置；
基于所述第一索引，从所述第一表格中确定SIB1的PDCCH所占用的CORESET配置。
这种方式是通过存储SIB1的CORESET配置表格，根据索引信息，获得SIB1的CORESET配置，比直接发送SIB1的CORESET配置节省信令开销。
示例性地，根据上述表13-1至表13-11可知，当SS/PBCH BLOCK的子载波间隔相同的情况下，不同的最小信道带宽对应的表格不同。因此，上级节点还需要获知第一节点DU所占用的最小信道带宽，其中，最小信道带宽的取值为5Mhz，10Mhz，或40Mhz。
进一步地，所述第二节点预存储一个或多个表格，所述一个或多个表格中的每一个表格记录有配置索引，SIB1的频域信息，以及，所述SS/PBCH BLOCK与SIB1复用图案信息；根据从Donor节点或IAB节点接收的配置索引以及所述一个或多个表格，确定所述SIB1的频域信息，以及，所述SIB1与SS/PBCH BLOCK的复用图案信息；基于所述SS/PBCH BLOCK的时域信息，以及所述SIB1与SS/PBCH BLOCK的复用图案信息，获取所述SIB1的时域信息。
示例性地，第二节点可以预存储如下表13-1,到表13-11等表格(如下表格仅为示例，实际实现中可能存储的表格不同于本实施例例举的取值)，基于所述预存储的表格，以及获取的SIB1-PDCCH的配置信息，获取SIB1的时域位置。
例如，当SS/PBH块子载波间隔为120kHz，SIB1的子载波间隔为120Khz时，对应表格13-8，当索引为4，第二节点可以获取SS/PBCH BLOCK与SIB1的复用图案为3，SIB1的频域信息包括SIB1的RB数为24，SIB1的符号数为2，RB的偏移量为-20或-21。由于SS/PBCH BLOCK与SIB1的复用图案为3，SIB1的PDCCH和PDSCH均与SS/PBCH BLOCK频分复用，那么终端设备根据SS/PBCH BLOCK的时域位置，即可获得SIB1的时域位置。而SS/PBCH BLOCK的时域位置信息的获取，可以参考上文的描述，这里不再赘述。
例如，当SS/PBCH BLOCK子载波间隔为120kHz且SIB1的子载波间隔为60Khz时，对应表格13-7，当索引为8，第二节点可以获取SS/PBCH BLOCK与SIB1的复用图案为2，SIB1的频域信息包括SIB1的RB数为48，SIB1的符号数为1，RB的偏移量为-41或-42。由于SS/PBCH BLOCK与SIB1的复用图案为2，SIB1的PDCCH与SS/PBCH BLOCK时分复用以及频分复用；SIB1的PDSCH与SS/PBCH BLOCK频分复用(请见图5中的pattern2)，那么终端设备根据SS/PBCH BLOCK的时域位置，即可获得SIB1的PDSCH时域位置。而SS/PBCH BLOCK的时域位置信息的获取，可以参考上文的描述，这里不再赘述。SIB1-PDCCH的时域位置，还需要进一步的指示。例如，通过指示SIB1-PDCCH的发送周期以及相对于SS/PBCH BLOCK的偏移量。以图8为例，SIB1的PDCCH的发送周期是SS/PBCH BLOCK周期的2倍，偏移量可以是时域上偏移的时隙数或者OFDM符 号数。
又比如，当SS/PBCH BLOCK子载波间隔为15kHz，CORESET子载波间隔为15kHz，且信道最小带宽为5MHz或10MHz时，对应表格13-1，当索引为0，第二节点可以获取SS/PBCH BLOCK与SIB1的复用图案为1，SIB1的频域信息包括RB数为24，符号数为2，频域偏移量为2RB。由于SS/PBCH BLOCK与SIB1的复用图案为1，SIB1的PDCCH与PDSCH与SS/PBCH BLOCK时分复用，第二节点可以根据SS/PBCH BLOCK的时域位置，以及SIB1相对于SS/PBCH BLOCK的偏移量，确定SIB1的时域位置。SS/PBCH BLOCK的时域位置信息的获取，可以参考上文的描述，这里不再赘述。
由于pattern1具有特殊性，对于pattern1，当终端设备确定了SIB1-PDCCH的时隙编号后，会连续在两个连续的时隙进行PDCCH监测，然而在实际实现中，IAB DU可仅在其中一个时隙发送SIB1-PDCCH。因此，IAB节点或上级节点还可以向上级节点发送其在发送SIB1-PDCCH的具体时隙。
Table 13-1:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{15,15}kHz for frequency bands with minimum channel bandwidth 5MHz or 10MHz
Figure PCTCN2020075799-appb-000005
Table 13-2:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{15,30}kHz for frequency bands with minimum channel bandwidth 5MHz or 10MHz
Figure PCTCN2020075799-appb-000006
Table 13-3:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{30,15}kHz for frequency bands with minimum channel bandwidth 5MHz or 10MHz
Figure PCTCN2020075799-appb-000007
Table 13-4:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{30,30}kHz for frequency bands with minimum channel bandwidth 5MHz or 10MHz
Figure PCTCN2020075799-appb-000008
Table 13-5:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{30,15}kHz for frequency bands with minimum channel bandwidth 40MHz
Figure PCTCN2020075799-appb-000009
Table 13-6:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{30,30}kHz for frequency bands with minimum channel bandwidth 40MHz
Figure PCTCN2020075799-appb-000010
Table 13-7:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{120,60}kHz
Figure PCTCN2020075799-appb-000011
Table 13-8:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{120,120}kHz
Figure PCTCN2020075799-appb-000012
Table 13-9:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{240,60}kHz
Figure PCTCN2020075799-appb-000013
Table 13-10:Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS/PBCH block,PDCCH}SCS is{240,120}kHz
Figure PCTCN2020075799-appb-000014
上级节点获取IAB节点DU可能发送SIB1的时频资源，还需要进一步获取IAB节点DU实际发送SIB1的时频资源。
为了获取IAB节点DU实际发送SIB1的时频资源，还需要进一步的信息指示。该信息指示可以是SIB1-PDCCH的周期以及偏移量(偏移量非必须，可以只指示SIB1-PDCCH的周期)的信息。例如，周期和偏移量可以是绝对时间的周期和偏移量，例如，周期为40ms，偏移量为10ms；也可以是相对时间的周期和偏移量，例如，SIB1-PDCCH的发送周期是SS/PBCH BLOCK周期的倍数。比如，当SS/PBCH BLOCK周期为20ms时，IAB节点可使用(4,1)表示周期和偏移量，得到的周期和偏移量为(80ms，20ms)。
进一步地，用于指示SIB1-PDCCH周期以及偏移量的信息，可以由Donor节点发送给该上级节点，也可以由IAB节点发送给该上级节点。如果由Donor节点发送，有两种可能。第一，周期信息由Donor节点确定，并发送给IAB节点和所述上级节点；第二，周期信息由IAB节点确定并上报至Donor节点，而后由Donor节点通知给上级节点。
可选的，还可以仅配置周期信息，而采用默认的偏移量，例如偏移量默认为0。
综上，上级节点通过获取IAB节点DU的SIB1的时域资源，相应地，将该些时域资源视为IAB节点的MT的不可用资源，即，上级节点不在上述时域资源上向IAB节点MT发送下行信号，以避免资源冲突。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
可以理解的是，上述各个方法实施例中，由IAB节点或上级节点实现的方法和操作， 也可以由可用于IAB节点或上级节点的部件(例如芯片或者电路)实现。
上文描述了本申请实施例提供的方法实施例，下文将描述本申请实施例提供的装置实施例。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如第一节点和第二节点，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的网元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对第一节点、第二节点进行功能模块的划分，例如，可以划分成各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。应理解，第二节点可以是IAB节点，也可以是Donor节点。
图11为本申请的提供的上述实施例中所涉及的一种节点1100的一种可能的结构示意图。该节点1100包括收发单元1110和处理单元1120.收发单元1110可以与外部进行通信，处理单元1120用于进行数据处理。收发单元1110还可以称为通信接口或通信单元。
该节点1100可以用于执行上文方法实施例中IAB节点所执行的动作，或者，也可以执行上文方法实施例中IAB节点的上级节点所执行的动作。
作为一种实现方式，收发单元1110用于执行IAB节点或者上级节点收发相关的操作；处理单元1120用于执行IAB节点或上级节点数据处理相关的操作。
一种实施例中，收发单元1110，用于：从第一节点或第三节点接收配置信息，所述配置信息指示所述第一节点分布式单元DU的系统信息块1SIB1的时频信息；处理单元1120，用于基于获取的所述第一节点DU的SIB1的时频信息，确定所述第一节点移动终端MT功能的不可用资源。
另一种实施例中，收发单元1110，用于：向第二节点上报配置信息，所述配置信息指示所述SIB1的时频信息；其中，第一节点为集成接入回传IAB节点，第二节点为所述第一节点的上级节点。处理单元1120，用于用于确定分布式单元DU的系统信息块1SIB1的时频信息。
其中，所述配置信息可以包括SS/PBCH BLOCK的时域信息，所述同步信号/物理广播信道SS/PBCH BLOCK的时域信息包括所述SS/PBCH BLOCK的周期以及偏移量。
可选地，所述配置信息还包括：所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
可选地，所述节点还包括存储单元，用于存储一个或多个表格，所述一个或多个表格中的每一个表格记录有如下信息：
索引，SS/PBCH BLOCK与SIB1的复用图案，SIB1的频域信息，SIB1的频域偏移量。
可选地，所述收发单元，还用于接收所述SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔，以及，第一索引，所述第一索引指示一种SIB1的PDCCH所占用的CORESET配置；
所述处理单元，用于基于所述SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔，确定所述一个或多个表格中的第一表格；以及，基于所述第一索引，从所述第一表格中确定SIB1的PDCCH所占用的CORESET配置。
可选地，所述配置信息还包括：SS/PBCH BLOCK的子载波间隔，以及，SIB1的子载波间隔。
可选地，所述配置信息还包括：第一节点的DU所占用的最小信道带宽。
可选地，所述配置信息还包括：指示所述SIB1的周期以及偏移量的信息。
进一步地，所述收发单元1110，还用于通过无线资源控制RRC信令或者接口消息F1-AP发送或接收所述配置信息。
进一步地，所述收发单元1110，还用于向第二节点上报DU调度SIB1的物理下行共享信道PDSCH的时域参数。其中，所述时域参数包括下行控制信息中的时域资源分配Time domain resource assignment。
应理解，上文实施例中的处理单元1120可以由处理器或处理器相关电路实现，收发单元1110可以由收发器或收发器相关电路实现。
如图12所示，本申请实施例还提供一种通信装置1200。通信装置1200包括处理器1210、存储器1220和收发器1230，存储器1210中存储有程序，处理器1210用于执行存储器1220中存储的程序，对存储器1220中存储的程序的执行，使得处理器1210用于执行上文方法实施例中的相关处理步骤，对存储器1220中存储的程序的执行，使得处理器1210控制收发器1230执行上文方法实施例中的收发相关步骤。
作为一种实现，该通信装置1200用于执行上文方法实施例中第一节点或第二节点或第三节点所执行的动作，这时，对存储器1220中存储的程序的执行，使得处理器1210用于执行上文方法实施例中第一节点或第二节点或第三节点侧的处理步骤，对存储器1220中存储的程序的执行，使得处理器1210控制收发器1230执行上文方法实施例中第一节点或第二节点或第三节点侧的接收和发送步骤。
当该通信装置1200为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或者微处理器或者集成电路。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的Donor节点、IAB节点以及IAB节点的上级节点。
本申请实施例还提供一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被计算机执行时使得该计算机实现上述方法实施例中终端设备侧的方法或定位管理设备侧的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中终端设备侧的方法或定位管理设备侧的方法。
上述提供的任一种通信装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请实施例所提到的节点包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
应理解，本申请实施例中提及的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及 算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (50)

  1. 一种通信的方法，其特征在于，包括：
    第二节点从第一节点或第三节点接收配置信息，所述配置信息指示所述第一节点分布式单元DU的系统信息块1 SIB1的时频信息；
    基于获取的所述第一节点DU的SIB1的时频信息，确定所述第一节点移动终端MT功能的不可用资源；
    其中，第一节点为集成接入回传IAB节点，第二节点为所述第一节点的上级节点，第三节点为Donor节点。
  2. 根据权利要求1所述的方法，其特征在于，所述配置信息包括同步信号/物理广播信道SS/PBCH BLOCK的时频信息。
  3. 根据权利要求2所述的方法，其特征在于，所述同步信号/物理广播信道SS/PBCH BLOCK的时频信息包括如下信息中的一项或多项：
    所述SS/PBCH BLOCK的周期、偏移量、所述SS/PBCH BLOCK在半帧内的索引、所述SS/PBCH BLOCK子载波间隔、SS/PBCH BLOCK的频域信息。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述配置信息还包括：
    所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
    SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述第二节点存储一个或多个表格，所述一个或多个表格中的每一个表格记录有如下信息：
    索引，SS/PBCH BLOCK与SIB1的复用图案，SIB1的频域信息，SIB1的频域偏移量。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述第二节点获取SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔；
    基于所述SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔，确定所述一个或多个表格中的第一表格；
    所述第二节点接收第一索引，所述第一索引指示一种SIB1的PDCCH所占用的CORESET配置；
    基于所述第一索引，从所述第一表格中确定SIB1的PDCCH所占用的CORESET配置。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述配置信息还包括：
    指示所述SIB1的周期以及偏移量的信息。
  8. 根据权利要求7所述的方法，其特征在于，所述所述SIB1的周期的信息为SS/PBCH BLOCK的周期的倍数。
  9. 根据权利要求8所述的方法，其特征在于，所述配置信息还包括：
    第一节点DU的SIB1的PDCCH所占用的时隙。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，基于获取的所述第一节点DU的SIB1的时频信息，确定所述第一节点移动终端MT功能的不可用资源，具体包括：
    将所述第一节点DU的SIB1所占用的时频资源，确定为所述第一节点MT功能的不可用资源。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，通过无线资源控制RRC信令或者接口消息F1-AP接收所述配置信息。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述方法还包括：
    所述第二节点接收第一节点DU调度SIB1的物理下行共享信道PDSCH的时域参数。
  13. 根据权利要求12所述的方法，其特征在于，所述时域参数包括下行控制信息中的时域资源分配Time domain resource assignment。
  14. 一种通信的方法，其特征在于，包括：
    第一节点确定集成接入回传IAB节点分布式单元DU的系统信息块1 SIB1的时频信息；
    向第二节点发送配置信息，所述配置信息指示所述SIB1的时频信息；其中，第一节点为所述集成接入回传IAB节点或者Donor节点，第二节点为所述IAB节点的上级节点。
  15. 根据权利要求14所述的方法，其特征在于，所述配置信息具体包括同步信号/物理广播信道SS/PBCH BLOCK的时域信息。
  16. 根据权利要求15所述的方法，其特征在于，所述同步信号/物理广播信道SS/PBCH BLOCK的时频信息包括如下信息中的一项或多项：
    所述SS/PBCH BLOCK的周期、偏移量、所述SS/PBCH BLOCK在半帧内的索引、所述SS/PBCH BLOCK子载波间隔、SS/PBCH BLOCK的频域信息。
  17. 根据权利要求14-16任一项所述的方法，其特征在于，所述配置信息还包括：
    所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
    SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
  18. 根据权利要求14-16任一项所述的方法，其特征在于，所述配置信息还包括：
    SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔。
  19. 根据权利要求15-18任一项所述的方法，其特征在于，所述配置信息还包括：
    指示所述SIB1的周期以及偏移量的信息。
  20. 根据权利要求19所述的方法，其特征在于，所述指示所述SIB1的周期的信息为SS/PBCH BLOCK的周期的倍数。
  21. 根据权利要求15-20任一项所述的方法，其特征在于，所述配置信息还包括：
    第一节点DU的SIB1的PDCCH所占用的时隙。
  22. 根据权利要求14-21任一项所述的方法，其特征在于，通过无线资源控制RRC信令或者接口消息F1-AP发送所述配置信息。
  23. 根据权利要求14-22任一项所述的方法，其特征在于，所述方法还包括：
    所述第一节点向第二节点上报DU调度SIB1的物理下行共享信道PDSCH的时域参数。
  24. 根据权利要求23所述的方法，其特征在于，所述时域参数包括下行控制信息中的时域资源分配Time domain resource assignment。
  25. 一种节点，其特征在于，包括：
    收发单元，用于从第一节点或第三节点接收配置信息，所述配置信息指示所述第一节点分布式单元DU的系统信息块1 SIB1的时频信息；
    处理单元，用于基于获取的所述第一节点DU的SIB1的时频信息，确定所述第一节点移动终端MT功能的不可用资源；
    其中，第一节点为集成接入回传IAB节点，第三节点为Donor节点。
  26. 根据权利要求25所述的节点，其特征在于，所述配置信息具体包括同步信号/物理广播信道SS/PBCH BLOCK的时域信息。
  27. 根据权利要求26所述的节点，其特征在于，所述同步信号/物理广播信道SS/PBCH BLOCK的时域信息包括所述SS/PBCH BLOCK的周期以及偏移量。
  28. 根据权利要求25-27任一项所述的节点，其特征在于，所述配置信息还包括：
    所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
    SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
  29. 根据权利要求25-27任一项所述的节点，其特征在于，所述节点还包括存储单元，用于存储一个或多个表格，所述一个或多个表格中的每一个表格记录有如下信息：
    索引，SS/PBCH BLOCK与SIB1的复用图案，SIB1的频域信息，SIB1的频域偏移量。
  30. 根据权利要求29所述的节点，其特征在于，所述收发单元，还用于获取SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔；以及，接收第一索引，所述第一索引指示一种SIB1的PDCCH所占用的CORESET配置；
    所述处理单元，还用于基于所述SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔，确定所述一个或多个表格中的第一表格；以及，基于所述第一索引，从所述第一表格中确定SIB1的PDCCH所占用的CORESET配置。
  31. 根据权利要求25-30任一项所述的节点，其特征在于，所述配置信息还包括：
    指示所述SIB1的周期以及偏移量的信息。
  32. 根据权利要求31所述的节点，其特征在于，所述指示所述SIB1的周期的信息为SS/PBCH BLOCK的周期的倍数。
  33. 根据权利要求25-32任一项所述的节点，其特征在于，所述配置信息还包括：
    第一节点DU的SIB1的PDCCH所占用的时隙。
  34. 根据权利要求25-33任一项所述的节点，其特征在于，所述处理单元，用于将所述第一节点DU的SIB1所占用的时频资源，确定为所述第一节点MT功能的不可用资源。
  35. 根据权利要求25-34任一项所述的节点，其特征在于，所述收发单元，用于通过无线资源控制RRC信令或者接口消息F1-AP接收所述配置信息。
  36. 根据权利要求25-35任一项所述的节点，其特征在于，所述收发单元，还用于：
    接收所述第一节点DU调度SIB1的物理下行共享信道PDSCH的时域参数。
  37. 根据权利要求36所述的节点，其特征在于，所述时域参数包括下行控制信息中的时域资源分配Time domain resource assignment。
  38. 一种第一节点，其特征在于，包括：
    处理单元，用于确定集成接入回传IAB节点分布式单元DU的系统信息块1 SIB1的时频信息；
    收发单元，用于向第二节点发送配置信息，所述配置信息指示所述SIB1的时频信息；其中，第一节点为集成接入回传IAB节点或者Donor节点，第二节点为所述IAB节点的上级节点。
  39. 根据权利要求38所述的第一节点，其特征在于，所述配置信息具体包括：
    同步信号/物理广播信道SS/PBCH BLOCK的时域信息。
  40. 根据权利要求39所述的第一节点，其特征在于，所述同步信号/物理广播信道SS/PBCH BLOCK的时域信息包括所述SS/PBCH BLOCK的周期以及偏移量。
  41. 根据权利要求38或39所述的第一节点，其特征在于，所述配置信息还包括：
    所述SIB1的PDCCH所占用的搜索空间CORESET配置，所述CORESET配置包括如下信息中的一项或多项：
    SS/PBCH BLOCK与SIB1的复用图案信息、SIB1的频域信息、SIB1的频域偏移量。
  42. 根据权利要求38-41任一项所述的第一节点，其特征在于，所述配置信息还包括：SIB1的子载波间隔以及SS/PBCH BLOCK的子载波间隔。
  43. 根据权利要求38-42任一项所述的第一节点，其特征在于，所述配置信息还包括：指示所述SIB1的周期以及偏移量的信息。
  44. 根据权利要求43所述的第一节点，其特征在于，所述指示所述SIB1的周期的信息为SS/PBCH BLOCK的周期的倍数。
  45. 根据权利要求38-44任一项所述的第一节点，其特征在于，所述配置信息还包括：
    第一节点DU的SIB1的PDCCH所占用的时隙。
  46. 根据权利要求38-45任一项所述的第一节点，其特征在于，所述收发单元，通过无线资源控制RRC信令或者接口消息F1-AP发送所述配置信息。
  47. 根据权利要求38-46任一项所述的第一节点，其特征在于，所述收发单元，还用于：
    向第二节点上报DU调度SIB1的物理下行共享信道PDSCH的时域参数。
  48. 根据权利要求47所述的第一节点，其特征在于，所述时域参数包括下行控制信息中的时域资源分配Time domain resource assignment。
  49. 一种计算机可读存储介质，其上存储有指令，其特征在于，该指令被执行时执行如权利要求1-13任一项所述的通信的方法，或者执行权利要求14-24任一项所述的通信的方法。
  50. 一种中继系统中资源确定的系统，所述系统包括Donor节点，至少一个第一节点，以及至少一个第二节点，其中，第二节点为第一节点的上级节点，其特征在于，包括：
    所述第二节点用于执行如权利要求1-13中任一项所述的通信的方法；
    所述第一节点执行如权利要求14-24中任一项所述的通信的方法。
PCT/CN2020/075799 2019-05-03 2020-02-19 一种通信的方法和装置 Ceased WO2020224306A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
BR112021022042A BR112021022042A2 (pt) 2019-05-03 2020-02-19 Método e aparelho de comunicação
MX2021013469A MX2021013469A (es) 2019-05-03 2020-02-19 Método y aparato de comunicación.
JP2021565097A JP7374221B2 (ja) 2019-05-03 2020-02-19 通信方法および装置
EP20801620.4A EP3952553A4 (en) 2019-05-03 2020-02-19 COMMUNICATION METHOD AND APPARATUS
KR1020217039231A KR102763820B1 (ko) 2019-05-03 2020-02-19 통신 방법 및 장치
US17/517,385 US20220061006A1 (en) 2019-05-03 2021-11-02 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910376533.2A CN111884777B (zh) 2019-05-03 2019-05-03 一种通信的方法及装置
CN201910376533.2 2019-05-03

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/517,385 Continuation US20220061006A1 (en) 2019-05-03 2021-11-02 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2020224306A1 true WO2020224306A1 (zh) 2020-11-12

Family

ID=73051006

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075799 Ceased WO2020224306A1 (zh) 2019-05-03 2020-02-19 一种通信的方法和装置

Country Status (8)

Country Link
US (1) US20220061006A1 (zh)
EP (1) EP3952553A4 (zh)
JP (1) JP7374221B2 (zh)
KR (1) KR102763820B1 (zh)
CN (2) CN115426084A (zh)
BR (1) BR112021022042A2 (zh)
MX (1) MX2021013469A (zh)
WO (1) WO2020224306A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114520987A (zh) * 2020-11-20 2022-05-20 维沃移动通信有限公司 Iab节点的冲突处理方法、装置、设备及可读存储介质
WO2022127906A1 (zh) * 2020-12-18 2022-06-23 维沃移动通信有限公司 资源配置方法、装置、网络节点和存储介质
WO2025061155A1 (zh) * 2023-09-22 2025-03-27 华为技术有限公司 通信方法和相关装置

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11690054B2 (en) * 2020-01-22 2023-06-27 Qualcomm Incorporated Gap enhancements in wireless networks
CN113163491B (zh) * 2020-01-23 2023-03-24 维沃移动通信有限公司 频域资源处理方法、频域资源配置方法及相关设备
EP4128632A1 (en) * 2020-04-02 2023-02-08 Lenovo (Singapore) Pte. Ltd. Resource attribute configuration
US11824817B2 (en) * 2020-05-13 2023-11-21 Qualcomm Incorporated Cross-link interference signaling for integrated access and backhaul
EP3911091A1 (en) * 2020-05-14 2021-11-17 Robert Bosch GmbH Resource conflict indicator transmission for device-to-device mobile communications
CN116602050A (zh) * 2020-12-15 2023-08-15 韩国电子通信研究院 无线通信系统中的资源管理的方法和装置
JP2024504301A (ja) * 2021-01-15 2024-01-31 華為技術有限公司 アクセス・バックホール統合に基づいた通信方法及び装置
US12363680B2 (en) * 2021-03-30 2025-07-15 Qualcomm Incorporated Techniques for supporting dynamic frequency division multiplexing within carrier
CN115175318A (zh) * 2021-04-01 2022-10-11 中兴通讯股份有限公司 一种指示方法、装置、第一节点、第二节点及存储介质
CN116846445A (zh) * 2022-03-25 2023-10-03 华为技术有限公司 小区信息的配置方法、装置、可读存储介质及芯片系统
CN114980179B (zh) * 2022-06-13 2024-10-29 深圳市佳贤通信科技股份有限公司 一种智能调整ssb周期的装置和方法
JP7705562B2 (ja) * 2022-07-19 2025-07-09 楽天モバイル株式会社 通信品質に基づく通信機の移動局から周辺基地局への遷移
KR20240132359A (ko) * 2022-07-19 2024-09-03 라쿠텐 모바일 가부시키가이샤 이동국 및 주변 기지국에 관한 접속 제어
CN116388911B (zh) * 2023-03-24 2025-08-12 成都中科微信息技术研究院有限公司 一种5gnr接入回传一体化波形设计方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108401533A (zh) * 2017-11-30 2018-08-14 北京小米移动软件有限公司 信息指示方法及装置、基站和用户设备
CN109451585A (zh) * 2018-04-04 2019-03-08 华为技术有限公司 一种通信方法及装置
US20190132096A1 (en) * 2017-10-27 2019-05-02 Qualcomm Incorporated Power control for concurrent transmissions

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101877880A (zh) 2009-04-28 2010-11-03 中兴通讯股份有限公司 一种解决中继节点系统广播信息冲突的方法
US10492157B2 (en) * 2017-01-04 2019-11-26 Samsung Electronics Co., Ltd. Method and apparatus for system information delivery in advanced wireless systems
WO2018128427A1 (en) 2017-01-04 2018-07-12 Samsung Electronics Co., Ltd. Method and apparatus for system information delivery in wireless communication system
CN109246796B (zh) * 2017-05-05 2021-09-28 中兴通讯股份有限公司 一种通信方法及装置
US11219015B2 (en) * 2017-08-11 2022-01-04 Lg Electronics Inc. Method for transmitting/receiving signal in wireless communication system, and device therefor
CN108882376B (zh) * 2017-11-10 2020-01-17 华为技术有限公司 一种通信方法、装置以及系统
KR101999702B1 (ko) * 2017-11-17 2019-07-12 엘지전자 주식회사 하향링크 채널을 송수신하는 방법 및 이를 위한 장치
CN111066363B (zh) * 2018-08-07 2023-04-18 Lg电子株式会社 节点在无线通信系统中的资源使用方法和使用该方法的装置
CN110972274B (zh) * 2018-09-28 2023-01-20 中兴通讯股份有限公司 时域资源分配方法及装置
WO2020062167A1 (zh) * 2018-09-29 2020-04-02 北京小米移动软件有限公司 网络接入方法、装置及存储介质
WO2020092348A1 (en) * 2018-10-31 2020-05-07 Intel Corporation Off-raster ssb design in iab networks
US20220104104A1 (en) * 2019-01-21 2022-03-31 Ntt Docomo, Inc. Wireless node and wireless communication control method
CN113728676A (zh) * 2019-03-29 2021-11-30 瑞典爱立信有限公司 在集成接入和回程网络中的子节点处和父节点处的资源对准

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190132096A1 (en) * 2017-10-27 2019-05-02 Qualcomm Incorporated Power control for concurrent transmissions
CN108401533A (zh) * 2017-11-30 2018-08-14 北京小米移动软件有限公司 信息指示方法及装置、基站和用户设备
CN109451585A (zh) * 2018-04-04 2019-03-08 华为技术有限公司 一种通信方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS: "Discussions on resource multiplexing among backhaul and access links", 3GPP TSG RAN WG1 #96BIS R1-1904205, 30 March 2019 (2019-03-30), XP051691343 *
QUALCOMM INC.: "Updated IAB resource management framework", 3GPP TSG RAN WG1 MEETING #96BIS R1-1905006, 30 March 2019 (2019-03-30), XP051691929 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114520987A (zh) * 2020-11-20 2022-05-20 维沃移动通信有限公司 Iab节点的冲突处理方法、装置、设备及可读存储介质
WO2022127906A1 (zh) * 2020-12-18 2022-06-23 维沃移动通信有限公司 资源配置方法、装置、网络节点和存储介质
WO2025061155A1 (zh) * 2023-09-22 2025-03-27 华为技术有限公司 通信方法和相关装置

Also Published As

Publication number Publication date
MX2021013469A (es) 2022-01-31
US20220061006A1 (en) 2022-02-24
CN115426084A (zh) 2022-12-02
KR20210154256A (ko) 2021-12-20
JP2022530838A (ja) 2022-07-01
BR112021022042A2 (pt) 2022-03-22
EP3952553A4 (en) 2022-06-15
CN111884777A (zh) 2020-11-03
CN111884777B (zh) 2022-07-29
JP7374221B2 (ja) 2023-11-06
KR102763820B1 (ko) 2025-02-05
EP3952553A1 (en) 2022-02-09

Similar Documents

Publication Publication Date Title
WO2020224306A1 (zh) 一种通信的方法和装置
JP7645309B2 (ja) リソース構成方法および装置
US12273863B2 (en) Method and apparatus for resource allocation
CN116346546A (zh) 一种通信方法及装置
CN110401515B (zh) 一种资源配置方法及节点
WO2021203873A1 (zh) 资源配置方法、装置、通信节点及存储介质
CN110972279B (zh) 传输数据的方法和装置
US20180063858A1 (en) System and Method for Co-existence of Low-Latency and Latency-Tolerant Communication Resources
WO2021062918A1 (zh) 一种资源的动态指示方法及装置
CN116097812B (zh) 用于增强型配置授权的系统和方法
CN111698778B (zh) 指示资源的方法和装置
CN116250192B (zh) 用于实现增强的配置授权的移动设备和方法
WO2022207002A1 (zh) 无线通信方法和装置
WO2023011518A1 (zh) 一种通信方法及通信装置
JP2024503850A (ja) 伝送タイミング決定方法及び装置
WO2023284485A1 (zh) 信号传输方法及装置
WO2025167141A1 (zh) 无线通信方法、通信装置及存储介质
WO2024011632A1 (zh) 资源配置方法、装置、设备及存储介质
JP7302095B2 (ja) リソース指示方法および装置
WO2023065365A1 (zh) 无线通信方法、终端设备和网络设备
WO2021062892A1 (zh) 一种资源的动态指示方法及装置
US20250071741A1 (en) Communication method and communication apparatus
EP4683406A1 (en) Sidelink transmission method and terminal devices
JP2026513200A (ja) 通信方法、端末機器及びネットワーク機器
WO2024212249A1 (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: 20801620

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021565097

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2021/013469

Country of ref document: MX

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020801620

Country of ref document: EP

Effective date: 20211105

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112021022042

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20217039231

Country of ref document: KR

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01E

Ref document number: 112021022042

Country of ref document: BR

Free format text: APRESENTAR A TRADUCAO SIMPLES DA FOLHA DE ROSTO DA CERTIDAO DE DEPOSITO DA PRIORIDADE CN 201910376533.2 DE 03/05/2019 OU DECLARACAO CONTENDO, OBRIGATORIAMENTE, TODOS OS DADOS IDENTIFICADORES DESTA CONFORME O ART. 15 DA PORTARIA 39/2021. O DOCUMENTO APRESENTADO NAO ESTA TRADUZIDO.

WWP Wipo information: published in national office

Ref document number: MX/A/2021/013469

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 112021022042

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20211103

WWG Wipo information: grant in national office

Ref document number: 202127049945

Country of ref document: IN

WWG Wipo information: grant in national office

Ref document number: MX/A/2021/013469

Country of ref document: MX