WO2022206544A1 - 数据调度方法、装置及设备 - Google Patents
数据调度方法、装置及设备 Download PDFInfo
- Publication number
- WO2022206544A1 WO2022206544A1 PCT/CN2022/082731 CN2022082731W WO2022206544A1 WO 2022206544 A1 WO2022206544 A1 WO 2022206544A1 CN 2022082731 W CN2022082731 W CN 2022082731W WO 2022206544 A1 WO2022206544 A1 WO 2022206544A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- iab node
- iab
- node
- donor
- bap
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 238000011084 recovery Methods 0.000 claims abstract description 34
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 25
- 238000004891 communication Methods 0.000 claims abstract description 18
- 238000013507 mapping Methods 0.000 claims description 18
- 230000005540 biological transmission Effects 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 9
- 230000003044 adaptive effect Effects 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 14
- 108091047090 iab-4 stem-loop Proteins 0.000 description 14
- 230000008569 process Effects 0.000 description 12
- 230000000694 effects Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 4
- 230000009849 deactivation Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 101150014328 RAN2 gene Proteins 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/121—Wireless traffic scheduling for groups of terminals or users
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
Definitions
- the present application belongs to the field of communication technologies, and in particular relates to a data scheduling method, apparatus and device.
- IAB nodes support type-2/3 Radio Link Failure indication (type-2/3 RLF indication), where the type 2 backhaul radio link failure indication (type-2 backhaul Radio Link Failure indication, type-2 BH RLF indication) indicates that a radio link failure occurs between an IAB node and its parent IAB node, and the child IAB node is notified that "the wireless link is detected.
- "Link failure RLF"; type-3 BH RLF indication indicates that the radio link between an IAB node and its parent IAB node fails and the radio link recovers successfully, and the child IAB node is notified of the successful RLF recovery.
- IAB-donor-Centralized Unit IAB-donor-CU
- IAB-donor-CU IAB-donor-Centralized Unit
- the embodiments of the present application provide a data scheduling method, apparatus and device, which can solve the problem of unnecessary loss of uplink transmission data after the IAB node and the wireless link are restored.
- a data scheduling method comprising:
- the first IAB node receives the BAP control PDU, the first IAB node is the downstream node of the second IAB node, and the BAP control PDU is used to indicate whether the topology network accessed by the third IAB node and the fourth IAB node has changed,
- the third IAB node is the upstream IAB node after the second IAB node performs radio link recovery, and the fourth IAB node is the upstream IAB node before the second IAB node performs radio link recovery;
- the first IAB node performs a corresponding data scheduling operation on the downstream node of the first IAB node according to the BAP control PDU, and the downstream node of the first IAB node is an IAB node or a terminal.
- a data scheduling apparatus including:
- the receiving module is used for the first IAB node to receive the BAP control PDU, the first IAB node is the downstream node of the second IAB node, and the BAP control PDU is used to indicate the topology of the third IAB node and the fourth IAB node access Whether the network has changed, the third IAB node is the upstream IAB node after the second IAB node performs radio link recovery, and the fourth IAB node is the upstream IAB node before the second IAB node performs radio link recovery IAB node;
- a first scheduling module used for the first IAB node to perform a corresponding data scheduling operation on the downstream node of the first IAB node according to the BAP control PDU, where the downstream node of the first IAB node is an IAB node or terminal.
- a terminal in a third aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor.
- a terminal including a processor and a communication interface, wherein the communication interface is used for a first IAB node to receive a BAP control PDU, and the first IAB node is a downstream node of the second IAB node, so
- the BAP control PDU is used to indicate whether the topology network accessed by the third IAB node and the fourth IAB node has changed, and the third IAB node is the upstream IAB node after the second IAB node performs wireless link recovery, so
- the fourth IAB node is the upstream IAB node before the second IAB node performs radio link recovery;
- the processor is used by the first IAB node to perform the operation of the first IAB node on the downstream of the first IAB node according to the BAP control PDU.
- the node performs a corresponding data scheduling operation, and the downstream node of the first IAB node is an IAB node or a terminal.
- a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method according to the first aspect are implemented.
- a chip in a sixth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the method according to the first aspect A step of.
- a seventh aspect provides a computer program product, the computer program product being stored in a non-volatile storage medium, the program/program product being executed by at least one processor to implement the method according to the first aspect A step of.
- the first IAB node performs a corresponding data scheduling operation on the downstream node according to whether the topology network accessed by the node performing wireless link recovery changes, thereby avoiding loss of uplink transmission data and improving the transmission of uplink data. reliability.
- Fig. 1a is one of the structural schematic diagrams of the existing IAB system
- Figure 1b is the second schematic diagram of the existing IAB system structure
- Fig. 1c is the third schematic diagram of the existing IAB system structure
- Fig. 1d is the fourth schematic diagram of the existing IAB system structure
- Figure 1e is a schematic diagram of the structure of the existing BAP control PDU
- FIG. 2 is a schematic flowchart of a data scheduling method provided by an embodiment of the present application
- FIG. 3 a is one of the schematic structural diagrams of the BAP control PDU provided by the embodiment of the application.
- FIG. 3b is the second schematic structural diagram of the BAP control PDU provided by the embodiment of the application.
- Fig. 3c is the third schematic structural diagram of the BAP control PDU provided by the embodiment of the present application.
- FIG. 3d is the fourth schematic structural diagram of the BAP control PDU provided by the embodiment of the application.
- FIG. 4 is a schematic structural diagram of a data scheduling apparatus provided by an embodiment of the present application.
- FIG. 5 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
- FIG. 6 is a schematic structural diagram of a first IAB node according to an embodiment of the present application.
- first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
- the first object may be one or multiple.
- “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
- LTE Long Term Evolution
- LTE-Advanced LTE-Advanced
- LTE-A Long Term Evolution-Advanced
- CDMA Code Division Multiple Access
- TDMA Time Division Multiple Access
- FDMA Frequency Division Multiple Access
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single-carrier Frequency-Division Multiple Access
- system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
- NR New Radio
- the following description describes a New Radio (NR) system for example purposes, and uses NR terminology in most of the description below, but the techniques can also be applied to applications other than NR system applications, such as 6th generation (6th generation ) Generation, 6G) communication system.
- 6th generation 6th generation
- 6G 6th generation
- An IAB node includes a distributed processing unit (Distributed Unit, DU) functional part and a mobile terminal (Mobile Termination, MT) functional part.
- DU distributed Processing Unit
- MT Mobile Termination
- an access point ie IAB node
- the IAB node After an IAB node establishes a complete backhaul link, the IAB node turns on its DU function, and the DU provides cell services, that is, the DU can provide access services for the UE.
- a self-return loop includes an IAB-donor (host) node, and the IAB-donor node has a directly connected cable transport network (Cable transport).
- FIG. 1b the figure shows a CU-DU structure diagram of an IAB system.
- the DUs of all IAB nodes are connected to a CU node, and the DU is configured by this node through the F1 application protocol (F1 application protocol, F1-AP) protocol.
- the CU configures the MT through a radio resource control (Radio Resource Control, RRC) protocol.
- RRC Radio Resource Control
- the introduction of the IAB system is to solve the situation that the wired transmission network is not deployed in place when the access points are densely deployed. That is, when there is no wired transmission network, the access point can rely on wireless backhaul.
- the wireless link between IAB nodes is called Backhaul (BH) link, and a Backhaul (BH) RLC channel (channel) is configured on the BH link for wireless backhaul.
- BH Backhaul
- BH Backhaul
- RLC channel channel
- an IAB network including IAB-donor-CU1, IAB-donor-CU2, IAB-donor-DU11, IAB-donor-DU12, IAB-donor-DU2, IAB1-IAB6, and UE;
- IAB-donor-DU11 and IAB-donor-DU12 are under IAB-donor-CU1
- IAB-donor-DU2 is under IAB-donor-CU2
- IAB1 is under IAB-donor-DU2
- IAB2 is under IAB-donor-DU11
- IAB3 and IAB4 are under IAB-donor-DU12
- IAB5 is the downstream IAB node of IAB4
- IAB6 is the downstream IAB node of IAB5
- UE is the downstream node of IAB6.
- IAB5 may be restored to any one of IAB1 to IAB4, specifically:
- Case 1 The IAB node and the node performing wireless link recovery belong to the same IAB-donor-DU under the same IAB-donor-CU, namely intra-IAB-donor-CU intra-IAB-donor-DU;
- IAB5 is restored to IAB3, and both IAB3 and IAB4 are under IAB-donor-DU12 under IAB-donor-CU1, so they belong to intra-IAB-donor-CU, intra-IAB-donor-DU;
- Case 2 The IAB node and the node performing radio link recovery belong to different IAB-donor-DUs under the same IAB-donor-CU, namely intra-IAB-donor-CU, inter-IAB-donor-DU;
- IAB5 is restored to IAB2
- IAB2 and IAB4 are under IAB-donor-CU1
- IAB2 is under IAB-donor-DU11
- IAB4 is under IAB-donor-DU12, so it belongs to intra-IAB-donor-CU , inter-IAB-donor-DU;
- IAB5 is restored to IAB1, IAB1 is under IAB-donor-CU2, and IAB1 is under IAB-donor-CU1, so it belongs to inter-IAB-donor-CU;
- IAB5 After the backhaul link between IAB4 and IAB5 detects RLF, IAB5 will send the type-2 RLF indication to IAB6. If there are child nodes under IAB6, then IAB6 will continue to forward type-2 when there is only a single link. RLF indication to its child nodes, if IAB6 has two links, and the other link has also received type-2/4 RLF indication, it will continue to forward type-2 RLF indication to its child nodes.
- the backhaul adaptation protocol control protocol data unit (Backhaul Adaptation Protocol Control Protocol Data Unit, BAP control PDU) is used to carry the control information of the BAP layer.
- BAP control PDU Backhaul Adaptation Protocol Control Protocol Data Unit
- BH RLF indication also known as type-4 RLF indication: An IAB node can use the BAP control PDU to notify its child IAB node that the radio link between the IAB node and its parent node fails to recover ;
- IAB2 will send BH RLF indication to its child node IAB1 to inform IAB1 that there is a problem with the link between IAB2 and IAB3 .
- BAP control PDU type for downlink flow control report by BH RLC channel which is reported by the child IAB node to the parent IAB node;
- the parent IAB node asks the child IAB node for the BAP control PDU type of the downlink flow control report, which is sent by the parent IAB node to the child IAB node;
- the PDU Type (PDU Type) field is used to indicate the type of BAP control PDU.
- the existing BAP control PDU type indication is shown in Table 1:
- Bit (Bit) Description 0000 Flow control feedback per BH RLC channel 0001 Flow control feedback per BAP routing ID 0010 Flow control feedback polling 0011 BH RLF indication 0100-1111 Reserved
- type-2 BH RLF indication The radio link between an IAB node and its parent IAB node fails, and the child IAB node is notified of RLF discovery;
- Type-2 RLF indication may be used to trigger deactivation or reduction of SR and/or BSR transmissions (type-2 RLF indication may be used to trigger deactivation or reduction of SR and/or BSR transmissions).
- the downstream IAB node of the IAB node receives the type-3 RLF indication, it starts to resume the uplink scheduling of UE data, Since the anchor point of PDCP is changed from the source CU to the target CU (the key used to encrypt the data has changed), the data that finally reaches the target CU cannot be successfully decoded by the target CU, and the data sent by the UE will eventually be decoded by the target CU. lost.
- an embodiment of the present application provides a data scheduling method, including:
- Step 201 the first IAB node receives the BAP control PDU
- Step 202 the first IAB node performs a corresponding data scheduling operation on the downstream node of the first IAB node according to the BAP control PDU;
- the first IAB node is the downstream node of the second IAB node
- the BAP control PDU is used to indicate whether the topology network accessed by the third IAB node and the fourth IAB node has changed
- the third IAB node is the first IAB node.
- the fourth IAB node is the upstream IAB node before the second IAB node performs wireless link recovery
- the downstream node of the first IAB node is an IAB node or a terminal.
- the first IAB node in this embodiment of the present application is equivalent to IAB6 in FIG. 1c
- the second IAB node is equivalent to IAB5 in FIG. 1c
- the third IAB node is In any one of IAB1-IAB4 in Figure 1c (that is, the second IAB node can recover to any one of IAB1-IAB4 after the wireless link recovery)
- the fourth IAB node is equivalent to IAB4 in Figure 1c (that is, the second IAB
- the node is the downstream IAB node of IAB4 before radio link recovery).
- the BAP control PDU in the embodiment of the present application is used to indicate the change of the topology structure relationship between the IAB node that issues the message and the IAB node that performs wireless link recovery, and the topology structure refers to a network deployment, Whether the topology network to which the third IAB node and the fourth IAB node are connected changes refers to the change in network deployment after the wireless link recovery is performed.
- a new type-3 RLF indication signaling is designed, so that the first IAB node can know the wireless Changes in the topology network after the link is restored, and perform corresponding data scheduling operations, thereby avoiding loss of uplink transmission data and improving the transmission reliability of uplink data.
- Embodiment 1 is a diagrammatic representation of Embodiment 1:
- the BAP control PDU includes a first indication field.
- a reserved bit in the header of the existing BAP Control PDU is used to define it as a topology indication ( Figure 3a).
- the middle is TI, topology indicator), through which the TI is used to indicate the change of the topology network, as follows:
- the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are the same IAB node, indicating that the wireless link is successfully recovered and the topology is not Change;
- the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are different IAB nodes, indicating that the wireless link is successfully restored, but the topology structure has changed;
- the first IAB node performs a corresponding data scheduling operation on the downstream node of the first IAB node according to the BAP control PDU, including:
- the first IAB node resumes the uplink scheduling of the downstream nodes of the first IAB node;
- the first IAB node stops the uplink scheduling of the downstream nodes of the first IAB node.
- Embodiment 2 is a diagrammatic representation of Embodiment 1:
- N new type-3 RLF indications in the PDU type field of the BAP control PDU to indicate different backhaul link recovery situations, for example, define N new type-3 types from 0100-1111 reserved in the PDU type field.
- 3 RLF indication as follows:
- the BAP control PDU When the PDU type field of the BAP control PDU is the first value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is in the same IAB-donor-DU; when the BAP control PDU When the PDU type field is the second value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is under a different IAB-donor-DU under the same IAB-donor-CU; when the BAP When the PDU type field of the control PDU is the third value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs;
- the BAP control PDU When the PDU type field of the BAP control PDU is the first value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU; when the BAP control PDU When the PDU type field of the PDU is the second value, the BAP control PDU is used to indicate that the topology networks accessed by the third IAB node and the fourth IAB node are under different IAB-donor-DUs;
- two new PDU types are selected from the reserved 0100-1111.
- 0100 and 0101 are used to indicate the two cases of restoring to the original donor-DU and restoring to the new donor-DU.
- the BAP control PDU When the PDU type field of the BAP control PDU is the first value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU; when the BAP control PDU When the PDU type field of the PDU is the second value, the BAP control PDU is used to indicate that the topology networks accessed by the third IAB node and the fourth IAB node are under different IAB-donor-CUs;
- two new PDU types are selected from the reserved 0100-1111.
- 0100 and 0101 are used to indicate the two situations of restoring the donor DU under the control of the original CU and restoring the donor-DU under the control of the new CU. .
- the BAP control PDU When the PDU type field of the BAP control PDU is the first value, the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are the same IAB node; when the PDU type field of the BAP control PDU is the second value , the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are different IAB nodes.
- two new PDU types are selected, such as 0100 and 0101, which are respectively used to indicate that the wireless link is successfully recovered and the topology has not changed, and that the wireless link has been successfully recovered but the topology has changed.
- the BAP control PDU contains a second indication field, optionally, as shown in Figure 3b, a new PDU type is selected from 0100-1111 reserved in the PDU type field of the BAP control PDU, For example, 0100 indicates that the BAP control PDU is Type3 RLF indication, and a topology adaptation indicator is added to the header of the existing BAP Control PDU, that is, the second indication field, which indicates the wireless link through the second indication field. Whether the topology structure relationship has changed and/or the information has changed after the recovery is successful, as follows:
- the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU;
- the second indication field in the BAP control PDU is used to indicate any of the following:
- the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU;
- the second indication field in the BAP control PDU is used to indicate any of the following:
- the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU;
- the second indication field in the BAP control PDU is used to indicate any of the following:
- the third IAB node and the fourth IAB node are the same IAB node
- the difference between the second embodiment and the third embodiment is that when the second embodiment is adopted, the first IAB node needs to detect the PDU type field in the BAP control PDU first, and then detect the value of the PDU type field, Thereby, the topology network situation of the access of the third IAB node and the fourth IAB node is known, that is, two steps are included; when the third embodiment is adopted, when the first IAB node detects the Topology adaptation indicator in the BAP control PDU, it can be known. Topological network conditions that the third IAB node and the fourth IAB node access. That is, in the third embodiment, only one new PDU type is used in the PDU type field without any enhancement.
- the BAP control PDU includes a third indication field, and the third indication field is used to indicate to the first IAB node which backhaul link has successfully performed radio link recovery.
- the first An IAB node can have one or more upstream IAB nodes. Taking the scenario shown in Figure 1d as an example, it is assumed that IAB5 has established connections with IAB3 and IAB4 nodes respectively (that is, IAB5 is in a dual-connection scenario, and its parent nodes are IAB3 and IAB4) , a radio link failure occurs in the backhaul link between IAB3 and IAB4 and IAB5. After a period of time, the backhaul link between IAB3 and IAB5 recovers successfully.
- IAB5 needs to send the BAP control PDU to the downstream node. If the BAP The control PDU does not carry the identification information to indicate which link is successfully restored (BH link between IAB3 and IAB5, or BH link between IAB4 and IAB5), then downstream nodes such as IAB6 cannot receive the BAP control PDU. Knowing which backhaul link is successfully recovered, it is necessary to set a third indication field in the BAP control PDU to indicate which backhaul link is recovered successfully.
- the BAP control PDU is used to indicate to the first IAB node that the backhaul link corresponding to the target value is successfully restored; that is, the first IAB node can know that the Which backhaul link was successfully restored.
- the third indication field includes any of the following:
- BAP routing ID (BAP routing ID);
- BH Link ID Backhaul link identification
- IAB-donor-CU Backhaul link identification
- Path ID which indicates the transmission path of a data packet.
- reuse 1 reserved bit in the header of the existing BAP Control PDU and indicate which return link is successfully restored according to the value of the reserved bit.
- the reserved bit is the first When the value is set, it indicates that the first backhaul link between the first IAB section and the upstream IAB node is successfully restored, and when the second value is taken, it means that the second backhaul link between the first IAB section and the upstream IAB node is successfully restored.
- the first IAB node performs a corresponding data scheduling operation on the downstream nodes of the first IAB node according to the BAP control PDU, including at least one of the following:
- the first IAB node restores the Uplink scheduling of the downstream node of the first IAB node, or after the IAB-donor-CU performs BAP routing configuration reconfiguration or BAP routing mapping configuration reconfiguration, the uplink scheduling of the downstream node of the first IAB node is resumed, or whether to resume the uplink scheduling depends on the implementation;
- BAP routing configuration reconfiguration is for the data transmitted by the intermediate node: after an IAB node receives the data transmitted by the previous IAB node, it will be parsed at the BAP layer. If the destination ID (destination ID) obtained after parsing is the current node, Then it will stop passing down; but if it is not this node, you need to find the next hop IAB node corresponding to the BAP routing ID carried in the BAP header of this data packet in the BAP routing configuration according to the BAP routing configuration, so as to perform data routing. transmission.
- the BAP routing mapping configuration is for the data from the upper layer: if a data packet is generated from a higher layer of an IAB node (a protocol layer higher than the BAP layer), then when the data is generated at the BAP layer, the BAP routing ID needs to be filled in the BAP header, using To explain where this node is to be transmitted and which path to transmit through, what is used at this time is the BAP routing mapping configuration, that is, according to the packet header of the IP layer, find the corresponding BAP routing that needs to be filled in the BAP header from the BAP routing mapping configuration. ID.
- the BAP control PDU is used to indicate that the topological networks accessed by the third IAB node and the fourth IAB node are under different IAB-donor-CUs, that is, when the topological relationship is indicated as inter-IAB-donor-CU, in the IAB -
- the first IAB node stops the uplink scheduling of the downstream nodes of the first IAB node;
- the first IAB node restores the downstream of the first IAB node
- the upstream scheduling of the node or after the IAB-donor-CU reconfigures the BAP routing configuration or the BAP routing mapping configuration, restores the upstream scheduling for the downstream node of the first IAB node, or whether to restore the upstream scheduling depends on the implementation.
- the method further includes:
- the first IAB node stops the uplink scheduling of the downstream nodes of the first IAB node
- the preset conditions include at least one of the following:
- the first IAB node receives a scheduling message from the second IAB node, that is, if a node is scheduled by an upstream node, the node can start to schedule uplink transmission data of its downstream node.
- IAB-donor-CU completes RRC reconfiguration for all terminals served by the first IAB node
- the downstream node receives the new BAP routing configuration or BAP routing mapping configuration from the IAB-donor-CU;
- the downstream node receives from the IAB-donor-CU, the IAB-donor-DU or the second IAB node the indication information for resuming uplink data transmission.
- the execution body may be a data scheduling apparatus, or a control module in the data scheduling apparatus for executing the data scheduling method.
- the data scheduling device provided by the embodiment of the present application is described by taking the data scheduling method performed by the data scheduling device as an example.
- a data scheduling apparatus 400 includes:
- the receiving module 401 is used for the first IAB node to receive the BAP control PDU, the first IAB node is the downstream node of the second IAB node, and the BAP control PDU is used to indicate the access point between the third IAB node and the fourth IAB node. Whether the topology network has changed, the third IAB node is the upstream IAB node after the second IAB node performs radio link recovery, and the fourth IAB node is the second IAB node before the wireless link recovery is performed. Upstream IAB node;
- the first scheduling module 402 is used for the first IAB node to perform a corresponding data scheduling operation on the downstream node of the first IAB node according to the BAP control PDU, and the downstream node of the first IAB node is the IAB node or terminal.
- the BAP control PDU includes a first indication field
- the BAP control PDU When the first indication field is the first value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is in the same IAB host centralized processing unit IAB-donor - under CU; when the first indication field is the second value, the BAP control PDU is used to indicate that the topology networks accessed by the third IAB node and the fourth IAB node are in different IAB-donors -under CU;
- the BAP control PDU When the first indication field is the first value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is in the same host distribution processing unit IAB-donor- DU; when the first indication field is the second value, the BAP control PDU is used to indicate that the topology networks accessed by the third IAB node and the fourth IAB node are in different IAB-donor-DUs Down;
- the BAP control PDU When the first indication field is the first value, the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are the same IAB node; when the first indication field is the second IAB node value, the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are different IAB nodes;
- the first scheduling module is further used for:
- the first IAB node restores the uplink scheduling to the downstream nodes of the first IAB node;
- the first IAB node stops the uplink scheduling of the downstream nodes of the first IAB node.
- the BAP control PDU when the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is in The same IAB-donor-DU; when the PDU type field of the BAP control PDU is the second value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is Under different IAB-donor-DUs under the same IAB-donor-CU; when the PDU type field of the BAP control PDU is a third value, the BAP control PDU is used to indicate that the third IAB node is related to the The topology network accessed by the fourth IAB node is under different IAB-donor-CUs;
- the BAP control PDU When the PDU type field of the BAP control PDU is the first value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node are in the same IAB-donor-DU When the PDU type field of the BAP control PDU is the second value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is in a different IAB-donor - under DU;
- the BAP control PDU When the PDU type field of the BAP control PDU is the first value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node are in the same IAB-donor-CU When the PDU type field of the BAP control PDU is the second value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is in a different IAB-donor -under CU;
- the BAP control PDU When the PDU type field of the BAP control PDU is the first value, the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are the same IAB node; When the PDU type field is the second value, the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are different IAB nodes.
- the BAP control PDU includes a second indication field
- the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU;
- the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs under the same IAB-donor-CU;
- the topology networks accessed by the third IAB node and the fourth IAB node are under different IAB-donor-CUs;
- the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU;
- the topology networks accessed by the third IAB node and the fourth IAB node are under different IAB-donor-DUs;
- the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU;
- the topology networks accessed by the third IAB node and the fourth IAB node are under different IAB-donor-CUs;
- the third IAB node and the fourth IAB node are the same IAB node
- the third IAB node and the fourth IAB node are different IAB nodes.
- the first scheduling module is further used for at least one of the following:
- the first IAB node resumes the first IAB node Uplink scheduling of the downstream node of the IAB node, or after the IAB-donor-CU performs BAP routing configuration reconfiguration or BAP routing mapping configuration reconfiguration, restore the uplink scheduling of the downstream node of the first IAB node;
- the IAB-donor-CU controls the first IAB Before all terminals served by the node complete the RRC reconfiguration, the first IAB node stops the uplink scheduling of the downstream nodes of the first IAB node;
- the first IAB node resumes the uplink scheduling of the downstream nodes of the first IAB node, or resumes the reconfiguration of the BAP route configuration or the BAP route mapping configuration after the IAB-donor-CU reconfigures the BAP route mapping configuration. Describe the uplink scheduling of the downstream node of the first IAB node.
- the apparatus further comprises:
- the second scheduling module configured for the first IAB node to stop the uplink scheduling of the downstream nodes of the first IAB node
- the third scheduling module configured to restore, by the first IAB node, the uplink scheduling to the downstream nodes of the first IAB node when a preset condition is met;
- the preset condition includes at least one of the following:
- the first IAB node receives a scheduling message from the second IAB node
- the IAB-donor-CU completes RRC reconfiguration for all terminals served by the first IAB node
- the downstream node receives a new BAP routing configuration or a BAP routing mapping configuration from the IAB-donor-CU;
- the downstream node receives, from the IAB-donor-CU, the IAB-donor-DU or the second IAB node, instruction information for resuming uplink data transmission.
- the BAP control PDU includes a third indication field
- the BAP control PDU is used to indicate to the first IAB node that the backhaul link corresponding to the target value is successfully restored;
- the third indication field includes any of the following:
- the first IAB node performs a corresponding data scheduling operation on the downstream node according to whether the topology network accessed by the node performing wireless link recovery changes, thereby avoiding loss of uplink transmission data and improving the transmission of uplink data. reliability.
- the data scheduling apparatus in this embodiment of the present application may be an apparatus, an apparatus having an operating system or an electronic device, or may be a component, an integrated circuit, or a chip in a terminal.
- the apparatus or electronic device may be a mobile terminal or a non-mobile terminal.
- the mobile terminal may include but is not limited to the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (Personal Computer, PC), a television ( Television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
- the data scheduling apparatus provided in this embodiment of the present application can implement each process implemented by the method embodiment in FIG. 2 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
- an embodiment of the present application further provides a communication device 500, including a processor 501, a memory 502, a program or instruction stored in the memory 502 and executable on the processor 501,
- a communication device 500 including a processor 501, a memory 502, a program or instruction stored in the memory 502 and executable on the processor 501
- the communication device 500 is a terminal
- the program or instruction is executed by the processor 501
- each process of the foregoing data scheduling method embodiment is implemented, and the same technical effect can be achieved.
- the communication device 500 is a network-side device
- the program or instruction is executed by the processor 501
- each process of the above data scheduling method embodiment can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not described here.
- An embodiment of the present application further provides a first IAB node, including a processor and a communication interface, wherein the communication interface is used for the first IAB node to receive a BAP control PDU, and the first IAB node is downstream of the second IAB node node, the BAP control PDU is used to indicate whether the topology network accessed by the third IAB node and the fourth IAB node has changed, and the third IAB node is the upstream IAB after the second IAB node performs wireless link recovery node, the fourth IAB node is the upstream IAB node before the second IAB node performs radio link recovery; the processor is used by the first IAB node to perform the operation of the first IAB node according to the BAP control PDU A downstream node of the node performs a corresponding data scheduling operation, and the downstream node of the first IAB node is an IAB node or a terminal.
- This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment,
- the embodiment of the present application further provides a first IAB node.
- the first IAB node 600 includes: an antenna 61 , a radio frequency device 62 , and a baseband device 63 .
- the antenna 61 is connected to the radio frequency device 62 .
- the radio frequency device 62 receives information through the antenna 61, and sends the received information to the baseband device 63 for processing.
- the baseband device 63 processes the information to be sent and sends it to the radio frequency device 62
- the radio frequency device 62 processes the received information and sends it out through the antenna 61 .
- the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 63, and the method performed by the first IAB node in the above embodiment may be implemented in the baseband apparatus 63, where the baseband apparatus 63 includes a processor 64 and a memory y5.
- the baseband device 63 may include, for example, at least one baseband board on which a plurality of chips are arranged. As shown in FIG. 6 , one of the chips is, for example, the processor 64 and is connected to the memory 65 to call the program in the memory 65 to execute The network devices shown in the above method embodiments operate.
- the baseband device 63 may further include a network interface 66 for exchanging information with the radio frequency device 62, and the interface is, for example, a Common Public Radio Interface (CPRI for short).
- CPRI Common Public Radio Interface
- the network-side device in the embodiment of the present invention further includes: instructions or programs stored in the memory 65 and executable on the processor 64, and the processor 64 invokes the instructions or programs in the memory 65 to execute the modules shown in FIG. 6 .
- the embodiments of the present application further provide a computer program product, where the computer program product is stored in a non-volatile storage medium, and the computer program product is executed by at least one processor to implement each process of the above data scheduling method embodiments , and can achieve the same technical effect, in order to avoid repetition, it is not repeated here.
- the embodiments of the present application further provide a readable storage medium, the readable storage medium may be non-transitory, and a program or an instruction is stored on the readable storage medium, and the program or instruction realizes the above data when executed by a processor
- the various processes of the scheduling method embodiments can achieve the same technical effect, and are not repeated here in order to avoid repetition.
- the processor is the processor in the terminal described in the foregoing embodiment.
- the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
- An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the above data scheduling method embodiments.
- the chip includes a processor and a communication interface
- the communication interface is coupled to the processor
- the processor is configured to run a program or an instruction to implement the above data scheduling method embodiments.
- the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请公开了一种数据调度方法、装置及设备,属于通信技术领域,方法包括:第一IAB节点接收BAP control PDU,第一IAB节点为第二IAB节点的下游节点,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,第三IAB节点为第二IAB节点进行无线链路恢复之后的上游IAB节点,第四IAB节点为第二IAB节点进行无线链路恢复之前的上游IAB节点;第一IAB节点根据BAP control PDU,对第一IAB节点的下游节点执行对应的数据调度操作,第一IAB节点的下游节点为IAB节点或者终端。
Description
相关申请的交叉引用
本申请主张在2021年3月31日在中国提交的中国专利申请No.202110351906.8的优先权,其全部内容通过引用包含于此。
本申请属于通信技术领域,具体涉及一种数据调度方法、装置及设备。
目前无线接入与回传一体化(integrated access and backhaul,IAB)节点支持类型2/3无线链路失败指示(type-2/3 Radio Link Failure indication,type-2/3 RLF indication),其中类型2回传无线链路失败指示(type-2 backhaul Radio Link Failure indication,type-2 BH RLF indication)表示一个IAB节点与其父IAB节点之间发生无线链路失败,向子IAB节点通知“检测到无线链路失败RLF”;type-3 BH RLF indication表示一个IAB节点与其父IAB节点的无线链路失败后无线链路恢复成功,向子IAB节点通知RLF恢复成功。
对于IAB节点与进行无线链路恢复的节点属于不同IAB宿主集中处理单元(IAB-donor-Centralized Unit,IAB-donor-CU)的场景,如果该IAB节点的下游IAB节点接收到type-3 RLF indication就开始恢复对UE数据的上行调度,由于分组数据汇聚协议(Packet Data Convergence Protocol,PDCP)的锚点(anchor点)从源CU转为目标CU(用于加密数据的秘钥等发生了改变),则会导致最终到达目标CU的数据无法被目标CU成功解码,UE发送的数据最终将会被丢失。
发明内容
本申请实施例提供一种数据调度方法、装置及设备,能够解决IAB节点与进行无线链路恢复后上行传输数据不必要的丢失问题。
第一方面,提供了一种数据调度方法,该方法包括:
第一IAB节点接收BAP control PDU,所述第一IAB节点为第二IAB节点的下游节点,所述BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,所述第三IAB节点为所述第二IAB节点进行无线链路恢复之后的上游IAB节点,所述第四IAB节点为所述第二IAB节点进行无线链路恢复之前的上游IAB节点;
所述第一IAB节点根据所述BAP control PDU,对所述第一IAB节点的下游节点执行对应的数据调度操作,所述第一IAB节点的下游节点为IAB节点或者终端。
第二方面,提供了一种数据调度装置,包括:
接收模块,用于第一IAB节点接收BAP control PDU,所述第一IAB节点为第二IAB节点的下游节点,所述BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,所述第三IAB节点为所述第二IAB节点进行无线链路恢复之后的上游IAB节点,所述第四IAB节点为所述第二IAB节点进行无线链路恢复之前的上游IAB节点;
第一调度模块,用于所述第一IAB节点根据所述BAP control PDU,对所述第一IAB节点的下游节点执行对应的数据调度操作,所述第一IAB节点的下游节点为IAB节点或者终端。
第三方面,提供了一种终端,该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第四方面,提供了一种终端,包括处理器及通信接口,其中,所述通信接口用于第一IAB节点接收BAP control PDU,所述第一IAB节点为第二IAB节点的下游节点,所述BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,所述第三IAB节点为所述第二IAB节点进行无线链路恢复之后的上游IAB节点,所述第四IAB节点为所述第二IAB节点进行无线链路恢复之前的上游IAB节点;所述处理器用于所述第一IAB节点根据所述BAP control PDU,对所述第一IAB节点的下游节点执行对应的数据调度操作,所述第一IAB节点的下游节点为IAB节点或者终端。
第五方面,提供了一种可读存储介质,所述可读存储介质上存储程序或 指令,所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤。
第六方面,提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如第一方面所述的方法的步骤。
第七方面,提供了一种计算机程序产品,所述计算机程序产品被存储在非易失的存储介质中,所述程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤。
在本申请实施例中,第一IAB节点根据进行无线链路恢复的节点接入的拓扑网络是否发生变化,对下游节点进行的相应数据调度操作,从而避免丢失上行传输数据,提高上行数据的传输可靠性。
图1a为现有IAB***结构示意图之一;
图1b为现有IAB***结构示意图之二;
图1c为现有IAB***结构示意图之三;
图1d为现有IAB***结构示意图之四;
图1e为现有BAP control PDU的结构示意;
图2为本申请实施例提供的数据调度方法的流程示意图;
图3a为本申请实施例提供的BAP control PDU的结构示意图之一;
图3b为本申请实施例提供的BAP control PDU的结构示意图之二;
图3c为本申请实施例提供的BAP control PDU的结构示意图之三;
图3d为本申请实施例提供的BAP control PDU的结构示意图之四;
图4为本申请实施例提供的数据调度装置的结构示意图;
图5为本申请实施例提供的通信设备的结构示意图;
图6为本申请实施例提供的第一IAB节点的结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实 施例。基于本申请中的实施例,本领域普通技术人员所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施,且“第一”、“第二”所区别的对象通常为一类,并不限定对象的个数,例如第一对象可以是一个,也可以是多个。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是,本申请实施例所描述的技术不限于长期演进型(Long Term Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)***,还可用于其他无线通信***,诸如码分多址(Code Division Multiple Access,CDMA)、时分多址(Time Division Multiple Access,TDMA)、频分多址(Frequency Division Multiple Access,FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access,OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access,SC-FDMA)和其他***。本申请实施例中的术语“***”和“网络”常被可互换地使用,所描述的技术既可用于以上提及的***和无线电技术,也可用于其他***和无线电技术。以下描述出于示例目的描述了新空口(New Radio,NR)***,并且在以下大部分描述中使用NR术语,但是这些技术也可应用于NR***应用以外的应用,如第6代(6
th Generation,6G)通信***。
为更好理解本申请实施例的方案,首先对以下内容进行介绍:
IAB网络
参见图1a,图中显示了一个IAB***示意图。一个IAB节点包括分布式处理单元(Distributed Unit,DU)功能部分和移动终端(Mobile Termination,MT)功能部分。依靠MT,一个接入点(即IAB node)可以找到一个上游接入点(parent IAB node),并跟上游接入点的DU建立无线连接,该无线连接被称为回程链路(backhaul link)。在一个IAB节点建立完整的回传链路后,该IAB节点打开其DU功能,DU会提供小区服务,即DU可以为UE提供接 入服务。一个自回传回路包含一个IAB-donor(宿主)节点,IAB-donor节点有直接相连的有线传输网(Cable transport)。
参见图1b,图中示出一个IAB***的CU-DU结构图。在一个自回传回路中,所有的IAB节点的DU都连接到一个CU节点,由这一个节点通过F1应用协议(F1application protocol,F1-AP)协议进行对DU进行配置。CU通过无线资源控制(Radio Resource Control,RRC)协议,对MT进行配置。IAB-donor节点没有MT功能部分。
IAB***的引入是为了解决接入点密集部署时,有线传输网部署不到位的情况。即在没有有线传输网络时,接入点可以依赖无线回传。
IAB节点之间的无线链路称为Backhaul(BH)link,BH link上配置有Backhaul(BH)RLC信道(channel)进行无线回传。
下面结合附图对IAB网络中IAB节点进行无线链路恢复时可能出现的情况进行描述:
参见图1c,图中示出一种IAB网络,包括IAB-donor-CU1、IAB-donor-CU2、IAB-donor-DU11、IAB-donor-DU12、IAB-donor-DU2、IAB1~IAB6、UE;其中IAB-donor-DU11和IAB-donor-DU12处于IAB-donor-CU1下,IAB-donor-DU2处于IAB-donor-CU2下,IAB1处于IAB-donor-DU2下,IAB2处于IAB-donor-DU11下,IAB3和IAB4处于IAB-donor-DU12下,IAB5为IAB4的下游IAB节点,IAB6为IAB5的下游IAB节点,UE为IAB6的下游节点。
如果IAB4和IAB5之间链路有问题,即无线链路失败,则进行无线链路恢复,此时IAB5有可能恢复到IAB1~IAB4中任意一个,具体地:
情况一:IAB节点与进行无线链路恢复的节点属于同一IAB-donor-CU下的同一IAB-donor-DU,即intra-IAB-donor-CU intra-IAB-donor-DU;
在情况一中,IAB5恢复到了IAB3下,IAB3与IAB4均处于IAB-donor-CU1下的IAB-donor-DU12下,因此属于intra-IAB-donor-CU,intra-IAB-donor-DU;
情况二:IAB节点与进行无线链路恢复的节点属于同一IAB-donor-CU下的不同IAB-donor-DU,即intra-IAB-donor-CU,inter-IAB-donor-DU;
在情况二中,IAB5恢复到了IAB2下,IAB2与IAB4处于IAB-donor-CU1下,但IAB2处于IAB-donor-DU11下,IAB4处于IAB-donor-DU12下,因此属于intra-IAB-donor-CU,inter-IAB-donor-DU;
情况三:该IAB节点与进行无线链路恢复的节点属于不同IAB-donor-CU,即inter-IAB-donor-CU;
在情况三中,IAB5恢复到了IAB1下,IAB1处于IAB-donor-CU2下,IAB1处于IAB-donor-CU1下,因此属于inter-IAB-donor-CU;
在IAB4与IAB5间的回传链路检测到RLF后,IAB5会向IAB6发送type-2 RLF indication,如果IAB6下面还有子节点,那么IAB6在只有单条链路的情况下会继续转发type-2 RLF indication给其子节点,如果IAB6有两条链路,且另一条链路上也收到过type-2/4 RLF indication,则也会继续转发type-2 RLF indication给其子节点。
BAP Control PDU
回传自适应协议控制协议数据单元(Backhaul Adaptation Protocol Control Protocol Data Unit,BAP control PDU)用来承载BAP层的控制信息。目前已经定义4个BAP control PDU类型:
(1)BH RLF indication(也可称为type-4 RLF indication):一个IAB节点可以用该BAP control PDU可以用来通知其子IAB节点该IAB节点与其父节点之间无线链路恢复失败的消息;
如假设IAB网络拓扑结构为:
IAB1->IAB2->IAB3->IAB-donor-DU->IAB-donor-CU;
假设IAB2与父节点IAB3之间的链路发生了RLF,且进行RLF recovery失败了,则IAB2会向其子节点IAB1发送BH RLF indication,用于告知IAB1节点IAB2与IAB3之间的链路出现问题。
(2)每个BH RLC通道的流量控制反馈(Flow control feedback per BH RLC channel):按BH RLC channel进行下行流量控制报告的BAP control PDU类型,由子IAB节点向父IAB节点汇报;
(3)每个BAP路由标识(Identity Document,ID)的流量控制反馈(Flow control feedback per BAP routing ID):按BAP routing ID进行下行流量控制报 告的BAP control PDU类型,由子IAB节点向父IAB节点汇报;
(4)流量控制反馈轮询(Flow control feedback polling):父IAB节点向子IAB节点询问下行流量控制报告的BAP control PDU类型,由父IAB节点向子IAB节点发送;
参见图1d,图中示出BAP control PDU的头部(header)结构:
其中PDU类型(PDU Type)域用来指示BAP control PDU的类型,现有BAP control PDU类型指示如表1所示:
比特(Bit) | 描述(Description) |
0000 | Flow control feedback per BH RLC channel |
0001 | Flow control feedback per BAP routing ID |
0010 | Flow control feedback polling |
0011 | BH RLF indication |
0100-1111 | Reserved |
表1
使用BAP control PDU的情形:
(1)type-2 BH RLF indication:一个IAB节点与其父IAB节点的无线链路失败,向子IAB节点通知RLF发现;
(2)type-3 BH RLF indication:一个IAB节点与其父IAB节点的无线链路失败后无线链路恢复成功,向子IAB节点通知RLF恢复成功;
具体规定如下:
(1)RAN2支持2/3型RLF指示(行为TS影响待定,FFS详细信息待定)(RAN2 to support type-2/3 RLF indication(FFS specified behavior(s)TS impact,FFS details))。
(2)类型2RLF指示可用于触发SR和/或BSR传输的停用或减少(type-2 RLF indication may be used to trigger deactivation or reduction of SR and/or BSR transmissions)。
对于IAB节点与进行无线链路恢复的节点属于不同IAB-donor-CU(inter CU)的场景,如果该IAB节点的下游IAB节点接收到type-3 RLF indication就开始恢复对UE数据的上行调度,由于PDCP的anchor点从源CU转为目 标CU(用于加密数据的秘钥等发生了改变),则会导致最终到达目标CU的数据无法被目标CU成功解码,UE发送的数据最终将会被丢失。
下面结合附图,通过一些实施例及其应用场景对本申请实施例提供的数据调度方法进行详细地说明。
参见图2,本申请实施例提供一种一种数据调度方法,包括:
步骤201:第一IAB节点接收BAP control PDU;
步骤202:第一IAB节点根据BAP control PDU,对第一IAB节点的下游节点执行对应的数据调度操作;
在本申请实施例中,第一IAB节点为第二IAB节点的下游节点,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,第三IAB节点为第二IAB节点进行无线链路恢复之后的上游IAB节点,第四IAB节点为第二IAB节点进行无线链路恢复之前的上游IAB节点;第一IAB节点的下游节点为IAB节点或者终端。
具体地,以图1c所示场景为例进行解释说明,本申请实施例中的第一IAB节点相当于图1c中的IAB6,第二IAB节点当于图1c中的IAB5,第三IAB节点当于图1c中的IAB1~IAB4中任意一个(即第二IAB节点进行无线链路恢复之后可以恢复至IAB1~IAB4中任意一个),第四IAB节点当于图1c中的IAB4(即第二IAB节点进行无线链路恢复之前是IAB4的下游IAB节点)。
需要说明的是,本申请实施例中的BAP control PDU用于指示下发该消息的IAB节点与进行无线链路恢复的IAB节点之间的拓扑结构关系变化,拓扑结构指的是一个网络部署,上述第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,指的是在进行无线链路恢复以后,网络部署的变化情况。
本申请实施例中,通过设计一种能够指示接入的拓扑网络是否发生变化的BAP control PDU,具体地,是设计一种新的type-3RLF indication的信令,使得第一IAB节点能够获知无线链路恢复之后拓扑网络的变化情况,并执行对应的数据调度操作,从而避免丢失上行传输数据,提高上行数据的传输可靠性。
本申请实施例提供几种BAP control PDU的实施方式:
实施方式一:
在本申请实施方式中,BAP control PDU中包含第一指示域,可选地,如图3a所示,采用现有BAP Control PDU的header中的1个reserved bit,定义其为拓扑指示(图3a中为TI,topology indicator),通过该TI来指示拓扑网络的变化情况,具体如下:
(1)当第一指示域为第一值,例如TI=0时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下,表示拓扑关系为“同CU”;当第一指示域为第二值,例如TI=1时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于不同的IAB-donor-CU下,表示拓扑关系为“不同CU”;
(2)当第一指示域为第一值,例如TI=0时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下,表示拓扑关系为“同donor-DU”;当第一指示域为第二值,例如TI=1时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下,表示拓扑关系为无线链路恢复到新donor-DU,即“不同donor-DU”;
(3)当第一指示域为第一值,例如TI=0时,BAP control PDU用于指示第三IAB节点与第四IAB节点为相同的IAB节点,表示无线链路恢复成功,拓扑结构未发生变化;当第一指示域为第二值,例如TI=1时,BAP control PDU用于指示第三IAB节点与第四IAB节点为不同的IAB节点,表示无线链路恢复成功,但拓扑结构已发生变化;
可选地,第一IAB节点根据BAP control PDU,对第一IAB节点的下游节点执行对应的数据调度操作,包括:
(1)当第一指示域为第一值,例如TI=0时,第一IAB节点恢复对第一IAB节点的下游节点的上行调度;
(2)当第一指示域为第二值,例如TI=1时,所述第一IAB节点停止对第一IAB节点的下游节点的上行调度。
实施方式二:
在BAP control PDU的PDU type域中定义N个新的type-3 RLF indication,分别指示不同的回传链路恢复情形,例如从PDU type域预留的0100-1111中 定义N个新的type-3 RLF indication,具体如下:
(1)当BAP control PDU的PDU type域为第一值时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU;当BAP control PDU的PDU type域为第二值时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下的不同IAB-donor-DU下;当BAP control PDU的PDU type域为第三值时,BAP control PDU用于指示第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;
即,从预留的0100-1111中选择3个新的PDU type,如0100、0101和0110分别用来表示无线链路恢复到原donor-DU、无线链路恢复到原CU控制下的新donor-DU和无线链路恢复到新CU控制下的新donor-DU这3种情况。
(2)当BAP control PDU的PDU type域为第一值时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;当BAP control PDU的PDU type域为第二值时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;
即,从预留的0100-1111中选择2个新的PDU type,如0100、0101分别用来表示恢复到原donor-DU和恢复到新donor-DU这2种情况。
(3)当BAP control PDU的PDU type域为第一值时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下;当BAP control PDU的PDU type域为第二值时,BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;
即,从预留的0100-1111中选择2个新的PDU type,如0100、0101分别用来表示恢复到原CU控制下的donor DU和恢复到新CU控制下的donor-DU这2种情况。
(4)当BAP control PDU的PDU type域为第一值时,BAP control PDU用于指示第三IAB节点与第四IAB节点为相同的IAB节点;当BAP control PDU的PDU type域为第二值时,BAP control PDU用于指示第三IAB节点与 第四IAB节点为不同的IAB节点。
即,选择2个新的PDU type,如0100、0101分别用来表示无线链路恢复成功且拓扑结构未发生变化和表示无线链路恢复成功但拓扑结构已发生变化这2种情况。
实施方式三:
在本申请实施方式中,BAP control PDU中包含第二指示域,可选地,如图3b所示,从BAP control PDU的PDU type域预留的0100-1111中选择1个新的PDU type,如0100表示该BAP control PDU为Type3 RLF indication,在现有BAP Control PDU的header中新增一个拓扑自适应指示域(Topology adaptation indicator),即第二指示域,通过第二指示域指示无线链路恢复成功后拓扑结构关系是否发生变化和/或发生变化的信息,具体如下:
BAP control PDU中的第二指示域用于指示以下任意一项:
(1)第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;
(2)第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下的不同IAB-donor-DU下;
(3)第三IAB节点与第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;
或者,BAP control PDU中的第二指示域用于指示以下任意一项:
(1)第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;
(2)第三IAB节点与第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;
或者,BAP control PDU中的第二指示域用于指示以下任意一项:
(1)第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下;
(2)第三IAB节点与第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;
或者,BAP control PDU中的第二指示域用于指示以下任意一项:
(1)第三IAB节点与第四IAB节点为相同的IAB节点;
(2)第三IAB节点与第四IAB节点为不同的IAB节点。
需要说明的是,实施方式二与实施方式三之间的区别在于,采用实施方式二时,第一IAB节点需要先检测BAP control PDU中的PDU type域,然后再检测该PDU type域的值,从而获知第三IAB节点与第四IAB节点接入的拓扑网络情况,即包含两个步骤;采用实施方式三时,当第一IAB节点检测到BAP control PDU中的Topology adaptation indicator后,即可获知第三IAB节点与第四IAB节点接入的拓扑网络情况。即,实施方式三中只是在PDU type域采用1个新的PDU type,而不进行任何的增强。
实施方式四:
在本申请实施方式中,BAP control PDU中包含第三指示域,该第三指示域用于向第一IAB节点指示进行无线链路恢复成功的是哪条回传链路,具体地,第一IAB节点可以具有一个或多个上游IAB节点,以图1d所示场景为例,假设IAB5分别与IAB3和IAB4节点建立了连接(即IAB5处于双连接的场景中,其父节点为IAB3和IAB4),IAB3与IAB4及IAB5间的回传链路发生无线链路失败,一段时间后IAB3与IAB5间的回传链路恢复成功,此时IAB5需要对下游节点发送所述BAP control PDU,如果该BAP control PDU中未携带标识信息说明是哪条链路恢复成功(IAB3与IAB5间的BH link,或者IAB4与IAB5间的BH link),那么下游节点如IAB6在收到该BAP control PDU后也就无法知晓具体恢复成功的回传链路是哪一条,因此需要在BAP control PDU中设置一个第三指示域指示出具体是哪个回传链路恢复成功了。
具体地,当第三指示域为目标值时,BAP control PDU用于向第一IAB节点指示与目标值对应的回传链路恢复成功;即第一IAB节点根据第三指示域即可获知是哪个回传链路恢复成功了。
其中,第三指示域包括以下任意一项:
BAP control PDU中的预留域;
BAP路由标识(BAP routing ID);
回传链路标识(BH Link ID),该BH Link ID是由IAB-donor-CU为其拓扑网络下的每一条link进行统一管理编号的,并且通过F1AP或RRC信令下 发给每个IAB节点;
路径标识(Path ID),表示某数据包的传输路径。
如图3c和图3d所示,复用现有BAP Control PDU的header中的1个reserved bit,根据该reserved bit的取值指示是哪个回传链路恢复成功,例如:该reserved bit取第一值时表示第一IAB节与上游IAB节点的第一回传链路恢复成功,取第二值时表示第一IAB节与上游IAB节点的第二回传链路恢复成功。
需要说明的是,上述BAP routing ID(20bits)等于Path ID(10bits)加上目的地标识(destination ID(10bits)),即BAP routing ID=Path ID+destination ID,其中Path ID表示数据包的传输路径,destination ID表示数据包要传输到的目标IAB节点。
在一些实施方式中,第一IAB节点根据BAP control PDU,对第一IAB节点的下游节点执行对应的数据调度操作,包括以下至少一项:
(1)当BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下,即指示拓扑关系为intra-CU时,第一IAB节点恢复对第一IAB节点的下游节点的上行调度,或者待IAB-donor-CU进行BAP路由配置重配或者BAP路由映射配置重配后再恢复对第一IAB节点的下游节点的上行调度,或者是否恢复上行调度取决于实现;
需要说明的是,上述“BAP路由配置重配”和“BAP路由映射配置重配”中的“重配”表示的意思是重新收到一个这样的配置,然后用新配置来替换旧配置。
BAP路由配置重配针对中间节点传输的数据:一个IAB节点接收到上一个IAB节点传递过来的数据后,会在BAP层解析,如果解析后得到的目的地ID(destination ID)就是本节点的话,那么会停止往下传递;但是如果不是本节点,则需要根据BAP路由配置,从中找到这个数据包BAP header中携带的BAP routing ID在BAP路由配置中对应的下一跳IAB节点,从而进行数据的传输。
BAP路由映射配置针对高层来的数据:一个数据包如果从某一IAB节点高层(高于BAP层的协议层)产生,那么在BAP层生成数据时,需要在BAP header中填BAP routing ID,用来说明这个节点要传输到哪儿,通过哪条路径传输,这个时候要用到的就是BAP路由映射配置,也就是根据IP层的包头从BAP路由映射配置中找到对应需要填入BAP header的BAP routing ID。
上述是否恢复上行调度取决于实现(Left to implementation),指的是具体的操作看各个厂商的实现方法,不进行标准化。
(2)当BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下,即指示拓扑关系为inter-IAB-donor-CU时,在IAB-donor-CU对第一IAB节点服务的所有终端完成RRC重配之前,第一IAB节点停止对第一IAB节点的下游节点的上行调度;
(3)当BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下,或者处于相同IAB-donor-CU下的不同IAB-donor-DU下,即指示拓扑关系为intra-IAB-donor-CU,intra-IAB-donor-DU或intra-IAB-donor-CU,inter-donor-DU时,第一IAB节点恢复对第一IAB节点的下游节点的上行调度,或者待IAB-donor-CU进行BAP路由配置或者BAP路由映射配置重配后再恢复对第一IAB节点的下游节点的上行调度,或者是否恢复上行调度取决于实现。
在一些实施方式中,本方法还包括:
(1)第一IAB节点停止对第一IAB节点的下游节点的上行调度;
(2)当满足预设条件时,第一IAB节点恢复对第一IAB节点的下游节点的上行调度;
其中,预设条件包括以下至少一项:
(1)第一IAB节点从第二IAB节点接收调度消息,即如果某节点被上游节点调度,则该节点可以开始调度其下游节点的上行传输数据。
(2)IAB-donor-CU对第一IAB节点服务的所有终端完成RRC重配;
(3)下游节点从IAB-donor-CU接收新的BAP路由配置或者BAP路由映射配置;
(4)下游节点从IAB-donor-CU、IAB-donor-DU或第二IAB节点接收恢复上行数据发送的指示信息。
需要说明的是,本申请实施例提供的数据调度方法,执行主体可以为数 据调度装置,或者,该数据调度装置中的用于执行数据调度方法的控制模块。本申请实施例中以数据调度装置执行数据调度方法为例,说明本申请实施例提供的数据调度装置。
参见图4,本申请实施例一种数据调度装置400,包括:
接收模块401,用于第一IAB节点接收BAP control PDU,所述第一IAB节点为第二IAB节点的下游节点,所述BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,所述第三IAB节点为所述第二IAB节点进行无线链路恢复之后的上游IAB节点,所述第四IAB节点为所述第二IAB节点进行无线链路恢复之前的上游IAB节点;
第一调度模块402,用于所述第一IAB节点根据所述BAP control PDU,对所述第一IAB节点的下游节点执行对应的数据调度操作,所述第一IAB节点的下游节点为IAB节点或者终端。
在一些实施方式中,所述BAP control PDU中包含第一指示域;
当所述第一指示域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB宿主集中处理单元IAB-donor-CU下;当所述第一指示域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同的IAB-donor-CU下;
或者,
当所述第一指示域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同宿主分布处理单元IAB-donor-DU下;当所述第一指示域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;
或者,
当所述第一指示域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为相同的IAB节点;当所述第一指示域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为不同的IAB节点;
所述第一调度模块,进一步用于:
当所述第一指示域为第一值时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度;
当所述第一指示域为第二值时,所述第一IAB节点停止对所述第一IAB节点的下游节点的上行调度。
在一些实施方式中,当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下的不同IAB-donor-DU下;当所述BAP control PDU的PDU type域为第三值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;
或者,
当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;
或者,
当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;
或者,
当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为相同的IAB节点;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU 用于指示所述第三IAB节点与所述第四IAB节点为不同的IAB节点。
在一些实施方式中,所述BAP control PDU中包含第二指示域;
所述BAP control PDU中的第二指示域用于指示以下任意一项:
所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;
所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下的不同IAB-donor-DU下;
所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;
或者,
所述BAP control PDU中的第二指示域用于指示以下任意一项:
所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;
所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;
或者,
所述BAP control PDU中的第二指示域用于指示以下任意一项:
所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下;
所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;
或者,
所述BAP control PDU中的第二指示域用于指示以下任意一项:
所述第三IAB节点与所述第四IAB节点为相同的IAB节点;
所述第三IAB节点与所述第四IAB节点为不同的IAB节点。
在一些实施方式中,所述第一调度模块,进一步用于以下至少一项:
当所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度,或者待IAB-donor-CU进行BAP 路由配置重配或者BAP路由映射配置重配后再恢复对所述第一IAB节点的下游节点的上行调度;
当所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下时,在IAB-donor-CU对所述第一IAB节点服务的所有终端完成无线资源控制RRC重配之前,所述第一IAB节点停止对所述第一IAB节点的下游节点的上行调度;
当所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下,或者处于相同IAB-donor-CU下的不同IAB-donor-DU下时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度,或者待IAB-donor-CU进行BAP路由配置或者BAP路由映射配置重配后再恢复对所述第一IAB节点的下游节点的上行调度。
在一些实施方式中,所述装置还包括:
所述第二调度模块,用于所述第一IAB节点停止对所述第一IAB节点的下游节点的上行调度;
所述第三调度模块,用于当满足预设条件时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度;
其中,所述预设条件包括以下至少一项:
所述第一IAB节点从第二IAB节点接收调度消息;
IAB-donor-CU对所述第一IAB节点服务的所有终端完成RRC重配;
所述下游节点从IAB-donor-CU接收新的BAP路由配置或者BAP路由映射配置;
所述下游节点从IAB-donor-CU、IAB-donor-DU或第二IAB节点接收恢复上行数据发送的指示信息。
在一些实施方式中,所述BAP control PDU中包含第三指示域;
当所述第三指示域为目标值时,所述BAP control PDU用于向所述第一IAB节点指示与所述目标值对应的回传链路恢复成功;
其中,所述第三指示域包括以下任意一项:
所述BAP control PDU中的预留域;
BAP routing ID;
BH Link ID;
Path ID。
在本申请实施例中,第一IAB节点根据进行无线链路恢复的节点接入的拓扑网络是否发生变化,对下游节点进行的相应数据调度操作,从而避免丢失上行传输数据,提高上行数据的传输可靠性。
本申请实施例中的数据调度装置可以是装置,具有操作***的装置或电子设备,也可以是终端中的部件、集成电路、或芯片。该装置或电子设备可以是移动终端,也可以为非移动终端。示例性的,移动终端可以包括但不限于上述所列举的终端11的类型,非移动终端可以为服务器、网络附属存储器(Network Attached Storage,NAS)、个人计算机(Personal Computer,PC)、电视机(Television,TV)、柜员机或者自助机等,本申请实施例不作具体限定。
本申请实施例提供的数据调度装置能够实现图2的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
可选的,如图5所示,本申请实施例还提供一种通信设备500,包括处理器501,存储器502,存储在存储器502上并可在所述处理器501上运行的程序或指令,例如,该通信设备500为终端时,该程序或指令被处理器501执行时实现上述数据调度方法实施例的各个过程,且能达到相同的技术效果。该通信设备500为网络侧设备时,该程序或指令被处理器501执行时实现上述数据调度方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种第一IAB节点,包括处理器和通信接口,其中,所述通信接口用于第一IAB节点接收BAP control PDU,所述第一IAB节点为第二IAB节点的下游节点,所述BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,所述第三IAB节点为所述第二IAB节点进行无线链路恢复之后的上游IAB节点,所述第四IAB节点为所述第二IAB节点进行无线链路恢复之前的上游IAB节点;所述处理器用于所述第一IAB节点根据所述BAP control PDU,对所述第一IAB节点的下游节点执行对应的数据调度操作,所述第一IAB节点的下游节点为IAB节点或者 终端。该网络侧设备实施例是与上述网络侧设备方法实施例对应的,上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中,且能达到相同的技术效果。
具体地,本申请实施例还提供了一种第一IAB节点。如图6所示,该第一IAB节点600包括:天线61、射频装置62、基带装置63。天线61与射频装置62连接。在上行方向上,射频装置62通过天线61接收信息,将接收的信息发送给基带装置63进行处理。在下行方向上,基带装置63对要发送的信息进行处理,并发送给射频装置62,射频装置62对收到的信息进行处理后经过天线61发送出去。
上述频带处理装置可以位于基带装置63中,以上实施例中第一IAB节点执行的方法可以在基带装置63中实现,该基带装置63包括处理器64和存储器y5。
基带装置63例如可以包括至少一个基带板,该基带板上设置有多个芯片,如图6所示,其中一个芯片例如为处理器64,与存储器65连接,以调用存储器65中的程序,执行以上方法实施例中所示的网络设备操作。
该基带装置63还可以包括网络接口66,用于与射频装置62交互信息,该接口例如为通用公共无线接口(Common Public Radio Interface,简称CPRI)。
具体地,本发明实施例的网络侧设备还包括:存储在存储器65上并可在处理器64上运行的指令或程序,处理器64调用存储器65中的指令或程序执行图6所示各模块执行的方法,并达到相同的技术效果,为避免重复,故不在此赘述。
本申请实施例还提供一种计算机程序产品,所述计算机程序产品被存储在非易失的存储介质中,所述计算机程序产品被至少一个处理器执行以实现上述数据调度方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种可读存储介质,所述可读存储介质可以是非瞬态的,所述可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现上述数据调度方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
其中,所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质,包括计算机可读存储介质,如计算机只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现上述数据调度方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为***级芯片,***芯片,芯片***或片上***芯片等。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的, 本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。
Claims (19)
- 一种数据调度方法,包括:第一无线接入与回传一体化IAB节点接收回传自适应协议控制协议数据单元BAP control PDU,所述第一IAB节点为第二IAB节点的下游节点,所述BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,所述第三IAB节点为所述第二IAB节点进行无线链路恢复之后的上游IAB节点,所述第四IAB节点为所述第二IAB节点进行无线链路恢复之前的上游IAB节点;所述第一IAB节点根据所述BAP control PDU,对所述第一IAB节点的下游节点执行对应的数据调度操作,所述第一IAB节点的下游节点为IAB节点或者终端。
- 根据权利要求1所述的方法,其中,所述BAP control PDU中包含第一指示域;当所述第一指示域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB宿主集中处理单元IAB-donor-CU下;当所述第一指示域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同的IAB-donor-CU下;或者,当所述第一指示域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同宿主分布处理单元IAB-donor-DU下;当所述第一指示域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;或者,当所述第一指示域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为相同的IAB节点;当所述第一指示域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB 节点为不同的IAB节点;所述第一IAB节点根据所述BAP control PDU,对所述第一IAB节点的下游节点执行对应的数据调度操作,包括:当所述第一指示域为第一值时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度;当所述第一指示域为第二值时,所述第一IAB节点停止对所述第一IAB节点的下游节点的上行调度。
- 根据权利要求1所述的方法,其中,当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下的不同IAB-donor-DU下;当所述BAP control PDU的PDU type域为第三值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;或者,当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;或者,当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;或者,当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为相同的IAB节点;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为不同的IAB节点。
- 根据权利要求1所述的方法,其中,所述BAP control PDU中包含第二指示域;所述BAP control PDU中的第二指示域用于指示以下任意一项:所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下的不同IAB-donor-DU下;所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;或者,所述BAP control PDU中的第二指示域用于指示以下任意一项:所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;或者,所述BAP control PDU中的第二指示域用于指示以下任意一项:所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下;所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;或者,所述BAP control PDU中的第二指示域用于指示以下任意一项:所述第三IAB节点与所述第四IAB节点为相同的IAB节点;所述第三IAB节点与所述第四IAB节点为不同的IAB节点。
- 根据权利要求2至4中任意一项所述的方法,其中,所述第一IAB节点根据所述BAP control PDU,对所述第一IAB节点的下游节点执行对应的数据调度操作,包括以下至少一项:当所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度,或者待IAB-donor-CU进行BAP路由配置重配或者BAP路由映射配置重配后再恢复对所述第一IAB节点的下游节点的上行调度;当所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下时,在IAB-donor-CU对所述第一IAB节点服务的所有终端完成无线资源控制RRC重配之前,所述第一IAB节点停止对所述第一IAB节点的下游节点的上行调度;当所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下,或者处于相同IAB-donor-CU下的不同IAB-donor-DU下时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度,或者待IAB-donor-CU进行BAP路由配置或者BAP路由映射配置重配后再恢复对所述第一IAB节点的下游节点的上行调度。
- 根据权利要求4所述的方法,其中,所述方法还包括:所述第一IAB节点停止对所述第一IAB节点的下游节点的上行调度;当满足预设条件时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度;其中,所述预设条件包括以下至少一项:所述第一IAB节点从第二IAB节点接收调度消息;IAB-donor-CU对所述第一IAB节点服务的所有终端完成RRC重配;所述下游节点从IAB-donor-CU接收新的BAP路由配置或者BAP路由映射配置;所述下游节点从IAB-donor-CU、IAB-donor-DU或第二IAB节点接收恢复上行数据发送的指示信息。
- 根据权利要求1所述的方法,其中,所述BAP control PDU中包含第 三指示域;当所述第三指示域为目标值时,所述BAP control PDU用于向所述第一IAB节点指示与所述目标值对应的回传链路恢复成功;其中,所述第三指示域包括以下任意一项:所述BAP control PDU中的预留域;BAP路由标识BAP routing ID;回传链路标识BH Link ID;路径标识Path ID。
- 一种数据调度装置,包括:接收模块,用于第一IAB节点接收BAP control PDU,所述第一IAB节点为第二IAB节点的下游节点,所述BAP control PDU用于指示第三IAB节点与第四IAB节点接入的拓扑网络是否发生变化,所述第三IAB节点为所述第二IAB节点进行无线链路恢复之后的上游IAB节点,所述第四IAB节点为所述第二IAB节点进行无线链路恢复之前的上游IAB节点;第一调度模块,用于所述第一IAB节点根据所述BAP control PDU,对所述第一IAB节点的下游节点执行对应的数据调度操作,所述第一IAB节点的下游节点为IAB节点或者终端。
- 根据权利要求8所述的装置,其中,所述BAP control PDU中包含第一指示域;当所述第一指示域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB宿主集中处理单元IAB-donor-CU下;当所述第一指示域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同的IAB-donor-CU下;或者,当所述第一指示域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同宿主分布处理单元IAB-donor-DU下;当所述第一指示域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同 IAB-donor-DU下;或者,当所述第一指示域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为相同的IAB节点;当所述第一指示域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为不同的IAB节点;所述第一调度模块,进一步用于:当所述第一指示域为第一值时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度;当所述第一指示域为第二值时,所述第一IAB节点停止对所述第一IAB节点的下游节点的上行调度。
- 根据权利要求8所述的装置,其中,当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下的不同IAB-donor-DU下;当所述BAP control PDU的PDU type域为第三值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;或者,当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;或者,当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于 相同IAB-donor-CU下;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;或者,当所述BAP control PDU的PDU type域为第一值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为相同的IAB节点;当所述BAP control PDU的PDU type域为第二值时,所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点为不同的IAB节点。
- 根据权利要求8所述的装置,其中,所述BAP control PDU中包含第二指示域;所述BAP control PDU中的第二指示域用于指示以下任意一项:所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下的不同IAB-donor-DU下;所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;或者,所述BAP control PDU中的第二指示域用于指示以下任意一项:所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下;所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-DU下;或者,所述BAP control PDU中的第二指示域用于指示以下任意一项:所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下;所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下;或者,所述BAP control PDU中的第二指示域用于指示以下任意一项:所述第三IAB节点与所述第四IAB节点为相同的IAB节点;所述第三IAB节点与所述第四IAB节点为不同的IAB节点。
- 根据权利要求9至11中任意一项所述的装置,其中,所述第一调度模块,进一步用于以下至少一项:当所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-CU下时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度,或者待IAB-donor-CU进行BAP路由配置重配或者BAP路由映射配置重配后再恢复对所述第一IAB节点的下游节点的上行调度;当所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于不同IAB-donor-CU下时,在IAB-donor-CU对所述第一IAB节点服务的所有终端完成无线资源控制RRC重配之前,所述第一IAB节点停止对所述第一IAB节点的下游节点的上行调度;当所述BAP control PDU用于指示所述第三IAB节点与所述第四IAB节点接入的拓扑网络为处于相同IAB-donor-DU下,或者处于相同IAB-donor-CU下的不同IAB-donor-DU下时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度,或者待IAB-donor-CU进行BAP路由配置或者BAP路由映射配置重配后再恢复对所述第一IAB节点的下游节点的上行调度。
- 根据权利要求11所述的装置,其中,所述装置还包括:第二调度模块,用于所述第一IAB节点停止对所述第一IAB节点的下游节点的上行调度;第三调度模块,用于当满足预设条件时,所述第一IAB节点恢复对所述第一IAB节点的下游节点的上行调度;其中,所述预设条件包括以下至少一项:所述第一IAB节点从第二IAB节点接收调度消息;IAB-donor-CU对所述第一IAB节点服务的所有终端完成RRC重配;所述下游节点从IAB-donor-CU接收新的BAP路由配置或者BAP路由映 射配置;所述下游节点从IAB-donor-CU、IAB-donor-DU或第二IAB节点接收恢复上行数据发送的指示信息。
- 根据权利要求8所述的装置,其中,所述BAP control PDU中包含第三指示域;当所述第三指示域为目标值时,所述BAP control PDU用于向所述第一IAB节点指示与所述目标值对应的回传链路恢复成功;其中,所述第三指示域包括以下任意一项:所述BAP control PDU中的预留域;BAP routing ID;回传链路标识BH Link ID;Path ID。
- 一种第一IAB节点,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求1至7任一项所述的数据调度方法的步骤。
- 一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如权利要求1至7任一项所述的数据调度方法的步骤。
- 一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如权利要求1至7任一项所述的数据调度方法的步骤。
- 一种计算机程序产品,所述计算机程序产品被存储在可读存储介质中,所述计算机程序产品被至少一个处理器执行时实现如权利要求1至7任一项所述的数据调度方法的步骤。
- 一种终端,所述终端被配置成用于执行如权利要求1至7任一项所述的数据调度方法的步骤。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110351906.8 | 2021-03-31 | ||
CN202110351906.8A CN115150965B (zh) | 2021-03-31 | 2021-03-31 | 数据调度方法、装置及设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022206544A1 true WO2022206544A1 (zh) | 2022-10-06 |
Family
ID=83405344
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/082731 WO2022206544A1 (zh) | 2021-03-31 | 2022-03-24 | 数据调度方法、装置及设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN115150965B (zh) |
WO (1) | WO2022206544A1 (zh) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110621050A (zh) * | 2018-06-20 | 2019-12-27 | 财团法人工业技术研究院 | 网络链路拓扑适应方法及接入和回传一体化节点 |
CN110784413A (zh) * | 2018-07-31 | 2020-02-11 | 华硕电脑股份有限公司 | 更新集成接入后传节点的路由表的方法和设备 |
WO2021028807A1 (en) * | 2019-08-09 | 2021-02-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Dual connectivity recovery on backhaul failure |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110351109B (zh) * | 2018-04-04 | 2022-04-29 | 中兴通讯股份有限公司 | 拓扑信息的管理方法及装置、***、存储介质、电子装置 |
CN110536351B (zh) * | 2019-02-15 | 2024-06-04 | 中兴通讯股份有限公司 | Iab网络中信息处理方法、iab及计算机存储介质 |
WO2021026704A1 (zh) * | 2019-08-09 | 2021-02-18 | 华为技术有限公司 | 一种无线通信的方法和装置 |
GB2602794A (en) * | 2021-01-06 | 2022-07-20 | Canon Kk | Management of radio link failure and deficiencies in integrated access backhauled networks |
-
2021
- 2021-03-31 CN CN202110351906.8A patent/CN115150965B/zh active Active
-
2022
- 2022-03-24 WO PCT/CN2022/082731 patent/WO2022206544A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110621050A (zh) * | 2018-06-20 | 2019-12-27 | 财团法人工业技术研究院 | 网络链路拓扑适应方法及接入和回传一体化节点 |
CN110784413A (zh) * | 2018-07-31 | 2020-02-11 | 华硕电脑股份有限公司 | 更新集成接入后传节点的路由表的方法和设备 |
WO2021028807A1 (en) * | 2019-08-09 | 2021-02-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Dual connectivity recovery on backhaul failure |
Non-Patent Citations (1)
Title |
---|
FUTUREWEI: "RAN2 impacts of Rel.17 IAB topology adaptation enhancements", 3GPP DRAFT; R2-2010490, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20201101, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051943156 * |
Also Published As
Publication number | Publication date |
---|---|
CN115150965B (zh) | 2023-06-23 |
CN115150965A (zh) | 2022-10-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110636628B (zh) | 信息传输方法及装置 | |
EP3610673B1 (en) | Access node and methods for handovers in a dual connectivity communications system | |
KR102460350B1 (ko) | 통신 시스템에서 데이터 송수신 방법 및 장치 | |
CN110622548A (zh) | 在双连接网络中报告从节点故障的方法和*** | |
CN110198556B (zh) | 无线资源控制rrc消息处理方法、装置和*** | |
KR20170107534A (ko) | 무선 베어러 재구성 방법, 무선 베어러 구축 방법, 사용자 기기, 및 기지국 | |
US20220263743A1 (en) | Selective packet duplication or alternative packet transmission based on survival time | |
US10728946B2 (en) | System information handling for dual connectivity cellular systems | |
WO2019096274A1 (zh) | 信号传输的方法和装置 | |
WO2020088305A1 (zh) | 一种通信方法、通信装置及*** | |
KR20210141696A (ko) | 링크상태 통지 방법 및 장치, 링크 처리 방법 및 장치, 저장매체, 전자장치 | |
US20230269653A1 (en) | Rerouting method and apparatus, and communication device | |
CN112715053A (zh) | 用于处理无线中继网络中的无线电链路监测和无线电链路故障的***、设备和方法 | |
JP2021511705A (ja) | 中継のルーティング方法及び通信ノード | |
WO2018202131A1 (zh) | 通信方法、装置及*** | |
US20230413154A1 (en) | Data Unit Processing Method and Node | |
WO2017201689A1 (zh) | 数据传输方法、设备及*** | |
WO2022206544A1 (zh) | 数据调度方法、装置及设备 | |
CN117044278A (zh) | 辅小区组故障检测和报告 | |
JP2023524345A (ja) | ネットワークコーディング動作の中断及び再開をシグナリングする方法及び装置 | |
WO2022188705A1 (zh) | 信息传输方法、装置及iab节点 | |
CN117062253B (zh) | 一种通信方法 | |
CN116506869A (zh) | 一种通信***中由通信节点执行的方法及通信节点 | |
CN117751678A (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: 22778727 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 22778727 Country of ref document: EP Kind code of ref document: A1 |