WO2022082518A1 - 信号的接收和发送方法、装置和通信系统 - Google Patents

信号的接收和发送方法、装置和通信系统 Download PDF

Info

Publication number
WO2022082518A1
WO2022082518A1 PCT/CN2020/122555 CN2020122555W WO2022082518A1 WO 2022082518 A1 WO2022082518 A1 WO 2022082518A1 CN 2020122555 W CN2020122555 W CN 2020122555W WO 2022082518 A1 WO2022082518 A1 WO 2022082518A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
iab
reconfiguration message
reconfiguration
message
Prior art date
Application number
PCT/CN2020/122555
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/122555 priority Critical patent/WO2022082518A1/zh
Priority to JP2023522374A priority patent/JP2023545801A/ja
Priority to CN202080106036.1A priority patent/CN116326161A/zh
Publication of WO2022082518A1 publication Critical patent/WO2022082518A1/zh
Priority to US18/133,805 priority patent/US20230247514A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
    • H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the embodiments of the present application relate to the field of communication technologies.
  • IAB integrated access and backhaul
  • NR New Radio
  • IAB-donor represents a network device (eg, gNB) that supports IAB functionality.
  • the backhaul can happen over a single hop or multiple hops.
  • IAB-node supports the function of gNB-DU (distributed unit, distributed unit). IAB-node DU is also called IAB-DU. IAB-DU is the wireless communication between terminal equipment (UE) and next hop IAB-node. The endpoint of the access (NR access) interface is also the endpoint of the F1 protocol to the gNB-CU (central unit) on the IAB-donor.
  • gNB-DU distributed unit, distributed unit
  • IAB-node DU is also called IAB-DU.
  • IAB-DU is the wireless communication between terminal equipment (UE) and next hop IAB-node.
  • the endpoint of the access (NR access) interface is also the endpoint of the F1 protocol to the gNB-CU (central unit) on the IAB-donor.
  • IAB-node In addition to gNB-DU functions, IAB-node also supports a part of UE functions, called IAB-MT, IAB-MT includes functions such as physical layer, layer 2, RRC and NAS to connect to another IAB-node or IAB-donor gNB-DU, connected to the gNB-CU on the IAB-donor and connected to the core network.
  • IAB-MT includes functions such as physical layer, layer 2, RRC and NAS to connect to another IAB-node or IAB-donor gNB-DU, connected to the gNB-CU on the IAB-donor and connected to the core network.
  • the IAB-node under the IAB-donor is connected to the IAB-donor through one or more hops, and the IAB-donor is the root node (root).
  • FIG. 1 is a schematic diagram of the IAB topology.
  • the IAB-node 100 includes an IAB-MT functional unit 101 and an IAB-DU functional unit 102, and the adjacent nodes on the interface of the IAB-DU functional unit 102 are called child nodes ( child node), the child nodes 201, 202, 203 shown in FIG. 1; the adjacent node on the interface of the IAB-MT functional unit 101 is called the parent node, the parent node shown in FIG. 1 301, 302.
  • the direction from the IAB-node 100 to the child nodes 201, 202, 203 is called the downstream direction
  • the direction from the IAB-node 100 to the parent nodes 301, 302 is called the upstream (upstream) direction.
  • the IAB-donor (not shown) performs centralized resource, topology and routing management for the IAB topology 10 .
  • the inventors of the present application have found that when an IAB-node is migrated from one parent node to another parent node, how to reconfigure the child nodes and/or terminal devices under the IAB-node, in the prior art not involved.
  • An integrated access and backhaul node receives a first reconfiguration message and sends a message to a wireless device.
  • the indication information is sent to enable the wireless device to apply the configuration in the second reconfiguration message, thereby enabling the wireless device to perform handover or reconfiguration.
  • a signal receiving and sending device which is set at an integrated access and backhaul node, and the signal receiving and sending device includes:
  • the first sending unit sends indication information to the wireless device, where the indication information is used to instruct the wireless device to apply the configuration in the second reconfiguration message.
  • a signal receiving apparatus which is arranged in a wireless device, and the signal receiving apparatus includes:
  • a third receiving unit which receives the indication information
  • the indication information is used to indicate the configuration of the wireless device in the second reconfiguration message received by the radio resource control layer application.
  • an apparatus for sending a signal which is arranged in a source centralized unit, and the apparatus for sending a signal includes:
  • a fourth sending unit that sends the first reconfiguration message to the integrated access and backhaul node
  • a fifth sending unit which sends a second reconfiguration message to the wireless device, wherein, in the second reconfiguration message, a target candidate cell with the same identification as the current serving cell of the integrated access and backhaul node is configured once.
  • a method for receiving and sending a signal including:
  • the integrated access and backhaul node receives the first reconfiguration message
  • the integrated access and backhaul node sends indication information to the wireless device, where the indication information is used to instruct the wireless device to apply the configuration in the second reconfiguration message.
  • a method for receiving a signal including:
  • the wireless device receives the second reconfiguration message
  • the wireless device receives indication information, where the indication information is used to instruct the wireless device to apply the configuration in the second reconfiguration message received by the radio resource control layer.
  • a method for sending a signal including:
  • the source centralized unit sends a first reconfiguration message to the integrated access and backhaul nodes
  • the source centralized unit sends a second reconfiguration message to the wireless device, wherein, in the second reconfiguration message, a target candidate cell with the same identity as the current serving cell of the integrated access and backhaul node is selected. Configure once.
  • the sub-nodes and/or terminal devices under the IAB-node can be made to apply the configuration in the second reconfiguration message, so as to reconfigure the IAB-node. configured for proper communication with the IAB-donor.
  • Fig. 1 is a schematic diagram of IAB topology
  • FIG. 2 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a method for receiving and transmitting a signal according to an embodiment of the first aspect of the present application
  • Fig. 4 is another schematic diagram of the signal receiving and sending method of the present application.
  • Fig. 5 is a flowchart when IAB-node 3 performs inter-CU migration
  • Fig. 6 is another flowchart when IAB-node 3 performs inter-CU migration
  • FIG. 7 is a schematic diagram of a method for receiving a signal in an embodiment of the second aspect
  • FIG. 8 is a schematic diagram of a method for sending a signal in an embodiment of the third aspect
  • FIG. 9 is another schematic diagram of a method for sending a signal in an embodiment of the third aspect.
  • FIG. 10 is another schematic diagram of a method for sending a signal in an embodiment of the third aspect
  • FIG. 11 is a schematic diagram of an apparatus for receiving and transmitting a signal according to an embodiment of the fourth aspect of the present application.
  • FIG. 12 is a schematic diagram of a signal receiving apparatus according to an embodiment of the fifth aspect of the present application.
  • FIG. 13 is a schematic diagram of an apparatus for transmitting a signal according to an embodiment of the sixth aspect of the present application.
  • FIG. 14 is another schematic diagram of an apparatus for sending a signal according to an embodiment of the sixth aspect of the present application.
  • FIG. 15 is another schematic diagram of an apparatus for sending a signal according to an embodiment of the sixth aspect of the present application.
  • FIG. 16 is a schematic diagram of the composition of an integrated access and backhaul node IAB-node according to an embodiment of the seventh aspect of the present application.
  • FIG. 17 is a schematic structural diagram of a terminal device according to an embodiment of the seventh aspect of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of numelation, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having”, etc. refer to the presence of stated features, elements, elements or components, but do not preclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” may refer to a network that conforms to any of the following communication standards, such as New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to communication protocols at any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G , New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network devices may include, but are not limited to, the following devices: Integrated Access and Backhaul Node (IAB-node), Base Station (BS, Base Station), Access Point (AP, Access Point), Transmission Reception Point (TRP, Transmission Reception) Point), broadcast transmitter, Mobile Management Entity (MME, Mobile Management Entity), gateway, server, Radio Network Controller (RNC, Radio Network Controller), Base Station Controller (BSC, Base Station Controller) and so on.
  • IAB-node Integrated Access and Backhaul Node
  • BS Base Station
  • AP Access Point
  • TRP Transmission Reception Point
  • MME Mobile Management Entity
  • gateway server
  • Radio Network Controller Radio Network Controller
  • BSC Base Station Controller
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include a remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low power node (eg femeto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low power node eg femeto, pico, etc.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "User Equipment” (UE, User Equipment) or “Terminal Equipment” (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services.
  • a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, and the like.
  • the terminal device may include but is not limited to the following devices: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication device
  • handheld device machine type communication device
  • laptop computer Cordless phones, smartphones, smart watches, digital cameras, and more.
  • the terminal device may also be a machine or device that performs monitoring or measurement, such as but not limited to: Machine Type Communication (MTC, Machine Type Communication) terminals, In-vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station, and may also include one or more network devices as described above.
  • user side or “terminal side” or “terminal device side” refers to the side of a user or terminal, which may be a certain UE, or may include one or more terminal devices as above.
  • uplink control signal and “uplink control information (UCI, Uplink Control Information)” or “physical uplink control channel (PUCCH, Physical Uplink Control Channel)” can be used interchangeably without causing confusion.
  • uplink data signal and “uplink data information” or “physical uplink shared channel (PUSCH, Physical Uplink Shared Channel)” can be interchanged;
  • downlink control signal and “downlink control information (DCI, Downlink Control Information)” or “physical downlink control channel (PDCCH, Physical Downlink Control Channel)” are interchangeable, and the terms “downlink data signal” and “downlink data information” Or “Physical Downlink Shared Channel (PDSCH, Physical Downlink Shared Channel)” can be interchanged.
  • DCI Downlink Control Information
  • PDCCH Physical Downlink Control Channel
  • sending or receiving PUSCH can be understood as sending or receiving uplink data carried by PUSCH
  • sending or receiving PUCCH can be understood as sending or receiving uplink information carried by PUCCH
  • sending or receiving PRACH can be understood as sending or receiving data carried by PRACH preamble
  • uplink signals may include uplink data signals and/or uplink control signals, etc., and may also be referred to as uplink transmission (UL transmission) or uplink information or uplink channel.
  • Sending the uplink transmission on the uplink resource can be understood as using the uplink resource to send the uplink transmission.
  • downlink data/signal/channel/information can be understood accordingly.
  • the high-level signaling may be, for example, Radio Resource Control (RRC) signaling; for example, it is called an RRC message (RRC message), for example, including MIB, system information (system information), and dedicated RRC message; RRC IE (RRC information element).
  • RRC Radio Resource Control
  • the high-layer signaling can also be, for example, MAC (Medium Access Control) signaling; or called MAC CE (MAC control element).
  • MAC Medium Access Control
  • MAC CE MAC control element
  • the UE/descendent IAB-node may need to update the security key due to the change of the IAB-donor CU.
  • any IAB-node similar to normal UEs, CHO or conditional reconfiguration will benefit the robustness of an IAB-node's inter-donor migration. Furthermore, when an IAB-node triggers a migration from a parent IAB-node to another parent IAB-node under a different IAB-donor, the migrated IAB-node can no longer receive calls to its UE or child IAB-node The data packets of the node, including handover command (handover command or RRC reconfiguration with reconfiguration with sync) or RRC reconfiguration (RRC reconfiguration), so these child IAB-nodes can trigger migration by using CHO. Otherwise, the migrated IAB-node may need to wait for its UE or child IAB-node to complete the migration before performing the migration, which will take a long time and may increase the risk of handover failure caused by too late handover.
  • handover command handover command or RRC reconfiguration with reconfiguration with sync
  • RRC reconfiguration R
  • the UE when the UE receives the RRC reconfiguration (carrying reconfiguration with sync) message, it starts to perform the handover process.
  • the network configures the condition (condExecutionCond) corresponding to one or more candidate target cells (SpCell) of the UE and the corresponding conditional RRC reconfiguration (condRRCReconfig) in the conditional reconfiguration.
  • the UE evaluates the conditions corresponding to each configured candidate target cell. If a condition corresponding to a target candidate cell (ie, a measurement event) is satisfied, the UE initiates a conditional reconfiguration to that cell, applying the conditional reconfiguration associated with the cell.
  • the RRC reconfiguration message of conditional switching or reconfiguration includes ConditionalReconfiguration IE (conditional reconfiguration), ConditionalReconfiguration IE includes condReconfigToAddModList IE (conditional reconfiguration add modification list), which includes one or more CondReconfigToAddMod (conditional reconfiguration add modification list) ). As shown in Table 1 below.
  • a CondReconfigToAddMod IE includes condReconfigId (conditional reconfiguration identifier), condExecutionCond (conditional), and condRRCReconfig (conditional RRC reconfiguration).
  • condRRCReconfig includes relevant information of the target candidate cell, such as physical cell identity (PCI), frequency, and so on.
  • FIG. 2 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates a situation that an IAB-node performs migration (migration) in an IAB topology structure.
  • IAB-node 3 is initially connected to IAB-node 1 and the source (Source) IAB-donor.
  • IAB-node 3 For purposes such as load balancing, IAB-node 3 needs to be migrated to IAB-node 2 (ie, IAB -The parent node of node 3 is changed from IAB-node 1 to IAB-node 2), IAB-node 2 is connected to the target (Target) IAB-donor, and the Target IAB-donor and the Source IAB-donor are different central units (CU) .
  • the migration process of IAB-node 3 can use handover (handover or RRC reconfiguration with reconfiguration with sync) or conditional handover (CHO) or other reconfigurations.
  • Source IAB-donor and Target IAB-donor can communicate through Xn interface.
  • intra-CU migration intra-CU migration
  • IAB-node 2 and IAB-node 1 in FIG. 2 are both child nodes of Source IAB-donor .
  • an IAB-node when migrated from one parent node to another parent node, if the child nodes and/or terminal devices under the IAB-node cannot be reconfigured in time, these child nodes will be affected and/or communication between the terminal device and the IAB-donor or IAB-CU.
  • the physical cell identity (PCI) and frequency of the cell served by IAB-node 3 may remain unchanged, If the terminal equipment UE1, UE2 and IAB-node 4 served by IAB-node 3 are still under the coverage of the original cell, then the connection relationship between UE1, UE2 and IAB-node 4 and IAB-node 3 and between UE3 and IAB-node 4 The connection relationship between them can remain unchanged.
  • PCI physical cell identity
  • the network configures CHO for UE1, UE2, UE3 and IAB-node 4, the measurement events included in the conditional reconfiguration for UE1, UE2, UE3 and IAB-node 4 even if IAB-node 3 migrates It may also not be satisfied (because the current serving cell quality may change little, or there may be no neighbor cell to meet the measurement event), then UE1, UE2, UE3 and IAB-node 4 will not initiate handover or reconfiguration process to update the encryption. key and other operations, so UE1, UE2, UE3 and IAB-node 4 may fail to communicate with the new CU (located at Target IAB-donor).
  • UE1, UE2, UE3 and IAB-node 4 under IAB-node 3 may not be able to communicate with CU correctly due to the migration of IAB-node 3, for example, the CU has been updated Configure the PDCP layer of UE1, UE2, UE3 or IAB-node 4 or update the configuration of the DU of IAB-node 3, etc. Therefore, it is also necessary to make UE1, UE2, UE3 and IAB-node 4 initiate a handover or reconfiguration process to Update configuration to communicate properly with CU and/or IAB-node 3.
  • embodiments of the present application provide a method for receiving and sending signals.
  • the method for receiving and sending signals of the embodiment of the first aspect of the present application will be described from the side of the IAB-node 3 in FIG. 2 . It should be pointed out that the method for receiving and sending signals in the embodiment of the first aspect of the present application is not limited to the scenario of inter-CU migration, and the method is also applicable to the scenario of intra-CU migration.
  • FIG. 3 is a schematic diagram of a method for receiving and transmitting a signal according to an embodiment of the present application. As shown in FIG. 3 , the method includes:
  • the integrated access and backhaul node (ie, IAB-node 3) receives the first reconfiguration message
  • the integrated access and backhaul node sends indication information to the wireless device, where the indication information is used to instruct the wireless device to apply the configuration in the second reconfiguration message.
  • the IAB-node receives the first reconfiguration message, and sends indication information to the wireless device to enable the wireless device to apply the configuration in the second reconfiguration message, so that the wireless device can perform handover or reconfiguration configuration.
  • the integrated access and backhaul node (ie, IAB-node 3) in operation 301 may be a migrated IAB-node, or a reconfigured IAB-node (eg, the IAB-node's related parameters are reconfigured, or no migration is required), or the IAB-node of the connected CU is changed, or the IAB-node for security configuration (such as updating security keys, etc.), where the IAB-node can be IAB-MT.
  • the first reconfiguration message in operation 301 may be a reconfiguration message received by the parent node IAB-node 1 of IAB-node 3 from the Source IAB-donor and forwarded to IAB-node 3, such as , the first reconfiguration message is a radio resource control reconfiguration (RRC Reconfiguration) message, which may or may not carry reconfiguration with sync, or the radio resource control reconfiguration (RRC Reconfiguration) message includes conditional reconfiguration or CHO.
  • RRC Reconfiguration radio resource control reconfiguration
  • IAB-node 3 performs the handover process or migration process to the target cell.
  • IAB-node 3 performs the reconfiguration process.
  • the IAB-node 3 evaluates whether a specific condition is met, and executes the conditional reconfiguration or CHO to the corresponding target cell when the condition is met, and in the RRC Reconfiguration message includes security information (eg key configuration), IAB-node 3 performs security-related configuration.
  • security information eg key configuration
  • the wireless device in operation 302 may be a terminal device served by IAB-node 3, for example, the wireless device may be UE1, UE2 served by IAB-node 3 in FIG. 2, or an IAB-node 3
  • the next-level integrated access and backhaul node or downlink (downstream) IAB-node or sub-IAB-node, etc., for example, the wireless device may be the downlink IAB-node 4 of the IAB-node 3 in FIG. 2 .
  • the second reconfiguration message may be a radio resource control reconfiguration (RRC Reconfiguration) message, such as a conditional RRC Reconfiguration message.
  • RRC Reconfiguration radio resource control reconfiguration
  • the timing for the IAB-node 3 to send the indication information to the wireless device is one of the following timings:
  • the IAB-node 3 determines that the measurement event related to the conditional reconfiguration is satisfied; for example, the measurement The event can be an A3 event (the quality of the neighboring cell is better than the serving cell by an offset value) or an A5 event (the quality of the serving cell is lower than one threshold, and the quality of the neighboring cell is higher than another threshold);
  • IAB-node 3 When IAB-node 3 receives the first reconfiguration message, for example, it receives the RRC reconfiguration message;
  • the source set unit is, for example, Source IAB-donar in Figure 2
  • the source parent node is, for example, Figure 2 IAB-node 1;
  • the IAB-node 3 When the IAB-node 3 is synchronized with the new parent node or the target parent node (target parent IAB-node) downlink, for example, the SSB of the cell under the new parent node or the target parent node is detected;
  • IAB-node 3 initiates a random access process to a new parent node or target parent node (target parent IAB-node)
  • the new parent node or target parent node is, for example, IAB-node 2 of FIG. 2 , for example, Initiating the random access process may be initializing the random access process or selecting random access resources or sending random access preambles or sending message A (MSG A), etc.;
  • IAB-node 3 sends a reconfiguration complete (for example, RRC reconfiguration complete) message based on the first reconfiguration message to the new parent node or target parent node (parent IAB-node);
  • a reconfiguration complete for example, RRC reconfiguration complete
  • the random access process of IAB-node 3 is successful, for example, the random access process of IAB-node 3 to the new parent node or target parent node (parent IAB-node) is successful, such as receiving a random access response or successful contention resolution Or received message B (MSG B), etc.;
  • MSG B contention resolution Or received message B
  • IAB-node 3 When IAB-node 3 receives an acknowledgement message or feedback message for a reconfiguration complete (eg, RRC reconfiguration complete) message from its new parent node (parent IAB-node), where the acknowledgement message is, for example, a radio link control (RLC) layer acknowledgement message, such as a Hybrid Automatic Repeat Request (HARQ) feedback message.
  • RLC radio link control
  • HARQ Hybrid Automatic Repeat Request
  • the indication information sent in operation 302 enables or disables the wireless device: applying the configuration in the second reconfiguration message, or initiating execution of conditional reconfiguration, or performing migration, or changing the CU, or the like.
  • Source IAB-donor or Source CU can send a handover request message to Target IAB-donor or Target CU, which carries, for example, the context of all terminal devices , contexts of all IAB-MTs, contexts of all IAB-DUs, backhaul and topology-related information and IP address information, etc.
  • the terminal device it may include information such as the physical cell identity (PCI) of the source cell where the terminal device (eg, UE1, UE2) is located, and in the context of IAB-MT, it may include the location where the IAB-node (eg, IAB-node 4) is located.
  • PCI physical cell identity
  • the Target IAB-donor or Target CU After receiving the handover request, the Target IAB-donor or Target CU sends a handover request confirmation message to the Source IAB-donor or Source CU, which may include the configuration corresponding to the PCI of the source cell of the terminal device and/or the source of the IAB-node. The configuration corresponding to the PCI of the cell. After the Source IAB-donor or Source CU receives the configuration, it can set the conditions corresponding to the cell, and the conditions and configurations corresponding to the cell are included in the transmission to the wireless device (ie the current wireless device UE1, UE2 or IAB-node 4). The second reconfiguration message.
  • the wireless device ie the current wireless device UE1, UE2 or IAB-node 4
  • the second reconfiguration message for example, in ServingCellConfigCommon included in reconfigurationWithSync
  • IAB-node 3 serving the UE or the cell of the downlink IAB-node (ie, currently the wireless device UE1
  • a target candidate cell with the same identity serving cell of UE2, UE3 or IAB-node 4
  • the identification may be a PCI or a cell ID (cell ID) or a cell global identifier (CGI) or a cell global identifier (ECGI) or the like.
  • the indication information enables the wireless device to apply the configuration of the target candidate cell with the same identity as the current serving cell in the second reconfiguration message.
  • the wireless device eg, UE1, UE2, UE3 or IAB-node 4
  • the wireless device eg, UE1, UE2, UE3 or IAB-node 3
  • the applied condRRCReconfig is the current serving cell of this IAB-node 3.
  • the condRRCReconfig corresponding to the PCI that is, the physical cell identifier (PCI) indicated in the ServingCellConfigCommon included in the reconfigurationWithSync in the RRC reconfiguration message is condRRCReconfig of the physical cell identifier of the current serving cell.
  • PCI physical cell identifier
  • the present application may not be limited thereto, in at least some embodiments, in the second reconfiguration message (for example, in the ServingCellConfigCommon included in reconfigurationWithSync), the cell with the IAB-node 3 serving the UE or the downlink IAB-node (ie, currently serving cell of wireless device UE1, UE2 or IAB-node 4) target candidate cells with the same identity are configured more than twice (ie, appear more than twice) or are not configured (ie, do not appear).
  • the indication information in operation 302 indicates information of a centralized unit (CU), where the centralized unit refers to a centralized unit to which the IAB-node 3 is about to connect or has been connected based on the first reconfiguration message, for example, In the case of inter-CU migration, the centralized unit may be the CU of the Target IAB-donor in FIG. 2 .
  • CU centralized unit
  • the information of the centralized unit includes at least one of the following information: the identifier of the centralized unit; the index of the centralized unit; the Internet Protocol (IP) address and/or the network device identifier (gNB Identifier (gNB ID) of the centralized unit ))) at least a part (for example, the most significant bit MSB or the least significant bit LSB); the cell identity (Cell identity) of the unit in the set or at least a part of the cell identity (for example, the most significant bit MSBs of the Cell identity); the set At least part of the unit's Public Land Mobile Network Identity Information (PLMN-IdentityInfo); at least part of the Common Gateway Interface (CGI).
  • IP Internet Protocol
  • gNB ID network device identifier
  • PLMN-IdentityInfo Public Land Mobile Network Identity Information
  • the second reconfiguration message may include information of the centralized unit and a configuration corresponding to the information of the centralized unit.
  • the wireless device for example, UE1, UE2 or IAB-node 4
  • the wireless device can information, use the configuration corresponding to the information of the centralized unit in the second reconfiguration message, and apply the configuration.
  • the indication information may indicate a configuration applied by the wireless device (eg, condRRCReconfig).
  • the IAB-node 3 since the RRC function is located in the IAB-donor CU, the IAB-node has no RRC function, so the migrated IAB-node 3 cannot resolve the wireless devices under the IAB-node 3 (for example, UE1, UE2, UE3 or IAB-node 4) The configuration in the received second reconfiguration message. Therefore, the IAB-node 3 can determine the configuration (for example, condRRCReconfig) applied by the wireless device through the corresponding relationship indication information, and then indicate the determined configuration to the wireless device.
  • the configuration for example, condRRCReconfig
  • the data receiving and sending method may further include:
  • the IAB-node 3 receives the corresponding relationship indication information.
  • the corresponding relationship indication information in operation 303 is used to indicate:
  • the configured identification information for example, CondReconfigId or MeasId, etc.
  • the corresponding relationship indication information in operation 303 is used to indicate:
  • the node 3 may receive an F1-C message (for example, UE Context Modification Request), and the F1-C message includes the corresponding relationship indication information.
  • F1-C message for example, UE Context Modification Request
  • operation 301, operation 302, and operation 303 may not be limited to that shown in FIG. 3.
  • operation 303 may also precede operation 301 or operation 302; or, operation 303 may also be included in operation 301.
  • the IAB-nide 3 simultaneously receives the first reconfiguration message and the corresponding relationship indication information.
  • the IAB-node 3 may return an adaptive protocol data unit (BAP PDU), a radio link layer control protocol data unit (RLC PDU), a medium access control control information element (MAC CE), medium access control subheader (MAC subheader) or physical layer signaling sends indication information to the wireless device (for example, UE1, UE2, UE3 or IAB-node 4).
  • BAP PDU adaptive protocol data unit
  • RLC PDU radio link layer control protocol data unit
  • MAC CE medium access control control information element
  • MAC subheader medium access control subheader
  • physical layer signaling sends indication information to the wireless device (for example, UE1, UE2, UE3 or IAB-node 4).
  • a new backhaul adaptive control protocol data unit may be defined for sending the indication information, for example, the BAP control PDU may use a new PDU type to identify it for sending
  • the indication information and/or the BAP control PDU may contain 8-bit, 16-bit, or 24-bit CU information.
  • the format of the BAP control PDU may be as shown in Table 2 below.
  • the D/C field is 1 bit, indicating whether the corresponding BAP PDU is a BAP data PDU or a BAP control PDU
  • the PDU type is, for example, 3 bits, indicating the type of control information included in the BAP control PDU.
  • R is a reserved bit.
  • the format of the BAP control PDU may also be as shown in Table 3 below.
  • the BAP control PDU in addition to the fields shown in Table 2, the BAP control PDU also includes CU information, such as CU ID.
  • the CU ID shown in Table 3 is 8 bits.
  • the CU ID can also be 16 bits or 24 bits. Bit etc.
  • a new radio link layer control control protocol data unit may be defined for transmitting the indication information, for example, the RLC control PDU may use a new Control PDU Type (CPT) to Identifies that it is used to send the indication information, and/or, the BAP control PDU may contain 8-bit or 16-bit or 24-bit CU information;
  • CPT Control PDU Type
  • a new medium access control control information element may be defined for sending the indication information, and the MAC CE may correspond to a new logical channel identifier (LCID in subheader) located in the subheader ), for example, when the indication information includes CU information, the MAC CE may include 8bit or 16bit or 24bit CU information, and the MAC CE may also be 8bit or 16bit or 24bit in length;
  • LCID in subheader new logical channel identifier
  • the medium access control subheader may have a new LCID that can be used to send the indication information, eg, in the case where the indication information is used to instruct the wireless device to enable the configuration in the second reconfiguration
  • the wireless device receives the MAC subheader containing the LCID, and applies the configuration in the second reconfiguration;
  • the physical layer signaling may be a field in downlink control information (DCI), the one field in the DCI is used to send the indication information, and the one field in the DCI may be, for example, a group common DCI (group DCI).
  • group DCI common DCI
  • common DCI common DCI
  • common DCI common DCI
  • common DCI common DCI
  • UE-specific DCI terminal device-specific DCI
  • the DCI may A field of 1 bit is added to send the indication information.
  • the DCI may also be a paging DCI (paging DCI).
  • the method for receiving and sending the signal may further include:
  • the integrated access and backhaul node further forwards the second reconfiguration message to the wireless device.
  • IAB-node 3 may receive the second reconfiguration message from Source IAB-donar and forward the second reconfiguration message to the wireless device (eg, UE1, UE2, UE3, or IAB-node 4).
  • the wireless device eg, UE1, UE2, UE3, or IAB-node 4
  • operation 301, operation 302, operation 303, and operation 304 may not be limited to that shown in FIG. 3.
  • operation 304 may also precede operation 301 or operation 302 or operation 303; or, operation 304 may also be is included in operation 301 or operation 303 .
  • FIG. 4 is another schematic diagram of the signal receiving and transmitting method of the present application. The difference between the method shown in FIG. 4 and the method shown in FIG. 3 is that FIG. 4 does not have operation 304 , but has operations 305 and 306 .
  • the integrated access and backhaul node stores the second reconfiguration message
  • the integrated access and backhaul node sends the second reconfiguration message to the wireless device.
  • the IAB-node 3 stores the received second reconfiguration message, and sends the second reconfiguration message to the wireless device (for example, UE1, UE2, UE3 or IAB-node 4).
  • the wireless device for example, UE1, UE2, UE3 or IAB-node 4.
  • operation 301, operation 302, operation 303, operation 305, and operation 306 may not be limited to that shown in FIG. 4, for example: operation 305 and operation 306 may also be before operation 301 or operation 302 or operation 303; Alternatively, operation 305 precedes operation 301 or operation 302 and operation 306 is included in operation 302 .
  • the occasion when the IAB-node 3 sends the second reconfiguration message to the wireless device may be one of the following occasions:
  • the IAB-node 3 determines that the measurement event related to the conditional reconfiguration is satisfied, for example, the measurement
  • the event can be an A3 event (the quality of the neighboring cell is better than the serving cell by an offset value) or an A5 event (the quality of the serving cell is lower than one threshold, and the quality of the neighboring cell is higher than another threshold);
  • IAB-node 3 When IAB-node 3 receives the first reconfiguration message, for example, it receives the RRC reconfiguration message;
  • the source set unit is, for example, Source IAB-donar in Figure 2
  • the source parent node is, for example, Figure 2 IAB-node 1;
  • the IAB-node 3 When the IAB-node 3 is synchronized with the new parent node or the target parent node (target parent IAB-node) downlink, for example, the SSB of the cell under the new parent node or the target parent node is detected;
  • IAB-node 3 initiates a random access process to a new parent node or target parent node (target parent IAB-node)
  • the new parent node or target parent node is, for example, the IAB-node 2 of FIG. 2; for example, Initiating the random access process may be initializing the random access process or selecting random access resources or sending random access preambles or sending message A (MSG A), etc.;
  • IAB-node 3 sends a reconfiguration complete (for example, RRC reconfiguration complete) message based on the first reconfiguration message to the new parent node or target parent node (parent IAB-node);
  • a reconfiguration complete for example, RRC reconfiguration complete
  • the random access process of IAB-node 3 is successful, for example, the random access process of IAB-node 3 to the new parent node or target parent node (parent IAB-node) is successful, such as receiving a random access response or successful contention resolution Or received message B (MSG B), etc.;
  • MSG B contention resolution Or received message B
  • the IAB-node 3 When the IAB-node 3 receives an acknowledgement message or feedback message for the reconfiguration complete (eg, RRC reconfiguration complete) message from its new parent node (parent IAB-node), where the acknowledgement message is, for example, a radio link control (RLC) layer acknowledgement message, such as a Hybrid Automatic Repeat Request (HARQ) feedback message.
  • RLC radio link control
  • HARQ Hybrid Automatic Repeat Request
  • the timing at which the IAB-node 3 sends the second reconfiguration message to the wireless device may be the same as the timing at which the IAB-node 3 sends the indication information to the wireless device, that is, the IAB-node 3 simultaneously sends the reconfiguration message to the wireless device.
  • the wireless device sends the second reconfiguration message and the indication information, or includes the second reconfiguration message and the indication information in one message. Thereby, transmission resources can be saved.
  • the timing at which the IAB-node 3 sends the second reconfiguration message to the wireless device may also be different from the timing at which the IAB-node 3 sends the indication information to the wireless device.
  • the timing is more flexible.
  • Fig. 5 is a flowchart when IAB-node 3 performs inter-CU migration. As shown in Figure 5, the process includes the following operations:
  • the Source IAB donor makes a conditional switch decision (CHO decision) for UE1, UE2 and/or IAB-node 4, and makes a migration decision for IAB-node 3.
  • CHO decision conditional switch decision
  • IAB-MT IAB-node
  • the Source IAB donor sends a Handover Request to the Target IAB donor
  • the target parent node IAB-node 2 of IAB-node 3 for example, the request is a terminal device context setup request (UE context setup req);
  • IAB-node 2 sends a response to the request of operation 3, which is, for example, a terminal device context setup response (UE context setup resp);
  • Target IAB donor sends a handover request confirmation message to Source IAB donor, for example, handover Request Acknowledge;
  • the Source IAB donor sends a request to the IAB-node 3, which is, for example, a terminal device context modification request (UE context modification req), which may include second configuration information, such as RRC Reconfiguration;
  • UE context modification req terminal device context modification request
  • RRC Reconfiguration second configuration information
  • IAB-node 3 forwards the second configuration information (for example, RRC Reconfiguration) to the wireless device (for example, UE1, UE2 or IAB-node 4), operation 7 corresponds to operation 304 of FIG. 3;
  • the wireless device for example, UE1, UE2 or IAB-node 4
  • the IAB-node 3 sends a response to the Source IAB donor, which is, for example, a terminal device context modification response (UE context modification resp);
  • UE context modification resp a terminal device context modification response
  • the wireless device (eg, UE1, UE2 or IAB-node 4) sends a second configuration complete message, such as RRC reconfiguration complete, to IAB-node 3;
  • the IAB-node 3 sends an uplink radio resource control message transfer message, such as UL RRC Message Transfer, to the Source IAB donor.
  • an uplink radio resource control message transfer message such as UL RRC Message Transfer
  • the IAB-node 3 can perform the conditional switching (CHO) shown in 11A or the switching (HO) shown in 11B.
  • condition switching (CHO) shown in 11A includes the following operations:
  • Source IAB donor sends a request to IAB-node 3 source parent node IAB-node 1, for example, the request is UE context modification req;
  • IAB-node 1 sends first configuration information to IAB-node 3, where the first configuration information is, for example, RRC Reconfiguration;
  • IAB-node 1 sends a response to the Source IAB donor, which is, for example, a UE context modification response (UE context modification resp);
  • IAB-node 3 sends a first configuration information reception completion response to IAB-node 1, the first configuration complete message, such as RRC reconfiguration complete;
  • IAB-node 1 sends an uplink radio resource control message transfer message (UL RRC Message Transfer) to the Source IAB donor;
  • UL RRC Message Transfer uplink radio resource control message transfer message
  • 16a.IAB-node 3 evaluates the switching condition (Evaluate HO condition).
  • the handover (HO) shown in 11B includes the following operations:
  • Source IAB donor sends a request to IAB-node 3 source parent node IAB-node 1, the request is, for example, a UE context modification request (UE context modification req);
  • IAB-node 1 sends first configuration information to IAB-node 3, where the first configuration information is, for example, RRC Reconfiguration;
  • the IAB-node 1 sends a response to the Source IAB donor, which is, for example, a UE context modification response (UE context modification resp).
  • UE context modification resp UE context modification resp
  • the migration process also includes the following operations:
  • IAB-node 3 sends first configuration information configuration completion information to new parent node IAB-node 2, and this first configuration information configuration completion information can be, for example, RRC reconfiguration complete;
  • IAB-node 2 sends an uplink radio resource control message transfer message (UL RRC Message Transfer) to Target IAB-donor;
  • UL RRC Message Transfer uplink radio resource control message transfer message
  • the IAB-node 3 may send indication information to the wireless device (eg, UE1, UE2 or IAB-node 4) at one of multiple occasions, for example, the occasion shown in 15a is the IAB-node 3 determination condition
  • the timing shown in 15b is when the IAB-node 3 sends the reconfiguration based on the first reconfiguration message, wherein the indication information enables or prohibits the wireless device from applying the second reconfiguration.
  • the configuration in the message, or the indication information indicates the information of the Target IAB donor (Target CU);
  • the wireless device evaluates the handover condition (Evaluate HO condition);
  • the wireless device receives the indication information, it applies the configuration in the second configuration information, and sends the second configuration information to IAB-node 3 after the application configuration is completed Configuration complete information, for example, RRC reconfiguration complete.
  • Target IAB donor sends a request to IAB-node 3, which is, for example, a terminal device context setup request (UE context setup req);
  • IAB-node 3 sends a response to the Target IAB donor for the request of operation 3a, and the response is, for example, a terminal device context setup response (UE context setup resp);
  • UE context setup resp terminal device context setup response
  • IAB-node 3 sends an uplink radio resource control message transfer message (UL RRC Message Transfer) to the Target IAB donor, and the UL RRC message transfer may include information for wireless devices (for example, UE1, UE2 or IAB-node 4)
  • the second configuration information of the configuration complete information (RRC reconfiguration complete for UE/descent IAB nodes).
  • FIG. 6 is another flowchart when IAB-node 3 performs inter-CU migration. As shown in Figure 6, the process includes the following operations:
  • the Source IAB donor makes a conditional switch decision (CHO decision) for UE1, UE2 and/or IAB-node 4, and makes a migration decision for IAB-node 3.
  • conditional switch decision CHO decision
  • IAB-node 3 and its serviced UE and/or IAB-node migrate to Target IAB donor;
  • the Source IAB donor sends a Handover Request to the Target IAB donor
  • the target parent node IAB-node 2 of IAB-node 3 for example, the request is a terminal device context setup request (UE context setup req);
  • IAB-node 2 sends a response to the request of operation 3, which is, for example, a terminal device context setup response (UE context setup resp);
  • Target IAB donor sends a handover request confirmation message to Source IAB donor, for example, handover Request Acknowledge;
  • the Source IAB donor sends a request to the IAB-node 3, which is, for example, a terminal device context modification request (UE context modification req), which may include second configuration information, such as RRC Reconfiguration;
  • UE context modification req terminal device context modification request
  • RRC Reconfiguration second configuration information
  • the IAB-node stores the second configuration information, corresponding to operation 305 in FIG. 4;
  • the IAB-node 3 sends a response to the Source IAB donor, which is, for example, a terminal device context modification response (UE context modification resp);
  • UE context modification resp a terminal device context modification response
  • the IAB-node 3 can perform the conditional switching (CHO) shown in 9A or the switching (HO) shown in 9B.
  • the description of the conditional switching (CHO) shown in 9A is the same as the description of the conditional switching (CHO) shown in 11A of FIG.
  • the description of the handover (HO) shown is the same.
  • the migration process also includes the following operations:
  • IAB-node 3 sends first configuration information configuration completion information to new parent node IAB-node 2, and this first configuration information configuration completion information can be, for example, RRC reconfiguration complete;
  • IAB-node 2 sends an uplink radio resource control message transfer message (UL RRC Message Transfer) to Target IAB-donor;
  • UL RRC Message Transfer uplink radio resource control message transfer message
  • IAB-node 3 may send indication information to the wireless device (eg, UE1, UE2 or IAB-node 4) at one of multiple occasions, for example, the timing of operation 13 shown in FIG. 6 is IAB-node 3
  • the IAB-node 3 also sends the second configuration information (RRC Reconfiguration) in operation 13, which corresponds to operation 306 in FIG. Operation 13 of 6 corresponds to combining operation 306 and operation 302 of FIG. 4 into one operation; in addition, the present application may not be limited to this, for example, the second configuration information or indication information may be sent at other timings, or the indication information and the second configuration information may not be sent at the same time;
  • the wireless device (for example, UE1, UE2 or IAB-node 4) applies the configuration in the second configuration information in the case of receiving the indication information, and sends the second configuration information to the IAB-node 3 after the application configuration is completed Configuration complete information, for example, RRC reconfiguration complete.
  • Configuration complete information for example, RRC reconfiguration complete.
  • the wireless device UE or IAB-node (eg UE1, UE2 or IAB-node 4) under the IAB-node (eg IAB-node 3) that is migrating or preparing to migrate also Configurations from the new IAB-donor, such as security key-related configuration, can be applied for proper communication with the new IAB-donor, and the scheme is less complex and has less impact on current standards; furthermore,
  • the method of the embodiment of the first aspect of the present application can also be used for processing, so that the wireless device UE or IAB under the IAB-node (for example, IAB-node 3) that is to be migrated or to be migrated -node (eg UE1, UE2 or IAB-node 4) to apply the new configuration in time.
  • the embodiment of the second aspect of the present application provides a method for receiving a signal, which corresponds to the method of the embodiment of the first aspect.
  • the wireless equipment includes: terminal equipment, for example, UE1, UE2; or, the next-level integrated access and backhaul node of IAB-node 3, IAB-node 4.
  • FIG. 7 is a schematic diagram of a method for receiving a signal in an embodiment of the second aspect. As shown in FIG. 7 , the method includes:
  • the wireless device receives a second reconfiguration message
  • Operation 702 The wireless device receives indication information, where the indication information is used to instruct the wireless device to apply the configuration in the received second reconfiguration message at the Radio Resource Control (RRC) layer.
  • RRC Radio Resource Control
  • FIG. 7 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of each operation can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the description of the above-mentioned FIG. 7 .
  • the timing for the wireless device to receive the indication information sent by IAB-node 3 is one of the following timings:
  • the IAB-node 3 determines that the measurement event related to the conditional reconfiguration is satisfied, for example, the measurement
  • the event can be an A3 event (the quality of the neighboring cell is better than the serving cell by an offset value) or an A5 event (the quality of the serving cell is lower than one threshold, and the quality of the neighboring cell is higher than another threshold);
  • IAB-node 3 When IAB-node 3 receives the first reconfiguration message, for example, it receives the RRC reconfiguration message;
  • the source set unit is, for example, Source IAB-donar in Figure 2
  • the source parent node is, for example, Figure 2 IAB-node 1;
  • IAB-node 3 When IAB-node 3 synchronizes with the new parent node or target parent node (target parent IAB-node) downlink, for example, the SSB of the cell under the new parent node or the target parent node is detected; IAB-node 3 initiates to the new parent node During the random access process of the node or target parent node (target parent IAB-node), the new parent node or target parent node is, for example, IAB-node 2 in FIG. Access process or selection of random access resources or random access preamble sending or message A (MSG A) sending, etc.;
  • IAB-node 3 sends a reconfiguration complete (for example, RRC reconfiguration complete) message based on the first reconfiguration message to the new parent node or target parent node (parent IAB-node);
  • a reconfiguration complete for example, RRC reconfiguration complete
  • the random access process of IAB-node 3 is successful, for example, the random access process of IAB-node 3 to the new parent node or target parent node (parent IAB-node) is successful, such as receiving a random access response or successful contention resolution Or received message B (MSG B), etc.;
  • MSG B contention resolution Or received message B
  • IAB-node 3 When IAB-node 3 receives an acknowledgement message or feedback message for a reconfiguration complete (eg, RRC reconfiguration complete) message from its new parent node (parent IAB-node), where the acknowledgement message is, for example, a radio link control (RLC) layer acknowledgement message, such as a Hybrid Automatic Repeat Request (HARQ) feedback message.
  • RLC radio link control
  • HARQ Hybrid Automatic Repeat Request
  • the wireless device can return adaptive protocol data unit (BAP PDU), radio link layer control protocol data unit (RLC PDU), medium access control control cell (MAC CE), medium access
  • BAP PDU adaptive protocol data unit
  • RLC PDU radio link layer control protocol data unit
  • MAC CE medium access control control cell
  • the indication information is received by the control subheader (MAC subheader) or physical layer signaling.
  • the indication information enables or disables the wireless device to: apply the configuration in the second reconfiguration message at the Radio Resource Control (RRC) layer, or initiate execution of conditional reconfiguration, or perform migration, or change CU et al.
  • RRC Radio Resource Control
  • the cell with the same identity as the cell of the IAB-node 3 serving the UE or the downlink IAB-node that is, the current serving cell of the wireless device UE1, UE2, UE3 or the IAB-node 4
  • the target candidate cell is configured once or appears once.
  • the identification may be a PCI or a cell ID (cell ID) or a cell global identifier (CGI) or a cell global identifier (ECGI) or the like.
  • the wireless device applies the configuration of the target candidate cell with the same identity as the current serving cell in the second reconfiguration message at the Radio Resource Control (RRC) layer.
  • RRC Radio Resource Control
  • the present application may not be limited thereto, in at least some embodiments, in the second reconfiguration message (for example, in the ServingCellConfigCommon included in reconfigurationWithSync), the cell with the IAB-node 3 serving the UE or the downlink IAB-node (ie, currently serving cell of wireless device UE1, UE2 or IAB-node 4) target candidate cells with the same identity are configured more than twice (ie, appear more than twice) or are not configured (ie, do not appear).
  • the indication information indicates information of a centralized unit (CU), where the centralized unit refers to a centralized unit that the IAB-node 3 will connect or has connected to based on the first reconfiguration message, for example, FIG. 2 Target IAB donor in .
  • CU centralized unit
  • the information of the centralized unit includes at least one of the following information: the identifier of the centralized unit; the index of the centralized unit; the Internet Protocol (IP) address and/or the network device identifier (gNB Identifier (gNB ID) of the centralized unit ))) at least a part (for example, the most significant bit MSB or the least significant bit LSB); the cell identity (Cell identity) of the unit in the set or at least a part of the cell identity (for example, the most significant bit MSBs of the Cell identity); the set At least part of the unit's Public Land Mobile Network Identity Information (PLMN-IdentityInfo); at least part of the Common Gateway Interface (CGI).
  • IP Internet Protocol
  • gNB ID network device identifier
  • PLMN-IdentityInfo Public Land Mobile Network Identity Information
  • the second reconfiguration message includes information of the centralized unit and a configuration corresponding to the information of the centralized unit
  • the wireless device determines the first reconfiguration according to the information of the centralized unit in the indication information
  • the configuration corresponding to the information of the centralized unit in the dual configuration message is applied, and the configuration is applied at the Radio Resource Control (RRC) layer of the wireless device.
  • RRC Radio Resource Control
  • the indication information may indicate a configuration applied by the wireless device (eg, condRRCReconfig).
  • the configured identification information in the second reconfiguration message has a corresponding relationship with the identification information (for example, PCI) of the target cell in the first reconfiguration message; or, the second reconfiguration message (conditional RRC reconfiguration)
  • the configured identification information in the RRC reconfiguration has a corresponding relationship with the configured identification information in the first reconfiguration message; or, the target cell and the configured identification information included in the second configuration message (conditional RRC reconfiguration) (CondReconfigId) or configuration (condRRCReconfig) has a corresponding relationship.
  • the wireless device receives the second reconfiguration message from the Source IAB-donor forwarded by the IAB-node 3.
  • the IAB-node 3 receives the second reconfiguration message from the Source IAB-donor and stores it, and sends the stored second reconfiguration message to the wireless device at an appropriate time .
  • the opportunity for the wireless device to receive the second reconfiguration message sent by the IAB-node 3 is one of the following:
  • the IAB-node 3 determines that the measurement event related to the conditional reconfiguration is satisfied, for example, the measurement
  • the event can be an A3 event (the quality of the neighboring cell is better than the serving cell by an offset value) or an A5 event (the quality of the serving cell is lower than one threshold, and the quality of the neighboring cell is higher than another threshold);
  • IAB-node 3 When IAB-node 3 receives the first reconfiguration message, for example, it receives the RRC reconfiguration message;
  • the source set unit is, for example, Source IAB-donar in Figure 2
  • the source parent node is, for example, Figure 2 IAB-node 1;
  • the IAB-node 3 When the IAB-node 3 is synchronized with the new parent node or the target parent node (target parent IAB-node) downlink, for example, the SSB of the cell under the new parent node or the target parent node is detected;
  • IAB-node 3 initiates a random access process to a new parent node or target parent node (target parent IAB-node)
  • the new parent node or target parent node is, for example, the IAB-node 2 of FIG. 2; for example, Initiating the random access process may be initializing the random access process or selecting random access resources or sending random access preambles or sending message A (MSG A), etc.;
  • IAB-node 3 sends a reconfiguration complete (for example, RRC reconfiguration complete) message based on the first reconfiguration message to the new parent node or target parent node (parent IAB-node);
  • a reconfiguration complete for example, RRC reconfiguration complete
  • the random access process of IAB-node 3 is successful, for example, the random access process of IAB-node 3 to the new parent node or target parent node (parent IAB-node) is successful, such as receiving a random access response or successful contention resolution Or received message B (MSG B), etc.;
  • MSG B contention resolution Or received message B
  • IAB-node 3 When IAB-node 3 receives an acknowledgement message or feedback message for a reconfiguration complete (eg, RRC reconfiguration complete) message from its new parent node (parent IAB-node), where the acknowledgement message is, for example, a radio link control (RLC) layer acknowledgement message, such as a Hybrid Automatic Repeat Request (HARQ) feedback message.
  • RLC radio link control
  • HARQ Hybrid Automatic Repeat Request
  • the wireless device receives the second reconfiguration message and the indication information from the IAB-node 3 at the same time; in addition, the wireless device may not receive the second reconfiguration message and the indication information at the same time.
  • a wireless device under a migrated or ready-to-migrate IAB-node (eg, IAB-node 3) can be in time at the RRC layer
  • Apply the configuration in the second reconfiguration message such as the configuration related to the security key, for correct communication with the new IAB-donor, and the scheme is less complex and has less impact on the current standard; in addition, for In the scenario of intra-CU migration, the method of the embodiment of the second aspect of the present application is also applicable, so that the wireless devices (eg, UE1, UE2) under the migrated or ready-to-migrate IAB-node (eg, IAB-node 3) or IAB-node 4) to apply the new configuration in time.
  • the embodiment of the third aspect of the present application provides a method for sending a signal, which corresponds to the method of the embodiment of the first aspect.
  • the method for sending a signal according to the embodiment of the third aspect of the present application will be described from the side of the source centralized unit (Source IAB-donor) in FIG. 2 .
  • the signal sending method of the embodiment of the third aspect of the present application is not limited to the scenario of inter-CU migration, the method is also applicable to the scenario of intra-CU migration, Source IAB-donor and IAB-node 3
  • the interactive process can refer to Figure 5 or Figure 6.
  • FIG. 8 is a schematic diagram of a method for sending a signal in an embodiment of the third aspect. As shown in FIG. 8 , the method includes:
  • the source centralized unit sends a first reconfiguration message to the integrated access and backhaul node
  • Operation 802 The source centralized unit sends a second reconfiguration message to the wireless device, wherein, in the second reconfiguration message, a target candidate cell with the same identity as the current serving cell of the integrated access and backhaul node is configured once.
  • FIG. 9 is another schematic diagram of a method for sending a signal in an embodiment of the third aspect. As shown in FIG. 9 , the method includes:
  • the source centralized unit sends a first reconfiguration message to the integrated access and backhaul node
  • the source centralized unit sends a second reconfiguration message to the wireless device, where the second reconfiguration message includes information of the target centralized unit and the configuration corresponding to the information of the target centralized unit.
  • FIG. 10 is another schematic diagram of a method for sending a signal in an embodiment of the third aspect. As shown in FIG. 10 , the method includes:
  • the source centralized unit sends a first reconfiguration message to the integrated access and backhaul node
  • the source centralized unit sends a second reconfiguration message to the wireless device.
  • Operation 1003 Send corresponding relationship indication information to the integrated access and backhaul node.
  • the corresponding relationship indication information in operation 1003 is used to indicate: the identification information of the configuration in the second reconfiguration message (conditional RRC reconfiguration) and the identification information of the target cell in the first reconfiguration message (for example, PCI); the correspondence between the configured identification information in the second reconfiguration message (conditional RRC reconfiguration) and the configured identification information in the first reconfiguration message; the target cell and the second configuration
  • the integrated access and backhaul node is, for example, IAB-node 3 of Fig. 2;
  • the wireless device is, for example, UE1, UE2 or IAB-node 4 of Fig. 2;
  • the target centralized unit refers to The IAB-node 3 is about to connect or has already connected the centralized unit based on the first reconfiguration message, e.g. Target IAB-donor of Figure 2).
  • a wireless device under a migrated or ready-to-migrate IAB-node (eg, IAB-node3) can be in RRC in a timely manner
  • the layer applies the configuration in the second reconfiguration message, such as the configuration related to the security key, in order to communicate correctly with the new IAB-donor, and the complexity of the scheme is lower and has less impact on the current standard; moreover,
  • the methods of the embodiments of the third aspect of the present application are also applicable, so that wireless devices (eg, UE1, UE2 or IAB-node 4) applies the new configuration in time.
  • Embodiments of the present application provide a signal receiving and transmitting apparatus.
  • the device may be, for example, an integrated access and backhaul node, or may be one or some components or components configured in the integrated access and backhaul node.
  • the integrated access and backhaul node is, for example, the one shown in FIG. 2 .
  • the apparatus corresponds to an embodiment of the first aspect.
  • FIG. 11 is a schematic diagram of an apparatus for receiving and transmitting signals according to an embodiment of the present application. As shown in FIG. 11 , an apparatus for receiving and transmitting signals 1100 includes:
  • a first receiving unit 1101 which receives a first reconfiguration message
  • the first sending unit 1102 sends indication information to the wireless device, where the indication information is used to instruct the wireless device to apply the configuration in the second reconfiguration message.
  • the wireless device includes: terminal equipment, for example, UE1-UE3 in FIG. 2; or, the next-level integrated access and backhaul node IAB-node 4 of the integrated access and backhaul node.
  • the timing when the first sending unit 1102 sends the indication information to the wireless device is one of the following timings:
  • the IAB-node 3 determines that the measurement event related to the conditional reconfiguration is satisfied, for example, the measurement
  • the event can be an A3 event (the quality of the neighboring cell is better than the serving cell by an offset value) or an A5 event (the quality of the serving cell is lower than one threshold, and the quality of the neighboring cell is higher than another threshold);
  • IAB-node 3 When IAB-node 3 receives the first reconfiguration message, for example, it receives the RRC reconfiguration message;
  • the source set unit is, for example, Source IAB-donar in Figure 2
  • the source parent node is, for example, Figure 2 IAB-node 1;
  • the IAB-node 3 When the IAB-node 3 is synchronized with the new parent node or the target parent node (target parent IAB-node) downlink, for example, the SSB of the cell under the new parent node or the target parent node is detected;
  • IAB-node 3 initiates a random access process to a new parent node or target parent node (target parent IAB-node)
  • the new parent node or target parent node is, for example, the IAB-node 2 of FIG. 2; for example, Initiating the random access process may be initializing the random access process or selecting random access resources or sending random access preambles or sending message A (MSG A), etc.;
  • IAB-node 3 sends a reconfiguration complete (for example, RRC reconfiguration complete) message based on the first reconfiguration message to the new parent node or target parent node (parent IAB-node);
  • a reconfiguration complete for example, RRC reconfiguration complete
  • the random access process of IAB-node 3 is successful, for example, the random access process of IAB-node 3 to the new parent node or target parent node (parent IAB-node) is successful, such as receiving a random access response or successful contention resolution Or received message B (MSG B), etc.;
  • MSG B contention resolution Or received message B
  • IAB-node 3 When IAB-node 3 receives an acknowledgement message or feedback message for a reconfiguration complete (eg, RRC reconfiguration complete) message from its new parent node (parent IAB-node), where the acknowledgement message is, for example, a radio link control (RLC) layer acknowledgement message, such as a Hybrid Automatic Repeat Request (HARQ) feedback message.
  • RLC radio link control
  • HARQ Hybrid Automatic Repeat Request
  • the indication information enables or disables the wireless device: apply the configuration in the second reconfiguration message, or perform migration, or change the CU, or the like.
  • the target candidate cell with the same identity as the cell of the IAB-node 3 serving the UE or the downlink IAB-node (that is, the current serving cell of the wireless device UE1, UE2, UE3 or IAB-node 4) is configured once or appears once .
  • the identification may be a PCI or a cell ID (cell ID) or a cell global identifier (CGI) or a cell global identifier (ECGI) or the like.
  • the indication information enables the wireless device to apply the configuration of the target candidate cell with the same identity as the current serving cell in the second reconfiguration message.
  • the present application may not be limited thereto, in at least some embodiments, in the second reconfiguration message (for example, in the ServingCellConfigCommon included in reconfigurationWithSync), the cell with the IAB-node 3 serving the UE or the downlink IAB-node (ie, currently serving cell of wireless device UE1, UE2 or IAB-node 4) target candidate cells with the same identity are configured more than twice (ie, appear more than twice) or are not configured (ie, do not appear).
  • the indication information indicates the information of the centralized unit, wherein the centralized unit refers to the centralized unit to which the integrated access and backhaul node is about to connect or has been connected based on the first reconfiguration message, for example, the centralized unit shown in FIG. 2 Target IAB-node.
  • the second reconfiguration message includes the information of the centralized unit and the configuration corresponding to the information of the centralized unit.
  • the indication information may indicate the configuration of the wireless device application.
  • the signal receiving and transmitting apparatus 1100 may further include:
  • the second receiving unit 1103 receives the corresponding relationship indication information.
  • the corresponding relationship indication information is used to indicate: the corresponding relationship between the configured identification information in the second reconfiguration message and the identification information of the target cell in the first reconfiguration message; or, the configured identification information in the second reconfiguration message The corresponding relationship between the identification information and the configured identification information in the first reconfiguration message; or, the corresponding relationship between the target cell and the configured identification information or configuration included in the second reconfiguration message.
  • the signal receiving and transmitting apparatus 1100 further includes:
  • a second sending unit 1104 which forwards the second reconfiguration message to the wireless device.
  • the signal receiving and transmitting apparatus 1100 further includes:
  • a storage unit 1105 that stores the second reconfiguration message
  • a third sending unit 1106 sends a second reconfiguration message to the wireless device to the integrated access and backhaul node.
  • the timing for the third sending unit 1106 to send the second reconfiguration message to the wireless device is one of the following timings:
  • the IAB-node 3 determines that the measurement event related to the conditional reconfiguration is satisfied, for example, the measurement
  • the event can be an A3 event (the quality of the neighboring cell is better than the serving cell by an offset value) or an A5 event (the quality of the serving cell is lower than one threshold, and the quality of the neighboring cell is higher than another threshold);
  • IAB-node 3 When IAB-node 3 receives the first reconfiguration message, for example, it receives the RRC reconfiguration message;
  • the source set unit is, for example, Source IAB-donar in Figure 2
  • the source parent node is, for example, Figure 2 IAB-node 1;
  • the IAB-node 3 When the IAB-node 3 is synchronized with the new parent node or the target parent node (target parent IAB-node) downlink, for example, the SSB of the cell under the new parent node or the target parent node is detected;
  • IAB-node 3 initiates a random access process to a new parent node or target parent node (target parent IAB-node)
  • the new parent node or target parent node is, for example, the IAB-node 2 of FIG. 2; for example, Initiating the random access process may be initializing the random access process or selecting random access resources or sending random access preambles or sending message A (MSG A), etc.;
  • IAB-node 3 sends a reconfiguration complete (for example, RRC reconfiguration complete) message based on the first reconfiguration message to the new parent node or target parent node (parent IAB-node);
  • a reconfiguration complete for example, RRC reconfiguration complete
  • the random access process of IAB-node 3 is successful, for example, the random access process of IAB-node 3 to the new parent node or target parent node (parent IAB-node) is successful, such as receiving a random access response or successful contention resolution Or received message B (MSG B), etc.;
  • MSG B contention resolution Or received message B
  • IAB-node 3 When IAB-node 3 receives an acknowledgement message or feedback message for a reconfiguration complete (eg, RRC reconfiguration complete) message from its new parent node (parent IAB-node), where the acknowledgement message is, for example, a radio link control (RLC) layer acknowledgement message, such as a Hybrid Automatic Repeat Request (HARQ) feedback message.
  • RLC radio link control
  • HARQ Hybrid Automatic Repeat Request
  • the signal receiving and sending apparatus 1100 may use the second sending unit 1104 to forward the second reconfiguration message, or use the storage unit 1105 and the third sending unit 1106 to store and send the second reconfiguration message.
  • the signal receiving and sending apparatus 1100 sends the second reconfiguration message and the indication information to the wireless device at the same time
  • the third sending unit 1106 and the first sending unit 1102 send the second reconfiguration message and the indication information at the same time, or combine the second reconfiguration message and the indication information into one message, and the third sending unit 1106 or the first A sending unit 1102 sends.
  • the apparatus 1100 for receiving and sending a signal may not send the second reconfiguration message and the indication information at the same time.
  • the signal receiving and transmitting apparatus 1100 only exemplarily shows the connection relationship or signal direction between the various components or modules, but it should be clear to those skilled in the art that various bus connections, etc. may be used. related technologies.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • An embodiment of the present application provides a signal receiving apparatus.
  • the apparatus may be, for example, a wireless device, or may be some or some components or components configured in the wireless device, for example, the wireless device is UE1, UE2, or IAB-node 4 in FIG. 2 .
  • the apparatus for receiving the signal corresponds to the embodiment of the second aspect.
  • FIG. 12 is a schematic diagram of a signal receiving apparatus according to an embodiment of the present application. As shown in FIG. 12 , the signal receiving apparatus 1200 includes:
  • a receiving unit 1201 which receives the second reconfiguration message
  • the third receiving unit 1202 is configured to receive indication information, where the indication information is used to indicate the configuration of the wireless device in the second reconfiguration message received by the radio resource control layer application.
  • the timing for the third receiving unit 1202 to receive the indication information sent by the integrated access and backhaul node is one of the following timings:
  • the IAB-node 3 determines that the measurement event related to the conditional reconfiguration is satisfied, for example, the measurement
  • the event can be an A3 event (the quality of the neighboring cell is better than the serving cell by an offset value) or an A5 event (the quality of the serving cell is lower than one threshold, and the quality of the neighboring cell is higher than another threshold);
  • IAB-node 3 When IAB-node 3 receives the first reconfiguration message, for example, it receives the RRC reconfiguration message;
  • the source set unit is, for example, Source IAB-donar in Figure 2
  • the source parent node is, for example, Figure 2 IAB-node 1;
  • the IAB-node 3 When the IAB-node 3 is synchronized with the new parent node or the target parent node (target parent IAB-node) downlink, for example, the SSB of the cell under the new parent node or the target parent node is detected;
  • IAB-node 3 initiates a random access process to a new parent node or target parent node (target parent IAB-node)
  • the new parent node or target parent node is, for example, the IAB-node 2 of FIG. 2; for example, Initiating the random access process may be initializing the random access process or selecting random access resources or sending random access preambles or sending message A (MSG A), etc.;
  • IAB-node 3 sends a reconfiguration complete (for example, RRC reconfiguration complete) message based on the first reconfiguration message to the new parent node or target parent node (parent IAB-node);
  • a reconfiguration complete for example, RRC reconfiguration complete
  • the random access process of IAB-node 3 is successful, for example, the random access process of IAB-node 3 to the new parent node or target parent node (parent IAB-node) is successful, such as receiving a random access response or successful contention resolution Or received message B (MSG B), etc.;
  • MSG B contention resolution Or received message B
  • IAB-node 3 When IAB-node 3 receives an acknowledgement message or feedback message for a reconfiguration complete (eg, RRC reconfiguration complete) message from its new parent node (parent IAB-node), where the acknowledgement message is, for example, a radio link control (RLC) layer acknowledgement message, such as a Hybrid Automatic Repeat Request (HARQ) feedback message.
  • RLC radio link control
  • HARQ Hybrid Automatic Repeat Request
  • the third receiving unit 1202 receives the indication information by returning an adaptive protocol data unit, a radio link layer control protocol data unit, a medium access control control information element, a medium access control subheader or physical layer signaling.
  • the indication information enables or disables the wireless device to apply the configuration in the second reconfiguration message at the radio resource control layer.
  • the cell with the same identity as the cell of the IAB-node 3 serving the UE or the downlink IAB-node that is, the current serving cell of the wireless device UE1, UE2, UE3 or the IAB-node 4
  • the target candidate cell is configured once or appears once.
  • the identification may be a PCI or a cell ID (cell ID) or a cell global identifier (CGI) or a cell global identifier (ECGI) or the like.
  • the wireless device applies, at the radio resource control layer, the configuration of the target candidate cell with the same identity as the current serving cell in the second reconfiguration message.
  • the present application may not be limited thereto, in at least some embodiments, in the second reconfiguration message (for example, in the ServingCellConfigCommon included in reconfigurationWithSync), the cell with the IAB-node 3 serving the UE or the downlink IAB-node (ie, currently serving cell of wireless device UE1, UE2 or IAB-node 4) target candidate cells with the same identity are configured more than twice (ie, appear more than twice) or are not configured (ie, do not appear).
  • the indication information indicates information of a centralized unit
  • the centralized unit refers to a centralized unit to which the integrated access and backhaul node will connect or has been connected based on the first reconfiguration message, for example, FIG. 2 Target IAB donor in .
  • the second reconfiguration message includes the information of the centralized unit and the configuration corresponding to the information of the centralized unit.
  • the information of the centralized unit corresponds to the configuration, and the configuration is applied at the radio resource control layer.
  • the indication information indicates the configuration applied by the wireless device.
  • the configured identification information in the second reconfiguration message has a corresponding relationship with the identification information of the target cell in the first reconfiguration message; or, the configured identification information in the second reconfiguration message and the The identification information of the configuration in the first reconfiguration message has a corresponding relationship; or, the target cell has a corresponding relationship with the identification information of the configuration or the configuration included in the second reconfiguration message.
  • the timing at which the receiving unit 1201 receives the second reconfiguration message sent by the integrated access and backhaul node is one of the following timings:
  • the measurement event can be an A3 event (the quality of the neighboring cell is better than the serving cell by an offset value) or an A5 event (the quality of the serving cell is low) At one threshold, the quality of neighboring cells is higher than another threshold);
  • IAB-node 3 When IAB-node 3 receives the first reconfiguration message, for example, it receives the RRC reconfiguration message;
  • the source set unit is, for example, Source IAB-donar in Figure 2
  • the source parent node is, for example, Figure 2 IAB-node 1;
  • the IAB-node 3 When the IAB-node 3 is synchronized with the new parent node or the target parent node (target parent IAB-node) downlink, for example, the SSB of the cell under the new parent node or the target parent node is detected;
  • IAB-node 3 initiates a random access process to a new parent node or target parent node (target parent IAB-node)
  • the new parent node or target parent node is, for example, the IAB-node 2 of FIG. 2; for example, Initiating the random access process may be initializing the random access process or selecting random access resources or sending random access preambles or sending message A (MSG A), etc.;
  • IAB-node 3 sends a reconfiguration complete (for example, RRC reconfiguration complete) message based on the first reconfiguration message to the new parent node or target parent node (parent IAB-node);
  • a reconfiguration complete for example, RRC reconfiguration complete
  • the random access process of IAB-node 3 is successful, for example, the random access process of IAB-node 3 to the new parent node or target parent node (parent IAB-node) is successful, such as receiving a random access response or successful contention resolution Or received message B (MSG B), etc.;
  • MSG B contention resolution Or received message B
  • IAB-node 3 When IAB-node 3 receives an acknowledgement message or feedback message for a reconfiguration complete (eg, RRC reconfiguration complete) message from its new parent node (parent IAB-node), where the acknowledgement message is, for example, a radio link control (RLC) layer acknowledgement message, such as a Hybrid Automatic Repeat Request (HARQ) feedback message.
  • RLC radio link control
  • HARQ Hybrid Automatic Repeat Request
  • the signal receiving apparatus 1200 simultaneously receives the second reconfiguration message and the indication information from the integrated access and backhaul node.
  • the timing at which the receiving unit 1201 receives the second reconfiguration message is the same as the timing at which the third receiving unit 1202 receives the indication information, or, the second reconfiguration message and the indication information are combined into one message and sent through the receiving unit 1201 or the third The receiving unit 1202 receives the message.
  • the apparatus 1200 for receiving the signal may not simultaneously receive the second reconfiguration message and the indication information.
  • the signal receiving apparatus 1200 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used .
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • An embodiment of the present application provides a signal sending apparatus.
  • the apparatus may be, for example, a source concentration unit, or may be some or some components or components configured in the source concentration unit, and the source concentration unit is, for example, the Source IAB donor in FIG. 2 .
  • the signal transmitting apparatus corresponds to the embodiment of the third aspect.
  • FIG. 13 is a schematic diagram of a signal sending apparatus according to an embodiment of the present application. As shown in FIG. 13 , the signal sending apparatus 1300 includes:
  • a fourth sending unit 1301 that sends a first reconfiguration message to the integrated access and backhaul node
  • a fifth sending unit 1302 which sends a second reconfiguration message to the wireless device.
  • a target candidate cell with the same identity as the current serving cell of the integrated access and backhaul node is configured once.
  • FIG. 14 is another schematic diagram of an apparatus for sending a signal according to an embodiment of the present application.
  • the apparatus 1400 for sending a signal includes:
  • a seventh sending unit 1402 which sends a second reconfiguration message to the wireless device, where the second reconfiguration message includes the information of the target centralized unit and the configuration corresponding to the information of the target centralized unit, the target centralized unit A unit refers to a centralized unit to which the integrated access and backhaul node is about to connect or has connected based on the first reconfiguration message.
  • FIG. 15 is another schematic diagram of a signal sending apparatus according to an embodiment of the present application. As shown in FIG. 15 , the signal sending apparatus 1500 includes:
  • an eighth sending unit 1501 which sends a first reconfiguration message to the integrated access and backhaul node
  • a ninth sending unit 1502 that sends a second reconfiguration message to the wireless device.
  • the tenth sending unit 1503 which sends the corresponding relationship indication information to the integrated access and backhaul nodes.
  • the corresponding relationship indication information is used to indicate:
  • the corresponding relationship between the configured identification information in the second reconfiguration message and the identification information of the target cell in the first reconfiguration message; or, the configured identification in the second reconfiguration message The corresponding relationship between the information and the configured identification information in the first reconfiguration message; or, the corresponding relationship between the target cell and the configured identification information or the configuration included in the second reconfiguration message.
  • the integrated access and backhaul node is, for example, IAB-node 3 of Fig. 2;
  • the wireless device is, for example, UE1, UE2 or IAB-node 4 of Fig. 2;
  • the target centralized unit refers to The IAB-node 3 is about to connect or has already connected the centralized unit based on the first reconfiguration message, e.g. Target IAB-donor of Figure 2).
  • the signal sending apparatus 1300, 1400 or 1500 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that bus connections and the like may be used. various related technologies.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • An embodiment of the present application further provides a communication system, and reference may be made to FIG. 1 , and the same contents as those of the embodiments of the first aspect to the sixth aspect will not be repeated.
  • the communication system may include:
  • a source concentration unit which includes the signal transmitting apparatus 1300, 1400 or 1500 according to the embodiment of the sixth aspect;
  • a wireless device comprising the signal receiving apparatus 1200 according to the embodiment of the fifth aspect.
  • An integrated access and backhaul node comprising the signal receiving and sending apparatus 1100 according to the embodiment of the fourth aspect.
  • the embodiment of the present application also provides an integrated access and backhaul node, but the present application is not limited to this, and may also be other devices.
  • FIG. 16 is a schematic structural diagram of an integrated access and backhaul node IAB-node according to an embodiment of the present application.
  • the IAB-node 1600 may include: a processor 1610 (eg, a central processing unit CPU) and a memory 1620; the memory 1620 is coupled to the processor 1610.
  • the memory 1620 can store various data; in addition, the program 1630 for information processing is also stored, and the program 1630 is executed under the control of the processor 1610 .
  • the IAB-node 1600 may be a source centralized unit (eg, source IAB-donor in FIG. 2 ), a next-level IAB-node in the wireless device, or IAB-node 3 in FIG. 2 .
  • the processor 1610 may be configured to execute a program to implement the method as described in the embodiments of the first aspect, the second aspect or the third aspect.
  • the network device 1600 may further include: a transceiver 1640, an antenna 1650, etc.; wherein, the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the network device 1600 does not necessarily include all the components shown in FIG. 16 ; in addition, the network device 1600 may also include components not shown in FIG. 16 , and reference may be made to the prior art.
  • the embodiment of the present application also provides a terminal device, but the present application is not limited to this, and may also be other devices.
  • FIG. 17 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 1700 may include a processor 1710 and a memory 1720 ; the memory 1720 stores data and programs, and is coupled to the processor 1710 .
  • this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
  • the terminal device 1700 may be at least one of UE1, UE2, UE3 in the wireless device.
  • the processor 1710 may be configured to execute a program to implement the method as described in the embodiments of the second aspect.
  • the terminal device 1700 may further include: a communication module 1730 , an input unit 1740 , a display 1750 , and a power supply 1760 .
  • the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the terminal device 1700 does not necessarily include all the components shown in FIG. 17 , and the above components are not required; in addition, the terminal device 1700 may also include components not shown in FIG. 17 . There is technology.
  • An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the signal receiving method according to the embodiment of the second aspect.
  • An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program causes a terminal device to execute the signal receiving method according to the embodiment of the second aspect.
  • the embodiment of the present application further provides a computer program, wherein when the program is executed in an IAB-node, the program causes the IAB-node to execute the method described in the embodiment of the first or third aspect.
  • the embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program causes the IAB-node to execute the method described in the embodiment of the first or third aspect.
  • the apparatuses and methods above in the present application may be implemented by hardware, or may be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by logic components, enables the logic components to implement the above-described apparatus or constituent components, or causes the logic components to implement the above-described various methods or steps.
  • the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, and the like.
  • the method/apparatus described in conjunction with the embodiments of this application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams shown in the figures and/or one or more combinations of the functional block diagrams may correspond to either software modules or hardware modules of the computer program flow.
  • These software modules may respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by, for example, solidifying these software modules using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • the functional blocks and/or one or more combinations of the functional blocks described in the figures can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to the figures can also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors processor, one or more microprocessors in communication with the DSP, or any other such configuration.
  • a method for receiving and transmitting a signal comprising:
  • the integrated access and backhaul node receives the first reconfiguration message
  • the integrated access and backhaul node sends indication information to the wireless device, where the indication information is used to instruct the wireless device to apply the configuration in the second reconfiguration message.
  • the timing when the integrated access and backhaul node sends the indication information to the wireless device is one of the following timings:
  • the indication information enables or disables the wireless device:
  • the configuration in the second reconfiguration message is applied.
  • a target candidate cell with the same identity as the current serving cell of the integrated access and backhaul node is configured once.
  • the indication information enables the wireless device to apply the configuration of the target candidate cell with the same identity as the current serving cell in the second reconfiguration message.
  • the indication information indicates the information of the centralized unit
  • the centralized unit refers to a centralized unit to which the integrated access and backhaul node is about to connect or has been connected based on the first reconfiguration message.
  • the second reconfiguration message includes the information of the centralized unit and the configuration corresponding to the information of the centralized unit.
  • the indication information indicates the configuration applied by the wireless device.
  • the corresponding relationship indication information is used to indicate:
  • the integrated access and backhaul node sends back an adaptive protocol data unit, a radio link layer control protocol data unit, a medium access control control cell, a medium access control subheader or physical layer signaling to the
  • the wireless device sends the indication information.
  • the integrated access and backhaul node also forwards the second reconfiguration message to the wireless device.
  • the integrated access and backhaul node stores the second reconfiguration message
  • the integrated access and backhaul node sends the second reconfiguration message to the wireless device.
  • the timing when the integrated access and backhaul node sends the second reconfiguration message to the wireless device is one of the following timings:
  • the integrated access and backhaul node simultaneously sends the second reconfiguration message and the indication information to the wireless device.
  • the wireless device is:
  • the integrated access and backhaul node is the next level integrated access and backhaul node.
  • a method for receiving a signal comprising:
  • the wireless device receives the second reconfiguration message
  • the wireless device receives the indication information
  • the indication information is used for the configuration of the wireless device in the second reconfiguration message received by the radio resource control layer application.
  • the timing at which the wireless device receives the indication information sent by the integrated access and backhaul node is one of the following timings:
  • the indication information enables or disables the wireless device:
  • the configuration in the second reconfiguration message is applied at the radio resource control layer.
  • a target candidate cell with the same identity as the current serving cell of the integrated access and backhaul node is configured once.
  • the wireless device applies, at the radio resource control layer, the configuration of the target candidate cell with the same identity as the current serving cell in the second reconfiguration message.
  • the indication information indicates the information of the centralized unit
  • the centralized unit refers to a centralized unit to which the integrated access and backhaul node is about to connect or has been connected based on the first reconfiguration message.
  • the second reconfiguration message includes the information of the centralized unit and the configuration corresponding to the information of the centralized unit,
  • the wireless device determines, according to the information of the centralized unit in the indication information, the configuration corresponding to the information of the centralized unit in the second reconfiguration message, and applies the configuration at the radio resource control layer .
  • the indication information indicates the configuration applied by the wireless device.
  • the configured identification information in the second reconfiguration message has a corresponding relationship with the identification information of the target cell in the first reconfiguration message
  • the configured identification information in the second reconfiguration message has a corresponding relationship with the configured identification information in the first reconfiguration message
  • the target cell has a corresponding relationship with the configuration identification information or the configuration included in the second reconfiguration message.
  • the wireless device receives the indication information by returning an adaptive protocol data unit, a radio link layer control protocol data unit, a medium access control control information element, a medium access control subheader or physical layer signaling.
  • the timing at which the wireless device receives the second reconfiguration message sent by the integrated access and backhaul node is one of the following timings:
  • the wireless device receives the second reconfiguration message and the indication information simultaneously from the integrated access and backhaul node.
  • the wireless device is:
  • the integrated access and backhaul node is the next level integrated access and backhaul node.
  • a method for sending a signal comprising:
  • the source centralized unit sends a first reconfiguration message to the integrated access and backhaul nodes
  • the source centralized unit sends a second reconfiguration message to the wireless device
  • a target candidate cell with the same identity as the current serving cell of the integrated access and backhaul node is configured once.
  • a method for sending a signal comprising:
  • the source centralized unit sends a first reconfiguration message to the integrated access and backhaul nodes
  • the source centralized unit sends a second reconfiguration message to the wireless device
  • the second reconfiguration message includes the information of the target centralized unit and the configuration corresponding to the information of the target centralized unit,
  • the target centralized unit refers to the centralized unit to which the integrated access and backhaul node will connect or has connected based on the first reconfiguration message.
  • a method for sending a signal comprising:
  • the source centralized unit sends the first reconfiguration message to the integrated access and backhaul nodes
  • the source centralized unit sends a second reconfiguration message to the wireless device
  • the corresponding relationship indication information is used to indicate:
  • the wireless device is:
  • the integrated access and backhaul node is the next level integrated access and backhaul node.

Abstract

本申请实施例提供一种信号的接收和发送方法、装置和通信系统，该信号的接收和发送装置，设置于集成的接入和回传节点，所述信号的接收和发送装置包括：第一接收单元，其接收第一重配置消息；以及第一发送单元，向无线设备发送指示信息，所述指示信息用于指示所述无线设备应用第二重配置消息中的配置。

Description

信号的接收和发送方法、装置和通信系统 技术领域
本申请实施例涉及通信技术领域。
背景技术
集成的接入和回传(Integrated access and backhaul，IAB)技术使5G RAN支持无线中继。集成的接入和回传节点(IAB-node)支持通过新无线(New Radio，NR)的接入和回传。NR回传在网络侧中终止点被称为IAB-donor，它表示一个具有支持IAB功能的网络设备(例如，gNB)。回传可以通过单跳或多跳发生。
IAB-node支持gNB-DU(distributed unit，分布式单元)的功能，IAB-node DU也被称为IAB-DU，IAB-DU是到终端设备(UE)和下一跳IAB-node的信无线接入(NR access)接口的终点，也是到IAB-donor上的gNB-CU(central unit，中心单元)的F1协议的终点。
除了gNB-DU功能，IAB-node也支持一部分UE的功能，被称为IAB-MT，IAB-MT包括比如物理层、层2、RRC和NAS功能来连接到另一个IAB-node或IAB-donor的gNB-DU、连接到IAB-donor上的gNB-CU和连接到核心网。
在IAB拓扑结构中，IAB-donor下的IAB-node通过一跳或多跳连接到该IAB-donor，该IAB-donor为根节点(root)。
图1是IAB拓扑结构的一个示意图。如图1所示，在IAB拓扑结构10中，IAB-node 100包括IAB-MT功能单元101和IAB-DU功能单元102，IAB-DU功能单元102的接口上的邻节点被称为子节点(child node)，如图1中所示的子节点201、202、203；IAB-MT功能单元101的接口上的邻节点被称为父节点(parent node)，如图1中所示的父节点301、302。
如图1所示，IAB-node 100到子节点201、202、203的方向被称为下游(downstream)方向，IAB-node 100到父节点301、302的方向被称为上游(upstream)方向。IAB-donor(未图示)为该IAB拓扑结构10执行集中式的资源、拓扑和路由管理。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申 请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
本申请的发明人发现，当IAB-node从一个父节点下迁移到另一个父节点下的情况下，如何对该IAB-node下的子节点和/或终端设备进行重新配置，现有技术中并没有涉及。
针对上述问题的至少之一，本申请实施例提供一种信号的接收和发送方法、装置和通信系统，集成的接入和回传节点(IAB-node)接收第一重配置消息，向无线设备发送指示信息以使无线设备应用第二重配置消息中的配置，由此，无线设备能够进行切换或者重配置。
根据本申请实施例的一个方面，提供一种信号的接收和发送装置，设置于集成的接入和回传节点，所述信号的接收和发送装置包括：
第一接收单元，其接收第一重配置消息；以及
第一发送单元，向无线设备发送指示信息，所述指示信息用于指示所述无线设备应用第二重配置消息中的配置。
根据本申请实施例的另一个方面，提供一种信号的接收装置，设置于无线设备，所述信号的接收装置包括：
接收单元，其接收第二重配置消息；以及
第三接收单元，其接收指示信息，
所述指示信息用于指示所述无线设备在无线资源控制层应用接收到的所述第二重配置消息中的配置。
根据本申请实施例的另一个方面，提供一种信号的发送装置，设置于源集中单元，所述信号的发送装置包括：
第四发送单元，其向集成的接入和回传节点发送第一重配置消息；以及
第五发送单元，其向无线设备发送第二重配置消息，其中，在所述第二重配置消息中，与所述集成的接入和回传节点的当前服务小区具有相同标识的目标候选小区被配置一次。
根据本申请实施例的另一个方面，提供一种信号的接收和发送方法，包括：
集成的接入和回传节点接收第一重配置消息；以及
所述集成的接入和回传节点向无线设备发送指示信息，所述指示信息用于指示所述无线设备应用第二重配置消息中的配置。
根据本申请实施例的另一个方面，提供一种信号的接收方法，包括：
无线设备接收第二重配置消息；以及
所述无线设备接收指示信息，所述指示信息用于指示所述无线设备在无线资源控制层应用接收到的所述第二重配置消息中的配置。
根据本申请实施例的另一个方面，提供一种信号的发送方法，包括：
源集中单元向集成的接入和回传节点发送第一重配置消息；以及
所述源集中单元向无线设备发送第二重配置消息，其中，在所述第二重配置消息中，与所述集成的接入和回传节点的当前服务小区具有相同标识的目标候选小区被配置一次。
本申请实施例的有益效果之一在于：对于迁移的或准备迁移的IAB-node，能够使该IAB-node下的子节点和/或终端设备应用第二重配置消息中的配置，从而进行重新配置，以便与IAB-donor进行正确通信。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是IAB拓扑结构的一个示意图；
图2是本申请实施例的通信系统的一个示意图；
图3是本申请第一方面的实施例的信号的接收和发送方法的一示意图；
图4是本申请的信号接收和发送方法的另一示意图；
图5是IAB-node 3进行inter-CU迁移时的一个流程图；
图6是IAB-node 3进行inter-CU迁移时的另一个流程图；
图7是第二方面的实施例中信号的接收方法的一个示意图；
图8是第三方面的实施例中信号的发送方法的一个示意图；
图9是第三方面的实施例中信号的发送方法的另一个示意图；
图10是第三方面的实施例中信号的发送方法的另一个示意图；
图11是本申请第四方面的实施例的信号的接收和发送装置的一示意图；
图12是本申请第五方面的实施例的信号的接收装置的一示意图；
图13是本申请第六方面实施例的信号的发送装置的一示意图；
图14是本申请第六方面实施例的信号的发送装置的另一示意图；
图15是本申请第六方面实施例的信号的发送装置的另一示意图；
图16是本申请第七方面实施例的集成的接入和回传节点IAB-node的构成示意图；
图17是本申请第七方面实施例的终端设备的构成示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根 据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：集成的接入和回传节点(IAB-node)、基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持 设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。
在以下的说明中，在不引起混淆的情况下，术语“上行控制信号”和“上行控制信息(UCI，Uplink Control Information)”或“物理上行控制信道(PUCCH，Physical Uplink Control Channel)”可以互换，术语“上行数据信号”和“上行数据信息”或“物理上行共享信道(PUSCH，Physical Uplink Shared Channel)”可以互换；
术语“下行控制信号”和“下行控制信息(DCI，Downlink Control Information)”或“物理下行控制信道(PDCCH，Physical Downlink Control Channel)”可以互换，术语“下行数据信号”和“下行数据信息”或“物理下行共享信道(PDSCH，Physical Downlink Shared Channel)”可以互换。
另外，发送或接收PUSCH可以理解为发送或接收由PUSCH承载的上行数据，发送或接收PUCCH可以理解为发送或接收由PUCCH承载的上行信息，发送或接收PRACH可以理解为发送或接收由PRACH承载的preamble；上行信号可以包括上行数据信号和/或上行控制信号等，也可以称为上行传输(UL transmission)或上行信息或上行信道。在上行资源上发送上行传输可以理解为使用该上行资源发送该上行传输。类似地，可以相应地理解下行数据/信号/信道/信息。
在本申请实施例中，高层信令例如可以是无线资源控制(RRC)信令；例如称为RRC消息(RRC message)，例如包括MIB、系统信息(system information)、专用RRC消息；或者称为RRC IE(RRC information element)。高层信令例如还可以是MAC(Medium Access Control)信令；或者称为MAC CE(MAC control element)。但本申请不限于此。
3GPP中同意，在IAB节点迁移过程中，假设所有parent-child关系在新的 IAB-donor处被保留。对IAB-MT，如果没有特殊说明，也应当支持Rel-16中引入的条件切换(Conditional Handover，CHO)。
根据所有parent-child关系在新IAB-donor处被保留的假设，一个迁移(migration)的IAB-node和它服务的终端设备(UE)或下级IAB-node(descendent IAB-node或downstream IAB-node或child IAB-node等)的网络拓扑可以在migration之前和之后不改变。这种情况下，UE/descendent IAB-node可能由于IAB-donor CU改变而需要更新安全密钥。
对任何IAB-node，与对正常UE相似，CHO或条件重配置将对一个IAB-node在IAB-donor间迁移(inter-donor migration)的鲁棒性提升有好处。此外，当一个IAB-node触发从一个parent IAB-node到不同IAB-donor下的另一个parent IAB-node的迁移时，该迁移的IAB-node不再能接收到对它的UE或child IAB-node的数据包，包括切换命令(handover command或携带reconfiguration with sync的RRC reconfiguration)或RRC重配置(RRC reconfiguration)，因此这些child IAB-node可以通过使用CHO来触发migration。否则，该迁移的IAB-node可能需要在执行迁移之前等待它的UE或child IAB-node迁移完成，这将花费很长时间，可能增加太晚切换导致的切换失败风险。
在常规切换过程中，UE收到RRC reconfiguration(携带reconfiguration with sync)消息时，就开始执行切换过程。而在Rel-16 CHO中，网络在条件重配置中配置UE一个或更多候选目标小区(SpCell)对应的条件(condExecutionCond)及其对应的条件RRC重配置(condRRCReconfig)。UE评估每个配置的候选目标小区对应的条件。如果一个目标候选小区对应的条件(即测量事件)被满足，那么UE发起到该小区的条件重配置，应用与该小区相关的条件重配置。
条件切换或重配置(reconfiguration)的RRC reconfiguration消息包括ConditionalReconfiguration IE(条件重配置)，ConditionalReconfiguration IE包括condReconfigToAddModList IE(条件重配置增加修改列表)，其中包括1个或更多的CondReconfigToAddMod(条件重配置增加修改)。如下面的表1所示。
表1
Figure PCTCN2020122555-appb-000001
一个CondReconfigToAddMod IE包括condReconfigId(条件重配置标识)、condExecutionCond(条件)和condRRCReconfig(条件RRC重配置)。其中，condRRCReconfig包含目标候选小区的相关信息，例如物理小区标识(PCI)、频率等等。
以下通过示例对本申请实施例的场景进行说明，但本申请不限于此。
图2是本申请实施例的通信系统的一个示意图，示意性说明了在IAB拓扑结构中IAB-node进行迁移(migration)的情况。如图2所示，IAB-node 3最初连接到IAB-node 1和源(Source)IAB-donor，为了比如负载均衡等目的，需要将IAB-node 3迁移到IAB-node 2下(即，IAB-node 3的父节点由IAB-node 1变更为IAB-node 2)，IAB-node 2连接到目标(Target)IAB-donor，Target IAB-donor与Source IAB-donor是不同的中心单元(CU)。IAB-node 3迁移的过程可以使用切换(handover或携带reconfiguration with sync的RRC reconfiguration)或者条件切换(conditional handover，CHO)或者其他的重配置等。此外，Source IAB-donor和Target IAB-donor之间可以通过Xn接口进行通信。
在图2所示的迁移中，IAB-node 3迁移前后的Source IAB-donor和Target IAB-donor不同，因此，该迁移为中心单元间迁移(inter-CU migration)。
在本申请实施例的场景中，也可以是中心单元内的迁移(intra-CU migration)，例如，图2中的IAB-node 2和IAB-node 1都是Source IAB-donor的子节点的情况。
第一方面的实施例
在有些情况下，当IAB-node从一个父节点下迁移到另一个父节点下时，如果对 该IAB-node下的子节点和/或终端设备无法及时地进行重新配置，将影响这些子节点和/或终端设备与IAB-donor或IAB-CU之间的通信。
例如，在图2所示的inter-CU migration的场景下，在IAB-node 3迁移到Target IAB-donor时，IAB-node 3服务的小区的物理小区标识(PCI)和频率可能保持不改变，如果IAB-node 3服务的终端设备UE1、UE2和IAB-node 4仍在原小区的覆盖下，那么UE1、UE2和IAB-node 4与IAB-node 3之间的连接关系以及UE3与IAB-node 4之间的连接关系可以保持不变。如果网络为UE1、UE2、UE3和IAB-node 4配置了CHO，那么即使IAB-node 3发生迁移，对UE1、UE2、UE3和IAB-node 4的条件重配置(conditional reconfiguration)中包括的测量事件也可能不会被满足(因为当前服务小区质量可能变化较小，也可能没有邻小区满足测量事件)，那么UE1、UE2、UE3和IAB-node 4不会发起切换或重配置过程以进行更新密钥等操作，因此UE1、UE2、UE3和IAB-node 4可能与新的CU(位于Target IAB-donor)通信失败。
又例如，在某些intra-CU migration的场景下，IAB-node 3下的UE1、UE2、UE3和IAB-node 4也可能由于IAB-node 3的迁移而无法与CU正确通信，例如CU更新了对UE1、UE2、UE3或IAB-node 4的PDCP层的配置或者更新了IAB-node 3的DU的配置等，因而也需要使UE1、UE2、UE3和IAB-node 4发起切换或重配置过程来更新配置，以便与CU和/或IAB-node 3正确通信。
至少针对该问题，本申请实施例提供一种信号的接收和发送方法。
下面，以图2的inter-CU migration的场景为例，从图2的IAB-node 3一侧来说明本申请第一方面的实施例的信号的接收和发送方法。需要指出的是，本申请的第一方面的实施例的信号的接收和发送方法并不限于inter-CU migration的场景，该方法也适用于intra-CU migration的场景。
图3是本申请实施例的信号的接收和发送方法的一示意图，如图3所示，该方法包括：
操作301、集成的接入和回传节点(即，IAB-node 3)接收第一重配置消息；以及
操作302、该集成的接入和回传节点向无线设备发送指示信息，该指示信息用于指示该无线设备应用第二重配置消息中的配置。
值得注意的是，以上附图3仅对本申请实施例进行了示意性说明，但本申请不限 于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图3的记载。例如：操作301也可以在操作302之后。
根据本申请第一方面的实施例，IAB-node接收第一重配置消息，向无线设备发送指示信息以使无线设备应用第二重配置消息中的配置，由此，无线设备能够进行切换或者重配置。
在至少一个实施例中，操作301中的集成的接入和回传节点(即IAB-node 3)可以是迁移的IAB-node，或者是进行重配置的IAB-node(例如该IAB-node的相关参数被重配置，也可以不执行迁移)，或者是改变连接的CU的IAB-node，或者是进行安全配置(例如更新安全密钥等)的IAB-node等，这里的IAB-node可以是IAB-MT。
在至少一个实施例中，操作301中的第一重配置消息可以是由IAB-node 3的父节点IAB-node 1从Source IAB-donor接收到而转发给IAB-node 3的重配置消息，例如，第一重配置消息是无线资源控制重配置(RRC Reconfiguration)消息，其中可以携带reconfiguration with sync，也可以不携带reconfiguration with sync，或者该无线资源控制重配置(RRC Reconfiguration)消息包括条件重配置或CHO。在RRC Reconfiguration消息携带reconfiguration with sync的情况下，IAB-node 3执行到目标小区的切换过程或迁移过程，在RRC Reconfiguration消息不携带reconfiguration with sync的情况下，IAB-node 3执行重配置过程，在RRC Reconfiguration消息包括条件重配置或CHO的情况下，IAB-node 3评估是否满足特定的条件，在满足条件时执行到对应的目标小区的条件重配置或CHO，在RRC Reconfiguration消息包括安全信息(例如密钥配置)的情况下，IAB-node 3执行安全相关的配置。此外，需要说明的是，在至少一个实施例中，图2所示的IAB-node 3在收到第一重配置消息的情况下，IAB-node 3可以最终完成迁移，也可以不完成迁移。
在至少一个实施例中，操作302中的无线设备可以是IAB-node 3服务的终端设备，例如，该无线设备可以是图2中IAB-node 3服务的UE1、UE2，或者是IAB-node 3的下一级集成的接入和回传节点或下行(下游)IAB-node或子IAB-node等，例如，该无线设备可以是图2中IAB-node 3的下行IAB-node 4。
第二重配置消息可以是无线资源控制重配置(RRC Reconfiguration)消息，例如conditional RRC Reconfiguration消息。在操作302中，IAB-node 3向该无线设备发送 指示信息的时机为下述时机之一：
在IAB-node 3以条件切换或条件重配置(Conditional handover/reconfiguration)的方式迁移或重配置或改变CU的情况下，IAB-node 3确定条件重配置的相关测量事件被满足时；例如，测量事件可以是A3事件(邻小区质量比服务小区质量好一个偏移值)或A5事件(服务小区质量低于一个门限，邻小区质量高于另一个门限)；
在IAB-node 3以条件切换或条件重配置的方式迁移或重配置或改变CU的情况下，IAB-node 3发起条件切换或条件重配置的执行时；
IAB-node 3接收到第一重配置消息时，例如收到RRC reconfiguration消息；
IAB-node 3从源集中单元或父节点(source IAB-donor/source parent IAB-node)去附着(detach)时，源集中单元例如是图2的Source IAB-donar，源父节点例如是图2的IAB-node 1；
IAB-node 3与新的父节点或目标父节点(target parent IAB-node)下行同步时，例如检测到新的父节点或目标父节点下的小区的SSB；
IAB-node 3发起到新的父节点或目标父节点(target parent IAB-node)的随机接入过程时，其中，新的父节点或目标父节点例如是图2的IAB-node 2，例如，发起随机接入过程可以是初始化随机接入过程或选择随机接入资源或随机接入preamble发送或消息A(MSG A)发送等；
IAB-node 3向新的父节点或目标父节点(parent IAB-node)发送基于第一重配置消息的重配置完成(例如，RRC reconfiguration complete)消息时；
IAB-node 3随机接入过程成功时，例如，IAB-node 3到新的父节点或目标父节点(parent IAB-node)的随机接入过程成功，例如收到随机接入响应或竞争解决成功或接收到消息B(MSG B)等；
IAB-node 3收到来自其新的父节点(parent IAB-node)的针对重配置完成(例如，RRC reconfiguration complete)消息的确认消息或反馈消息时，其中，该确认消息例如是无线链路控制(RLC)层确认消息，该反馈消息例如是混合自动重传请求(HARQ)反馈消息。
在至少一些实施例中，操作302发送的指示信息使能或者禁止该无线设备：应用第二重配置消息中的配置，或者发起条件重配置的执行，或者执行迁移，或者改变CU等。
以IAB-node 3进行inter-CU迁移为例，在IAB-node 3迁移前，Source IAB-donor或Source CU可以发送切换请求消息给Target IAB-donor或Target CU，其中携带例如所有终端设备的上下文、所有IAB-MT的上下文、所有IAB-DU的上下文、回传和拓扑相关的信息和IP地址信息等。在终端设备的上下文中可以包括终端设备(例如UE1、UE2)所在的源小区的物理小区标识(PCI)等信息，在IAB-MT的上下文中可以包括IAB-node(例如IAB-node 4)所在的源小区的物理小区标识(PCI)等信息。Target IAB-donor或Target CU收到切换请求后，发送切换请求确认消息给Source IAB-donor或Source CU，其中可以包括与终端设备的源小区的PCI对应的配置和/或与IAB-node的源小区的PCI对应的配置。Source IAB-donor或Source CU收到该配置后，可以设置与该小区对应的条件，将该小区对应的条件和配置包括在向无线设备(即当前无线设备UE1、UE2或IAB-node 4)发送第二重配置消息。
在该至少一些实施例中，在第二重配置消息中(例如，在reconfigurationWithSync中包括的ServingCellConfigCommon中)，与IAB-node 3服务UE或下行IAB-node的小区(即，当前为无线设备UE1、UE2、UE3或IAB-node 4的服务小区)具有相同标识的目标候选小区被配置一次或出现一次。例如，标识可以是PCI或小区标识(cell ID)或小区全球识别码(CGI)或小区全局标识符(ECGI)等。由此，该指示信息使能该无线设备应用第二重配置消息中的与当前服务小区具有相同标识的目标候选小区的配置。
例如，无线设备(例如，UE1、UE2、UE3或IAB-node 4)收到IAB-node 3发送的该指示信息后，发起条件重配置，应用的condRRCReconfig为该IAB-node 3的当前服务小区的PCI对应的condRRCReconfig，也就是RRC reconfiguration消息中的reconfigurationWithSync中包括的ServingCellConfigCommon中指示的物理小区标识(PCI)为当前服务小区的物理小区标识的condRRCReconfig。
此外，本申请可以不限于此，在该至少一些实施例中，在第二重配置消息中(例如，在reconfigurationWithSync中包括的ServingCellConfigCommon中)，与IAB-node 3服务UE或下行IAB-node的小区(即，当前为无线设备UE1、UE2或IAB-node 4的服务小区)具有相同标识的目标候选小区被配置两次以上(即，出现两次以上)或者不被配置(即，不出现)。
在至少另一些实施例中，操作302中的该指示信息指示集中单元(CU)的信息， 该集中单元是指IAB-node 3基于第一重配置消息将要连接或已经连接的集中单元，例如，在inter-CU迁移的情况下该集中单元可以是图2中的Target IAB-donor的CU。
其中，该集中单元的信息包括下列信息中的至少一者：该集中单元的标识；该集中单元的索引；该集中单元的互联网协议(IP)地址和/或网络设备标识(gNB Identifier(gNB ID))的至少一部分(例如，最高有效位MSB或最低有效位LSB)；该集中单元的小区标识(Cell identity)或者该小区标识的至少一部分(例如，Cell identity的最高有效位MSBs)；该集中单元的公共陆地移动网标识信息(PLMN-IdentityInfo)的至少一部分；公共网关接口(CGI)的至少一部分。
在该至少另一些实施例中，第二重配置消息中可以包括该集中单元的信息以及与该集中单元的信息对应的配置。由此，无线设备(例如，UE1、UE2或IAB-node 4)在收到IAB-node 3发送的该指示信息，以及第二重配置消息的情况下，能够根据该指示信息中的该集中单元的信息，使用第二重配置消息中的与该集中单元的信息对应的配置，并应用该配置。
在至少又一些实施例中，该指示信息可以指示该无线设备应用的配置(例如，condRRCReconfig)。
此外，由于RRC功能位于IAB-donor CU中，IAB-node没有RRC功能，因此迁移的IAB-node 3无法解析IAB-node 3下的无线设备(例如，UE1、UE2、UE3或IAB-node 4)收到的第二重配置消息中的配置。因而，IAB-node 3可以通过对应关系指示信息来确定该无线设备应用的配置(例如，condRRCReconfig)，进而将确定下来的配置指示给无线设备。
如图3所示，该数据的接收和发送方法还可以包括：
操作303、IAB-node 3接收对应关系指示信息。
例如，操作303中的对应关系指示信息用于指示：
第二重配置消息(例如，conditional RRC reconfiguration)中的配置的标识信息(例如CondReconfigId或MeasId等)与第一重配置消息中的目标小区的标识信息(例如，目标小区的PCI)的对应关系；或者，第二重配置消息(例如，conditional RRC reconfiguration)中的配置的标识信息(例如CondReconfigId或MeasId等)与第一重配置消息中的配置的标识信息(例如CondReconfigId或MeasId等)的对应关系。
又例如，操作303中的对应关系指示信息用于指示：
目标小区(或目标候选小区)与第二配置消息(例如，conditional RRC reconfiguration)中包括的配置的标识信息(例如，CondReconfigId或MeasId等)或配置(例如，condRRCReconfig)的对应关系，其中，IAB-node 3可以接收F1-C消息(例如，UE Context Modification Request)，该F1-C消息中包括该对应关系指示信息。
值得注意的是，操作301、操作302、操作303的顺序可以不限于图3所示，例如：操作303也可以在操作301或操作302的前面；或者，操作303也可以被包括在操作301中，即，IAB-nide 3同时接收第一重配置消息和对应关系指示信息。
在本申请第一方面的实施例中，IAB-node 3可以通过回传自适应协议数据单元(BAP PDU)、无线链路层控制协议数据单元(RLC PDU)、媒体接入控制控制信元(MAC CE)、媒体接入控制子头(MAC subheader)或物理层信令向该无线设备(例如，UE1、UE2、UE3或IAB-node 4)发送指示信息。
在一些实施例中，可以定义新的回传自适应控制协议数据单元(BAP control PDU)，用于发送该指示信息，例如：该BAP control PDU可以使用一个新的PDU type来标识其用于发送该指示信息，和/或，该BAP control PDU可以包含8bit或16bit或24bit等的CU的信息。
例如，该BAP control PDU的格式可以如下面的表2所示。在表2中，D/C域为1比特，指示对应的BAP PDU为BAP数据PDU还是BAP控制PDU，PDU type例如为3比特，指示BAP控制PDU中包括的控制信息的类型。R为保留比特。
表2
D/C PDU type R R R
又例如，该BAP control PDU的格式也可以如下面的表3所示。在表3中，除了表2所示的域之外，BAP control PDU还包括CU的信息，例如CU ID，表3所示的CU ID为8比特，此外，CU ID也可以是16比特或24比特等。
表3
Figure PCTCN2020122555-appb-000002
在一些实施例中，可以定义新的无线链路层控制控制协议数据单元(RLC control  PDU)，用于发送该指示信息，例如，该RLC control PDU可以使用一个新的Control PDU Type(CPT)来标识其用于发送该指示信息，和/或，该BAP control PDU可以包含8bit或16bit或24bit等的CU的信息；
在一些实施例中，可以定义新的媒体接入控制控制信元(MAC CE)，用于发送该指示信息，该MAC CE可以对应一个新的、位于子头中的逻辑信道标识(LCID in subheader)，例如，在该指示信息包含CU的信息的情况下，该MAC CE可以包含8bit或16bit或24bit的CU的信息，该MAC CE也可以是8bit或16bit或24bit长度；
在一些实施例中，媒体接入控制子头(MAC subheader)可以具有新的LCID，能够用于发送该指示信息，例如，在指示信息用于指示无线设备使能第二重配置中的配置的情况下，该无线设备接收到包含该LCID的MAC子头，则应用第二重配置中的配置；
在一些实施例中，物理层信令可以是下行控制信息(DCI)中的一个域，DCI中的该一个域用于发送该指示信息，DCI中的该一个域例如可以是组公共DCI(group common DCI)、公共DCI(common DCI)或终端设备特定的DCI(UE-specific DCI)等，例如，在指示信息用于指示无线设备使能第二重配置中的配置的情况下，DCI中可以增加1bit的域用于发送该指示信息，另外，DCI也可以是寻呼DCI(paging DCI)等。
在本申请第一方面的实施例中，如图3所示，该信号的接收和发送方法还可以包括：
操作304、所述集成的接入和回传节点还向所述无线设备转发所述第二重配置消息。
例如，IAB-node 3可以从Source IAB-donar收到第二重配置消息，并将该第二重配置消息转发给无线设备(例如，UE1、UE2、UE3或IAB-node 4)。
值得注意的是，操作301、操作302、操作303、操作304的顺序可以不限于图3所示，例如：操作304也可以在操作301或操作302或操作303的前面；或者，操作304也可以被包括在操作301或操作303中。
图4是本申请的信号接收和发送方法的另一示意图。如图4所示的方法与图3所示的方法的区别在于，图4不具有操作304，而是具有操作305和操作306。
操作305、集成的接入和回传节点存储第二重配置消息；以及
操作306、该集成的接入和回传节点向无线设备发送该第二重配置消息。
在图4的方法中，IAB-node 3存储收到的第二重配置消息，在迁移过程中或迁移完成后将该第二重配置消息发送给该无线设备(例如，UE1、UE2、UE3或IAB-node 4)。
值得注意的是，操作301、操作302、操作303、操作305、操作306的顺序可以不限于图4所示，例如：操作305和操作306也可以在操作301或操作302或操作303的前面；或者，操作305在操作301或操作302的前面，操作306被包括在操作302中。
在操作306中，IAB-node 3向该无线设备发送第二重配置消息的时机可以为下述时机之一：
在IAB-node 3以条件切换或条件重配置(Conditional handover/reconfiguration)的方式迁移或重配置或改变CU的情况下，IAB-node 3确定条件重配置的相关测量事件被满足时，例如，测量事件可以是A3事件(邻小区质量比服务小区质量好一个偏移值)或A5事件(服务小区质量低于一个门限，邻小区质量高于另一个门限)；
在IAB-node 3以条件切换或条件重配置的方式迁移或重配置或改变CU的情况下，IAB-node 3发起条件切换或条件重配置的执行时；
IAB-node 3接收到第一重配置消息时，例如收到RRC reconfiguration消息；
IAB-node 3从源集中单元或父节点(source IAB-donor/source parent IAB-node)去附着(detach)时，源集中单元例如是图2的Source IAB-donar，源父节点例如是图2的IAB-node 1；
IAB-node 3与新的父节点或目标父节点(target parent IAB-node)下行同步时，例如检测到新的父节点或目标父节点下的小区的SSB；
IAB-node 3发起到新的父节点或目标父节点(target parent IAB-node)的随机接入过程时，其中，新的父节点或目标父节点例如是图2的IAB-node 2；例如，发起随机接入过程可以是初始化随机接入过程或选择随机接入资源或随机接入preamble发送或消息A(MSG A)发送等；
IAB-node 3向新的父节点或目标父节点(parent IAB-node)发送基于第一重配置消息的重配置完成(例如，RRC reconfiguration complete)消息时；
IAB-node 3随机接入过程成功时，例如，IAB-node 3到新的父节点或目标父节点 (parent IAB-node)的随机接入过程成功，例如收到随机接入响应或竞争解决成功或接收到消息B(MSG B)等；
IAB-node 3收到来自其新的父节点(parent IAB-node)的针对重配置完成(例如，RRC reconfiguration complete)消息的确认消息或反馈消息时，其中，该确认消息例如是无线链路控制(RLC)层确认消息，该反馈消息例如是混合自动重传请求(HARQ)反馈消息。
在图4所示的方法中，IAB-node 3向该无线设备发送第二重配置消息的时机与IAB-node 3向该无线设备发送指示信息的时机可以相同，即，IAB-node 3同时向该无线设备发送第二重配置消息和指示信息，或者在一条消息中包含该第二重配置消息和该指示信息。由此，能够节省发送资源。
此外，在图4所示的方法中，IAB-node 3向该无线设备发送第二重配置消息的时机与IAB-node 3向该无线设备发送指示信息的时机也可以不相同，由此，发送时机的灵活性较大。
图5是IAB-node 3进行inter-CU迁移时的一个流程图。如图5所示，该流程包括如下操作：
1.Source IAB donor对UE1、UE2和/或IAB-node 4作出进行条件切换的决定(CHO decision)，对IAB-node 3做出进行迁移的决定，例如可以使用CHO或切换过程，准备使IAB-node 3及其服务的UE和/或IAB-node(IAB-MT)迁移到Target IAB donor下；
2.Source IAB donor向Target IAB donor发送切换请求(Handover Request)；
3.Target IAB donor向IAB-node 3的目标父节点IAB-node 2发送请求，该请求例如是终端设备上下文建立请求(UE context setup req)；
4.IAB-node 2针对操作3的请求发送响应，该响应例如是终端设备上下文建立响应(UE context setup resp)；
5.Target IAB donor向Source IAB donor发送切换请求确认消息，例如，handover Request Acknowledge；
6.Source IAB donor向IAB-node 3发送请求，该请求例如是终端设备上下文修改请求(UE context modification req)，该请求中可以包括第二配置信息，例如RRC Reconfiguration；
7.IAB-node 3将第二配置信息(例如RRC Reconfiguration)转发给无线设备(例如，UE1、UE2或IAB-node 4)，操作7对应于图3的操作304；
8.IAB-node 3向Source IAB donor发送响应，该响应例如是终端设备上下文修改响应(UE context modification resp)；
9.无线设备(例如，UE1、UE2或IAB-node 4)向IAB-node 3发送第二配置完成消息，例如RRC reconfiguration complete；
10.IAB-node 3向Source IAB donor发送上行链路无线资源控制消息传递消息，例如UL RRC Message Transfer。
在图5所示的流程中，IAB-node 3可以进行11A所示的条件切换(CHO)或者11B所示的切换(HO)。
如图5所示，11A所示的条件切换(CHO)包括如下操作：
11a.Source IAB donor向IAB-node 3源父节点IAB-node 1发送请求，该请求例如是UE context modification req；
12a.IAB-node 1向IAB-node 3发送第一配置信息，该第一配置信息例如是RRC Reconfiguration；
13a.IAB-node 1向Source IAB donor发送响应，该响应例如是UE上下文修改响应(UE context modification resp)；
14a.IAB-node 3向IAB-node 1发送第一配置信息接收完成响应，该第一配置完成消息，例如是RRC reconfiguration complete；
15a.IAB-node 1向Source IAB donor发送上行链路无线资源控制消息传递消息(UL RRC Message Transfer)；
16a.IAB-node 3评估切换条件(Evaluate HO condition)。
如图5所示，11B所示的切换(HO)包括如下操作：
11b.Source IAB donor向IAB-node 3源父节点IAB-node 1发送请求，该请求例如是UE上下文修改请求(UE context modification req)；
12b.IAB-node 1向IAB-node 3发送第一配置信息，该第一配置信息例如是RRC Reconfiguration；
13b.IAB-node 1向Source IAB donor发送响应，该响应例如是UE上下文修改响应(UE context modification resp)。
如图5所示，迁移的流程还包括如下操作：
12.在操作11A的16a中评估切换条件的结果为切换条件满足时，或者在操作11B完成时，在操作12中，IAB-node 3从Source IAB donor去附着，应用第一配置信息中的配置，并进行向目标/新的父节点的随机接入过程(detach from source，apply the stored configuration，RACH)；
13.IAB-node 3向新的父节点IAB-node 2发送第一配置信息配置完成信息，该第一配置信息配置完成信息例如可以是RRC reconfiguration complete；
14.IAB-node 2向Target IAB-donor发送上行链路无线资源控制消息传递消息(UL RRC Message Transfer)；
15a、15b.IAB-node 3可以在多个时机中的一个时机发送指示信息给无线设备(例如，UE1、UE2或IAB-node 4)，例如，15a所示的时机是IAB-node 3确定条件重配置的相关测量事件被满足时，15b所示的时机是IAB-node 3发送基于第一重配置消息的重配置完成时，其中，该指示信息使能或者禁止该无线设备应用第二重配置消息中的配置，或者，该指示信息指示Target IAB donor(Target CU)的信息；
16.无线设备(例如，UE1、UE2、UE3或IAB-node 4)评估切换条件(Evaluate HO condition)；
17.无线设备(例如，UE1、UE2或IAB-node 4)在收到指示信息的情况下，应用第二配置信息中的配置，并在应用配置完成后向IAB-node 3发送第二配置信息配置完成信息，例如，RRC reconfiguration complete。
3a.Target IAB donor向IAB-node 3发送请求，该请求例如是终端设备上下文建立请求(UE context setup req)；
4a.IAB-node 3针对操作3a的请求向Target IAB donor发送响应，该响应例如是终端设备上下文建立响应(UE context setup resp)；
5a.IAB-node 3向Target IAB donor发送上行链路无线资源控制消息传递消息(UL RRC Message Transfer)，该UL RRC message transfer中可以包括针对无线设备(例如，UE1、UE2或IAB-node 4)的第二配置信息配置完成信息(RRC reconfiguration complete for UE/descent IAB nodes)。
图6是IAB-node 3进行inter-CU迁移时的另一个流程图。如图6所示，该流程包括如下操作：
1.Source IAB donor对UE1、UE2和/或IAB-node 4作出进行条件切换的决定(CHO decision)，对IAB-node 3做出进行迁移的决定，例如可以使用CHO或切换过程，并且准备使IAB-node 3及其服务的UE和/或IAB-node(IAB-MT)迁移到Target IAB donor下；
2.Source IAB donor向Target IAB donor发送切换请求(Handover Request)；
3.Target IAB donor向IAB-node 3的目标父节点IAB-node 2发送请求，该请求例如是终端设备上下文建立请求(UE context setup req)；
4.IAB-node 2针对操作3的请求发送响应，该响应例如是终端设备上下文建立响应(UE context setup resp)；
5.Target IAB donor向Source IAB donor发送切换请求确认消息，例如，handover Request Acknowledge；
6.Source IAB donor向IAB-node 3发送请求，该请求例如是终端设备上下文修改请求(UE context modification req)，该请求中可以包括第二配置信息，例如RRC Reconfiguration；
7.IAB-node存储该第二配置信息，对应于图4的操作305；
8.IAB-node 3向Source IAB donor发送响应，该响应例如是终端设备上下文修改响应(UE context modification resp)；
在图6所示的流程中，IAB-node 3可以进行9A所示的条件切换(CHO)或者9B所示的切换(HO)。其中，针对9A所示的条件切换(CHO)的说明与针对图5的11A所示的条件切换(CHO)的说明相同，针对9B所示的切换(HO)的说明与针对图5的11B所示的切换(HO)的说明相同。
如图6所示，迁移的流程还包括如下操作：
10.在操作9A的16a中评估切换条件的结果为切换条件满足时，或者在操作9B完成时，在操作10中，IAB-node 3从Source IAB donor去附着，应用第一配置信息中的配置，并进行向目标/新的父节点的随机接入过程(detach from source，apply the stored configuration，RACH)；
11.IAB-node 3向新的父节点IAB-node 2发送第一配置信息配置完成信息，该第一配置信息配置完成信息例如可以是RRC reconfiguration complete；
12.IAB-node 2向Target IAB-donor发送上行链路无线资源控制消息传递消息(UL  RRC Message Transfer)；
13.IAB-node 3可以在多个时机中的一个时机发送指示信息给无线设备(例如，UE1、UE2或IAB-node 4)，例如，图6所示的操作13的时机是IAB-node 3发送基于第一重配置消息的重配置完成时(即，图6的操作11)，其中，该指示信息使能或者禁止该无线设备应用第二重配置消息中的配置，或者，该指示信息指示Target IAB donor的信息；并且，在图6所示的实施方式中，IAB-node 3在操作13中还发送第二配置信息(RRC Reconfiguration)，对应于图4的操作306，也就是说，图6的操作13对应于将图4的操作306和操作302合并为一个操作；此外，本申请可以不限于此，例如，第二配置信息或指示信息可以在其它的时机被发送，或者，指示信息和第二配置信息可以不同时发送；
14.无线设备(例如，UE1、UE2或IAB-node 4)在收到指示信息的情况下，应用第二配置信息中的配置，并在应用配置完成后向IAB-node 3发送第二配置信息配置完成信息，例如，RRC reconfiguration complete。
此外，针对图6中操作3a、4a、5a的说明与针对图5中操作3a、4a、5a的说明相同。
根据本申请的第一方面的实施例，迁移的或准备迁移的IAB-node(例如，IAB-node 3)下的无线设备UE或IAB-node(例如，UE1、UE2或IAB-node 4)也可以应用来自新的IAB-donor的配置，例如安全密钥相关的配置，以便与新的IAB-donor进行正确通信，并且，方案的复杂度较低，且对当前的标准影响较小；此外，对于intra-CU迁移的场景，同样能够使用本申请的第一方面的实施例的方法进行处理，使得迁移的或准备迁移的IAB-node(例如，IAB-node 3)下的无线设备UE或IAB-node(例如，UE1、UE2或IAB-node 4)及时地应用新的配置。
第二方面的实施例
至少针对与第一方面的实施例相同的问题，本申请第二方面的实施例提供一种信号的接收方法，与第一方面的实施例的方法对应。
下面，以图2的inter-CU migration的场景为例，从图2的无线设备一侧来说明本申请第二方面的实施例的信号的接收方法。需要指出的是，本申请的第二方面的实施例的信号的接收方法并不限于inter-CU migration的场景，该方法也适用于intra-CU  migration的场景，无线设备与IAB-node 3的交互过程可以参考图5或图6。无线设备包括：终端设备，例如，UE1、UE2；或者，IAB-node 3的下一级集成的接入和回传节点，IAB-node 4。
图7是第二方面的实施例中信号的接收方法的一个示意图，如图7所示，该方法包括：
操作701、无线设备接收第二重配置消息；以及
操作702、该无线设备接收指示信息，所述指示信息用于指示所述无线设备在无线资源控制(RRC)层应用接收到的所述第二重配置消息中的配置。
值得注意的是，以上附图7仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图7的记载。
该无线设备接收IAB-node 3发送的该指示信息的时机为下述时机之一：
在IAB-node 3以条件切换或条件重配置(Conditional handover/reconfiguration)的方式迁移或重配置或改变CU的情况下，IAB-node 3确定条件重配置的相关测量事件被满足时，例如，测量事件可以是A3事件(邻小区质量比服务小区质量好一个偏移值)或A5事件(服务小区质量低于一个门限，邻小区质量高于另一个门限)；
在IAB-node 3以条件切换或条件重配置的方式迁移或重配置或改变CU的情况下，IAB-node 3发起条件切换或条件重配置的执行时；
IAB-node 3接收到第一重配置消息时，例如收到RRC reconfiguration消息；
IAB-node 3从源集中单元或父节点(source IAB-donor/source parent IAB-node)去附着(detach)时，源集中单元例如是图2的Source IAB-donar，源父节点例如是图2的IAB-node 1；
IAB-node 3与新的父节点或目标父节点(target parent IAB-node)下行同步时，例如检测到新的父节点或目标父节点下的小区的SSB；IAB-node 3发起到新的父节点或目标父节点(target parent IAB-node)的随机接入过程时，其中，新的父节点或目标父节点例如是图2的IAB-node 2，例如，发起随机接入过程可以是初始化随机接入过程或选择随机接入资源或随机接入preamble发送或消息A(MSG A)发送等；
IAB-node 3向新的父节点或目标父节点(parent IAB-node)发送基于第一重配置 消息的重配置完成(例如，RRC reconfiguration complete)消息时；
IAB-node 3随机接入过程成功时，例如，IAB-node 3到新的父节点或目标父节点(parent IAB-node)的随机接入过程成功，例如收到随机接入响应或竞争解决成功或接收到消息B(MSG B)等；
IAB-node 3收到来自其新的父节点(parent IAB-node)的针对重配置完成(例如，RRC reconfiguration complete)消息的确认消息或反馈消息时，其中，该确认消息例如是无线链路控制(RLC)层确认消息，该反馈消息例如是混合自动重传请求(HARQ)反馈消息。
在本申请中，该无线设备可以通过回传自适应协议数据单元(BAP PDU)、无线链路层控制协议数据单元(RLC PDU)、媒体接入控制控制信元(MAC CE)、媒体接入控制子头(MAC subheader)或物理层信令接收该指示信息。
在至少一些实施例中，该指示信息使能或者禁止无线设备：在无线资源控制(RRC)层应用该第二重配置消息中的配置，或者发起条件重配置的执行，或者执行迁移，或者改变CU等。其中，在该第二重配置消息中，与IAB-node 3服务UE或下行IAB-node的小区(即，当前为无线设备UE1、UE2、UE3或IAB-node 4的服务小区)具有相同标识的目标候选小区被配置一次或出现一次。例如，标识可以是PCI或小区标识(cell ID)或全球小区识别码(CGI)或小区全局标识符(ECGI)等。该无线设备在无线资源控制(RRC)层应用第二重配置消息中的与当前服务小区具有相同标识的目标候选小区的配置。
此外，本申请可以不限于此，在该至少一些实施例中，在第二重配置消息中(例如，在reconfigurationWithSync中包括的ServingCellConfigCommon中)，与IAB-node 3服务UE或下行IAB-node的小区(即，当前为无线设备UE1、UE2或IAB-node 4的服务小区)具有相同标识的目标候选小区被配置两次以上(即，出现两次以上)或者不被配置(即，不出现)。
在至少另一些实施例中，该指示信息指示集中单元(CU)的信息，其中，该集中单元是指IAB-node 3基于第一重配置消息将要连接或已经连接的集中单元，例如，图2中的Target IAB donor。
其中，该集中单元的信息包括下列信息中的至少一者：该集中单元的标识；该集中单元的索引；该集中单元的互联网协议(IP)地址和/或网络设备标识(gNB Identifier (gNB ID))的至少一部分(例如，最高有效位MSB或最低有效位LSB)；该集中单元的小区标识(Cell identity)或者该小区标识的至少一部分(例如，Cell identity的最高有效位MSBs)；该集中单元的公共陆地移动网标识信息(PLMN-IdentityInfo)的至少一部分；公共网关接口(CGI)的至少一部分。
在该在至少另一些实施例中，第二重配置消息中包括集中单元的信息以及与该集中单元的信息对应的配置，该无线设备根据该指示信息中的该集中单元的信息，确定该第二重配置消息中与该集中单元的信息对应的配置，并在该无线设备的无线资源控制(RRC)层应用该配置。
在至少又一些实施例中，该指示信息可以指示该无线设备应用的配置(例如，condRRCReconfig)。
其中，第二重配置消息(conditional RRC reconfiguration)中的配置的标识信息与所述第一重配置消息中的目标小区的标识信息(例如PCI)具有对应关系；或者，第二重配置消息(conditional RRC reconfiguration)中的所述配置的标识信息与所述第一重配置消息中的配置的标识信息具有对应关系；或者，目标小区与第二配置消息(conditional RRC reconfiguration)中包括的配置的标识信息(CondReconfigId)或配置(condRRCReconfig)具有对应关系。
在操作701中，在一些实施例中，该无线设备接收由IAB-node 3转发的来自Source IAB-donor的该第二重配置消息。
在操作701中，在另一些实施例中，IAB-node 3接收来自Source IAB-donor的该第二重配置消息并进行存储，在适当的时机将存储的该第二重配置消息发送给无线设备。
其中，无线设备接收由IAB-node 3发送的第二重配置消息的时机为下述时机之一：
在IAB-node 3以条件切换或条件重配置(Conditional handover/reconfiguration)的方式迁移或重配置或改变CU的情况下，IAB-node 3确定条件重配置的相关测量事件被满足时，例如，测量事件可以是A3事件(邻小区质量比服务小区质量好一个偏移值)或A5事件(服务小区质量低于一个门限，邻小区质量高于另一个门限)；
在IAB-node 3以条件切换或条件重配置的方式迁移或重配置或改变CU的情况下，IAB-node 3发起条件切换或条件重配置的执行时；
IAB-node 3接收到第一重配置消息时，例如收到RRC reconfiguration消息；
IAB-node 3从源集中单元或父节点(source IAB-donor/source parent IAB-node)去附着(detach)时，源集中单元例如是图2的Source IAB-donar，源父节点例如是图2的IAB-node 1；
IAB-node 3与新的父节点或目标父节点(target parent IAB-node)下行同步时，例如检测到新的父节点或目标父节点下的小区的SSB；
IAB-node 3发起到新的父节点或目标父节点(target parent IAB-node)的随机接入过程时，其中，新的父节点或目标父节点例如是图2的IAB-node 2；例如，发起随机接入过程可以是初始化随机接入过程或选择随机接入资源或随机接入preamble发送或消息A(MSG A)发送等；
IAB-node 3向新的父节点或目标父节点(parent IAB-node)发送基于第一重配置消息的重配置完成(例如，RRC reconfiguration complete)消息时；
IAB-node 3随机接入过程成功时，例如，IAB-node 3到新的父节点或目标父节点(parent IAB-node)的随机接入过程成功，例如收到随机接入响应或竞争解决成功或接收到消息B(MSG B)等；
IAB-node 3收到来自其新的父节点(parent IAB-node)的针对重配置完成(例如，RRC reconfiguration complete)消息的确认消息或反馈消息时，其中，该确认消息例如是无线链路控制(RLC)层确认消息，该反馈消息例如是混合自动重传请求(HARQ)反馈消息。
在一些实施例中，无线设备从IAB-node 3同时接收该第二重配置消息和指示信息；此外，无线设备也可以不同时接收该第二重配置消息和指示信息。
根据本申请的第二方面的实施例，迁移的或准备迁移的IAB-node(例如，IAB-node 3)下的无线设备(例如，UE1、UE2或IAB-node 4)可以及时地在RRC层应用第二重配置消息中的配置，例如安全密钥相关的配置，以便与新的IAB-donor进行正确通信，并且，方案的复杂度较低，且对当前的标准影响较小；此外，对于intra-CU迁移的场景，本申请的第二方面的实施例的方法同样适用，从而使得迁移的或准备迁移的IAB-node(例如，IAB-node 3)下的无线设备(例如，UE1、UE2或IAB-node 4)及时地应用新的配置。
第三方面的实施例
至少针对与第一方面的实施例相同的问题，本申请第三方面的实施例提供一种信号的发送方法，与第一方面的实施例的方法对应。
下面，以图2的inter-CU migration的场景为例，从图2的源集中单元(Source IAB-donor)一侧来说明本申请第三方面的实施例的信号的发送方法。需要指出的是，本申请的第三方面的实施例的信号的发送方法并不限于inter-CU migration的场景，该方法也适用于intra-CU migration的场景，Source IAB-donor与IAB-node 3的交互过程可以参考图5或图6。
图8是第三方面的实施例中信号的发送方法的一个示意图，如图8所示，该方法包括：
操作801、源集中单元向集成的接入和回传节点发送第一重配置消息；以及
操作802、源集中单元向无线设备发送第二重配置消息，其中，在第二重配置消息中，与所述集成的接入和回传节点的当前服务小区具有相同标识的目标候选小区被配置一次。
图9是第三方面的实施例中信号的发送方法的另一个示意图，如图9所示，该方法包括：
操作901、源集中单元向集成的接入和回传节点发送第一重配置消息；以及
操作902、源集中单元向无线设备发送第二重配置消息，第二重配置消息中包括目标集中单元的信息以及与所述目标集中单元的信息对应的所述配置。
图10是第三方面的实施例中信号的发送方法的另一个示意图，如图10所示，该方法包括：
操作1001、源集中单元向集成的接入和回传节点发送第一重配置消息；
操作1002、源集中单元向无线设备发送第二重配置消息；以及
操作1003、向所述集成的接入和回传节点发送对应关系指示信息。
其中，操作1003中的该对应关系指示信息用于指示：第二重配置消息(conditional RRC reconfiguration)中的所述配置的标识信息与所述第一重配置消息中的目标小区的标识信息(例如PCI)的对应关系；第二重配置消息(conditional RRC reconfiguration)中的所述配置的标识信息与所述第一重配置消息中的配置的标识信息的对应关系；目标小区与所述第二配置消息(conditional RRC reconfiguration)中包括的所述配置的标 识信息(CondReconfigId)或所述配置(condRRCReconfig)的对应关系。
在图8、图9和图10中：集成的接入和回传节点例如是图2的IAB-node 3；无线设备例如是图2的UE1、UE2或IAB-node 4；目标集中单元是指IAB-node 3基于第一重配置消息将要连接或已经连接的集中单元，例如，图2的Target IAB-donor)。
根据本申请的第三方面的实施例，迁移的或准备迁移的IAB-node(例如，IAB-node3)下的无线设备(例如，UE1、UE2、UE3或IAB-node 4)可以及时地在RRC层应用第二重配置消息中的配置，例如安全密钥相关的配置，以便与新的IAB-donor进行正确通信，并且，方案的复杂度较低，且对当前的标准影响较小；此外，对于intra-CU迁移的场景，本申请的第三方面的实施例的方法同样适用，从而使得迁移的或准备迁移的IAB-node(例如，IAB-node 3)下的无线设备(例如，UE1、UE2或IAB-node 4)及时地应用新的配置。
第四方面的实施例
本申请实施例提供一种信号的接收和发送装置。该装置例如可以是集成的接入和回传节点，也可以是配置于集成的接入和回传节点的某个或某些部件或者组件，集成的接入和回传节点例如是图2的IAB-node 3。该装置对应于第一方面的实施例。
图11是本申请实施例的信号的接收和发送装置的一示意图，如图11所示，信号的接收和发送装置1100包括：
第一接收单元1101，其接收第一重配置消息；以及
第一发送单元1102，其向无线设备发送指示信息，指示信息用于指示无线设备应用第二重配置消息中的配置。
其中，该无线设备包括：终端设备，例如，图2中的UE1～UE3；或者，集成的接入和回传节点的下一级集成的接入和回传节点IAB-node 4。
在至少一个实施例中，第一发送单元1102向该无线设备发送指示信息的时机为下述时机之一：
在IAB-node 3以条件切换或条件重配置(Conditional handover/reconfiguration)的方式迁移或重配置或改变CU的情况下，IAB-node 3确定条件重配置的相关测量事件被满足时，例如，测量事件可以是A3事件(邻小区质量比服务小区质量好一个偏移值)或A5事件(服务小区质量低于一个门限，邻小区质量高于另一个门限)；
在IAB-node 3以条件切换或条件重配置的方式迁移或重配置或改变CU的情况下，IAB-node 3发起条件切换或条件重配置的执行时；
IAB-node 3接收到第一重配置消息时，例如收到RRC reconfiguration消息；
IAB-node 3从源集中单元或父节点(source IAB-donor/source parent IAB-node)去附着(detach)时，源集中单元例如是图2的Source IAB-donar，源父节点例如是图2的IAB-node 1；
IAB-node 3与新的父节点或目标父节点(target parent IAB-node)下行同步时，例如检测到新的父节点或目标父节点下的小区的SSB；
IAB-node 3发起到新的父节点或目标父节点(target parent IAB-node)的随机接入过程时，其中，新的父节点或目标父节点例如是图2的IAB-node 2；例如，发起随机接入过程可以是初始化随机接入过程或选择随机接入资源或随机接入preamble发送或消息A(MSG A)发送等；
IAB-node 3向新的父节点或目标父节点(parent IAB-node)发送基于第一重配置消息的重配置完成(例如，RRC reconfiguration complete)消息时；
IAB-node 3随机接入过程成功时，例如，IAB-node 3到新的父节点或目标父节点(parent IAB-node)的随机接入过程成功，例如收到随机接入响应或竞争解决成功或接收到消息B(MSG B)等；
IAB-node 3收到来自其新的父节点(parent IAB-node)的针对重配置完成(例如，RRC reconfiguration complete)消息的确认消息或反馈消息时，其中，该确认消息例如是无线链路控制(RLC)层确认消息，该反馈消息例如是混合自动重传请求(HARQ)反馈消息。
在一些实施例中，指示信息使能或者禁止该无线设备：应用第二重配置消息中的配置，或者执行迁移，或者改变CU等。其中，与IAB-node 3服务UE或下行IAB-node的小区(即，当前为无线设备UE1、UE2、UE3或IAB-node 4的服务小区)具有相同标识的目标候选小区被配置一次或出现一次。例如，标识可以是PCI或小区标识(cell ID)或全球小区识别码(CGI)或小区全局标识符(ECGI)等。由此，指示信息使能无线设备应用第二重配置消息中的与当前服务小区具有相同标识的目标候选小区的配置。
此外，本申请可以不限于此，在该至少一些实施例中，在第二重配置消息中(例 如，在reconfigurationWithSync中包括的ServingCellConfigCommon中)，与IAB-node 3服务UE或下行IAB-node的小区(即，当前为无线设备UE1、UE2或IAB-node 4的服务小区)具有相同标识的目标候选小区被配置两次以上(即，出现两次以上)或者不被配置(即，不出现)。
在另一些实施例中，指示信息指示集中单元的信息，其中，该集中单元是指集成的接入和回传节点基于第一重配置消息将要连接或已经连接的集中单元，例如，图2的Target IAB-node。
其中，第二重配置消息中包括集中单元的信息以及与集中单元的信息对应的配置。
在又一些实施例中，指示信息可以指示无线设备应用的配置。
在图11所示，信号的接收和发送装置1100还可以包括：
第二接收单元1103，其接收对应关系指示信息。
其中，该对应关系指示信息用于指示：第二重配置消息中的配置的标识信息与第一重配置消息中的目标小区的标识信息的对应关系；或者，第二重配置消息中的配置的标识信息与第一重配置消息中的配置的标识信息的对应关系；或者，目标小区与第二重配置消息中包括的配置的标识信息或配置的对应关系。
在图11中，信号的接收和发送装置1100还包括：
第二发送单元1104，其向无线设备转发第二重配置消息。
在图11中，信号的接收和发送装置1100还包括：
存储单元1105，其存储第二重配置消息；以及
第三发送单元1106，其向集成的接入和回传节点向无线设备发送第二重配置消息。
其中，第三发送单元1106向无线设备发送第二重配置消息的时机为下述时机之一：
在IAB-node 3以条件切换或条件重配置(Conditional handover/reconfiguration)的方式迁移或重配置或改变CU的情况下，IAB-node 3确定条件重配置的相关测量事件被满足时，例如，测量事件可以是A3事件(邻小区质量比服务小区质量好一个偏移值)或A5事件(服务小区质量低于一个门限，邻小区质量高于另一个门限)；
在IAB-node 3以条件切换或条件重配置的方式迁移或重配置或改变CU的情况下，IAB-node 3发起条件切换或条件重配置的执行时；
IAB-node 3接收到第一重配置消息时，例如收到RRC reconfiguration消息；
IAB-node 3从源集中单元或父节点(source IAB-donor/source parent IAB-node)去附着(detach)时，源集中单元例如是图2的Source IAB-donar，源父节点例如是图2的IAB-node 1；
IAB-node 3与新的父节点或目标父节点(target parent IAB-node)下行同步时，例如检测到新的父节点或目标父节点下的小区的SSB；
IAB-node 3发起到新的父节点或目标父节点(target parent IAB-node)的随机接入过程时，其中，新的父节点或目标父节点例如是图2的IAB-node 2；例如，发起随机接入过程可以是初始化随机接入过程或选择随机接入资源或随机接入preamble发送或消息A(MSG A)发送等；
IAB-node 3向新的父节点或目标父节点(parent IAB-node)发送基于第一重配置消息的重配置完成(例如，RRC reconfiguration complete)消息时；
IAB-node 3随机接入过程成功时，例如，IAB-node 3到新的父节点或目标父节点(parent IAB-node)的随机接入过程成功，例如收到随机接入响应或竞争解决成功或接收到消息B(MSG B)等；
IAB-node 3收到来自其新的父节点(parent IAB-node)的针对重配置完成(例如，RRC reconfiguration complete)消息的确认消息或反馈消息时，其中，该确认消息例如是无线链路控制(RLC)层确认消息，该反馈消息例如是混合自动重传请求(HARQ)反馈消息。
在本申请中，信号的接收和发送装置1100可以使用第二发送单元1104来转发第二重配置消息，或者，使用存储单元1105和第三发送单元1106来存储和发送第二重配置消息。
在使用存储单元1105和第三发送单元1106来存储和发送第二重配置消息的情况下，在一些实施例中，信号的接收和发送装置1100向无线设备同时发送第二重配置消息和指示信息，例如，第三发送单元1106和第一发送单元1102同时发送第二重配置消息和指示信息，或者，将第二重配置消息和指示信息合并到一个消息中，由第三发送单元1106或第一发送单元1102进行发送。此外，信号的接收和发送装置1100也可以不同时发送第二重配置消息和指示信息。
此外，为了简单起见，信号的接收和发送装置1100中仅示例性示出了各个部件 或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
以上各实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
第五方面的实施例
本申请实施例提供一种信号的接收装置。该装置例如可以是无线设备，也可以是配置于无线设备的某个或某些部件或者组件，无线设备例如是图2的UE1、UE2、或IAB-node 4。该信号的接收装置对应于第二方面的实施例。
图12是本申请实施例的信号的接收装置的一示意图，如图12所示，信号的接收装置1200包括：
接收单元1201，其接收第二重配置消息；以及
第三接收单元1202，其接收指示信息，所述指示信息用于指示所述无线设备在无线资源控制层应用接收到的所述第二重配置消息中的配置。
其中，第三接收单元1202接收集成的接入和回传节点(例如，图2的IAB-node 3)发送的该指示信息的时机为下述时机之一：
在IAB-node 3以条件切换或条件重配置(Conditional handover/reconfiguration)的方式迁移或重配置或改变CU的情况下，IAB-node 3确定条件重配置的相关测量事件被满足时，例如，测量事件可以是A3事件(邻小区质量比服务小区质量好一个偏移值)或A5事件(服务小区质量低于一个门限，邻小区质量高于另一个门限)；
在IAB-node 3以条件切换或条件重配置的方式迁移或重配置或改变CU的情况下，IAB-node 3发起条件切换或条件重配置的执行时；
IAB-node 3接收到第一重配置消息时，例如收到RRC reconfiguration消息；
IAB-node 3从源集中单元或父节点(source IAB-donor/source parent IAB-node)去附着(detach)时，源集中单元例如是图2的Source IAB-donar，源父节点例如是图2的IAB-node 1；
IAB-node 3与新的父节点或目标父节点(target parent IAB-node)下行同步时， 例如检测到新的父节点或目标父节点下的小区的SSB；
IAB-node 3发起到新的父节点或目标父节点(target parent IAB-node)的随机接入过程时，其中，新的父节点或目标父节点例如是图2的IAB-node 2；例如，发起随机接入过程可以是初始化随机接入过程或选择随机接入资源或随机接入preamble发送或消息A(MSG A)发送等；
IAB-node 3向新的父节点或目标父节点(parent IAB-node)发送基于第一重配置消息的重配置完成(例如，RRC reconfiguration complete)消息时；
IAB-node 3随机接入过程成功时，例如，IAB-node 3到新的父节点或目标父节点(parent IAB-node)的随机接入过程成功，例如收到随机接入响应或竞争解决成功或接收到消息B(MSG B)等；
IAB-node 3收到来自其新的父节点(parent IAB-node)的针对重配置完成(例如，RRC reconfiguration complete)消息的确认消息或反馈消息时，其中，该确认消息例如是无线链路控制(RLC)层确认消息，该反馈消息例如是混合自动重传请求(HARQ)反馈消息。该第三接收单元1202通过回传自适应协议数据单元、无线链路层控制协议数据单元、媒体接入控制控制信元、媒体接入控制子头或物理层信令接收该指示信息。
在一些实施例中，该指示信息使能或者禁止该无线设备：在无线资源控制层应用该第二重配置消息中的配置。其中，在该第二重配置消息中，与IAB-node 3服务UE或下行IAB-node的小区(即，当前为无线设备UE1、UE2、UE3或IAB-node 4的服务小区)具有相同标识的目标候选小区被配置一次或出现一次。例如，标识可以是PCI或小区标识(cell ID)或全球小区识别码(CGI)或小区全局标识符(ECGI)等。该无线设备在无线资源控制层应用该第二重配置消息中的与当前服务小区具有相同标识的目标候选小区的配置。
此外，本申请可以不限于此，在该至少一些实施例中，在第二重配置消息中(例如，在reconfigurationWithSync中包括的ServingCellConfigCommon中)，与IAB-node 3服务UE或下行IAB-node的小区(即，当前为无线设备UE1、UE2或IAB-node 4的服务小区)具有相同标识的目标候选小区被配置两次以上(即，出现两次以上)或者不被配置(即，不出现)。
在另一些实施例中，该指示信息指示集中单元的信息，该集中单元是指该集成的 接入和回传节点基于该第一重配置消息将要连接或已经连接的集中单元，例如，图2中的Target IAB donor。该第二重配置消息中包括该集中单元的信息以及与该集中单元的信息对应的该配置，该无线设备根据该指示信息中的该集中单元的信息，确定该第二重配置消息中与该集中单元的信息对应的该配置，并在无线资源控制层应用该配置。
在又一些实施例中，该指示信息指示该无线设备应用的该配置。
例如，该第二重配置消息中的该配置的标识信息与该第一重配置消息中的目标小区的标识信息具有对应关系；或者，该第二重配置消息中的该配置的标识信息与该第一重配置消息中的配置的标识信息具有对应关系；或者，目标小区与该第二重配置消息中包括的该配置的标识信息或该配置具有对应关系。
在本申请中，接收单元1201接收集成的接入和回传节点发送的该第二重配置消息的时机为下述时机之一：
在IAB-node 3以条件切换或条件重配置(Conditional handover/reconfiguration)的方式迁移或重配置或改变CU
的情况下，IAB-node 3确定条件重配置的相关测量事件被满足时，例如，测量事件可以是A3事件(邻小区质量比服务小区质量好一个偏移值)或A5事件(服务小区质量低于一个门限，邻小区质量高于另一个门限)；
在IAB-node 3以条件切换或条件重配置的方式迁移或重配置或改变CU的情况下，IAB-node 3发起条件切换或条件重配置的执行时；
IAB-node 3接收到第一重配置消息时，例如收到RRC reconfiguration消息；
IAB-node 3从源集中单元或父节点(source IAB-donor/source parent IAB-node)去附着(detach)时，源集中单元例如是图2的Source IAB-donar，源父节点例如是图2的IAB-node 1；
IAB-node 3与新的父节点或目标父节点(target parent IAB-node)下行同步时，例如检测到新的父节点或目标父节点下的小区的SSB；
IAB-node 3发起到新的父节点或目标父节点(target parent IAB-node)的随机接入过程时，其中，新的父节点或目标父节点例如是图2的IAB-node 2；例如，发起随机接入过程可以是初始化随机接入过程或选择随机接入资源或随机接入preamble发送或消息A(MSG A)发送等；
IAB-node 3向新的父节点或目标父节点(parent IAB-node)发送基于第一重配置消息的重配置完成(例如，RRC reconfiguration complete)消息时；
IAB-node 3随机接入过程成功时，例如，IAB-node 3到新的父节点或目标父节点(parent IAB-node)的随机接入过程成功，例如收到随机接入响应或竞争解决成功或接收到消息B(MSG B)等；
IAB-node 3收到来自其新的父节点(parent IAB-node)的针对重配置完成(例如，RRC reconfiguration complete)消息的确认消息或反馈消息时，其中，该确认消息例如是无线链路控制(RLC)层确认消息，该反馈消息例如是混合自动重传请求(HARQ)反馈消息。
该信号的接收装置1200从该集成的接入和回传节点同时接收该第二重配置消息和该指示信息。例如，接收单元1201接收第二重配置消息的时机与第三接收单元1202接收指示信息的时机相同，或者，将第二重配置消息和指示信息合并为一个消息发送，通过接收单元1201或第三接收单元1202来接收该消息。此外，该信号的接收装置1200也可以不同时接收该第二重配置消息和该指示信息。
此外，为了简单起见，信号的接收装置1200中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
以上各实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
第六方面的实施例
本申请实施例提供一种信号的发送装置。该装置例如可以是源集中单元，也可以是配置于源集中单元的某个或某些部件或者组件，源集中单元例如是图2的Source IAB donor。该信号的发送装置对应于第三方面的实施例。
图13是本申请实施例的信号的发送装置的一示意图，如图13所示，信号的发送装置1300包括：
第四发送单元1301，其向集成的接入和回传节点发送第一重配置消息；以及
第五发送单元1302，其向无线设备发送第二重配置消息。
其中，在所述第二重配置消息中，与所述集成的接入和回传节点的当前服务小区具有相同标识的目标候选小区被配置一次。
图14是本申请实施例的信号的发送装置的另一示意图，如图14所示，信号的发送装置1400包括：
第六发送单元1401，其向集成的接入和回传节点发送第一重配置消息；以及
第七发送单元1402，其向无线设备发送第二重配置消息，所述第二重配置消息中包括目标集中单元的信息以及与所述目标集中单元的信息对应的所述配置，所述目标集中单元是指所述集成的接入和回传节点基于所述第一重配置消息将要连接或已经连接的集中单元。
图15是本申请实施例的信号的发送装置的又一示意图，如图15所示，信号的发送装置1500包括：
第八发送单元1501，其向集成的接入和回传节点发送第一重配置消息；
第九发送单元1502，其向无线设备发送第二重配置消息；以及
第十发送单元1503，其向所述集成的接入和回传节点发送对应关系指示信息.
所述对应关系指示信息用于指示：
所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的目标小区的标识信息的对应关系；或者，所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的配置的标识信息的对应关系；或者，目标小区与所述第二重配置消息中包括的所述配置的标识信息或所述配置的对应关系。
在图13、图14和图15中：集成的接入和回传节点例如是图2的IAB-node 3；无线设备例如是图2的UE1、UE2或IAB-node 4；目标集中单元是指IAB-node 3基于第一重配置消息将要连接或已经连接的集中单元，例如，图2的Target IAB-donor)。
此外，为了简单起见，信号的发送装置1300、1400或1500中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
以上各实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也 可以将以上各个实施例中的一种或多种结合起来。
第七方面的实施例
本申请实施例还提供一种通信系统，可以参考图1，与第一方面至第六方面的实施例相同的内容不再赘述。
在一些实施例中，通信系统可以包括：
源集中单元，其包括如第六方面的实施例所述的信号的发送装置1300、1400或1500；
无线设备，其包括如第五方面的实施例所述的信号的接收装置1200；以及
集成的接入和回传节点，其包括如第四方面的实施例所述的信号的接收和发送装置1100。
本申请实施例还提供一种集成的接入和回传节点，但本申请不限于此，还可以是其他的设备。
图16是本申请实施例的集成的接入和回传节点IAB-node的构成示意图。如图16所示，IAB-node 1600可以包括：处理器1610(例如中央处理器CPU)和存储器1620；存储器1620耦合到处理器1610。其中该存储器1620可存储各种数据；此外还存储信息处理的程序1630，并且在处理器1610的控制下执行该程序1630。IAB-node 1600可以是源集中单元(例如，图2中的source IAB-donor)、无线设备中的下一级IAB-node或者图2中的IAB-node 3。
例如，处理器1610可以被配置为执行程序而实现如第一方面、第二方面或第三方面的实施例所述的方法。
此外，如图16所示，网络设备1600还可以包括：收发机1640和天线1650等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1600也并不是必须要包括图16中所示的所有部件；此外，网络设备1600还可以包括图16中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种终端设备，但本申请不限于此，还可以是其他的设备。
图17是本申请实施例的终端设备的示意图。如图17所示，该终端设备1700可以包括处理器1710和存储器1720；存储器1720存储有数据和程序，并耦合到处理器1710。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或 代替该结构，以实现电信功能或其他功能。终端设备1700可以是无线设备中的UE1、UE2、UE3中的至少一者。
例如，处理器1710可以被配置为执行程序而实现如第二方面的实施例所述的方法。
如图17所示，该终端设备1700还可以包括：通信模块1730、输入单元1740、显示器1750、电源1760。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备1700也并不是必须要包括图17中所示的所有部件，上述部件并不是必需的；此外，终端设备1700还可以包括图17中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在终端设备中执行所述程序时，所述程序使得所述终端设备执行第二方面的实施例所述的信号的接收方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得终端设备执行第二方面的实施例所述的信号的接收方法。
本申请实施例还提供一种计算机程序，其中当在IAB-node中执行所述程序时，所述程序使得所述IAB-node执行第一或第三方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得IAB-node执行第一或第三方面的实施例所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信 息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
IAB-node侧方法：
1.一种信号的接收和发送方法，包括：
集成的接入和回传节点接收第一重配置消息；以及
所述集成的接入和回传节点向无线设备发送指示信息，所述指示信息用于指示所述无线设备应用第二重配置消息中的配置。
2.如附记1所述的方法，其中，
所述集成的接入和回传节点向所述无线设备发送指示信息的时机为下述时机之一：
所述集成的接入和回传节点确定条件重配置的相关测量事件被满足时；
所述集成的接入和回传节点发起条件切换或条件重配置的执行时；
所述集成的接入和回传节点接收到所述第一重配置消息时；
所述集成的接入和回传节点从源集中单元或父节点去附着时；
所述集成的接入和回传节点与新的父节点或目标父节点下行同步时；
所述集成的接入和回传节点发起到新的父节点或目标父节点的随机接入过程时；
所述集成的接入和回传节点向新的父节点或目标父节点发送基于所述第一重配置消息的重配置完成消息时；
所述集成的接入和回传节点随机接入过程成功时；
所述集成的接入和回传节点收到来自其父节点的针对所述重配置完成消息的确认消息或反馈消息时。
3.如附记1～2中任一项所述的方法，其中，
所述指示信息使能或者禁止所述无线设备：
应用所述第二重配置消息中的配置。
4.如附记3所述的方法，其中，
在所述第二重配置消息中，与所述集成的接入和回传节点的当前服务小区具有相同标识的目标候选小区被配置一次。
5.如附记3所述的方法，其中，
所述指示信息使能所述无线设备应用所述第二重配置消息中的与当前服务小区具有相同标识的目标候选小区的配置。
6.如附记1～2中任一项所述的方法，其中，
所述指示信息指示集中单元的信息，
所述集中单元是指所述集成的接入和回传节点基于所述第一重配置消息将要连接或已经连接的集中单元。
7.如附记6所述的方法，其中，
所述第二重配置消息中包括所述集中单元的信息以及与所述集中单元的信息对应的所述配置。
8.如附记1～2中任意一项所述的方法，其中，
所述指示信息指示所述无线设备应用的所述配置。
9.如附记8所述的方法，其中，所述方法还包括：
接收对应关系指示信息，
所述对应关系指示信息用于指示：
所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的目标 小区的标识信息的对应关系；
所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的配置的标识信息的对应关系；
目标小区与所述第二重配置消息中包括的所述配置的标识信息或所述配置的对应关系。
10.如附记1～9中任一项所述的方法，其中，
所述集成的接入和回传节点通过回传自适应协议数据单元、无线链路层控制协议数据单元、媒体接入控制控制信元、媒体接入控制子头或物理层信令向所述无线设备发送所述指示信息。
11.如附记1～9中任一项所述的方法，其中，所述方法还包括：
所述集成的接入和回传节点还向所述无线设备转发所述第二重配置消息。
12.如附记1～9中任一项所述的方法，其中，所述方法还包括：
所述集成的接入和回传节点存储所述第二重配置消息；以及
所述集成的接入和回传节点向所述无线设备发送所述第二重配置消息。
13.如附记12所述的方法，其中，
所述集成的接入和回传节点向所述无线设备发送所述第二重配置消息的时机为下述时机之一：
所述集成的接入和回传节点确定条件重配置的相关测量事件被满足时；
所述集成的接入和回传节点发起条件切换或条件重配置的执行时；
所述集成的接入和回传节点接收到所述第一重配置消息时；
所述集成的接入和回传节点从源集中单元或父节点去附着时；
所述集成的接入和回传节点与新的父节点或目标父节点下行同步时；
所述集成的接入和回传节点发起到新的父节点或目标父节点的随机接入过程时；
所述集成的接入和回传节点向新的父节点或目标父节点发送基于所述第一重配置消息的重配置完成消息时；
所述集成的接入和回传节点随机接入过程成功时；
所述集成的接入和回传节点收到来自其父节点的针对所述重配置完成消息的确认消息或反馈消息时。
14.如附记13所述的方法，其中，
所述集成的接入和回传节点向所述无线设备同时发送所述第二重配置消息和所述指示信息。
15.如附记1～14中任一项所述的方法，其中，
所述无线设备是：
终端设备；或
所述集成的接入和回传节点的下一级集成的接入和回传节点。
UE和descendant IAB-node侧方法：
1.一种信号的接收方法，包括：
无线设备接收第二重配置消息；以及
所述无线设备接收指示信息，
所述指示信息用于所述无线设备在无线资源控制层应用接收到的所述第二重配置消息中的配置。
2.如附记1所述的方法，其中，
所述无线设备接收集成的接入和回传节点发送的所述指示信息的时机为下述时机之一：
所述集成的接入和回传节点确定条件重配置的相关测量事件被满足时；
所述集成的接入和回传节点发起条件切换或条件重配置的执行时；
所述集成的接入和回传节点接收到第一重配置消息时；
所述集成的接入和回传节点从源集中单元或父节点去附着时；
所述集成的接入和回传节点与新的父节点或目标父节点下行同步时；
所述集成的接入和回传节点发起到新的父节点或目标父节点的随机接入过程时；
所述集成的接入和回传节点向新的父节点或目标父节点发送基于所述第一重配置消息的重配置完成消息时；
所述集成的接入和回传节点随机接入过程成功时；
所述集成的接入和回传节点收到来自其父节点的针对所述重配置完成消息的确认消息或反馈消息时。
3.如附记1～2中任一项所述的方法，其中，
所述指示信息使能或者禁止所述无线设备：
在无线资源控制层应用所述第二重配置消息中的配置。
4.如附记3所述的方法，其中，
在所述第二重配置消息中，与所述集成的接入和回传节点的当前服务小区具有相同标识的目标候选小区被配置一次。
5.如附记4所述的方法，其中，
所述无线设备在无线资源控制层应用所述第二重配置消息中的与当前服务小区具有相同标识的目标候选小区的配置。
6.如附记1～2中任一项所述的方法，其中，
所述指示信息指示集中单元的信息，
所述集中单元是指所述集成的接入和回传节点基于所述第一重配置消息将要连接或已经连接的集中单元。
7.如附记6所述的方法，其中，
所述第二重配置消息中包括所述集中单元的信息以及与所述集中单元的信息对应的所述配置，
所述无线设备根据所述指示信息中的所述集中单元的信息，确定所述第二重配置消息中与所述集中单元的信息对应的所述配置，并在无线资源控制层应用所述配置。
8.如附记1～2中任意一项所述的方法，其中，
所述指示信息指示所述无线设备应用的所述配置。
9.如附记7所述的方法，其中，
所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的目标小区的标识信息具有对应关系；
所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的配置的标识信息具有对应关系；
目标小区与所述第二重配置消息中包括的所述配置的标识信息或所述配置具有对应关系。
10.如附记1～9中任一项所述的方法，其中，
所述无线设备通过回传自适应协议数据单元、无线链路层控制协议数据单元、媒体接入控制控制信元、媒体接入控制子头或物理层信令接收所述指示信息。
11.如附记1所述的方法，其中，
所述无线设备接收集成的接入和回传节点发送的所述第二重配置消息的时机为 下述时机之一：
所述集成的接入和回传节点确定条件重配置的相关测量事件被满足时；
所述集成的接入和回传节点发起条件切换或条件重配置的执行时；
所述集成的接入和回传节点接收到第一重配置消息时；
所述集成的接入和回传节点从源集中单元或父节点去附着时；
所述集成的接入和回传节点与新的父节点或目标父节点下行同步时；
所述集成的接入和回传节点发起到新的父节点或目标父节点的随机接入信道时；
所述集成的接入和回传节点向新的父节点或目标父节点发送基于所述第一重配置消息的重配置完成消息时；
所述集成的接入和回传节点随机接入过程成功时；
所述集成的接入和回传节点收到来自其父节点的针对所述重配置完成消息的确认消息或反馈消息时。
12.如附记11所述的方法，其中，
所述无线设备从所述集成的接入和回传节点同时接收所述第二重配置消息和所述指示信息。
13.如附记1～12中任一项所述的方法，其中，
所述无线设备是：
终端设备；或
所述集成的接入和回传节点的下一级集成的接入和回传节点。
Source donor侧方法：
1.一种信号的发送方法，包括：
源集中单元向集成的接入和回传节点发送第一重配置消息；以及
所述源集中单元向无线设备发送第二重配置消息，
其中，在所述第二重配置消息中，与所述集成的接入和回传节点的当前服务小区具有相同标识的目标候选小区被配置一次。
2.一种信号的发送方法，包括：
源集中单元向集成的接入和回传节点发送第一重配置消息；以及
所述源集中单元向无线设备发送第二重配置消息，
所述第二重配置消息中包括目标集中单元的信息以及与所述目标集中单元的信 息对应的所述配置，
所述目标集中单元是指所述集成的接入和回传节点基于所述第一重配置消息将要连接或已经连接的集中单元。
3.一种信号的发送方法，包括：
源集中单元向集成的接入和回传节点发送第一重配置消息；
所述源集中单元向无线设备发送第二重配置消息；以及
向所述集成的接入和回传节点发送对应关系指示信息，
所述对应关系指示信息用于指示：
所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的目标小区的标识信息的对应关系；
所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的配置的标识信息的对应关系；
目标小区与所述第二重配置消息中包括的所述配置的标识信息或所述配置的对应关系。
4.如附记1～3中任一项所述的方法，其中，
所述无线设备是：
终端设备；或
所述集成的接入和回传节点的下一级集成的接入和回传节点。

Claims (20)

  1. 一种信号的接收和发送装置，设置于集成的接入和回传节点，所述信号的接收和发送装置包括：
    第一接收单元，其接收第一重配置消息；以及
    第一发送单元，向无线设备发送指示信息，所述指示信息用于指示所述无线设备应用第二重配置消息中的配置。
  2. 如权利要求1所述的装置，其中，
    所述第一发送单元向所述无线设备发送指示信息的时机为下述时机之一：
    所述集成的接入和回传节点确定条件重配置的相关测量事件被满足时；
    所述集成的接入和回传节点发起条件切换或条件重配置的执行时；
    所述集成的接入和回传节点接收到所述第一重配置消息时；
    所述集成的接入和回传节点从源集中单元或父节点去附着时；
    所述集成的接入和回传节点与新的父节点或目标父节点下行同步时；
    所述集成的接入和回传节点发起到新的父节点或目标父节点的随机接入过程时；
    所述集成的接入和回传节点向新的父节点或目标父节点发送基于所述第一重配置消息的重配置完成消息时；
    所述集成的接入和回传节点随机接入过程成功时；
    所述集成的接入和回传节点收到来自其父节点的针对所述重配置完成消息的确认消息或反馈消息时。
  3. 如权利要求1所述的装置，其中，
    所述指示信息使能或者禁止所述无线设备：
    应用所述第二重配置消息中的配置。
  4. 如权利要求3所述的装置，其中，
    在所述第二重配置消息中，与所述集成的接入和回传节点的当前服务小区具有相同标识的目标候选小区被配置一次。
  5. 如权利要求3所述的装置，其中，
    所述指示信息使能所述无线设备应用所述第二重配置消息中的与当前服务小区具有相同标识的目标候选小区的配置。
  6. 如权利要求1所述的装置，其中，
    所述指示信息指示集中单元的信息，
    所述集中单元是指所述集成的接入和回传节点基于所述第一重配置消息将要连接或已经连接的集中单元。
  7. 如权利要求6所述的装置，其中，
    所述第二重配置消息中包括所述集中单元的信息以及与所述集中单元的信息对应的所述配置。
  8. 如权利要求1所述的装置，其中，
    所述指示信息指示所述无线设备应用的所述配置。
  9. 如权利要求8所述的装置，其中，所述装置还包括：
    第二接收单元，其接收对应关系指示信息，
    所述对应关系指示信息用于指示：
    所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的目标小区的标识信息的对应关系；或者
    所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的配置的标识信息的对应关系；或者
    目标小区与所述第二重配置消息中包括的所述配置的标识信息或所述配置的对应关系。
  10. 如权利要求1所述的装置，其中，
    所述第一发送单元通过回传自适应协议数据单元、无线链路层控制协议数据单元、媒体接入控制控制信元、媒体接入控制子头或物理层信令向所述无线设备发送所述指示信息。
  11. 一种信号的接收装置，设置于无线设备，所述信号的接收装置包括：
    接收单元，其接收第二重配置消息；以及
    第三接收单元，其接收指示信息，
    所述指示信息用于所述无线设备在无线资源控制层应用接收到的所述第二重配置消息中的配置。
  12. 如权利要求11所述的装置，其中，
    所述第三接收单元接收集成的接入和回传节点发送的所述指示信息的时机为下 述时机之一：
    所述集成的接入和回传节点确定条件重配置的相关测量事件被满足时；
    所述集成的接入和回传节点发起条件切换或条件重配置的执行时；
    所述集成的接入和回传节点接收到第一重配置消息时；
    所述集成的接入和回传节点从源集中单元或父节点去附着时；
    所述集成的接入和回传节点与新的父节点或目标父节点下行同步时；
    所述集成的接入和回传节点发起到新的父节点或目标父节点的随机接入过程时；
    所述集成的接入和回传节点向新的父节点或目标父节点时发送基于第一重配置消息的重配置完成消息；
    所述集成的接入和回传节点随机接入过程成功时；
    所述集成的接入和回传节点收到来自其父节点的针对所述重配置完成消息的确认消息或反馈消息时。
  13. 如权利要求11所述的装置，其中，
    所述指示信息使能或者禁止所述无线设备：
    在无线资源控制层应用所述第二重配置消息中的配置。
  14. 如权利要求13所述的装置，其中，
    所述无线设备在无线资源控制层应用所述第二重配置消息中的与当前服务小区具有相同标识的目标候选小区的配置。
  15. 如权利要求11所述的装置，其中，
    所述指示信息指示集中单元的信息，
    所述集中单元是指集成的接入和回传节点基于第一重配置消息将要连接或已经连接的集中单元。
  16. 如权利要求15所述的装置，其中，
    所述第二重配置消息中包括所述集中单元的信息以及与所述集中单元的信息对应的所述配置，
    所述无线设备根据所述指示信息中的所述集中单元的信息，确定所述第二重配置消息中与所述集中单元的信息对应的所述配置，并在无线资源控制层应用所述配置。
  17. 如权利要求11所述的装置，其中，
    所述指示信息指示所述无线设备应用的所述配置。
  18. 如权利要求16所述的装置，其中，
    所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的目标小区的标识信息具有对应关系；或者
    所述第二重配置消息中的所述配置的标识信息与所述第一重配置消息中的配置的标识信息具有对应关系；或者
    目标小区与所述第二重配置消息中包括的所述配置的标识信息或所述配置具有对应关系。
  19. 一种信号的发送装置，设置于源集中单元，所述信号的发送装置包括：
    第四发送单元，其向集成的接入和回传节点发送第一重配置消息；以及
    第五发送单元，其向无线设备发送第二重配置消息，
    其中，在所述第二重配置消息中，与所述集成的接入和回传节点的当前服务小区具有相同标识的目标候选小区被配置一次。
  20. 如权利要求19所述的装置，其中，
    所述无线设备包括：
    终端设备；或
    所述集成的接入和回传节点的下一级集成的接入和回传节点。
PCT/CN2020/122555 2020-10-21 2020-10-21 信号的接收和发送方法、装置和通信系统 WO2022082518A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2020/122555 WO2022082518A1 (zh) 2020-10-21 2020-10-21 信号的接收和发送方法、装置和通信系统
JP2023522374A JP2023545801A (ja) 2020-10-21 2020-10-21 信号の送受信方法、装置及び通信システム
CN202080106036.1A CN116326161A (zh) 2020-10-21 2020-10-21 信号的接收和发送方法、装置和通信系统
US18/133,805 US20230247514A1 (en) 2020-10-21 2023-04-12 Method and apparatus for receiving and transmitting signals and a communication system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/122555 WO2022082518A1 (zh) 2020-10-21 2020-10-21 信号的接收和发送方法、装置和通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/133,805 Continuation US20230247514A1 (en) 2020-10-21 2023-04-12 Method and apparatus for receiving and transmitting signals and a communication system

Publications (1)

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

Family

ID=81291424

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/122555 WO2022082518A1 (zh) 2020-10-21 2020-10-21 信号的接收和发送方法、装置和通信系统

Country Status (4)

Country Link
US (1) US20230247514A1 (zh)
JP (1) JP2023545801A (zh)
CN (1) CN116326161A (zh)
WO (1) WO2022082518A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024026803A1 (zh) * 2022-08-04 2024-02-08 富士通株式会社 移动节点的配置方法和宿主设备
WO2024074514A1 (en) * 2022-10-05 2024-04-11 Canon Kabushiki Kaisha Method and apparatus for use in managing conditional handover in a sidelink relay network

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220225060A1 (en) * 2021-01-14 2022-07-14 Qualcomm Incorporated Selective forwarding of rrc reconfiguration messages in iab

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质
CN111148163A (zh) * 2018-11-02 2020-05-12 华为技术有限公司 通信方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111148163A (zh) * 2018-11-02 2020-05-12 华为技术有限公司 通信方法及装置
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CATT: "Group Handover in Inter IAB donor-CU", 3GPP DRAFT; R3-204733, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915622 *
HUAWEI, HISILICON: "Consideration of inter-CU migration", 3GPP DRAFT; R2-2007863, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051912485 *
HUAWEI: "Inter IAB donor-CU topology adaptation", 3GPP DRAFT; R3-200763, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20200224 - 20200306, 14 February 2020 (2020-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051854207 *
ZTE, SANECHIPS: "Discussion on network-controlled IAB migration handling", 3GPP DRAFT; R3-190542 DISCUSSION ON NETWORK-CONTROLLED IAB MIGRATION HANDLING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Athens, Greece; 20190225 - 20190301, 15 February 2019 (2019-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051604480 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024026803A1 (zh) * 2022-08-04 2024-02-08 富士通株式会社 移动节点的配置方法和宿主设备
WO2024074514A1 (en) * 2022-10-05 2024-04-11 Canon Kabushiki Kaisha Method and apparatus for use in managing conditional handover in a sidelink relay network

Also Published As

Publication number Publication date
JP2023545801A (ja) 2023-10-31
US20230247514A1 (en) 2023-08-03
CN116326161A (zh) 2023-06-23

Similar Documents

Publication Publication Date Title
US11140676B2 (en) Data transmission method, terminal device, and access network device
EP3493601B1 (en) Selecting a network slice
JP7433488B2 (ja) 無線アクセスネットワーク通知エリア（ｒｎａ）更新の拒否時の構成を処理するための方法および装置
WO2022082518A1 (zh) 信号的接收和发送方法、装置和通信系统
US20200077287A1 (en) Apparatus, method and computer program
US10420117B2 (en) Bearer establishment method, user equipment, and base station
WO2018121616A9 (zh) 一种双连接方法及接入网设备
JP2019527006A (ja) 報告受信方法及びネットワーク装置、並びに報告実行方法及び基地局
US11019543B2 (en) Methods and system for managing handover procedure in a radio access network
WO2010048835A1 (zh) 一种资源配置的方法、装置和系统
US20220014901A1 (en) Method and apparatus for identifying user equipment capability in sidelink transmission
CN113038590B (zh) 时间同步方法、电子设备及存储介质
JP2021532644A (ja) ダウンリンク信号の監視方法、送信方法、パラメータ構成方法及び装置
US20160021591A1 (en) Data transmission method, communications device, and communications system
JP2021510950A (ja) 媒体アクセス制御層の制御要素の確認方法、装置及び通信システム
US20230354136A1 (en) Integrated access and backhaul communication method and apparatus
US20230254729A1 (en) Migration method and apparatus for iab-node
WO2021056702A1 (zh) 上行信号的发送和接收方法以及装置
CN112262610B (zh) 装置、方法和计算机程序
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
JP7486397B2 (ja) プライマリセル変更のための方法、デバイス及びコンピュータプログラム
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2023130368A1 (zh) 收发信息的方法、装置和通信系统
JP7276416B2 (ja) セル設定装置及び方法
WO2022205252A1 (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: 20958101

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023522374

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20958101

Country of ref document: EP

Kind code of ref document: A1