WO2023205941A1 - 信息的发送、接收、配置方法以及装置和通信系统 - Google Patents

信息的发送、接收、配置方法以及装置和通信系统 Download PDF

Info

Publication number
WO2023205941A1
WO2023205941A1 PCT/CN2022/088749 CN2022088749W WO2023205941A1 WO 2023205941 A1 WO2023205941 A1 WO 2023205941A1 CN 2022088749 W CN2022088749 W CN 2022088749W WO 2023205941 A1 WO2023205941 A1 WO 2023205941A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
scg
link
node
terminal node
Prior art date
Application number
PCT/CN2022/088749
Other languages
English (en)
French (fr)
Inventor
易粟
贾美艺
路杨
Original Assignee
富士通株式会社
易粟
贾美艺
路杨
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 易粟, 贾美艺, 路杨 filed Critical 富士通株式会社
Priority to PCT/CN2022/088749 priority Critical patent/WO2023205941A1/zh
Publication of WO2023205941A1 publication Critical patent/WO2023205941A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the embodiments of this application relate to the field of communication technology.
  • MR-DC Multi-Radio Dual Connectivity, multi-radio dual connectivity
  • SCG secondary cell group, auxiliary cell group
  • the UE When the SCG is deactivated, the UE will not send PUSCH (Physical Uplink Shared CHannel, physical uplink shared channel), SRS (Sounding Reference Signal, detection reference signal) and CSI (Channel State Information, channel state information) reports on the SCG. And the UE does not need to monitor the PDCCH (Physical Downlink Control CHannel, physical downlink control channel) on the SCG.
  • PUSCH Physical Uplink Shared CHannel, physical uplink shared channel
  • SRS Sounding Reference Signal, detection reference signal
  • CSI Channel State Information, channel state information
  • the network can indicate the TCI (Transmission Configuration Indicator, Transmission Configuration Indicator) status to the UE for the PDCCH/PDSCH (primary SCell, primary cell of the secondary cell group) of PSCell.
  • TCI Transmission Configuration Indicator
  • PDCCH/PDSCH primary SCell, primary cell of the secondary cell group
  • PSCell primary SCell, primary cell of the secondary cell group
  • Physical Downlink Shared CHannel physical downlink shared channel
  • MN Master Node
  • SCG SCG
  • PSCell PSCell
  • RRC Radio Resource Control
  • the network can trigger SCG RRC reconfiguration, such as PSCell changes, configuration updates, etc.
  • SCG activation can be requested by MN, SN (Secondary Node, secondary node) or UE.
  • SCG deactivation can be requested by the MN or SN.
  • the UE indicates to the MN that it has uplink data to send on the SCG bearer.
  • the target MN may indicate the status of the SCG in the RRC reconfiguration message sent to the UE through the source MN.
  • IAB Integrated access and backhaul
  • NG-RAN next generation radio access network
  • IAB-node The integrated access and backhaul node
  • NR New Radio
  • IAB-donor represents a network device (for example, gNB) that supports IAB functionality.
  • IAB-node can connect to an IAB host (IAB-donor) through one or multiple 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 interface to the terminal equipment (UE) and the next hop IAB-node. The end point of the NR access interface is also the end point of the F1 protocol to the gNB-CU (central unit, central unit) on the IAB-donor. IAB-DU can serve ordinary UEs and IAB sub-nodes. IAB-DU implements network-side device functions, connects to the downstream child IAB-node, provides NR air interface access to the UE and the downstream child IAB-node, and establishes an F1 connection with the IAB donor-CU.
  • IAB-node In addition to the gNB-DU function, IAB-node also supports some UE functions, called IAB-MT (Mobile Termination, mobile terminal).
  • IAB-MT includes functions such as physical layer, layer 2, RRC and NAS to connect to another gNB-DU of IAB-node or IAB-donor, gNB-CU connected to IAB-donor and connected to the core network.
  • IAB-MT can support UE physical layer, access stratum (AS), radio resource control (RRC) layer and non-access stratum (NAS) layer functions, and can be connected to the IAB parent node.
  • AS access stratum
  • RRC radio resource control
  • NAS non-access stratum
  • IAB-donor is the terminal node on the network side. IAB-donor provides network access for IAB-MT or UE through backhaul or access links. IAB-donor is further divided into IAB-donor-CU (central unit) and IAB-donor-DU. IAB-DU and IAB-donor-CU are connected through the F1 interface. In the independent networking scenario, gNB and IAB-donor-CU are connected through the Xn interface.
  • BAP Backhaul Adaptation Protocol
  • RLC Radio Link Control
  • FIG 1 is a schematic diagram of the relationship between IAB parent and child nodes.
  • IAB-node 100 includes IAB-MT functional unit 101 and IAB-DU functional unit 102.
  • the neighboring nodes on the interface of IAB-DU functional unit 102 are called children.
  • Node (child node), the child nodes 201, 202, 203 shown in Figure 1, the IAB-DU functional unit 102 and the child nodes 201, 202, 203 can communicate through the air interface (Uu);
  • IAB-MT The neighboring nodes on the interface of the functional unit 101 are called parent nodes, such as the parent nodes 301 and 302 shown in Figure 1.
  • the IAB-MT functional unit 101 and the parent nodes 301 and 302 can be connected through the air interface. (Uu) communicate.
  • the direction from IAB-node 100 to child nodes 201, 202, and 203 is called the downstream direction, and the direction from IAB-node 100 to parent nodes 301 and 302 is called the upstream direction.
  • the IAB-donor (not shown) performs centralized resource, topology and routing management for the IAB topology 10 .
  • the IAB node In a multi-hop scenario, in order to realize the relay and forwarding of data packets, the IAB node needs to determine the target node where the data packet arrives, and then determine the next-hop node corresponding to the target node according to the routing table and send it.
  • the donor-CU configures the IAB node through F1AP (F1application protocol) signaling for each uplink F1-U Tunnel, non-UE associated (Non-UE associated) F1AP message, and user equipment-associated (UE- Mapping of associated)F1AP messages, non-F1 traffic (Non-F1Traffic) to BAP routing identifiers.
  • F1AP F1application protocol
  • the IAB node determines the BAP routing identifiers corresponding to different types of upstream IP packets initiated from the IAB node based on the routing identifier mapping information, and encapsulates the BAP subheaders containing the BAP routing identifier information for these upstream IP packets.
  • Donor-CU configures the mapping of different types of downlink data packets to BAP routing identifiers for donor-DU through F1AP signaling.
  • Donor-DU determines the BAP routing identifier corresponding to the received downstream IP packets based on the routing identifier mapping information, and encapsulates the BAP subheader containing the BAP routing identifier downstream for these downstream IP packets.
  • the BAP routing identifier includes the destination BAP address and the path identity from the IAB node to the donor-DU.
  • the BAP address is also called DESTINATION in the BAP header.
  • Each IAB node and donor-DU are configured with a BAP address.
  • NR-DC NR-NR Dual Connectivity, New Air Interface Dual Connectivity
  • F1-AP messages or F1-C related (SCTP/) IP data are encapsulated into SCTP/IP (Stream Control Transmission Protocol/IP) Packets can be transferred through the BAP sublayer, or through the SRB (Signalling Radio Bearer) between the IAB node and the corresponding non-F1-termination node.
  • SCTP/IP Stream Control Transmission Protocol/IP
  • SRB Signaling Radio Bearer
  • the purpose of transmitting data related to F1-C or F1-C through SRB is to select different paths for F1-U and F1-C, that is, CP-UP (control plane-user plane, control plane-user plane) plane) separation.
  • the purpose is to better ensure the transmission of the control plane and select a shorter path or a link with better wireless channel conditions for the control plane, such as selecting the link where FR1 (frequency range 1) is located.
  • Figure 2 is a schematic diagram of achieving CP-UP separation in two NR-DC scenarios.
  • IAB node 1 dual-connection node in a) of Figure 2
  • IAB-donor 2 i.e., F1-termination node, secondary node in a) of Figure 2
  • the link exchanges F1-AP messages or F1-C related (SCTP/) IP data packets encapsulated in SCTP/IP via the primary node (non-F1 terminal node); through the backhaul link and SN (secondary node, secondary node) to exchange F1-U traffic.
  • SRB2 is used to transmit F1-AP messages encapsulated in SCTP/IP or F1-C related (SCTP/) IP data packets between IAB-MT and MN (master node).
  • F1-AP messages or F1-C related (SCTP/) IP packets encapsulated in SCTP/IP are transmitted between the MN and SN through XnAP (Xn Application Protocol, Xn Application Protocol) as a container.
  • XnAP Xn Application Protocol, Xn Application Protocol
  • the master node (MN) is the M-NG-RAN node.
  • Scenario 2 IAB node 1 and IAB-donor 2) in MN (F1 termination node, b) of Figure 2) exchange F1 encapsulated into SCTP/IP via SN (non-F1 termination node) through the NR access link - AP messages or F1-C related (SCTP/) IP packets; exchange F1-U traffic with the MN via the backhaul link.
  • Split SRB2 is used to transport F1-AP messages encapsulated in SCTP/IP or F1-C related (SCTP/)IP packets between IAB-MT and SN.
  • These F1-AP messages or F1-C related (SCTP/)IP data packets encapsulated in SCTP/IP are transmitted between the SN and MN through XnAP as a container.
  • F1-AP messages or F1-C related (SCTP/)IP packets encapsulated in SCTP/IP can be passed through the BAP sublayer or SRB, but the use of both on the same parent link is not supported. method. If RRC configures the BH (backhaul) RLC channel for transmitting F1-C traffic in the cell group indicated for F1-C traffic transmission, it will be encapsulated into the F1-AP message or F1-C in SCTP/IP. C-related (SCTP/)IP packets are passed through the BAP sublayer.
  • Split SRB refers to the SRB carried by RLC between the MN and the terminal equipment (for example, UE) in Multi-Radio Dual Connectivity (MR-DC) and both MCG and SCG.
  • the downlink transmission path depends on the network implementation; for the uplink, the UE is configured by the MN's RRC signaling to use the MCG path or copy and transmit on the MCG and SCG.
  • IAB-MT has the functions of terminal equipment, such as supporting MR-DC related processes and MCG/SCG related mechanisms.
  • the inventor of this application found that the existing technology does not provide a specific method for realizing SCG deactivation for IAB-MT, nor does it provide for SCG deactivation for IAB nodes' CP-UP separation, routing, BH RLF (radio link failure, wireless link) (path failure) detection indication and other behaviors; therefore, the existing technology cannot well support the SCG deactivation function on IAB-MT.
  • Embodiments of the present application provide an information sending, receiving, configuring method, device and communication system, so that in the SCG deactivation state, the dual-connection IAB node can implement at least one of the following functions: Support CP-UP separation ; Perform routing and rerouting; trigger BH RLF detection indication.
  • an information sending device is provided, applied to a terminal node, and the device includes:
  • the first sending unit uses the RRC message carried by split SRB2 to transmit F1-C related information when the SCG is not deactivated.
  • an information configuration device is provided, applied to a terminal node, and the device includes:
  • a first receiving unit that receives RRC configuration information, where the RRC configuration information is used to configure a path to the MCG for the terminal node when the SCG is deactivated.
  • an information configuration device which is applied to a terminal node.
  • the terminal node includes an IAB node, such as IAB-MT.
  • the device includes:
  • the second receiving unit receives RRC configuration information, where the RRC configuration information is used to configure the terminal node to not support activation/deactivation of SCG.
  • an information configuration device is provided, which is applied to a terminal node.
  • the terminal node includes an IAB node, such as IAB-MT.
  • the device includes:
  • a third receiving unit that receives RRC configuration information, the RRC configuration information being used to configure the terminal node such that the SCG of the terminal node is deactivated;
  • a configuration unit that performs routing configuration, wherein when the SCG of the terminal node is deactivated, the egress link corresponding to the SCG is unavailable.
  • an information sending device is provided, applied to a terminal node, and the terminal node includes an IAB node, such as IAB-MT,
  • the device includes a second sending unit:
  • the second sending unit sends a BH RLF detection indication
  • the second sending unit sends a BH RLF detection indication.
  • an information receiving device applied to a network equipment node, and the device includes:
  • the fourth receiving unit uses the RRC message carried by split SRB2 to receive the F1-C related information sent by the terminal node when the SCG is not deactivated.
  • an information configuration device which is applied to a network equipment node.
  • the device includes:
  • the third sending unit sends RRC configuration information, where the RRC configuration information is used to configure a path to the MCG for the terminal node when the SCG is deactivated.
  • an information configuration device is provided, which is applied to a network equipment node,
  • the device includes:
  • the fourth sending unit sends RRC configuration information.
  • the RRC configuration information is used to configure the terminal node to not support activation/deactivation of SCG.
  • the terminal node includes an IAB node, such as IAB-MT.
  • the dual-connection IAB node in the SCG deactivation state, can at least support CP-UP separation, and/or perform routing and rerouting, and/or trigger BH RLF detection indication.
  • Figure 1 is a schematic diagram of the relationship between IAB parent and child nodes
  • Figure 2 is a schematic diagram of achieving CP-UP separation in two NR-DC scenarios
  • Figure 3 is a schematic diagram of an information sending method in Solution 1 of the embodiment of the first aspect
  • Figure 4 is a schematic diagram of the information configuration method of Solution 2 of the embodiment of the first aspect
  • Figure 5 is a schematic diagram of the information configuration method of solution three of the embodiment of the first aspect
  • Figure 6 is a schematic diagram of the information configuration method according to the embodiment of the second aspect
  • Figure 7 is a schematic diagram of an information sending method in Solution 1 of the embodiment of the third aspect
  • Figure 8 is a schematic diagram of the information sending method in Solution 2 of the embodiment of the third aspect
  • Figure 9 is a schematic diagram of an information receiving method according to the embodiment of the fourth aspect.
  • Figure 10 is a schematic diagram of the information configuration method according to the embodiment of the fourth aspect.
  • Figure 11 is a schematic diagram of another information configuration method according to the embodiment of the fourth aspect.
  • Figure 12 is a schematic diagram of an information sending device according to the embodiment of the fifth aspect.
  • Figure 13 is a schematic diagram of the information configuration device according to the embodiment of the fifth aspect.
  • Figure 14 is a schematic diagram of another information configuration device according to the embodiment of the fifth aspect.
  • Figure 15 is a schematic diagram of the information configuration device according to the embodiment of the sixth aspect.
  • Figure 16 is a schematic diagram of an information sending device according to the embodiment of the seventh aspect.
  • Figure 17 is a schematic diagram of an information receiving device according to the embodiment of the eighth aspect.
  • Figure 18 is a schematic diagram of the information configuration device according to the embodiment of the eighth aspect.
  • Figure 19 is a schematic diagram of another information configuration device according to the embodiment of the eighth aspect.
  • Figure 20 is a schematic diagram of the composition of an electronic device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be used by these terms. restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprises,” “includes,” “having” and the like refer to the presence of stated features, elements, elements or components but do not exclude 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 complies with any of the following communication standards, such as New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), Enhanced Long-term evolution (LTE-A, LTE-Advanced), wideband code division multiple access (WCDMA, Wideband Code Division Multiple Access), high-speed packet access (HSPA, High-Speed Packet Access), etc.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A Long-term evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • communication between devices in the communication system can be carried out according to any stage of communication protocols, which may include but are not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G. , New Wireless (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • Network device refers to a device in a communication system that connects a terminal device to a communication network and provides services to the terminal device.
  • Network equipment may include but is not limited to the following equipment: integrated access and backhaul node (IAB-node), relay (relay), base station (BS, Base Station), access point (AP, Access Point), transmitting and receiving Point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, wireless network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) etc.
  • IAB-node integrated access and backhaul node
  • relay relay
  • base station BS, Base Station
  • AP Access Point
  • TRP Transmission Reception Point
  • broadcast transmitter mobile management entity
  • MME Mobile Management Entity
  • gateway server
  • wireless network controller RNC, Radio Network Controller
  • BSC Base Station Controller
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB) and 5G base station (gNB), etc.
  • it may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay or low-power node (such as femeto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay or low-power node such as femeto, pico, etc.
  • base station may include some or all of their functions, each of which may provide communications coverage to a specific geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "user equipment” (UE, User Equipment) or “terminal equipment” (TE, Terminal Equipment or Terminal Device) refers to a device that accesses a communication network through a network device and receives network services.
  • Terminal equipment can be fixed or mobile, and can also be called mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), mobile terminal (MT, mobile termination), stations, etc.
  • the terminal equipment may include but is not limited to the following equipment: cellular phone (Cellular Phone), personal digital assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld device, machine-type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • cellular phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication equipment
  • handheld device machine-type communication equipment
  • laptop computer Cordless phones
  • Cordless phones smartphones, smart watches, digital cameras, and more.
  • the terminal device can also be a machine or device for monitoring or measuring.
  • the terminal device can include but is not limited to: Machine Type Communication (MTC) terminals, Vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station or may include one or more network devices as above.
  • user side or “terminal side” or “terminal device side” refers to the side of the user or terminal, which may be a certain UE or may include one or more terminal devices as above.
  • the high-level signaling may be, for example, radio resource control (RRC) signaling; for example, it is called an RRC message (RRC message), and includes, for example, MIB, system information (system information), and dedicated RRC message; or Called RRC IE (RRC information element).
  • RRC radio resource control
  • the high-level signaling may also be F1-C signaling, or F1AP protocol, for example.
  • F1-C signaling F1AP protocol
  • the first network node is, for example, an IAB node (IAB-node).
  • IAB-node IAB node
  • This application will take a multi-hop IAB network deployment scenario as an example to describe each embodiment, in which multiple UEs use multiple The hopped IAB node is connected to the IAB-donor and finally connected to the network.
  • the network is, for example, a 5G network.
  • the embodiments of the present application may not be limited to the above scenarios.
  • the first network node may also be other types of network nodes.
  • the scenarios of the embodiment are not limited to several dual connection scenarios as shown in the figure, nor are they limited to CP-UP separation scenarios.
  • split SRB2 is used to transmit F1-AP messages encapsulated into SCTP/IP between IAB-MT and SN Or F1-C related (SCTP/)IP packets. Because the F1-C related information in scenario 2 is transmitted by the SN, the primary path (primaryPath) of the PDCP (Packet Data Convergence Protocol) entity corresponding to split SRB2 is configured by the network device to point to the SCG.
  • primaryPath Packet Data Convergence Protocol
  • embodiments of the first aspect of the present application provide a variety of solutions.
  • Solution one is a method of sending information. This method applies to the terminal node, which can be an IAB node, for example, IAB-node 1 in Figure 2.
  • FIG. 3 is a schematic diagram of an information sending method in Solution 1 of the embodiment of the first aspect. As shown in Figure 3, the method includes:
  • Operation 301 When the SCG is not deactivated, use the RRC message carried by split SRB2 to transmit F1-C related information.
  • the terminal node for example, the IAB-MT of the terminal node
  • F1-C related information needs to be transferred
  • the IAB-MT has been established in SRB2, or split SRB2 has been established.
  • the RRC uplink information transfer process is initiated when the SCG is not deactivated.
  • the RRC uplink information transfer process can be used to transfer F1-C related information.
  • the SRB2 has been established and is applicable to CP-UP separation scenario 1.
  • the split SRB2 has been established and SCG has not been activated and is applicable to CP-UP separation scenario 2.
  • the F1-C related message is included in the ULInformationTransfer message.
  • the RRC standard can be enhanced in TS 38.331 to implement operation 301.
  • An example of a modification to the standard is shown in Table 1.
  • Solution two is an information configuration method. This method applies to terminal nodes.
  • Figure 4 is a schematic diagram of the information configuration method of Solution 2 of the embodiment of the first aspect. As shown in Figure 4, the method includes:
  • Operation 401 Receive RRC configuration information, where the RRC configuration information is used to configure a path to the MCG for the terminal node when the SCG is deactivated.
  • the field primaryPath (primary path) and/or the field ul-DataSplitThreshold (uplink data split threshold) in the RRC configuration information can be appropriately configured.
  • This at least one embodiment is applicable to both user equipment (UE) and IAB-MT (that is, the terminal node in operation 401 includes user equipment or IAB-MT).
  • UE user equipment
  • IAB-MT that is, the terminal node in operation 401 includes user equipment or IAB-MT.
  • all RBs radio bearers, radio bearers
  • the corresponding PDCP entities can be configured according to this method.
  • the IE (Information Element) RadioBearerConfig in the RRC message can add, modify or release signaling and/or data radio bearers.
  • this IE RadioBearerConfig can carry PDCP parameters, etc.
  • the IE PDCP-Config about PDCP parameters contains a field primaryPath, which is used to indicate the cell group ID and LCID (Logical Channel Identification, logical channel identifier). Network equipment uses logical channels of different cell groups to indicate split bearer cell groups.
  • the primaryPath may be configured to point to the MCG when the SCG is deactivated.
  • the cell group ID field in primaryPath represents the ID of the primary cell group (MCG), which is usually 0.
  • MCG primary cell group
  • ul-DataSplitThreshold can be further configured.
  • the terminal node submits the PDCP PDU (Protocol Data Unit) to the primary RLC entity;
  • the terminal node submits the PDCP PDU to the primary RLC entity or the secondary RLC entity.
  • the RRC standard may be enhanced in TS 38.331 to implement at least one embodiment.
  • An example of a modification to the standard is shown in Tables 2 and 3 below.
  • flc-TransferPathNRDC and flc-TransferPath in the RRC configuration information may be appropriately configured.
  • This at least one other embodiment is applicable to IAB-MT (ie, the terminal node in operation 401 includes IAB-MT).
  • RRC signaling configures the parameter f1c-TransferPathNRDC (f1c-transfer path NR dual connection) for the IAB node.
  • This parameter f1c-TransferPathNRDC specifies the delivery path that the NR-DC's IAB-MT should use when delivering F1-C data packets to IAB-donor-CU. If the parameter f1c-TransferPathNRDC of IAB-MT is configured as "mcg", IAB-MT can only use MCG for F1-C transfer; if IAB-MT is configured as "scg”, IAB-MT can only use SCG for F1-C transfer. Make an F1-C transfer. If IAB-MT is configured as "both", IAB-MT selects MCG or SCG for F1-C delivery.
  • the parameter f1c-TransferPath (f1c-transfer path) is also configured for the IAB node in RRC signaling.
  • This parameter f1c-TransferPath specifies the delivery path that the IAB-MT of EN-DC should use when delivering F1-C data packets to IAB-donor-CU. If the parameter f1c-TransferPath of IAB-MT is configured as "lte", IAB-MT can only use LTE (Long Term Evolution) link for F1-C transfer. If the parameter f1c-TransferPath of IAB-MT is configured as "nr", IAB-MT can only use the NR (New Radio) link for F1-C transfer.
  • IAB-MT selects the LTE or NR link for F1-C transfer. If the parameter f1c-TransferPath is not configured, the IAB node uses the NR link as the default configuration.
  • the above parameters f1c-TransferPathNRDC and/or f1c-TransferPath can be configured by the network device, wherein, in the case where the SCG is deactivated, the configuration parameters f1c-TransferPathNRDC and/or f1c-TransferPath point to the MCG .
  • f1c-TransferPathNRDC is set to a first value (the first value is, for example, "mcg")
  • f1c-TransferPath is set to a second value (the second value is, for example, "mcg") is "lte").
  • f1c-TransferPath is set to "lte" which means that IAB-MT uses MCG for F1-C transfer.
  • the RRC standard may be enhanced in TS 38.331 to implement at least one other embodiment.
  • An example of a modification to the standard is shown in Tables 4 and 5 below.
  • Solution three is an information configuration method. This method applies to terminal nodes that include an IAB-MT (e.g., IAB-MT for IAB-node 1 of Figure 2).
  • IAB-MT e.g., IAB-MT for IAB-node 1 of Figure 2.
  • Figure 5 is a schematic diagram of the information configuration method of solution three of the embodiment of the first aspect. As shown in Figure 5, the method includes:
  • Operation 501 Receive RRC configuration information, where the RRC configuration information is used to configure the terminal node to not support activation/deactivation of SCG.
  • the IAB node may be configured not to support SCG deactivation.
  • the IAB node There are differences between the IAB node and the UE. For example, the power saving requirements are different and the data transmission volume is larger. If the IAB node supports SCG deactivation, it will affect many functions. For example, the IAB node has a node data forwarding function. The forwarding is routed at the BAP sublayer and transmitted through the configured BH RLC channel. If the SCG of IAB-MT is deactivated, it will affect the route forwarding of the SCG link, thereby affecting the routing table configuration and/or BH RLC channel mapping configuration. If the IAB node does not support the SCG deactivation function, it can avoid the impact on BAP routing, routing table configuration, BH RLC channel mapping configuration, BH RLF indication related behavior, etc., so that the IAB node can work normally.
  • the RRC reconfiguration message has a field scg-State (secondary cell group state), which indicates that the SCG is in a deactivated state.
  • scg-State secondary cell group state
  • the scg-State can be configured so that the terminal node (for example, IAB-MT) does not use this field scg-State. Therefore, the terminal node can be configured not to support activation/deactivation of SCG. .
  • the RRC standard can be enhanced in TS 38.331 to implement Operation 501.
  • An example of a modification to the standard is shown in Table 6 below.
  • the terminal node can support the CP-UP separation of the IAB, so control plane signaling can be transmitted, ensuring the working performance of the IAB node.
  • the BAP routing ID contained in the BAP packet is used to search for matching entries in the return routing configuration to select the appropriate egress link. If an RLF occurs on a link, or a BH RLF detection indication is received from a backhaul link, the link is considered unavailable.
  • the IAB node will perform local re-routing, such as selecting other available egress links by matching the destination address or BAP header rewriting.
  • the second embodiment of the present application provides an information configuration method, which is applied to a terminal node, such as an IAB node.
  • Figure 6 is a schematic diagram of the information configuration method according to the embodiment of the second aspect. As shown in Figure 6, the method includes:
  • Operation 601 Receive RRC configuration information, the RRC configuration information is used to configure the terminal node to deactivate the SCG of the terminal node;
  • Operation 602 Routing configuration, where when the SCG of the terminal node is deactivated, the egress link corresponding to the SCG is unavailable.
  • Routing configuration is operated by the BAP layer.
  • the BAP layer receives an indication that the SCG is deactivated from the upper layer (RRC layer), it considers that the SCG of the terminal node is deactivated, that is, the SCG link of the IAB-MT cannot transmit.
  • the terminal node when the SCG is deactivated, if the terminal node selects the egress link corresponding to the SCG through the search process of the backhaul routing configuration, the terminal node can perform local rerouting, that is, re-routing. Select another available egress link.
  • embodiments of the third aspect of the present application provide multiple solutions, so that in the case of SCG deactivation, if an RLF occurs in the MCG or the terminal node receives a BH RLF detection indication from the MCG link, The terminal node can send BH RLF detection indication to the child node.
  • Solution 1 provides a method for sending information, which method is applied to a terminal node, such as an IAB node.
  • FIG. 7 is a schematic diagram of an information sending method in Solution 1 of the embodiment of the third aspect. As shown in Figure 7, the information sending methods include:
  • Operation 701 When BH RLF occurs on all activated backhaul links of the terminal node, send a BH RLF detection indication; or when at least one backhaul link of the terminal node receives a BH RLF detection indication, and the terminal node has no other When the backhaul link or other backhaul links are unavailable or other backhaul links are deactivated, the BH RLF detection indication is sent.
  • the transmit portion of the collocated BAP entity on the IAB-DU may construct (e.g., form a) BAP control PDU for BH RLF detection indication and submit it to the associated The egress link of this IAB-DU (e.g., submitted to each egress link associated with this IAB-DU).
  • the link is considered a deactivated link; otherwise, the link is considered an activated link.
  • the BAP layer standard may be enhanced in TS 38.340 to implement operation 701.
  • An example of a modification to the standard is shown in Table 8 below.
  • the IAB node can propagate the received BH RLF detection indication, that is, send the BH RLF detection indication to the child node.
  • the received BH RLF detection indication needs to be propagated. Because the BAP control PDU format used for the BH RLF indication is the same, propagating the BH RLF detection indication is equivalent to sending a BH RLF detection indication itself.
  • the following behavior when defining the RLF-related behavior of the BAP layer, the following behavior may be added: when a backhaul wireless event occurs on all active links of the IAB-MT that provide the F1 interface through the BAP When a link fails, or when a BH RLF detection indication is received from a backhaul link and no other link is available that provides the F1 interface through the BAP, the transmit part of the collocated BAP entity on the IAB-DU can be formed ( For example, construct a BAP control PDU for BH RLF detection indication and submit it to each egress link associated with the IAB-DU (e.g., submit to each egress link associated with the IAB-DU).
  • the RRC standard may be enhanced in TS 38.340 to implement operation 701.
  • An example of a modification to the standard is shown in Table 9 below.
  • operation 701 may use an "activated” related concept to set the behavior of the terminal node.
  • "Activated link” is defined as in the previous description.
  • the transmit portion of the collocated BAP entity on the IAB-DU may be formed (e.g., form a).
  • the indicated BAP control PDU is detected on the BH RLF and submitted to each egress link associated with the IAB-DU (e.g., submitted to each egress link associated with the IAB-DU).
  • the RRC standard may be enhanced in TS 38.340 to implement operation 701.
  • An example of a modification to the standard is shown in Table 10 below.
  • Table 10 adds a technical solution to set the behavior of the terminal node based on "activated”.
  • Solution 2 provides a method for sending information, which method is applied to a terminal node, such as an IAB node.
  • FIG. 8 is a schematic diagram of an information sending method in Solution 2 of the embodiment of the third aspect. As shown in Figure 8, the information sending methods include:
  • Operation 801 When BH RLF occurs in the MCG of the terminal node and the SCG is deactivated, the BH RLF detection indication is sent.
  • the sending part of the collocated BAP entity on the IAB-DU can be formed (e.g., forming a ) BAP control PDU for BH RLF detection indication and submitted to the egress link associated with this IAB-DU (e.g., submitted to each egress link associated with this IAB-DU).
  • the BAP layer standard can be enhanced in TS 38.340 to implement operation 801.
  • An example of a modification to the standard is shown in Table 11 below.
  • the sending part of the collocated BAP entity on the IAB-DU may assemble a BAP control PDU for the BH RLF detection indication and submit it to each The egress link associated with this IAB-DU.
  • the BAP layer standard may be enhanced in TS 38.340 to implement at least another implementation of operation 801.
  • An example of a modification to the standard is shown in Table 12 below.
  • the BH RLF detection indication can be sent to the child node.
  • An embodiment of the fourth aspect provides a method for receiving information, which corresponds to the method of sending information in Solution 1 of the embodiment of the first aspect. This method is applied to network device nodes, for example, IAB-donor in a) or b) of Figure 2.
  • FIG. 9 is a schematic diagram of an information receiving method according to the embodiment of the fourth aspect. As shown in Figure 9, the method includes:
  • Operation 901 When the SCG is not deactivated, use the RRC message carried by split SRB2 to receive the F1-C related information sent by the terminal node.
  • the terminal node may be an IAB node, such as IAB-MT.
  • the network device node can receive the RRC message carried by split SRB2. F1-C related information.
  • the embodiment of the fourth aspect also provides an information configuration method, which corresponds to the information configuration method of the second solution of the embodiment of the first aspect. This method applies to network device nodes.
  • Figure 10 is a schematic diagram of the information configuration method according to the embodiment of the fourth aspect. As shown in Figure 10, the method includes:
  • Operation 1001 Send RRC configuration information, where the RRC configuration information is used to configure a path to the MCG for the terminal node when the SCG is deactivated.
  • the terminal node may include a user equipment or an IAB node, such as an IAB-MT, and correspondingly, the network device node may include a base station or an IAB-donor.
  • the primary path (primaryPath) in the RRC configuration information is set to point to the MCG.
  • the uplink data split threshold (ul-DataSplitThreshold) of the RRC configuration information can also be set to infinity or set to a default value.
  • the main path and/or the uplink data splitting threshold configuration is applicable to all PDCP entities associated with more than one RLC entity, including the PDCP entities corresponding to separate SRB2.
  • the terminal node may include an IAB node, such as IAB-MT, and correspondingly, the network device node may include an IAB-donor.
  • the f1c transfer path NR dual connection (f1c-TransferPathNRDC) parameter and/or the f1c transfer path (f1c-TransferPath) parameter is configured to point to the MCG.
  • the f1c transfer path NR dual connection (f1c-TransferPathNRDC) parameter is set to a first value, and the first value is, for example, "MCG"; when SCG is deactivated, f1c The transfer path (f1c-TransferPath) parameter is set to a second value, which is, for example, "lte".
  • the embodiment of the fourth aspect also provides another information configuration method, which corresponds to the information configuration method of the third solution of the embodiment of the first aspect. This method is applied to network device nodes, for example, IAB-donor in a) or b) of Figure 2.
  • FIG 11 is a schematic diagram of another information configuration method according to the embodiment of the fourth aspect. As shown in Figure 11, the method includes:
  • Operation 1101 Send RRC configuration information.
  • the RRC configuration information is used to configure the terminal node to not support activation/deactivation of SCG.
  • the terminal node may include an IAB node, such as IAB-MT, and correspondingly, the network device node may include an IAB-donor.
  • the secondary cell group state (scg-State) field in the RRC configuration information may be set to not be used by the terminal node.
  • the terminal node can support the CP-UP separation of the IAB, so the control plane signaling can be transmitted, ensuring the performance of the IAB node.
  • An embodiment of the fifth aspect provides an information sending device, which corresponds to the information sending method of the first solution of the embodiment of the first aspect. This device is applied to end nodes.
  • FIG. 12 is a schematic diagram of an information sending device according to the embodiment of the fifth aspect. As shown in Figure 12, the device 1200 includes:
  • the first sending unit 1201 uses the RRC message carried by split SRB2 to transmit F1-C related information when the SCG is not deactivated.
  • the terminal node may be an IAB node, such as IAB-MT.
  • the first sending unit 1201 initiates the RRC uplink information transfer process when SRB2 has been established, or the first sending unit 1201 initiates the RRC uplink information transfer process when split SRB2 has been established and the SCG has not been deactivated.
  • the embodiment of the fifth aspect also provides an information configuration method, which corresponds to the information configuration method of the second solution of the embodiment of the first aspect. This device is applied to end nodes.
  • Figure 13 is a schematic diagram of the information configuration device according to the embodiment of the fifth aspect. As shown in Figure 13, the device 1300 includes:
  • the first receiving unit 1301 receives RRC configuration information, where the RRC configuration information is used to configure a path to the MCG for the terminal node when the SCG is deactivated.
  • the terminal node includes a user equipment or an IAB node (IAB node such as IAB-MT).
  • IAB node such as IAB-MT
  • the primary path (primaryPath) in the RRC configuration information is set to point to the MCG.
  • the uplink data split threshold (ul-DataSplitThreshold) of the RRC configuration information is set to infinity or set to a default value.
  • the terminal node includes an IAB node.
  • the f1c transfer path NR dual connection (f1c-TransferPathNRDC) parameter and/or the f1c transfer path (f1c-TransferPath) parameter is configured to point to the MCG.
  • the f1c-TransferPathNRDC parameter is set to a first value, and the first value is, for example, "MCG”.
  • the f1c transfer path (f1c-TransferPath) parameter is set to a second value, and the second value is, for example, "lte”.
  • the embodiment of the fifth aspect also provides another information configuration device, corresponding to the information configuration method of the third solution of the embodiment of the first aspect. This device is applied to end nodes.
  • Figure 14 is a schematic diagram of another information configuration device according to the embodiment of the fifth aspect. As shown in Figure 14, the device 1400 includes:
  • the second receiving unit 1401 receives RRC configuration information, where the RRC configuration information is used to configure the terminal node to not support activation/deactivation of SCG.
  • the secondary cell group state (scg-State) field in the RRC configuration information is set so that the terminal node does not use this field.
  • An embodiment of the sixth aspect provides an information configuration device, corresponding to the embodiment of the second aspect. This device is applied to end nodes.
  • Figure 15 is a schematic diagram of the information configuration device according to the embodiment of the sixth aspect. As shown in Figure 15, the device 1500 includes:
  • the third receiving unit 1501 receives RRC configuration information, the RRC configuration information is used to configure the terminal node such that the SCG of the terminal node is deactivated;
  • Configuration unit 1502 which performs routing configuration, wherein when the SCG of the terminal node is deactivated, the egress link corresponding to the SCG is unavailable.
  • the configuration unit 1502 when the egress link corresponding to the SCG is selected through the lookup process of the backhaul route configuration, the configuration unit 1502 performs local rerouting.
  • An embodiment of the seventh aspect of the present application provides an information sending device, which corresponds to the information sending method described in the embodiment of the third aspect.
  • the device is applied to terminal nodes, and the terminal nodes include IAB nodes.
  • Figure 16 is a schematic diagram of an information sending device according to the embodiment of the seventh aspect. As shown in Figure 16, the information sending device 1600 includes a second sending unit 1601.
  • the second sending unit 1601 may correspond to the information sending method described in solution one of the embodiment of the third aspect.
  • the second sending unit 1601 when BH RLF occurs on all activated backhaul links of the terminal node, the second sending unit 1601 sends a BH RLF detection indication; or, when at least one backhaul link of the terminal node receives a BH RLF detection indication, and the terminal When the node has no other backhaul links or other backhaul links are unavailable or other backhaul links are in a deactivated state, the second sending unit 1601 sends a BH RLF detection indication.
  • the collocated BAP entity on the IAB-DU corresponding to the terminal node Send a partially constructed BAP control PDU for BH RLF detection indication and submit it to the egress link associated with this IAB-DU.
  • the link of the terminal node is the SCG link of the terminal node and the SCG is deactivated
  • the link is a deactivated link; that is, when the link of the terminal node The link is not an SCG link, or the SCG is in the active state, and the link is an active link.
  • the sending part of the collocated BAP entity on the IAB-DU corresponding to the terminal node constructs the BAP control PDU for the BH RLF detection indication and submits it to the IAB-DU associated with the terminal node. egress link.
  • the sending part of the collocated BAP entity on the IAB-DU corresponding to the terminal node constructs the BAP control PDU for the BH RLF detection indication and submits it to the IAB associated -DU's egress link.
  • the second sending unit 1601 may correspond to the information sending method described in the second solution of the embodiment of the third aspect.
  • the second sending unit 1601 sends a BH RLF detection indication.
  • the sending part of the collocated BAP entity on the IAB-DU corresponding to the terminal node constructs a BAP control PDU for BH RLF detection indication and submits it to the egress link associated with the IAB-DU.
  • the second sending unit 1601 sends the received BHRLF detection indication.
  • An embodiment of the eighth aspect provides an information receiving apparatus corresponding to the information sending method of the first solution of the embodiment of the first aspect. This method is applied to network device nodes, for example, IAB-donor in a) or b) of Figure 2.
  • FIG. 17 is a schematic diagram of an information receiving device according to an embodiment of the eighth aspect. As shown in Figure 17, the device 1700 includes:
  • the fourth receiving unit 1701 uses the RRC message carried by split SRB2 to receive the F1-C related information sent by the terminal node when the SCG is not deactivated.
  • the terminal node can be an IAB node, such as IAB-MT.
  • the fourth receiving unit 1701 uses the RRC message carried by split SRB2 to receive F1-C related information sent by the terminal node.
  • An embodiment of the eighth aspect further provides an information configuration device, corresponding to the information configuration method of the second solution of the embodiment of the first aspect. This method applies to network device nodes.
  • Figure 18 is a schematic diagram of the information configuration device according to the embodiment of the eighth aspect. As shown in Figure 18, the device 1800 includes:
  • the third sending unit 1801 sends RRC configuration information, which is used to configure a path to the MCG for the terminal node when the SCG is deactivated.
  • the terminal node may include a user equipment or an IAB node (the IAB node is, for example, an IAB-MT), and correspondingly, the network device node may include a base station or an IAB-donor.
  • the IAB node is, for example, an IAB-MT
  • the network device node may include a base station or an IAB-donor.
  • the primary path (primaryPath) in the RRC configuration information is set to point to the MCG.
  • the uplink data split threshold (ul-DataSplitThreshold) of the RRC configuration information can also be set to infinity or set to a default value.
  • the terminal node may include an IAB node, such as IAB-MT, and correspondingly, the network device node may include an IAB-donor.
  • the f1c transfer path NR dual connection (f1c-TransferPathNRDC) parameter and/or the f1c transfer path (f1c-TransferPath) parameter is configured to point to the MCG.
  • the f1c transfer path NR dual connection (f1c-TransferPathNRDC) parameter is set to a first value, and the first value is, for example, "MCG"; when SCG is deactivated, f1c The transfer path (f1c-TransferPath) parameter is set to a second value, which is, for example, "lte".
  • the embodiment of the eighth aspect also provides another information configuration device, which corresponds to the information configuration method of the third solution of the embodiment of the first aspect. This method is applied to network device nodes, for example, IAB-donor in a) or b) of Figure 2.
  • Figure 19 is a schematic diagram of another information configuration device according to the embodiment of the eighth aspect. As shown in Figure 19, the device 1900 includes:
  • the fourth sending unit 1901 sends RRC configuration information, where the RRC configuration information is used to configure the terminal node to not support activation/deactivation of SCG.
  • the terminal node may include an IAB node, such as IAB-MT, and correspondingly, the network device node may include an IAB-donor.
  • the secondary cell group state (scg-State) field in the RRC configuration information may be set to not be used by the terminal node.
  • An embodiment of the present application also provides a communication system, which may include a terminal node and a network device node. At least one of the terminal node and the network device node may have the composition of the electronic device shown in FIG. 20 .
  • Figure 20 is a schematic diagram of the composition of an electronic device according to an embodiment of the present application.
  • the electronic device 2000 may include a processor 2010 (eg, a central processing unit CPU) and a memory 2020 ; the memory 2020 is coupled to the processor 2010 .
  • the memory 2020 can store various data; in addition, it also stores an information processing program 2030, and the program 2030 is executed under the control of the processor 2010.
  • the processor 2010 may be configured to execute a program to implement the methods in the embodiments of the first to fourth aspects.
  • the electronic device 2000 may also include a transceiver 2040 and an antenna 2050 , etc.; the functions of the above components are similar to those in the prior art, and will not be described again here. It is worth noting that the electronic device 2000 does not necessarily include all components shown in FIG. 20 ; in addition, the electronic device 2000 may also include components not shown in FIG. 20 , and reference may be made to the existing technology.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal node, the program causes the terminal node to execute the method described in the embodiments of the first to third aspects.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device node, the program causes the network device node to execute the method described in the embodiment of the fourth aspect.
  • Embodiments of the present application also provide a storage medium storing a computer program, wherein the computer program causes the electronic device to perform the methods described in the embodiments of the first to fourth aspects.
  • the above devices and methods of this application can be implemented by hardware, or can be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or component described above, or enables the logic component to implement the various methods described above or steps.
  • This application also involves storage media used to store the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memories, etc.
  • the methods/devices described in connection with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figure may correspond to each software module of the computer program flow, or may correspond to each hardware module.
  • These software modules can respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by solidifying these software modules using a field programmable gate array (FPGA), for example.
  • FPGA field programmable gate array
  • the software module may be located 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 may be coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor.
  • the processor and storage media may be located in an ASIC.
  • the software module can be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the accompanying drawings may be implemented as a general-purpose processor or a digital signal processor (DSP) for performing the functions described in this application. ), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any appropriate combination thereof.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, or multiple microprocessors. processor, one or more microprocessors combined with DSP communications, or any other such configuration.
  • a method of sending information, applied to terminal nodes, the method includes:
  • the RRC message carried by split SRB2 is used to transmit F1-C related information.
  • the terminal node initiates the RRC uplink information transfer process when SRB2 has been established, or the terminal node initiates the RRC uplink information transfer process when split SRB2 has been established and the SCG has not been deactivated.
  • An information configuration method, applied to terminal nodes, the method includes:
  • Receive RRC configuration information where the RRC configuration information is used to configure a path to the MCG for the terminal node when the SCG is deactivated.
  • the terminal node includes user equipment or IAB node,
  • the primary path (primaryPath) in the RRC configuration information is set to point to the MCG.
  • the uplink data split threshold (ul-DataSplitThreshold) of the RRC configuration information is set to infinity or set to a default value.
  • the terminal node includes an IAB node,
  • the f1c transfer path NR dual connection (f1c-TransferPathNRDC) parameter and/or the f1c transfer path (f1c-TransferPath) parameter is configured to point to the MCG.
  • the f1c transfer path NR dual connection (f1c-TransferPathNRDC) parameter is set to a first value.
  • the f1c transfer path (f1c-TransferPath) parameter is set to the second value.
  • the terminal nodes include IAB nodes,
  • the method includes:
  • Receive RRC configuration information where the RRC configuration information is used to configure the terminal node to not support activation/deactivation of SCG.
  • the secondary cell group state (scg-State) field in the RRC configuration information is set so that the terminal node does not use this field.
  • terminal nodes include IAB nodes,
  • the method includes:
  • Receive RRC configuration information the RRC configuration information being used to configure the terminal node such that the SCG of the terminal node is deactivated
  • Routing configuration wherein when the SCG of the terminal node is deactivated, the egress link corresponding to the SCG is unavailable.
  • the terminal node performs local rerouting.
  • a method of sending information, applied to terminal nodes, and the terminal nodes include IAB nodes,
  • the method includes:
  • the sending part of the collocated BAP entity on the IAB-DU corresponding to the terminal node constructs a BAP control PDU for BH RLF detection indication and submits it to the egress link associated with the IAB-DU.
  • the link of the terminal node is the SCG link of the terminal node and the SCG is deactivated
  • the link is a deactivated link.
  • the link at the terminal node is not an SCG link, or the SCG is in an active state
  • the link is an active link.
  • the BH RLF detection indication is sent.
  • the sending part of the collocated BAP entity on the IAB-DU corresponding to the terminal node constructs a BAP control PDU for BH RLF detection indication and submits it to the egress link associated with the IAB-DU.
  • the terminal node sends the received BH RLF detection indication.
  • the sending part of the collocated BAP entity on the IAB-DU corresponding to the terminal node constructs a BAP control PDU for BH RLF detection indication and submits it to the egress link associated with the IAB-DU.
  • a method for receiving information, applied to network device nodes, the method includes:
  • the network device node uses the RRC message carried by split SRB2 to receive the F1-C related information.
  • An information configuration method, applied to network device nodes, the method includes:
  • Send RRC configuration information which is used to configure a path to the MCG for the terminal node when the SCG is deactivated.
  • the terminal node includes user equipment or IAB node,
  • the primary path (primaryPath) in the RRC configuration information is set to point to the MCG.
  • the uplink data split threshold (ul-DataSplitThreshold) of the RRC configuration information is set to infinity or set to a default value.
  • the terminal node includes an IAB node,
  • the f1c transfer path NR dual connection (f1c-TransferPathNRDC) parameter and/or the f1c transfer path (f1c-TransferPath) parameter is configured to point to the MCG.
  • the f1c transfer path NR dual connection (f1c-TransferPathNRDC) parameter is set to a first value.
  • the f1c transfer path (f1c-TransferPath) parameter is set to the second value.
  • the method includes:
  • Send RRC configuration information where the RRC configuration information is used to configure the terminal node to not support activation/deactivation of SCG, and the terminal node includes an IAB node.
  • the secondary cell group state (scg-State) field in the RRC configuration information is set so that the terminal node does not use this field.

Landscapes

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

Abstract

本申请实施例提供一种信息的发送、接收、配置方法以及装置和通信系统，该信息的发送装置，应用于终端节点，该装置包括：第一发送单元，其在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息传递F1-C相关信息。

Description

信息的发送、接收、配置方法以及装置和通信系统 技术领域
本申请实施例涉及通信技术领域。
背景技术
在用户设备(UE)配置了MR-DC(Multi-Radio Dual Connectivity，多无线双连接)的情况下，为了实现合理电池消耗和对SCG(secondary cell group，辅小区组)的快速使用，制定了一套支持激活/去激活(activation/deactivation)的机制。当SCG被去激活时，在SCG的RLC(Radio Link Control，无线链路控制)承载上没有传输(transmission)。只有NR(New Radio，新无线)SCG可以被去激活，当SCG被去激活时所有的SCG内的小区都在去激活状态。
当SCG被去激活时，UE不会在SCG上发送PUSCH(Physical Uplink Shared CHannel，物理上行共享信道)，SRS(Sounding Reference Signal，探测参考信号)和CSI(Channel State Information，信道状态信息)报告，并且UE不需要监控SCG上的PDCCH(Physical Downlink Control CHannel，物理下行控制信道)。在SCG被去激活时，如果网络设备进行了相应的配置，UE可以执行SCG上的无线链路监控和波束失败检测。在SCG被激活且不执行随机接入的情况下，网络可以给UE指示TCI(Transmission Configuration Indicator，传输配置指示)状态，用于PSCell(primary SCell，辅小区组的主小区)的PDCCH/PDSCH(Physical Downlink Shared CHannel，物理下行共享信道)接收；如果没有提供，UE使用原先激活的TCI状态。
MN(Master Node，主节点)可以在比如PSCell增加、PSCell改变、RRC恢复或者是切换时配置SCG为激活或者去激活。当SCG被配置成去激活时，UE在PSCell上不执行随机接入。在网络去激活SCG时，或是在SCG处在去激活状态时，网络可以触发SCG RRC重配置，比如PSCell改变，配置更新等。
SCG激活可以由MN，SN(Secondary Node，辅节点)或者UE来请求。SCG去激活可以由MN或者SN来请求。在SCG被去激活时，如果在SCG承载有上行数据到达，UE向MN指示其在SCG承载有上行数据要发送。在切换过程中，目标MN可以通过源MN在发送给UE的RRC重配置消息中指示SCG的状态。
集成的接入和回传(Integrated access and backhaul，IAB)又称接入回传一体化在下一代无线接入网络(NG-RAN：next generation radio access network)中实现了无线中继的功能。集成的接入和回传节点(IAB-node)支持通过新无线(New Radio，NR)的接入和回传。NR回传在网络侧中终止点被称为IAB-donor，它表示一个具有支持IAB功能的网络设备(例如，gNB)。
IAB-node可以通过一跳或者多跳来连接到一个IAB宿主(IAB-donor)。这些多跳连接形成了一个以IAB宿主为根节点的有向无环图(DAG，Directed Acyclic Graph)拓扑结构。IAB宿主负责执行IAB网络拓扑中集中式的资源管理、拓扑管理和路由管理。
IAB-node支持gNB-DU(distributed unit，分布式单元)的功能，IAB-node DU也被称为IAB-DU，IAB-DU是到终端设备(UE)和下一跳IAB-node的无线接入(NR access)接口的终点，也是到IAB-donor上的gNB-CU(central unit，中心单元)的F1协议的终点。IAB-DU可以服务普通的UE和IAB子节点。IAB-DU实现网络侧设备功能，连接到下游的child IAB-node，对UE以及下游child IAB-node提供NR空口接入并与IAB donor-CU之间建立有F1连接。
除了gNB-DU功能，IAB-node也支持一部分UE的功能，被称为IAB-MT(Mobile Termination，移动终端)，IAB-MT包括比如物理层、层2、RRC和NAS功能来连接到另一个IAB-node或IAB-donor的gNB-DU、连接到IAB-donor上的gNB-CU和连接到核心网。IAB-MT可支持如UE物理层、接入(access stratum，AS)、无线资源控制(radio resource control，RRC)层和非接入(non-access stratum，NAS)层功能，可以连接到IAB父节点。
IAB-donor是网络侧的终结节点，IAB-donor通过回传或接入链路为IAB-MT或UE提供网络接入。IAB-donor又进一步分为IAB-donor-CU(central unit)和IAB-donor-DU。IAB-DU和IAB-donor-CU之间通过F1接口连接。在独立组网场景下，gNB与IAB-donor-CU之间通过Xn接口连接。
为了支持数据包的多跳路由转发，IAB引入了回传适配协议(Backhaul Adaptation Protocol，BAP)子层。BAP子层位于无线链路控制(RLC)子层之上、IP层之下，支持数据包目的节点及路径选择、数据包路由转发、承载映射、流控反馈、回传链路失败通知等功能。
图1是IAB父子节点关系的一个示意图。如图1所示，在IAB父子节点关系结构10中，IAB-node 100包括IAB-MT功能单元101和IAB-DU功能单元102，IAB-DU功能单元102的接口上的邻节点被称为子节点(child node)，如图1中所示的子节点201、202、203，IAB-DU功能单元102与子节点201、202、203之间可以通过空中接口(Uu)进行通信；IAB-MT功能单元101的接口上的邻节点被称为父节点(parent node)，如图1中所示的父节点301、302，IAB-MT功能单元101与父节点301、302之间可以通过空中接口(Uu)进行通信。
如图1所示，IAB-node 100到子节点201、202、203的方向被称为下游(downstream)方向，IAB-node 100到父节点301、302的方向被称为上游(upstream)方向。IAB-donor(未图示)为该IAB拓扑结构10执行集中式的资源、拓扑和路由管理。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
在多跳场景下，为了实现数据包的中继转发，IAB节点需要确定数据包到达的目标节点，然后根据路由表确定到达目标节点对应的下一跳节点并发送。由donor-CU通过F1AP(F1application protocol)信令为IAB节点配置从IAB节点发起的上行每个F1-U Tunnel、非用户设备关联的(Non-UE associated)F1AP消息、用户设备关联的(UE-associated)F1AP消息、非F1流量(Non-F1Traffic)到BAP路由标识的映射。
IAB节点根据路由标识映射信息确定从IAB节点发起的不同类型上行IP包对应的BAP路由标识，并为这些上行IP包封装包含BAP路由标识信息的BAP子头。Donor-CU通过F1AP信令为donor-DU配置不同类型的下行数据包到BAP路由标识的映射。Donor-DU根据路由标识映射信息确定收到的下行IP包对应的BAP路由标识，并为这些下行IP包封装包含BAP路由标识下行的BAP子头。
BAP路由标识包括目的BAP地址和从IAB节点到donor-DU之间的路径标识(path identity)。BAP地址在BAP报头中也被称为DESTINATION(目的地)。每个IAB节点及donor-DU都被配置了一个BAP地址。
在NR-DC(NR-NR Dual Connectivity，新空口双连接)中，被封装到SCTP/IP(流控制传输协议/IP)中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包可以通过BAP子层传递(transfer)，也可以通过IAB节点和对应的非F1终结(non-F1-termination)节点之间的SRB(Signalling Radio Bearer，信令无线承载)传递。当MCG(master cell group，主小区组)和SCG(secondary cell group，辅小区组)都被配置成可以传递被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包时，由IAB的实现来选择路径。
对F1-C或者F1-C相关的数据通过SRB来进行传输(transport)是为了将F1-U和F1-C选择不同的路径，也就是CP-UP(control plane-user plane，控制平面-用户平面)分离。目的是为了更好地保证控制平面的传输，为控制平面选择更短的路径或者是无线信道条件更好的链路，比如选择FR1(frequency range 1)所在的链路。
图2是在两种NR-DC场景下达到CP-UP分离的示意图。
场景1：IAB节点1(图2的a)中的双连接节点)和IAB-donor 2(即，F1终结节点(F1-termination node)，图2的a)中的辅节点)通过NR接入链路经由主节点(非F1终结节点)来交换被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包；通过回传链路和SN(secondary node，辅节点)来交换F1-U流量。SRB2被用来传输IAB-MT和MN(master node，主节点)之间的被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包。这些被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包在MN和SN之间通过XnAP(Xn Application Protocol，Xn应用协议)作为一个容器进行传递。在图2的a)中，主节点(MN)是M-NG-RAN node。
场景2：IAB节点1和MN(F1终结节点，图2的b)中的IAB-donor 2)通过NR接入链路经由SN(非F1终结节点)来交换被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包；通过回传链路和MN来交换F1-U流量。分裂的(split)SRB2被用来传输IAB-MT和SN之间的被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包。这些被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包在SN和MN之间通过XnAP作为一个容器进行传递。
这些被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包可以通过BAP子层或SRB传递，但是不支持在同一个父节点链路上同时使用这两种方 法。如果RRC在指示用于F1-C流量传输的小区组配置了用于传输F1-C流量的BH(backhaul，回传)RLC信道，则被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包通过BAP子层传递。
分裂的SRB指在多重无线双连接(Multi-Radio Dual Connectivity，MR-DC)中，MN和终端设备(例如，UE)之间的和MCG和SCG都有RLC承载的SRB。对于分裂的SRB，下行的发送路径取决于网络实现；对于上行，UE通过被MN的RRC信令配置成使用MCG路径或者是在MCG和SCG上进行复制发送。
IAB-MT具有终端设备的功能，比如支持MR-DC的相关流程和MCG/SCG相关机制。本申请的发明人发现，现有技术没有规定具体针对IAB-MT实现SCG去激活的方法，也没有规定SCG去激活对于IAB节点的CP-UP分离、路由、BH RLF(radio link failure，无线链路失败)检测指示等行为的影响；因此，现有技术不能很好地在IAB-MT上支持SCG去激活的功能。
本申请的实施例提供一种信息的发送、接收、配置方法以及装置和通信系统，使得在SCG去激活状态下，双连接IAB节点能够实现下述功能中的至少一者：支持CP-UP分离；进行路由和重新路由；触发BH RLF检测指示。
根据本申请实施例的一个方面，提供一种信息的发送装置，应用于终端节点，该装置包括：
第一发送单元，其在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息传递F1-C相关信息。
根据本申请实施例的另一个方面，提供一种信息配置装置，应用于终端节点，该装置包括：
第一接收单元，其接收RRC配置信息，所述RRC配置信息用于在SCG被去激活的情况下为所述终端节点配置指向MCG的路径。
根据本申请实施例的另一个方面，提供一种信息配置装置，应用于终端节点，所述终端节点包括IAB节点，比如IAB-MT，该装置包括：
第二接收单元，其接收RRC配置信息，所述RRC配置信息用于将所述终端节点配置为不支持SCG的激活/去激活。
根据本申请实施例的另一个方面，提供一种信息配置装置，应用于终端节点，所述终端节点包括IAB节点，比如IAB-MT
该装置包括：
第三接收单元，其接收RRC配置信息，所述RRC配置信息用于将所述终端节点配置为所述终端节点的SCG被去激活；以及
配置单元，其进行路由配置，其中，当所述终端节点的SCG被去激活时，所述SCG对应的出口链路不可用。
根据本申请实施例的另一个方面，提供一种信息的发送装置，应用于终端节点，所述终端节点包括IAB节点，比如IAB-MT，
该装置包括第二发送单元：
所述终端节点的所有激活的回传链路都发生BH RLF时，所述第二发送单元发送BH RLF检测指示；或者
当所述终端节点的至少一个回传链路收到了BH RLF检测指示，并且所述终端节点没有其他回传链路或者其他回传链路不可用或者其他回传链路处于去激活状态时，所述第二发送单元发送BH RLF检测指示。
根据本申请实施例的另一个方面，提供一种信息的接收装置，应用于网络设备节点，该装置包括：
第四接收单元，其在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息接收终端节点发送的F1-C相关信息。
根据本申请实施例的另一个方面，提供一种信息配置装置，应用于网络设备节点，该装置包括：
第三发送单元，其发送RRC配置信息，所述RRC配置信息用于在SCG被去激活的情况下为终端节点配置指向MCG的路径。
根据本申请实施例的另一个方面，提供一种信息配置装置，应用于网络设备节点，
该装置包括：
第四发送单元，其发送RRC配置信息，所述RRC配置信息用于将终端节点配置为不支持SCG的激活/去激活，所述终端节点包括IAB节点，比如IAB-MT。
本申请实施例的有益效果在于：在SCG去激活状态下，双连接IAB节点至少能够支持CP-UP分离，和/或进行路由和重新路由，和/或触发BH RLF检测指示。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在 所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是IAB父子节点关系的一个示意图；
图2是在两种NR-DC场景下达到CP-UP分离的示意图；
图3是第一方面的实施例的解决方案一的信息的发送方法的一个示意图；
图4是第一方面的实施例的解决方案二的信息配置方法的一个示意图；
图5是第一方面的实施例的解决方案三的信息配置方法的一个示意图；
图6是第二方面实施例的信息配置方法的一个示意图；
图7是第三方面的实施例的解决方案一的信息的发送方法的一个示意图；
图8是第三方面的实施例的解决方案二的信息的发送方法的一个示意图；
图9是第四方面的实施例的信息的接收方法的一个示意图；
图10是第四方面的实施例的信息配置方法的一个示意图；
图11是第四方面的实施例的另一种信息配置方法的一个示意图；
图12是第五方面的实施例的信息的发送装置的一个示意图；
图13是第五方面的实施例的信息配置装置的一个示意图；
图14是第五方面的实施例的另一种信息配置装置的一个示意图；
图15是第六方面的实施例的信息配置装置的一个示意图；
图16是第七方面的实施例的信息的发送装置的一个示意图；
图17是第八方面的实施例的信息的接收装置的一个示意图；
图18是第八方面的实施例的信息配置装置的一个示意图；
图19是第八方面的实施例的另一种信息配置装置的一个示意图；
图20是本申请实施例的电子设备的组成的一个示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：集成的接入和回传节点(IAB-node)、中继(relay)、基站(BS，Base Station)、接入点(AP、 Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、移动终端(MT，mobile termination)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。
在本申请的各实施例中，高层信令例如可以是无线资源控制(RRC)信令；例如称为RRC消息(RRC message)，例如包括MIB、系统信息(system information)、专用RRC消息；或者称为RRC IE(RRC information element)。高层信令例如还可以是F1-C信令，或者叫F1AP协议。但本申请不限于此。
在本申请的各实施例中，第一网络节点例如是IAB节点(IAB-node)，本申请将 以多跳IAB网络部署场景为例，对各实施例进行说明，其中，多个UE通过多跳的IAB节点，连接到IAB-donor，最后接入网络，该网络例如是5G网络。需要说明的是，本申请的各实施例可以不限于上述场景，例如，第一网络节点也可以是其它类型的网络节点。例如，实施例的场景也不局限于图示的几种双连接场景，也不仅限于CP-UP分离的场景。
第一方面的实施例
在IAB的CP-UP分离场景2(例如，图2的b))中，分裂的(split)SRB2被用来传输IAB-MT和SN之间的被封装到SCTP/IP中的F1-AP消息或者F1-C相关的(SCTP/)IP数据包。因为场景2中的F1-C相关信息是由SN来传递的，所以split SRB2对应的PDCP(Packet Data Convergence Protocol，分组数据汇聚协议)实体的主路径(primaryPath)被网络设备配置成指向SCG。如果SCG被去激活，那么在SCG的RLC承载上不能有传输，所以split SRB2不能使用，导致不能支持IAB的CP-UP分离，也就是控制面信令无法传输，严重影响IAB的性能。
为了解决上述问题或类似问题，本申请第一方面的实施例提供多种解决方案。
解决方案一是一种信息的发送方法。该方法应用于终端节点，该终端节点可以是IAB节点，例如，图2的IAB-node 1。
图3是第一方面的实施例的解决方案一的信息的发送方法的一个示意图。如图3所示，该方法包括：
操作301、在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息传递F1-C相关信息。
在操作301中，在终端节点(例如，终端节点的IAB-MT)发起上行信息传递过程时，当F1-C相关信息需要被传递时，IAB-MT在SRB2已经建立，或者是split SRB2已经建立且SCG没有被去激活的情况下发起RRC上行信息传递过程，该RRC上行信息传递过程能够用于传递F1-C相关信息。所述SRB2已经建立适用于CP-UP分离场景1，split SRB2已经建立且SCG没有被激活适用于CP-UP分离场景2。所述F1-C相关消息被包含在ULInformationTransfer消息中。
例如，可以在TS 38.331中对RRC标准进行增强，从而实现操作301。一个对标准的修改示例如表1所示。
表1
Figure PCTCN2022088749-appb-000001
解决方案二是一种信息配置方法。该方法应用于终端节点。
图4是第一方面的实施例的解决方案二的信息配置方法的一个示意图。如图4所示，该方法包括：
操作401、接收RRC配置信息，该RRC配置信息用于在SCG被去激活的情况下为终端节点配置指向MCG的路径。
在操作401的至少一个实施方式中，可以对RRC配置信息中的字段primaryPath(主路径)和/或字段ul-DataSplitThreshold(上行数据分裂阈值)进行适当的配置。该至少一个实施方式对于用户设备(UE)和IAB-MT都适用(即，操作401中的终端节点包括用户设备或IAB-MT)，在SCG去激活时，所有RB(radio bearer，无线承载)对应的PDCP实体都可按此方法进行配置。
RRC消息中的IE(信息元素)RadioBearerConfig可以对信令和/或数据无线承载进行增加、修改或者释放。例如，这个IE RadioBearerConfig可以携带PDCP参数等。其中，关于PDCP参数的IE PDCP-Config包含一个字段primaryPath，用于指示当这个PDCP实体关联了多于一个RLC实体时用于上行数据传输的主RLC实体的小区组ID和LCID(Logical Channel Identification，逻辑信道标识)。网络设备使用不同小区组的逻辑信道来指示分裂的承载的小区组。
在该至少一个实施方式中，在SCG被去激活时，primaryPath可以被配置成指向MCG。也就是说，primaryPath中的cell group ID字段表示主小区组(MCG)的ID，通常是0。该配置适用于所有的关联了多于一个RLC实体的PDCP实体，包括分离的SRB2对应的PDCP实体，也适用于所有UE和IAB-MT(即，操作401中的终端节点包括用户设备或IAB-MT)。
在该至少一个实施方式中，在对分裂的承载对应的PDCP进行primaryPath配置的情况下，还可以进一步配置ul-DataSplitThreshold。在主RLC实体和分裂的辅RLC实体上等待初次传输的PDCP层的数据量和RLC层的数据量的总和小于 ul-DataSplitThreshold时，终端节点将PDCP PDU(协议数据单元)提交到主RLC实体；在该总和大于或等于ul-DataSplitThreshold时，终端节点将PDCP PDU提交到主RLC实体或者辅RLC实体。在SCG去激活的状态下，除了将primaryPath(主路径)设置成指向MCG(即，主RLC实体是MCG上的RLC实体)，还可以进一步将ul-DataSplitThreshold设置为无穷大或者为缺省值(例如，将ul-DataSplitThreshold设置为缺省值可以是不对ul-DataSplitThreshold进行设置)，由此，PDCP层可以只提交到主RLC实体，即，只在MCG进行传输。
可以在TS 38.331中对RRC标准进行增强，以实现该至少一个实施方式。一个对标准的修改示例如下面的表2和表3。
表2
Figure PCTCN2022088749-appb-000002
表3
Figure PCTCN2022088749-appb-000003
在操作401的至少另一个实施方式中，可以对RRC配置信息中的f1c-TransferPathNRDC和f1c-TransferPath进行适当配置。该至少另一个实施方式对于IAB-MT适用(即，操作401中的终端节点包括IAB-MT)。
RRC信令为IAB节点配置了参数f1c-TransferPathNRDC(f1c-传递路径NR双连接)。该参数f1c-TransferPathNRDC指定了NR-DC的IAB-MT在向IAB-donor-CU传递F1-C数据包时应该使用的传递路径。如果IAB-MT的该参数f1c-TransferPathNRDC被配置成“mcg”，IAB-MT只能使用MCG来进行F1-C传递；如果IAB-MT被配置成 “scg”，IAB-MT只能使用SCG来进行F1-C传递。如果IAB-MT被配置成“both”，由IAB-MT来选择MCG或者是SCG来进行F1-C传递。
RRC信令中还为IAB节点配置了参数f1c-TransferPath(f1c-传递路径)。该参数f1c-TransferPath指定了EN-DC的IAB-MT在向IAB-donor-CU传递F1-C数据包时应该使用的传递路径。如果IAB-MT的该参数f1c-TransferPath被配置成“lte”，IAB-MT只能使用LTE(长期演进)链路来进行F1-C传递。如果IAB-MT的该参数f1c-TransferPath被配置成“nr”，IAB-MT只能使用NR(新无线)链路来进行F1-C传递。如果IAB-MT的该参数f1c-TransferPath被配置成“both”，由IAB-MT来选择LTE或者是NR链路来进行F1-C传递。如果的该参数f1c-TransferPath没有配置，IAB节点使用NR链路作为缺省配置。
在该至少另一个实施方式中，可以由网络设备配置以上参数f1c-TransferPathNRDC和/或f1c-TransferPath，其中，在SCG被去激活的情况下，配置参数f1c-TransferPathNRDC和/或f1c-TransferPath指向MCG。例如，在SCG被去激活的情况下：将f1c-TransferPathNRDC设为第一值(该第一值例如是“mcg”)，和/或将f1c-TransferPath设为第二值(该第二值例如是“lte”)。其中，在EN-DC场景中，f1c-TransferPath被设置为“lte”，意味着IAB-MT使用MCG来进行F1-C传递。
可以在TS 38.331中对RRC标准进行增强，以实现该至少另一个实施方式。一个对标准的修改示例如下面的表4和表5。
表4
Figure PCTCN2022088749-appb-000004
表5
Figure PCTCN2022088749-appb-000005
解决方案三是一种信息配置方法。该方法应用于终端节点，该终端节点包括IAB-MT(例如，图2的IAB-node 1的IAB-MT)。
图5是第一方面的实施例的解决方案三的信息配置方法的一个示意图。如图5所示，该方法包括：
操作501、接收RRC配置信息，该RRC配置信息用于将所述终端节点配置为不支持SCG的激活/去激活。
通过操作501，IAB节点可以被配置为不支持SCG去激活。
IAB节点和UE之间存在不同，例如，省电的需求不同，数据传输量也更大，如果IAB节点支持SCG去激活，会对很多功能产生影响。例如，IAB节点具有节点数据转发功能，转发通过在BAP子层进行路由，并通过配置的BH RLC信道进行传输。如果IAB-MT的SCG被去激活，会影响到SCG链路的路由转发，从而对路由表的配置和/或BH RLC信道映射配置产生影响。如果IAB节点不支持SCG去激活功能，那么就可以避免对BAP路由、路由表配置、BH RLC信道映射配置、BH RLF指示相关行为等的影响，从而使IAB节点能正常工作。
在RRC重配置消息中具有字段scg-State(辅小区组状态)，该字段scg-State指示了SCG处于去激活状态。网络设备在配置scg-State时，可以将scg-State配置为终端节点(例如，IAB-MT)不使用该字段scg-State，由此，终端节点能够被配置为不支持SCG的激活/去激活。
可以在TS 38.331中对RRC标准进行增强，以实现操作501。一个对标准的修改示例如下面的表6。
表6
Figure PCTCN2022088749-appb-000006
通过第一方面的实施例，终端节点能够支持IAB的CP-UP分离，因而控制面信令能够传输，保证了IAB节点的工作性能。
第二方面的实施例
在BAP子层进行路由时，通过BAP数据包所含的BAP路由ID在回传路由配置中进行查找匹配的条目来选择合适的出口链路。如果链路发生了RLF，或者是从某个回传链路收到了BH RLF检测指示，则该链路被认为不可用。IAB节点将进行本地重新路由(local re-routing)，比如通过匹配目的地地址，或者是BAP报头重写的方法来选择其他可用的出口链路。
在SCG去激活的状态下，如果通过回传路由配置选择了SCG对应的出口链路，则会导致数据无法发送，BAP路由失败。因此，需要避免选择IAB-MT的SCG对应的出口链路。
为了解决上述问题或类似问题，本申请第二方面的实施例提供一种信息配置方法，该方法应用于终端节点，该终端节点例如是IAB节点。
图6是第二方面实施例的信息配置方法的一个示意图，如图6所示，该方法包括：
操作601、接收RRC配置信息，该RRC配置信息用于将终端节点配置为该终端节点的SCG被去激活；以及
操作602、路由配置，其中，当该终端节点的SCG被去激活时，SCG对应的出口链路不可用。
路由配置由BAP层进行操作，当BAP层从上层(RRC层)收到SCG被去激活的指示，认为该终端节点的SCG被去激活，也就是IAB-MT的SCG链路不能进行传输。
对于BAP层来说，如果从上层收到SCG被去激活的通知，那么认为IAB-MT的SCG对应的出口链路不可用。
对于操作602，可以通过在TS 38.340中对BAP标准的路由部分进行增强来实现。一个对标准的修改示例如下面的表7。
表7
Figure PCTCN2022088749-appb-000007
通过操作602，能够避免选择IAB-MT的SCG对应的出口链路。
此外，在第二方面的实施例中，在SCG去激活的状态下，如果终端节点通过回 传路由配置的查找过程选择了SCG对应的出口链路，终端节点可以进行本地重新路由，即，重新选择其他可用出口链路。
通过第二方面的实施例，在SCG去激活的情况下，能够避免选择IAB-MT的SCG对应的出口链路。
第三方面的实施例
SCG去激活时，会对BH RLF检测指示的触发条件产生影响。现有技术中，在IAB-MT的所有的通过BAP提供F1接口的链路上都发生了回传无线链路失败时，IAB节点的DU部分会发送BH RLF检测指示。但是如果IAB-MT的SCG被去激活时，SCG链路即使没有发生无线链路失败也不能传输数据，因此这种情况下IAB节点即使只有MCG发生了RLF，因为该IAB节点自身不能通过SCG链路进行本地重新路由，所以会导致路由失败，数据丢失。
为了解决上述问题或类似问题，本申请的第三方面的实施例提供多种解决方案，使得在SCG去激活的情况下，如果MCG发生RLF或者终端节点从MCG链路收到BH RLF检测指示，该终端节点能够发送BH RLF检测指示给子节点。
解决方案一提供一种信息的发送方法，该方法应用于终端节点，该终端节点例如是IAB节点。
图7是第三方面的实施例的解决方案一的信息的发送方法的一个示意图。如图7所示，信息的发送方法包括：
操作701、终端节点的所有激活的回传链路都发生BH RLF时，发送BH RLF检测指示；或者，当终端节点的至少一个回传链路收到了BH RLF检测指示，并且该终端节点没有其他回传链路或者其他回传链路不可用或者其他回传链路处于去激活状态时，发送BH RLF检测指示。
在操作701的至少一个实施例中，在定义BAP层的BH RLF相关指示的发送操作时，可以增加如下行为：当在终端节点(例如，IAB节点)的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，IAB-DU上的并置的BAP实体的发送部分可以组建(例如，组建一个)用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路(例如，提交到每一个关联到该IAB-DU的出口链路)。其中，当一个链路对应的是IAB-MT的SCG链路且SCG被去激活时，该 链路被认为是去激活链路；否则，该链路被认为是激活的链路。
在至少一个实施方式中，可以在TS 38.340中对BAP层标准进行增强，以实现操作701。一个对标准的修改示例如下面的表8所示。
表8
Figure PCTCN2022088749-appb-000008
IAB节点在MT是单连接情况或者是双连接但是自身没有能力做本地重新路由的情况下，可以将收到的BH RLF检测指示进行传播，也就是发送BH RLF检测指示给子节点。
如果考虑BH RLF检测指示可以传播的情况，当某个回传链路收到了BH RLF检测指示，而没有其他回传链路或者其他回传链路不可用或者是其他回传链路处于去激活状态时，需要传播收到的BH RLF检测指示。因为用于BH RLF指示的BAP控制PDU格式都是一样，传播BH RLF检测指示等于是自身发送一个BH RLF检测指示。
在操作701的至少一个实施例中，在定义BAP层的RLF相关行为时，可以增加如下行为：当在IAB-MT的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，或者是当从一个回传链路收到BH RLF检测指示且没有其他可用的通过BAP提供F1接口的链路，IAB-DU上的并置的BAP实体的发送部分可以组建(例如，组建一个)用于BH RLF检测指示的BAP控制PDU并提交到每一个关联到该IAB-DU的出口链路(例如，提交到每一个关联到该IAB-DU的出口链路)。
在至少一个实施方式中，可以在TS 38.340中对RRC标准进行增强，以实现操作701。一个对标准的修改示例如下面的表9所示。
表9
Figure PCTCN2022088749-appb-000009
在表9对应的实施方式中，关于“可用(available)”的说明，可以参见第二方面的实施例的相关说明，即，表9对应的实施方式基于第二方面的实施例(例如，第二方面的实施例被标准所接受)。
此外，如果不基于第二方面的实施例(例如，第二方面的实施例没有被标准所接受)，那么，操作701可以使用“激活的(activated)”相关概念来设定终端节点的行为。“激活的链路”定义见前述说明。
例如，在定义BAP层的RLF相关行为时，可以增加如下行为：当在IAB-MT的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，或者是当从一个回传链路收到BH RLF检测指示且没有其他可用且激活的通过BAP提供F1接口的链路，IAB-DU上的并置的BAP实体的发送部分可以组建(例如，组建一个)用于BH RLF检测指示的BAP控制PDU并提交到每一个关联到该IAB-DU的出口链路(例如，提交到每一个关联到该IAB-DU的出口链路)。
在至少另一个实施方式中，可以在TS 38.340中对RRC标准进行增强，以实现操作701。一个对标准的修改示例如下面的表10所示。
表10
Figure PCTCN2022088749-appb-000010
表10在表9的基础上，增加了基于“激活的(activated)”来设定终端节点的行为的技术方案。
解决方案二提供一种信息的发送方法，该方法应用于终端节点，该终端节点例如是IAB节点。
图8是第三方面的实施例的解决方案二的信息的发送方法的一个示意图。如图8所示，信息的发送方法包括：
操作801、终端节点的MCG发生BH RLF且SCG被去激活时，发送该BH RLF检测指示。
在操作801的至少一个实施例方式中，在定义BAP层的BH RLF相关指示的发 送操作时，可以增加如下行为：当在IAB-MT的所有的通过BAP提供F1接口的链路上都发生了回传无线链路失败时，或者当IAB-MT的MCG发生了回传无线链路失败且SCG被去激活时，IAB-DU上的并置的BAP实体的发送部分可以组建(例如，组建一个)用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路(例如，提交到每一个关联到该IAB-DU的出口链路)。
例如，可以在TS 38.340中对BAP层标准进行增强，以实现操作801。一个对标准的修改示例如下面的表11所示。
表11
Figure PCTCN2022088749-appb-000011
在操作801的至少另一个实施方式中，如果考虑BH RLF检测指示可以传播的情况，当某个回传链路收到了BH RLF检测指示，而其他链路不可用，或者是当IAB-MT从MCG收到了BH RLF检测指示且SCG被去激活，那么传播收到的BH RLF检测指示。
例如，在定义BAP层的BH RLF相关指示的发送操作时，可以增加如下行为：当在IAB-MT的所有的通过BAP提供F1接口的链路上都发生了回传无线链路失败时，或者当从某个回传链路收到了BH RLF检测指示且其他通过BAP提供F1接口的链路都不可用，或者当IAB-MT的MCG发生了回传无线链路失败且SCG被去激活，或者当IAB-MT从MCG收到了BH RLF检测指示且SCG被去激活时，IAB-DU上的并置的BAP实体的发送部分可以组建一个用于BH RLF检测指示的BAP控制PDU并提交到每一个关联到该IAB-DU的出口链路。
具体地，可以在TS 38.340中对BAP层标准进行增强，以实现操作801的该至少另一个实施方式。一个对标准的修改示例如下面的表12所示。
表12
Figure PCTCN2022088749-appb-000012
通过第三方面的实施例，在SCG去激活的情况下，MCG发生RLF或者是从MCG链路收到BH RLF检测指示时，能够发送BH RLF检测指示给子节点。
第四方面的实施例
第四方面的实施例提供一种信息的接收方法，与第一方面的实施例的解决方案一的信息的发送方法对应。该方法应用于网络设备节点，例如，图2的a)或b)中的IAB-donor。
图9是第四方面的实施例的信息的接收方法的一个示意图。如图9所示，该方法包括：
操作901、在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息接收终端节点发送的F1-C相关信息。
在操作901中，终端节点可以是IAB节点，比如IAB-MT。在至少一个实施例中，在终端节点的SRB2已经建立的情况下，或者，终端节点的split SRB2已经建立且SCG没有被去激活的情况下，网络设备节点可以使用split SRB2承载的RRC消息接收该F1-C相关信息。
第四方面的实施例还提供一种信息配置方法，与第一方面的实施例的解决方案二的信息配置方法对应。该方法应用于网络设备节点。
图10是第四方面的实施例的信息配置方法的一个示意图。如图10所示，该方法包括：
操作1001、发送RRC配置信息，该RRC配置信息用于在SCG被去激活的情况下为终端节点配置指向MCG的路径。
在操作1001的至少一个实施方式中，终端节点可以包括用户设备或IAB节点，比如IAB-MT，对应地，网络设备节点可以包括基站或IAB-donor。
在终端节点的SCG为去激活的状态下，RRC配置信息中的主路径(primaryPath)被设置成指向MCG。此外，该RRC配置信息的上行数据分裂阈值(ul-DataSplitThreshold)还可以被设置为无穷大或被设置为缺省值。该主路径和/或该上行数据分裂阈值配置适用于所有的关联了多于一个RLC实体的PDCP实体，包括分离的SRB2对应的PDCP实体。
在操作1001的至少另一个实施方式中，终端节点可以包括IAB节点，比如 IAB-MT，对应地，网络设备节点可以包括IAB-donor。
在终端节点的SCG为去激活的状态下，f1c传递路径NR双连接(f1c-TransferPathNRDC)参数和/或f1c传递路径(f1c-TransferPath)参数被配置成指向MCG。例如，在SCG为去激活的状态下，f1c传递路径NR双连接(f1c-TransferPathNRDC)参数被设置为第一值，该第一值例如是“MCG”；在SCG为去激活的状态下，f1c传递路径(f1c-TransferPath)参数被设置为第二值，该第二值例如是“lte”。
第四方面的实施例还提供另一种信息配置方法，与第一方面的实施例的解决方案三的信息配置方法对应。该方法应用于网络设备节点，例如，图2的a)或b)中的IAB-donor。
图11是第四方面的实施例的另一种信息配置方法的一个示意图。如图11所示，该方法包括：
操作1101、发送RRC配置信息，RRC配置信息用于将终端节点配置为不支持SCG的激活/去激活。
在操作1101的至少一个实施方式中，终端节点可以包括IAB节点，比如IAB-MT，对应地，网络设备节点可以包括IAB-donor。
在操作1101中，RRC配置信息中的辅小区组状态(scg-State)字段可以被设置为该终端节点不使用该字段。
通过第四方面的实施例，终端节点能够支持IAB的CP-UP分离，因而控制面信令能够传输，保证了IAB节点的性能。
第五方面的实施例
第五方面的实施例提供一种信息的发送装置，与第一方面的实施例的解决方案一的信息的发送方法对应。该装置应用于终端节点。
图12是第五方面的实施例的信息的发送装置的一个示意图。如图12所示，该装置1200包括：
第一发送单元1201，其在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息传递F1-C相关信息。
在至少一个实施例中，终端节点可以是IAB节点，比如IAB-MT。第一发送单元 1201在SRB2已经建立的情况下发起RRC上行信息传递过程，或者，第一发送单元1201在split SRB2已经建立且SCG没有被去激活的情况下发起RRC上行信息传递过程。
第五方面的实施例还提供一种信息配置方法，与第一方面的实施例的解决方案二的信息配置方法对应。该装置应用于终端节点。
图13是第五方面的实施例的信息配置装置的一个示意图。如图13所示，该装置1300包括：
第一接收单元1301，其接收RRC配置信息，所述RRC配置信息用于在SCG被去激活的情况下为所述终端节点配置指向MCG的路径。
在至少一个实施方式中，终端节点包括用户设备或IAB节点(IAB节点例如IAB-MT)。在SCG为去激活的状态下，RRC配置信息中的主路径(primaryPath)被设置成指向MCG。此外，该RRC配置信息的上行数据分裂阈值(ul-DataSplitThreshold)被设置为无穷大或设置为缺省值。
在至少另一个实施方式中，终端节点包括IAB节点。在SCG为去激活的状态下，f1c传递路径NR双连接(f1c-TransferPathNRDC)参数和/或f1c传递路径(f1c-TransferPath)参数被配置成指向MCG。例如，在SCG为去激活的状态下，f1c传递路径NR双连接(f1c-TransferPathNRDC)参数被设置为第一值，第一值例如是“MCG”。又例如，在SCG为去激活的状态下，f1c传递路径(f1c-TransferPath)参数被设置为第二值，第二值例如是“lte”。
第五方面的实施例还提供另一种信息配置装置，与第一方面的实施例的解决方案三的信息配置方法对应。该装置应用于终端节点。
图14是第五方面的实施例的另一种信息配置装置的一个示意图。如图14所示，该装置1400包括：
第二接收单元1401，其接收RRC配置信息，所述RRC配置信息用于将所述终端节点配置为不支持SCG的激活/去激活。
RRC配置信息中的辅小区组状态(scg-State)字段被设置为终端节点不使用该字段。
第六方面的实施例
第六方面的实施例提供一种信息配置装置，与第二方面的实施例对应。该装置应用于终端节点。
图15是第六方面的实施例的信息配置装置的一个示意图。如图15所示，该装置1500包括：
第三接收单元1501，其接收RRC配置信息，所述RRC配置信息用于将所述终端节点配置为所述终端节点的SCG被去激活；以及
配置单元1502，其进行路由配置，其中，当所述终端节点的SCG被去激活时，所述SCG对应的出口链路不可用。
在至少一个实施方式中，在通过回传路由配置的查找过程选择了所述SCG对应的出口链路的情况下，配置单元1502进行本地重新路由。
第七方面的实施例
本申请第七方面的实施例提供一种信息的发送装置，与第三方面的实施例所述的信息的发送方法对应。该装置应用于终端节点，该终端节点包括IAB节点。
图16是第七方面的实施例的信息的发送装置的一个示意图，如图16所示，信息的发送装置1600包括第二发送单元1601。
在至少一个实施方式中，第二发送单元1601可以对应于第三方面的实施例的解决方案一所述的信息的发送方法。
即，终端节点的所有激活的回传链路都发生BH RLF时，第二发送单元1601发送BH RLF检测指示；或者，当终端节点的至少一个回传链路收到了BH RLF检测指示，并且终端节点没有其他回传链路或者其他回传链路不可用或者其他回传链路处于去激活状态时，第二发送单元1601发送BH RLF检测指示。
例如，当在所述终端节点的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。其中，当所述终端节点的链路为所述终端节点的SCG链路并且所述SCG被去激活时，所述链路是去激活的链路；也就是说，在所述终端节点的链路不是SCG链路，或者所述SCG在激活状态是，该链路是激活的链路。
例如，当在所述终端节点的所有的通过BAP提供F1接口的激活的链路上都发生 了回传无线链路失败时，或者当从一个回传链路收到BH RLF检测指示且没有其他可用的通过BAP提供F1接口的链路，所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
例如，当在所述终端节点的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，或者当从一个回传链路收到BH RLF检测指示且没有其他可用且激活的通过BAP提供F1接口的链路，所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
在至少另一个实施方式中，第二发送单元1601可以对应于第三方面的实施例的解决方案二所述的信息的发送方法。
即，在终端节点的MCG发生BH RLF且SCG被去激活时，所述第二发送单元1601发送BH RLF检测指示。
例如，当所述终端节点的所有的通过BAP提供F1接口的链路上都发生了回传无线链路失败时，或者当IAB-MT的MCG发生了回传无线链路失败且SCG被去激活时，所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
例如，当所述终端节点的至少一个回传链路收到了BH RLF检测指示且所述终端节点的其他回传链路不可用时，或者，当所述终端节点从MCG收到了BH RLF检测指示且SCG被去激活时，第二发送单元1601发送收到的BH RLF检测指示。
例如，当终端节点的所有的通过BAP提供F1接口的链路上都发生了回传无线链路失败时，或者当从至少一个回传链路收到了BH RLF检测指示且其他通过BAP提供F1接口的链路都不可用，或者当所述终端节点的MCG发生了回传无线链路失败且SCG被去激活，或者当所述终端节点从MCG收到了BH RLF检测指示且SCG被去激活时，所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
第八方面的实施例
第八方面的实施例提供一种信息的接收装置，与第一方面的实施例的解决方案一 的信息的发送方法对应。该方法应用于网络设备节点，例如，图2的a)或b)中的IAB-donor。
图17是第八方面的实施例的信息的接收装置的一个示意图。如图17所示，该装置1700包括：
第四接收单元1701，其在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息接收终端节点发送的F1-C相关信息。
其中，终端节点可以是IAB节点，比如IAB-MT。在至少一个实施例中，在终端节点的SRB2已经建立的情况下，或者，终端节点的split SRB2已经建立且SCG没有被去激活的情况下，第四接收单元1701使用split SRB2承载的RRC消息接收终端节点发送的F1-C相关信息。
第八方面的实施例还提供一种信息配置装置，与第一方面的实施例的解决方案二的信息配置方法对应。该方法应用于网络设备节点。
图18是第八方面的实施例的信息配置装置的一个示意图。如图18所示，该装置1800包括：
第三发送单元1801，其发送RRC配置信息，所述RRC配置信息用于在SCG被去激活的情况下为终端节点配置指向MCG的路径。
在至少一个实施方式中，终端节点可以包括用户设备或IAB节点(该IAB节点例如是IAB-MT)，对应地，网络设备节点可以包括基站或IAB-donor。
在SCG为去激活的状态下，RRC配置信息中的主路径(primaryPath)被设置成指向MCG。此外，该RRC配置信息的上行数据分裂阈值(ul-DataSplitThreshold)还可以被设置为无穷大或被设置为缺省值。
在至少另一个实施方式中，终端节点可以包括IAB节点，比如IAB-MT，对应地，网络设备节点可以包括IAB-donor。
在SCG为去激活的状态下，f1c传递路径NR双连接(f1c-TransferPathNRDC)参数和/或f1c传递路径(f1c-TransferPath)参数被配置成指向MCG。例如，在SCG为去激活的状态下，f1c传递路径NR双连接(f1c-TransferPathNRDC)参数被设置为第一值，该第一值例如是“MCG”；在SCG为去激活的状态下，f1c传递路径(f1c-TransferPath)参数被设置为第二值，该第二值例如是“lte”。
第八方面的实施例还提供另一种信息配置装置，与第一方面的实施例的解决方案 三的信息配置方法对应。该方法应用于网络设备节点，例如，图2的a)或b)中的IAB-donor。
图19是第八方面的实施例的另一种信息配置装置的一个示意图。如图19所示，该装置1900包括：
第四发送单元1901，其发送RRC配置信息，所述RRC配置信息用于将终端节点配置为不支持SCG的激活/去激活。
在至少一个实施方式中，终端节点可以包括IAB节点，比如IAB-MT，对应地，网络设备节点可以包括IAB-donor。
在第四发送单元1901的操作中，RRC配置信息中的辅小区组状态(scg-State)字段可以被设置为该终端节点不使用该字段。
第九方面的实施例
本申请实施例还提供一种通信系统，该通信系统可以包括终端节点和网络设备节点。该终端节点和网络设备节点中的至少一者可以具有图20所示的电子设备的组成。
图20是本申请实施例的电子设备的组成的一个示意图。如图20所示，电子设备2000可以包括：处理器2010(例如中央处理器CPU)和存储器2020；存储器2020耦合到处理器2010。其中该存储器2020可存储各种数据；此外还存储信息处理的程序2030，并且在处理器2010的控制下执行该程序2030。
例如，处理器2010可以被配置为执行程序而实现如第一方面的实施例至第四方面的实施例中的方法。
此外，如图20所示，电子设备2000还可以包括：收发机2040和天线2050等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，电子设备2000也并不是必须要包括图20中所示的所有部件；此外，电子设备2000还可以包括图20中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在终端节点中执行所述程序时，所述程序使得所述终端节点执行第一方面至第三方面的实施例所述的方法。
本申请实施例还提供一种计算机程序，其中当在网络设备节点中执行所述程序时，所述程序使得所述网络设备节点执行第四方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使 得电子设备执行第一方面至第四方面的实施例所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
(终端侧)
1.一种信息的发送方法，应用于终端节点，该方法包括：
在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息传递F1-C相关信息。
2.如附记1所述的方法，其中，所述终端节点包括IAB节点，
所述终端节点在SRB2已经建立的情况下发起RRC上行信息传递过程，或者，所述终端节点在split SRB2已经建立且SCG没有被去激活的情况下发起RRC上行信息传递过程。
3.一种信息配置方法，应用于终端节点，该方法包括：
接收RRC配置信息，所述RRC配置信息用于在SCG被去激活的情况下为所述终端节点配置指向MCG的路径。
4.如附记3所述的方法，其中，
所述终端节点包括用户设备或IAB节点，
在SCG为去激活的状态下，所述RRC配置信息中的主路径(primaryPath)被设置成指向MCG。
5.如附记4所述的方法，其中，
所述RRC配置信息的上行数据分裂阈值(ul-DataSplitThreshold)被设置为无穷大或设置为缺省值。
6.如附记3所述的方法，其中，
所述终端节点包括IAB节点，
在SCG为去激活的状态下，f1c传递路径NR双连接(f1c-TransferPathNRDC)参数和/或f1c传递路径(f1c-TransferPath)参数被配置成指向MCG。
7.如附记6所述的方法，其中，
在SCG为去激活的状态下，所述f1c传递路径NR双连接(f1c-TransferPathNRDC)参数被设置为第一值。
8.如附记6所述的方法，其中，
在SCG为去激活的状态下，所述f1c传递路径(f1c-TransferPath)参数被设置为第二值。
9.一种信息配置方法，应用于终端节点，所述终端节点包括IAB节点，
该方法包括：
接收RRC配置信息，所述RRC配置信息用于将所述终端节点配置为不支持SCG的激活/去激活。
10.如附记9所述的方法，其中，
所述RRC配置信息中的辅小区组状态(scg-State)字段被设置为所述终端节点不使用该字段。
11.一种信息配置方法，应用于终端节点，所述终端节点包括IAB节点，
该方法包括：
接收RRC配置信息，所述RRC配置信息用于将所述终端节点配置为所述终端节点的SCG被去激活；以及
路由配置，其中，当所述终端节点的SCG被去激活时，所述SCG对应的出口链路不可用。
12.如附记11所述的方法，其中，所述方法还包括：
在通过回传路由配置的查找过程选择了所述SCG对应的出口链路的情况下，所述终端节点进行本地重新路由。
13.一种信息的发送方法，应用于终端节点，所述终端节点包括IAB节点，
该方法包括：
所述终端节点的所有激活的回传链路都发生BH RLF时，发送BH RLF检测指示；或者
当所述终端节点的至少一个回传链路收到了BH RLF检测指示，并且所述终端节点没有其他回传链路或者其他回传链路不可用或者其他回传链路处于去激活状态时，发送BH RLF检测指示。
14.如附记13所述的方法，其中，
当在所述终端节点的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，
所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
15.如附记13所述的方法，其中，
当所述终端节点的链路为所述终端节点的SCG链路并且所述SCG被去激活时，所述链路是去激活的链路。
16.如附记13所述的方法，其中，
在所述终端节点的链路不是SCG链路，或者所述SCG在激活状态，
所述链路是激活的链路。
17.如附记13所述的方法，其中，
当在所述终端节点的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，或者当从一个回传链路收到BH RLF检测指示且没有其他可用的通过BAP提供F1接口的链路，所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
18.如附记13所述的方法，其中，
当在所述终端节点的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，或者当从一个回传链路收到BH RLF检测指示且没有其他可用且激活的通过BAP提供F1接口的链路，所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
19.如附记13所述的方法，其中，
所述终端节点的MCG发生BH RLF且SCG被去激活时，发送所述BH RLF检测指示。
20.如附记19所述的方法，其中，
当所述终端节点的所有的通过BAP提供F1接口的链路上都发生了回传无线链路失败时，或者当IAB节点的MCG发生了回传无线链路失败且SCG被去激活时，
所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
21.如附记13所述的方法，其中，
当所述终端节点的至少一个回传链路收到了BH RLF检测指示且所述终端节点的其他回传链路不可用时，或者，当所述终端节点从MCG收到了BH RLF检测指示且SCG被去激活时，
所述终端节点发送收到的BH RLF检测指示。
22.如附记21所述的方法，其中，
当所述终端节点的所有的通过BAP提供F1接口的链路上都发生了回传无线链路失败时，或者当从至少一个回传链路收到了BH RLF检测指示且其他通过BAP提供F1接口的链路都不可用，或者当所述终端节点的MCG发生了回传无线链路失败且SCG被去激活，或者当所述终端节点从MCG收到了BH RLF检测指示且SCG被去激活时，
所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
(网络侧)
23.一种信息的接收方法，应用于网络设备节点，该方法包括：
在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息接收终端节点发送的F1-C相关信息。
24.如附记23所述的方法，其中，所述终端节点包括IAB节点，
在SRB2已经建立的情况下，或者，split SRB2已经建立且SCG没有被去激活的情况下，所述网络设备节点使用split SRB2承载的RRC消息接收所述F1-C相关信息。
25.一种信息配置方法，应用于网络设备节点，该方法包括：
发送RRC配置信息，所述RRC配置信息用于在SCG被去激活的情况下为终端节点配置指向MCG的路径。
26.如附记25所述的方法，其中，
所述终端节点包括用户设备或IAB节点，
在SCG为去激活的状态下，所述RRC配置信息中的主路径(primaryPath)被设置成指向MCG。
27.如附记26所述的方法，其中，
所述RRC配置信息的上行数据分裂阈值(ul-DataSplitThreshold)被设置为无穷大或被设置为缺省值。
28.如附记25所述的方法，其中，
所述终端节点包括IAB节点，
在SCG为去激活的状态下，f1c传递路径NR双连接(f1c-TransferPathNRDC)参数和/或f1c传递路径(f1c-TransferPath)参数被配置成指向MCG。
29.如附记28所述的方法，其中，
在SCG为去激活的状态下，所述f1c传递路径NR双连接(f1c-TransferPathNRDC)参数被设置为第一值。
30.如附记28所述的方法，其中，
在SCG为去激活的状态下，所述f1c传递路径(f1c-TransferPath)参数被设置为第二值。
31.一种信息配置方法，应用于网络设备节点，
该方法包括：
发送RRC配置信息，所述RRC配置信息用于将终端节点配置为不支持SCG的激活/去激活，所述终端节点包括IAB节点。
32.如附记31所述的方法，其中，
所述RRC配置信息中的辅小区组状态(scg-State)字段被设置为所述终端节点不使用该字段。

Claims (18)

  1. 一种信息的发送装置，应用于终端节点，该装置包括：
    第一发送单元，其在SCG没有被去激活的情况下，使用split SRB2承载的RRC消息传递F1-C相关信息。
  2. 如权利要求1所述的装置，其中，所述终端节点是IAB节点，
    所述终端节点在SRB2已经建立的情况下发起RRC上行信息传递过程，或者，所述终端节点在split SRB2已经建立且SCG没有被去激活的情况下发起RRC上行信息传递过程。
  3. 一种信息配置装置，应用于终端节点，该装置包括：
    第一接收单元，其接收RRC配置信息，所述RRC配置信息用于在SCG被去激活的情况下为所述终端节点配置指向MCG的路径。
  4. 如权利要求3所述的装置，其中，
    所述终端节点包括用户设备或IAB节点，
    在SCG为去激活的状态下，所述RRC配置信息中的主路径(primaryPath)被设置成指向MCG。
  5. 如权利要求4所述的装置，其中，
    所述RRC配置信息的上行数据分裂阈值(ul-DataSplitThreshold)被设置为无穷大或设置为缺省值。
  6. 如权利要求3所述的装置，其中，
    所述终端节点包括IAB节点，
    在SCG为去激活的状态下，f1c传递路径NR双连接(f1c-TransferPathNRDC)参数和/或f1c传递路径(f1c-TransferPath)参数被配置成指向MCG。
  7. 如权利要求6所述的装置，其中，
    在SCG为去激活的状态下，所述f1c传递路径NR双连接(f1c-TransferPathNRDC)参数被设置为第一值。
  8. 如权利要求6所述的装置，其中，
    在SCG为去激活的状态下，所述f1c传递路径(f1c-TransferPath)参数被设置为第二值。
  9. 一种信息的发送装置，应用于终端节点，所述终端节点包括IAB节点，
    该装置包括第二发送单元：
    所述终端节点的所有激活的回传链路都发生BH RLF时，所述第二发送单元发送BH RLF检测指示；或者
    当所述终端节点的至少一个回传链路收到了BH RLF检测指示，并且所述终端节点没有其他回传链路或者其他回传链路不可用或者其他回传链路处于去激活状态时，所述第二发送单元发送BH RLF检测指示。
  10. 如权利要求9所述的装置，其中，
    当在所述终端节点的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，
    所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
  11. 如权利要求9所述的装置，其中，
    当所述终端节点的链路为所述终端节点的SCG链路并且所述SCG被去激活时，所述链路是去激活的链路。
  12. 如权利要求9所述的装置，其中，
    在所述终端节点的链路不是SCG链路，或者所述SCG在激活状态，
    所述链路是激活的链路。
  13. 如权利要求9所述的装置，其中，
    当在所述终端节点的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，或者当从一个回传链路收到BH RLF检测指示且没有其他可用的通过BAP提供F1接口的链路，所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
  14. 如权利要求9所述的装置，其中，
    当在所述终端节点的所有的通过BAP提供F1接口的激活的链路上都发生了回传无线链路失败时，或者当从一个回传链路收到BH RLF检测指示且没有其他可用且激活的通过BAP提供F1接口的链路，所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
  15. 如权利要求9所述的装置，其中，
    所述终端节点的MCG发生BH RLF且SCG被去激活时，发送所述BH RLF检测指示。
  16. 如权利要求15所述的装置，其中，
    当所述终端节点的所有的通过BAP提供F1接口的链路上都发生了回传无线链路失败时，或者当IAB节点的MCG发生了回传无线链路失败且SCG被去激活时，
    所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
  17. 如权利要求9所述的装置，其中，
    当所述终端节点的至少一个回传链路收到了BH RLF检测指示且所述终端节点的其他回传链路不可用时，或者，当所述终端节点从MCG收到了BH RLF检测指示且SCG被去激活时，
    所述第二发送单元发送收到的BH RLF检测指示。
  18. 如权利要求17所述的装置，其中，
    当所述终端节点的所有的通过BAP提供F1接口的链路上都发生了回传无线链路失败时，或者当从至少一个回传链路收到了BH RLF检测指示且其他通过BAP提供F1接口的链路都不可用，或者当所述终端节点的MCG发生了回传无线链路失败且SCG被去激活，或者当所述终端节点从MCG收到了BH RLF检测指示且SCG被去激活时，
    所述终端节点对应的IAB-DU上的并置的BAP实体的发送部分组建用于BH RLF检测指示的BAP控制PDU并提交到关联到该IAB-DU的出口链路。
PCT/CN2022/088749 2022-04-24 2022-04-24 信息的发送、接收、配置方法以及装置和通信系统 WO2023205941A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/088749 WO2023205941A1 (zh) 2022-04-24 2022-04-24 信息的发送、接收、配置方法以及装置和通信系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/088749 WO2023205941A1 (zh) 2022-04-24 2022-04-24 信息的发送、接收、配置方法以及装置和通信系统

Publications (1)

Publication Number Publication Date
WO2023205941A1 true WO2023205941A1 (zh) 2023-11-02

Family

ID=88516574

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/088749 WO2023205941A1 (zh) 2022-04-24 2022-04-24 信息的发送、接收、配置方法以及装置和通信系统

Country Status (1)

Country Link
WO (1) WO2023205941A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021028807A1 (en) * 2019-08-09 2021-02-18 Telefonaktiebolaget Lm Ericsson (Publ) Dual connectivity recovery on backhaul failure
WO2021057389A1 (zh) * 2019-09-27 2021-04-01 华为技术有限公司 一种双连接管理方法和通信装置
WO2021230544A1 (en) * 2020-05-12 2021-11-18 Samsung Electronics Co., Ltd. Method and apparatus for radio link failure reporting in wireless communication system
WO2022027168A1 (en) * 2020-08-03 2022-02-10 Zte Corporation Wireless cell activation and deactivation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021028807A1 (en) * 2019-08-09 2021-02-18 Telefonaktiebolaget Lm Ericsson (Publ) Dual connectivity recovery on backhaul failure
WO2021057389A1 (zh) * 2019-09-27 2021-04-01 华为技术有限公司 一种双连接管理方法和通信装置
WO2021230544A1 (en) * 2020-05-12 2021-11-18 Samsung Electronics Co., Ltd. Method and apparatus for radio link failure reporting in wireless communication system
WO2022027168A1 (en) * 2020-08-03 2022-02-10 Zte Corporation Wireless cell activation and deactivation

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 37.340, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V17.0.0, 15 April 2022 (2022-04-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 110, XP052145991 *
ZTE CORPORATION: "Introduction of SCG deactivation and activation", 3GPP DRAFT; R2-2202032, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-meeting; 20220117 - 20220125, 31 January 2022 (2022-01-31), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052104451 *

Similar Documents

Publication Publication Date Title
US10499307B2 (en) System and method for dynamic data relaying
WO2020164613A1 (zh) 中继通信的方法和装置
US20200128430A1 (en) METHOD FOR TRANSMITTING UL PACKET BASED ON QUALITY OF SERVICE (QoS) FLOW IN WIRELESS COMMUNICATION SYSTEM AND A DEVICE THEREFOR
EP3659355B1 (en) Method for handling of a prohibit timer to transmit a rrc message related to ue capability restriction in wireless communication system and a device therefor
US20200154304A1 (en) Method for performing reflective quality of service in wireless communication system and a device therefor
WO2022036555A1 (zh) 中继传输的方法、中继终端和远端终端
WO2021218938A1 (zh) 一种资源协调方法及装置
AU2018402241A1 (en) Relay transmission method and relay node
CN115699816A (zh) 用于在双连接下进行侧行链路中继通信的方法
US20230254729A1 (en) Migration method and apparatus for iab-node
WO2017193402A1 (zh) 一种数据传输方法、装置及系统
WO2022236644A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2022205252A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2023205941A1 (zh) 信息的发送、接收、配置方法以及装置和通信系统
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2023197105A1 (zh) 配置信息的方法、装置和通信系统
WO2023150968A1 (zh) 收发信号的方法、装置和通信系统
WO2023130260A1 (zh) Rrc消息的配置方法、装置和系统
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统
WO2022205251A1 (zh) 信息收发方法，数据发送方法以及装置
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
WO2023092482A1 (zh) 一种通过中继终端进行通信的方法及装置、终端
WO2022205485A1 (zh) 信息收发方法以及装置
WO2014000611A1 (zh) 传输数据的方法和装置

Legal Events

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

Ref document number: 22938800

Country of ref document: EP

Kind code of ref document: A1