WO2022151095A1 - 信号的发送和接收方法、装置和通信系统 - Google Patents
信号的发送和接收方法、装置和通信系统 Download PDFInfo
- Publication number
- WO2022151095A1 WO2022151095A1 PCT/CN2021/071591 CN2021071591W WO2022151095A1 WO 2022151095 A1 WO2022151095 A1 WO 2022151095A1 CN 2021071591 W CN2021071591 W CN 2021071591W WO 2022151095 A1 WO2022151095 A1 WO 2022151095A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- congestion
- iab
- report message
- information
- node
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 106
- 238000004891 communication Methods 0.000 title claims abstract description 80
- 230000011664 signaling Effects 0.000 claims description 53
- 230000006978 adaptation Effects 0.000 claims description 4
- 235000019580 granularity Nutrition 0.000 description 35
- 238000010586 diagram Methods 0.000 description 28
- 230000015654 memory Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 12
- 230000007774 longterm Effects 0.000 description 10
- 238000004590 computer program Methods 0.000 description 7
- 238000007726 management method Methods 0.000 description 6
- 230000000116 mitigating effect Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 5
- 238000012790 confirmation Methods 0.000 description 5
- 238000013507 mapping Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- ZIXXRXGPBFMPFD-UHFFFAOYSA-N 1-chloro-4-[(4-chlorophenyl)disulfanyl]benzene Chemical compound C1=CC(Cl)=CC=C1SSC1=CC=C(Cl)C=C1 ZIXXRXGPBFMPFD-UHFFFAOYSA-N 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 235000008694 Humulus lupulus Nutrition 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
- H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0289—Congestion control
Definitions
- the embodiments of the present application relate to the field of communication technologies.
- IAB Integrated access and backhaul
- NG-RAN next generation radio access network
- IAB-node An integrated access and backhaul node
- NR New Radio
- IAB-donor represents a network device (eg, gNB) that supports IAB functionality.
- An IAB node can connect to an IAB host (IAB-donor) through one or more hops. These multi-hop connections form a Directed Acyclic Graph (DAG) topology with the IAB host as the root node.
- DAG Directed Acyclic Graph
- the IAB host is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.
- IAB-node supports the function of gNB-DU (distributed unit, distributed unit). IAB-node DU is also called IAB-DU. IAB-DU is the wireless connection to the terminal equipment (UE) and the next hop IAB-node. The endpoint of the incoming (NR access) interface is also the endpoint of the F1 protocol to the gNB-CU (central unit) on the IAB-donor.
- the IAB-DU can serve normal UEs and IAB sub-nodes.
- IAB-node In addition to the gNB-DU function, the IAB-node also supports a part of UE functions, called IAB-MT (Mobile Termination).
- IAB-MT includes functions such as physical layer, layer 2, RRC and NAS to connect to another IAB-node Or gNB-DU of IAB-donor, gNB-CU connected to IAB-donor and connected to core network.
- IAB-MT can support functions such as UE physical layer, access stratum (AS), radio resource control (RRC) layer and non-access stratum (NAS) layer, and can be connected to the IAB parent node.
- AS access stratum
- RRC radio resource control
- NAS non-access stratum
- FIG. 1 is a schematic diagram of the IAB topology.
- the IAB-node 100 includes an IAB-MT functional unit 101 and an IAB-DU functional unit 102, and the adjacent nodes on the interface of the IAB-DU functional unit 102 are called child nodes. node), the sub-nodes 201, 202, 203 shown in FIG. 1, the IAB-DU functional unit 102 and the sub-nodes 201, 202, 203 can communicate through the air interface (Uu); the IAB-MT functional unit 101
- the adjacent nodes on the interface are called parent nodes, such as the parent nodes 301 and 302 shown in FIG. to communicate.
- the direction from the IAB-node 100 to the child nodes 201, 202, 203 is called the downstream direction
- the direction from the IAB-node 100 to the parent nodes 301, 302 is called the upstream (upstream) direction.
- the IAB-donor (not shown) performs centralized resource, topology and routing management for the IAB topology 10 .
- Congestion may occur when there is a mismatch between the data rate of the ingress and the data rate of the egress of an IAB node.
- the inventors of the present application found that the methods for alleviating congestion in the prior art have some limitations, such as: unable to solve long-term congestion problems; limited options for alleviating congestion; inability to alleviate uplink congestion, etc.
- the embodiments of the present application provide a method, device and communication system for transmitting and receiving signals.
- a congestion report message is sent, whereby the host central unit (IAB-donor CU) can use a control plane (control plane, CP)-based method to alleviate the congestion of the IAB-node.
- control plane control plane, CP
- an apparatus for sending and receiving signals is provided, which is applied to an integrated access and backhaul node (IAB) node, including:
- the first sending and receiving unit which sends a congestion report message to the host central unit (IAB-donor CU) of the integrated access and backhaul node, and the congestion report message is used to indicate the integrated access and backhaul.
- the load status of the communication link of the transmission node is used to indicate the integrated access and backhaul.
- a device for transmitting and receiving a signal is provided, which is applied to a host central unit (IAB-donor CU), including:
- a third sending and receiving unit that receives a congestion report message sent by an integrated access and backhaul node (IAB) for indicating the load of the communication link of the integrated access and backhaul node state.
- IAB integrated access and backhaul node
- a method for sending and receiving signals including:
- the integrated access and backhaul node sends a congestion report message to the home central unit (IAB-donor CU) of the integrated access and backhaul node, and the congestion report message is used to indicate the integrated access and backhaul node. Load status of the communication link of the incoming and backhaul nodes.
- a method for sending and receiving signals including:
- the host central unit receives the congestion report message sent by the integrated access and backhaul node (IAB), the congestion report message is used to indicate the communication link of the integrated access and backhaul node. load status.
- the IAB-node sends a congestion report message to the IAB-donor CU, whereby the IAB-donor CU can use a CP-based method to alleviate the congestion of the IAB-node.
- Fig. 1 is a schematic diagram of IAB topology
- Fig. 2 is a schematic diagram of hop-by-hop downlink flow control
- FIG. 3 is a schematic diagram of a method for sending and receiving signals in an embodiment of the first aspect of the present application
- FIG. 4 is a schematic diagram of a downlink load state indicated by a congestion report message in an embodiment of the first aspect of the present application
- Fig. 5 is a schematic diagram of the congestion report message indicating the load state of the uplink in the embodiment of the first aspect of the present application
- Fig. 6 is a schematic diagram of IAB-donor CU 6 triggering IAB node 3 to send congestion report message through request information;
- Fig. 7 is a schematic diagram of IAB-donor CU 6 sending congestion reporting configuration information to IAB node 3;
- Fig. 8 is another schematic diagram of IAB-donor CU 6 triggering IAB node 3 to send congestion report message through request information;
- FIG. 9 is a schematic diagram of a method for transmitting and receiving signals in an embodiment of the second aspect
- Fig. 10 is a schematic diagram of the apparatus for transmitting and receiving signals in the embodiment of the third aspect
- Fig. 11 is a schematic diagram of the apparatus for transmitting and receiving signals in the embodiment of the fourth aspect
- FIG. 12 is a schematic structural diagram of a network device according to an embodiment of the present application.
- FIG. 13 is a schematic diagram of a terminal device according to an embodiment of the present application.
- the terms “first”, “second”, etc. are used to distinguish different elements in terms of numelation, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be referred to by these terms restricted.
- the term “and/or” includes any and all combinations of one or more of the associated listed items.
- the terms “comprising”, “including”, “having”, etc. refer to the presence of stated features, elements, elements or components, but do not preclude the presence or addition of one or more other features, elements, elements or components.
- the term "communication network” or “wireless communication network” may refer to a network that conforms to any of the following communication standards, such as New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.
- NR New Radio
- LTE Long Term Evolution
- LTE-A Long Term Evolution
- LTE-A LTE-Advanced
- WCDMA Wideband Code Division Multiple Access
- High-Speed Packet Access High-Speed Packet Access
- the communication between devices in the communication system can be carried out according to communication protocols at any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G , New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
- Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
- Network devices may include but are not limited to the following devices: integrated access and backhaul node (IAB-node), base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception) Point), broadcast transmitter, Mobile Management Entity (MME, Mobile Management Entity), gateway, server, Radio Network Controller (RNC, Radio Network Controller), Base Station Controller (BSC, Base Station Controller) and so on.
- IAB-node integrated access and backhaul node
- BS Base Station
- AP Access Point
- TRP Transmission Reception point
- MME Mobile Management Entity
- gateway server
- Radio Network Controller Radio Network Controller
- BSC Base Station Controller
- the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include a remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low power node (eg femeto, pico, etc.).
- RRH Remote Radio Head
- RRU Remote Radio Unit
- relay relay
- low power node eg femeto, pico, etc.
- base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic area.
- the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
- the term "User Equipment” (UE, User Equipment) or “Terminal Equipment” (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services.
- a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, and the like.
- the terminal device may include but is not limited to the following devices: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
- Cellular Phone Cellular Phone
- PDA Personal Digital Assistant
- wireless modem wireless communication device
- handheld device machine type communication device
- laptop computer Cordless phones, smartphones, smart watches, digital cameras, and more.
- the terminal device may also be a machine or device that performs monitoring or measurement, such as but not limited to: Machine Type Communication (MTC, Machine Type Communication) terminals, In-vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
- MTC Machine Type Communication
- D2D Device to Device
- M2M Machine to Machine
- network side refers to one side of the network, which may be a certain base station, and may also include one or more network devices as described above.
- user side or “terminal side” or “terminal device side” refers to the side of a user or terminal, which may be a certain UE, or may include one or more terminal devices as above.
- the high-level signaling may be, for example, Radio Resource Control (RRC) signaling; for example, it is called an RRC message (RRC message), for example, including MIB, system information (system information), and dedicated RRC message; RRC IE (RRC information element).
- RRC Radio Resource Control
- the high-layer signaling may also be, for example, F1-C signaling, or the F1AP protocol.
- F1-C signaling or the F1AP protocol.
- the present application is not limited to this.
- Hop-by-hop downlink flow control which is based on the backhaul adaptation protocol (BAP).
- BAP backhaul adaptation protocol
- PDU protocol data unit
- end-to-end flow control the method through the new radio (new radio, NR) user plane protocol layer downlink data Transmission status (downlink data delivery status, DDDS) to achieve.
- FIG. 2 is a schematic diagram of hop-by-hop downlink flow control.
- IAB node 3 when IAB node 3 experiences congestion in the downstream direction, for example, when the buffer load exceeds a certain threshold, IAB node 3 sends a flow control feedback message to the parent node, ie, IAB node 5.
- This flow control feedback information is sent in the form of a BAP Control PDU.
- the parent node ie, the IAB node 5
- IAB node (node) 3 and IAB node (node) 4 are both child nodes of IAB node (node) 5; IAB node (node) 5 is a child of IAB host node (IAB-donor) 6a node; IAB node (node) 2 is a child node of IAB node (node) 3 and IAB node (node) 4; IAB node (node) 1 is a child node of IAB node (node) 2.
- hop-by-hop flow control can only alleviate short-term congestion, but cannot solve long-term congestion; DDDS cannot provide information about the nodes where congestion occurs, so the options for alleviating congestion are limited; the above-mentioned hop-by-hop and end-to-end Flow control can only be used to relieve downstream congestion.
- the embodiments of the first aspect of the present application provide a method for sending and receiving signals.
- FIG. 3 is a schematic diagram of a method for sending and receiving signals according to an embodiment of the present application. As shown in FIG. 3 , the method includes:
- the integrated access and backhaul node sends a congestion report message to the home central unit (IAB-donor CU) of the integrated access and backhaul node, where the congestion report message is used to indicate the integration
- the load status of the communication links of the access and backhaul nodes is used to indicate the integration
- the IAB sends a congestion report message for indicating the load state of the communication link to the IAB-donor CU, whereby the IAB-donor CU can perform control plane (CP)-based congestion mitigation Methods, for example, the IAB-donor CU can perform according to the congestion message: reconfigure routing, and/or backhaul radio link control (BH RLC) channel mapping, and/or resource reallocation, etc.
- CP control plane
- the IAB-donor CU can perform according to the congestion message: reconfigure routing, and/or backhaul radio link control (BH RLC) channel mapping, and/or resource reallocation, etc. This can alleviate long-term data congestion, reduce data loss, and optimize network performance.
- CP control plane
- BH RLC backhaul radio link control
- the method may further include:
- the integrated access and backhaul node communicates with the child node and/or the parent node through the communication link.
- the communication link may be an uplink or a downlink.
- the congestion report message in operation 301 may indicate the load status of the uplink and/or downlink.
- FIG. 4 is a schematic diagram of a downlink load state indicated by a congestion report message in an embodiment of the first aspect of the present application.
- the IAB node 3 when the downlink of the IAB node (node) 3 is congested, for example, the buffer load (buffer load) exceeds a certain threshold, the IAB node 3 sends the congestion to the host central unit (IAB-donor CU) 6 A report message to indicate the downlink load status of the IAB node (node) 3.
- the description of other nodes in FIG. 4 is the same as the related description for FIG. 2 .
- FIG. 5 is a schematic diagram of the congestion report message indicating the load status of the uplink in the embodiment of the first aspect of the present application.
- the IAB node 3 when the uplink of the IAB node (node) 3 is congested, for example, the buffer load (buffer load) exceeds a certain threshold, the IAB node 3 sends the congestion to the host central unit (IAB-donor CU) 6 A report message to indicate the load status of the uplink of the IAB node (node) 3.
- the description of other nodes in FIG. 5 is the same as the related description for FIG. 2 .
- the operation of the IAB node 3 sending the congestion report message to the host central unit (IAB-donor CU) 6 corresponds to the operation 301 of FIG. 3 .
- the IAB of operation 301 is, for example, the IAB node 3 in FIGS. 4 and 5 .
- the content of the congestion report message sent by the IAB node 3 may include: a buffer size (buffer size), where the buffer size refers to the state of the buffer of the BH RLC channel in the congestion report message; and/or, the buffer occupancy and/or, available buffer size (available buffer size), the available buffer size refers to the maximum traffic that the sender of IAB node 3 should send; and/or, available data rate (available data rate), available data
- the rate refers to the maximum traffic data rate that the sender of the IAB node 3 should use, where the available data rate (available data rate) may also be referred to as the desired data rate (desired data rate); and/or, used to represent the communication chain
- the information that the road is congested (congestion) may be a simple indication information for indicating that the communication link is congested.
- the method may further include:
- the integrated access and backhaul node sends congestion clearance indication information to the host central unit (IAB-donor CU), where the congestion clearance indication information is used to indicate that the communication link of the integrated access and backhaul node is non-congested state.
- the host central unit IAB-donor CU
- the IAB node 3 can send the IAB-donor CU 6 to the Congestion clearance indication information.
- FIG. 3 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
- the execution order of the various operations can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
- Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the description of the above-mentioned FIG. 3 .
- operation 301 may also precede operation 302 .
- the congestion report message may contain an information element (information element, IE), and the IE may be used to carry a list of congestion status information, for example, the name of the list may be Congestion Information List IE.
- IE information element
- the list of congestion state information may include multiple pieces of congestion state information, and each piece of congestion state information includes the content of the congestion report message reported with a certain granularity.
- the granularity may be, for example: per BH RLC channel; alternatively, per routing ID; alternatively, per communication link.
- the BH RLC channel or communication link in the congestion state information can be on the IAB-DU side or on the IAB-MT side.
- the congestion status information may also include information indicating the direction of traffic.
- the content of the congestion report message is reported for each BH RLC channel, and the congestion state information may contain information for indicating the traffic direction to indicate the congestion state information.
- the information used to indicate the traffic direction may be information indicating uplink or downlink, or information indicating ingress (Ingress) or egress (Engress); for another example, for the granularity of communication link
- the congestion status information may also have a piece of information for indicating the traffic direction
- the information indicating the traffic direction may be information indicating that the communication link is an ingress (Ingress) link or an egress (Engress) link, or is information indicating whether the communication link is uplink or downlink.
- routing ID can already distinguish the uplink or the downlink, in the case where the granularity is the routing ID, it may not be necessary to add information for indicating the traffic direction to the congestion state information.
- a piece of congestion state information may include: BH RLC channel ID/or route ID/or link ID, and the content of the corresponding congestion report message.
- a congestion report message may include congestion report information of different granularities.
- the BH RLC channel identifier is unique in each link, so the BH RLC channel identifier mentioned in this application actually refers to the combination of the link identifier and the BH RLC channel identifier, for example, the link identifier + BH RLC channel identifier logo.
- Table 1 is an example of the format of the Congestion Information IE in the Congestion Report message.
- the "O" in the Presence indicates that it is optional. For example, "O” indicates that the granularity or report content of each item in the list of the Congestion Information IE can be selected only one.
- the link identifier instead of using the link identifier directly, the link identifier is equivalently replaced with the BAP address of the previous hop node (Prior-Hop BAP Address) or the BAP address of the next hop node (Next-Hop BAP Address). .
- the congestion report message sent for the uplink and the congestion report message sent for the downlink may have the same message format, eg, the format of the Congestion Information IE is the same for the uplink and downlink (For example, all are in the format shown in Table 1).
- the IAB node 3 when the IAB node 3 receives the polling/request information of the IAB-donor CU 6, the IAB node 3 sends the congestion report message to the IAB-donor CU.
- the request information may include the granularity of the congestion status information in the congestion report message, and/or the BHRLC channel identification, and/or the routing identification, and/or the link identification.
- the request message may also include an uplink or downlink indication, or an entry or exit indication. If the request information includes the granularity (that is, the request information indicates the granularity of the congestion status information), then the IAB node 3 can generate the congestion report message according to the granularity; if the request message includes the BH RLC channel identifier, route identifier, or link identifier , then the IAB node 3 can generate congestion report messages corresponding to these identifiers.
- the request information may also include an interval period and/or duration. Thereby, the IAB node 3 can transmit the congestion report message at the transmission interval period within the duration.
- Fig. 6 is a schematic diagram of IAB-donor CU 6 triggering IAB node 3 to send congestion report message through request information.
- the IAB-donor CU 6 sends request information to the DU of the IAB node 3, and the name of the request information is, for example, CONGESTION REPORT POLLING or CONGESTION REPORT REQUEST; in operation 602, the request information of the IAB node 3
- the DU generates a congestion report message and sends it to the IAB-donor CU 6 according to the granularity in the request information, and/or the BH RLC channel identifier, and/or the routing identifier, and/or the link identifier.
- the IAB node 3 sends the congestion report message to the IAB-donor CU when the predetermined condition of the IAB node 3 is satisfied.
- the predetermined condition includes: the cache load corresponding to the granularity of the congestion state information in the congestion report message exceeds the first threshold and lasts for the first time period.
- the first time period may be implemented by timer 1. For example, when the cache load of a certain granularity reaches the first threshold 1, start or restart timer 1, and when the timer 1 times out, trigger the sending of a congestion report message; when the cache load drops below the first threshold 1, Stop Timer 1 if Timer 1 is running.
- the predetermined condition includes: within the second time period, a response sent by the IAB node 3 with respect to the same identifier (eg, link identifier, BHRLC channel identifier, routing identifier) exceeds the second threshold.
- the second time period may be realized by the timer 2 corresponding to the identifier.
- the counter of the number or instance of the flow control feedback for a certain identity of the BAP sublayer is initialized to an initial value (the initial value is, for example, 0).
- the The counter of the flow control feedback number or instance is incremented by 1, and timer 2 is started or restarted.
- timer 2 is the interval between two flow control feedbacks, and timer 2 is used to indirectly implement the second time period.
- timer 2 is the interval between two flow control feedbacks, and timer 2 is used to indirectly implement the second time period.
- the time is long enough (for example, the second timer expires)
- the operation of sending the BAP sublayer flow control feedback when the cache load of the IAB node 3 exceeds the second threshold reference may be made to the related art.
- the method may further include:
- the integrated access and backhaul node receives the congestion reporting configuration information sent by the host central unit (IAB-donor CU).
- the IAB node 3 receives the congestion reporting configuration information sent by the IAB-donor CU 6.
- the congestion reporting configuration information is used to configure: parameters required by the IAB node 3 in the predetermined conditions for judging the timing of sending the congestion reporting message, and/or parameters or configurations required by the IAB node 3 for sending the congestion reporting message.
- the parameters required in the predetermined conditions used by the IAB node 3 for judging the timing of sending the congestion report message include, for example: the granularity in the above-mentioned predetermined conditions, and/or the first threshold 1, and/or the second threshold, and/or the first threshold Three thresholds 3, and/or the initial value of the timer, etc.
- the parameters or configurations required by the IAB node 3 to send the congestion report message include, for example, the granularity in the congestion report message, and the like.
- the method may further include:
- the integrated access and backhaul node sends configuration confirmation information to the host central unit (IAB-donor CU).
- the configuration confirmation information is used to confirm that the IAB node 3 has received the congestion reporting configuration information.
- Fig. 7 is a schematic diagram of IAB-donor CU 6 sending congestion reporting configuration information to IAB node 3.
- the IAB-donor CU 6 sends the congestion reporting configuration information to the DU of the IAB node 3, and the name of the congestion reporting configuration information is, for example, CONGESTION REPORTING CONFIGURATION; in operation 702, the IAB node 3's
- the DU sends a configuration confirmation message to the IAB-donor CU 6, and the name of the configuration confirmation message is, for example, CONGESTION REPORTING CONFIGURATION ACKNOWLEDGE.
- Operation 701 and operation 702 of FIG. 7 or operation 304 and operation 305 of FIG. 3 may be referred to as a congestion reporting configuration (Congestion Reporting Configuration) procedure.
- the congestion reporting configuration (Congestion Reporting Configuration) process may use control plane signaling.
- the IAB node 3 may receive the congestion reporting configuration information through the F1 interface application protocol (F1 application protocol, F1AP, defined in TS38.473) signaling.
- the Congestion Reporting Configuration (Congestion Reporting Configuration) process may be a newly added IAB process, which may use non-User Equipment (UE) related signaling.
- UE User Equipment
- the congestion report message in operation 301 may be carried in control plane signaling.
- the signaling of the control plane may include, for example, F1 interface application protocol signaling, that is, F1AP signaling is used to carry the congestion report message regardless of the load status of the uplink or the load status of the downlink.
- F1 interface application protocol signaling that is, F1AP signaling is used to carry the congestion report message regardless of the load status of the uplink or the load status of the downlink.
- the congestion report message for the uplink is generated from the IAB-MT of the IAB node 3, and the IAB-DU in the IAB node 3 collocated with the IAB-MT converts the congestion report message generated by the IAB-MT for the uplink.
- the congestion report message is sent to the IAB-donor-CU 6.
- a new IAB elementary procedure can be added to the F1AP service for sending and receiving congestion report messages between gNB-DU and gNB-CU, and the newly added procedure can be named as Congestion Reporting process.
- Congestion Reporting process all considerations of gNB-DU apply to IAB-DU and IAB-donor-DU; gNB-CU refers to IAB-donor-CU.
- an existing process may be used to implement the sending and receiving of congestion report messages between the IAB node 3 and the IAB-donor CU 6.
- the existing process may be a gNB-DU status indication (Status Indication) process, and congestion status information is added to the content of the existing process, such as redesigning the gNB-DU Overload Information IE.
- F1AP signaling be used to carry congestion report messages for both uplink and downlink load states, but also congestion reports for uplink and downlink can be sent through F1AP signaling request, and use of F1AP signaling for the congestion reporting configuration process for both uplink and downlink.
- the DU of the IAB node 3 receives the congestion report request for uplink and downlink from the IAB-donor CU 6 through F1AP signaling, and the DU of the IAB node 3 reports to the IAB through F1AP signaling -donor CU 6 sends a congestion report message; in addition, as shown in Figure 7, the DU of IAB node 3 receives the congestion report configuration for uplink and downlink through F1AP signaling, and sends configuration confirmation information through F1AP signaling.
- the signaling of the control plane may also include signaling in radio resource control (RRC) messages.
- RRC radio resource control
- the downlink that is, for the link on the DU side in the IAB node
- the BH RLC channel, or the congestion report message of the downlink route ID can be carried in the F1AP message
- the uplink that is, for the IAB node.
- the link on the MT side, the BH RLC channel, or the congestion report message of the uplink route ID can be carried in the RRC message.
- Fig. 8 is another schematic diagram of the IAB-donor CU 6 triggering the IAB node 3 to send the congestion report message through the request information.
- the IAB-donor CU 6 sends request information to the MT of the IAB node 3, and the name of the request information is, for example, CONGESTION REPORT POLLING or CONGESTION REPORT REQUEST; in operation 802, the request information of the IAB node 3
- the MT According to the granularity in the request information, and/or the BH RLC channel identifier, and/or the routing identifier, and/or the link identifier, the MT generates a congestion report message and sends it to the IAB-donor CU 6 through an RRC message.
- the MT of the IAB node 3 may also generate a congestion report message and send it through an RRC message when a predetermined condition is satisfied instead of receiving the request information.
- the predetermined condition may be an event type.
- the congestion reporting configuration (Congestion Reporting Configuration) process can use dedicated signaling in the RRC message, such as RRCReconfiguration or RRCResume, the process can refer to the definition in the standard TS38.331 , the content of the configuration information can be added in this process, for example: the granularity in the congestion report message, and/or the above-mentioned first threshold 1 (that is, the cache load threshold), and/or the above-mentioned second threshold, and/or the above-mentioned first threshold Three thresholds 3, and/or the initial value of the above timer, etc.
- the IAB sends a congestion report message for indicating the load state of the communication link to the IAB-donor CU, whereby the IAB-donor CU can perform control plane (CP)-based congestion mitigation Methods, for example, the IAB-donor CU can perform according to the congestion message: reconfigure routing, and/or backhaul radio link control (BH RLC) channel mapping, and/or resource reallocation, etc.
- CP control plane
- the IAB-donor CU can perform according to the congestion message: reconfigure routing, and/or backhaul radio link control (BH RLC) channel mapping, and/or resource reallocation, etc. This can alleviate long-term data congestion, reduce data loss, and optimize network performance.
- CP control plane
- BH RLC backhaul radio link control
- the embodiment of the second aspect of the present application provides a method for sending and receiving a signal, which corresponds to the method of the embodiment of the first aspect.
- FIG. 9 is a schematic diagram of a method for sending and receiving signals in an embodiment of the second aspect. As shown in FIG. 9 , the method includes:
- the host central unit receives a congestion report message sent by an integrated access and backhaul node (IAB), where the congestion report message is used to indicate a communication link of the integrated access and backhaul node load status.
- IAB integrated access and backhaul node
- the content of the congestion report message includes: buffer size (buffer size); and/or, buffer occupancy (buffer occupation); and/or, available buffer size (available buffer size); and/or, available data rate; and/or information used to indicate that the communication link is congested.
- the method further includes:
- the host central unit (IAB-donor CU) also receives the congestion clearance indication information sent by the integrated access and backhaul node, where the congestion clearance indication information is used to indicate the communication chain of the integrated access and backhaul node The road is in a non-congested state.
- the congestion report message may include an information element (IE, information element) that is used to carry a list of congestion status information.
- the granularity of the congestion status information is: per backhaul radio link control (BH RLC) channel, and/or per route ID, and/or per communication link.
- the congestion state information when the granularity of the congestion state information is each backhaul radio link control (BH RLC) channel or each communication link, the congestion state information also includes information for indicating the traffic direction (for example, uplink or downlink). link, egress or ingress) information.
- the congestion report message for the uplink has the same message format as the congestion report message for the downlink, for example, the format of the Congestion Information IE in the congestion report message is the same.
- the method further includes:
- the host central unit sends request (polling) information to the integrated access and backhaul node (IAB), wherein, when the request (polling) information is sent, the integrated access and backhaul node (IAB) is received.
- the congestion report message sent by the access and backhaul node (IAB).
- the request information includes the granularity of the congestion state information in the congestion report message, and/or the backhaul radio link control (BH RLC) channel identifier, and/or route identifier, and/or link identifier in the congestion state information road sign.
- the request information also includes the interval period for sending the congestion report message, and/or the duration for sending the congestion report message at the period.
- BH RLC backhaul radio link control
- the method further includes:
- the donor central unit (IAB-donor CU) sends the congestion reporting configuration information to the integrated access and backhaul node (IAB).
- the congestion reporting configuration information is used to configure:
- the integrated access and backhaul node (IAB) is used to determine the parameters required in the predetermined conditions of the timing to send the congestion report message, and/or the integrated access and backhaul node (IAB) sends the congestion report Parameters or configuration required for the message.
- the congestion reporting configuration information can be sent through F1AP signaling or dedicated signaling in an RRC message.
- the congestion report message is carried in control plane signaling.
- the signaling of the control plane includes F1AP signaling.
- the congestion report message can be carried in the F1AP signaling.
- an IAB process may be added to the F1AP to send the congestion report message.
- the control plane signaling may also include RRC messages.
- the congestion report message can be carried in the F1AP; and for the load status of the uplink, the congestion report message is carried in the radio resource control (RRC) message.
- RRC radio resource control
- the donor central unit can also send congestion reporting configuration information to the integrated access and backhaul node (IAB) through dedicated signaling in a radio resource control (RRC) message, and the configuration information is the same as the above The same, e.g., for configuring: the parameters required by the Integrated Access and Backhaul Node (IAB) in the predetermined conditions for judging the timing of sending the Congestion Report message, and/or the Integrated Access and Backhaul The parameters or configuration required by the node (IAB) to send this congestion report message.
- RRC radio resource control
- the IAB sends a congestion report message for indicating the load status of the communication link to the IAB-donor CU, whereby the IAB-donor CU can perform control plane (CP)-based congestion mitigation Methods, for example, the IAB-donor CU can perform according to the congestion message: reconfigure routing, and/or backhaul radio link control (BH RLC) channel mapping, and/or resource reallocation, etc.
- CP control plane
- the IAB-donor CU can perform according to the congestion message: reconfigure routing, and/or backhaul radio link control (BH RLC) channel mapping, and/or resource reallocation, etc. This can alleviate long-term data congestion, reduce data loss, and optimize network performance.
- CP control plane
- BH RLC backhaul radio link control
- Embodiments of the present application provide a device for transmitting and receiving signals.
- the apparatus may be, for example, an integrated access and backhaul node, or may be one or some components or components configured in the integrated access and backhaul node.
- the integrated access and backhaul node is, for example, shown in Figure 4 or IAB-node 3 of Figure 5.
- the apparatus corresponds to the method of an embodiment of the first aspect.
- FIG. 10 is a schematic diagram of an apparatus for transmitting and receiving signals according to an embodiment of the present application.
- an apparatus 1000 for transmitting and receiving signals includes:
- the first sending and receiving unit 1001 which sends a congestion report message to the host central unit (IAB-donor CU) of the integrated access and backhaul node, and the congestion report message is used to indicate the communication of the integrated access and backhaul node The load status of the link.
- IAB-donor CU host central unit
- the content of the congestion report message includes: buffer size (buffer size); and/or, buffer occupancy (buffer occupation); and/or, available buffer size (available buffer size); and/or, available data rate (available data) rate); and/or, information used to indicate that the communication link is congested.
- the first sending and receiving unit 1001 further sends congestion clearing indication information to a host central unit (IAB-donor CU), where the congestion clearing indication information is used to indicate the integrated access and backhaul nodes.
- the communication link is in a non-congested state.
- the congestion report message includes an information element (IE, information element), which is used to carry a list of congestion state information, the granularity of which is: each backhaul radio link control (BH RLC) channel , and/or each route ID, and/or each communication link.
- IE information element
- the congestion report message for the uplink has the same message format as the congestion report message for the downlink.
- the congestion state information In the case where the granularity of the congestion state information is each backhaul radio link control (BH RLC) channel or each communication link, the congestion state information also includes information for indicating the traffic direction.
- BH RLC backhaul radio link control
- the integrated access and backhaul node receives the polling information of the host central unit (IAB-donor CU), or when the integrated access and backhaul node (IAB)
- the Integrated Access and Backhaul Node (IAB) sends the Congestion Report message if the predetermined condition of is satisfied.
- the request information includes the granularity of the congestion state information in the congestion report message, and/or the backhaul radio link control (BHRLC) channel identifier, and/or route identifier, and/or link identifier in the congestion state information.
- the request information further includes the interval period for sending the congestion report message, and/or the duration for sending the congestion report message in the period.
- the predetermined condition includes: the cache load corresponding to the granularity of the congestion state information in the congestion report message exceeds the first threshold and lasts for the first time period; or, within the second time period, the information about the same identifier (such as link ID, BH RLC channel ID, route ID), the number of backhaul adaptation protocol control protocol (BAP) sublayer flow control feedback sent back when the cache load exceeds the second threshold or the number of instances (instances) exceeds the third threshold threshold.
- the cache load corresponding to the granularity of the congestion state information in the congestion report message exceeds the first threshold and lasts for the first time period; or, within the second time period, the information about the same identifier (such as link ID, BH RLC channel ID, route ID), the number of backhaul adaptation protocol control protocol (BAP) sublayer flow control feedback sent back when the cache load exceeds the second threshold or the number of instances (instances) exceeds the third threshold threshold.
- BAP backhaul adaptation protocol control protocol
- the apparatus 1000 further includes:
- the second sending and receiving unit 1002 which receives the congestion reporting configuration information sent by the host central unit (IAB-donor CU).
- the congestion reporting configuration information is used to configure: the parameters required by the integrated access and backhaul node (IAB) in the predetermined conditions for judging the timing of sending the congestion reporting message, and/or the integrated access and The backhaul node (IAB) sends the parameters or configuration required for the congestion report message.
- the congestion reporting configuration information is received through F1 interface application protocol signaling.
- the congestion report message is carried in control plane signaling.
- the signaling of the control plane includes F1 interface application protocol signaling.
- the congestion report message can be carried in the F1AP signaling.
- an IAB procedure may be added in the F1 interface application protocol to send the congestion report message.
- the control plane signaling may also include RRC messages.
- the congestion report message can be carried in the F1AP; and for the load status of the uplink, the congestion report message is carried in the radio resource control (RRC) message.
- RRC radio resource control
- the second sending and receiving unit 1002 can also receive congestion reporting configuration information from the IAB-donor CU through dedicated signaling in a radio resource control (RRC) message, the configuration information being the same as the above, for example, for configuring: the integrated The parameters required in the predetermined conditions used by the access and backhaul node (IAB) for judging the timing of sending the congestion report message, and/or the parameters in which the integrated access and backhaul node (IAB) sends the congestion report message required parameters or configuration.
- RRC radio resource control
- the IAB sends a congestion report message for indicating the load state of the communication link to the IAB-donor CU, whereby the IAB-donor CU can perform control plane (CP)-based congestion mitigation Methods, for example, the IAB-donor CU can perform according to the congestion message: reconfigure routing, and/or backhaul radio link control (BH RLC) channel mapping, and/or resource reallocation, etc. This can alleviate long-term data congestion, reduce data loss, and optimize network performance.
- CP control plane
- BH RLC backhaul radio link control
- Embodiments of the present application provide a device for transmitting and receiving signals.
- the device may be, for example, a host central unit (IAB-donor CU), or may be one or some components or components configured in the host central unit (IAB-donor CU), for example, the host central unit (IAB-donor CU) is The IAB-donor CU 6 of Figure 4 or Figure 5.
- the signal sending and receiving apparatus corresponds to the signal sending and receiving method described in the embodiment of the second aspect.
- FIG. 11 is a schematic diagram of an apparatus for transmitting and receiving signals in an embodiment of the fourth aspect. As shown in FIG. 11 , the apparatus includes:
- the third sending and receiving unit 1101 receives a congestion report message sent by an integrated access and backhaul node (IAB), where the congestion report message is used to indicate the load status of the communication link of the integrated access and backhaul node .
- IAB integrated access and backhaul node
- the content of the congestion report message includes: buffer size (buffer size); and/or, buffer occupancy (buffer occupation); and/or, available buffer size (available buffer size); and/or, available data rate; and/or, information used to indicate that the communication link is congested.
- the third sending and receiving unit 1101 may also receive congestion clearance indication information sent by the integrated access and backhaul node, where the congestion clearance indication information is used to indicate that the communication link of the integrated access and backhaul node is non-congested state.
- the congestion report message may include an information element (IE, information element) that is used to carry a list of congestion status information.
- the granularity of the congestion status information is: per backhaul radio link control (BH RLC) channel, and/or per route ID, and/or per communication link.
- the congestion state information when the granularity of the congestion state information is each backhaul radio link control (BH RLC) channel or each communication link, the congestion state information also includes information for indicating the traffic direction (for example, uplink or downlink). link, egress or ingress) information.
- the congestion report message for the uplink has the same message format as the congestion report message for the downlink, for example, the format of the Congestion Information IE in the congestion report message is the same.
- the apparatus 1100 further includes:
- the fourth sending and receiving unit 1102 which sends polling information to the integrated access and backhaul node (IAB), wherein, in the case of sending the polling information, the integrated access is received and the congestion report message sent by the backhaul node (IAB).
- the request information includes the granularity of the congestion state information in the congestion report message, and/or the backhaul radio link control (BH RLC) channel identifier, and/or route identifier, and/or link identifier in the congestion state information road sign.
- the request information also includes the interval period for sending the congestion report message, and/or the duration for sending the congestion report message at the period.
- BH RLC backhaul radio link control
- the apparatus 1100 further includes:
- the congestion reporting configuration information is used to configure:
- the integrated access and backhaul node (IAB) is used to determine the parameters required in the predetermined conditions of the timing to send the congestion report message, and/or the integrated access and backhaul node (IAB) sends the congestion report Parameters or configuration required for the message.
- the congestion reporting configuration information can be sent through the F1 interface application protocol signaling or dedicated signaling in the RRC message.
- the congestion report message is carried in control plane signaling.
- the signaling of the control plane includes F1 interface application protocol signaling.
- the congestion report message can be carried in the F1AP signaling.
- an IAB procedure may be added in the F1 interface application protocol to send the congestion report message.
- the control plane signaling may also include RRC messages.
- the congestion report message can be carried in the F1AP; and for the load status of the uplink, the congestion report message is carried in the radio resource control (RRC) message.
- RRC radio resource control
- the fifth sending and receiving unit 1103 may also send congestion reporting configuration information to the integrated access and backhaul node (IAB) through dedicated signaling in a radio resource control (RRC) message, where the configuration information is the same as the above, For example, for configuring: the parameters required by the integrated access and backhaul node (IAB) in the predetermined conditions for judging the timing of sending the congestion report message, and/or the integrated access and backhaul node ( IAB) parameters or configuration required to send this congestion report message.
- RRC radio resource control
- the IAB sends the congestion report message for indicating the load status of the communication link to the IAB-donor CU, whereby the IAB-donor CU can perform control plane (CP)-based congestion mitigation Methods, for example, the IAB-donor CU can perform according to the congestion message: reconfigure routing, and/or backhaul radio link control (BH RLC) channel mapping, and/or resource reallocation, etc. This can alleviate long-term data congestion, reduce data loss, and optimize network performance.
- CP control plane
- BH RLC backhaul radio link control
- the signal sending apparatuses 1000 and 1100 only exemplarily show the connection relationship or signal direction between the various components or modules, but it should be clear to those skilled in the art that various bus connections, etc. can be used. related technologies.
- the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
- An embodiment of the present application further provides a communication system, and reference may be made to FIG. 1 , and the same content as the embodiments of the first aspect to the fourth aspect will not be repeated.
- the communication system may include:
- IAB-donor CU a host central unit comprising the signal transmitting and receiving apparatus 1100 according to the embodiment of the fourth aspect
- An integrated access and backhaul node comprising the signal transmission and reception apparatus 1000 according to the embodiment of the third aspect.
- the integrated access and backhaul node may include an IAB-MT functional unit and an IAB-DU functional unit.
- the IAB-MT functional unit may have the same structure as the terminal equipment.
- the IAB-DU functional unit and the host central unit (IAB-donor CU) may have the same units as the network equipment.
- FIG. 12 is a schematic structural diagram of a network device according to an embodiment of the present application.
- the network device 1200 may include: a processor 1210 (eg, a central processing unit CPU) and a memory 1220 ; the memory 1220 is coupled to the processor 1210 .
- the memory 1220 can store various data; in addition, the program 1230 for information processing is also stored, and the program 1230 is executed under the control of the processor 1210 .
- the processor 1210 may be configured to execute a program to implement the method performed by the IAB-DU in the embodiment of the first aspect or the IAB-donor CU in the embodiment of the second aspect.
- the network device 1200 may further include: a transceiver 1240, an antenna 1250, etc.; wherein, the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the network device 1200 does not necessarily include all the components shown in FIG. 12 ; in addition, the network device 1200 may also include components not shown in FIG. 12 , and reference may be made to the prior art.
- FIG. 13 is a schematic diagram of a terminal device according to an embodiment of the present application.
- the terminal device 1300 may include a processor 1310 and a memory 1320 ; the memory 1320 stores data and programs, and is coupled to the processor 1310 .
- this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
- the processor 1310 may be configured to execute a program to implement the method performed by the IAB-MT as described in the embodiments of the first aspect.
- the terminal device 1300 may further include: a communication module 1330 , an input unit 1340 , a display 1350 , and a power supply 1360 .
- the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the terminal device 1300 does not necessarily include all the components shown in FIG. 13 , and the above components are not required; in addition, the terminal device 1300 may also include components not shown in FIG. 13 . There is technology.
- the embodiment of the present application further provides a computer program, wherein when the program is executed in the IAB, the program causes the IAB to execute the method for sending and receiving signals according to the embodiment of the first aspect.
- the embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program causes the IAB to execute the method for sending and receiving signals according to the embodiment of the first aspect.
- the embodiment of the present application also provides a computer program, wherein when the program is executed in the IAB-donor CU, the program causes the IAB-donor CU to perform the method described in the embodiment of the second aspect.
- the embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program causes the IAB-donor CU to execute the method described in the embodiment of the second aspect.
- the apparatuses and methods above in the present application may be implemented by hardware, or may be implemented by hardware combined with software.
- the present application relates to a computer-readable program that, when executed by logic components, enables the logic components to implement the above-described apparatus or constituent components, or causes the logic components to implement the above-described various methods or steps.
- the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, and the like.
- the method/apparatus described in conjunction with the embodiments of this application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
- one or more of the functional block diagrams shown in the figures and/or one or more combinations of the functional block diagrams may correspond to either software modules or hardware modules of the computer program flow.
- These software modules may respectively correspond to the various steps shown in the figure.
- These hardware modules can be implemented by, for example, solidifying these software modules using a Field Programmable Gate Array (FPGA).
- FPGA Field Programmable Gate Array
- a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
- a storage medium can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
- the processor and storage medium may reside in an ASIC.
- the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
- the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
- the functional blocks and/or one or more combinations of the functional blocks described in the figures can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
- DSP digital signal processor
- ASICs Application Specific Integrated Circuits
- FPGAs Field Programmable Gate Arrays
- One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to the figures can also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors processor, one or more microprocessors in communication with the DSP, or any other such configuration.
- a method of transmitting and receiving a signal comprising:
- the integrated access and backhaul node sends a congestion report message to the home central unit (IAB-donor CU) of the integrated access and backhaul node, and the congestion report message is used to indicate the integrated access and backhaul node. Load status of the communication link of the incoming and backhaul nodes.
- the content of the congestion report message includes:
- the method also includes:
- the integrated access and backhaul node sends congestion clearance indication information to the host central unit (IAB-donor CU), where the congestion clearance indication information is used to indicate the communication chain of the integrated access and backhaul nodes
- the road is in a non-congested state.
- the congestion report message for the uplink has the same message format as the congestion report message for the downlink.
- the congestion report message includes an information element (IE, information element), which is used to carry a list of congestion state information,
- the granularity of the congestion status information is: per backhaul radio link control (BHRLC) channel, and/or per route ID, and/or per communication link.
- BHRLC backhaul radio link control
- the granularity of the congestion state information is in the case of each backhaul radio link control (BH RLC) channel or each communication link,
- the congestion state information also includes information for indicating the traffic direction.
- the integrated access and backhaul node (IAB) receives the polling information of the host central unit (IAB-donor CU), or when the integrated access and backhaul node (The integrated access and backhaul node (IAB) sends the congestion report message if the predetermined conditions of the IAB) are satisfied.
- the request information includes the granularity of the congestion state information in the congestion report message, and/or the backhaul radio link control (BH RLC) channel identifier in the congestion state information, and/or the routing identifier, and/or the link identifier. road sign.
- BH RLC backhaul radio link control
- the request information further includes the interval period for sending the congestion report message, and/or the duration for sending the congestion report message in the period.
- the predetermined conditions include:
- the cache load corresponding to the granularity of the congestion state information in the congestion report message exceeds the first threshold and lasts for the first time period;
- BAP backhaul adaptation protocol control protocol
- the method also includes:
- the integrated access and backhaul node receives the congestion reporting configuration information sent by the host central unit (IAB-donor CU), where the congestion reporting configuration information is used to configure:
- the congestion reporting configuration information is received through F1 interface application protocol signaling.
- the congestion report message is sent through F1 interface application protocol signaling.
- the congestion report message is sent in the IAB process newly added in the F1 interface application protocol.
- the congestion report message is carried in a radio resource control (RRC) message.
- RRC radio resource control
- the congestion reporting configuration information is received through dedicated signaling in the RRC message.
- a method of transmitting and receiving a signal comprising:
- the host central unit receives the congestion report message sent by the integrated access and backhaul node (IAB), the congestion report message is used to indicate the communication link of the integrated access and backhaul node. load status.
- the content of the congestion report message includes:
- the method also includes:
- the host central unit also receives the congestion clearance indication information sent by the integrated access and backhaul nodes, where the congestion clearance indication information is used to indicate the integrated access and backhaul nodes.
- the communication link is in a non-congested state.
- the congestion report message for the uplink has the same message format as the congestion report message for the downlink.
- the congestion report message includes an information element (IE, information element), which is used to carry a list of congestion state information,
- the granularity of the congestion status information is: per backhaul radio link control (BHRLC) channel, and/or per route ID, and/or per communication link.
- BHRLC backhaul radio link control
- the granularity of the congestion state information is in the case of each backhaul radio link control (BH RLC) channel or each communication link,
- the congestion status information also includes information for indicating uplink or downlink.
- the method also includes:
- the host central unit (IAB-donor CU) sends request (polling) information to the integrated access and backhaul node (IAB),
- the congestion report message sent by the integrated access and backhaul node (IAB) is received.
- the request information includes the granularity of the congestion state information in the congestion report message, and/or the backhaul radio link control (BHRLC) channel identifier in the congestion state information, and/or the routing identifier, and/or Link ID.
- BHRLC backhaul radio link control
- the request information further includes the interval period for sending the congestion report message, and/or the duration for sending the congestion report message in the period.
- the method also includes:
- the host central unit (IAB-donor CU) sends congestion reporting configuration information to the integrated access and backhaul node (IAB),
- the congestion reporting configuration information is used to configure:
- the parameters required by the integrated access and backhaul node (IAB) in the predetermined conditions for judging the timing of sending the congestion report message, and/or the integrated access and backhaul node (IAB) sends The parameters or configuration required for the congestion report message.
- the congestion reporting configuration information is sent through F1 interface application protocol signaling.
- the congestion report message is sent through F1 interface application protocol signaling.
- the congestion report message is sent in the IAB process newly added in the F1 interface application protocol.
- the congestion report message is carried in a radio resource control (RRC) message.
- RRC radio resource control
- the donor central unit (IAB-donor CU) sends congestion reporting configuration information to the integrated access and backhaul node (IAB) through dedicated signaling in a radio resource control (RRC) message.
- RRC radio resource control
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (20)
- 一种信号的发送和接收装置,应用于集成的接入和回传节点,包括:第一发送和接收单元,其向所述集成的接入和回传节点的宿主中心单元发送拥塞报告消息,所述拥塞报告消息用于指示所述集成的接入和回传节点的通信链路的负荷状态。
- 如权利要求1所述的装置,其中,所述拥塞报告消息的内容包括:缓存大小;和/或缓存占用率;和/或可用缓存大小;和/或可用数据速率;和/或用于表示所述通信链路发生拥塞的信息。
- 如权利要求1所述的装置,其中,所述第一发送和接收单元还向所述宿主中心单元发送拥塞清除指示信息,所述拥塞清除指示信息用于指示所述集成的接入和回传节点的通信链路为非拥塞状态。
- 如权利要求1所述的装置,其中,所述拥塞报告消息包括信息元素,所述信息元素用来携带拥塞状态信息的列表,所述拥塞状态信息的粒度为:每个回传无线链路控制信道,和/或每个路由ID,和/或每个通信链路。
- 如权利要求4所述的装置,其中,所述拥塞状态信息的粒度为每个回传无线链路控制信道或者每个通信链路的情况下,所述拥塞状态信息还包括用于指示业务方向的信息。
- 如权利要求1所述的装置,其中,在所述集成的接入和回传节点接收到所述宿主中心单元的请求信息的情况下,或者在所述集成的接入和回传节点的预定条件被满足的情况下,所述集成的接入和回传节点发送所述拥塞报告消息。
- 如权利要求6所述的装置,其中,所述请求信息包括所述拥塞报告消息中拥塞状态信息的粒度,和/或所述拥塞状态信息中的回传无线链路控制信道标识,和/或路由标识,和/或链路标识。
- 如权利要求6所述的装置,其中,所述预定条件包括:所述拥塞报告消息中拥塞状态信息的粒度对应的缓存负荷超过第一阈值,并持续了第一时间段;或者第二时间段内,所述集成的接入和回传节点的关于同一标识的缓存负荷超出第二阈值而发送的回传适应协议控制协议子层流量控制反馈的个数或实例的数量超出第三阈值。
- 如权利要求1所述的装置,其中,所述装置还包括:第二发送和接收单元,其接收所述宿主中心单元发送的拥塞上报配置信息,所述拥塞上报配置信息用于配置:所述集成的接入和回传节点用于判断发送所述拥塞报告消息的时机的预定条件中需要的参数,和/或所述集成的接入和回传节点发送所述拥塞报告消息所需的参数或配置。
- 如权利要求9所述的装置,其中,所述拥塞上报配置信息通过F1接口应用协议信令来接收。
- 如权利要求1所述的装置,其中,所述拥塞报告消息通过F1接口应用协议信令发送。
- 如权利要求11所述的装置,其中,在所述F1接口应用协议中新增的集成的接入和回传节点过程中发送所述拥塞报告消息。
- 如权利要求1所述的装置,其中,针对上行链路的负荷状态,所述拥塞报告消息被携带于无线资源控制消息中。
- 如权利要求9所述的装置,其中,所述拥塞上报配置信息通过RRC消息中的专用信令来接收。
- 一种信号的发送和接收装置,应用于宿主中心单元,包括:第三发送和接收单元,其接收集成的接入和回传节点发送的拥塞报告消息,所述拥塞报告消息用于指示所述集成的接入和回传节点的通信链路的负荷状态。
- 如权利要求15所述的装置,其中,所述拥塞报告消息的内容包括:缓存大小;和/或缓存占用率;和/或可用缓存大小;和/或可用数据速率;和/或用于表示所述通信链路发生拥塞的信息。
- 如权利要求15所述的装置,其中,所述拥塞报告消息包括信息元素,其用来携带拥塞状态信息的列表,所述拥塞状态信息的粒度为:每个回传无线链路控制信道,和/或每个路由ID,和/或每个通信链路。
- 如权利要求17所述的装置,其中,所述拥塞状态信息的粒度为每个回传无线链路控制信道或者每个通信链路的情况下,所述拥塞状态信息还包括用于指示上行链路或下行链路的信息。
- 如权利要求15所述的装置,其中,所述装置还包括:第四发送和接收单元,其向所述集成的接入和回传节点发送请求信息,其中,在发送了所述请求信息的情况下,接收所述集成的接入和回传节点发送的所述拥塞报告消息。
- 如权利要求15所述的装置,其中,所述装置还包括:第五发送和接收单元,其向所述集成的接入和回传节点发送拥塞上报配置信息,所述拥塞上报配置信息用于配置:所述集成的接入和回传节点用于判断发送所述拥塞报告消息的时机的预定条件中所需的参数,和/或所述集成的接入和回传节点发送所述拥塞报告消息所需的参数或配置。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202180088996.4A CN116686329A (zh) | 2021-01-13 | 2021-01-13 | 信号的发送和接收方法、装置和通信系统 |
JP2023540638A JP2024502582A (ja) | 2021-01-13 | 2021-01-13 | 信号の送受信方法、装置及び通信システム |
PCT/CN2021/071591 WO2022151095A1 (zh) | 2021-01-13 | 2021-01-13 | 信号的发送和接收方法、装置和通信系统 |
US18/218,628 US20230345344A1 (en) | 2021-01-13 | 2023-07-06 | Signal transmission and reception method and apparatus and communication system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2021/071591 WO2022151095A1 (zh) | 2021-01-13 | 2021-01-13 | 信号的发送和接收方法、装置和通信系统 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/218,628 Continuation US20230345344A1 (en) | 2021-01-13 | 2023-07-06 | Signal transmission and reception method and apparatus and communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022151095A1 true WO2022151095A1 (zh) | 2022-07-21 |
Family
ID=82446603
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/071591 WO2022151095A1 (zh) | 2021-01-13 | 2021-01-13 | 信号的发送和接收方法、装置和通信系统 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20230345344A1 (zh) |
JP (1) | JP2024502582A (zh) |
CN (1) | CN116686329A (zh) |
WO (1) | WO2022151095A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2024092671A1 (zh) * | 2022-11-03 | 2024-05-10 | 北京小米移动软件有限公司 | 一种拥塞通知方法、装置、设备及存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019190650A1 (en) * | 2018-03-26 | 2019-10-03 | Qualcomm Incorporated | Backpressure signaling for wireless communications |
CN110636548A (zh) * | 2019-09-30 | 2019-12-31 | 中兴通讯股份有限公司 | 一种流量控制方法、装置、节点和存储介质 |
CN110856222A (zh) * | 2018-08-20 | 2020-02-28 | 华为技术有限公司 | 一种流量控制的方法及装置 |
CN111586749A (zh) * | 2019-02-15 | 2020-08-25 | 华为技术有限公司 | 一种下行缓存状态反馈方法及装置 |
CN112771929A (zh) * | 2018-09-27 | 2021-05-07 | 联想(北京)有限公司 | 触发缓冲区状态报告 |
-
2021
- 2021-01-13 JP JP2023540638A patent/JP2024502582A/ja active Pending
- 2021-01-13 CN CN202180088996.4A patent/CN116686329A/zh active Pending
- 2021-01-13 WO PCT/CN2021/071591 patent/WO2022151095A1/zh active Application Filing
-
2023
- 2023-07-06 US US18/218,628 patent/US20230345344A1/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019190650A1 (en) * | 2018-03-26 | 2019-10-03 | Qualcomm Incorporated | Backpressure signaling for wireless communications |
CN110856222A (zh) * | 2018-08-20 | 2020-02-28 | 华为技术有限公司 | 一种流量控制的方法及装置 |
CN112771929A (zh) * | 2018-09-27 | 2021-05-07 | 联想(北京)有限公司 | 触发缓冲区状态报告 |
CN111586749A (zh) * | 2019-02-15 | 2020-08-25 | 华为技术有限公司 | 一种下行缓存状态反馈方法及装置 |
CN110636548A (zh) * | 2019-09-30 | 2019-12-31 | 中兴通讯股份有限公司 | 一种流量控制方法、装置、节点和存储介质 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2024092671A1 (zh) * | 2022-11-03 | 2024-05-10 | 北京小米移动软件有限公司 | 一种拥塞通知方法、装置、设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN116686329A (zh) | 2023-09-01 |
US20230345344A1 (en) | 2023-10-26 |
JP2024502582A (ja) | 2024-01-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210168656A1 (en) | Flow control method and apparatus | |
US11968565B2 (en) | User plane information reporting method and apparatus | |
WO2019157752A1 (zh) | 随机接入方法及装置 | |
US11510083B2 (en) | Method and apparatus for sending data volume report | |
WO2021031022A1 (zh) | 链路切换的方法和通信设备 | |
US20200351714A1 (en) | Communication Method for Deterministic Transmission and Related Apparatus | |
WO2018112871A1 (zh) | 数据发送/接收装置、方法以及通信系统 | |
US11259362B2 (en) | Method for repeatedly transmitting data and device | |
US20220124500A1 (en) | Communication method, terminal device and network device | |
WO2015081553A1 (zh) | 传输数据的方法、装置和系统 | |
WO2021056702A1 (zh) | 上行信号的发送和接收方法以及装置 | |
US20230247523A1 (en) | Routing selection method and apparatus and system | |
EP4262263A1 (en) | Rerouting method and apparatus, and communication device | |
US20230345344A1 (en) | Signal transmission and reception method and apparatus and communication system | |
CN116866981A (zh) | 通信方法和装置 | |
WO2022061872A1 (zh) | 一种小数据传输方法及装置、终端设备 | |
US20230216611A1 (en) | Packet loss indication method and related device | |
WO2020223907A1 (zh) | 一种信息传输方法及装置、网络设备 | |
WO2022151021A1 (zh) | 缓存状态上报的方法、缓存状态上报的配置方法及装置 | |
WO2022082543A1 (zh) | Iab节点的移植方法及装置 | |
WO2022151107A1 (zh) | 信号的发送和接收方法、装置和通信系统 | |
WO2018058474A1 (zh) | 一种数据发送方法和装置 | |
JP2023527821A (ja) | 通信ネットワークにおける、アプリケーション機能ノード、アクセスおよびモビリティ管理機能ノード、システムならびに方法 | |
WO2019191872A1 (zh) | 监听方法、参数配置方法以及装置、通信系统 | |
WO2022205485A1 (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: 21918310 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023540638 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180088996.4 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21918310 Country of ref document: EP Kind code of ref document: A1 |