WO2022082789A1 - 复用关系上报方法及通信装置 - Google Patents

复用关系上报方法及通信装置 Download PDF

Info

Publication number
WO2022082789A1
WO2022082789A1 PCT/CN2020/123438 CN2020123438W WO2022082789A1 WO 2022082789 A1 WO2022082789 A1 WO 2022082789A1 CN 2020123438 W CN2020123438 W CN 2020123438W WO 2022082789 A1 WO2022082789 A1 WO 2022082789A1
Authority
WO
WIPO (PCT)
Prior art keywords
sul
node
information
resource
carrier
Prior art date
Application number
PCT/CN2020/123438
Other languages
English (en)
French (fr)
Inventor
袁世通
刘凤威
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2020/123438 priority Critical patent/WO2022082789A1/zh
Publication of WO2022082789A1 publication Critical patent/WO2022082789A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and a communication device for reporting a multiplexing relationship.
  • a cell consists of one downlink carrier and one uplink carrier.
  • NR new radio
  • UE user equipment
  • the UE in the cell edge area can receive signals from the base station.
  • the base station cannot receive the signal from the UE, that is, there is a problem of asymmetric uplink and downlink coverage.
  • SUL supplementary uplink
  • a cell supporting SUL configuration may include one downlink carrier and two uplink carriers, one of the two uplink carriers is called the SUL carrier (carrier), and the other uplink carrier is called the normal uplink (NUL) carrier.
  • a relay node In order to improve spectrum utilization, the deployment density of base stations can be increased. With the increase in the deployment density of base stations, in order to save the cost of fiber deployment between the base station and the core network, a relay node (RN) is introduced. The relay node establishes a connection with the core network based on the wireless backhaul link, thereby saving the cost of fiber deployment. Generally, a relay node can establish a wireless backhaul link with one or more upper-level nodes, and access the core network based on the upper-level node; the relay node can provide services for one or more lower-level nodes.
  • the in-band relay scheme refers to a relay scheme in which the backhaul link and the access link share the same frequency band, which has the advantages of high spectral efficiency and low deployment cost.
  • Integrated access and backhaul is an in-band relay scheme, and in the in-band relay scheme, a relay node may be called an IAB node (node).
  • the upper-level node of the IAB node may be a base station or another IAB node; the lower-level node of the IAB node may be a UE or another IAB node.
  • the present application provides a method and a communication device for reporting a multiplexing relationship.
  • the reporting of the multiplexing relationship related to the SUL carrier can be implemented, which is helpful for configuring resources for the SUL carrier.
  • the present application provides a method for reporting a multiplexing relationship.
  • the method is applied to a communication system of a first node and a second node, where the first node is an upper-level node or a host node of the second node, and the second node includes a mobile terminal. and distributed units.
  • the method may be executed by the second node, or may also be executed by a chip configured in the second node, which is not limited in this application.
  • the method includes: the second node sends multiplexing relationship information to the first node, where the multiplexing relationship information is used to indicate one or more of the following: the second node sends the multiplexing relationship information to the first node; multiplexing relationship information is sent to the first node; The relationship information is used to indicate one or more of the following multiplexing relationships: the multiplexing relationship between the SUL carrier of the first cell corresponding to the mobile terminal and the NUL carrier of the second cell corresponding to the distributed unit; The multiplexing relationship between the NUL carrier of the cell and the SUL carrier of the second cell corresponding to the distributed unit; the multiplexing between the SUL carrier of the first cell corresponding to the mobile terminal and the SUL carrier of the second cell corresponding to the distributed unit relation.
  • the second node reports the SUL carrier-related multiplexing relationship to the first node, so that the first node can configure resources for the SUL carrier according to the multiplexing relationship, thereby improving network resource utilization. Rate.
  • the second node receives the first configuration information from the first node.
  • the distributed unit of the second node receives the first configuration information.
  • the first configuration information is used to configure SUL resource information
  • the SUL resource information is used to support uplink reception by the second cell through the SUL carrier.
  • the SUL resource information includes one or more SUL resources and resource attributes of the SUL resources, where the resource attribute is always available, indicating whether it is available or unavailable.
  • the first node supports uplink reception of the second cell of the second node through the SUL carrier through the first configuration information, so as to improve the utilization rate of network resources.
  • the first configuration information is carried in the cell resource configuration signaling, which can implement the configuration of SUL resources and NUL resources, thereby saving signaling overhead.
  • one second cell may correspond to one or more SUL resources
  • one or more SUL resources may correspond to one SUL resource configuration identifier.
  • SUL resources are associated with one or more second cells through the SUL resource configuration identifiers corresponding to the SUL resources, and it is no longer necessary to add the specific resource configuration of the SUL in the resource configuration of each cell, which can simplify the configuration of the SUL resources and reduce the overhead.
  • the resource attribute of the SUL resource is to indicate whether the SUL resource is available
  • the second node receives the SUL resource availability indication information from the first node
  • the SUL resource availability indication information is used to indicate that the SUL resource is available. or unavailable.
  • the availability or unavailability of the SUL resource is indicated by the SUL resource availability indication information, so that the second node can reasonably use the SUL resource.
  • the RRC signaling is used to indicate the location of the SUL resource availability indication information in the DCI
  • the second node may determine the location of the SUL resource availability indication information in the DCI according to the RRC signaling. position, so as to learn the SUL resource availability indication information from the DCI.
  • the RRC signaling is used to indicate the location of the SUL resource configuration identifier in the DCI; the second node determines, according to the RRC signaling, that the SUL resource availability indication information corresponding to the SUL resource configuration identifier is in the The position in the DCI, so that the SUL resource availability indication information corresponding to the SUL resource configuration identifier is obtained from the DCI.
  • the RRC signaling is used to indicate the location of the resource availability indication information of a certain second cell in the DCI, and the identifier after the cell ID of the second cell is used to indicate the resource
  • the availability indication information is applicable to the SUL resource, so as to realize the indication of whether the SUL resource is available.
  • the foregoing multiplexing relationship information includes one or more of a configuration index of the SUL configuration information, a SUL bandwidth number, or a SUL identifier.
  • the second node receives the second configuration information, and determines the foregoing multiplexing relationship information according to the second configuration information.
  • the second configuration information may come from the core network device or the first node.
  • the second configuration information includes SUL configuration information.
  • the second configuration information includes SUL configuration information and a configuration index of the SUL configuration information.
  • the SUL configuration information includes one or more of SUL bandwidth list, SUL transmission bandwidth, SUL frequency offset, SUL absolute wireless channel number, SUL bandwidth number, and SUL carrier list.
  • the second node can obtain the SUL frequency band and related information configured for it, and can determine the multiplexing relationship according to the second configuration information.
  • the second node sends capability information to the first node.
  • the capability information includes SUL information
  • the SUL information includes the configuration index of the SUL configuration information, the SUL bandwidth list, the SUL transmission bandwidth, the SUL frequency offset, the SUL bandwidth number, the SUL absolute wireless channel number, the SUL carrier list, and the SUL subcarrier interval. one or more of.
  • the second node notifies the first node of the SUL frequency band and related information supported by the second node by reporting the capability information, so that the first node can configure SUL resources.
  • the second node sends symbol indication information to the first node, and the symbol indication information is used to indicate that the number of protection symbols sent by the second node is the number of protection symbols in the SUL scenario, to Distinguish whether the reported number of protection symbols is in the SUL scenario or in the NUL scenario.
  • the above-mentioned symbol indication information is indicated by a newly defined logical channel identifier, and the newly defined logical channel identifier does not overlap with the existing logical channel identifier.
  • the above-mentioned symbol indication information is indicated by the uplink transmission resources of the SUL. It can be understood that the number of protection symbols sent through the NUL uplink transmission resource is the number of protection symbols in the NUL scenario; the number of protection symbols sent through the SUL uplink transmission resource is the number of protection symbols in the SUL scenario.
  • the present application provides a multiplexing relationship reporting method, which is applied to a communication system of a first node and a second node, where the first node is an upper-level node or a host node of the second node, and the second node includes a mobile terminal and distributed units.
  • the method may be executed by the first node, or may also be executed by a chip configured in the first node, which is not limited in this application.
  • the first node receives the multiplexing relationship information from the distributed units of the second node; determines the first configuration information according to the multiplexing relationship information; the multiplexing relationship information is used to indicate one or more of the following multiplexing relationships: mobile The multiplexing relationship between the SUL carrier of the first cell corresponding to the terminal and the NUL carrier of the second cell corresponding to the distributed unit; the NUL carrier of the first cell corresponding to the mobile terminal and the SUL carrier of the second cell corresponding to the distributed unit The multiplexing relationship between; the multiplexing relationship between the SUL carrier of the first cell corresponding to the mobile terminal and the SUL carrier of the second cell corresponding to the distributed unit.
  • the second node reports the SUL carrier-related multiplexing relationship to the first node, so that the first node can configure resources for the SUL carrier according to the multiplexing relationship, thereby improving network resource utilization. Rate.
  • the first node sends the first configuration information to the second node.
  • the first node sends the first configuration information to the distributed unit of the second node.
  • the first configuration information is used to configure SUL resource information
  • the SUL resource information is used to support uplink reception by the second cell through the SUL carrier.
  • the SUL resource information includes one or more SUL resources and resource attributes of the SUL resources, where the resource attribute is always available, indicating whether it is available or unavailable.
  • the first node supports uplink reception of the second cell of the second node through the SUL carrier through the first configuration information, so as to improve the utilization rate of network resources.
  • one second cell may correspond to one or more SUL resources
  • one or more SUL resources may correspond to one SUL resource configuration identifier.
  • SUL resources are associated with one or more second cells through the SUL resource configuration identifiers corresponding to the SUL resources, and it is no longer necessary to add the specific resource configuration of the SUL in the resource configuration of each cell, which can simplify the configuration of the SUL resources and reduce the overhead.
  • the first node sends SUL resource availability indication information to the second node.
  • the SUL resource availability indication information is used to indicate that the SUL resource is available or unavailable.
  • the availability or unavailability of the SUL resource is indicated by the SUL resource availability indication information, so that the second node can reasonably use the SUL resource.
  • the foregoing multiplexing relationship information includes one or more of a configuration index of the SUL configuration information, a SUL bandwidth number, or a SUL identifier.
  • the first node sends the second configuration information to the second node.
  • the first node sends the second configuration information to the mobile terminal of the second node.
  • the second configuration information includes SUL configuration information.
  • the second configuration information includes SUL configuration information and a configuration index of the SUL configuration information.
  • the SUL configuration information includes one or more of SUL bandwidth list, SUL transmission bandwidth, SUL frequency offset, SUL absolute wireless channel number, SUL bandwidth number, and SUL carrier list.
  • the second node can obtain the SUL frequency band and related information configured for it, and can determine the multiplexing relationship according to the second configuration information.
  • the first node receives capability information from the second node, the capability information includes SUL information, and the SUL information includes a configuration index of the SUL configuration information, a SUL bandwidth list, a SUL transmission bandwidth, One or more of SUL frequency offset, SUL bandwidth number, SUL absolute radio channel number, SUL carrier list, and SUL subcarrier spacing.
  • the first node obtains the capability information of the second node, and can configure SUL resources for the second node according to the capability information.
  • the first node receives symbol indication information from the second node, and the symbol indication information is used to indicate that the number of the first protection symbols sent by the second node is the protection symbols in the SUL scenario number, in order to distinguish whether the number of protection symbols reported is in the SUL scenario or the NUL scenario.
  • the above-mentioned symbol indication information is indicated by a newly defined logical channel identifier.
  • the above-mentioned symbol indication information is indicated by the uplink transmission resources of the SUL.
  • the present application further provides a communication device.
  • the communication device has part or all of the functions of the second node described in the first aspect.
  • the function of the device may have the function of some or all of the embodiments of the second node in this application, and may also have the function of independently implementing any one of the embodiments of this application.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a processing unit and a communication unit, and the processing unit is configured to support the communication device to perform the corresponding functions in the above method.
  • the communication unit is used to support communication between the communication device and other devices.
  • the communication device may also include a storage unit for coupling with the processing unit and the communication unit, which stores program instructions and data necessary for the communication device.
  • the communication device includes:
  • a communication unit configured to send multiplexing relationship information to the first node, where the multiplexing relationship information is used to indicate one or more of the following: the second node sends the multiplexing relationship information to the first node; the multiplexing relationship information is used to indicate One or more of the following multiplexing relationships: the multiplexing relationship between the SUL carrier of the first cell corresponding to the mobile terminal and the NUL carrier of the second cell corresponding to the distributed unit; the NUL carrier of the first cell corresponding to the mobile terminal and the NUL carrier of the second cell corresponding to the distributed unit The multiplexing relationship between the SUL carriers of the second cell corresponding to the distributed unit; the multiplexing relationship between the SUL carrier of the first cell corresponding to the mobile terminal and the SUL carrier of the second cell corresponding to the distributed unit.
  • the communication device may include:
  • a processor configured to send the multiplexing relationship information to the first node through the transceiver, where the multiplexing relationship information is used to indicate one or more of the following: the second node sends the multiplexing relationship information to the first node; the multiplexing relationship information It is used to indicate one or more of the following multiplexing relationships: the multiplexing relationship between the SUL carrier of the first cell corresponding to the mobile terminal and the NUL carrier of the second cell corresponding to the distributed unit; The multiplexing relationship between the NUL carrier and the SUL carrier of the second cell corresponding to the distributed unit; the multiplexing relationship between the SUL carrier of the first cell corresponding to the mobile terminal and the SUL carrier of the second cell corresponding to the distributed unit.
  • the present application further provides a communication device.
  • the communication device has part or all of the functions of the first node described in the first aspect.
  • the function of the device may have the function of some or all of the embodiments of the first node in this application, and may also have the function of independently implementing any one of the embodiments of this application.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a processing unit and a communication unit, and the processing unit is configured to support the communication device to perform the corresponding functions in the above method.
  • the communication unit is used to support communication between the communication device and other devices.
  • the communication device may also include a storage unit for coupling with the processing unit and the communication unit, which stores program instructions and data necessary for the communication device.
  • the communication device includes:
  • a communication unit configured to receive multiplexing relationship information from the second node, where the multiplexing relationship information is used to indicate one or more of the following multiplexing relationships: the SUL carrier of the first cell corresponding to the mobile terminal and the SUL carrier corresponding to the distributed unit The multiplexing relationship between the NUL carriers of the second cell; the multiplexing relationship between the NUL carriers of the first cell corresponding to the mobile terminal and the SUL carriers of the second cell corresponding to the distributed unit; the multiplexing relationship of the first cell corresponding to the mobile terminal The multiplexing relationship between the SUL carrier and the SUL carrier of the second cell corresponding to the distributed unit;
  • the processing unit is configured to determine the first configuration information according to the multiplexing relationship information.
  • the communication device may include:
  • a processor configured to receive the multiplexing relationship information from the second node through the transceiver; determine the first configuration information according to the multiplexing relationship information; the multiplexing relationship information is used to indicate one or more of the following multiplexing relationships: The multiplexing relationship between the SUL carrier of the first cell corresponding to the mobile terminal and the NUL carrier of the second cell corresponding to the distributed unit; the NUL carrier of the first cell corresponding to the mobile terminal and the SUL of the second cell corresponding to the distributed unit The multiplexing relationship between carriers; the multiplexing relationship between the SUL carrier of the first cell corresponding to the mobile terminal and the SUL carrier of the second cell corresponding to the distributed unit.
  • the processor may be used to perform, for example but not limited to, baseband related processing
  • the transceiver may be used to perform, for example but not limited to, radio frequency transceiving.
  • the above-mentioned devices may be respectively arranged on chips that are independent of each other, or at least part or all of them may be arranged on the same chip.
  • processors can be further divided into analog baseband processors and digital baseband processors.
  • the analog baseband processor can be integrated with the transceiver on the same chip, and the digital baseband processor can be set on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip.
  • a digital baseband processor can be integrated with a variety of application processors (such as but not limited to graphics processors, multimedia processors, etc.) on the same chip.
  • application processors such as but not limited to graphics processors, multimedia processors, etc.
  • Such a chip may be called a System on Chip. Whether each device is independently arranged on different chips or integrated on one or more chips often depends on the needs of product design. The embodiments of the present application do not limit the implementation form of the foregoing device.
  • the present application further provides a processor for executing the above-mentioned various methods.
  • the process of sending and receiving the above-mentioned information in the above-mentioned methods can be understood as the process of outputting the above-mentioned information by the processor and the process of receiving the above-mentioned input information by the processor.
  • the processor When outputting the above-mentioned information, the processor outputs the above-mentioned information to the transceiver for transmission by the transceiver. After the above-mentioned information is output by the processor, other processing may be required before reaching the transceiver.
  • the transceiver receives the above-mentioned information and inputs it into the processor. Furthermore, after the transceiver receives the above-mentioned information, the above-mentioned information may need to perform other processing before being input to the processor.
  • the sending of the multiplexing relationship information mentioned in the foregoing method can be understood as the processor outputting the multiplexing relationship information.
  • the above-mentioned processor may be a processor specially used to execute these methods, or may be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor.
  • the above-mentioned memory can be a non-transitory (non-transitory) memory, such as a read-only memory (Read Only Memory, ROM), which can be integrated with the processor on the same chip, or can be set on different chips respectively.
  • ROM read-only memory
  • the embodiment does not limit the type of the memory and the setting manner of the memory and the processor.
  • the present application provides a computer-readable storage medium for storing computer software instructions, and when the instructions are executed by a computer, the method described in the first aspect or the second aspect is implemented.
  • the present application further provides a computer program product comprising instructions, which, when executed on a computer, cause the computer to perform the method described in the first aspect or the second aspect.
  • the present application provides a chip system, the chip system includes at least one processor and a communication interface, the at least one processor is used for executing a computer program, and the communication interface is used for inputting and/or outputting information such that The second node implements the functions involved in the first aspect, or the first node implements the functions involved in the second aspect.
  • the chip system further includes a memory for storing necessary program instructions and data of the second node or the first node.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • Fig. 1 is an example diagram of a kind of IAB system
  • Fig. 2 is a kind of example diagram that DCI instructs
  • Fig. 3 is a format example diagram of MAC CE
  • FIG. 4 is an example diagram of a SUL link and a NUL link
  • FIG. 5 is a schematic diagram of a network architecture applied to the present application.
  • FIG. 6 is a schematic flowchart of a method for reporting a multiplexing relationship provided by the present application.
  • FIG. 6a is an example diagram of a kind of SUL resource availability indication information provided by this application.
  • FIG. 6b is an example diagram of another SUL resource availability indication information provided by this application.
  • FIG. 6c is an example diagram of yet another SUL resource availability indication information provided by this application.
  • FIG. 8 is a schematic flowchart of sending compliance indication information provided by the present application.
  • FIG. 8a is an example diagram of a compliance indication information provided by the present application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by the present application.
  • FIG. 10 is another schematic structural diagram of the communication device provided by the application.
  • FIG. 11 is a schematic structural diagram of an IAB node provided by this application.
  • a relay node can establish a wireless backhaul link with one or more upper-level nodes, and access the core network through the upper-level nodes.
  • the upper node can perform certain control (eg, data scheduling, timing modulation, power control, etc.) on the relay node through various signaling.
  • a relay node may serve one or more subordinate nodes.
  • the in-band relay scheme in a new radio (NR) system may be referred to as IAB.
  • the relay node can be called an IAB node (node), the upper-level node of the IAB node can be a base station, or another IAB node; the lower-level node of the IAB node can be a UE, or another IAB node.
  • IAB node node
  • the upper-level node of the IAB node can be a base station, or another IAB node
  • the lower-level node of the IAB node can be a UE, or another IAB node.
  • the upper node refers to the node that provides resources for the wireless backhaul link
  • the base station can be the upper node of the IAB node
  • the lower node refers to the use of wireless backhaul link resources to transmit data to the network and/or the node receiving data from the network, eg, the UE may be a subordinate node of the IAB node.
  • the network may be a core network or a network on other access networks, such as the Internet or a private network.
  • An upper-level node can also be described as a parent node or an upstream node, etc., and a lower-level node can also be described as a child node or a downstream node, etc.
  • An IAB system may include at least one base station 100, and one or more IAB nodes 110.
  • the base station 100 may provide services for one or more UEs 101 , and may also provide services for one or more IAB nodes 110 .
  • the IAB node 110 may serve one or more UEs 111 .
  • the base station 100 may be referred to as 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 .
  • DgNB donor next generation node B
  • the host base station can also be described as a host node, a donor node, an IAB donor, or an IAB host node, etc. In this application, the description is taken as an example of an IAB donor.
  • the IAB system may also include a number of other IAB nodes, such as IAB node 120 and IAB node 130 .
  • the IAB node 120 is connected to the IAB node 110 via a wireless backhaul link 123 for access to the network.
  • the IAB node 130 is connected to the IAB node 110 via a wireless backhaul link 133 for access to the network.
  • the IAB node 120 may serve one or more UEs 121 and the IAB node 130 may serve one or more UEs 131 .
  • IAB node 110, IAB node 120, and IAB node 130 can all access the network through wireless backhaul links. In this application, the wireless backhaul links are all viewed from the point of view of the IAB node.
  • the wireless backhaul link 113 is the backhaul link of the IAB node 110
  • the wireless backhaul link 123 is the backhaul link of the IAB node 120
  • the backhaul link, the wireless backhaul link 133 is the backhaul link for the IAB node 130 .
  • the IAB node can directly access the network, for example, the IAB node 110 is connected to the network through the wireless backhaul link 113; it can also access the network through a multi-level relay node, for example, the IAB node 120 is first connected through the wireless backhaul link 123 The IAB node 110 is then connected to the network through the wireless backhaul link 113 of the IAB node 110 .
  • a multi-level relay node for example, the IAB node 120 is first connected through the wireless backhaul link 123 The IAB node 110 is then connected to the network through the wireless backhaul link 113 of the IAB node 110 .
  • An IAB node can generally refer to any node or device with a relay function.
  • the IAB node in this application The use of and relay nodes should be understood to have the same meaning.
  • Figure 1 involves two transmission links, one is a wireless access link and the other is a wireless backhaul link.
  • the wireless access link which can also be described as an access link, refers to the link between the UE and the IAB node or IAB donor.
  • the radio access link includes a radio link used by a node to communicate with its subordinate nodes.
  • the radio 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.
  • the wireless backhaul link which can also be described as a backhaul link (backhaul, BH), refers to a link between an IAB node and an IAB child node or between an IAB node and an IAB parent node.
  • backhaul backhaul link
  • the wireless backhaul link includes a link for downlink transmission with the IAB child node or IAB parent node, and a link for uplink transmission between the IAB child node or IAB parent node.
  • An IAB node transmits data to its IAB parent node, or receives an uplink transmission from its IAB child node, which is referred to as the uplink transmission of the backhaul link.
  • An IAB node receives data transmissions from its IAB parent node, or data transmissions to its IAB child nodes are referred to as downlink transmissions on the backhaul link.
  • the backhaul link between the IAB node and its IAB parent node is also called the parent BH link
  • the backhaul link between the IAB node and its IAB child nodes is also called the parent BH link.
  • the path is called the subordinate backhaul link (child BH link).
  • a subordinate node can be regarded as a UE of an upper node.
  • one IAB node is connected to one upper-level node for example.
  • one IAB node, such as 120 can be connected to multiple upper-level nodes, that is, multiple upper-level nodes can simultaneously provide services for one IAB node. For example, in FIG. 1
  • the IAB node 130 can also be connected to the IAB node 120 through the wireless backhaul link a'a134, that is, both the IAB node 110 and the IAB node 120 can be regarded as the upper-level nodes of the IAB node 130.
  • the wireless links 102, 112, 122, 132, 113, 123, 133, a'a 134 may be bidirectional links, including uplink and downlink transmission links, in particular, the wireless backhaul links 113, 123, 133, a'a 134 may be used by the upper node to provide the lower node Services, such as a superior node (eg, base station 100 ) providing wireless backhaul services to a subordinate node (eg, IAB node 110 ). It should be understood that the uplink and downlink of the backhaul link may be separate, ie the uplink and downlink are not transmitted through the same node.
  • a superior node eg, base station 100
  • a subordinate node eg, IAB node 110
  • Downlink transmission refers to the transmission of information or data from a superior node (such as the base station 100) to a subordinate node (such as the IAB node 110); uplink transmission refers to the transmission of information or data from a subordinate node (such as the IAB node 110) to a superior node (such as the base station 100).
  • the nodes are not limited to the base station, the IAB node and the UE.
  • the UE may act as a relay node to serve other UEs.
  • the wireless backhaul link can also be an access link in some scenarios.
  • the wireless backhaul link 123 can also be regarded as an access link for the node 110, and the backhaul link 113 is also the connection of the node 100. into the 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 UE with a relay function.
  • the lower-level node may also be a UE.
  • the IAB node may include a mobile terminal (MT) and a distributed unit (DU).
  • MT is used for the communication between the IAB node and the upper node
  • the DU is used for the communication between the IAB node and the lower node.
  • the link where the MT communicates with the upper node may be referred to as the upper backhaul link
  • the link where the DU communicates with the lower node may be referred to as the lower backhaul link.
  • the subordinate backhaul link may also be referred to as the access link, eg, where the subordinate node of the DU is the UE.
  • an IAB donor may include a centralized unit (CU) and a DU.
  • CU centralized unit
  • DU mainly responsible for scheduling, physical signal generation and transmission.
  • the F1 interface application protocol (F1-application protocol, F1-AP) data packet generated by the IAB donor CU is encapsulated into an Internet Protocol (Internet Protocol, IP) packet, After the IP packet is delivered to the IAB node through the multi-hop node on the air interface, after processing by the MT adaptation layer of the IAB node, the IP packet is forwarded to the IAB node DU for processing, and the IAB node DU parses the IP packet to obtain the F1-AP data packet .
  • IP Internet Protocol
  • the multiplexing mode is time division multiplexing (TDM) Mode; when MT and DU work on the same time domain resources, or when access and backhaul are performed on the same time domain resources, the multiplexing mode is spatial division multiplexing (SDM) mode or full Duplex (full duplex, FD) mode.
  • TDM time division multiplexing
  • SDM spatial division multiplexing
  • FD full duplex
  • the multiplexing mode is the space division multiplexing mode; if the MT and the DU are both receiving and transmitting , or the backhaul and access both receive and transmit, then the multiplexing mode is full-duplex mode.
  • the implementation forms and hardware capabilities of the IAB nodes are different, so that different IAB nodes may support different multiplexing modes, so the IAB nodes apply capabilities to their superior nodes.
  • the multiplexing capability between the cell corresponding to the DU and the serving cell corresponding to the MT is reported through an information element (information element, IE).
  • IE information element
  • IAB-MT Cell Item is used to identify a serving cell corresponding to MT
  • NR Cell Identity is used to identify a cell corresponding to DU
  • Presence is M, which means carrying parameter items, that is, carrying support or not support.
  • the IAB node DU reports to its superior node CU whether the cell identified by "NR Cell Identity” and the serving cell identified by "IAB-MT Cell Item” can transmit or receive at the same time.
  • DU_RX/MT_RX indicates whether the cell corresponding to the DU and the serving cell corresponding to the MT can receive at the same time.
  • the IAB node is configured with MT resources and DU resources.
  • the MT resource can be configured as three resource types, namely downlink (downlink, D), uplink (uplink, U), and flexible (flexible, F).
  • the donor base station of the IAB node can configure the type of MT resource for the IAB node through signaling.
  • the MT resource of the IAB node has three resource types,
  • DU resources can be configured into four resource types, namely uplink, downlink, flexible, and not available (NA). Unavailable can also be described as disabled or unavailable, etc. Further, DU-uplink resources and DU-flexible resources can be further divided into hard (hard) resources and soft (soft) resources. Among them, hard resources represent resources that are always available to DUs; soft resources, whether DUs are available or not, depend on the instructions of upper-level nodes.
  • the DU resource of the IAB node has seven resource types.
  • the IAB donor CU sends resource configuration information to the IAB node DU through F1-AP signaling, where the resource configuration information is used to configure the resource attributes of the DU resources and the transmission direction of the DU.
  • the resource configuration information can be "gNB-DU Cell Resource Configuration” included in "GNB-DU RESOURCE CONFIGURATION”, DUF Slot related configuration in "gNB-DU Cell Resource Configuration” is used to configure the transmission direction of DU, "gNB-DU Cell Resource Configuration”
  • the HSNA Slot-related configuration in "Cell Resource Configuration” is used to configure the resource attributes (hard, soft, not available) of DU resources.
  • the superior node of the IAB node indicates the availability through downlink control information (downlink control indication, DCI).
  • DCI downlink control indication
  • the position indicated by the arrow indicates the position of the availability indication (AI) of the cell p corresponding to the DU in the DCI 2_5 signaling, and the dark gray area from this position in the DCI 2_5 signaling indicates that the DU corresponds to the AI index field value of cell p.
  • the location of the cell p corresponding to the DU in the DCI 2_5 can be configured by radio resource control (radio resource control, RRC) signaling.
  • RRC radio resource control
  • the maximum length of the DCI 2_5 signaling is 128 bits, and the cell p may be any one of the cells corresponding to the DU.
  • the AI index field value can be indicated by 3 bits, and every 3 bits in DCI 2_5 indicate the availability of a time slot. The possible values of the AI index field value and its meaning can be seen in Table 2 below.
  • AI index field value meaning 0 No soft symbols are indicated to be available 1 Only DL soft symbols are indicated to be available 2 Only UL soft symbols are indicated to be available 3 Only DL and UL soft symbols are indicated to be available 4 Only flexible soft symbols are indicated to be available 5 Only DL and flexible soft notation are indicated to be available 6 Only UL and flexible soft symbols are indicated to be available 7 DL, UL and flexible soft symbols are indicated as available
  • the diversity of IAB node implementations and the diversity of switching scenarios between MT and DU may require a certain amount of time for the transceiving between MT and DU. Therefore, the IAB node MT reports the number of protection symbols to its superior node. For example, see Table 3.
  • the handover scenarios in Table 3 involve MT to DU, DU to MT, uplink to downlink, downlink to uplink, uplink to uplink, downlink to downlink, and various situations.
  • the number of protection symbols corresponding to each case is indicated by a medium access control (MAC) control element (control element, CE).
  • CE medium access control
  • the MAC CE composed of 4 8-bit information is used for indication.
  • the format of the 4 8-bit information can be referred to as shown in Figure 3.
  • R represents reserved bits
  • SCS represents subcarriers. interval.
  • a cell that supports SUL configuration can include one downlink carrier and two uplink carriers.
  • One uplink carrier of the two uplink carriers is called the SUL carrier, and the other uplink carrier is called the NUL carrier.
  • the NUL carrier is the cell that is not configured with SUL. the upstream carrier.
  • the UE in the idle state can determine which uplink carrier to use for access according to the reference signal receiving power (RSRP) in the downlink measurement result.
  • RSRP reference signal receiving power
  • the NUL link is used at the near point and the SUL link is used at the far point, as shown in FIG. 4 .
  • one of the uplink links is selected for uplink access, and two links cannot be scheduled at the same time.
  • the base station may configure the SUL carrier for the UE through serving cell configuration information (servingCell config).
  • servingCell config serving cell configuration information
  • the base station can directly schedule the UE to transmit the physical uplink shared channel (PUSCH) on the SUL carrier through DCI.
  • the configuration information of the serving cell includes the physical cell identity (physical cell identity, PCI) of the serving cell, downlink configuration information, uplink configuration information and SUL configuration information, See below.
  • the present application provides a multiplexing relationship reporting method and communication device, which can realize the reporting of the multiplexing relationship related to the SUL carrier when the SUL carrier is applied to the IAB system, which helps to configure resources for the SUL carrier.
  • a, b, or c may represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c Can be single or multiple.
  • words such as “first” and “second” are used to distinguish technical features with substantially the same or similar functions. Those skilled in the art can understand that the words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • the techniques described in this application can be used in various communication systems, such as a 4th generation (4G) communication system, a 4.5G communication system, a 5G communication system, a system where multiple communication systems are converged, or a communication system that evolves in the future.
  • 4G 4th generation
  • 4.5G communication system
  • 5G 5th generation
  • LTE long term evolution
  • NR new radio
  • WiFi wireless-fidelity
  • 3GPP 3rd generation partnership project
  • the UE (also referred to as a terminal) involved in this application can be a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); It can also be deployed in the air (eg on airplanes, balloons, satellites, etc.).
  • UEs include handheld devices, in-vehicle devices, wearable devices or computing devices with wireless communication capabilities.
  • the UE may be a mobile phone, a tablet computer, or a computer with a wireless transceiver function.
  • the terminal device may also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a smart vehicle (smart vehicle) terminal device, a wireless terminal in industrial control, and a wireless terminal in unmanned driving.
  • VR virtual reality
  • AR augmented reality
  • smart vehicle smart vehicle terminal device
  • wireless terminals in telemedicine wireless terminals in smart grids, wireless terminals in smart cities, wireless terminals in smart homes, and so on.
  • the UE may be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories.
  • Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets, smart jewelry, etc. for physical sign monitoring.
  • UE may be a terminal in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • the terminal in this application may be a terminal in machine type communication (MTC).
  • MTC machine type communication
  • the terminal of the present application may be an on-board module, on-board module, on-board component, on-board chip or on-board unit built into the vehicle as one or more components or units, and the vehicle passes through the built-in on-board module, on-board module, on-board component , on-board chip or on-board unit can implement the method of the present application. Therefore, the present application can be applied to the Internet of Vehicles, such as vehicle to everything (V2X), long term evolution vehicle (LTE-V), vehicle to vehicle (V2V), etc.
  • V2X vehicle to everything
  • LTE-V long term evolution vehicle
  • V2V vehicle to vehicle
  • the base station (base station, BS) involved in this application may be a device deployed in a wireless access network and capable of wirelessly communicating with a terminal device.
  • the base station may have various forms, such as a macro base station, a micro base station, a relay station, and an access point.
  • the base station involved in this application may be a base station in 5G or a base station in long term evolution (LTE), where the base station in 5G may also be called a transmission reception point (transmission reception point, TRP) Or next generation Node B (gNB).
  • a base station may include a distributed unit (distribute unit, DU) and a centralized unit (centralized unit, CU).
  • FIG. 5 is a schematic diagram of a network architecture applied to the present application.
  • the network architecture includes a first node 501 and a second node 502, the first node may be an IAB donor, the second node may be an IAB node, and the IAB node includes MT and DU.
  • the first node 501 is an upper-level node of the second node 502#1, or is referred to as a host node; the second node 502#1 may be an upper-level node of the second node 502#2.
  • the network architecture further includes UE503, UE503#1 can access the first node 501, and UE503#2 can access the second node 502#1. It should be noted that the number and shape of the nodes shown in FIG. 5 are only for example, and do not constitute a limitation to the present application.
  • the second node 502#1 sends the multiplexing relationship information of the second node 502#1 to the first node 501, and the multiplexing relationship information is used to indicate one or more of the following multiplexing relationships: (1) the first The multiplexing relationship between the SUL carrier of the first cell corresponding to the MT of the second node 502#1 and the NUL carrier of the second cell corresponding to the DU of the second node 502#1; (2) the first cell corresponding to the MT The multiplexing relationship between the NUL carrier and the SUL carrier of the second cell corresponding to the DU; (3) the multiplexing relationship between the SUL carrier of the first cell corresponding to the MT and the SUL carrier of the second cell corresponding to the DU.
  • the second node 502#2 sends the multiplexing relationship information of the second node 502#2 to the first node 501 through the second node 502#1.
  • the second node reports the multiplexing relationship related to the SUL carrier, which helps the IAB donor to configure resources for the SUL carrier, thereby improving the network spectrum efficiency.
  • the first node 501 determines SUL resource information for the second node according to the multiplexing relationship information reported by the second node, and sends the SUL resource information to the second node, where the SUL resource information is used to support DU correspondence
  • the second cell performs uplink reception through the SUL carrier, thereby implementing resource configuration for the SUL carrier.
  • the first node 501 also sends SUL resource availability indication information to the second node, which is used to indicate that the SUL resource whose resource attribute is soft is available or unavailable, so as to realize the availability indication of the SUL resource.
  • the second node 502#1 sends symbol indication information to the first node, which is used to indicate that the number of protection symbols sent by the second node 502#1 is the number of protection symbols in the SUL scenario, so as to distinguish the number of protection symbols in the SUL scenario The number of protection symbols to report and the number of protection symbols to report in the NUL scenario.
  • the multiplexing relationship reporting method is applied to a communication system including a first node and a second node, where the first node is an upper-level node or a host node of the second node, and the second node includes an MT and a DU.
  • the communication system is not limited to the IAB system, and the IAB system is taken as an example for introduction. It should be noted that the names of information or data exchanged between nodes are used as examples, and do not constitute a limitation to the present application.
  • FIG. 6 is a schematic flowchart of a method for reporting a multiplexing relationship provided by the present application.
  • the process may include but is not limited to the following steps:
  • Step 601 the second node sends the multiplexing relationship information to the first node.
  • the first node receives the multiplexing relationship information from the second node.
  • the IAB node sends the multiplexing relationship information to the IAB donor; or the IAB node sends the multiplexing relationship information to its upper-level node IAB node, and the upper-level node sends the multiplexing relationship information to the IAB donor.
  • the IAB DU sends the multiplexing relationship information to the first node.
  • the multiplexing relationship information is used to indicate the multiplexing relationship between the SUL carrier or NUL carrier of the first cell corresponding to the MT and the SUL carrier or NUL carrier of the second cell corresponding to the DU. Specifically, the multiplexing relationship information is used to indicate one or more of the following multiplexing relationships:
  • the above-mentioned multiplexing relationships (1) to (3) can be understood as the multiplexing relationship related to the SUL carrier, that is, the multiplexing relationship between the first cell corresponding to the MT and the second cell corresponding to the DU under the consideration of the SUL carrier;
  • the multiplexing relationship (4) can be understood as the multiplexing relationship between the first cell corresponding to the MT and the second cell corresponding to the DU without considering the SUL carrier.
  • the first cell may be understood as a serving cell.
  • Step 602 the first node determines the first configuration information according to the multiplexing relationship information.
  • the IAB donor configures the SUL resource information for the IAB DU according to the multiplexing relationship information reported by the IAB node.
  • the first configuration information is used to configure SUL resource information, and is specifically used to configure SUL resource information for DUs.
  • the SUL resource information is used to support uplink reception by the second cell through the SUL carrier.
  • the SUL resource information includes one or more SUL resources.
  • the SUL resource information includes resource attributes of each SUL resource.
  • the SUL resource information includes one or more SUL resources and resource attributes of each SUL resource. Among them, the resource attribute can be always available (hard), indicating whether it is available (soft) or unavailable.
  • the first node determines the first configuration information according to the multiplexing relationship information. In another implementation manner, the first node determines the first configuration information according to capability information of the second node.
  • the capability information is introduced in the embodiment shown in FIG. 7 .
  • step 603 the first node sends the first configuration information to the second node.
  • the second node receives the first configuration information from the first node.
  • the first node sends the first configuration information to the DU of the second node.
  • the first configuration information is carried in cell resource configuration signaling, and the cell resource configuration signaling may be gNB-DU Cell Resource Configuration signaling.
  • the gNB-DU Cell Resource Configuration signaling is used to configure the resource attributes of the DU resources and the transmission direction of the DU; in the case of considering the SUL carrier, it is added in the gNB-DU Cell Resource Configuration signaling.
  • first configuration information The SUL resource configured by the first configuration information may be independent of the NUL resource of the second cell.
  • the resource configuration information of the second cell that is, the existing gNB-DU Cell Resource Configuration signaling
  • the SUL resource that is, the existing gNB-DU Cell Resource Configuration signaling
  • the SUL resources are configured independently, and the first configuration information may not be carried in the cell resource configuration signaling.
  • the number of second cells may be multiple, one second cell may correspond to one or more SUL resources, and one or more SUL resources may correspond to one SUL resource configuration identifier, for example, the SUL resources of cell 1 to cell 3 correspond to the SUL resource configuration Identifier 1, the SUL resources of cell 3 to cell 4 correspond to SUL resource configuration identifier 2.
  • the IAB node implements the configuration of the SUL resource for the DU by receiving the first configuration information.
  • step 604 is further included, in which the first node sends SUL resource availability indication information to the second node.
  • the second node receives the SUL resource availability indication information from the first node.
  • the superior node of the IAB node or the IAB donor sends the SUL resource availability indication information to the IAB node.
  • step 604 is performed.
  • the IAB MT receives SUL resource availability indication information.
  • indicating whether it is available should be understood as indicating that it is available, and not indicating that it is available. Not indicating available does not indicate unavailable, indicating that the upper-level node does not indicate whether the resource is available.
  • the SUL resource availability indication information is used to indicate that the SUL resource whose resource attribute is soft is available or unavailable.
  • the IAB MT receives the RRC signaling, which is used to indicate the location of the SUL resource availability indication information in the DCI; the IAB MT receives the DCI from its superior node, and the DCI includes the SUL resource availability indication information, according to the RRC The signaling determines the location of the SUL resource availability indication information in the DCI.
  • Mode 1 can be seen in Figure 6a.
  • the SUL resource availability indication information may be expressed as an AI index for SUL (AI index for SUL), and the DCI is DCI 2_5.
  • the RRC signaling can be used to indicate the location of the SUL resource availability indication information of each second cell in the DCI, and the DCI includes the SUL resource availability indication information of each second cell.
  • the DCI includes the SUL resource availability indication information of each second cell.
  • the IAB MT receives the RRC signaling from the IAB donor CU, and the RRC signaling is used to indicate the location of the SUL resource configuration identifier in the DCI; the IAB MT receives the DCI from its superior node, and the DCI includes the SUL resource configuration identifier
  • the position in the DCI of the SUL resource availability indication information corresponding to the SUL resource configuration identifier is determined according to the RRC signaling. For example, way 2 can be seen in Fig. 6c.
  • the IAB MT receives the RRC signaling from the IAB donor CU, and the RRC signaling is added after the cell ID of the second cell when configuring the location of the resource availability indication information of a second cell in the DCI
  • An identifier used to indicate whether the configuration is used for the SUL resource of the second cell. It can be understood that the RRC signaling can not only be used to configure the location of the resource availability indication information of the cell q in the DCI, but also can indicate whether the resource availability indication information is applicable to SUL resources through the identifier.
  • the DCI received by the IAB MT includes a feature identifier, and the feature identifier is used to indicate that the soft resource availability indication information is NUL resource availability indication information or SUL resource availability indication information.
  • the signature may be one or more bits in a fixed position in the DCI.
  • the feature identifier may be a bit, when the bit is "1", it indicates that the soft resource availability indication information is NUL resource availability indication information; when the bit is "0", it indicates that the soft resource availability indication information is SUL resource availability indication information.
  • the position of the feature bit in the DCI is specified by the protocol, or configured by the RRC.
  • the IAB donor configures a special control resource set (control resource set, CORESET) or availability indicator-radio network temporary identifier (AI-RNTI) for the SUL resource availability indication information;
  • IAB MT Receive signaling carrying SUL resource availability indication information on the corresponding downlink control channel resource, such as DCI 2_5; or receive DCI 2_5 scrambled by a specific AI-RNTI, indicating that DCI 2_5 is used to indicate whether the SUL resource whose resource attribute is soft is not available.
  • the protocol stipulates that the soft resource availability indication information in the DCI is used for all uplink carriers, that is, it is applicable to both SUL resources and NUL resources.
  • step 604 the IAB node determines whether the SUL resource is available by receiving the SUL resource availability indication information.
  • the IAB node reports the SUL carrier-related multiplexing relationship to the IAB donor, which helps the IAB donor to configure resources for the SUL carrier, thereby improving the network spectrum efficiency.
  • the above-mentioned multiplexing relationship information can be one of the following methods:
  • the multiplexing relationship information includes a configuration index of the SUL configuration information, which is used to indicate the multiplexing relationship related to the SUL frequency band identified by the configuration index.
  • the multiplexing relationship information may be a configuration index of the SUL configuration information added on the basis of the IE shown in Table 1.
  • the configuration index of the SUL configuration information may be carried in the second configuration information or capability information, and the second configuration information or capability information is introduced in the embodiment shown in FIG. 7 .
  • Example 1 add "IAB-MT SUL Item” under the "IAB-MT Cell Item” entry in the IE shown in Table 1, as shown in Table 5.
  • the "IAB-MT SUL Item” added under the "IAB-MT Cell Item” entry indicates the configuration index of the SUL configuration information for the MT, so that the above multiplexing relationship (1) can be indicated. It can be understood that the second node reports the multiplexing relationship between the SUL carrier of the first cell and the NUL carrier of the second cell to the first node through the IE.
  • this row indicates whether the reception by the second cell through the NUL carrier and the reception by the first cell through the SUL carrier can be performed simultaneously.
  • Example 2 add "IAB-DU SUL Item” under the "NR Cell Identity” entry in the IE shown in Table 1, as shown in Table 6. Adding "IAB-DU SUL Item” under the "NR Cell Identity” entry indicates the configuration index of the SUL configuration information for the DU, so that the above multiplexing relationship (2) can be indicated. It can be understood that the second node reports the multiplexing relationship between the NUL carrier of the first cell and the SUL carrier of the second cell to the first node through the IE.
  • this row indicates whether the reception by the second cell through the SUL carrier and the reception by the first cell through the NUL carrier can be performed simultaneously.
  • the multiplexing relationship information includes the SUL bandwidth number, which is used to indicate the multiplexing relationship related to the SUL frequency band corresponding to the SUL bandwidth number.
  • the multiplexing relationship information may be based on the IE shown in Table 1, adding the SUL bandwidth number.
  • the SUL bandwidth number may be carried in the second configuration information or capability information, and the second configuration information or capability information is introduced in the embodiment shown in FIG. 7 .
  • the SUL bandwidth number may be a protocol number predefined by the 3GPP protocol, for example, may be one or more of n80 to n89 and n95.
  • Example 3 add "IAB-MT SUL band list” under the "IAB-MT Cell Item” entry in the IE shown in Table 1, as shown in Table 7.
  • the "IAB-MT SUL band list” added under the "IAB-MT Cell Item” entry indicates the SUL bandwidth number for the MT, so that the above multiplexing relationship (1) can be indicated. It can be understood that the second node reports the multiplexing relationship between the SUL carrier of the first cell and the NUL carrier of the second cell to the first node through the IE.
  • Example 4 add "IAB-DU SUL band list” under the "IAB-MT Cell Item” entry in the IE shown in Table 1, as shown in Table 8.
  • the "IAB-DU SUL band list” added under the "IAB-DU Cell Item” entry indicates the SUL bandwidth number for the DU, so that the above multiplexing relationship (2) can be indicated. It can be understood that the second node reports the multiplexing relationship between the NUL carrier of the first cell and the SUL carrier of the second cell to the first node through the IE.
  • the multiplexing relationship information includes one or more of the foregoing multiplexing relationships (1) to (3).
  • the multiplexing relationship information may be based on the IE shown in Table 1, adding one or more of the following:
  • A may indicate whether the transmission of the second cell over the NUL carrier and the transmission of the first cell over the SUL carrier can be performed simultaneously.
  • Example 5 adding the above A and C to the IE shown in Table 1, as shown in Table 9, can indicate the above-mentioned multiplexing relationship (1).
  • the multiplexing relationship information includes the SUL identifier, which is used to indicate the multiplexing relationship of the SUL carriers of the first cell and/or the second cell identified by the SUL identifier.
  • the multiplexing relationship information may be based on the IE shown in Table 1, adding a SUL identifier.
  • Example 6 add "SUL flag” under the "IAB-MT Cell Item” entry in the IE shown in Table 1, as shown in Table 10. If “SUL flag” is true, it means that there is a multiplexing relationship related to the SUL carrier of the first cell, and if it is false, it means that there is no multiplexing relationship related to the SUL carrier of the first cell. It can be understood that the second node reports the multiplexing relationship between the SUL carrier of the first cell and the NUL carrier of the second cell to the first node through the IE.
  • Example 7 add "SUL flag” under the "NR Cell Identity” entry in the IE shown in Table 1. If “SUL flag” is true, it indicates that there is a multiplexing relationship related to the SUL carrier of the second cell. If it is false, it indicates that the first cell does not exist. The multiplexing relationship related to the SUL carriers of the two cells. It can be understood that the second node reports the multiplexing relationship between the NUL carrier of the first cell and the SUL carrier of the second cell to the first node through the IE.
  • FIG. 7 is a schematic flowchart of configuration information sending provided by this application.
  • the process may include but not limited to the following steps:
  • Step 701 The first node sends first configuration information to the second node.
  • the second node receives the first configuration information from the first node.
  • step 701 For the implementation process of step 701, reference may be made to the specific description of step 603, which will not be repeated here.
  • Step 702 The first node sends second configuration information to the second node.
  • the second node receives the second configuration information from the first node.
  • the first node sends the second configuration information to the MT of the second node.
  • the first configuration information is configured by the IAB donor for the IAB DU
  • the second configuration information is configured by the IAB donor for the IAB MT. It should be noted that the present application does not limit the order in which steps 701 and 702 are executed.
  • the second configuration information is used to configure SUL resource information for the MT, and the SUL resource information is used to support uplink transmission by the first cell through the SUL carrier.
  • the second configuration information includes SUL configuration information.
  • the second configuration information includes a configuration index of the SUL configuration information, which is used to identify the SUL configuration information.
  • the second configuration information includes SUL configuration information and a configuration index of the SUL configuration information.
  • the SUL configuration information includes one or more of SUL bandwidth list, SUL transmission bandwidth, SUL frequency offset, SUL absolute radio frequency channel number (absolute radio frequency channel number, ARFCN), SUL bandwidth number, and SUL carrier list.
  • the configuration index of the SUL configuration information can be added to the IE shown in Table 1 to indicate any of the above multiplexing relationships (1) to (3), which can save signaling overhead. Without considering the signaling overhead, the SUL configuration information may be added to the IE shown in Table 1 to indicate any of the above multiplexing relationships (1) to (3).
  • the SUL bandwidth number can be added to the IE shown in Table 1 to indicate any of the above multiplexing relationships (1) to (3), which can save signaling overhead.
  • the first node sends the second configuration information to the second node.
  • the core network device sends the second configuration information to the second node.
  • Core network equipment such as operation and maintenance servers (operation and maintenance, OAM).
  • OAM operation and maintenance servers
  • the core network equipment configures working frequency band resources for the IAB DU, where the working frequency band resources include at least one SUL frequency band, and the at least one SUL frequency band may be part of the frequency band resources on the SUL frequency band.
  • the at least one SUL frequency band is SUL configuration information
  • the working frequency band resource is the second configuration information
  • the working frequency band resource may further include a configuration index corresponding to the at least one SUL frequency band, that is, a configuration index of the SUL configuration information.
  • FIG. 7 further includes step 700, where the second node sends capability information to the first node.
  • the IAB DU sends capability information to the IAB donor.
  • the present application does not limit the order in which step 700 is performed in FIG. 7 .
  • the capability information includes whether the DU supports SUL, and the supported SUL information.
  • SUL information may include, but is not limited to, one or more of the following: configuration index of SUL configuration information, SUL bandwidth list, SUL transmission bandwidth, SUL frequency offset, SUL absolute radio channel number, SUL bandwidth number, SUL carrier list, SUL sub carrier spacing.
  • the configuration index or SUL bandwidth number of the SUL configuration information can be added to the IE shown in Table 1 to indicate any of the above multiplexing relationships (1) to (3), which can save signaling overhead.
  • the IAB donor may determine the first configuration information according to the capability information.
  • step 700 can be decoupled from step 701, that is, the IAB donor determines that the first configuration information has nothing to do with the capability information reported by the IAB node.
  • step 700 may be performed in FIG. 6 , and the order in which step 700 is performed in FIG. 6 is not limited.
  • the configuration of the SUL carrier for the DU is implemented through the first configuration information
  • the configuration of the SUL carrier for the MT is implemented through the second configuration information.
  • FIG. 8 is a schematic flowchart of a method for reporting a multiplexing relationship provided by the present application.
  • the process may include but is not limited to the following steps:
  • Step 801 the second node sends symbol indication information to the first node.
  • the first node receives the symbol indication information from the second node.
  • the symbol indication information is used to indicate that the number of protection symbols sent by the second node is the number of protection symbols in the SUL scenario.
  • the symbol indication information is indicated by a bit in the MAC CE. For example, when the bit is "1", it represents the number of protection symbols in the SUL scenario; when the bit is "0", it represents the number of protection symbols in the NUL scenario. For example, as shown in FIG. 8a, a certain reserved bit in the first 8-bit bit is used to represent symbol indication information.
  • the symbol indication information is indicated by a newly defined logical channel identifier.
  • the newly defined logical channel identifier A is used to indicate that the number of protection symbols is the number of protection symbols in the SUL scenario.
  • the number of protection symbols in the NUL scenario can be indicated by the existing logical channel identifier.
  • the logical channel identifier is 50, which is used to indicate the number of protection symbols in the NUL uplink scenario; the logical channel identifier is 45, which is used to indicate the NUL downlink scenario.
  • the number of protection symbols below.
  • the specific value of A is not limited in this application, but does not overlap with the existing logical channel identifier.
  • the symbol indication information is indicated by uplink transmission resources of the SUL.
  • the number of protection symbols sent by the IAB MT through the SUL uplink transmission resource is the number of protection symbols in the SUL scenario.
  • the protocol may stipulate: when the IAB node has the transmission resources of the SUL carrier and the NUL carrier at the same time, the number of protection symbols sent through the uplink transmission resources of NUL is the number of protection symbols in the NUL scenario; the number of protection symbols sent through the uplink transmission resources of SUL The number of protection symbols is the number of protection symbols in the SUL scenario.
  • the number of protection symbols in the SUL scenario and the number of protection symbols in the NUL scenario can be distinguished through the symbol indication information.
  • FIG. 6 , FIG. 7 , and FIG. 8 may be performed independently or in combination, for example, FIG. 6 and FIG. 7 may be performed in combination, and FIG. 6 and FIG. 8 may be performed in combination.
  • the above method introduces how to report the multiplexing relationship related to the SUL carrier when the SUL carrier is applied to the IAB system, how to configure the SUL resource information, and how to distinguish the number of guard symbols in the SUL scenario and the NUL scenario. If the IAB system supports a supplementary downlink (supplementary downlink, SDL) carrier, or the IAB system supports other component carriers (component carriers) that extend the transmission bandwidth, the SUL carrier in the above method can be replaced with an SDL carrier or a component carrier.
  • supplementary downlink supplementary downlink, SDL
  • component carriers component carriers
  • the embodiments of the present application further provide corresponding apparatuses, including corresponding modules for executing the foregoing embodiments.
  • the modules may be software, hardware, or a combination of software and hardware.
  • FIG. 9 is a schematic structural diagram of a communication device.
  • the communication device 900 may be a second node, a first node, a chip, a chip system, or a processor that supports the second node to implement the above method, or a chip that supports the first node to implement the above method, Chip system, or processor, etc.
  • the apparatus can be used to implement the methods described in the foregoing method embodiments, and for details, reference may be made to the descriptions in the foregoing method embodiments.
  • the communication apparatus 900 may include one or more processors 901, and the processors 901 may also be referred to as processing units or processing modules, etc., and may implement certain control functions.
  • the processor 901 may be a general-purpose processor or a special-purpose processor, or the like.
  • the general-purpose processor may be, for example, a central processing unit
  • the special-purpose processor may be, for example, a baseband processor.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processing unit can be used to control communication devices (such as base stations, baseband chips, MT, DU, or CU, etc.), execute software programs, and process software programs. data.
  • the processor 901 may also store instructions 903, and the instructions 903 may be executed by the processor 901, so that the communication apparatus 900 executes the methods described in the above method embodiments.
  • the processor 901 may include a transceiver unit for implementing receiving and transmitting functions.
  • the transceiver unit may be a transceiver circuit, or an interface.
  • Transceiver circuits, interfaces or interface circuits used to implement receiving and transmitting functions may be separate or integrated.
  • the above-mentioned transceiver circuit or interface can be used for reading and writing instructions, or the above-mentioned transceiver circuit or interface can be used for signal transmission.
  • the communication apparatus 900 may include one or more memories 902 on which instructions 904 may be stored, and the instructions 904 may be executed on the processor 901, so that the communication apparatus 900 executes the methods described in the above method embodiments.
  • data may also be stored in the memory 902 .
  • instructions and/or data may also be stored in the processor 901 .
  • the processor 901 and the memory 902 can be provided separately or integrated together. For example, the corresponding relationship described in the above method embodiments may be stored in the memory 902 or in the processor 901 .
  • the communication device 900 may further include a transceiver 905 and/or an antenna 906 .
  • the transceiver 905 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, a transceiver device, or a transceiver module, etc., and is used to implement a transceiver function.
  • the communication device 900 when the communication device 900 is the second node, it may include various functional modules for executing steps 601, 603, and 604 in FIG. 6; steps 700 to 604 in FIG. 7 702; Step 801 in FIG. 8 .
  • the communication apparatus 900 when the communication apparatus 900 is the first node, it may include various functional modules for executing steps 601 to 604 in FIG. 6 ; steps 700 to 702 in FIG. 7 ; Step 801 in 8.
  • ICs may include analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application specific integrated circuits (ASICs), and the like.
  • RFICs radio frequency integrated circuits
  • ASICs application specific integrated circuits
  • PCB printed circuit board
  • the communication apparatus described in the above embodiments may be network equipment or terminal equipment, but the scope of the apparatus described in this application is not limited thereto, and the structure of the communication apparatus may not be limited by FIG. 9 .
  • the communication means may be:
  • Receivers terminals, cellular phones, wireless equipment, handsets, mobile units, in-vehicle equipment, network equipment, cloud equipment, artificial intelligence equipment, machine equipment, home equipment, medical equipment, industrial equipment, etc.
  • the apparatus may be the second node or a component of the second node (eg, an integrated circuit, a chip, etc.).
  • the apparatus may be the first node, or may be a component of the first node (eg, an integrated circuit, a chip, etc.).
  • the apparatus may also be other communication modules, which are used to implement the methods in the method embodiments of the present application.
  • the communication apparatus 1000 may include: a processing unit 1001 (or referred to as a processing module).
  • a communication unit 1002 (or referred to as a transceiver unit, a receiving unit and/or a sending unit) may also be included.
  • a storage unit (or referred to as a storage module) may also be included.
  • one or more units as in FIG. 10 may be implemented by one or more processors, or by one or more processors and memory; or by one or more processors and a transceiver; or implemented by one or more processors, a memory, and a transceiver, which is not limited in this embodiment of the present application.
  • the processor, memory, and transceiver can be set independently or integrated.
  • each module in the communication apparatus 1000 in the embodiment of the present application may be used to execute the method described in FIG. 6 , FIG. 7 , or FIG. 8 in the embodiment of the present application, or may be used to execute the above two or more The methods described in the figure are combined with each other.
  • the IAB node includes DU and MT.
  • the MT is the UE function module of the IAB node, that is, the IAB node communicates with the upper node through the MT;
  • the DU is the base station function module of the IAB node, that is, the IAB node communicates with the lower node or UE through the DU.
  • Both the MT and DU of the IAB node have complete transceiver modules, and there is an interface between them.
  • the MT and the DU are logical modules, and in practice, the two may share some sub-modules, such as a transceiver antenna, a baseband processing module, and the like.
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other possible Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • a processing unit for performing the techniques at a communication device may be implemented in one or more general purpose processors, DSPs, digital signal processing devices, ASICs, A programmable logic device, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of the above.
  • a general-purpose processor may be a microprocessor, or alternatively, the general-purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration. accomplish.
  • the memory in this embodiment 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 may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct ram bus RAM direct ram bus RAM
  • the corresponding relationships shown in each table in this application may be configured or predefined.
  • the values of the information in each table are only examples, and can be configured with other values, which are not limited in this application.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, for example, splitting, merging, and so on.
  • the names of the parameters shown in the headings in the above tables may also adopt other names that can be understood by the communication device, and the values or representations of the parameters may also be other values or representations that the communication device can understand.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables. Wait.
  • Predefined in this application may be understood as defining, predefining, storing, pre-storing, pre-negotiating, pre-configuring, curing, or pre-firing.
  • the systems, devices and methods described in this application can also be implemented in other ways.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of 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 components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请提供一种复用关系上报方法及通信装置，应用于包括第一节点和第二节点的通信系统，第一节点为第二节点的上级节点或宿主节点，第二节点包括MT和DU。该方法可包括：第二节点向第一节点发送复用关系信息，该复用关系信息用于指示SUL载波相关的复用关系，具体用于指示以下一种或多种：MT对应的第一小区的SUL载波与DU对应的第二小区的NUL载波之间的复用关系；MT对应的第一小区的NUL载波与DU对应的第二小区的SUL载波之间的复用关系；或MT对应的第一小区的SUL载波与DU对应的第二小区的SUL载波之间的复用关系。采用本申请，通过上报SUL载波相关的复用关系，有助于为SUL载波配置资源。

Description

复用关系上报方法及通信装置 技术领域
本申请涉及通信技术领域，具体涉及一种复用关系上报方法及通信装置。
背景技术
通常，一个小区由一个下行载波和一个上行载波组成。但是新空口(new radio，NR)部署高频小区时，由于NR运行频段较高且用户设备(user equipment，UE)的发射功率较低，处于小区边缘区域的UE，可以接收到来自基站的信号，但是基站无法接收到来自UE的信号，即存在上下行覆盖不对称的问题。为了解决该问题，提出补充上行(supplementary uplink，SUL)技术，该技术引入另外一段用于辅助UE进行上行传输的低频频段，以使UE拥有两段频段进行上行传输。这样，支持SUL配置的小区可以包括一个下行载波和两个上行载波，这两个上行载波中的一个上行载波称为SUL载波(carrier)，另一个上行载波称为普通上行(normal uplink，NUL)载波。
为了提高频谱利用率，可以增大基站的部署密度。随着基站部署密度的增大，为了节省基站与核心网之间的光纤部署成本，引入中继节点(relay node，RN)。中继节点基于无线回传链路与核心网建立连接，从而更加节省光纤部署成本。通常，中继节点可与一个或多个上级节点建立无线回传链路，并基于上级节点接入核心网；中继节点可为一个或多个下级节点提供服务。带内中继方案，指的是回传链路与接入链路共享相同频段的中继方案，具有频谱效率高和部署成本低等优点。一体化接入回传(integrated access and backhaul，IAB)是一种带内中继方案，在该带内中继方案中，中继节点可以被称为IAB节点(node)。在IAB系统中，IAB节点的上级节点可以是基站，也可以是另外的IAB节点；IAB节点的下级节点可以是UE，也可以是另外的IAB节点。
在SUL载波应用于IAB系统的场景下，如何实现SUL载波相关的复用关系上报是亟待解决的技术问题。
发明内容
本申请提供一种复用关系上报方法及通信装置，在SUL载波应用于IAB系统的场景下，可以实现SUL载波相关的复用关系上报，有助于为SUL载波配置资源。
第一方面，本申请提供一种复用关系上报方法，该方法应用于第一节点和第二节点的通信系统，第一节点为第二节点的上级节点或宿主节点，第二节点包括移动终端和分布式单元。该方法可以由第二节点执行，或者也可以由配置于第二节点中的芯片执行，本申请对此不作限定。
具体的，该方法包括：第二节点向第一节点发送复用关系信息，该复用关系信息用于指示以下一种或多种：第二节点向第一节点发送复用关系信息；复用关系信息用于指示以下一种或多种复用关系：移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的NUL载波之间的复用关系；移动终端对应的第一小区的NUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系；移动终端对应的第一小区的SUL载波与分布式 单元对应的第二小区的SUL载波之间的复用关系。
可见，在SUL载波应用于IAB系统的场景下，第二节点通过向第一节点上报SUL载波相关的复用关系，以便第一节点可以根据复用关系为SUL载波配置资源，从而提升网络资源利用率。
结合第一方面，在某些可能的实现方式中，第二节点接收来自第一节点的第一配置信息。可选的，第二节点的分布式单元接收第一配置信息。其中，第一配置信息用于配置SUL资源信息，SUL资源信息用于支持第二小区通过SUL载波进行上行接收。其中，SUL资源信息包括一个或多个SUL资源以及SUL资源的资源属性，资源属性为始终可用，指示是否可用，或不可用。
可见，第一节点通过第一配置信息支持第二节点的第二小区通过SUL载波进行上行接收，以提升网络资源利用率。
结合第一方面，在某些可能的实现方式中，第一配置信息携带在小区资源配置信令中，可以实现对SUL资源以及NUL资源的配置，从而节省信令开销。
结合第一方面，在某些可能的实现方式中，一个第二小区可以对应一个或多个SUL资源，一个或多个SUL资源可以对应一个SUL资源配置标识。SUL资源通过SUL资源对应的SUL资源配置标识关联至一个或多个第二小区，不再需要在每个小区的资源配置中增加SUL的具体资源配置，可简化SUL资源的配置，降低开销。
结合第一方面，在某些可能的实现方式中，SUL资源的资源属性为指示是否可用，第二节点接收来自第一节点的SUL资源可用性指示信息，SUL资源可用性指示信息用于指示SUL资源可用或不可用。通过SUL资源可用性指示信息指示SUL资源可用或不可用，以便第二节点合理使用SUL资源。
结合第一方面，在某些可能的实现方式中，RRC信令用于指示SUL资源可用性指示信息在DCI中的位置，第二节点根据该RRC信令可确定SUL资源可用性指示信息在DCI中的位置，从而从DCI中获知SUL资源可用性指示信息。
结合第一方面，在某些可能的实现方式中，RRC信令用于指示SUL资源配置标识在DCI中的位置；第二节点根据RRC信令确定SUL资源配置标识对应的SUL资源可用性指示信息在DCI中的位置，从而从DCI中获知SUL资源配置标识对应的SUL资源可用性指示信息。
结合第一方面，在某些可能的实现方式中，RRC信令用于指示某个第二小区的资源可用性指示信息在DCI中的位置，该第二小区的小区ID后的标识用于指示资源可用性指示信息是否适用于SUL资源，从而实现对SUL资源是否可用的指示。
结合第一方面，在某些可能的实现方式中，上述复用关系信息包括SUL配置信息的配置索引、SUL带宽编号或SUL标识中的一种或多种。
可见，通过SUL配置信息的配置索引、SUL带宽编号或SUL标识中的一种或多种确定复用关系，可节省信令开销。
结合第一方面，在某些可能的实现方式中，第二节点接收第二配置信息，根据第二配置信息，确定上述复用关系信息。其中，第二配置信息可以来自核心网设备或第一节点。
在一种方式中，第二配置信息包括SUL配置信息。在另一种方式中，第二配置信息包 括SUL配置信息和SUL配置信息的配置索引。其中，SUL配置信息包括SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL绝对无线频道编号、SUL带宽编号、SUL载波列表中的一种或多种。
可见，通过第二配置信息，第二节点可获知为其配置的SUL频段及相关信息，可根据第二配置信息确定复用关系。
结合第一方面，在某些可能的实现方式中，第二节点向第一节点发送能力信息。其中，能力信息包括SUL信息，SUL信息包括SUL配置信息的配置索引、SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL带宽编号、SUL绝对无线频道编号、SUL载波列表、SUL子载波间隔中的一种或多种。
可见，第二节点通过上报能力信息，将其支持的SUL频段及相关信息告知第一节点，以便第一节点配置SUL资源。
结合第一方面，在某些可能的实现方式中，第二节点向第一节点发送符号指示信息，符号指示信息用于指示第二节点发送的保护符号数为SUL场景下的保护符号数，以区分上报的保护符号数为SUL场景下的还是NUL场景下的。
结合第一方面，在某些可能的实现方式中，上述符号指示信息通过新定义的逻辑信道标识进行指示，该新定义的逻辑信道标识不与现有的逻辑信道标识重复。
结合第一方面，在某些可能的实现方式中，上述符号指示信息通过SUL的上行传输资源进行指示。可以理解的是，通过NUL的上行传输资源发送的保护符号数即为NUL场景下的保护符号数；通过SUL的上行传输资源发送的保护符号数即为SUL场景下的保护符号数。
第二方面，本申请提供一种复用关系上报方法，该方法应用于第一节点和第二节点的通信系统，第一节点为第二节点的上级节点或宿主节点，第二节点包括移动终端和分布式单元。该方法可以由第一节点执行，或者也可以由配置于第一节点中的芯片执行，本申请对此不作限定。
第一节点接收来自第二节点的分布式单元的复用关系信息；根据该复用关系信息，确定第一配置信息；该复用关系信息用于指示以下一种或多种复用关系：移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的NUL载波之间的复用关系；移动终端对应的第一小区的NUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系；移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系。
可见，在SUL载波应用于IAB系统的场景下，第二节点通过向第一节点上报SUL载波相关的复用关系，从而第一节点可以根据复用关系为SUL载波配置资源，从而提升网络资源利用率。
结合第二方面，在某些可能的实现方式中，第一节点向第二节点发送第一配置信息。可选的，第一节点向第二节点的分布式单元发送第一配置信息。其中，第一配置信息用于配置SUL资源信息，SUL资源信息用于支持第二小区通过SUL载波进行上行接收。其中，SUL资源信息包括一个或多个SUL资源以及SUL资源的资源属性，资源属性为始终可用，指示是否可用，或不可用。
可见，第一节点通过第一配置信息支持第二节点的第二小区通过SUL载波进行上行接收，以提升网络资源利用率。
结合第二方面，在某些可能的实现方式中，一个第二小区可以对应一个或多个SUL资源，一个或多个SUL资源可以对应一个SUL资源配置标识。SUL资源通过SUL资源对应的SUL资源配置标识关联至一个或多个第二小区，不再需要在每个小区的资源配置中增加SUL的具体资源配置，可简化SUL资源的配置，降低开销。
结合第二方面，在某些可能的实现方式中，第一节点向第二节点发送SUL资源可用性指示信息。SUL资源可用性指示信息用于指示SUL资源可用或不可用。通过SUL资源可用性指示信息指示SUL资源可用或不可用，以便第二节点合理使用SUL资源。
结合第二方面，在某些可能的实现方式中，上述复用关系信息包括SUL配置信息的配置索引、SUL带宽编号或SUL标识中的一种或多种。
可见，通过SUL配置信息的配置索引、SUL带宽编号或SUL标识中的一种或多种确定复用关系，可节省信令开销。
结合第二方面，在某些可能的实现方式中，第一节点向第二节点发送第二配置信息。可选的，第一节点向第二节点的移动终端发送第二配置信息。
在一种方式中，第二配置信息包括SUL配置信息。在另一种方式中，第二配置信息包括SUL配置信息和SUL配置信息的配置索引。其中，SUL配置信息包括SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL绝对无线频道编号、SUL带宽编号、SUL载波列表中的一种或多种。
可见，通过第二配置信息，第二节点可获知为其配置的SUL频段及相关信息，可根据第二配置信息确定复用关系。
结合第二方面，在某些可能的实现方式中，第一节点接收来自第二节点的能力信息，能力信息包括SUL信息，SUL信息包括SUL配置信息的配置索引、SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL带宽编号、SUL绝对无线频道编号、SUL载波列表、SUL子载波间隔中的一种或多种。
可见，第一节点获取第二节点的能力信息，可以根据能力信息为第二节点配置SUL资源。
结合第二方面，在某些可能的实现方式中，第一节点接收来自第二节点的符号指示信息，符号指示信息用于指示第二节点发送的第一保护符号数为SUL场景下的保护符号数，以区分上报的保护符号数为SUL场景下的还是NUL场景下的。
结合第二方面，在某些可能的实现方式中，上述符号指示信息通过新定义的逻辑信道标识进行指示。
结合第二方面，在某些可能的实现方式中，上述符号指示信息通过SUL的上行传输资源进行指示。
第三方面，本申请还提供一种通信装置。该通信装置具有实现上述第一方面所述的第二节点的部分或全部功能。比如，装置的功能可具备本申请中第二节点的部分或全部实施例中的功能，也可以具备单独实施本申请中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功 能相对应的单元或模块。
在一种可能的设计中，该通信装置的结构中可包括处理单元和通信单元，所述处理单元被配置为支持通信装置执行上述方法中相应的功能。所述通信单元用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储单元，所述存储单元用于与处理单元和通信单元耦合，其保存通信装置必要的程序指令和数据。
一种实施方式中，所述通信装置包括：
通信单元，用于向第一节点发送复用关系信息，该复用关系信息用于指示以下一种或多种：第二节点向第一节点发送复用关系信息；复用关系信息用于指示以下一种或多种复用关系：移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的NUL载波之间的复用关系；移动终端对应的第一小区的NUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系；移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系。
该实施方式的相关内容可参见上述第一方面的相关内容，此处不再详述。
另一种实施方式中，所述通信装置可包括：
处理器，用于通过收发器向第一节点发送复用关系信息，该复用关系信息用于指示以下一种或多种：第二节点向第一节点发送复用关系信息；复用关系信息用于指示以下一种或多种复用关系：移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的NUL载波之间的复用关系；移动终端对应的第一小区的NUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系；移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系。
该实施方式的相关内容可参见上述第一方面的相关内容，此处不再详述。
第四方面，本申请还提供一种通信装置。该通信装置具有实现上述第一方面所述的第一节点的部分或全部功能。比如，装置的功能可具备本申请中第一节点的部分或全部实施例中的功能，也可以具备单独实施本申请中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的设计中，该通信装置的结构中可包括处理单元和通信单元，所述处理单元被配置为支持通信装置执行上述方法中相应的功能。所述通信单元用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储单元，所述存储单元用于与处理单元和通信单元耦合，其保存通信装置必要的程序指令和数据。
一种实施方式中，所述通信装置包括：
通信单元，用于接收来自第二节点的复用关系信息，该复用关系信息用于指示以下一种或多种复用关系：移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的NUL载波之间的复用关系；移动终端对应的第一小区的NUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系；移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系；
处理单元，用于根据该复用关系信息，确定第一配置信息。
该实施方式的相关内容可参见上述第二方面的相关内容，此处不再详述。
另一种实施方式中，所述通信装置可包括：
处理器，用于通过收发器接收来自第二节点的复用关系信息；根据该复用关系信息，确定第一配置信息；该复用关系信息用于指示以下一种或多种复用关系：移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的NUL载波之间的复用关系；移动终端对应的第一小区的NUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系；移动终端对应的第一小区的SUL载波与分布式单元对应的第二小区的SUL载波之间的复用关系。
该实施方式的相关内容可参见上述第二方面的相关内容，此处不再详述。
在实现过程中，处理器可用于进行，例如但不限于，基带相关处理，收发器可用于进行，例如但不限于，射频收发。上述器件可以分别设置在彼此独立的芯片上，也可以至少部分的或者全部的设置在同一块芯片上。例如，处理器可以进一步划分为模拟基带处理器和数字基带处理器。其中，模拟基带处理器可以与收发器集成在同一块芯片上，数字基带处理器可以设置在独立的芯片上。随着集成电路技术的不断发展，可以在同一块芯片上集成的器件越来越多。例如，数字基带处理器可以与多种应用处理器(例如但不限于图形处理器，多媒体处理器等)集成在同一块芯片之上。这样的芯片可以称为系统芯片(System on Chip)。将各个器件独立设置在不同的芯片上，还是整合设置在一个或者多个芯片上，往往取决于产品设计的需要。本申请实施例对上述器件的实现形式不做限定。
第五方面，本申请还提供一种处理器，用于执行上述各种方法。在执行这些方法的过程中，上述方法中有关发送上述信息和接收上述信息的过程，可以理解为由处理器输出上述信息的过程，以及处理器接收输入的上述信息的过程。在输出上述信息时，处理器将该上述信息输出给收发器，以便由收发器进行发射。该上述信息在由处理器输出之后，还可能需要进行其他的处理，然后才到达收发器。类似的，处理器接收输入的上述信息时，收发器接收该上述信息，并将其输入处理器。更进一步的，在收发器收到该上述信息之后，该上述信息可能需要进行其他的处理，然后才输入处理器。
基于上述原理，举例来说，前述方法中提及的发送复用关系信息可以理解为处理器输出复用关系信息。
对于处理器所涉及的发射、发送和接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则均可以更加一般性的理解为处理器输出和接收、输入等操作，而不是直接由射频电路和天线所进行的发射、发送和接收操作。
在实现过程中，上述处理器可以是专门用于执行这些方法的处理器，也可以是执行存储器中的计算机指令来执行这些方法的处理器，例如通用处理器。上述存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(Read Only Memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第六方面，本申请提供了一种计算机可读存储介质，用于储存计算机软件指令，当所述指令被计算机执行时，实现上述第一方面或第二方面所述的方法。
第七方面，本申请还提供了一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第二方面所述的方法。
第八方面，本申请提供了一种芯片系统，该芯片系统包括至少一个处理器和通信接口，所述至少一个处理器用于执行计算机程序，所述通信接口用于输入和/或输出信息，使得第二节点实现第一方面所涉及的功能，或第一节点实现第二方面所涉及的功能。
在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存第二节点或第一节点必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
附图说明
图1为一种IAB系统的示例图；
图2为DCI进行指示的一种示例图；
图3为MAC CE的一种格式示例图；
图4为SUL链路和NUL链路的示例图；
图5为应用于本申请的网络架构的示意图；
图6为本申请提供的一种复用关系上报方法的流程示意图；
图6a为本申请提供的一种SUL资源可用性指示信息的示例图；
图6b为本申请提供的另一种SUL资源可用性指示信息的示例图；
图6c为本申请提供的又一种SUL资源可用性指示信息的示例图；
图7为本申请提供的配置信息发送的流程示意图；
图8为本申请提供的符合指示信息发送的流程示意图；
图8a为本申请提供的一种符合指示信息的示例图；
图9为本申请提供的通信装置的结构示意图；
图10为本申请提供的通信装置的另一种结构示意图；
图11为本申请提供的IAB节点的结构示意图。
具体实施方式
为了更好地理解本申请提供的技术方案，首先对本申请涉及的技术术语进行介绍。
1、IAB系统
在带内中继方案中，通常，中继节点可以与一个或多个上级节点建立无线回传链路，并通过上级节点接入核心网。上级节点可通过多种信令对中继节点进行一定的控制(例如，数据调度、定时调制、功率控制等)。中继节点可以为一个或多个下级节点提供服务。新空口(new radio，NR)系统中的带内中继方案可以被称为IAB。在IAB系统中，中继节点可以被称为IAB节点(node)，IAB节点的上级节点可以是基站，也可以是另外的IAB节点；IAB节点的下级节点可以是UE，也可以是另外的IAB节点。
在本申请中，上级节点，指的是为无线回传链路提供资源的节点，例如基站可以是IAB节点的上级节点；下级节点，指的是使用无线回传链路资源向网络进行数据传输的节点，和/或接收来自网络的数据的节点，例如UE可以是IAB节点的下级节点。网络，可以是核心网或其它接入网之上的网络，例如因特网或专网等。上级节点也可以描述为父节点或上游节点等，下级节点也可以描述为子节点或下游节点等。
可参见图1所示的IAB系统的示例图。IAB系统可以包括至少一个基站100，以及一 个或多个IAB节点110。基站100可以为一个或多个UE101提供服务，也可以为一个或多个IAB节点110提供服务。IAB节点110可以为一个或多个UE111提供服务。通常，基站100可以被称为宿主基站(donor next generation node B，DgNB)，IAB节点110通过无线回传链路113连接到基站100。宿主基站也可以描述为宿主节点，donor节点，IAB donor，或IAB宿主节点等，在本申请中以描述为IAB donor为例。
IAB系统还可以包括多个其他IAB节点，例如IAB节点120和IAB节点130。IAB节点120是通过无线回传链路123连接到IAB节点110以接入到网络的。IAB节点130是通过无线回传链路133连接到IAB节点110以接入到网络的。IAB节点120可为一个或多个UE121提供服务，IAB节点130为一个或多个UE131服务。图1中，IAB节点110、IAB节点120和IAB节130都可以通过无线回传链路接入到网络。在本申请中，无线回传链路都是从IAB节点的角度来看的，比如无线回传链路113是IAB节点110的回传链路，无线回传链路123是IAB节点120的回传链路，无线回传链路133是IAB节点130的回传链路。
IAB节点可以直接接入到网络，例如IAB节点110通过无线回传链路113接入到网络；也可以经过多级中继节点接入网络，例如IAB节点120先通过无线回传链路123连接IAB节点110，再通过IAB节点110的无线回传链路113接入到网络。应理解，本申请中用IAB节点出于描述的需要，并不表示本申请的方案仅用于NR的场景，IAB节点可以泛指任何具有中继功能的节点或设备，本申请中的IAB节点和中继节点的使用应理解具有相同的含义。
图1涉及两种传输链路，一种是无线接入链路，一种是无线回传链路。
无线接入链路，也可以描述为接入链路(access link)，指的是UE与IAB节点或IAB donor之间的链路。或者，无线接入链路包括某个节点和它的下级节点进行通信时所使用的无线链路。无线接入链路包括上行接入链路和下行接入链路。上行接入链路也被称为接入链路的上行传输，下行接入链路也被称为接入链路的下行传输。
无线回传链路，也可以描述为回传链路(backhaul，BH)，指的是IAB节点与IAB子节点之间或者IAB节点与IAB父节点之间的链路。例如，对节点110而言，其IAB子节点为IAB节点120，其IAB父节点为基站100。无线回传链路包括与IAB子节点或IAB父节点之间的下行传输的链路，以及与IAB子节点或者IAB父节点之间的上行传输的链路。IAB节点向其IAB父节点进行数据传输，或者接收其IAB子节点的上行传输被称为回传链路的上行传输。IAB节点接收其IAB父节点的数据传输，或者向其IAB子节点进行的数据传输被称为回传链路的下行传输。为了对UE和IAB节点进行区分，IAB节点与其IAB父节点之间的回传链路被又称为上级回传链路(parent BH link)，而IAB节点与其IAB子节点之间的回传链路被称为下级回传链路(child BH link)。
通常，下级节点可以被看作是上级节点的一个UE。应理解，图1所示的IAB系统中，一个IAB节点连接一个上级节点用于举例。实际应用中，为了提高无线回传链路的可靠性，一个IAB节点，如120，可以连接多个上级节点，即多个上级节点可以同时为一个IAB节点提供服务。例如图1中，IAB节点130还可以通过无线回传链路a’a134连接到IAB节点120，即，IAB节点110和IAB节点120都可以视为IAB节点130的上级节点。
在图1中，无线链路102,112,122,132,113,123,133,a’a134可以是双向链路，包括上 行和下行传输链路，特别地，无线回传链路113,123,133,a’a 134可以用于上级节点为下级节点提供服务，如上级节点(例如基站100)为下级节点(例如IAB节点110)提供无线回传服务。应理解，回传链路的上行和下行可以是分离的，即，上行链路和下行链路不是通过同一个节点进行传输的。下行传输是指上级节点(例如基站100)向下级节点(例如IAB节点110)传输信息或数据；上行传输是指下级节点(例如IAB节点110)向上级节点(例如基站100)传输信息或数据。节点不限于是基站、IAB节点以及UE，例如，在设备到设备(device-to-device，D2D)场景下，UE可以充当中继节点为其他UE服务。无线回传链路在某些场景下又可以是接入链路，如无线回传链路123对节点110而言也可以被视作接入链路，回传链路113也是节点100的接入链路。应理解，上述上级节点可以是基站，也可以是中继节点，下级节点可以是中继节点，也可以是具有中继功能的UE，如D2D场景下，下级节点也可以是UE。
在一种实现方式中，IAB节点可包括移动终端(mobile termination，MT)和分布式单元(distributed unit，DU)。其中，MT用于IAB节点实现与上级节点之间的通信，DU用于实现IAB节点与下级节点之间的通信。MT与上级节点进行通信的链路可以被称为上级回传链路，DU与下级节点进行通信的链路可以被称为下级回传链路。在一些情况下，下级回传链路也可以被称为接入链路，例如，DU的下级节点是UE的情况。
在一种实现方式中，IAB donor可包括集中式单元(centralized unit，CU)和DU。其中，CU主要负责无线资源控制与配置，跨小区移动性管理，承载管理等，DU主用负责调度，物理信号生成与发送。以IAB donor CU向IAB节点DU发送配置信息为例，IAB donor CU生成的F1接口应用协议(F1-application protocol，F1-AP)数据包被封装成网络互连协议(Internet protocol，IP)包，该IP包在空口经过多跳节点传递到达IAB节点后，IAB节点MT适配层处理后，将该IP包转发给IAB节点DU进行处理，IAB节点DU解析该IP包可获得F1-AP数据包。
(1)复用模式和复用能力上报
对IAB节点而言，当MT和DU在不同的时域资源上工作时，或者接入与回传在不同的时域资源上进行时，复用模式为时分复用(time division multiplexing，TDM)模式；当MT和DU在相同的时域资源上工作时，或者接入与回传在相同的时域资源上进行时，复用模式为空分复用(spatial division multiplexing，SDM)模式或全双工(full duplex，FD)模式。具体的，对于同一时间，若MT和DU上进行接收或发送，或者回传与接入进行接收或发送，那么复用模式为空分复用模式；若MT和DU上既进行接收又进行发送，或者回传与接入既进行接收又进行发送，那么复用模式为全双工模式。
IAB节点的实现形式以及硬件能力的不同，使得不同IAB节点可能支持不同的复用模式，因此IAB节点向其上级节点上报复用能力。
在一种实现方式中，通过信息元素(information element，IE)上报DU对应的小区与MT对应的服务小区之间的复用能力。该IE可参见下表1所示。
Figure PCTCN2020123438-appb-000001
Figure PCTCN2020123438-appb-000002
表1
表1中，“IAB-MT Cell Item”用于标识MT对应的一个服务小区，“NR Cell Identity”用于标识DU对应的一个小区；“Presence”为M，表示携带参数项，即携带支持或不支持。IAB节点DU向其上级节点CU上报，“NR Cell Identity”所标识的小区与“IAB-MT Cell Item”所标识的服务小区能否同时进行发送或接收。例如“DU_RX/MT_RX”表示DU对应的小区与MT对应的服务小区能否同时接收，参数为支持时表示支持同时接收，参数为不支持时表示不支持同时接收。
(2)IAB节点的资源以及资源配置
在NR系统中，IAB节点配置有MT资源和DU资源。
MT资源，可被配置为三种资源类型，分别为下行(downlink，D)，上行(uplink，U)，灵活(flexible，F)。IAB节点的宿主基站可通过信令为IAB节点配置MT资源是哪种类型。IAB节点的MT资源具有三种资源类型，
DU资源，可被配置为四种资源类型，分别为上行，下行，灵活，不可用(not available，NA)。不可用也可以描述为禁用或不能使用等。进一步的，DU-上行资源和DU-灵活资源还可分为硬(hard)资源和软(soft)资源。其中，hard资源表示DU始终可用的资源；soft资源，DU是否可用，依赖于上级节点的指示。IAB节点的DU资源具有七种资源类型。
在一种实现方式中，IAB donor CU通过F1-AP信令向IAB节点DU发送资源配置信息，该资源配置信息用于配置DU资源的资源属性以及DU的传输方向。该资源配置信息可以是“GNB-DU RESOURCE CONFIGURATION”包括的“gNB-DU Cell Resource Configuration”，“gNB-DU Cell Resource Configuration”中的DUF Slot相关配置用于配置DU的传输方向，“gNB-DU Cell Resource Configuration”中的HSNA Slot相关配置用于配置DU 资源的资源属性(hard，soft，not available)。
进一步的，在DU资源的资源属性为soft的情况下，IAB节点的上级节点通过下行控制信息(downlink control indication，DCI)对可用性进行指示。DU对应的小区可能有多个，DCI可动态指示多个小区中哪些小区的哪些资源的可用状态。
示例性的，可参见图2所示的DCI。图2中，箭头所指的位置表示DU对应的小区p的可用性指示(availability indication，AI)在DCI 2_5信令中的位置，DCI 2_5信令中从该位置起的深灰色区域表示DU对应的小区p的AI索引(index)字段(field)值(value)。DU对应的小区p在DCI 2_5中的位置可由无线资源控制(radio resource control，RRC)信令进行配置。其中，DCI 2_5信令的最大长度为128比特，小区p可以是DU对应的小区中的任意一个小区。AI索引字段值可通过3个比特进行指示，DCI 2_5中每3个比特指示一个时隙的可用性，AI索引字段值的可能取值以及其含义可参见下表2所示。
AI索引字段值 含义
0 没有soft符号被指示可用
1 仅DL soft符号被指示可用
2 仅UL soft符号被指示可用
3 仅DL和UL soft符号被指示可用
4 仅灵活的soft符号被指示可用
5 仅DL和灵活的soft符号被指示可用
6 仅UL和灵活的soft符号被指示可用
7 DL，UL和灵活的soft符号被指示可用
表2
(3)保护符号数上报
IAB节点实现方式的多样性，MT与DU切换场景的多样性，使得MT与DU的收发转换可能需要一定时间，因此IAB节点MT向其上级节点上报保护符号数。示例性的，可参见表3所示。
Figure PCTCN2020123438-appb-000003
表3
表3中的切换场景涉及MT到DU，DU到MT，上行到下行，下行到上行，上行到上 行，下行到下行，多种情况。每种情况对应的保护符号数通过媒体接入控制(medium access control，MAC)控制元素(control element，CE)进行指示。在一种实现方式中，采用4个8位信息组成的MAC CE进行指示，这4个8位信息的格式可参见图3所示，图3中，R表示预留比特位，SCS表示子载波间隔。
2、补充上行(SUL)载波
支持SUL配置的小区可以包括一个下行载波和两个上行载波，这两个上行载波中的一个上行载波称为SUL载波，另一个上行载波称为NUL载波，NUL载波即未配置SUL的小区所包括的上行载波。空闲态的UE，可以根据下行测量结果中的参考信号接收功率(reference signal receiving power，RSRP)确定通过哪种上行载波进行接入，当RSRP高于阈值时，UE选择NUL载波进行上行接入；当RSRP小于该阈值时，UE选择SUL载波进行上行接入。
对于配置SUL载波的UE，中近点使用NUL链路，远点使用SUL链路，可参见图4所示。同一时刻，选择其中一条上行链接进行上行接入，不能同时调度两条链路。
对于一个UE而言，如果一个服务小区支持SUL传输，则基站可以通过服务小区配置信息(servingCell config)为UE配置SUL载波。实际传输中，基站可以通过DCI直接调度UE在SUL载波上传输物理上行共享信道(physical uplink shared channel，PUSCH)。协议在配置上，NUL载波与SUL载波属于同一服务小区，该服务小区的配置信息中包括该服务小区的物理小区标识(physical cell identiy，PCI)，下行配置信息，上行配置信息以及SUL配置信息，可参见如下所示。
Figure PCTCN2020123438-appb-000004
上述介绍了IAB系统和SUL载波，在SUL载波应用于IAB系统的场景下，如何实现SUL载波相关的复用关系上报是亟待解决的技术问题。
鉴于此，本申请提供一种复用关系上报方法及通信装置，在SUL载波应用于IAB系统的场景下，可实现SUL载波相关的复用关系的上报，有助于为SUL载波配置资源。
下面将结合本申请中的附图，对本申请中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下一项(个)或多项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的一项或多项，可以表示：a，b，c，a和b，a和c，b和c，或a和b和c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清 楚描述本申请的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能基本相同或相似的技术特征进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请描述的技术可用于各种通信系统，例如第四代(4th generation，4G)通信系统，4.5G通信系统，5G通信系统，多种通信系统融合的系统，或者未来演进的通信系统。例如长期演进(long term evolution，LTE)系统，新空口(new radio,NR)系统，无线保真(wireless-fidelity，WiFi)系统，以及第三代合作伙伴计划(3rd generation partnership project，3GPP)相关的通信系统等，以及其他此类通信系统。
本申请涉及的UE(也可称为终端)可以是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。UE包括具有无线通信功能的手持式设备、车载设备、穿戴式设备或计算设备。示例性地，UE可以是手机(mobile phone)、平板电脑或带无线收发功能的电脑。终端设备还可以是虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、智能汽车(smart vehicle)终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、等等。
作为示例而非限定，在本申请中，UE可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请中，UE可以是物联网(internet of things，IoT)系统中的终端，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。本申请中的终端可以是机器类型通信(machine type communication，MTC)中的终端。本申请的终端可以是作为一个或多个部件或者单元而内置于车辆的车载模块、车载模组、车载部件、车载芯片或者车载单元，车辆通过内置的所述车载模块、车载模组、车载部件、车载芯片或者车载单元可以实施本申请的方法。因此，本申请可以应用于车联网，例如车辆外联(vehicle to everything，V2X)、车间通信长期演进技术(long term evolution vehicle，LTE-V)、车到车(vehicle to vehicle，V2V)等。
本申请涉及的基站(base station，BS)，可以是一种部署在无线接入网络中能够和终端设备进行无线通信的设备。其中，基站可能有多种形式，比如宏基站、微基站、中继站和接入点等。示例性地，本申请涉及到的基站可以是5G中的基站或长期演进(long term evolution，LTE)中的基站，其中，5G中的基站还可以称为发送接收点(transmission reception point，TRP)或下一代基站节点(next generation Node B，gNB)。应用在本申请中，基站可以包括分布式单元(distribute unit，DU)和集中式单元(centralized unit，CU)。
请参见图5，图5为应用于本申请的网络架构的示意图。该网络架构包括第一节点501和第二节点502，第一节点可以是IAB donor，第二节点可以是IAB node，IAB node包括MT和DU。第一节点501为第二节点502#1的上级节点，或称为宿主节点；第二节点502#1可以是第二节点502#2的上级节点。可选的，该网络架构还包括UE503，UE503#1可以接入第一节点501，UE503#2可以接入第二节点502#1。需要说明的是，图5所示的节点的数量和形态仅用于举例，并不构成对本申请的限定。
在本申请中，第二节点502#1向第一节点501发送第二节点502#1的复用关系信息，复用关系信息用于指示以下一种或多种复用关系：(1)第二节点502#1的MT对应的第一小区的SUL载波，与第二节点502#1的DU对应的第二小区的NUL载波之间的复用关系；(2)MT对应的第一小区的NUL载波，与DU对应的第二小区的SUL载波之间的复用关系；(3)MT对应的第一小区的SUL载波，与DU对应的第二小区的SUL载波之间的复用关系。可选的，第二节点502#2通过第二节点502#1向第一节点501发送第二节点502#2的复用关系信息。第二节点上报SUL载波相关的复用关系，有助于IAB donor为SUL载波配置资源，从而提升网络频谱效率。
在一种实现方式中，第一节点501根据第二节点上报的复用关系信息，确定针对第二节点的SUL资源信息，并向第二节点发送SUL资源信息，SUL资源信息用于支持DU对应的第二小区通过SUL载波进行上行接收，从而实现对SUL载波的资源配置。进一步的，第一节点501还向第二节点发送SUL资源可用性指示信息，用于指示资源属性为soft的SUL资源可用或不可用，从而实现对SUL资源的可用性指示。
在一种实现方式中，第二节点502#1向第一节点发送符号指示信息，用于指示第二节点502#1发送的保护符号数为SUL场景下的保护符号数，以便区分SUL场景下的保护符号数上报与NUL场景下的保护符号数上报。
本申请描述的网络架构以及业务场景是为了更加清楚的说明本申请的技术方案，并不构成对于本申请提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
下面将结合附图对本申请提供的复用关系上报方法进行介绍。该复用关系上报方法应用于包括第一节点和第二节点的通信系统，第一节点为第二节点的上级节点或宿主节点，第二节点包括MT和DU。该通信系统不限于IAB系统，以IAB系统为例进行介绍。需要说明的是，节点之间交互的信息或数据的名称用于举例，并不构成对本申请的限定。
请参见图6，为本申请提供的一种复用关系上报方法的流程示意图，该流程可以包括但不限于如下步骤：
步骤601，第二节点向第一节点发送复用关系信息。相应的，第一节点接收来自第二节点的复用关系信息。
可选的，IAB node向IAB donor发送复用关系信息；或IAB node向其上级节点IAB node发送复用关系信息，该上级节点再向IAB donor发送该复用关系信息。在一种实现方式中，IAB DU向第一节点发送复用关系信息。
其中，复用关系信息用于指示MT对应的第一小区的SUL载波或NUL载波，与DU对应的第二小区的SUL载波或NUL载波之间的复用关系。具体的，复用关系信息用于指 示以下一种或多种复用关系：
(1)MT对应的第一小区的SUL载波与DU对应的第二小区的NUL载波之间的复用关系；
(2)MT对应的第一小区的NUL载波与DU对应的第二小区的SUL载波之间的复用关系；
(3)MT对应的第一小区的SUL载波与DU对应的第二小区的SUL载波之间的复用关系；
(4)MT对应的第一小区的NUL载波与DU对应的第二小区的NUL载波之间的复用关系。
上述复用关系(1)至(3)可以理解为SUL载波相关的复用关系，即在考虑SUL载波情况下，MT对应的第一小区与DU对应的第二小区之间的复用关系；复用关系(4)可以理解为在不考虑SUL载波的情况下，MT对应的第一小区与DU对应的第二小区之间的复用关系。其中，第一小区可以理解为服务小区。
步骤602，第一节点根据复用关系信息，确定第一配置信息。
可以理解的是，IAB donor根据IAB node上报的复用关系信息，为IAB DU配置SUL资源信息。
其中，第一配置信息用于配置SUL资源信息，具体用于配置针对DU的SUL资源信息。SUL资源信息用于支持第二小区通过SUL载波进行上行接收。
在一种实现方式中，SUL资源信息包括一个或多个SUL资源。在另一种实现方式中，SUL资源信息包括各个SUL资源的资源属性。在又一种实现方式中，SUL资源信息包括一个或多个SUL资源以及各个SUL资源的资源属性。其中，资源属性可以是始终可用(hard)、指示是否可用(soft)或不可用。
步骤602中，第一节点根据复用关系信息确定第一配置信息。在另一种实现方式中，第一节点根据第二节点的能力信息，确定第一配置信息。能力信息在图7所示的实施例中进行介绍。
可选的，步骤602之后还包括步骤603：第一节点向第二节点发送第一配置信息。相应的，第二节点接收来自第一节点的第一配置信息。在一种实现方式中，第一节点向第二节点的DU发送第一配置信息。
在一种实现方式中，第一配置信息携带在小区资源配置信令中，小区资源配置信令可以是gNB-DU Cell Resource Configuration信令。在不考虑SUL载波的情况下，gNB-DU Cell Resource Configuration信令用于配置DU资源的资源属性以及DU的传输方向；在考虑SUL载波的情况下，在gNB-DU Cell Resource Configuration信令中增加第一配置信息。第一配置信息配置的SUL资源可以独立于第二小区的NUL资源。或，第二小区的资源配置信息(即现有的gNB-DU Cell Resource Configuration信令)既用于配置NUL载波，也用于配置SUL载波，这样SUL资源无需单独配置。
在另一种实现方式中，SUL资源单独进行配置，那么第一配置信息可以不必携带在小区资源配置信令中。第二小区的数量可能为多个，一个第二小区可以对应一个或多个SUL资源，一个或多个SUL资源可以对应一个SUL资源配置标识，例如小区1至小区3的SUL 资源对应SUL资源配置标识1，小区3至小区4的SUL资源对应SUL资源配置标识2。该种方式，通过将SUL资源配置标识与小区关联，不再需要在每个小区的资源配置中增加SUL的具体资源配置，可以简化SUL资源的配置，降低开销。
可见，步骤603，IAB node通过接收第一配置信息，实现针对DU的SUL资源的配置。
可选的，步骤603之后还包括步骤604，第一节点向第二节点发送SUL资源可用性指示信息。相应的，第二节点接收来自第一节点的SUL资源可用性指示信息。
IAB node的上级节点或IAB donor向IAB node发送SUL资源可用性指示信息。可选的，在SUL资源的资源属性为soft的情况下，执行步骤604。在一种实现方式中，IAB MT接收SUL资源可用性指示信息。
需要说明的是，指示是否可用应理解为指示可用，和不指示可用。不指示可用不表示不可用，表示上级节点不指示该资源是否可用。
其中，SUL资源可用性指示信息用于指示资源属性为soft的SUL资源可用或不可用。
在方式1中，IAB MT接收RRC信令，该RRC信令用于指示SUL资源可用性指示信息在DCI中的位置；IAB MT接收来自其上级节点的DCI，DCI包括SUL资源可用性指示信息，根据RRC信令确定SUL资源可用性指示信息在DCI中的位置。方式1可参见图6a所示。可选的，SUL资源可用性指示信息可表示为针对SUL的AI索引(AI index for SUL)，该DCI为DCI 2_5。
进一步的，在多个第二小区存在SUL载波的情况下，RRC信令可用于指示各个第二小区的SUL资源可用性指示信息在DCI中的位置，DCI包括各个第二小区的SUL资源可用性指示信息。例如，两个第二小区存在SUL载波的情况，可参见图6b所示。
在方式2中，IAB MT接收来自IAB donor CU的RRC信令，该RRC信令用于指示SUL资源配置标识在DCI中的位置；IAB MT接收来自其上级节点的DCI，DCI包括SUL资源配置标识对应的SUL资源可用性指示信息，根据RRC信令确定SUL资源配置标识对应的SUL资源可用性指示信息在DCI中的位置。例如，方式2可参见图6c所示。
在方式3中，IAB MT接收来自IAB donor CU的RRC信令，该RRC信令在配置某个第二小区的资源可用性指示信息在DCI中的位置时，在该第二小区的小区ID后增加一个标识，该标识用于指示该配置是否用于该第二小区的SUL资源的指示。可以理解的是，RRC信令不仅可以用于配置小区q的资源可用性指示信息在DCI中的位置，还可以通过该标识指示该资源可用性指示信息是否适用于SUL资源。
在方式4中，IAB MT接收的DCI中包括特征标识，该特征标识用于指示soft资源可用性指示信息为NUL资源可用性指示信息或SUL资源可用性指示信息。该特征标识可以是DCI中固定位置的一个或多个比特。例如，该特征标识可以是一个比特，该比特为“1”时表示soft资源可用性指示信息为NUL资源可用性指示信息；该比特为“0”时表示soft资源可用性指示信息为SUL资源可用性指示信息。可选的，该特征比特在DCI中的位置由协议规定，或者由RRC进行配置。
在方式5中，IAB donor为SUL资源可用性指示信息配置专门的控制资源集合(control resource set，CORESET)或可用指示-无线网络临时标识(availability indicator-radio network temporary identifier，AI-RNTI)；IAB MT在相应下行控制信道资源上接收携带SUL资源可 用性指示信息的信令，例如DCI 2_5；或者接收到通过特定AI-RNTI加扰的DCI 2_5，表示DCI 2_5用于指示资源属性为soft的SUL资源是否可用。
在方式6中，协议规定DCI中的soft资源可用性指示信息用于所有上行载波，即既适用于SUL资源，又适用于NUL资源。
上述SUL资源可用性指示信息的值和含义可参见下表4所示。
Figure PCTCN2020123438-appb-000005
表4
可见，步骤604，IAB node通过接收SUL资源可用性指示信息，确定SUL资源是否可用。
在图6所示的方法中，IAB node向IAB donor上报SUL载波相关的复用关系，有助于IAB donor为SUL载波配置资源，从而提升网络频谱效率。
上述复用关系信息可以是以下几种方式中的一种：
方式一，复用关系信息包括SUL配置信息的配置索引，用于指示配置索引所标识的SUL频段相关的复用关系。可选的，复用关系信息可以是在表1所示IE的基础上，增加SUL配置信息的配置索引。其中，SUL配置信息的配置索引可以携带在第二配置信息或能力信息中，第二配置信息或能力信息在图7所示实施例中进行介绍。
示例1，在表1所示IE中的“IAB-MT Cell Item”条目下增加“IAB-MT SUL Item”，可参 见表5所示。“IAB-MT Cell Item”条目下增加的“IAB-MT SUL Item”表示针对MT的SUL配置信息的配置索引，从而可以指示上述复用关系(1)。可以理解的是第二节点通过该IE向第一节点上报第一小区的SUL载波与第二小区的NUL载波之间的复用关系。
Figure PCTCN2020123438-appb-000006
表5
以表5中的“DU_RX/MT_RX”所在行为例，该行表示第二小区通过NUL载波进行接收与第一小区通过SUL载波进行接收能否同时进行。
示例2，在表1所示IE中的“NR Cell Identity”条目下增加“IAB-DU SUL Item”，可参见表6所示。“NR Cell Identity”条目下增加“IAB-DU SUL Item”表示针对DU的SUL配置信息的配置索引，从而可以指示上述复用关系(2)。可以理解的是第二节点通过该IE向第一节点上报第一小区的NUL载波与第二小区的SUL载波之间的复用关系。
Figure PCTCN2020123438-appb-000007
Figure PCTCN2020123438-appb-000008
表6
以表6中的“DU_RX/MT_RX”所在行为例，该行表示第二小区通过SUL载波进行接收与第一小区通过NUL载波进行接收能否同时进行。
方式二，复用关系信息包括SUL带宽编号，用于指示SUL带宽编号所对应的SUL频段相关的复用关系。可选的，复用关系信息可以是在表1所示IE的基础上，增加SUL带宽编号。其中，SUL带宽编号可以携带在第二配置信息或能力信息中，第二配置信息或能力信息在图7所示实施例中进行介绍。
其中，SUL带宽编号可以是3GPP协议预定义的协议编号，例如可以是n80至n89以及n95中的一个或多个。
示例3，在表1所示IE中的“IAB-MT Cell Item”条目下增加“IAB-MT SUL band list”，可参见表7所示。“IAB-MT Cell Item”条目下增加的“IAB-MT SUL band list”表示针对MT的SUL带宽编号，从而可以指示上述复用关系(1)。可以理解的是第二节点通过该IE向第一节点上报第一小区的SUL载波与第二小区的NUL载波之间的复用关系。
Figure PCTCN2020123438-appb-000009
Figure PCTCN2020123438-appb-000010
表7
示例4，在表1所示IE中的“IAB-MT Cell Item”条目下增加“IAB-DU SUL band list”，可参见表8所示。“IAB-DU Cell Item”条目下增加的“IAB-DU SUL band list”表示针对DU的SUL带宽编号，从而可以指示上述复用关系(2)。可以理解的是第二节点通过该IE向第一节点上报第一小区的NUL载波与第二小区的SUL载波之间的复用关系。
Figure PCTCN2020123438-appb-000011
Figure PCTCN2020123438-appb-000012
表8
可以理解的是，方式一和方式二在表1的基础上增加条目，从而指示上述复用关系(1)至(3)中的任意一种，可节省信令开销。
方式三，复用关系信息包括上述复用关系(1)至(3)中的一种或多种。可选的，复用关系信息可以是在表1所示IE的基础上，增加以下一种或多种：
A、{DU DL_TX/MT SUL_TX}；
B、{DU SUL_RX/MT SUL_TX}；
C、{DU UL_RX/MT SUL_TX}；
D、{DU SUL_RX/MT DL_RX}；
E、{DU SUL_RX/MT UL_TX}。
例如，A可表示第二小区通过NUL载波进行发送与第一小区通过SUL载波进行发送能否同时进行。
示例5，在表1所示的IE中增加上述A和C，可参见表9所示，可指示上述复用关系(1)。
Figure PCTCN2020123438-appb-000013
Figure PCTCN2020123438-appb-000014
表9
可以理解的是，方式三在表1的基础中，增加关于SUL载波的复用能力的定义，实现较为简单。
方式四，复用关系信息包括SUL标识，用于指示SUL标识所标识的第一小区和/或第二小区的SUL载波的复用关系。可选的，复用关系信息可以是在表1所示IE的基础上，增加SUL标识。
示例6，在表1所示IE中的“IAB-MT Cell Item”条目下增加“SUL flag”，可参见表10所示。“SUL flag”为true表示存在第一小区的SUL载波相关的复用关系，为flase表示不存在第一小区的SUL载波相关的复用关系。可以理解的是第二节点通过该IE向第一节点上报第一小区的SUL载波与第二小区的NUL载波之间的复用关系。
Figure PCTCN2020123438-appb-000015
表10
示例7，在表1所示IE中的“NR Cell Identity”条目下增加“SUL flag”，“SUL flag”为true表示存在第二小区的SUL载波相关的复用关系，为false表示不存在第二小区的SUL载波 相关的复用关系。可以理解的是第二节点通过该IE向第一节点上报第一小区的NUL载波与第二小区的SUL载波之间的复用关系。
可以理解的是，方式四在表1的基础上增加条目，从而指示上述复用关系(1)至(3)中的任意一种，可节省信令开销。
需要说明的是，上述复用关系信息的四种方式可则一执行，也可则二或更多执行。这四种方式用于举例，实际应用中可能还存在其他方式的复用关系信息。
请参见图7，为本申请提供的配置信息发送的流程示意图，该流程可以包括但不限于如下步骤：
步骤701，第一节点向第二节点发送第一配置信息。相应的，第二节点接收来自第一节点的第一配置信息。
步骤701的实现过程可参见步骤603的具体描述，在此不再赘述。
步骤702，第一节点向第二节点发送第二配置信息。相应的，第二节点接收来自第一节点的第二配置信息。在一种实现方式中，第一节点向第二节点的MT发送第二配置信息。
可以理解的是，第一配置信息为IAB donor为IAB DU配置的，第二配置信息为IAB donor为IAB MT配置的。需要说明的是，本申请不限定步骤701与步骤702执行的先后顺序。
其中，第二配置信息用于配置针对MT的SUL资源信息，SUL资源信息用于支持第一小区通过SUL载波进行上行发送。
在一种实现方式中，第二配置信息包括SUL配置信息。在另一种实现方式中，第二配置信息包括SUL配置信息的配置索引，用于标识SUL配置信息。在又一种实现方式中，第二配置信息包括SUL配置信息和SUL配置信息的配置索引。其中，SUL配置信息包括SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL绝对无线频道编号(absolute radio frequency channel number，ARFCN)、SUL带宽编号、SUL载波列表中的一种或多种。
SUL配置信息的配置索引可增加在表1所示的IE中，以指示上述复用关系(1)至(3)中的任一种，这样可节省信令开销。在不考虑信令开销的情况下，可将SUL配置信息增加在表1所示的IE中，以指示上述复用关系(1)至(3)中的任一种。
SUL带宽编号可增加在表1所示的IE中，以指示上述复用关系(1)至(3)中的任一种，这样可节省信令开销。
第一节点向第二节点发送第二配置信息是一种实现方式，在另一种实现方式中，核心网设备向第二节点发送第二配置信息。核心网设备，例如运维服务器(operation and maintenance，OAM)。核心网设备为IAB DU配置工作频段资源，该工作频段资源包括至少一个SUL频段，所述至少一个SUL频段可以是SUL频段上的部分频段资源。所述至少一个SUL频段即为SUL配置信息，该工作频段资源即为第二配置信息，该工作频段资源还可以包括所述至少一个SUL频段对应的配置索引，即SUL配置信息的配置索引。
可选的，图7还包括步骤700，第二节点向第一节点发送能力信息。在一种实现方式中，IAB DU向IAB donor发送能力信息。本申请不限定步骤700在图7中执行的顺序。
其中，能力信息包括DU是否支持SUL，以及支持的SUL信息。SUL信息可以包括但不限于以下一种或多种：SUL配置信息的配置索引、SUL带宽列表、SUL传输带宽、SUL 频率偏移、SUL绝对无线频道编号、SUL带宽编号、SUL载波列表、SUL子载波间隔。
SUL配置信息的配置索引或SUL带宽编号可增加在表1所示的IE中，以指示上述复用关系(1)至(3)中的任一种，这样可节省信令开销。
在一种实现方式中，IAB donor可根据能力信息确定第一配置信息。在另一种实现方式中，步骤700可与步骤701解耦，即IAB donor确定第一配置信息与IAB node上报的能力信息无关。
可选的，步骤700可在图6中执行，不限定步骤700在图6中执行的顺序。
在图7所示的实施例中，通过第一配置信息实现针对DU的SUL载波的配置，通过第二配置信息实现针对MT的SUL载波的配置。
请参见图8，为本申请提供的复用关系上报方法的流程示意图，该流程可以包括但不限于如下步骤：
步骤801，第二节点向第一节点发送符号指示信息。相应的，第一节点接收来自第二节点的符号指示信息。
其中，符号指示信息用于指示第二节点发送的保护符号数为SUL场景下的保护符号数。
在一种实现方式中，符号指示信息通过MAC CE中的一个比特进行指示。例如，该比特为“1”时表示为SUL场景下的保护符号数；该比特为“0”时表示为NUL场景下的保护符号数。例如，可参见图8a所示，第一个8位比特中的某个预留比特位用于表示符号指示信息。
在另一种实现方式中，符号指示信息通过新定义的逻辑信道标识进行指示。新定义的逻辑信道标识A用于指示保护符号数为SUL场景下的保护符号数。在NUL场景下的保护符号数可通过现有的逻辑信道标识进行指示，例如逻辑信道标识为50，用于指示NUL上行场景下的保护符号数；逻辑信道标识为45，用于指示NUL下行场景下的保护符号数。具体A的取值在本申请不作限定，但不与现有的逻辑信道标识重复。
在又一种实现方式中，符号指示信息通过SUL的上行传输资源进行指示。可以理解的是，IAB MT通过SUL的上行传输资源发送的保护符号数即为SUL场景下的保护符号数。相应的，协议可规定：当IAB node同时具有SUL载波和NUL载波的传输资源时，通过NUL的上行传输资源发送的保护符号数即为NUL场景下的保护符号数；通过SUL的上行传输资源发送的保护符号数即为SUL场景下的保护符号数。
在图8所示的方法中，通过符号指示信息可以区分SUL场景下的保护符号数和NUL场景下的保护符号数。
图6、图7以及图8所示的方法可以独立执行，也可结合执行，例如图6与图7可以结合执行，图6与图8可以结合执行。
上述方法介绍将SUL载波应用于IAB系统时，如何上报SUL载波相关的复用关系，如何配置SUL资源信息，如何区分SUL场景与NUL场景下的保护符号数。若IAB系统支持补充下行(supplementary downlink，SDL)载波，或IAB系统支持其他扩展传输带宽的分量载波(component carrier)，那么可将上述方法中的SUL载波替换为SDL载波或分量载波。
相应于上述方法实施例给出的方法，本申请实施例还提供了相应的装置，包括用于执 行上述实施例相应的模块。所述模块可以是软件，也可以是硬件，或者是软件和硬件结合。
图9给出了一种通信装置的结构示意图。通信装置900可以是第二节点，也可以是第一节点，也可以是支持第二节点实现上述方法的芯片、芯片系统、或处理器等，还可以是支持第一节点实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置900可以包括一个或多个处理器901，处理器901也可以称为处理单元或处理模块等，可以实现一定的控制功能。处理器901可以是通用处理器或者专用处理器等。通用处理器例如可以是中央处理器，专用处理器例如可以是基带处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，MT、DU或CU等)进行控制，执行软件程序，处理软件程序的数据。
在一种可选的设计中，处理器901也可以存有指令903，所述指令903可以被处理器901运行，使得通信装置900执行上述方法实施例中描述的方法。
在另一种可选的设计中，处理器901中可以包括用于实现接收和发送功能的收发单元。例如该收发单元可以是收发电路，或者是接口。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路或接口可以用于指令的读写，或者，上述收发电路或接口可以用于信号的传输。
可选的，通信装置900中可以包括一个或多个存储器902，其上可以存有指令904，指令904可在处理器901上被运行，使得通信装置900执行上述方法实施例中描述的方法。可选的，存储器902中还可以存储有数据。可选的，处理器901中也可以存储指令和/或数据。处理器901和存储器902可以单独设置，也可以集成在一起。例如，上述方法实施例中所描述的对应关系可以存储在存储器902中，或者存储在处理器901中。
可选的，通信装置900还可以包括收发器905和/或天线906。收发器905可以称为收发单元、收发机、收发电路、收发装置或收发模块等，用于实现收发功能。
可选的，本申请实施例中，通信装置900为第二节点时，可以包含各种功能模块，用于执行图6中的步骤601、步骤603以及步骤604；图7中的步骤700至步骤702；图8中的步骤801。
可选的，本申请实施例中，通信装置900为第一节点时，可以包含各种功能模块，用于执行图6中的步骤601至步骤604；图7中的步骤700至步骤702；图8中的步骤801。
本申请中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)上。IC可以包括模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)等。印刷电路板(printed circuit board，PCB)上印刷电路可以实现IC。
以上实施例描述中的通信装置可以是网络设备或者终端设备，但本申请中描述的装置的范围并不限于此，而且通信装置的结构可以不受图9的限制。通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或其子系统；
(2)接收机、终端、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备、机器设备、家居设备、医疗设备、工业设备等等。
如图10所示，本申请又一实施例提供了一种通信装置1000。该装置可以是第二节点，也可以是第二节点的部件(例如，集成电路，芯片等等)。或者，该装置可以是第一节点， 也可以是第一节点的部件(例如，集成电路，芯片等等)。该装置也可以是其他通信模块，用于实现本申请方法实施例中的方法。该通信装置1000可以包括：处理单元1001(或称为处理模块)。可选的，还可以包括通信单元1002(或称为收发单元，接收单元和/或发送单元)。可选的，还可以包括存储单元(或称为存储模块)。
在一种可能的设计中，如图10中的一个或者多个单元可能由一个或者多个处理器来实现，或者由一个或者多个处理器和存储器来实现；或者由一个或多个处理器和收发器实现；或者由一个或者多个处理器、存储器和收发器实现，本申请实施例对此不作限定。所述处理器、存储器、收发器可以单独设置，也可以集成。
可选的，本申请实施例中的通信装置1000中各个模块可以用于执行本申请实施例中图6、图7或图8描述的方法，也可以用于执行上述两个图或更多个图中描述的方法相互结合的方法。
如图11所示，为本申请提供的一种IAB节点的结构示意图。IAB节点包括DU和MT。其中，MT是IAB节点的UE功能模块，即IAB节点通过MT与上级节点进行通信；DU是IAB节点的基站功能模块，即IAB节点通过DU与下级节点或UE进行通信。IAB节点的MT与DU均具有完整的收发模块，且两者之间具有接口。需要说明的是，MT与DU为逻辑模块，在实际中，两者可以共用部分子模块，例如可共用收发天线，基带处理模块等。
可以理解的是，本申请实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，比如其当前所基于的方案，而独立实施，解决相应的技术问题，达到相应的效果，也可以在某些场景下，依据需求与其他特征进行结合。相应的，本申请实施例中给出的装置也可以相应的实现这些特征或功能，在此不予赘述。
本领域技术人员还可以理解到本申请实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员对于相应的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本申请实施例保护的范围。
可以理解，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
本申请所描述的方案可通过各种方式来实现。例如，这些技术可以用硬件、软件或者硬件结合的方式来实现。对于硬件实现，用于在通信装置(例如，基站，终端、网络实体、或芯片)处执行这些技术的处理单元，可以实现在一个或多个通用处理器、DSP、数字信号处理器件、ASIC、可编程逻辑器件、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 ram bus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
可以理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。可以理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本申请中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本申请并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本申请中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以理解，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本领域普通技术人员可以理解，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
可以理解，本申请中描述的系统、装置和方法也可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划 分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请中各个实施例之间相同或相似的部分可以互相参考。在本申请中各个实施例、以及各实施例中的各个实施方式/实施方法/实现方法中，如果没有特殊说明以及逻辑冲突，不同的实施例之间、以及各实施例中的各个实施方式/实施方法/实现方法之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例、以及各实施例中的各个实施方式/实施方法/实现方法中的技术特征根据其内在的逻辑关系可以组合形成新的实施例、实施方式、实施方法、或实现方法。以上所述的本申请实施方式并不构成对本申请保护范围的限定。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。

Claims (44)

  1. 一种复用关系上报方法，其特征在于，所述方法应用于包括第一节点和第二节点的通信系统，所述第一节点为所述第二节点的上级节点或宿主节点，所述第二节点包括移动终端和分布式单元；所述方法包括：
    所述第二节点向所述第一节点发送复用关系信息；所述复用关系信息用于指示以下一种或多种复用关系：
    所述移动终端对应的第一小区的补充上行SUL载波与所述分布式单元对应的第二小区的普通上行NUL载波之间的复用关系；
    所述移动终端对应的第一小区的NUL载波与所述分布式单元对应的第二小区的SUL载波之间的复用关系；
    所述移动终端对应的第一小区的SUL载波与所述分布式单元对应的第二小区的SUL载波之间的复用关系。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第二节点接收来自所述第一节点的第一配置信息，所述第一配置信息用于配置SUL资源信息，所述SUL资源信息用于支持所述第二小区通过SUL载波进行上行接收；
    其中，所述SUL资源信息包括一个或多个SUL资源以及所述SUL资源的资源属性，所述资源属性为始终可用，指示是否可用，或不可用。
  3. 根据权利要求2所述的方法，其特征在于，所述SUL资源通过所述SUL资源对应的SUL资源配置标识关联至一个或多个所述第二小区。
  4. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    所述SUL资源的资源属性为指示是否可用，所述第二节点接收来自所述第一节点的SUL资源可用性指示信息，所述SUL资源可用性指示信息用于指示所述SUL资源可用或不可用。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述复用关系信息包括SUL配置信息的配置索引、SUL带宽编号或SUL标识中的一种或多种。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述第二节点接收第二配置信息，所述第二配置信息用于配置SUL资源信息，所述SUL资源信息用于支持所述第一小区通过SUL载波进行上行发送；所述第二配置信息包括SUL配置信息以及所述SUL配置信息的配置索引，所述SUL配置信息包括SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL绝对无线频道编号、SUL带宽编号、SUL载波列表中的一种或多种；
    所述第二节点根据所述第二配置信息，确定所述复用关系信息。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    所述第二节点向所述第一节点发送能力信息，所述能力信息包括SUL信息，所述SUL信息包括SUL配置信息的配置索引、SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL带宽编号、SUL绝对无线频道编号、SUL载波列表、SUL子载波间隔中的一种或多种。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述方法还包括：
    所述第二节点向所述第一节点发送符号指示信息，所述符号指示信息用于指示所述第二节点发送的保护符号数为SUL场景下的保护符号数。
  9. 根据权利要求8所述的方法，其特征在于，所述符号指示信息通过新定义的逻辑信道标识进行指示。
  10. 根据权利要求8所述的方法，其特征在于，所述符号指示信息通过SUL的上行传输资源进行指示。
  11. 一种复用关系上报方法，其特征在于，所述方法应用于包括第一节点和第二节点的通信系统，所述第一节点为所述第二节点的上级节点或宿主节点，所述第二节点包括移动终端和分布式单元；所述方法包括：
    所述第一节点接收来自所述第二节点的分布式单元的复用关系信息；所述复用关系信息用于指示以下一种或多种复用关系：
    所述移动终端对应的第一小区的补充上行SUL载波与所述分布式单元对应的第二小区的普通上行NUL载波之间的复用关系；
    所述移动终端对应的第一小区的NUL载波与所述分布式单元对应的第二小区的SUL载波之间的复用关系；
    所述移动终端对应的第一小区的SUL载波与所述分布式单元对应的第二小区的SUL载波之间的复用关系；
    所述第一节点根据所述复用关系信息，确定第一配置信息。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述第一节点向所述分布式单元发送第一配置信息，所述第一配置信息用于配置SUL资源信息，所述SUL资源信息用于支持所述第二小区通过SUL载波进行上行接收；
    其中，所述SUL资源信息包括一个或多个SUL资源以及所述SUL资源的资源属性，所述资源属性为始终可用，指示是否可用，或不可用。
  13. 根据权利要求12所述的方法，其特征在于，所述SUL资源通过所述SUL资源对应的SUL资源配置标识关联至一个或多个所述第二小区。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    所述第一节点向第二节点发送SUL资源可用性指示信息，所述SUL资源可用性指示信息用于指示所述SUL资源可用或不可用。
  15. 根据权利要求11-14任一项所述的方法，其特征在于，所述复用关系信息包括SUL配置信息的配置索引、SUL带宽编号或SUL标识中的一种或多种。
  16. 根据权利要求11-15任一项所述的方法，其特征在于，所述方法还包括：
    所述第一节点向所述移动终端发送第二配置信息，所述第二配置信息用于配置SUL资源信息，所述SUL资源信息用于支持所述第一小区通过SUL载波进行上行发送；所述第二配置信息包括SUL配置信息以及所述SUL配置信息的配置索引，所述SUL配置信息包括SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL绝对无线频道编号、SUL带宽编号、SUL载波列表中的一种或多种。
  17. 根据权利要求11-16任一项所述的方法，其特征在于，所述方法还包括：
    所述第一节点接收来自所述第二节点的移动终端的能力信息，所述能力信息包括SUL 信息，所述SUL信息包括SUL配置信息的配置索引、SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL带宽编号、SUL绝对无线频道编号、SUL载波列表、SUL子载波间隔中的一种或多种。
  18. 根据权利要求11-17任一项所述的方法，其特征在于，所述方法还包括：
    所述第一节点接收来自所述第二节点的符号指示信息，所述符号指示信息用于指示所述第二节点发送的第一保护符号数为SUL场景下的保护符号数。
  19. 根据权利要求18所述的方法，其特征在于，所述符号指示信息通过新定义的逻辑信道标识进行指示。
  20. 根据权利要求18所述的方法，其特征在于，所述符号指示信息通过SUL的上行传输资源进行指示。
  21. 一种第二节点，其特征在于，所述第二节点应用于通信系统，所述通信系统包括第一节点和所述第二节点；所述第一节点为所述第二节点的上级节点或宿主节点，所述第二节点包括移动终端和分布式单元；所述第二节点包括处理单元和通信单元；
    所述处理单元，用于通过所述通信单元向第一节点发送复用关系信息；所述复用关系信息用于指示以下一种或多种复用关系：
    所述移动终端对应的第一小区的补充上行SUL载波与所述分布式单元对应的第二小区的普通上行NUL载波之间的复用关系；
    所述移动终端对应的第一小区的NUL载波与所述分布式单元对应的第二小区的SUL载波之间的复用关系；
    所述移动终端对应的第一小区的SUL载波与所述分布式单元对应的第二小区的SUL载波之间的复用关系。
  22. 根据权利要求21所述的第二节点，其特征在于，
    所述处理单元，还用于通过所述通信单元接收来自所述第一节点的第一配置信息，所述第一配置信息用于配置SUL资源信息，所述SUL资源信息用于支持所述第二小区通过SUL载波进行上行接收；
    其中，所述SUL资源信息包括一个或多个SUL资源以及所述SUL资源的资源属性，所述资源属性为始终可用，指示是否可用，或不可用。
  23. 根据权利要求22所述的第二节点，其特征在于，所述SUL资源通过所述SUL资源对应的SUL资源配置标识关联至一个或多个所述第二小区。
  24. 根据权利要求22或23所述的第二节点，其特征在于，
    所述SUL资源的资源属性为指示是否可用，所述处理单元，还用于通过所述通信单元接收来自所述第一节点的SUL资源可用性指示信息，所述SUL资源可用性指示信息用于指示所述SUL资源可用或不可用。
  25. 根据权利要求21-24任一项所述的第二节点，其特征在于，所述复用关系信息包括SUL配置信息的配置索引、SUL带宽编号或SUL标识中的一种或多种。
  26. 根据权利要求21-25任一项所述的第二节点，其特征在于，
    所述处理单元，还用于通过所述通信单元接收第二配置信息，所述第二配置信息用于配置SUL资源信息，所述SUL资源信息用于支持所述第一小区通过SUL载波进行上行发 送；所述第二配置信息包括SUL配置信息以及所述SUL配置信息的配置索引，所述SUL配置信息包括SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL绝对无线频道编号、SUL带宽编号、SUL载波列表中的一种或多种；
    所述第二节点根据所述第二配置信息，确定所述复用关系信息。
  27. 根据权利要求21-26任一项所述的第二节点，其特征在于，
    所述处理单元，还用于通过所述通信单元向所述第一节点发送能力信息，所述能力信息包括SUL信息，所述SUL信息包括SUL配置信息的配置索引、SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL带宽编号、SUL绝对无线频道编号、SUL载波列表、SUL子载波间隔中的一种或多种。
  28. 根据权利要求21-27任一项所述的第二节点，其特征在于，
    所述处理单元，还用于通过所述通信单元向所述第一节点发送符号指示信息，所述符号指示信息用于指示所述第二节点发送的保护符号数为SUL场景下的保护符号数。
  29. 根据权利要求28所述的第二节点，其特征在于，所述符号指示信息通过新定义的逻辑信道标识进行指示。
  30. 根据权利要求28所述的第二节点，其特征在于，所述符号指示信息通过SUL的上行传输资源进行指示。
  31. 一种第一节点，其特征在于，所述第一节点应用于通信系统，所述通信系统包括所述第一节点和第二节点，所述第一节点为所述第二节点的上级节点或宿主节点，所述第二节点包括移动终端和分布式单元；所述第一节点包括处理单元和通信单元；
    所述通信单元，用于接收来自所述第二节点的分布式单元的复用关系信息；所述复用关系信息用于指示以下一种或多种复用关系：
    所述移动终端对应的第一小区的补充上行SUL载波与所述分布式单元对应的第二小区的普通上行NUL载波之间的复用关系；
    所述移动终端对应的第一小区的NUL载波与所述分布式单元对应的第二小区的SUL载波之间的复用关系；
    所述移动终端对应的第一小区的SUL载波与所述分布式单元对应的第二小区的SUL载波之间的复用关系；
    所述处理单元，用于根据所述复用关系信息，确定第一配置信息。
  32. 根据权利要求31所述的第一节点，其特征在于，
    所述通信单元，还用于向所述分布式单元发送第一配置信息，所述第一配置信息用于配置SUL资源信息，所述SUL资源信息用于支持所述第二小区通过SUL载波进行上行接收；
    其中，所述SUL资源信息包括一个或多个SUL资源以及所述SUL资源的资源属性，所述资源属性为始终可用，指示是否可用，或不可用。
  33. 根据权利要求32所述的第一节点，其特征在于，所述SUL资源通过所述SUL资源对应的SUL资源配置标识关联至一个或多个所述第二小区。
  34. 根据权利要求32或33所述的第一节点，其特征在于，
    所述通信单元，还用于向第二节点发送SUL资源可用性指示信息，所述SUL资源可 用性指示信息用于指示所述SUL资源可用或不可用。
  35. 根据权利要求31-34任一项所述的第一节点，其特征在于，所述复用关系信息包括SUL配置信息的配置索引、SUL带宽编号或SUL标识中的一种或多种。
  36. 根据权利要求31-35任一项所述的第一节点，其特征在于，
    所述通信单元，还用于向所述移动终端发送第二配置信息，所述第二配置信息用于配置SUL资源信息，所述SUL资源信息用于支持所述第一小区通过SUL载波进行上行发送；所述第二配置信息包括SUL配置信息以及所述SUL配置信息的配置索引，所述SUL配置信息包括SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL绝对无线频道编号、SUL带宽编号、SUL载波列表中的一种或多种。
  37. 根据权利要求31-36任一项所述的第一节点，其特征在于，
    所述通信单元，还用于接收来自所述第二节点的移动终端的能力信息，所述能力信息包括SUL信息，所述SUL信息包括SUL配置信息的配置索引、SUL带宽列表、SUL传输带宽、SUL频率偏移、SUL带宽编号、SUL绝对无线频道编号、SUL载波列表、SUL子载波间隔中的一种或多种。
  38. 根据权利要求31-37任一项所述的第一节点，其特征在于，
    所述通信单元，还用于接收来自所述第二节点的符号指示信息，所述符号指示信息用于指示所述第二节点发送的第一保护符号数为SUL场景下的保护符号数。
  39. 根据权利要求38所述的第一节点，其特征在于，所述符号指示信息通过新定义的逻辑信道标识进行指示。
  40. 根据权利要求38所述的第一节点，其特征在于，所述符号指示信息通过SUL的上行传输资源进行指示。
  41. 一种第二节点，其特征在于，所述第二节点包括处理器和存储器；
    所述存储器用于存储计算机程序；
    所述处理器用于执行所述存储器存储的计算机程序，使得所述装置实现如权利要求1至10任一项所述的方法。
  42. 一种第一节点，其特征在于，所述第二节点包括处理器和存储器；
    所述存储器用于存储计算机程序；
    所述处理器用于执行所述存储器存储的计算机程序，使得所述装置实现如权利要求11至20任一项所述的方法。
  43. 一种通信装置，包括至少一个处理器和通信接口，所述至少一个处理器用于执行计算机程序，所述通信接口用于输入和/或输出信息，使得所述装置实现如权利要求1至10中任一项所述的方法，或实现如权利要求11至20任一项所述的方法。
  44. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至10中任一项所述的方法，或执行如权利要求1至10中任一项所述的方法。
PCT/CN2020/123438 2020-10-23 2020-10-23 复用关系上报方法及通信装置 WO2022082789A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/123438 WO2022082789A1 (zh) 2020-10-23 2020-10-23 复用关系上报方法及通信装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/123438 WO2022082789A1 (zh) 2020-10-23 2020-10-23 复用关系上报方法及通信装置

Publications (1)

Publication Number Publication Date
WO2022082789A1 true WO2022082789A1 (zh) 2022-04-28

Family

ID=81291149

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123438 WO2022082789A1 (zh) 2020-10-23 2020-10-23 复用关系上报方法及通信装置

Country Status (1)

Country Link
WO (1) WO2022082789A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110278610A (zh) * 2019-05-28 2019-09-24 华为技术有限公司 一种资源配置方法及通信装置
US20200107369A1 (en) * 2018-09-27 2020-04-02 Hyoungsuk Jeon RACH Type Switching
CN111096027A (zh) * 2018-08-07 2020-05-01 Lg电子株式会社 在无线通信系统中操作节点的方法和使用该方法的装置
US20200146054A1 (en) * 2018-11-01 2020-05-07 Comcast Cable Communications, Llc Random Access Response Reception

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111096027A (zh) * 2018-08-07 2020-05-01 Lg电子株式会社 在无线通信系统中操作节点的方法和使用该方法的装置
US20200107369A1 (en) * 2018-09-27 2020-04-02 Hyoungsuk Jeon RACH Type Switching
US20200146054A1 (en) * 2018-11-01 2020-05-07 Comcast Cable Communications, Llc Random Access Response Reception
CN110278610A (zh) * 2019-05-28 2019-09-24 华为技术有限公司 一种资源配置方法及通信装置

Similar Documents

Publication Publication Date Title
CN110572877B (zh) 一种信息发送、接收的方法及装置
CN110662299B (zh) 通信方法、装置及存储介质
US20230362727A1 (en) Communication method and apparatus based on integrated access and backhaul
WO2021159341A1 (zh) 一种通信方法及通信装置
CN113573408A (zh) 一种资源协调方法及装置
WO2023130897A1 (zh) 一种通信方法、装置及系统
US20230007645A1 (en) Resource Indication Method and Communication Apparatus
US20220394503A1 (en) Wireless communication method and device
US10944625B2 (en) Bearer configuration method and related products
WO2022082789A1 (zh) 复用关系上报方法及通信装置
WO2022088085A1 (zh) 上报直流载波位置的方法、终端设备和网络设备
CN115175350A (zh) 一种资源配置方法及通信装置
WO2023051755A1 (zh) 一种资源配置方法及通信装置
CN114223292B (zh) 一种资源指示方法及装置
WO2024067869A1 (zh) 通信方法和通信装置
WO2023102813A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022141103A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022068416A1 (zh) 一种反馈信息的传输方法和通信设备
WO2023102848A1 (zh) 无线通信的方法和终端设备
WO2023000328A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022236697A1 (zh) 无线通信的方法、终端设备和网络设备
WO2024011553A9 (zh) 无线通信的方法、终端设备和网络设备
WO2023197936A1 (zh) 一种通信方法及装置
WO2022077346A1 (zh) 信道传输的方法、终端设备和网络设备
CN116437470A (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: 20958371

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20958371

Country of ref document: EP

Kind code of ref document: A1