WO2022022504A1 - 资源的分配方法及装置、网络侧设备和可读存储介质 - Google Patents

资源的分配方法及装置、网络侧设备和可读存储介质 Download PDF

Info

Publication number
WO2022022504A1
WO2022022504A1 PCT/CN2021/108649 CN2021108649W WO2022022504A1 WO 2022022504 A1 WO2022022504 A1 WO 2022022504A1 CN 2021108649 W CN2021108649 W CN 2021108649W WO 2022022504 A1 WO2022022504 A1 WO 2022022504A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
iab node
iab
report
threshold value
Prior art date
Application number
PCT/CN2021/108649
Other languages
English (en)
French (fr)
Inventor
文鸣
刘进华
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2022022504A1 publication Critical patent/WO2022022504A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/52Allocation or scheduling criteria for wireless resources based on load
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/12Avoiding congestion; Recovering from congestion
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/76Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/765Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management

Definitions

  • the present application belongs to the field of communication technologies, and in particular relates to a resource allocation method and apparatus, a network side device and a readable storage medium.
  • a node in the Integrated Access and Backhaul (IAB) network When a node in the Integrated Access and Backhaul (IAB) network has a congestion warning, it can be improved to a certain extent through the current flow control mechanism, such as reducing the data rate of the ingress link (input link) to reduce buffering.
  • the pressure of data although the pressure of buffering data is relieved in this way, it is at the expense of sacrificing the transmission data rate of the input link of the node, that is, sacrificing the service quality of the IAB network.
  • the purpose of the embodiments of the present application is to provide a resource allocation method and device, a network side device, and a readable storage medium, which can solve the problem of reducing the data rate of an input link by reducing the data rate of an input link through a flow control mechanism in the prior art when data congestion occurs in a node. , resulting in sacrificing the quality of service of the IAB network.
  • a method for allocating resources including: when a preset condition is met, a first IAB node sends a resource reallocation report to a second IAB node; the first IAB node receives the second IAB node The resource reallocation configuration message sent by the IAB node in response to the resource reallocation report.
  • a method for allocating resources including: a second IAB node receiving a resource reallocation report sent by a first IAB node; In the case that the node reallocates resources, the second IAB node sends a configuration message of resource reallocation to the first IAB node.
  • a resource allocation device including: a first sending module, configured to send a resource reallocation report to a second IAB node when a preset condition is met; a first receiving module, configured to receive The second IAB node sends a resource reallocation configuration message in response to the resource reallocation report.
  • a resource allocation device comprising: a second receiving module, configured to receive a resource reallocation report sent by a first IAB node; In the case of re-allocating resources by the first IAB node, a configuration message of resource re-allocation is sent to the first IAB node.
  • a network-side device in a fifth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the When executed by the processor, the steps of the method described in the first aspect or the steps of the method described in the second aspect are realized.
  • a readable storage medium on which a program or an instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps as described in the first aspect are implemented.
  • the steps of the method of the second aspect are provided, on which a program or an instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps as described in the first aspect are implemented.
  • a chip in a seventh aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or instruction, implementing the method as described in the first aspect. the method described, or implement the method described in the second aspect.
  • the first IAB node in the IAB network may send a resource reallocation report to the second IAB node when a preset condition is met, and then receive the resource reallocation report sent by the second IAB node in response to the resource reallocation report It can be seen that when the first IAB node is congested, resources can be reallocated to the first IAB node through the second IAB node.
  • the cache pressure of the first IAB node can be reduced without reducing the data transmission rate, which can not only ensure the link transmission data rate but also alleviate the node data congestion.
  • the IAB nodes in the IAB node perform partial or all resource redistribution, thereby solving the problem of sacrificing the service quality of the IAB network by reducing the data rate of the input link when the data congestion occurs in the node through the flow control mechanism in the prior art.
  • FIG. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application can be applied
  • FIG. 2 is a schematic structural diagram of an IAB system in an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a CU-DU in an IAB system according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a flow control mechanism adopted in an IAB network according to an embodiment of the present application.
  • FIG. 5 is a flowchart 1 of a resource allocation method according to an embodiment of the present application.
  • FIG. 6 is a second flowchart of a method for resource allocation according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a periodically triggered resource reallocation report according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of an event-triggered resource reallocation report according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a polling-based resource reallocation report according to an embodiment of the present application.
  • FIG. 10 is a first structural schematic diagram of an apparatus for allocating resources according to an embodiment of the present application.
  • FIG. 11 is a second schematic structural diagram of an apparatus for allocating resources according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a network side device 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 data 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 "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 NR terminology is used in most of the description below, although these techniques are also applicable to applications other than NR system applications, such as 6th generation ( 6th Generation , 6G) communication system.
  • 6th generation 6th Generation
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), PDA, Netbook, Ultra-mobile Personal Computer (UMPC), Mobile Internet Device (MID), Wearable Device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • MID Wearable Device
  • VUE vehicle-mounted device
  • PUE pedestrian terminal
  • wearable devices include: bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms.
  • the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • FIG. 2 is a schematic structural diagram of an IAB system in an embodiment of the present application.
  • an IAB node includes a DU (Distributed Unit) functional part and an MT (Mobile Termination) functional part.
  • DU Distribution Unit
  • MT Mobile Termination
  • an access point ie IAB node
  • an upstream access point namely parent IAB node (parent node) or IAB-donor-DU (IAB host distribution unit)
  • IAB-donor-DU IAB host distribution unit
  • a self-return loop consists of an IAB-donor node, which has a directly connected wired transmission network.
  • FIG. 3 is a schematic structural diagram of a CU-DU (Centralized Unit-Distributed Unit) in an IAB system according to an embodiment of the present application.
  • CU-DU Centralized Unit-Distributed Unit
  • FIG. 3 in a self-backhaul loop, DUs of all IAB nodes pass through the F1-AP signal.
  • the IAB-donor-CU configures the MT through the 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.
  • BAP Backhaul Adaptation Protocol
  • the protocol layer of BAP is a protocol layer unique to the IAB network.
  • the BAP entity in each IAB node has an address, called BAP address, which can be used to route data in combination with the PATH ID assigned by IAB-donor-CU.
  • the protocol layer provides some functions as follows:
  • Routing function 1 send the data packet from the CU to the UE through the return channel or send the data packet from the UE to the CU through the return channel;
  • BAP protocol also provides the routing function of F1-AP information, sending F1 control information from CU to IAB-DU through the return channel or sending F1 control information from IAB-DU to CU through the return channel;
  • the transmission function of quality of service (Quality of Service, QoS) control information the BAP protocol layer defines some backhaul adaptation protocol control protocol data units (BAP Control Protocol Data Unit, BAP Control PDU) used in the IAB network, which is used to Do flow control, return the notification of wireless link failure, etc.
  • BAP Control Protocol Data Unit BAP Control PDU
  • IAB hop-by-hop and end-to-end flow control.
  • 3GPP RAN2 agrees to adopt a flow control mechanism in the IAB network to solve the data congestion during downlink transmission (The DL hop-by-hop flow control is supported in IAB network.)
  • the data received by the parent IAB node is too late to be sent to the downstream node or UE, resulting in data accumulation.
  • the data accumulates that is, when the data accumulates to the risk of buffer overflow, it will send a flow control feedback to its parent node (congested IAB node feedback flow control info to its parent IAB node) to warn of congestion, the IAB node that receives the flow control feedback will control the transmission rate of downlink data sent to the child IAB node.
  • the IAB-donor node can send downlink data to the UE through IAB node 1, IAB node 2 and IAB node 3. Once the backhaul link between IAB node 2 and IAB node 3 encounters the link Congestion, then IAB node 2 will send flow control message to its upstream node, that is, IAB node 1. After IAB node 1 receives the message, it will stop or reduce sending new downlink data to IAB node 2.
  • 3GPP RAN3 agrees to reuse the current downlink data delivery status (DDDS).
  • DDDS current downlink data delivery status
  • the purpose of the DDDS procedure is to provide feedback from the corresponding node to the node carrying the NR PDCP entity to allow the node carrying the NR PDCP entity to control the downlink user data flow through the node carrying the corresponding data radio bearer.
  • the corresponding node may also transmit the uplink user data for the relevant data radio bearer to the node of the NR PDCP entity together with the DDDS frame in the same GTP-U PDU.
  • FIG. 5 is a flowchart of a resource allocation method according to an embodiment of the present application. As shown in FIG. 5 , the steps of the method include:
  • Step S502 in the case that the preset conditions are met, the first IAB node sends a resource reallocation report to the second IAB node;
  • the types of the first IAB node and the second IAB node in the embodiment of the present application include one of the following: a common IAB node, an IAB host centralized unit IAB-donor-CU, and an IAB host Distribution unit IAB-donor-DU. That is to say, the first IAB node can be one of a common IAB node, IAB host centralized unit IAB-donor-CU, IAB host distribution unit IAB-donor-DU, and the second IAB node can also be a common IAB node, IAB One of the host centralized unit IAB-donor-CU and the IAB host distribution unit IAB-donor-DU.
  • the common IAB node in the implementation of this application may be a node other than the IAB-donor-CU and IAB-donor-DU in the IAB network, for example, the IAB1 and IAB2 nodes in FIG. 3 .
  • Step S504 the first IAB node receives the resource reallocation configuration message sent by the second IAB node in response to the resource reallocation report.
  • the first IAB node in the IAB network can send a resource reallocation report to the second IAB node when the preset conditions are met, and then receive the resources sent by the second IAB node in response to the resource reallocation report.
  • the redistributed configuration message is used to reallocate resources; it can be seen that when the first IAB node is congested, resources can be redistributed to the first IAB node through the second IAB node.
  • the cache pressure of the first IAB node can be reduced without reducing the data transmission rate, which can not only ensure the link transmission data rate but also alleviate node data congestion.
  • the IAB nodes in the IAB network perform partial or total resource redistribution, which solves the problem of sacrificing the quality of service of the IAB network by reducing the data rate of the input link through the flow control mechanism in the prior art when data congestion occurs in the node. problem.
  • the preset condition in the present application may include at least one of the following: an event trigger condition, a periodic trigger condition, and a polling trigger condition.
  • the periodic trigger condition in the embodiment of the present application refers to the timeout of the second timer set to be periodically triggered.
  • the event triggering condition may include at least one of the following:
  • the cached data of the first IAB node exceeds the first threshold value or is lower than the second threshold value; wherein, the first threshold value is greater than the second threshold value;
  • the cached data may be cached data in the cache of the first IAB node.
  • the data transmission rate of the first IAB node is higher than the third threshold value or lower than the fourth threshold value; wherein, the third threshold value is greater than the fourth threshold value;
  • the usage number or usage rate of the time-frequency resources of the first IAB node exceeds the fifth threshold value or is lower than the sixth threshold value; wherein, the fifth threshold value is greater than the sixth threshold value.
  • the event triggering condition 1) if the buffered data in the buffer of the first IAB node exceeds the first threshold, it means that the current first IAB node may be congested, and other non-congested ones need to be
  • the resources of the node are adjusted to the first IAB to relieve congestion, or the buffered data in the buffer is lower than the second threshold value, it means that the resources of the current first IAB node are surplus. Therefore, the surplus resources of the first IAB node can be used. Scheduled to other congested nodes. Other event triggering conditions are also similar processing processes, which are not repeated here.
  • the time-frequency resource usage number of the first IAB node in the above event trigger condition 3) includes the time-frequency resource usage number or the time-frequency resource usage rate of the DU of the first IAB node, wherein the DU of the first IAB node.
  • the time-frequency resource usage rate of the DU includes at least one of the following: the uplink time-frequency resource usage rate of the DU, the downlink time-frequency resource usage rate of the DU, the hard uplink time-frequency resource usage rate of the DU, the hard downlink time-frequency resource usage rate of the DU, Soft uplink time-frequency resource usage rate of DU and Soft downlink time-frequency resource usage rate of DU.
  • the method of this embodiment of the present application may further include:
  • Step S11 the first IAB node starts the first timer after sending the resource reallocation report to the second IAB node;
  • Step S12 in the case that the first timer does not expire, the first IAB node prohibits sending the resource reallocation report again;
  • Step S13 when the first timer expires and the event trigger condition is satisfied, the first IAB node sends the resource reallocation report again.
  • the first IAB node can repeatedly send the resource reallocation report when the timer expires, so as to ensure that the second IAB node can receive the resource reallocation report.
  • the first threshold value, the second threshold value, the third threshold value, the fourth threshold value, the fifth threshold value, the sixth threshold value, and the first threshold value is pre-defined by the protocol or pre-configured by the network.
  • the way of pre-defining the protocol or pre-configuring the network may be configured by the IAB-donor-CU through RRC or F1-AP signaling in a specific application scenario.
  • the polling trigger condition in this embodiment of the present application is that the first IAB node receives the polling message sent by the second IAB node.
  • the process of sending the polling message may be that the IAB-donor-CU sends a message to the ordinary IAB through RRC and/or F1AP signaling.
  • the IAB node sends a polling message, and when the common IAB node receives the message, it generates a resource reallocation report and sends it to the IAB-donor-CU;
  • IAB1 IAB node
  • BAP control PDU or MAC CE BAP control PDU or MAC CE
  • the child IAB node receives the message, it generates a report and sends it to IAB1.
  • the IAB1 corresponds to the second IAB node in this application
  • its child IAB node corresponds to the first IAB node in this application.
  • the polling message may be sent by the second IAB node through at least one of the following: a radio resource control RRC message, an F1 application protocol F1-AP signaling, and a backhaul adaptation protocol Control protocol data unit BAP control PDU, medium access control unit MAC CE.
  • the method steps of the present application may further include:
  • Step S21 the first IAB node receives the polling message sent again by the second IAB node; wherein the condition for triggering the second IAB node to send the polling message again is that the third timer expires and the resource reallocation report is not received.
  • the resource reallocation report in this embodiment of the present application may include at least one of the following: an identifier of the first IAB node, an identifier of the second IAB node, a resource usage rate counted by a multiplexing method of time-frequency resources, a The resource usage rate of the type statistics, the resource request of the first IAB node.
  • the resource usage rate counted according to the multiplexing method of time-frequency resources includes at least one of the following: the resource ratio of time division multiplexing TDM scheduling, the resource ratio of space division multiplexing SDM scheduling, and the resource ratio of frequency division multiplexing FDM scheduling.
  • the resource usage statistics by resource type include at least one of the following: the number of hard downlink time-frequency resources, the utilization rate of hard downlink resources, the number of hard uplink time-frequency resources, the utilization rate of hard uplink resources, the number of hard flexible time-frequency resources, the number of hard Flexible resource utilization, number of soft downlink time-frequency resources, soft downlink resource utilization, number of soft uplink time-frequency resources, soft uplink resource utilization, number of soft flexible time-frequency resources, soft flexible resource utilization, total resource utilization.
  • the resource request of the first IAB node includes at least one of the following: the type of the requested resource, the quantity of the requested resource, and the multiplexing scheduling mode.
  • the quantity of the requested resources is the quantity of resources to be added in a unit time.
  • the first IAB node sends a resource reallocation report to the second IAB node through a message of at least one of the following: RRC message, F1-AP signaling, BAP control PDU.
  • the RRC message includes at least one of the following:
  • User terminal assistance information UEAssistanceInformation wherein the user terminal assistance information includes a first field, and the first field is used for reporting resource usage and/or making resource requests;
  • the UEAssistanceInformation is used by the IAB-MT to request the network to assign an IP address to the IAB node or to notify the network of the IP address assigned to the IAB-DU.
  • Self-returning other information IABOtherInformation wherein the self-returning other information includes a second field, and the second field is used for reporting resource usage and/or making resource requests.
  • IABOtherInformation is used to indicate UE assistance information to the network.
  • the F1-AP includes: a downlink data transmission status report, wherein a third field is newly added to the downlink data transmission status report, and the third field is used for reporting resource usage and/or making resource requests.
  • the delivery manner of the resource reallocation report carried by the BAP control PDU includes at least one of the following:
  • the resource reallocation report sent by the first IAB node of the bearer is delivered to the parent IAB node of the first IAB node through the BAP control PDU, and the inter-layer interaction is performed in the parent IAB node, and is indicated to the RRC by the BAP layer of the parent IAB node. layer or F1AP layer and generate a new message for delivery to the IAB-donor-CU;
  • the resource reallocation report sent by the first IAB node of the bearer is delivered to the IAB-donor-DU node through the BAP control PDU, and the inter-layer interaction is performed in the IAB-donor-DU, and the BAP layer of the IAB-donor-DU Indicated to the F1AP layer, and a new message is generated by the F1AP layer and passed to the IAB-donor-CU.
  • the method steps of the embodiment of the present application may further include:
  • Step S506 start a third timer
  • Step S508 when the third timer times out and the configuration message is not received, the first IAB node executes the flow control mechanism.
  • the flow control mechanism can be used to relieve the pressure on the IAB node.
  • FIG. 6 is a flowchart of the method for resource allocation according to an embodiment of the present application.
  • Fig. 2, as shown in Fig. 6, the method steps of the embodiment of the present application may further include:
  • Step S602 the second IAB node receives the resource reallocation report sent by the first IAB node
  • Step S604 when the second IAB node determines to reallocate resources to the first IAB node according to the current resource allocation state, the second IAB node sends a configuration message of resource reallocation to the first IAB node.
  • the method steps in the embodiments of the present application may further include:
  • Step S606 the second IAB node sends configuration parameters corresponding to the resource reallocation report to the first IAB node accessing the IAB network.
  • the configuration parameters include at least one of the following: threshold value of buffered data, threshold value of output connection and/or data transmission rate of output connection, threshold value of time-frequency resource usage number/usage rate, timer, resource usage.
  • the second IAB node can determine whether to reallocate resources for the first IAB node according to the current resource allocation state, that is, the resources of the IAB nodes in the IAB network can be partially allocated. Or global adjustment, thereby solving the problem of sacrificing the service quality of the IAB network by reducing the data rate of the input link when the node is congested by the flow control mechanism in the prior art.
  • the IAB-donor-CU configures the MT of the access node with the relevant parameters of the resource reallocation report through RRC signaling; or through the F1-AP signaling for The DU of the access node configures the relevant parameters for the resource reallocation report.
  • the related parameters configured include: high/low thresholds (corresponding to the above-mentioned first to sixth thresholds), periodic trigger timers, statistics of resource usage rates that need to be carried in the report, and the like.
  • FIG. 7 is a schematic diagram of a periodically triggered resource reassignment report according to an embodiment of the present application. Taking the IAB2 in FIG. 7 as the first IAB node and the IAB-donor-CU as the second IAB node as an example, the periodically triggered resource reassignment report
  • the method steps for assigning a report include:
  • Step S702 after the IAB2 access is completed, a periodic trigger timer is started, and a resource reassignment report is generated when the timer expires;
  • Step S704 sending the generated report to the IAB-donor-CU through an RRC message (such as IABOtherInformation);
  • Step S706 after receiving the report, the IAB-donor-CU decides whether to reallocate resources for the IAB 2-DU according to the current resource allocation situation.
  • the IAB-donor-CU sends the gNB-DU Resource Configuration to the IAB2-DU through the F1-AP signaling; the IAB2-DU configures it according to the reallocated resources in the message after receiving it, and replies to the GNB- DU RESOURCE CONFIGURATION ACKNOWLEDGE (GNB-DU resource configuration response) to IAB-donor-CU.
  • the IAB-donor-CU will not take any action.
  • the IAB-donor-CU configures the MT of the access node with the relevant parameters of the resource reallocation report through RRC signaling; or through the F1-AP signaling for The DU of the access node configures the relevant parameters for the resource reallocation report.
  • the related parameters configured include: high/low thresholds, periodic trigger timers, and statistics of resource usage rates that need to be carried in the report.
  • FIG. 8 is a schematic diagram of an event-triggered resource reallocation report according to an embodiment of the present application.
  • IAB2 in FIG. 8 as the first IAB node
  • IAB-donor-CU as the second IAB node
  • the method steps of the event-triggered resource reallocation report include:
  • step S802 the cached data in the buffer of IAB 2 exceeds a predetermined threshold, triggering the generation of a resource reallocation report, and simultaneously enabling the prohibit timer.
  • Step S804 send the generated report to the IAB-donor-CU through an RRC message (IABOtherInformation), and start the resource reassignment timer;
  • Step S806 after receiving the report, the IAB-donor-CU decides whether to allocate more resources for the IAB 2-DU to schedule the IAB2-MT according to the current resource allocation, so as to improve the data rate of the egress link so that it can match the ingress link data rate, thereby reducing the amount of data cached in the IAB 2 node.
  • IAB-donor-CU sends gNB-DU Resource Configuration to IAB2-DU through F1AP signaling; IAB2-DU configures it according to the reallocated resources in the message after receiving it, and replies to GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE to IAB-donor-CU.
  • IAB-donor-CU will not take any measures.
  • IAB 2 adopts the mechanism of flow control to reduce the data rate of the ingress link.
  • the IAB-donor-CU configures the MT of the access node with the relevant parameters of the resource reallocation report through RRC signaling; or through the F1-AP signaling for The DU of the access node configures the relevant parameters for the resource reallocation report.
  • the related parameters configured include: high/low thresholds, periodic trigger timers, resource usage statistics that need to be carried in the report, and the like.
  • FIG. 9 is a schematic diagram of a polling-based resource reallocation report according to an embodiment of the present application. Taking IAB2 in FIG. 9 as the first IAB node and IAB-donor-CU as the second IAB node, the polling-based resource reallocation is an example.
  • the method steps for reporting include:
  • Step S902 the IAB-donor-CU sends a polling message (polling message) to the IAB node through RRC or F1AP signaling, and starts the polling reply message timer, if the timer expires and still does not receive the resource reallocation returned by IAB2 report, the polling message is sent again.
  • a polling message (polling message)
  • Step S904 the IAB2 node generates a report after receiving the message, and sends it to the IAB-donor-CU through an RRC message (UEAssistanceInformation);
  • Step S906 after receiving the report, the IAB-donor-CU decides whether to reallocate resources for the IAB 2-DU according to the current resource allocation situation.
  • IAB-donor-CU sends gNB-DU Resource Configuration to IAB2-DU through F1AP signaling; IAB2-DU configures it according to the reallocated resources in the message after receiving it, and replies to GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE to IAB-donor-CU;
  • the IAB-donor-CU will not take any action.
  • the resource reassignment report can enable the IAB network to know the resource usage of an IAB node in time, so as to reassign time-frequency resources locally or as a whole, without reducing the data transmission rate. On the premise, reduce the cache pressure of the IAB node.
  • the execution subject may be a resource allocation apparatus, or a control module in the resource allocation apparatus for executing the resource allocation method.
  • the resource allocating apparatus provided by the embodiment of the present application is described by taking the resource allocating apparatus for performing the resource allocating method as an example.
  • FIG. 10 is a schematic structural diagram 1 of an apparatus for allocating resources according to an embodiment of the present application. As shown in FIG. 10 , the apparatus includes:
  • a first sending module 1002 configured to send a resource reallocation report to the second IAB node when a preset condition is met;
  • the first receiving module 1004 is configured to receive a configuration message of resource reallocation sent by the second IAB node in response to the resource reallocation report.
  • the preset condition includes at least one of the following: an event trigger condition, a periodic trigger condition, and a polling trigger condition.
  • the event triggering condition includes at least one of the following: the buffered data of the first IAB node exceeds the first threshold value or is lower than the second threshold value; wherein, the first threshold value is greater than the second threshold value; The data transmission rate of an IAB node is higher than the third threshold value or lower than the fourth threshold value; wherein, the third threshold value is greater than the fourth threshold value; the usage number or usage rate of time-frequency resources of the first IAB node Exceeds the fifth threshold value or is lower than the sixth threshold value; wherein, the fifth threshold value is greater than the sixth threshold value.
  • the time-frequency resource usage number of the first IAB node includes the time-frequency resource usage number or the time-frequency resource usage rate of the DU of the first IAB node, wherein the time-frequency resource usage rate of the DU of the first IAB node includes the following: At least one item: DU uplink time-frequency resource usage rate, DU downlink time-frequency resource usage rate, DU hard uplink time-frequency resource usage rate, DU hard downlink time-frequency resource usage rate, DU soft uplink time-frequency resource usage rate rate, and the soft downlink time-frequency resource usage rate of the DU.
  • the apparatus in this embodiment of the present application further includes: a first starting module, configured to start the first IAB node after sending the resource reallocation report to the second IAB node. a first timer; a prohibition module, used for prohibiting re-sending a resource reallocation report when the first timer does not expire; a second sending module, used when the first timer times out and the event trigger condition is met Next, send the resource reallocation report again.
  • the first threshold value, the second threshold value, the third threshold value, the fourth threshold value, the fifth threshold value, the sixth threshold value, and the duration of the first timer are preset by the protocol. Defined or pre-configured by the network.
  • the periodic triggering condition refers to the timeout of the second timer set to be periodically triggered.
  • the polling trigger condition is that the first IAB node receives a polling message sent by the second IAB node.
  • the polling message is sent by the second IAB node through at least one of the following: radio resource control RRC message, F1 application protocol F1-AP signaling, backhaul adaptation protocol control protocol data unit BAP control PDU, medium Access Control Unit MAC CE.
  • the apparatus in this embodiment of the present application may further include: a second receiving module, configured to receive a polling message sent again by the second IAB node; wherein the condition for triggering the second IAB node to send the polling message again is the third The timer expired and no resource reallocation report was received.
  • a second receiving module configured to receive a polling message sent again by the second IAB node; wherein the condition for triggering the second IAB node to send the polling message again is the third The timer expired and no resource reallocation report was received.
  • the resource reassignment report includes at least one of the following: the identifier of the first IAB node, the identifier of the second IAB node, the resource usage statistics based on the multiplexing method of time-frequency resources, the resource usage statistics based on resource types, The resource request of the first IAB node.
  • the resource usage ratio calculated according to the multiplexing method of time-frequency resources includes at least one of the following: the resource ratio of time division multiplexing TDM scheduling, the resource ratio of space division multiplexing SDM scheduling, and the resource ratio of frequency division multiplexing FDM scheduling. .
  • the resource usage statistics by resource type include at least one of the following: the number of hard downlink time-frequency resources, the utilization rate of hard downlink resources, the number of hard uplink time-frequency resources, the utilization rate of hard uplink resources, and the number of hard flexible time-frequency resources. , Hard elastic resource utilization, Soft downlink time-frequency resources, Soft downlink resource utilization, Soft uplink time-frequency resources, Soft uplink resource utilization, Soft flexible time-frequency resources, Soft elastic resource utilization, Total resource utilization .
  • the resource request of the first IAB node includes at least one of the following: the type of the requested resource, the quantity of the requested resource, and the multiplexing scheduling mode.
  • the quantity of requested resources is the quantity of resources to be added per unit time.
  • the first IAB node sends a resource reallocation report to the second IAB node through at least one of the following messages: RRC message, F1-AP signaling, BAP control PDU.
  • the RRC message includes at least one of the following:
  • User terminal assistance information wherein the user terminal assistance information includes a first field, and the first field is used for reporting resource usage and/or making resource requests;
  • Self-returning other information wherein the self-returning other information includes a second field, and the second field is used for reporting resource usage and/or making resource requests.
  • the F1-AP signaling includes: a downlink data transmission status report, wherein a third field is newly added to the downlink data transmission status report, and the third field is used for reporting resource usage and/or making resource requests.
  • the types of the first IAB node and the second IAB node include one of the following: a common IAB node, an IAB host centralized unit IAB-donor-CU, and an IAB host distribution unit IAB-donor-DU.
  • the delivery method of the resource reallocation report carried by the BAP control PDU includes at least one of the following:
  • the resource reallocation report sent by the first IAB node carried by the BAP control PDU is delivered to the parent IAB node of the first IAB node, and the inter-layer interaction is performed in the parent IAB node.
  • the BAP layer of the parent IAB node indicates to the RRC layer or F1AP layer, and generate a new message to IAB-donor-CU;
  • the resource reallocation report sent by the first IAB node of the bearer is delivered to the IAB-donor-DU node through the BAP control PDU, and the inter-layer interaction is carried out in the IAB-donor-DU, and is indicated by the BAP layer of the IAB-donor-DU to the IAB-donor-DU.
  • the F1AP layer, and a new message is generated by the F1AP layer and passed to the IAB-donor-CU.
  • the apparatus in this embodiment of the present application may further include: a second starting module, configured to start a third timer; an execution module, configured to In the case that the third timer expires and the configuration message is not received, the flow control mechanism is executed.
  • FIG. 11 is a second schematic structural diagram of an apparatus for allocating resources according to an embodiment of the present application. As shown in FIG. 11 , the apparatus includes:
  • a second receiving module 1102 configured to receive a resource reallocation report sent by the first IAB node
  • the second sending module 1104 is configured to send a configuration message of resource reallocation to the first IAB node when it is determined according to the current resource allocation state to reallocate resources to the first IAB node.
  • the apparatus in this embodiment of the present application may further include: a third sending module, configured to send configuration parameters corresponding to the resource reallocation report to the first IAB node accessing the IAB network.
  • the configuration parameters include at least one of the following: threshold value of buffered data, threshold value of output connection and/or data transmission rate of output connection, threshold value of time-frequency resource usage number/usage rate, timer, resource usage.
  • the first IAB node in the IAB network can send a resource reallocation report to the second IAB node when the preset conditions are met, and then receive the resource reallocation report sent by the second IAB node in response to the resource reallocation report.
  • configuration message to reallocate resources it can be seen that when the first IAB node is congested, resources can be reallocated to the first IAB node through the second IAB node, for example, the node resources without congestion are allocated to the first IAB node
  • the cache pressure of the first IAB node can be reduced on the premise of not reducing the data transmission rate, which can not only ensure the link transmission data rate but also alleviate node data congestion.
  • the IAB node performs partial or all resource redistribution, thereby solving the problem of sacrificing the service quality of the IAB network by reducing the data rate of the input link when the node is congested by the flow control mechanism in the prior art.
  • the apparatus for allocating resources in this embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal.
  • the 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 (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 apparatus for allocating resources in this embodiment of the present application may be an apparatus having an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the resource allocation apparatus provided in this embodiment of the present application can implement each process implemented by the method embodiments in FIG. 5 to FIG. 6 , 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 1200, including a processor 1201, a memory 1202, a program or instruction stored in the memory 1202 and executable on the processor 1201,
  • a communication device 1200 including a processor 1201, a memory 1202, a program or instruction stored in the memory 1202 and executable on the processor 1201,
  • the communication device 1200 is a terminal
  • the program or instruction is executed by the processor 1201
  • each process of the foregoing resource allocation method embodiment is implemented, and the same technical effect can be achieved.
  • the communication device 1200 is a network side device, when the program or instruction is executed by the processor 1201, each process of the foregoing resource allocation method embodiments can be implemented, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • the network device 1300 includes: an antenna 131 , a radio frequency device 132 , and a baseband device 133 .
  • the antenna 131 is connected to the radio frequency device 132 .
  • the radio frequency device 132 receives information through the antenna 131, and sends the received information to the baseband device 133 for processing.
  • the baseband device 133 processes the information to be sent and sends it to the radio frequency device 132
  • the radio frequency device 132 processes the received information and sends it out through the antenna 131 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 133 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 133 .
  • the baseband apparatus 133 includes a processor 134 and a memory 135 .
  • the baseband device 133 may include, for example, at least one baseband board on which a plurality of chips are arranged, as shown in FIG. 13 , one of the chips is, for example, the processor 134 , which is connected to the memory 135 to call the program in the memory 135 to execute
  • the network devices shown in the above method embodiments operate.
  • the baseband device 133 may further include a network interface 136 for exchanging information with the radio frequency device 132, and the interface is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network-side device in the embodiment of the present invention further includes: an instruction or program stored in the memory 135 and executable on the processor 134 , and the processor 134 invokes the instruction or program in the memory 135 to execute the instructions or programs shown in FIG. 11 or 12 .
  • the method executed by each module achieves the same technical effect. To avoid repetition, it is not repeated here.
  • Embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the foregoing resource allocation method embodiment is implemented, and can achieve The same technical effect, in order to avoid repetition, will not be repeated here.
  • 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 used for running network-side device programs or instructions to realize the above resource allocation
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used for running network-side device programs or instructions to realize the above resource allocation
  • 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节点向第二IAB节点发送资源重分配报告;所述第一IAB节点接收所述第二IAB节点响应于所述资源重分配报告发送的资源重分配的配置消息。

Description

资源的分配方法及装置、网络侧设备和可读存储介质
相关申请的交叉引用
本申请主张在2020年7月28日在中国提交的中国专利申请号No.202010739844.3的优先权,其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域,具体涉及一种资源的分配方法及装置、网络侧设备和可读存储介质。
背景技术
当自回传(Integrated Access and Backhaul,IAB)网络中某节点出现拥塞预警时,可以通过目前的流控机制进行一定程度的改善,如通过降低ingress link(输入链路)的数据率以减轻缓存数据的压力,通过这种方式虽然减轻了缓存数据的压力,却是以牺牲节点输入链路传输数据率为代价,即牺牲了IAB网络的服务质量。
发明内容
本申请实施例的目的是提供一种资源的分配方法及装置、网络侧设备和可读存储介质,能够解决现有技术中通过流控机制在节点出现数据拥塞时通过降低输入链路的数据率,导致牺牲了IAB网络的服务质量的问题。
为了解决上述技术问题,本申请是这样实现的:
第一方面,提供了一种资源的分配方法,包括:在满足预设条件的情况下,第一IAB节点向第二IAB节点发送资源重分配报告;所述第一IAB节点接收所述第二IAB节点响应于所述资源重分配报告发送的资源重分配的配置消息。
第二方面,提供了一种资源的分配方法,包括:第二IAB节点接收第一IAB节点发送的资源重分配报告;在所述第二IAB节点根据当前资源分配状态确定为所述第一IAB节点重新分配资源的情况下,所述第二IAB节点向所 述第一IAB节点发送资源重分配的配置消息。
第三方面,提供了一种资源的分配装置,包括:第一发送模块,用于在满足预设条件的情况下,向第二IAB节点发送资源重分配报告;第一接收模块,用于接收所述第二IAB节点响应于所述资源重分配报告发送的资源重分配的配置消息。
第四方面,提供了一种资源的分配装置,包括:第二接收模块,用于接收第一IAB节点发送的资源重分配报告;第二发送模块,用于在根据当前资源分配状态确定为所述第一IAB节点重新分配资源的情况下,向所述第一IAB节点发送资源重分配的配置消息。
第五方面,提供了一种网络侧设备,该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤,或者实现如第二方面所述的方法的步骤。
第六方面,提供了一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤,或者实现如第二方面所述的方法的步骤。
第七方面,提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行网络侧设备程序或指令,实现如第一方面所述的方法,或实现如第二方面所述的方法。
在本申请实施例中,IAB网络中的第一IAB节点在满足预设条件时可以向第二IAB节点发送资源重分配报告,进而接收第二IAB节点响应于资源重分配报告发送的资源重分配的配置消息,进行资源的重分配;可见,在第一IAB节点出现拥塞时,可以通过第二IAB节点对第一IAB节点进行资源重分配,例如,把没有出现拥塞的节点资源分配到第一IAB节点处,使得在不降低数据传输率的前提下减少第一IAB节点的缓存压力,既可以保证链路传输数据率又能缓解节点数据拥塞,也就是说,在本申请中是对IAB网络中的IAB节点进行局部或全部的资源重分配,从而解决了现有技术中通过流控机制在节点出现数据拥塞时通过降低输入链路的数据率,导致牺牲了IAB网络的服务质量的问题。
附图说明
图1示出本申请实施例可应用的一种无线通信系统的框图;
图2是本申请实施例中IAB系统的结构示意图;
图3是本申请实施例的IAB系统中CU-DU结构示意图;
图4是本申请实施例的在IAB网络中采用流控机制的示意图;
图5是本申请实施例的资源的分配方法流程图一;
图6是本申请实施例的资源分配的方法流程图二;
图7是本申请实施例的周期性触发的资源重分配报告示意图;
图8是本申请实施例的事件触发的资源重分配报告示意图;
图9是本申请实施例的基于轮询的资源重分配报告示意图;
图10是本申请实施例的资源的分配装置的结构示意图一;
图11是本申请实施例的资源的分配装置的结构示意图二;
图12是本申请实施例的通信设备的结构示意图;
图13是本申请实施例的网络侧设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施,且“第一”、“第二”所区别的对象通常为一类,并不限定对象的个数,例如第一对象可以是一个,也可以是多个。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是,本申请实施例所描述的技术不限于长期演进型(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)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中,终端11也可以称作终端设备或者用户终端(User Equipment,UE),终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant,PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer,UMPC)、移动上网装置(Mobile Internet Device,MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备,可穿戴式设备包括:手环、耳机、眼镜等。需要说明的是,在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网,其中,基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point,TRP)或所述领域中其他某个合适的术语,只要达到相同的技术效果,所述基站不限于特定技术词汇,需要说明的是,在本申请实施例中仅以NR系统中的基站为例,但是并不限定基站的具体类型。
基于图1所示的无线通信系统,本申请具体涉及到的是自回传(Integrated Access and Backhaul,IAB)系统。图2是本申请实施例中IAB系统的结构示 意图,如图2所示,一个IAB节点包括DU(Distributed Unit)功能部分和MT(Mobile Termination)功能部分。依靠MT,一个接入点(即IAB node)可以找到一个上游接入点,即parent IAB node(父节点)或者IAB-donor-DU(IAB宿主分布单元),并跟上游接入点的DU建立无线连接,该无线连接被称为backhaul link(回传链路)。在一个IAB节点建立完整的回传链路后,该IAB节点打开其DU功能,DU会提供小区服务,即DU可以为UE(User Equipment)提供接入服务。一个自回传回路包含一个IAB-donor节点,IAB-donor节点有直接相连的有线传输网。
图3是本申请实施例的IAB系统中CU-DU(Centralized Unit-Distributed Unit)结构示意图,如图3所示,在一个自回传回路中,所有的IAB节点的DU都通过F1-AP信令(F1应用协议)连接到IAB-donor-CU节点。IAB-donor-CU通过无线资源控制(Radio Resource Control,RRC)协议,对MT进行配置。IAB-donor节点没有MT功能部分。
IAB系统的引入是为了解决接入点密集部署时,有线传输网部署不到位的情况。即在没有有线传输网络时,接入点可以依赖无线回传。
下面对IAB网络的中的回传适配协议(Backhaul Adaptation Protocol,BAP)协议进行介绍;
BAP的协议层是IAB网络特有的协议层,每个IAB节点中的BAP实体都有一个地址,称为BAP address,该地址结合IAB-donor-CU分配的PATH ID可以用来对数据进行路由。该协议层提供一部分功能如下:
路由功能1:将数据包从CU通过回传通道发送给UE或者是将数据包从UE经回传通道发送到CU;
路由功能2:BAP协议也提供F1-AP信息的路由功能,将来自CU的F1控制信息经回传通道发送给IAB-DU或将来自IAB-DU的F1控制信息经回传通道发送给CU;
服务质量(Quality of Service,QoS)控制信息的传输功能:BAP协议层中定义了一些IAB网络中使用的回传适配协议控制协议数据单元(BAP Control Protocol Data Unit,BAP Control PDU),用来做流量控制、回传无线链路失败的通知等。
IAB网络中的flow control简介:
IAB中支持两种类型的流控机制:hop-by-hop和end-to-end flow control。
(1)hop-by-hop flow control
3GPP RAN2同意在IAB网络中采用流控的机制来解决下行传输时的数据拥塞(The DL hop-by-hop flow control is supported in IAB network.),下行传输时的数据拥塞是指IAB节点从其父IAB节点收到的数据来不及发送给下游节点或者UE而造成数据堆积,当数据堆积,即当数据堆积到有缓存溢出风险时,会向其父节点发送一个flow control的反馈(congested IAB node feedback flow control info to its parent IAB node)以警示拥塞,接收到流控反馈的IAB节点会控制给子IAB节点发送下行数据的传输速率。
具体示例如图4所示,IAB-donor节点可以通过IAB节点1、IAB节点2以及IAB节点3给UE发送下行数据,一旦IAB节点2和IAB节点3之间的回传链路遭遇了链路拥塞,那么IAB节点2会向它的上游节点,即IAB节点1发送flow control message,IAB节点1收到消息后则会停止或者减少向IAB节点2发送新的下行数据。
(2)end-to-end flow control
对于end-to-end flow control,3GPP RAN3同意复用现在的下行链路数据传递状态(downlink data delivery status,DDDS)。
DDDS过程的目的是提供从相应节点到承载NR PDCP实体的节点的反馈,以允许承载NR PDCP实体的节点通过相应数据无线承载的节点控制下行链路用户数据流。相应的节点还可以将用于有关数据无线承载的上行链路用户数据与同一GTP-U PDU中的DDDS帧一起传送到NR PDCP实体的节点。
下面结合附图,通过具体的实施例及其应用场景对本申请实施例提供的资源的分配方法进行详细地说明。
图5是本申请实施例的资源的分配方法流程图一,如图5所示,该方法的步骤包括:
步骤S502,在满足预设条件的情况下,第一IAB节点向第二IAB节点发送资源重分配报告;
在本申请实施例的可选实施方式中,本申请实施例中的第一IAB节点和 第二IAB节点的类型包括以下之一:普通IAB节点、IAB宿主集中单元IAB-donor-CU、IAB宿主分布单元IAB-donor-DU。也就是说,第一IAB节点可以是普通IAB节点、IAB宿主集中单元IAB-donor-CU、IAB宿主分布单元IAB-donor-DU其中之一,而第二IAB节点也可以是普通IAB节点、IAB宿主集中单元IAB-donor-CU、IAB宿主分布单元IAB-donor-DU其中之一。
具体地,本申请实施中的普通IAB节点可以是在IAB网络中除IAB-donor-CU和IAB-donor-DU之外的节点,例如图3中的IAB1和IAB2节点。
步骤S504,第一IAB节点接收第二IAB节点响应于资源重分配报告发送的资源重分配的配置消息。
通过上述步骤S502至步骤S504可知,IAB网络中的第一IAB节点在满足预设条件时可以向第二IAB节点发送资源重分配报告,进而接收第二IAB节点响应于资源重分配报告发送的资源重分配的配置消息,进行资源的重分配;可见,在第一IAB节点出现拥塞时,可以通过第二IAB节点对第一IAB节点进行资源重分配,例如,把没有出现拥塞的节点资源分配到第一IAB节点处,使得在不降低数据传输率的前提下减少第一IAB节点的缓存压力,既可以保证链路传输数据率又能缓解节点数据拥塞,也就是说,在本申请中是对IAB网络中的IAB节点进行局部或全部的资源重分配,从而解决了现有技术中通过流控机制在节点出现数据拥塞时通过降低输入链路的数据率,导致牺牲了IAB网络的服务质量的问题。
在本申请实施例的可选实施方式中,本申请中的预设条件可以包括以下至少一项:事件触发条件、周期性触发条件、轮询触发条件。
其中,本申请实施例中的周期性触发条件是指被设置为周期性触发的第二定时器超时。
其中,该事件触发条件可以包括以下至少一项:
1)第一IAB节点的缓存数据超过第一门限值或低于第二门限值;其中,第一门限值大于第二门限值;
其中,该缓存数据可以是第一IAB节点的缓存器中的缓存数据。
2)第一IAB节点的数据传输速率高于第三门限值或低于第四门限值;其中,第三门限值大于第四门限值;
3)第一IAB节点的时频资源使用数或者使用率超过第五门限值或低于第六门限值;其中,第五门限值大于第六门限值。
由上述事件触发条件的1)~3)可知,其均是指某一类资源超过预设高门限值或低于预设低门限值,即是需要对该第一IAB节点的这一类资源进行重分配,也就是说出现上述事件时,第一IAB节点会主动发送资源重分配报告,进而进行资源重分配。
在具体应用场景中,以事件触发条件1)为例,第一IAB节点的缓存器中缓存数据超过第一门限值,则说明当前第一IAB节点可能存在拥塞,需要将其他没有出现拥塞的节点的资源调整到第一IAB以缓解拥塞,又或者缓存器中缓存数据低于第二门限值,则说明当前第一IAB节点的资源有富余,因此,可以将第一IAB节点富余的资源调度到别的拥塞节点处。其他事件触发条件也是类似的处理过程,在此不再赘述。
可选地,上述事件触发条件3)中的第一IAB节点的时频资源使用数包括第一IAB节点的DU的时频资源使用数或者时频资源使用率,其中,第一IAB节点的DU的时频资源使用率包括以下至少一项:DU的上行时频资源使用率、DU的下行时频资源使用率、DU的Hard上行时频资源使用率、DU的Hard下行时频资源使用率、DU的Soft上行时频资源使用率、DU的Soft下行时频资源使用率。
可选地,在预设条件为事件触发条件的情况下,本申请实施例的方法还可以包括:
步骤S11,第一IAB节点在向第二IAB节点发送资源重分配报告之后,启动第一定时器;
步骤S12,在第一定时器未超时的情况下,第一IAB节点禁止再次发送资源重分配报告;
步骤S13,在第一定时器超时且在满足事件触发条件的情况下,第一IAB节点再次发送资源重分配报告。
通过上述步骤S11至步骤S13可知,第一IAB节点可以在定时器超时的情况下,重复发送资源重分配报告,以确保第二IAB节点能够接收到该资源重分配报告。
可选地,在本申请实施例中的第一门限值、第二门限值、第三门限值、第四门限值、第五门限值、第六门限值、和第一定时器的时长为协议预先定义或网络预先配置的。其中,协议预先定义或网络预先配置的方式,在具体应用场景中可以是IAB-donor-CU通过RRC或F1-AP信令进行配置。
其中,本申请实施例中的轮询触发条件为第一IAB节点接收到第二IAB节点发送的轮询消息。
对于该发送轮询消息的过程,在具有应用场景中可以是:
1)以第一IAB节点为普通IAB节点,第二IAB节点为IAB-donor-CU为例,该发送轮询消息的过程可以是,IAB-donor-CU通过RRC和/或F1AP信令向普通IAB节点发送轮询消息,当普通IAB节点接收到该消息则生成资源重分配报告,并且发送给IAB-donor-CU;
2)IAB网络中的任一IAB节点(IAB1)通过BAP control PDU或MAC CE向其子IAB节点发送轮询消息,当子IAB节点接收到该消息则生成报告,并且发送给IAB1。其中该IAB1对应于本申请中的第二IAB节点,其子IAB节点对应于本申请中的第一IAB节点。
在本申请实施例的可选实施方式中,该轮询消息为第二IAB节点可以通过以下至少之一发送的:无线资源控制RRC消息、F1应用协议F1-AP信令、回传适配协议控制协议数据单元BAP control PDU、介质访问控制单元MAC CE。
在本申请实施例中的可选实施方式,本申请的方法步骤还可以进一步包括:
步骤S21,第一IAB节点接收第二IAB节点再次发送的轮询消息;其中,触发第二IAB节点再次发送轮询消息的条件为第三定时器超时且未收到资源重分配报告。
可选地,本申请实施例中的资源重分配报告可以包括以下至少一项:第一IAB节点的标识、第二IAB节点的标识、按时频资源的复用方式统计的资源使用率、按资源类型统计的资源使用率、第一IAB节点的资源请求。
其中,按时频资源的复用方式统计的资源使用率包括以下至少一项:时分复用TDM调度的资源比例、空分复用SDM调度的资源比例、频分复用 FDM调度的资源比例。
其中,按资源类型统计的资源使用率包括以下至少一项:Hard下行时频资源数、Hard下行资源利用率、Hard上行时频资源数、Hard上行资源利用率、Hard弹性时频资源数、Hard弹性资源利用率、Soft下行时频资源数、Soft下行资源利用率、Soft上行时频资源数、Soft上行资源利用率、Soft弹性时频资源数、Soft弹性资源利用率、总资源利用率。
其中,第一IAB节点的资源请求包括以下至少一项:请求资源的类型、请求资源的数量、复用调度模式。其中,该请求资源的数量为单位时间内需要增加的资源数量。
在本申请实施例的可选实施方式中,第一IAB节点通过以下至少之一项的消息向第二IAB节点发送资源重分配报告:RRC消息、F1-AP信令、BAP control PDU。
其中,RRC消息包括以下至少一项:
1)用户终端辅助信息UEAssistanceInformation,其中,用户终端辅助信息包括第一域,第一域用于报告资源使用率和/或进行资源请求;
需要说明的是,UEAssistanceInformation由IAB-MT使用,以请求网络为IAB节点分配IP地址或将分配给IAB-DU的IP地址通知给网络。
2)自回传其他信息IABOtherInformation,其中,自回传其他信息中包括第二域,第二域用于报告资源使用率和/或进行资源请求。
需要说明的是,IABOtherInformation用于向网络指示UE辅助信息。
其中,F1-AP包括:下行数据传输状态报告,其中,下行数据传输状态报告中新添加有第三域,第三域用于报告资源使用率和/或进行资源请求。
可选地,在本申请实施例中的通过BAP control PDU承载资源重分配报告的传递方式包括以下至少之一:
1)通过BAP control PDU将承载的资源重分配报告传递至第二IAB节点;
2)通过BAP control PDU将承载的第一IAB节点发送的资源重分配报告传递至第一IAB节点的父IAB节点,在父IAB节点内进行层间交互,由父IAB节点的BAP层指示给RRC层或F1AP层,并生成新的消息传递至IAB- donor-CU;
3)通过BAP control PDU将承载的第一IAB节点发送的资源重分配报告传递至IAB-donor-DU节点,在IAB-donor-DU内进行层间交互,并由IAB-donor-DU的BAP层指示给F1AP层,且由F1AP层生成新的消息传递至IAB-donor-CU。
在本申请实施例的可选实施方式中,在第一IAB节点向第二IAB节点发送资源重分配报告之后,本申请实施例的方法步骤还可以进一步包括:
步骤S506,启动第三定时器;
步骤S508,在第三定时器超时且未收到配置消息的情况下,第一IAB节点执行流控flow control机制。
通过上述步骤S506和步骤S508可知,如果不能进行资源重分配的,则可以采用flow control机制,以缓解IAB节点的压力。
上述步骤S502至步骤S508均是从第一IAB节点侧进行描述,对于第二IAB节点侧,本申请实施例提供了一种资源分配的方法,图6是本申请实施例的资源分配的方法流程图二,如图6所示,本申请实施例的方法步骤还可以包括:
步骤S602,第二IAB节点接收第一IAB节点发送的资源重分配报告;
步骤S604,在第二IAB节点根据当前资源分配状态确定为第一IAB节点重新分配资源的情况下,第二IAB节点向第一IAB节点发送资源重分配的配置消息。
可选地,本申请实施例的方法步骤还可以包括:
步骤S606,第二IAB节点向接入IAB网络的第一IAB节点发送资源重分配报告对应的配置参数。其中,配置参数包括以下至少一项:缓存数据的门限值、输出连接和/或输出连接的数据传输速率的门限值、时频资源使用数/使用率的门限值、定时器、资源使用率。
可见,通过本申请实施例的上述步骤S602至步骤S606可知,第二IAB节点可以根据当前资源分配状态确定是否为第一IAB节点重新分配资源,即可以对IAB网络中的IAB节点的资源进行局部或全局调整,从而解决了现有技术中通过流控机制在节点出现数据拥塞时通过降低输入链路的数据率,导 致牺牲了IAB网络的服务质量的问题。
下面结合本申请实施例中的具体实施例对本申请进行举例说明;
具体实施例1:周期性触发的资源重分配报告的过程
在本具体实施例中,当IAB节点接入IAB网络时,由IAB-donor-CU通过RRC信令为接入节点的MT配置关于资源重分配报告的相关参数;或者通过F1-AP信令为接入节点的DU配置关于资源重分配报告的相关参数。
其中,配置的相关参数包括:高/低门限阈值(对应于上述第一至第六门限值),周期性触发定时器,报告中需要携带的资源使用率统计量等。
图7是本申请实施例的周期性触发的资源重分配报告示意图,以图7中的IAB2为第一IAB节点,且IAB-donor-CU为第二IAB节点为例,周期性触发的资源重分配报告的方法步骤包括:
步骤S702,IAB2接入完成后,即开启周期性触发定时器,定时器超时则生成资源重分配报告;
步骤S704,将生成的报告通过RRC消息(如IABOtherInformation)发送给IAB-donor-CU;
步骤S706,IAB-donor-CU收到该报告后,根据当前资源分配情况,决定是否为IAB 2-DU重新分配资源。
其中,若同意分配,则IAB-donor-CU通过F1-AP信令发送gNB-DU Resource Configuration给IAB2-DU;IAB2-DU收到后根据该消息中重分配的资源进行配置,并且回复GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE(GNB-DU资源配置响应)给IAB-donor-CU。
若不同意分配,则IAB-donor-CU不会采取任何措施。
具体实施例2:事件触发的资源重分配报告的过程
在本具体实施例中,当IAB节点接入IAB网络时,由IAB-donor-CU通过RRC信令为接入节点的MT配置关于资源重分配报告的相关参数;或者通过F1-AP信令为接入节点的DU配置关于资源重分配报告的相关参数。其中,配置的相关参数包括:高/低门限阈值,周期性触发定时器,报告中需要携带的资源使用率统计量等。
图8是本申请实施例的事件触发的资源重分配报告示意图,以图8中的 IAB2为第一IAB节点,且IAB-donor-CU为第二IAB节点例,在IAB 2的ingress link的数据率大于egress link的数据率的情况下,事件触发的资源重分配报告的方法步骤包括:
步骤S802,IAB 2的buffer中缓存数据超出预定阈值,触发资源重分配报告的生成,同时开启prohibit timer。
步骤S804,将生成的报告通过RRC消息(IABOtherInformation)发送给IAB-donor-CU,并开启资源重分配定时器;
步骤S806,IAB-donor-CU收到该报告后,根据当前资源分配情况,决定是否为IAB 2-DU分配更多资源来调度IAB2-MT,以提升egress link的数据率,使其能够匹配ingress link的数据率,从而降低IAB 2节点中缓存的数据量。
其中,若同意分配,则IAB-donor-CU通过F1AP信令发送gNB-DU Resource Configuration给IAB2-DU;IAB2-DU收到后根据该消息中重分配的资源进行配置,并且回复GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE给IAB-donor-CU。
其中,若不同意分配,则IAB-donor-CU不会采取任何措施,IAB 2在重分配定时器超时后则采取flow control的机制降低ingress link的数据率。
具体实施例3:基于轮询的资源重分配报告的过程
在本具体实施例中,当IAB节点接入IAB网络时,由IAB-donor-CU通过RRC信令为接入节点的MT配置关于资源重分配报告的相关参数;或者通过F1-AP信令为接入节点的DU配置关于资源重分配报告的相关参数。其中,配置的相关参数包括:高/低门限阈值,周期性触发定时器,报告中需要携带的资源使用率统计量等。
图9是本申请实施例的基于轮询的资源重分配报告示意图,以图9中的IAB2为第一IAB节点,且IAB-donor-CU为第二IAB节点例,基于轮询的资源重分配报告的方法步骤包括:
步骤S902,IAB-donor-CU通过RRC或F1AP信令向IAB节点发送轮询消息(polling message),且开启轮询回复消息定时器,若定时器超时后仍未收到IAB2返回的资源重分配报告,则再次发送轮询消息。
步骤S904,IAB2节点接收到该消息后则生成报告,并且通过RRC消息(UEAssistanceInformation)发送给IAB-donor-CU;
步骤S906,IAB-donor-CU收到该报告后,根据当前资源分配情况,决定是否为IAB 2-DU重新分配资源。
其中,若同意分配,则IAB-donor-CU通过F1AP信令发送gNB-DU Resource Configuration给IAB2-DU;IAB2-DU收到后根据该消息中重分配的资源进行配置,并且回复GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE给IAB-donor-CU;
其中,若不同意分配,则IAB-donor-CU不会采取任何措施。
通过上述具体实施例可知,通过资源重分配报告,可以使得IAB网络能够及时地了解某一IAB节点的资源使用情况,从而局部或整体地对时频资源进行重分配,在不降低数据传输率的前提下减少IAB节点的缓存压力。
需要说明的是,本申请实施例提供的资源的分配方法,执行主体可以为资源的分配装置,或者,该资源的分配装置中的用于执行资源的分配方法的控制模块。本申请实施例中以资源的分配装置执行资源的分配方法为例,说明本申请实施例提供的资源的分配装置。
图10是本申请实施例的资源的分配装置的结构示意图一,如图10所示,该装置包括:
第一发送模块1002,用于在满足预设条件的情况下,向第二IAB节点发送资源重分配报告;
第一接收模块1004,用于接收第二IAB节点响应于资源重分配报告发送的资源重分配的配置消息。
可选地,预设条件包括以下至少一项:事件触发条件、周期性触发条件、轮询触发条件。
可选地,事件触发条件包括以下至少一项:第一IAB节点的缓存数据超过第一门限值或低于第二门限值;其中,第一门限值大于第二门限值;第一IAB节点的数据传输速率高于第三门限值或低于第四门限值;其中,第三门限值大于第四门限值;第一IAB节点的时频资源使用数或者使用率超过第五门限值或低于第六门限值;其中,第五门限值大于第六门限值。
可选地,第一IAB节点的时频资源使用数包括第一IAB节点的DU的时频资源使用数或者时频资源使用率,其中,第一IAB节点的DU的时频资源使用率包括以下至少一项:DU的上行时频资源使用率、DU的下行时频资源使用率、DU的Hard上行时频资源使用率、DU的Hard下行时频资源使用率、DU的Soft上行时频资源使用率、DU的Soft下行时频资源使用率。
可选地,在预设条件为事件触发条件的情况下,本申请实施例的装置还包括:第一启动模块,用于第一IAB节点在向第二IAB节点发送资源重分配报告之后,启动第一定时器;禁止模块,用于在第一定时器未超时的情况下,禁止再次发送资源重分配报告;第二发送模块,用于在第一定时器超时且在满足事件触发条件的情况下,再次发送资源重分配报告。
可选地,第一门限值、第二门限值、第三门限值、第四门限值、第五门限值、第六门限值、和第一定时器的时长为协议预先定义或网络预先配置的。
可选地,周期性触发条件是指被设置为周期性触发的第二定时器超时。
可选地,轮询触发条件为第一IAB节点接收到第二IAB节点发送的轮询消息。
可选地,该轮询消息为第二IAB节点通过以下至少之一发送的:无线资源控制RRC消息、F1应用协议F1-AP信令、回传适配协议控制协议数据单元BAP control PDU、介质访问控制单元MAC CE。
可选地,本申请实施例的装置还可以包括:第二接收模块,用于接收第二IAB节点再次发送的轮询消息;其中,触发第二IAB节点再次发送轮询消息的条件为第三定时器超时且未收到资源重分配报告。
可选地,资源重分配报告包括以下至少一项:第一IAB节点的标识、第二IAB节点的标识、按时频资源的复用方式统计的资源使用率、按资源类型统计的资源使用率、第一IAB节点的资源请求。
可选地,按时频资源的复用方式统计的资源使用率包括以下至少一项:时分复用TDM调度的资源比例、空分复用SDM调度的资源比例、频分复用FDM调度的资源比例。
可选地,按资源类型统计的资源使用率包括以下至少一项:Hard下行时频资源数、Hard下行资源利用率、Hard上行时频资源数、Hard上行资源利用 率、Hard弹性时频资源数、Hard弹性资源利用率、Soft下行时频资源数、Soft下行资源利用率、Soft上行时频资源数、Soft上行资源利用率、Soft弹性时频资源数、Soft弹性资源利用率、总资源利用率。
可选地,第一IAB节点的资源请求包括以下至少一项:请求资源的类型、请求资源的数量、复用调度模式。
可选地,请求资源的数量为单位时间内需要增加的资源数量。
可选地,第一IAB节点通过以下至少之一项的消息向第二IAB节点发送资源重分配报告:RRC消息、F1-AP信令、BAP control PDU。
可选地,RRC消息包括以下至少一项:
用户终端辅助信息,其中,用户终端辅助信息包括第一域,第一域用于报告资源使用率和/或进行资源请求;
自回传其他信息,其中,自回传其他信息中包括第二域,第二域用于报告资源使用率和/或进行资源请求。
可选地,F1-AP信令包括:下行数据传输状态报告,其中,下行数据传输状态报告中新添加有第三域,第三域用于报告资源使用率和/或进行资源请求。
可选地,第一IAB节点和第二IAB节点的类型包括以下之一:普通IAB节点、IAB宿主集中单元IAB-donor-CU、IAB宿主分布单元IAB-donor-DU。
可选地,通过BAP control PDU承载资源重分配报告的传递方式包括以下至少之一:
通过BAP control PDU将承载的资源重分配报告传递至第二IAB节点;
通过BAP control PDU将承载的第一IAB节点发送的资源重分配报告传递至第一IAB节点的父IAB节点,在父IAB节点内进行层间交互,由父IAB节点的BAP层指示给RRC层或F1AP层,并生成新的消息传递至IAB-donor-CU;
通过BAP control PDU将承载的第一IAB节点发送的资源重分配报告传递至IAB-donor-DU节点,在IAB-donor-DU内进行层间交互,并由IAB-donor-DU的BAP层指示给F1AP层,且由F1AP层生成新的消息传递至IAB-donor-CU。
可选地,在第一IAB节点向第二IAB节点发送资源重分配报告之后,本 申请实施例的装置还可以进一步包括:第二启动模块,用于启动第三定时器;执行模块,用于在第三定时器超时且未收到配置消息的情况下,执行流控机制。
图11是本申请实施例的资源的分配装置的结构示意图二,如图11所示,该装置包括:
第二接收模块1102,用于接收第一IAB节点发送的资源重分配报告;
第二发送模块1104,用于在根据当前资源分配状态确定为第一IAB节点重新分配资源的情况下,向第一IAB节点发送资源重分配的配置消息。
可选地,本申请实施例中的装置还可以进一步包括:第三发送模块,用于向接入IAB网络的第一IAB节点发送资源重分配报告对应的配置参数。其中,配置参数包括以下至少一项:缓存数据的门限值、输出连接和/或输出连接的数据传输速率的门限值、时频资源使用数/使用率的门限值、定时器、资源使用率。
通过本申请实施例,IAB网络中的第一IAB节点在满足预设条件时可以向第二IAB节点发送资源重分配报告,进而接收第二IAB节点响应于资源重分配报告发送的资源重分配的配置消息,进行资源的重分配;可见,在第一IAB节点出现拥塞时,可以通过第二IAB节点对第一IAB节点进行资源重分配,例如,把没有出现拥塞的节点资源分配到第一IAB节点处,使得在不降低数据传输率的前提下减少第一IAB节点的缓存压力,既可以保证链路传输数据率又能缓解节点数据拥塞,也就是说,在本申请中是对IAB网络中的IAB节点进行局部或全部的资源重分配,从而解决了现有技术中通过流控机制在节点出现数据拥塞时通过降低输入链路的数据率,导致牺牲了IAB网络的服务质量的问题。
本申请实施例中的资源的分配装置可以是装置,也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端,也可以为非移动终端。示例性的,移动终端可以包括但不限于上述所列举的终端11的类型,非移动终端可以为服务器、网络附属存储器(Network Attached Storage,NAS)、个人计算机(personal computer,PC)、电视机(television,TV)、柜员机或者自助机等,本申请实施例不作具体限定。
本申请实施例中的资源的分配装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统,可以为ios操作系统,还可以为其他可能的操作系统,本申请实施例不作具体限定。
本申请实施例提供的资源的分配装置能够实现图5至图6的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
可选的,如图12所示,本申请实施例还提供一种通信设备1200,包括处理器1201,存储器1202,存储在存储器1202上并可在所述处理器1201上运行的程序或指令,例如,该通信设备1200为终端时,该程序或指令被处理器1201执行时实现上述资源的分配方法实施例的各个过程,且能达到相同的技术效果。该通信设备1200为网络侧设备时,该程序或指令被处理器1201执行时实现上述资源的分配方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
具体地,本申请实施例还提供了一种网络侧设备。如图13所示,该网络设备1300包括:天线131、射频装置132、基带装置133。天线131与射频装置132连接。在上行方向上,射频装置132通过天线131接收信息,将接收的信息发送给基带装置133进行处理。在下行方向上,基带装置133对要发送的信息进行处理,并发送给射频装置132,射频装置132对收到的信息进行处理后经过天线131发送出去。
上述频带处理装置可以位于基带装置133中,以上实施例中网络侧设备执行的方法可以在基带装置133中实现,该基带装置133包括处理器134和存储器135。
基带装置133例如可以包括至少一个基带板,该基带板上设置有多个芯片,如图13所示,其中一个芯片例如为处理器134,与存储器135连接,以调用存储器135中的程序,执行以上方法实施例中所示的网络设备操作。
该基带装置133还可以包括网络接口136,用于与射频装置132交互信息,该接口例如为通用公共无线接口(common public radio interface,CPRI)。
具体地,本发明实施例的网络侧设备还包括:存储在存储器135上并可在处理器134上运行的指令或程序,处理器134调用存储器135中的指令或程序执行图11或12所示各模块执行的方法,并达到相同的技术效果,为避 免重复,故不在此赘述。
本申请实施例还提供一种可读存储介质,所述可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现上述资源的分配方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
其中,所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质,包括计算机可读存储介质,如计算机只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行网络侧设备程序或指令,实现上述资源的分配方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品(例如,可以是程序或程序产品)的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端 (可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。

Claims (53)

  1. 一种资源的分配方法,包括:
    在满足预设条件的情况下,第一IAB节点向第二IAB节点发送资源重分配报告;
    所述第一IAB节点接收所述第二IAB节点响应于所述资源重分配报告发送的资源重分配的配置消息。
  2. 根据权利要求1所述的方法,其中,所述预设条件包括以下至少一项:事件触发条件、周期性触发条件、轮询触发条件。
  3. 根据权利要求2所述的方法,其中,所述事件触发条件包括以下至少一项:
    所述第一IAB节点的缓存数据超过第一门限值或低于第二门限值;其中,所述第一门限值大于所述第二门限值;
    所述第一IAB节点的数据传输速率高于第三门限值或低于第四门限值;其中,所述第三门限值大于所述第四门限值;
    所述第一IAB节点的时频资源使用数或者使用率超过第五门限值或低于第六门限值;其中,所述第五门限值大于所述第六门限值。
  4. 根据权利要求3所述的方法,其中,所述第一IAB节点的时频资源使用数包括所述第一IAB节点的分布单元DU的时频资源使用数或者时频资源使用率,其中,所述第一IAB节点的DU的时频资源使用率包括以下至少一项:
    所述DU的上行时频资源使用率、所述DU的下行时频资源使用率、所述DU的Hard上行时频资源使用率、所述DU的Hard下行时频资源使用率、所述DU的Soft上行时频资源使用率、所述DU的Soft下行时频资源使用率。
  5. 根据权利要求3所述的方法,其中,在所述预设条件为事件触发条件的情况下,所述方法还包括:
    第一IAB节点在向第二IAB节点发送所述资源重分配报告之后,启动第 一定时器;
    在所述第一定时器未超时的情况下,所述第一IAB节点禁止再次发送资源重分配报告;
    在所述第一定时器超时且在满足所述事件触发条件的情况下,所述第一IAB节点再次发送资源重分配报告。
  6. 根据权利要求2所述的方法,其中,所述周期性触发条件是指被设置为周期性触发的第二定时器超时。
  7. 根据权利要求2所述的方法,其中,所述轮询触发条件为所述第一IAB节点接收到所述第二IAB节点发送的轮询消息。
  8. 根据权利要求7所述的方法,其中,所述轮询消息为所述第二IAB节点通过以下至少之一发送的:无线资源控制RRC消息、F1应用协议F1-AP信令、回传适配协议控制协议数据单元BAP control PDU、介质访问控制单元MAC CE。
  9. 根据权利要求8所述的方法,还包括:
    所述第一IAB节点接收第二IAB节点再次发送的轮询消息;其中,触发所述第二IAB节点再次发送轮询消息的条件为第三定时器超时且未收到所述资源重分配报告。
  10. 根据权利要求5或6或9所述的方法,其中,所述第一门限值、所述第二门限值、所述第三门限值、所述第四门限值、所述第五门限值、所述第六门限值、所述第一定时器的时长、所述第二定时器的时长和所述第三定时器的时长为协议预先定义的或由网络预先配置的。
  11. 根据权利要求1所述的方法,其中,所述资源重分配报告包括以下至少一项:
    所述第一IAB节点的标识、所述第二IAB节点的标识、按时频资源的复用方式统计的资源使用率、按资源类型统计的资源使用率、所述第一IAB节点的资源请求。
  12. 根据权利要求11所述的方法,其中,按时频资源的复用方式统计的 资源使用率包括以下至少一项:
    时分复用TDM调度的资源比例、空分复用SDM调度的资源比例、频分复用FDM调度的资源比例。
  13. 根据权利要求11所述的方法,其中,按资源类型统计的资源使用率包括以下至少一项:
    Hard下行时频资源数、Hard下行资源利用率、Hard上行时频资源数、Hard上行资源利用率、Hard弹性时频资源数、Hard弹性资源利用率、Soft下行时频资源数、Soft下行资源利用率、Soft上行时频资源数、Soft上行资源利用率、Soft弹性时频资源数、Soft弹性资源利用率、总资源利用率。
  14. 根据权利要求11所述的方法,其中,所述第一IAB节点的资源请求包括以下至少一项:
    请求资源的类型、请求资源的数量、复用调度模式。
  15. 根据权利要求14所述的方法,其中,所述请求资源的数量为单位时间内需要增加的资源数量。
  16. 根据权利要求1所述的方法,其中,所述第一IAB节点通过以下至少之一项的消息向第二IAB节点发送所述资源重分配报告:
    RRC消息、F1-AP信令、BAP control PDU。
  17. 根据权利要求16所述的方法,其中,所述RRC消息包括以下至少一项:
    用户终端辅助信息,其中,所述用户终端辅助信息包括第一域,所述第一域用于报告资源使用率和/或进行资源请求;
    自回传其他信息,其中,所述自回传其他信息中包括第二域,所述第二域用于报告资源使用率和/或进行资源请求。
  18. 根据权利要求16所述的方法,其中,所述F1-AP信令包括:下行数据传输状态报告,其中,所述下行数据传输状态报告中新添加有第三域,所述第三域用于报告资源使用率和/或进行资源请求。
  19. 根据权利要求16所述的方法,其中,所述第一IAB节点和所述第二 IAB节点的类型包括以下之一:普通IAB节点、IAB宿主集中单元IAB-donor-CU、IAB宿主分布单元IAB-donor-DU。
  20. 根据权利要求19所述的方法,其中,通过所述BAP control PDU承载所述资源重分配报告的传递方式包括以下至少之一:
    通过BAP control PDU将承载的所述资源重分配报告传递至所述第二IAB节点;
    通过BAP control PDU将承载的所述第一IAB节点发送的资源重分配报告传递至所述第一IAB节点的父IAB节点,在所述父IAB节点内进行层间交互,由父IAB节点的BAP层指示给RRC层或F1AP层,并生成新的消息传递至IAB-donor-CU;
    通过BAP control PDU将承载的所述第一IAB节点发送的资源重分配报告传递至IAB-donor-DU节点,在IAB-donor-DU内进行层间交互,并由IAB-donor-DU的BAP层指示给F1AP层,且由F1AP层生成新的消息传递至IAB-donor-CU。
  21. 根据权利要求1所述的方法,其中,在第一IAB节点向第二IAB节点发送资源重分配报告之后,所述方法还包括:
    启动第四定时器;
    在所述第四定时器超时且未收到所述配置消息的情况下,所述第一IAB节点执行流控机制。
  22. 一种资源的分配方法,包括:
    第二IAB节点接收第一IAB节点发送的资源重分配报告;
    在所述第二IAB节点根据当前资源分配状态确定为所述第一IAB节点重新分配资源的情况下,所述第二IAB节点向所述第一IAB节点发送资源重分配的配置消息。
  23. 根据权利要求22所述的方法,还包括:
    所述第二IAB节点向接入IAB网络的第一IAB节点发送资源重分配报告对应的配置参数。
  24. 根据权利要求23所述的方法,其中,所述配置参数包括以下至少一项:
    缓存数据的门限值、输出连接和/或输出连接的数据传输速率的门限值、时频资源使用数/使用率的门限值、定时器、资源使用率。
  25. 一种资源的分配装置,应用于第一IAB节点,包括:
    第一发送模块,用于在满足预设条件的情况下,向第二IAB节点发送资源重分配报告;
    第一接收模块,用于接收所述第二IAB节点响应于所述资源重分配报告发送的资源重分配的配置消息。
  26. 根据权利要求25所述的装置,其中,所述预设条件包括以下至少一项:事件触发条件、周期性触发条件、轮询触发条件。
  27. 根据权利要求26所述的装置,其中,所述事件触发条件包括以下至少一项:
    所述第一IAB节点的缓存数据超过第一门限值或低于第二门限值;其中,所述第一门限值大于所述第二门限值;
    所述第一IAB节点的数据传输速率高于第三门限值或低于第四门限值;其中,所述第三门限值大于所述第四门限值;
    所述第一IAB节点的时频资源使用数或者使用率超过第五门限值或低于第六门限值;其中,所述第五门限值大于所述第六门限值。
  28. 根据权利要求27所述的装置,其中,所述第一IAB节点的时频资源使用数包括所述第一IAB节点的DU的时频资源使用数或者时频资源使用率,其中,所述第一IAB节点的DU的时频资源使用率包括以下至少一项:
    所述DU的上行时频资源使用率、所述DU的下行时频资源使用率、所述DU的Hard上行时频资源使用率、所述DU的Hard下行时频资源使用率、所述DU的Soft上行时频资源使用率、所述DU的Soft下行时频资源使用率。
  29. 根据权利要求27所述的装置,其中,在所述预设条件为事件触发条件的情况下,所述装置还包括:
    启动模块,用于第一IAB节点在向第二IAB节点发送所述资源重分配报告之后,启动第一定时器;
    禁止模块,用于在所述第一定时器未超时的情况下,禁止再次发送资源重分配报告;
    第二发送模块,用于在所述第一定时器超时且在满足所述事件触发条件的情况下,再次发送资源重分配报告。
  30. 根据权利要求26所述的装置,其中,所述周期性触发条件是指被设置为周期性触发的第二定时器超时。
  31. 根据权利要求26所述的装置,其中,所述轮询触发条件为所述第一IAB节点接收到所述第二IAB节点发送的轮询消息。
  32. 根据权利要求31所述的装置,其中,所述轮询消息为所述第二IAB节点通过以下至少之一发送的:无线资源控制RRC消息、F1应用协议F1-AP信令、回传适配协议控制协议数据单元BAP control PDU、介质访问控制单元MAC CE。
  33. 根据权利要求31所述的装置,还包括:
    第二接收模块,用于接收第二IAB节点再次发送的轮询消息;其中,触发所述第二IAB节点再次发送轮询消息的条件为第三定时器超时且未收到所述资源重分配报告。
  34. 根据权利要求29或30或33所述的装置,其中,所述第一门限值、所述第二门限值、所述第三门限值、所述第四门限值、所述第五门限值、所述第六门限值、所述第一定时器的时长、所述第二定时器的时长和所述第三定时器的时长为协议预先定义的或网络预先配置的。
  35. 根据权利要求25所述的装置,其中,所述资源重分配报告包括以下至少一项:
    所述第一IAB节点的标识、所述第二IAB节点的标识、按时频资源的复用方式统计的资源使用率、按资源类型统计的资源使用率、所述第一IAB节点的资源请求。
  36. 根据权利要求35所述的装置,其中,按时频资源的复用方式统计的资源使用率包括以下至少一项:
    时分复用TDM调度的资源比例、空分复用SDM调度的资源比例、频分复用FDM调度的资源比例。
  37. 根据权利要求35所述的装置,其中,按资源类型统计的资源使用率包括以下至少一项:
    Hard下行时频资源数、Hard下行资源利用率、Hard上行时频资源数、Hard上行资源利用率、Hard弹性时频资源数、Hard弹性资源利用率、Soft下行时频资源数、Soft下行资源利用率、Soft上行时频资源数、Soft上行资源利用率、Soft弹性时频资源数、Soft弹性资源利用率、总资源利用率。
  38. 根据权利要求35所述的装置,其中,所述第一IAB节点的资源请求包括以下至少一项:
    请求资源的类型、请求资源的数量、复用调度模式。
  39. 根据权利要求38所述的装置,其中,所述请求资源的数量为单位时间内需要增加的资源数量。
  40. 根据权利要求25所述的装置,其中,所述第一发送模块通过以下至少之一项的消息向第二IAB节点发送所述资源重分配报告:
    RRC消息、F1-AP信令、BAP control PDU。
  41. 根据权利要求40所述的装置,其中,所述RRC消息包括以下至少一项:
    用户终端辅助信息,其中,所述用户终端辅助信息包括第一域,所述第一域用于报告资源使用率和/或进行资源请求;
    自回传其他信息,其中,所述自回传其他信息中包括第二域,所述第二域用于报告资源使用率和/或进行资源请求。
  42. 根据权利要求40所述的装置,其中,所述F1-AP信令包括:下行数据传输状态报告,其中,所述下行数据传输状态报告中新添加有第三域,所述第三域用于报告资源使用率和/或进行资源请求。
  43. 根据权利要求40所述的装置,其中,所述第一IAB节点和所述第二IAB节点的类型包括以下之一:普通IAB节点、IAB宿主集中单元IAB-donor-CU、IAB宿主分布单元IAB-donor-DU。
  44. 根据权利要求43所述的装置,其中,通过所述BAP control PDU承载所述资源重分配报告的传递方式包括以下至少之一:
    通过BAP control PDU将承载的所述资源重分配报告传递至所述第二IAB节点;
    通过BAP control PDU将承载的所述第一IAB节点发送的资源重分配报告传递至所述第一IAB节点的父IAB节点,在所述父IAB节点内进行层间交互,由父IAB节点的BAP层指示给RRC层或F1AP层,并生成新的消息传递至IAB-donor-CU;
    通过BAP control PDU将承载的所述第一IAB节点发送的资源重分配报告传递至IAB-donor-DU节点,在IAB-donor-DU内进行层间交互,并由IAB-donor-DU的BAP层指示给F1AP层,且由F1AP层生成新的消息传递至IAB-donor-CU。
  45. 根据权利要求25所述的装置,还包括:
    启动模块,用于在向第二IAB节点发送资源重分配报告之后,启动第四定时器;
    执行模块,用于在所述第四定时器超时且未收到所述配置消息的情况下,执行流控机制。
  46. 一种资源的分配装置,应用于第二IAB节点,包括:
    第二接收模块,用于接收第一IAB节点发送的资源重分配报告;
    第二发送模块,用于在根据当前资源分配状态确定为所述第一IAB节点重新分配资源的情况下,向所述第一IAB节点发送资源重分配的配置消息。
  47. 根据权利要求46所述的装置,还包括:
    第三发送模块,用于向接入IAB网络的第一IAB节点发送资源重分配报告对应的配置参数。
  48. 根据权利要求47所述的装置,其中,所述配置参数包括以下至少一项:
    缓存数据的门限值、输出连接和/或输出连接的数据传输速率的门限值、时频资源使用数/使用率的门限值、定时器、资源使用率。
  49. 一种网络侧设备,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求1至21任一项所述的资源的分配方法的步骤,或实现如权利要求22至24任一项所述的资源的分配方法的步骤。
  50. 一种可读存储介质,其中,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如权利要求1至21任一项所述的资源的分配方法,或者实现如权利要求22至24任一项所述的资源的分配方法的步骤。
  51. 一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如权利要求1至21任一项所述的资源的分配方法,或者实现如权利要求22至24任一项所述的资源的分配方法的步骤。
  52. 一种程序产品,所述程序产品被至少一个处理器执行以实现如权利要求1至21任一项所述的资源的分配方法,或者实现如权利要求22至24任一项所述的资源的分配方法的步骤。
  53. 一种网络侧设备,用于执行如权利要求1至21任一项所述的资源的分配方法,或执行如权利要求22至24任一项所述的资源的分配方法。
PCT/CN2021/108649 2020-07-28 2021-07-27 资源的分配方法及装置、网络侧设备和可读存储介质 WO2022022504A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010739844.3A CN114071718A (zh) 2020-07-28 2020-07-28 资源的分配方法及装置、网络侧设备和可读存储介质
CN202010739844.3 2020-07-28

Publications (1)

Publication Number Publication Date
WO2022022504A1 true WO2022022504A1 (zh) 2022-02-03

Family

ID=80037615

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/108649 WO2022022504A1 (zh) 2020-07-28 2021-07-27 资源的分配方法及装置、网络侧设备和可读存储介质

Country Status (2)

Country Link
CN (1) CN114071718A (zh)
WO (1) WO2022022504A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110351836A (zh) * 2018-04-03 2019-10-18 维沃移动通信有限公司 中继资源的配置方法和设备
CN110536351A (zh) * 2019-02-15 2019-12-03 中兴通讯股份有限公司 Iab网络中信息处理方法、iab及计算机存储介质
CN110621050A (zh) * 2018-06-20 2019-12-27 财团法人工业技术研究院 网络链路拓扑适应方法及接入和回传一体化节点

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110351836A (zh) * 2018-04-03 2019-10-18 维沃移动通信有限公司 中继资源的配置方法和设备
CN110621050A (zh) * 2018-06-20 2019-12-27 财团法人工业技术研究院 网络链路拓扑适应方法及接入和回传一体化节点
CN110536351A (zh) * 2019-02-15 2019-12-03 中兴通讯股份有限公司 Iab网络中信息处理方法、iab及计算机存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
VIVO: "Discussion on IAB node access and resource allocation", 3GPP DRAFT; R2-1809864-DISCUSSION ON IAB NODE ACCESS AND RESOURCE ALLOCATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Montreal, Canada; 20180702 - 20180706, 22 June 2018 (2018-06-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051525690 *
ZTE: "Discussion on flow control in IAB", 3GPP DRAFT; R2-1812463 DISCUSSION ON FLOW CONTROL IN IAB_V1.2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Gothenburg, Sweden; 20180820 - 20180824, 10 August 2018 (2018-08-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051522061 *

Also Published As

Publication number Publication date
CN114071718A (zh) 2022-02-18

Similar Documents

Publication Publication Date Title
US20200280871A1 (en) Optimization of resource allocation based on received quality of experience information
US11191072B2 (en) Information transmission method and radio access network device
US10743225B2 (en) Scheduling method and base station
KR101386052B1 (ko) 무선 자원 스케줄링 방법, 접속 네트워크 및 터미널
KR101176911B1 (ko) 스케줄링 요청을 위한 방법 및 장치
WO2020031583A1 (en) Communication system
CN111356172B (zh) 通信方法、装置、终端、网络设备及存储介质
WO2010025580A1 (zh) 无线接入网络中请求和处理上行资源分配的方法和装置
JP2022519121A (ja) ユーザ装置に対する完全性保護データレートの適用
JP2022542792A (ja) サイドリンクスケジューリングリクエストのトリガー方法、装置及びシステム
CN109246753B (zh) 一种传输数据的方法、网络设备和终端设备
WO2019029568A1 (zh) 通信方法、终端设备和网络设备
WO2020203446A1 (en) Communication system
EP3984290A1 (en) Transceiver device and scheduling device
WO2016125775A1 (ja) 制御装置、通信装置、制御方法及びプログラム
WO2020147814A1 (zh) 资源分配的方法和设备
WO2022022504A1 (zh) 资源的分配方法及装置、网络侧设备和可读存储介质
KR20130139684A (ko) 통화 트래픽을 위한 자원할당 방법, 그리고 이를 수행하는 자원할당장치
WO2018058474A1 (zh) 一种数据发送方法和装置
JP2023534724A (ja) スモールデータの送信に関与するユーザ機器および基地局
CN116686329A (zh) 信号的发送和接收方法、装置和通信系统
WO2023165387A1 (zh) 一种通信方法及设备
US20240098747A1 (en) Transmitting Periodic Cadence Reports to a Network
WO2023085031A1 (ja) 基地局装置、通信装置、通信システム及び通信方法
US20240098772A1 (en) Uplink Latency Enhancements

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

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

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 21850725

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 01/08/2023)