WO2022205485A1 - Procédé et appareil d'envoi et de réception d'informations - Google Patents

Procédé et appareil d'envoi et de réception d'informations Download PDF

Info

Publication number
WO2022205485A1
WO2022205485A1 PCT/CN2021/085474 CN2021085474W WO2022205485A1 WO 2022205485 A1 WO2022205485 A1 WO 2022205485A1 CN 2021085474 W CN2021085474 W CN 2021085474W WO 2022205485 A1 WO2022205485 A1 WO 2022205485A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
node
rlc channel
backhaul rlc
backhaul
Prior art date
Application number
PCT/CN2021/085474
Other languages
English (en)
Chinese (zh)
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/CN2021/085474 priority Critical patent/WO2022205485A1/fr
Publication of WO2022205485A1 publication Critical patent/WO2022205485A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path

Definitions

  • the embodiments of the present application relate to the field of communication technologies.
  • IAB Integrated access and backhaul
  • NG-RAN next generation radio access network
  • IAB-node An integrated access and backhaul node
  • NR New Radio
  • IAB-donor represents a network device (eg, gNB) that supports IAB functionality.
  • An IAB node can connect to an IAB host (IAB-donor) through one or more hops. These multi-hop connections form a Directed Acyclic Graph (DAG) topology with the IAB host as the root node.
  • DAG Directed Acyclic Graph
  • the IAB host is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.
  • 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 connection to the terminal equipment (UE) and the next hop IAB-node. The endpoint of the incoming (NR access) interface is also the endpoint of the F1 protocol to the gNB-CU (central unit) on the IAB-donor.
  • the IAB-DU can serve normal UEs and IAB sub-nodes.
  • IAB-MT mobile termination
  • IAB-MT includes such as physical layer, layer 2, radio resource control (radio resource control, RRC) layer and Non-access stratum (NAS) layer functions to connect to the gNB-DU of another IAB-node or IAB-donor, to the gNB-CU on the IAB-donor and to the core network.
  • IAB-MT can support functions such as UE physical layer, access stratum (AS), radio resource control (RRC) layer and non-access stratum (NAS) layer, and can be connected to the IAB parent node.
  • AS access stratum
  • RRC radio resource control
  • NAS non-access stratum
  • FIG. 1 is a schematic diagram of the IAB topology.
  • the IAB-node 100 includes the IAB-MT functional unit 101 and the IAB-DU functional unit 102, and the previous neighbor node of the IAB-MT is called the IAB parent node, as shown in FIG. 1 .
  • the parent nodes 301 and 302 shown, the IAB-MT functional unit 101 and the parent nodes 301 and 302 can communicate through the air interface (Uu), and the next-hop neighbor node of the IAB-DU is called the IAB child node (child node).
  • the sub-nodes 201, 202, 203 shown in FIG. 1 the IAB-DU functional unit 102 and the sub-nodes 201, 202, 203 can communicate through the air interface (Uu).
  • 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 .
  • BAP Backhaul Adaptation Protocol
  • the BAP sublayer is located under the network protocol IP layer above the RLC sublayer, and supports functions such as packet destination node and path selection, packet routing and forwarding, bearer mapping, flow control feedback, and return link failure notification.
  • the IAB node in order to realize the relay and forwarding of the data packet, the IAB node needs to determine the destination node to which the data packet arrives, and then determines the next hop node corresponding to the destination node according to the routing table and sends it. After the data packet reaches the next hop node, the next hop node needs to further look up the routing table to determine the next hop node that reaches the destination node, until the data packet is sent to the destination node.
  • the IAB introduces the concept of the backhaul radio link control channel (BH RLC channel) on the backhaul link.
  • the control signaling and user plane data encapsulated into BAP PDU are transmitted between the IAB-MT and the IAB parent node through the BH RLC channel.
  • the BH RLC channel is only used for data forwarding on the backhaul link.
  • a scheme of topology redundancy between hosts is proposed, that is, when an IAB-donor-CU has too much service traffic in the topology network managed by itself, it can offload some services to another.
  • the topology network managed by the donor-CU that is, data transmission is carried out through redundant paths.
  • intra-host intra-host
  • intra-CU intra-host
  • BH RLC channel mapping in the same host
  • All are managed and configured by the donor-CU of this topology.
  • bearer mapping and/or channel mapping configuration across topologies (controlled by different donor-CUs).
  • embodiments of the present application provide a method and apparatus for sending and receiving information.
  • an apparatus for sending and receiving information is provided, which is applied to a first IAB host node, including:
  • a first sending unit configured to send a first message to the second IAB host node, where the first message includes the backhaul RLC channel identifier on the third IAB node and/or the number of reserved backhaul RLC channels and/or the number of reserved backhaul RLC channels. in first indication information indicating whether at least two radio bearers are sharing the same backhaul RLC channel;
  • a first configuration unit which configures a backhaul RLC channel mapping relationship for IAB nodes in its topology.
  • an apparatus for sending and receiving information is provided, which is applied to a second IAB host node, including:
  • the second receiving unit which receives the first message sent by the first IAB host node, where the first message includes the backhaul RLC channel identifier on the third IAB node and/or the number of reserved backhaul RLC channels and/or the number of backhaul RLC channels reserved and/or used for first indication information indicating whether at least two radio bearers are sharing the same backhaul RLC channel;
  • the second configuration unit which configures the backhaul RLC channel mapping relationship for the IAB nodes in its topology.
  • an apparatus for sending and receiving information is provided, which is applied to a second IAB host node, including:
  • the fourth sending unit which sends first mapping relationship information to the fifth node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the mapping between the ingress backhaul RLC channel and the egress backhaul RLC channel relation;
  • each radio bearer on the fifth node is mapped to different backhaul RLC channels.
  • the first IAB host node notifies the second IAB host node of the backhaul RLC channel identifier and/or the number of reserved backhaul RLC channels on the third IAB node and/or used to indicate Whether at least two radio bearers are sharing the first indication information of the same backhaul RLC channel, so that the second IAB host node configures the bearer channel mapping relationship according to the first message, thereby realizing the bearer across topologies (controlled by different donor-CUs)
  • the mapping and/or channel mapping configuration supports topology redundancy between hosts in the IAB network, thereby achieving load balancing between hosts, increasing network robustness, and optimizing network performance.
  • One of the beneficial effects of the embodiments of the present application is that one ingress backhaul RLC channel on the border IAB node is not mapped to different egress backhaul RLC channels, thereby avoiding the border IAB node when the egress backhaul channel is mapped Channels cannot be split, so as to achieve load balancing between hosts, increase network robustness, and optimize network performance.
  • each radio bearer on the ancestor node of the border IAB node is mapped to different backhaul RLC channels. This avoids that different bearers are always mapped to the same BH RLC channel, and avoids the inability to distinguish the QoS of wireless bearers, so as to achieve load balancing between hosts, increase network robustness, and optimize network performance without affecting network transmission efficiency.
  • Fig. 1 is a schematic diagram of an IAB topology structure of an embodiment of the present application
  • FIG. 2 is a schematic diagram of a topology redundant network structure between hosts according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of a topology redundant transmission path between hosts according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of downlink topology redundant data transmission according to an embodiment of the present application.
  • 5 is a schematic diagram of downlink topology redundant data transmission according to an embodiment of the present application.
  • FIG. 6 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 7 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 8 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 9 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 10 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 11 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 12 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 13 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 14 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • 15A is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • 15B is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 16 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • 17 is another schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 18 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • FIG. 19 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • FIG. 21 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • FIG. 22 is another schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • FIG. 23 is another schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • FIG. 24 is another schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • FIG. 25 is another schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • FIG. 26 is another schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • FIG. 27 is a schematic diagram of a network device according to an embodiment of the present application.
  • FIG. 28 is a schematic diagram of a terminal device according to an embodiment 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 Long Term Evolution (LTE, Long Term Evolution), Long Term Evolution Enhanced (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), high-speed message access (HSPA, High-Speed Packet Access) and so on.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Enhanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA 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: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobility 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.
  • 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 (such as femeto, pico, etc.), IAB (Integrated Access and Backhaul) node or IAB-DU or IAB-donor.
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low power node such as femeto, pico, etc.
  • IAB Integrated Access and Backhaul node or IAB-DU or IAB-donor.
  • 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 terms “cell”
  • 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.
  • Terminal equipment may be fixed or mobile, and may also be referred to as Mobile Station (MS, Mobile Station), Terminal, Subscriber Station (SS, Subscriber Station), Access Terminal (AT, Access Terminal), IAB-MT, Station (station), etc.
  • 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 or “network device side” refers to the 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.
  • equipment may refer to network equipment or terminal equipment.
  • Inter-donor topology redundancy or inter-CU topology redundancy
  • Figure 2 is a schematic diagram of the topology redundant network structure between hosts:
  • Scenario 1 There are multiple connections between the IAB node and 2 hosts.
  • the IAB node 3 in Figure 2 is connected to both donor-CU1 and donor-CU2.
  • Scenario 2 The parent node/ancestor node of the IAB node has multiple connections to two hosts at the same time. As shown in IAB node 4 in Figure 2, its parent node is connected to both donor-CU1 and donor-CU2. It may not be shown in FIG. 2. For example, there are multiple nodes between IAB node 3 and IAB node 4 for multi-hop connection, so that IAB node 4 still belongs to this scenario and can support topology redundancy between hosts.
  • the IAB node 3 is called a boundary IAB node.
  • a border IAB node is connected to two or more parent nodes that are respectively connected to different donor-CUs.
  • a descendant IAB node refers to a node connected to the network through a border IAB node, and each IAB node is singly connected to its own parent node, such as IAB node 4 .
  • An F1-termination node refers to a donor-CU that terminates the F1 interface of a border IAB node and a descendant IAB node, such as donor-CU1.
  • a non-F1-termination node refers to a CU with a host function that does not terminate the F1 interface of the border IAB node and the descendant IAB node, such as donor-CU2.
  • topology redundancy The main purpose of topology redundancy is to perform load balancing of services.
  • the host that terminates the F1 interface initiates service offloading to other hosts.
  • IAB-donor-CU1 has too much service traffic in the topology network managed by itself, it can offload some services to the topology network managed by donor-CU2, that is, data transmission is performed through redundant paths. That is, the F1 interfaces of the border IAB node and its descendant IAB nodes are terminated to the same host.
  • FIG. 3 is a schematic diagram of a topology redundant transmission path between hosts.
  • the donor-CU1 is the F1 termination host of the IAB node 4 .
  • Some data between IAB node 4 and donor-CU1 is transmitted through the topology network controlled by donor-CU1 (as shown by solid arrows), and some data is transmitted through the topology network controlled by donor-CU2 (as shown by dashed arrows) ), so as to realize the purpose of data distribution and load balancing.
  • the IAB network supports two bearer mapping mechanisms from the data radio bearer (DRB) to the BH RLC channel when forwarding the user plane data packets of the UE.
  • DRB data radio bearer
  • One is 1:1 bearer mapping, which means that each UE DRB can be mapped to an independent BH RLC channel, and the BH RLC channel corresponding to the UE DRB continues to be mapped to an independent BH RLC channel at the next hop.
  • the other is N:1 bearer mapping, which means that multiple UE DRBs can be mapped to one BH RLC channel.
  • N:1 bearer mapping which means that multiple UE DRBs can be mapped to one BH RLC channel.
  • several UE DRBs with similar QoS can be mapped to the same BH RLC channel, while UE DRBs with relatively large QoS differences are mapped to different BH RLC channels.
  • DRBs from different UEs can also be mapped to the same BH RLC channel of the backhaul link
  • Intra-CU intra-host
  • the existing intra-host (intra-CU) topology redundancy process can be used to establish and release redundant paths in the IAB topology under the same IAB-donor-CU.
  • the BH RLC channel mapping in the same host is performed by this topology.
  • FIG. 4 is a schematic diagram of uplink topology redundant data transmission.
  • IAB node 3 is a border IAB node
  • IAB node 4 is its child node.
  • the master cell group (MCG) parent link of IAB node 3 is finally connected to the F1 termination donor that is IAB node 3 and IAB node 4, and the secondary cell group (SCG) parent node is connected Non-F1-terminated donors that are ultimately connected to them.
  • Other nodes as well as the IAB donor node are omitted in Figure 3.
  • In a topology with an F1-terminated donor configuration of a border node if multiple bearers are mapped to the same ingress BH RLC channel of a border IAB node, and in a topology with a non-F1-terminated donor configuration of a border node, these bearers are Different egress BH RLC channels mapped to border IAB nodes. In this case, the boundary IAB node cannot make BH RLC channel mapping.
  • Figure 5 is a schematic diagram of redundant data transmission in the downlink topology.
  • the donor In the topology of the non-F1-terminated donor configuration of the border node, if multiple bearers are mapped to the same ingress BH RLC channel of the border IAB node, the donor is terminated at the F1.
  • these bearer at the border IAB node can only be mapped to the same egress (egress) BH RLC channel. In this case, these bearers will always be mapped to the same BH RLC channel in the multiple hops behind the border IAB node, which makes it impossible to distinguish the QoS of wireless bearers and affects the network transmission efficiency.
  • the first IAB host node notifies the second IAB host node of the backhaul RLC channel identifier and/or the number of reserved backhaul RLC channels on the third IAB node and/or used to indicate at least two Whether the radio bearers are sharing the first indication information of the same backhaul RLC channel, so that the second IAB host node configures the bearer channel mapping relationship according to the first message, so as to realize the bearer mapping and/or cross topology (controlled by different donor-CUs) Or channel mapping configuration, supports topology redundancy between hosts in the IAB network, so as to achieve load balancing between hosts, increase network robustness, and optimize network performance.
  • each radio bearer on the ancestor node of the border IAB node is mapped to different backhaul RLC channels. This avoids that different bearers are always mapped to the same BH RLC channel, and avoids the inability to distinguish the QoS of wireless bearers, so as to achieve load balancing between hosts, increase network robustness, and optimize network performance without affecting network transmission efficiency.
  • FIG. 6 is a schematic diagram of the method for sending and receiving information according to an embodiment of the present application, which is described from the side of the first IAB host node (the F1 termination node of the border node), as shown in FIG. 6 ,
  • the method includes:
  • the first IAB host node sends a first message to the second IAB host node, where the first message includes the backhaul RLC channel identifier on the third IAB node and/or the number of reserved backhaul RLC channels and/or the number of backhaul RLC channels reserved and/or used for.
  • first indication information indicating whether at least two radio bearers share the same backhaul RLC channel;
  • the first IAB host node configures the backhaul RLC channel mapping relationship for the IAB nodes in its topology.
  • FIG. 7 is a schematic diagram of a method for sending and receiving information according to an embodiment of the present application, which is described from the side of an IAB host node (non-F1 terminating node). As shown in FIG. 7 , the method includes:
  • the second IAB host node receives a first message sent by the first IAB host node, where the first message includes the backhaul RLC channel identifier on the third IAB node and/or the reserved backhaul RLC channel number and/or use The first indication information indicating whether at least two radio bearers share the same backhaul RLC channel.
  • the second IAB host node configures the backhaul RLC channel mapping relationship for the IAB nodes in its topology.
  • the first IAB host node is the F1-terminated host node of the border node and its descendant nodes, such as donor-CU1, that is, the donor-CU that initiates traffic offloading
  • the second IAB host node is the border node and its descendants.
  • the second IAB host node can be one or at least two, that is, the cross topology can be cross two
  • the topology may also span multiple topologies, which is not limited in this embodiment of the present application.
  • the IAB node in the host node refers to that the DU part of the IAB node is managed by the donor-CU, that is, the IAB node F1 interface is terminated to the donor-CU.
  • the third IAB node is a border IAB node (eg, IAB node 3 shown in Figure 4), which is dual-connected to the first IAB host node and the second IAB host node.
  • the implementation of the aforementioned 602-702 can refer to the prior art, that is, for the midway IAB node of data forwarding in the topology, the IAB host node configures the mapping relationship from the ingress BH RLC channel to the egress BH RLC channel, wherein the ingress BH RLC channel refers to the mapping relationship.
  • the forwarding IAB node receives the BH RLC channel of the returned data packet, and the outgoing BH RLC channel refers to the BH RLC channel that the forwarding IAB node sends the returned data packet.
  • the mapping relationship of the configuration is carried through F1AP signaling, and sent to the corresponding IAB node.
  • the backhaul RLC channel identifier in the foregoing first message is the backhaul channel identifier mapped by the radio bearer at the third IAB node.
  • the radio bearer is a radio bearer that the first IAB host node performs traffic offloading to the second IAB host node.
  • the backhaul RLC channel identifier is an ingress channel identifier; when the radio bearer is uplink data, the backhaul RLC channel identifier is an egress channel identifier.
  • FIG. 8 is a schematic diagram of the method for sending and receiving information. As shown in FIG. 8 , the method includes:
  • the first IAB host node sends a first message to the second IAB host node, where the first message includes an egress return RLC channel identifier on the third IAB node.
  • the backhaul RLC channel identifier may be the previous radio bearer (the first radio bearer) at the egress BH RLC channel identifier of the third IAB node.
  • the egress BH RLC channel identifier refers to the BH RLC channel identifier of the data packet sent back by the third IAB node, and the egress BH RLC channel identifier of the previous radio bearer at the third IAB node is allocated and allocated by the second IAB host node for the previous radio bearer. Sent to the first IAB host node, that is, the method further includes:
  • the first IAB host node receives a second message sent by the second IAB host node, where the second message includes the egress BH RLC channel identifier of the previous wireless bearer on the third IAB node.
  • the first IAB host node when the aforementioned at least two radio bearers are mapped to the same ingress BH RLC channel of the child node link of the third node, after receiving the previous radio bearer After the egress on the border IAB node sends back the RLC channel identifier, and before the topology redundancy transmission of the latter radio bearer is performed, the first IAB host node sends the second IAB host node to the second IAB host node containing the egress echo on the third IAB node The first message of the RLC channel identification.
  • the first message and/or the second message may be carried by XnAP signaling, for example, by using an existing message or a newly created message in XnAP signaling, which is not limited in this embodiment of the present application.
  • the method may also include:
  • the second IAB host node determines the egress backhaul RLC channel for the second radio bearer according to the first message, so that the second radio bearer is mapped to the egress in the first message on the MT side of the third IAB node
  • the backhaul RLC channel identifier corresponds to the backhaul RLC channel.
  • the second host node can configure/reconfigure the backhaul RLC channel correspondingly according to the QoS requirements of the second radio bearer, for example, the BH RLC channel of the MT end of the third IAB node can be configured/reconfigured through an RRC message. QoS configuration is performed, and the second radio bearer is mapped to the backhaul RLC channel corresponding to the egress backhaul RLC channel identifier in the first message at the MT end of the third IAB node.
  • the first IAB host node configures the mapping relationship information from the radio bearer initiated by the fourth IAB node to the backhaul RLC channel (for example, bearer through F1AP signaling), so that the second radio bearer transmitted later It is also mapped to the ingress BH RLC channel of the ingress link of the first radio bearer on the third IAB node previously transmitted, and the third IAB node is configured (for example, carried by F1AP signaling), the ingress BH RLC channel and the third IAB node are configured.
  • the egress in a message returns the RLC channel for mapping (one-to-one correspondence).
  • the aforementioned at least two radio bearers are data radio bearers or signal radio bearers, which are not limited in the embodiments of the present application.
  • FIG. 9 is a schematic diagram of the method for sending and receiving information. As shown in FIG. 9 , the method includes:
  • the first IAB host node sends a first message to the second IAB host node, where the first message includes first indication information for indicating whether at least two radio bearers share the same egress backhaul RLC channel.
  • the at least two radio bearers are radio bearers that the first IAB host node performs traffic offloading to the second IAB host node, and within the topology of the first IAB host node, the at least two radio bearers ( In the following example referred to as the topology redundant path of the first radio bearer and the second radio bearer), the first indication information indicates whether at least two radio bearers share the same backhaul RLC channel, and the backhaul RLC channel is the egress BH RLC channel.
  • the first indication information may be a 1-bit value.
  • the 1-bit value is 1, it indicates that the same egress BH RLC channel is shared.
  • the 1-bit value is 0, it indicates that the same egress BH RLC channel is not shared.
  • egress BH RLC channel or use a different egress BH RLC channel, and vice versa.
  • the first indication information is included in the first message, it means that the same exit BH RLC channel is shared, and when the first indication information is not included, it means that the same exit BH RLC channel is not shared, and vice versa.
  • the example is not intended to be limiting.
  • the method may also include:
  • the second IAB host node determines the egress backhaul RLC channel for the at least two radio bearers according to the first message, so that the at least two data radio bearers share or do not share the third IAB node MT-side link (that is, the uplink). The same egress of the egress link) returns the RLC channel.
  • the second IAB host node may perform QoS configuration on the BH RLC channel of the MT end of the third IAB node through an RRC message, for example, the first indication information indicates at least two When the radio bearers share the same egress backhaul RLC channel, configure at least two radio bearers to map to the same egress backhaul RLC channel, and configure at least two radio bearers when the first indication information indicates that at least two radio bearers do not share the same egress backhaul RLC channel.
  • the two radio bearers are mapped to different egress backhaul RLC channels.
  • the method may also include:
  • the first IAB host node receives a second message sent by the second IAB host node, where the second message includes an egress return RLC channel identifier configured by the second IAB host node for the radio bearer on the third IAB node.
  • the first indication information indicates that at least two radio bearers share the same egress backhaul RLC channel
  • the backhaul RLC channel identifier is included in the second message and sent to the first IAB host node
  • the first message and/or the second message may be carried by XnAP signaling, for example, by using an existing message or a newly created message in XnAP signaling, which is not limited in this embodiment of the present application.
  • Figure 10 is a schematic diagram of the method for sending and receiving information. As shown in Figure 10, the method includes:
  • the first IAB host node sends a first message to the second IAB host node, where the first message includes an ingress return RLC channel identifier on the third IAB node.
  • the backhaul RLC channel identifier may be the previous radio bearer (the first radio bearer) in the entry BH RLC channel identifier of the third IAB node, the The ingress BH RLC channel identifier refers to the BH RLC channel identifier that the third IAB node receives the backhaul data packet, and the ingress BH RLC channel identifier of the previous radio bearer on the third IAB node is allocated and allocated by the second IAB host node for the previous radio bearer. Sent to the first IAB host node, that is, the method further includes:
  • the first IAB host node receives a second message sent by the second IAB host node, where the second message includes the ingress BH RLC channel identifier of the previous wireless bearer on the third IAB node.
  • the first IAB host node when the aforementioned at least two radio bearers are mapped to the same egress BH RLC channel of the child node link of the third node, the previous radio bearer is transmitted when the After the topology redundancy transmission of the first IAB node, and before the topology redundancy transmission of the next radio bearer, the first IAB host node sends a first message including the ingress return RLC channel identifier on the third IAB node to the second IAB host node.
  • the first message and/or the second message may be carried by XnAP signaling, for example, by using an existing message or a newly created message in XnAP signaling, which is not limited in this embodiment of the present application.
  • the method may also include:
  • the second IAB host node configures the bearer channel mapping relationship according to the first message (for example, for the parent node and each ancestor node configuration of the border IAB node, for example, sends the bearer channel mapping relationship to the fifth node of the third aspect embodiment) , so that the second radio bearer is mapped to the backhaul RLC channel corresponding to the backhaul RLC channel identifier in the first message.
  • the first message for example, for the parent node and each ancestor node configuration of the border IAB node, for example, sends the bearer channel mapping relationship to the fifth node of the third aspect embodiment
  • the second IAB host node after receiving the first message, configures the mapping relationship information of each radio bearer to the backhaul RLC channel (for example, bearer through F1AP signaling), the mapping relationship makes the second radio bearer It is mapped to the backhaul RLC channel corresponding to the backhaul RLC channel identifier in the first message, so that the second radio bearer transmitted later is also mapped to the first radio bearer transmitted previously in the entry BH RLC of the third IAB node. Therefore, the topology network managed by each host node can achieve a relatively consistent QoS control level for radio bearers.
  • the aforementioned at least two radio bearers are data radio bearers or signal radio bearers, which are not limited in the embodiments of the present application.
  • FIG. 11 is a schematic diagram of the method for sending and receiving information. As shown in FIG. 11 , the method includes:
  • the first IAB host node sends a first message to the second IAB host node, where the first message includes first indication information for indicating whether at least two radio bearers share the same entry backhaul RLC channel.
  • the at least two radio bearers are radio bearers that the first IAB host node performs traffic offloading to the second IAB host node, and within the topology of the first IAB host node, the at least two radio bearers ( When the following example is referred to as the topology redundant path of the first radio bearer and the second radio bearer), the first indication information indicates whether at least two radio bearers share the same backhaul RLC channel, and the backhaul RLC channel is the ingress BH RLC channel.
  • the first indication information may be a 1-bit value.
  • the 1-bit value is 1, it indicates that the same ingress BH RLC channel is shared.
  • the 1-bit value is 0, it indicates that the same ingress BH RLC channel is not shared. Ingress BH RLC channel, or use a different ingress BH RLC channel, and vice versa.
  • the first indication information is included in the first message, it means that the same entry BH RLC channel is shared, and when the first indication information is not included, it means that the same entry BH RLC channel is not shared, and vice versa.
  • the example is not intended to be limiting.
  • the method may also include:
  • the second IAB host node configures the bearer channel mapping relationship according to the first message (for example, for the parent node and each ancestor node configuration of the border IAB node, for example, sending the bearer channel mapping relationship to the fifth node of the third aspect embodiment) , so that at least two data radio bearers share or do not share the same ingress backhaul RLC channel.
  • the second IAB host node after receiving the first message, configures the mapping relationship information of each radio bearer to the backhaul RLC channel (for example, bearer through F1AP signaling), in the mapping relationship, at least two Each radio bearer is configured with the corresponding ingress BH RLC channel. For example, when the first indication information indicates that at least two radio bearers share the same ingress backhaul RLC channel, configure at least two radio bearers to map to the same ingress backhaul RLC channel. When the first indication information indicates that at least two radio bearers do not share the same ingress backhaul RLC channel, the at least two radio bearers are configured to be mapped to different ingress backhaul RLC channels.
  • the method may also include:
  • the first IAB host node receives a second message sent by the second IAB host node, where the second message includes an ingress return RLC channel identifier configured by the second IAB host node for the radio bearer on the third IAB node.
  • the at least two radio bearers when the first indication information indicates that at least two radio bearers share the same backhaul RLC channel, the at least two radio bearers are configured to be mapped to the same ingress backhaul RLC channel, and the configured same ingress backhaul RLC channel is configured.
  • the transmission RLC channel identifier is included in the second message and sent to the first IAB host node; when the first indication information indicates that at least two radio bearers do not share the same entry backhaul RLC channel, configure at least two radio bearers to map to different entries
  • the RLC channel is returned, and the identifiers of the previously configured different entry return RLC channels are included in the second message and sent to the first IAB host node.
  • the first message and/or the second message may be carried by XnAP signaling, for example, by using an existing message or a newly created message in XnAP signaling, which is not limited in this embodiment of the present application.
  • Figure 12 is a schematic diagram of the method for sending and receiving information. As shown in Figure 12, the method includes:
  • the second IAB host node receives a first message sent by the first IAB host node, where the first message includes the reserved number of backhaul RLC channels;
  • the second IAB host node configures the bearer channel mapping relationship according to the first message (for example, for the parent node and each ancestor node configuration of the border IAB node, for example, sending the bearer channel mapping relationship to the fifth node of the third aspect embodiment) , so that the number of backhaul RLC channels mapped by the radio bearer at the third IAB node is less than or equal to the reserved number of backhaul RLC channels.
  • the first IAB host node will reserve some number of egress backhaul RLC channels on the third IAB node for radio bearers transmitted over redundant paths; the first IAB host node will reserve the reserved egress backhaul The number of RLC channels is informed to the second IAB host node through the first message.
  • the second IAB host node after receiving the first message, configures the mapping relationship information of each radio bearer to the backhaul RLC channel (for example, bearer through F1AP signaling).
  • the radio bearer is the radio bearer that the first IAB host node performs traffic offloading to the second IAB host node.
  • the number of ingress BH RLC channels mapped by the third IAB node for each radio bearer does not exceed the reserved number of BH RLC channels. Returns the number of RLC channels.
  • the first IAB host node notifies the second IAB host node of the backhaul RLC channel identifier and/or the number of reserved backhaul RLC channels on the third IAB node and/or used to indicate at least two radio bearers Whether the first indication information of whether the same backhaul RLC channel is being shared, so that the second IAB host node configures the bearer channel mapping relationship according to the first message, thereby realizing bearer mapping and/or channels across topologies (controlled by different donor-CUs)
  • the mapping configuration supports topology redundancy between hosts in the IAB network, so as to achieve load balancing between hosts, increase network robustness, and optimize network performance.
  • FIG. 13 is a schematic diagram of the method for sending and receiving information according to an embodiment of the present application. The description is from the side of the IAB host node (F1 termination node), and for uplink redundant path transmission, as shown in FIG. 13 shown, the method includes:
  • the first IAB host node sends first mapping relationship information to the third IAB node and/or the sixth IAB node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC The mapping relationship between the channel and the egress backhaul RLC channel; so that one ingress backhaul RLC channel on the third IAB node will not be mapped to a different egress backhaul RLC channel.
  • the first IAB host node may configure or reconfigure the mapping on each link, and configure the first mapping relationship information to be sent to the third IAB node and/or the sixth IAB node
  • the third IAB node refers to the border IAB node
  • the sixth IAB node may be the fourth IAB node serving as the access IAB node
  • the sixth IAB node refers to the border IAB node
  • the IAB node between the fourth IAB node and the fourth IAB node is not limited in this embodiment of the present application.
  • the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel
  • the sixth IAB node is the IAB between the border IAB node and the fourth IAB node node, or for the third IAB node
  • the first mapping relationship information indicates the mapping relationship between the ingress backhaul RLC channel and the egress backhaul RLC channel, that is, for the access IAB node
  • the first mapping relationship indicates the radio bearer
  • the mapping relationship with the backhaul RLC channel, for the intermediate IAB node of data forwarding the first mapping relationship indicates the mapping relationship between the ingress backhaul RLC channel and the egress backhaul RLC channel.
  • the first mapping relationship is such that one ingress backhaul RLC channel on the third IAB node is not mapped to a different egress backhaul RLC channel, that is, the ingress backhaul RLC channel on the border IAB node After receiving the radio bearer, when transmitting again, it will not be split into different egress backhaul RLC channels, that is, there will be no 1:N channel mapping (N greater than 1) on the border IAB node.
  • 1:N channel mapping means that one ingress BH RLC channel is mapped to multiple egress BH RLC channels.
  • the method may also include:
  • the first IAB host node receives a second message sent by the second IAB host node, where the second message includes the egress BH RLC channel identifier of the third IAB node.
  • the second IAB host node when the uplink data needs to be transmitted using the redundant path between the hosts, the second IAB host node includes its configured egress BH RLC channel identifier on the third IAB node in the second message and sends it to The first IAB host node, after receiving the second message (for example, carried by XnAP signaling), the first IAB host node executes 1301.
  • the first IAB donor node may configure or reconfigure the mapping of the current radio bearer and/or other radio bearers and/or other backhaul RLC channels, as illustrated in the following examples.
  • the configured first mapping relationship information is: The mapping relationship between the radio bearer and the backhaul RLC channel:
  • the egress link ID (egress link ID) used
  • the egress returns the RLC channel Identifies (egress BH RLC channel ID) BH in the UL UP TNL Information to be setup List information element (information element, IE) of the UE Context Setup or UE Context Modification process of the F1AP signaling from gNB-CU to gNB-DU information in IE.
  • IE setup List information element
  • the first IAB host node uses the egress link identifier when configuring the routing identifier corresponding to the Non-UP Traffic Type to the fourth IAB node, and the egress return RLC channel identifier is sent from the gNB-CU Set in the F1Setup Response of the F1AP signaling to the gNB-DU, or the gNB-DU Configuration Update Acknowledge, or the BH information IE in the gNB-CU Configuration Update message.
  • the first mapping relationship information configured by the first IAB host node for the sixth IAB node (the node between the border IAB node and the access IAB node) or the third IAB node is: ingress backhaul RLC channel and egress backhaul
  • the mapping relationship of the RLC channel set by the BAP layer BH RLC channel mapping Information IE in the BAP Mapping Cofiguration process of the F1AP signaling from the gNB-CU to the gNB-DU.
  • one ingress backhaul RLC channel on the third IAB node is not mapped to a different egress backhaul RLC channel.
  • the border IAB node cannot split the channel when the egress backhaul channel is mapped, so as to achieve load balancing between hosts, increase the robustness of the network, and optimize the network performance.
  • FIG. 14 is a schematic diagram of the method for sending and receiving information according to an embodiment of the present application. The description is from the side of the IAB host node (non-F1 terminating node), and for downlink redundant path transmission, as shown in FIG. 14 As shown, the method includes:
  • the second IAB host node sends first mapping relationship information to the fifth node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the relationship between the ingress backhaul RLC channel and the egress backhaul RLC channel. mapping relationship; so that each radio bearer on the fifth node is mapped to different backhaul RLC channels.
  • the fifth node is the ancestor node of the third IAB node (the node at one end of the SCG parent link in FIG. 2 ), such as the IAB node 2 or donor-DU2 in FIG. 3 , in other words, the fifth node Refers to each ancestor node of the third IAB node on the redundant path, which is not limited in this embodiment of the present application.
  • the second IAB host node configures a first mapping relationship for each ancestor node of the third IAB node on the redundant path.
  • the first mapping relationship information Indicates the mapping relationship between the radio bearer and the backhaul RLC channel.
  • the fifth node is the IAB node 2 (when the IAB node between the donor-DU2 and the border IAB node)
  • the first mapping relationship indicates the ingress backhaul RLC channel and the backhaul RLC channel.
  • the egress returns the mapping relationship of the RLC channel.
  • each radio bearer on the fifth node is mapped to different backhaul RLC channels, that is, different radio bearers on each hop link are respectively mapped to On different backhaul RLC channels, that is, the fifth node always uses 1:1 bearer mapping, in which each radio bearer can be mapped to an independent BH RLC channel, and the next hop corresponds to the radio bearer.
  • the BH RLC channel continues to be mapped to the independent BH RLC channel.
  • the third IAB node performs channel mapping, it can be based on the second mapping relationship (the ingress BH RLC channel and the egress) configured by the first IAB host node for the third IAB node.
  • the third IAB node receives the data packet, according to the entry BH RLC channel of the data packet and the mapping relationship, the data packet is delivered to the The corresponding egress BH RLC channel is sent. That is to say, the most fine-grained QoS control is maintained on the redundant topology path.
  • the donor-CU can be terminated by F1 to determine what granular QoS control is used for the remaining paths.
  • the second IAB host node may configure or reconfigure the first mapping relationship to implement 1:1 bearer mapping, as described in the following examples.
  • the second IAB host node configures the fifth node donor-DU2 with BH Information corresponding to the IP header information (which can be regarded as a radio bearer) that requires traffic offloading.
  • the BH Information includes the egress link identifier (that is, the next-hop BAP address) and the egress BH RLC channel identifier.
  • the first mapping relationship (traffic mapping information) can be configured through the IP-to-layer-2 traffic mapping Information List IE in the BAP Mapping Configuration process of the F1AP signaling.
  • the second IAB host node needs to configure each IP header information that needs to be offloaded to correspond to different egress BH RLC channel identifiers.
  • the fifth node donor-DU2 When the fifth node donor-DU2 receives the IP data packet of the first IAB host node, it matches the first IAB host node.
  • the IP header information in the mapping relationship obtains the corresponding link identifier and BH RLC channel identifier.
  • the sending operation is then performed according to the prior art.
  • the configuration of the first mapping relationship is performed on the fifth node (the node between the border IAB node and the donor-DU2). It can be set in the BAP layer BH RLC channel mapping Information IE in the BAP Mapping Cofiguration process of the F1AP signaling from gNB-CU to gNB-DU. It is guaranteed that at each hop, the ingress BH RLC channel corresponding to each bearer that needs to be offloaded is mapped to a different egress BH RLC channel. In this way, at the end of the ingress link of the border IAB node, these different bearers will also be mapped on different ingress BH RLC channels.
  • the method may further include:
  • the second IAB host node receives second indication information sent by the first IAB host node, where the second indication information is used to indicate whether each radio bearer needs to be mapped to different backhaul RLC channels, that is, the second indication information
  • the indication information indicates whether 1:1 bearer mapping is required.
  • the second indication information may be borne by XnAP signaling (for example, by using a new message or an existing message), and the first mapping relationship information may be borne by F1AP signaling, which is not the case in this embodiment of the present application as a limitation.
  • each radio bearer on the fifth node is mapped to different backhaul RLC channels. This avoids that different bearers are always mapped to the same BH RLC channel, and avoids the inability to distinguish the QoS of wireless bearers, so as to achieve load balancing between hosts, increase network robustness, and optimize network performance without affecting network transmission efficiency.
  • This embodiment of the present application provides a method for sending and receiving information, which is described from a third IAB node.
  • FIG. 15A is a schematic diagram of the method for sending and receiving information. As shown in FIG. 15A, the method includes:
  • the third IAB node receives the default configuration information sent by the first IAB host node or the second IAB host node, where the default configuration information configures the default egress return RLC channel of the redundant link in the uplink direction.
  • the method when the first IAB host node does not receive the second message from the second IAB host node, or when 1:N bearer mapping occurs during uplink channel mapping, the method further includes:
  • the third IAB node uses the default configuration information to determine that the bearer is mapped to the default egress backhaul RLC channel.
  • the default configuration information may be carried by F1AP signaling or RRC signaling.
  • the default configuration information may be carried by F1AP signaling sent by the first IAB donor node, or may be carried by RRC signaling sent by the second IAB donor node.
  • An embodiment of the present application provides a method for sending and receiving information, which is described from the side of the first IAB host node or the second IAB host node.
  • FIG. 15B is a schematic diagram of the method for sending and receiving information. As shown in FIG. 15B , the method includes:
  • the first IAB host node or the second IAB host node sends default configuration information to the third IAB node, where the default configuration information configures the default egress of the redundant link in the uplink direction to return the RLC channel.
  • the third IAB node uses the missing message.
  • the provincial configuration information determines that the bearer is mapped to the default egress backhaul RLC channel.
  • the default configuration information may be carried by F1AP signaling or RRC signaling.
  • the default configuration information may be borne by F1AP signaling sent by the first IAB donor node, or may be borne by RRC signaling sent by the second IAB donor node.
  • An embodiment of the present application provides a method for sending and receiving information, which is described from the side of the third IAB node and/or the sixth IAB node, and the same content as the embodiment of the second aspect will not be repeated. Furthermore, the embodiments of the fifth aspect may be implemented in combination with the embodiments of the second aspect, or may be implemented independently.
  • Figure 16 is a schematic diagram of the method for sending and receiving information. As shown in Figure 16, the method includes:
  • the third IAB node and/or the sixth IAB node receives the first mapping relationship information sent by the first IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul The mapping relationship between the RLC channel and the egress return RLC channel;
  • the third IAB node and/or the sixth IAB node determines the backhaul RLC channel of the radio bearer according to the first mapping relationship, and delivers the radio bearer to the corresponding egress backhaul RLC channel and sends, wherein the third IAB An ingress backhaul RLC channel on a node does not map to a different egress backhaul RLC channel.
  • FIG. 17 is a schematic diagram of the method for sending and receiving information. As shown in FIG. 17 , the method includes:
  • the fifth node receives the first mapping relationship information sent by the second IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel and the egress backhaul RLC channel the mapping relationship;
  • the fifth node determines the backhaul RLC channel of the radio bearer according to the first mapping relationship, delivers the radio bearer to the corresponding egress backhaul RLC channel and sends it, wherein each radio bearer on the fifth node is mapped to different Return on the RLC channel.
  • Embodiments of the present application provide an apparatus for sending and receiving information.
  • the apparatus is applied to the first IAB host node, for example, may be the IAB host node, or may be some or some components or components configured in the IAB host node, and the same content as the embodiment of the first aspect will not be repeated.
  • FIG. 18 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application. As shown in FIG. 18 , the information transceiver apparatus 1800 includes:
  • a first sending unit 1801 configured to send a first message to the second IAB host node, where the first message includes the backhaul RLC channel identifier and/or the reserved backhaul RLC channel number on the third IAB node and/or first indication information for indicating whether at least two radio bearers are sharing the same backhaul RLC channel;
  • the first configuration unit 1802 which configures the backhaul RLC channel mapping relationship for the IAB nodes in its topology.
  • the third IAB node is dual connected to the first IAB host node and the second IAB host node.
  • the apparatus further includes:
  • a first receiving unit (optional, not shown), which receives a second message sent by the second IAB host node, where the second message includes a radio bearer allocated by the second IAB host node on the third IAB node Returns the RLC channel identifier.
  • the first message and/or the second message are carried by XnAP signaling.
  • the returned RLC channel identifier is described in the embodiments of the first aspect, and details are not repeated here.
  • the radio bearer is a radio bearer for traffic offloading from the first IAB host node to the second IAB host node.
  • Embodiments of the present application provide an apparatus for sending and receiving information.
  • the apparatus is applied to the second IAB host node, for example, it may be the IAB host node, or it may be some or some components or components configured in the IAB host node, and the same content as the embodiment of the first aspect will not be repeated.
  • FIG. 19 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application. As shown in FIG. 19 , the information transceiver apparatus 1900 includes:
  • the second receiving unit 1901 which receives the first message sent by the first IAB host node, where the first message includes the backhaul RLC channel identifier on the third IAB node and/or the reserved backhaul RLC channel number and/or the in first indication information indicating whether at least two radio bearers are sharing the same backhaul RLC channel;
  • the second configuration unit 1902 configures the backhaul RLC channel mapping relationship for the IAB nodes in its topology.
  • the third IAB node is dual connected to the first IAB host node and the second IAB host node.
  • the apparatus further includes:
  • a second sending unit (optional, not shown), which sends a second message to the first IAB host node, where the second message includes a response allocated by the second IAB host node for the radio bearer on the third IAB node Pass the RLC channel ID.
  • Embodiments of the present application provide an apparatus for sending and receiving information.
  • the apparatus is applied to the first IAB host node, for example, it may be the IAB host node, or may be some or some components or components configured in the IAB host node, and the same content as the embodiment of the second aspect will not be repeated.
  • FIG. 20 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application. As shown in FIG. 20 , the information transceiver apparatus 2000 includes:
  • the third sending unit 2001 which sends first mapping relationship information to the third IAB node and/or the sixth IAB node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC The mapping relationship between the channel and the egress return RLC channel;
  • the third IAB node is dual-connected to the first IAB host node and the second IAB host node.
  • Embodiments of the present application provide an apparatus for sending and receiving information.
  • the apparatus is applied to the second IAB host node, for example, it may be the IAB host node, or may be some or some components or components configured in the IAB host node, and the same content as the embodiment of the third aspect will not be repeated.
  • FIG. 21 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application. As shown in FIG. 21 , the information transceiver apparatus 2100 includes:
  • the fourth sending unit 2101 sends first mapping relationship information to the fifth node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the difference between the ingress backhaul RLC channel and the egress backhaul RLC channel. Mapping relations;
  • each radio bearer on the fifth node is mapped to different backhaul RLC channels.
  • the apparatus may also include:
  • a ninth receiving unit (optional, not shown), which receives second indication information sent by the first IAB host node, where the second indication information is used to indicate whether each radio bearer needs to be mapped to different backhaul RLC channels .
  • the second indication information is carried by XnAP signaling.
  • the information transceiver 1800-2100 may further include other components or modules, and for the specific content of these components or modules, reference may be made to the related art.
  • FIGS. 18-21 only exemplarily show 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., which are not limited in the implementation of this application.
  • the first IAB host node notifies the second IAB host node of the backhaul RLC channel identifier and/or the number of reserved backhaul RLC channels on the third IAB node and/or used to indicate at least two radio bearers Whether the first indication information of whether the same backhaul RLC channel is being shared, so that the second IAB host node configures the bearer channel mapping relationship according to the first message, thereby realizing bearer mapping and/or channels across topologies (controlled by different donor-CUs)
  • the mapping configuration supports topology redundancy between hosts in the IAB network, so as to achieve load balancing between hosts, increase network robustness, and optimize network performance.
  • one ingress backhaul RLC channel on the third IAB node is not mapped to a different egress backhaul RLC channel.
  • the border IAB node cannot split the channel when the egress backhaul channel is mapped, so as to achieve load balancing between hosts, increase the robustness of the network, and optimize the network performance.
  • each radio bearer on the fifth node is mapped to different backhaul RLC channels. This avoids that different bearers are always mapped to the same BH RLC channel, and avoids the inability to distinguish the QoS of wireless bearers, so as to achieve load balancing between hosts, increase network robustness, and optimize network performance without affecting network transmission efficiency.
  • Embodiments of the present application provide an apparatus for sending and receiving information.
  • the apparatus may be, for example, a third IAB node, or may be some or some components or components configured in the third IAB node.
  • the same content as the embodiment of the fourth aspect will not be repeated.
  • FIG. 22 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application. As shown in FIG. 22 , the information transceiver apparatus 2200 includes:
  • the third receiving unit 2201 which receives the default configuration information sent by the first IAB host node or the second IAB host node, where the default configuration information configures the default egress return RLC channel of the redundant link in the uplink direction.
  • the apparatus when the first IAB host node does not receive the second message from the second IAB host node, or when 1:N bearer mapping occurs during uplink channel mapping, the apparatus further includes:
  • unit 2202 which uses the default configuration information to determine that a bearer is mapped to the default egress backhaul RLC channel.
  • the default configuration information may be carried by F1AP signaling or RRC signaling.
  • the default configuration information may be borne by F1AP signaling sent by the first IAB donor node, or may be borne by RRC signaling sent by the second IAB donor node.
  • FIG. 23 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application.
  • the information transceiver apparatus is applied to a first IAB host node or a second IAB host node.
  • the information transceiver 2300 includes:
  • the fifth sending unit 2301 sends default configuration information to the third IAB node, where the default configuration information configures the default egress return RLC channel of the redundant link in the uplink direction.
  • the third IAB node uses the missing message.
  • the provincial configuration information determines that the bearer is mapped to the default egress backhaul RLC channel.
  • the default configuration information may be carried by F1AP signaling or RRC signaling.
  • the default configuration information may be borne by the F1AP signaling sent by the first IAB donor node, or may be borne by the RRC signaling sent by the second IAB donor node.
  • the information transceiving apparatuses 2200-2300 may further include other components or modules, and for the specific content of these components or modules, reference may be made to the related art.
  • FIGS. 22-23 only exemplarily show 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.
  • Embodiments of the present application provide an apparatus for sending and receiving information.
  • the apparatus may be, for example, a third IAB node, or may be some or some components or components configured in the third IAB node.
  • the same content as the embodiment of the fifth aspect will not be repeated.
  • FIG. 24 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application. As shown in FIG. 24 , the apparatus includes:
  • the fifth receiving unit 2401 which receives the first mapping relationship information sent by the first IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel and the egress backhaul.
  • the third determining unit 2402 determines the backhaul RLC channel of the radio bearer according to the mapping relationship, wherein one ingress backhaul RLC channel on the third IAB node is not mapped to a different egress backhaul RLC channel.
  • Embodiments of the present application provide an apparatus for sending and receiving information.
  • the apparatus may be the sixth IAB node, or may be some or some components or components configured in the sixth IAB node.
  • the same content as the embodiment of the fifth aspect will not be repeated.
  • FIG. 25 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application. As shown in FIG. 25 , the apparatus includes:
  • the seventh receiving unit 2501 which receives the first mapping relationship information sent by the first IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel and the egress backhaul.
  • the fourth determining unit 2502 determines the backhaul RLC channel of the radio bearer according to the mapping relationship, so that one ingress backhaul RLC channel on the third IAB node is not mapped to a different egress backhaul RLC channel.
  • Embodiments of the present application provide an apparatus for sending and receiving information.
  • the apparatus may be, for example, the fifth node, or may be some or some components or assemblies configured in the fifth node.
  • the same content as the embodiment of the sixth aspect will not be repeated.
  • FIG. 26 is a schematic diagram of an information transceiver apparatus according to an embodiment of the present application. As shown in FIG. 26 , the apparatus includes:
  • the eighth receiving unit 2601 which receives the first mapping relationship information sent by the second IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel and the egress backhaul.
  • the fifth determination unit 2602 which determines the backhaul RLC channel of the radio bearer according to the first mapping relationship, wherein, each radio bearer on the fifth node is mapped to a different backhaul RLC channel, or, so that the first The second radio bearer is mapped to the backhaul RLC channel corresponding to the backhaul RLC channel identifier of the first radio bearer, or,
  • the number of backhaul RLC channels mapped by the radio bearer at the third IAB node is less than or equal to the reserved number of backhaul RLC channels.
  • the embodiments of the present application further provide a communication system, and the same contents as those of the embodiments of the first aspect to the ninth aspect will not be repeated.
  • the communication system may include: a host IAB node, including the information transceiving apparatus according to the seventh aspect or the eighth aspect embodiment, which performs the information transceiving according to the first to fourth aspect embodiments method;
  • the communication system may include: an IAB node, including the information transceiving apparatus described in the embodiment of the eighth or ninth aspect, which executes the information described in the embodiment of the fourth or fifth or sixth aspect Send and receive method.
  • IAB node including the information transceiving apparatus described in the embodiment of the eighth or ninth aspect, which executes the information described in the embodiment of the fourth or fifth or sixth aspect Send and receive method.
  • the above embodiments may be implemented individually or in combination, and the embodiments of the present application are not limited thereto.
  • the IAB node (including the border IAB node) may include an IAB-DU functional unit, and may further include an IAB-MT functional unit.
  • the IAB-MT functional unit may have the same structure as the terminal equipment.
  • the IAB-DU functional unit may have the same structure as the network device.
  • FIG. 27 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the network device 2700 may include: a processor 2710 (eg, a central processing unit CPU) and a memory 2720 ; the memory 2720 is coupled to the processor 2710 .
  • the memory 2720 can store various data; in addition, a program 2780 for information processing is also stored, and the program 2780 is executed under the control of the processor 2710 .
  • the processor 2710 may be configured to execute a program to implement the method performed by the host IAB node as in the embodiments of the first or second or third or fourth aspect.
  • the network device 2700 may further include: a transceiver 2740, an antenna 2750, etc.; wherein, the functions of the above components are similar to those in the prior art, and will not be repeated here. It is worth noting that the network device 2700 does not necessarily include all the components shown in FIG. 27 ; in addition, the network device 2700 may also include components not shown in FIG. 27 , and reference may be made to the prior art.
  • FIG. 28 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 2800 may include a processor 2810 and a memory 2820 ; the memory 2820 stores data and programs, and is coupled to the processor 2828 .
  • 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 processor 2810 may be configured to execute a program to implement the method performed by the IAB node as described in the embodiments of the fourth or fifth or sixth aspect.
  • the terminal device 2800 may further include: a communication module 2830 , an input unit 2840 , a display 2850 , and a power supply 2850 .
  • 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 2800 does not necessarily include all the components shown in FIG. 28 , and the above components are not required; in addition, the terminal device 2800 may also include components not shown in FIG. 28 . There is technology.
  • the embodiment of the present application further provides a computer program, wherein when the program is executed in the IAB host node, the program causes the IAB host node to execute the information sending and receiving method described in the embodiments of any one of the first to fourth aspects .
  • An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables an IAB host node or a terminal device to execute the information sending and receiving method described in any one of the first to fourth aspects.
  • the embodiments of the present application further provide a computer program, wherein when the program is executed in an IAB node, the program causes the IAB node to execute the information sending and receiving methods described in the embodiments of the fourth to sixth aspects.
  • the embodiments of the present application further provide a storage medium storing a computer program, wherein the computer program enables an IAB node to execute the information sending and receiving methods described in the embodiments of the fourth to sixth aspects.
  • 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 sending and receiving information comprising:
  • the first IAB host node sends a first message to the second IAB host node, the first message includes the backhaul RLC channel identifier on the third IAB node and/or the number of reserved backhaul RLC channels and/or used to indicate First indication information of whether at least two radio bearers are sharing the same backhaul RLC channel;
  • the first IAB host node configures a backhaul RLC channel mapping relationship for IAB nodes in its topology.
  • the first IAB host node receives a second message sent by the second IAB host node, where the second message includes a backhaul RLC allocated by the second IAB host node for the radio bearer on the third IAB node Channel ID.
  • backhaul RLC channel identifier is the backhaul channel identifier mapped by the radio bearer in the third IAB node, or the backhaul RLC channel identifier is the previous radio bearer in the third IAB node. Return RLC channel identifier mapped by the IAB node.
  • the backhaul RLC channel identifier is an ingress channel identifier; when the radio bearer is uplink data, the backhaul RLC channel identifier is an egress channel identifier.
  • radio bearer is a radio bearer that the first IAB host node performs traffic offloading to the second IAB host node.
  • a method for sending and receiving information comprising:
  • the second IAB host node receives the first message sent by the first IAB host node, where the first message includes the backhaul RLC channel identifier on the third IAB node and/or the number of reserved backhaul RLC channels and/or the number of backhaul RLC channels reserved and/or used for first indication information indicating whether at least two radio bearers are sharing the same backhaul RLC channel;
  • the second IAB host node configures the backhaul RLC channel mapping relationship for the IAB nodes in its topology.
  • the second IAB host node sends a second message to the first IAB host node, the second message including the backhaul RLC channel allocated by the second IAB host node for the radio bearer on the third IAB node logo.
  • the second IAB host node determines the egress backhaul RLC channel and/or configures the backhaul RLC channel mapping relationship and/or the bearer channel mapping relationship for the radio bearer according to the first message;
  • the number of backhaul RLC channels mapped by the radio bearer at the third IAB node is less than or equal to the reserved number of backhaul RLC channels.
  • backhaul RLC channel identifier is the backhaul channel identifier mapped by the radio bearer at the third IAB node, or the backhaul RLC channel identifier is The backhaul RLC channel identifier mapped by the previous radio bearer at the third IAB node.
  • the backhaul RLC channel identifier is an ingress channel identifier; when the radio bearer is uplink data, the backhaul RLC channel identifier is an egress channel identifier.
  • radio bearer is a radio bearer that the first IAB host node performs traffic offloading to the second IAB host node.
  • a method for sending and receiving information comprising:
  • the first IAB host node sends first mapping relationship information to the third IAB node and/or the sixth IAB node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel Mapping relationship with the egress backhaul RLC channel;
  • a method for sending and receiving information comprising:
  • the second IAB host node sends first mapping relationship information to the fifth node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the mapping between the ingress backhaul RLC channel and the egress backhaul RLC channel relation;
  • each radio bearer on the fifth node is mapped to different backhaul RLC channels.
  • the second IAB host node receives the second indication information sent by the first IAB host node, where the second indication information is used to indicate whether each radio bearer needs to be mapped to different backhaul RLC channels.
  • a method for sending and receiving information comprising:
  • the third IAB node receives the first mapping relationship information sent by the first IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel and the egress backhaul RLC channel the mapping relationship;
  • the third IAB node determines the backhaul RLC channel of the radio bearer according to the mapping relationship, wherein one ingress backhaul RLC channel on the third IAB node is not mapped to a different egress backhaul RLC channel.
  • a method for sending and receiving information comprising:
  • the sixth IAB node receives the first mapping relationship information sent by the first IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel and the egress backhaul RLC channel the mapping relationship;
  • the sixth IAB node determines the backhaul RLC channel of the radio bearer according to the mapping relationship, so that one ingress backhaul RLC channel on the third IAB node is not mapped to a different egress backhaul RLC channel.
  • a method for sending and receiving information comprising:
  • the fifth node receives the first mapping relationship information sent by the second IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the relationship between the ingress backhaul RLC channel and the egress backhaul RLC channel.
  • mapping relations
  • the fifth node determines the backhaul RLC channel of the radio bearer according to the first mapping relationship, wherein each radio bearer on the fifth node is mapped to a different backhaul RLC channel, or, so that the second radio bearer is mapped Return the RLC channel corresponding to the RLC channel identifier to the first radio bearer, or,
  • the number of backhaul RLC channels mapped by the radio bearer at the third IAB node is less than or equal to the reserved number of backhaul RLC channels.
  • An information transceiver applied to a third IAB node, comprising:
  • the fifth receiving unit which receives the first mapping relationship information sent by the first IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel and the egress backhaul The mapping relationship of the RLC channel;
  • a third determining unit which determines the backhaul RLC channel of the radio bearer according to the mapping relationship, wherein one ingress backhaul RLC channel on the third IAB node is not mapped to a different egress backhaul RLC channel.
  • An apparatus for transmitting and receiving information, applied to a sixth IAB node comprising:
  • the seventh receiving unit which receives the first mapping relationship information sent by the first IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel and the egress backhaul The mapping relationship of the RLC channel;
  • the fourth determining unit determines the backhaul RLC channel of the radio bearer according to the mapping relationship, so that one ingress backhaul RLC channel on the third IAB node is not mapped to a different egress backhaul RLC channel.
  • An information transceiver applied to a fifth node, comprising:
  • the eighth receiving unit which receives the first mapping relationship information sent by the second IAB host node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC channel and the egress backhaul The mapping relationship of the RLC channel;
  • a fifth determining unit which determines the backhaul RLC channel of the radio bearer according to the first mapping relationship, wherein each radio bearer on the fifth node is mapped to a different backhaul RLC channel, or, so that the second radio bearer is mapped to the backhaul RLC channel corresponding to the backhaul RLC channel identifier of the first radio bearer, or,
  • the number of backhaul RLC channels mapped by the radio bearer at the third IAB node is less than or equal to the reserved number of backhaul RLC channels.
  • An information transceiver applied to a first IAB host node, comprising:
  • a third sending unit which sends first mapping relationship information to the third IAB node and/or the sixth IAB node, where the first mapping relationship information indicates the mapping relationship between the radio bearer and the backhaul RLC channel and/or the ingress backhaul RLC The mapping relationship between the channel and the egress return RLC channel;
  • a method for sending and receiving information comprising:
  • the third IAB node receives the default configuration information sent by the first IAB host node or the second IAB host node, where the default configuration information configures the default egress of the redundant link in the uplink direction to return the RLC channel.
  • a method for sending and receiving information comprising:
  • the first IAB host node or the second IAB host node sends default configuration information to the third IAB node, where the default configuration information configures the default egress of the redundant link in the uplink direction to return the RLC channel.
  • An apparatus for transmitting and receiving information, applied to a third IAB node, the apparatus comprising:
  • the third receiving unit is configured to receive the default configuration information sent by the first IAB host node or the second IAB host node, where the default configuration information configures the default egress of the redundant link in the uplink direction to return the RLC channel.
  • the fifth sending unit is configured to send default configuration information to the third IAB node, where the default configuration information configures the default egress return RLC channel of the redundant link in the uplink direction.
  • An IAB host node comprising a memory and a processor, wherein the memory stores a computer program, the processor is configured to execute the computer program to implement any one of appendix 1 to 20, 31 The method of sending and receiving information.
  • An IAB node comprising a memory and a processor, the memory stores a computer program, the processor is configured to execute the computer program to achieve the implementation of any one of appendix 21 to 23, 28-30 method of sending and receiving information.
  • a communication system comprising:
  • IAB host node which executes the information transceiving method described in any one of Supplementary Notes 1 to 20, 31
  • a communication system comprising:
  • the IAB node which executes the information transceiving method described in any one of Supplementary Notes 21 to 23, 28-30.

Landscapes

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

Abstract

Les modes de réalisation de la présente invention concernent un procédé et un appareil d'envoi et de réception d'informations. Le procédé comprend les étapes au cours desquelles : un premier nœud donneur IAB envoie un premier message à un deuxième nœud donneur IAB, le premier message contenant un identifiant d'un canal RLC de liaison terrestre sur un troisième nœud IAB et/ou le nombre de canaux RLC de liaison terrestre réservés et/ou des premières informations d'indication destinées à indiquer si au moins deux porteuses radio partagent le même canal RLC de liaison terrestre ; et le premier nœud donneur IAB configure une relation de mise en correspondance de canaux RLC de liaison terrestre pour des nœuds IAB dans une topologie du premier nœud donneur IAB.
PCT/CN2021/085474 2021-04-02 2021-04-02 Procédé et appareil d'envoi et de réception d'informations WO2022205485A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/085474 WO2022205485A1 (fr) 2021-04-02 2021-04-02 Procédé et appareil d'envoi et de réception d'informations

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/085474 WO2022205485A1 (fr) 2021-04-02 2021-04-02 Procédé et appareil d'envoi et de réception d'informations

Publications (1)

Publication Number Publication Date
WO2022205485A1 true WO2022205485A1 (fr) 2022-10-06

Family

ID=83455528

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/085474 WO2022205485A1 (fr) 2021-04-02 2021-04-02 Procédé et appareil d'envoi et de réception d'informations

Country Status (1)

Country Link
WO (1) WO2022205485A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020164523A1 (fr) * 2019-02-15 2020-08-20 华为技术有限公司 Appareil et procédé de commande pour liaison terrestre radio
CN111585725A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 标识管理的方法和装置
CN112042263A (zh) * 2018-10-31 2020-12-04 捷开通讯(深圳)有限公司 无线通信网络中的承载映射
CN112398959A (zh) * 2019-08-15 2021-02-23 华为技术有限公司 Rlc信道确定方法和装置
CN112584458A (zh) * 2019-09-30 2021-03-30 华为技术有限公司 数据传输方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112042263A (zh) * 2018-10-31 2020-12-04 捷开通讯(深圳)有限公司 无线通信网络中的承载映射
WO2020164523A1 (fr) * 2019-02-15 2020-08-20 华为技术有限公司 Appareil et procédé de commande pour liaison terrestre radio
CN111585725A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 标识管理的方法和装置
CN112398959A (zh) * 2019-08-15 2021-02-23 华为技术有限公司 Rlc信道确定方法和装置
CN112584458A (zh) * 2019-09-30 2021-03-30 华为技术有限公司 数据传输方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM (MODERATOR): "CB#34 IAB_MigrationProcedureDetails", 3GPP DRAFT; R3-211199, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210125 - 20210204, 5 February 2021 (2021-02-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051978484 *
SAMSUNG (MODERATOR): "Summary of offline discussion on topology redundancy", 3GPP DRAFT; R3-211004, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210125 - 20210204, 5 February 2021 (2021-02-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051978303 *

Similar Documents

Publication Publication Date Title
US11968565B2 (en) User plane information reporting method and apparatus
KR20180127967A (ko) 무선 자원 제어 연결을 설정하기 위한 방법 및 장치
US20220217505A1 (en) Message transmission method and apparatus
US20220408317A1 (en) Handover method and communication apparatus
US20230254729A1 (en) Migration method and apparatus for iab-node
CN115699816A (zh) 用于在双连接下进行侧行链路中继通信的方法
WO2021215979A1 (fr) Procédés et nœuds dans des réseaux de liaison terrestre à accès intégré
US11533769B2 (en) Multi-hop data transmission method and apparatus
WO2022082690A1 (fr) Procédé, appareil et système de commutation de groupe
WO2022082495A1 (fr) Procédé, appareil, et système de routage
WO2017193402A1 (fr) Procédé, dispositif et système de transmission de données
US20220182910A1 (en) Data Processing Method, Apparatus, And System
WO2023010364A1 (fr) Dispositif et procédé de communication de liaison terrestre et d'accès intégré
WO2022205485A1 (fr) Procédé et appareil d'envoi et de réception d'informations
WO2022236644A1 (fr) Procédé d'envoi et de réception de signal, appareil d'envoi et de réception de signal, et système de communication
WO2022151298A1 (fr) Procédé, appareil et système de migration de groupe
WO2011076115A1 (fr) Procédé de transmission de données, station de base et système de transmission de données
WO2023197185A1 (fr) Dispositif de nœud iab, dispositif donneur iab et procédé de détermination d'adresse de transmission
WO2022205251A1 (fr) Procédé d'envoi et de réception d'informations, procédé d'envoi de données et appareil
WO2023197105A1 (fr) Procédé et appareil de configuration d'informations et système de communication
WO2023184542A1 (fr) Procédé et appareil de configuration d'informations et système de communication
WO2024207363A1 (fr) Procédé et appareil d'émission-réception de signal et système de communication
WO2023150975A1 (fr) Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration
WO2023197184A1 (fr) Dispositif donneur iab et procédé de configuration d'adresse de transmission
WO2023060401A1 (fr) Procédé et appareil de routage sans fil

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: 21934140

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21934140

Country of ref document: EP

Kind code of ref document: A1