CN113709898A - Capability reporting and acquiring method, IP address requesting method and IAB node - Google Patents

Abstract

The application discloses a capability reporting method, a capability acquiring method, an IP address requesting method and an IAB node, wherein the capability reporting method comprises the following steps: sending a first message to a Centralized Unit (CU) of an IAB host node; wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT; the embodiment of the invention indicates the type of the IAB-MT through the first message, so that the CU of the IAB host node can distinguish the type of the IAB-MT, thereby accurately knowing the capability of the IAB node and effectively controlling the IAB node; or, the first message contains the minimum capability set supported by the first information field indication IAB-MT, so that the capability of the IAB node can be directly indicated, and the IAB node can be effectively controlled.

Description

Capability reporting and acquiring method, IP address requesting method and IAB node

Technical Field

The application belongs to the technical field of communication, and particularly relates to a capability reporting and acquiring method, an IP address requesting method and an IAB node.

Background

An Integrated Access Backhaul (IAB) node in an IAB system includes a Distributed Unit (DU) function portion and a Mobile Terminal (MT) function portion. By means of the MT, an access point (i.e. IAB node) can find an upstream access point (parent IAB node) and establish a wireless connection, called backhaul link, from the DU of the upstream access point. After an IAB node establishes a complete backhaul link, the IAB node opens its DU function, and the DU provides cell service, i.e., the DU can provide access service for the terminal. A self-return loop includes an IAB-donor (IAB-donor) node having a wire transport network directly connected to a core network.

An IAB-MT may be regarded as a normal terminal when accessing a network, and first initiates an initial access, and after the initial access is completed, sends a radio resource control setup complete (RRCSetupComplete) message to a Central Unit (CU) of an IAB node, where the message carries an IAB node indication field and sets its value to true (true), and indicates that the CU of the IAB node is an IAB node. Immediately after setting up the IAB-DU, the F1 signaling connection is established.

Currently 2 types of IAB-MT are defined, wide-area and local-area, respectively. Generally, a wide area IAB-MT may be equipped in an IAB node providing large coverage, which has a coverage range comparable to that of a macro base station (macro base station), and is large; local area IAB-MT is equipped in IAB nodes providing smaller coverage, whose coverage area is analogized to micro/pico base station (micro/pico base station). The functionality and characteristics of wide-area IAB-MT are known to the operator, and their deployment scenarios are typically fixed and well planned (operators are very familiar with current geographical environment characteristics). For local IAB-MT, it is usually deployed in places where the environment is severe or where the operator is not known in advance.

In the process of implementing the present application, the inventor finds that at least the following problems exist in the prior art:

after the current IAB node is accessed to the IAB network, the identity of the IAB node can be indicated through an IAB node indication domain in an RRC setting completion message, but a CU of an IAB host node cannot accurately know the capability of the accessed IAB node, and cannot effectively control the IAB node.

Disclosure of Invention

The embodiments of the present application provide a capability reporting and acquiring method, an IP address requesting method, and an IAB node, which can solve the problem that a CU of an IAB host node cannot accurately know capabilities of each IAB node and cannot effectively control the IAB node.

In order to solve the technical problem, the present application is implemented as follows:

in a first aspect, an embodiment of the present application provides a capability reporting method, which is applied to a self-backhauled IAB node, where the IAB node includes an IAB-MT, and includes:

sending a first message to a Centralized Unit (CU) of an IAB host node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

In a second aspect, an embodiment of the present application provides a capability obtaining method, applied to a self-backhauled IAB host node, including:

receiving a first message sent by an IAB node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

In a third aspect, an embodiment of the present application provides an IP address requesting method, applied to a self-backhauled IAB node, including:

sending an IP address request message to a centralized unit CU of an IAB host node and starting an IP request prohibition timer;

wherein the IAB node prohibits sending IP address request messages during the operation of the IP request prohibit timer.

In a fourth aspect, an embodiment of the present application provides a capability reporting apparatus, which is applied to a self-backhauled IAB node, where the IAB node includes an IAB-MT, and includes:

a first sending module, configured to send a first message to a centralized unit CU of an IAB host node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

In a fifth aspect, an embodiment of the present application further provides a capability obtaining apparatus, applied to a self-backhauled IAB host node, including:

a receiving module, configured to receive a first message sent by an IAB node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

In a sixth aspect, an embodiment of the present application further provides an IP address requesting apparatus, applied to a self-backhauled IAB node, including:

a second sending module, configured to send an IP address request message to a CU, which is a central unit of an IAB host node;

the starting module is used for starting an IP request forbidding timer;

wherein the IAB node prohibits sending IP address request messages during the operation of the IP request prohibit timer.

In a seventh aspect, an embodiment of the present application provides a self-backhauled IAB node, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method according to the first aspect, the second aspect, or the third aspect.

In an eighth aspect, the present application provides a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect, the second aspect or the third aspect.

In a ninth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect, the second aspect, or the third aspect.

In the embodiment of the application, the type of the IAB-MT is indicated through the first message, so that the CU of the IAB host node can distinguish the type of the IAB-MT, the capability of the IAB node can be accurately known, and the IAB node can be effectively controlled; or, the first message contains the minimum capability set supported by the first information field indication IAB-MT, so that the capability of the IAB node can be directly indicated, and the IAB node can be effectively controlled.

Drawings

Fig. 1 is a schematic diagram illustrating steps of a capability reporting method according to an embodiment of the present application;

FIG. 2 is a schematic diagram illustrating steps of a capability obtaining method according to an embodiment of the present application;

FIG. 3 is an interaction diagram of an example I provided by an embodiment of the invention;

fig. 4 is a schematic diagram illustrating steps of an IP address requesting method according to an embodiment of the present invention;

FIG. 5 is an interaction diagram of example two provided by an embodiment of the invention;

FIG. 6 is an interaction diagram of example three provided by an embodiment of the invention;

fig. 7 is a schematic structural diagram of a capability reporting apparatus according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a capability obtaining apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an IP address requesting device according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of an IAB node according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

Embodiments of the present application are described below with reference to the accompanying drawings. The capability reporting and acquiring method, the IP address requesting method and the IAB node provided by the embodiment of the application can be applied to a wireless communication system. The wireless communication system may be a 5G system, or a Long Term Evolution (LTE) system, or an Evolved Long Term Evolution (LTE) system, or a subsequent Evolution communication system. In the embodiment of the present application, LTE and NR systems are taken as examples, but not limited to this system, and the technical solution provided by the present application may be applied to other systems having the same problem.

The following describes in detail, in conjunction with the accompanying drawings, a capability reporting method, an acquiring method, an IP address requesting method, and an IAB node provided in the embodiments of the present application through specific embodiments and application scenarios thereof

As shown in fig. 1, an embodiment of the present application provides a capability reporting method applied to a self-backhauled IAB node, where the IAB node includes an IAB-MT, including:

step 101, sending a first message to a centralized unit CU of an IAB host node; wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

Among them, the types of IAB-MT include wide-area (wide-area) type and local-area (local-area) type.

Optionally, when the first message includes a first information field, multiple minimum capability sets need to be predefined, where the first information field indicates a sequence number of a certain minimum capability set, and the minimum capability set corresponding to the sequence number indicated by the first information field is the minimum capability set supported by the IAB-MT. In this case, the type of the IAB-MT may not be distinguished, and the minimum capability set supported by the IAB-MT is directly indicated through the first information field, so that the capability of the IAB node can be directly indicated, and the IAB node can be effectively controlled.

Optionally, the first information field is in integer format, and indicates the minimum capability set supported by the MT of the IAB node through the integer; wherein the integer indicates the sequence number of one of the minimum capability sets. For example, the first information field is interger {1,2, …, max _ minimum _ set }, where max _ minimum _ set represents the number of all minimum capability sets.

As an optional embodiment of the present application, if the first message is used to indicate the type of the IAB-MT, the first message is further used to indicate at least one of the following:

the type indicated by the first message corresponds to the minimum capability set supported by the IAB-MT;

and whether the IAB-MT corresponding to the type indicated by the first message has other capabilities to be reported except the minimum capability set supported by the IAB-MT.

For example, the first message indicates that the type of the IAB-MT is the wide-area type, and then the first message is further used to indicate the minimum capability set supported by the IAB-MT of the wide-area type, and/or whether the IAB-MT of the wide-area type has other capabilities to report in addition to the minimum capability set supported by the IAB-MT of the wide-area type.

For another example, the first message indicates that the type of the IAB-MT is a local-area type, and the first message is further used to indicate a minimum capability set supported by the local-area type IAB-MT, and/or whether the local-area type IAB-MT has other capabilities to report besides the minimum capability set supported by the local-area type IAB-MT.

In the embodiment of the present application, the capability information of the IAB-MT mainly includes two types, which are:

a) the minimum set of capabilities, which is partly the most basic functionality, must be supported by all terminals.

b) Capabilities other than the minimum set of capabilities that it supports; the capability requires the terminal to be selected before a certain time node, and before the time node, if the terminal does not support a certain function, the corresponding capability bit is set to be 0; alternatively, for optional functions, set 1 is supported and set 0 is not supported.

As another optional embodiment of the present application, the first message is a radio resource control, RRC, message. The RRC message may be a new RRC message or an enhancement of an existing RRC message. In the case that the RRC message is an existing RRC message, the RRC message may be any one of:

RRC setup complete (RRCSetupComplete) message;

a terminal information response (UEInformationResponse) message;

RRC reconfiguration complete (rrcreconfigurable complete) message.

As another optional embodiment of the present application, the type of the IAB-MT is indicated in the first message by a value of a second information field; and when the type of the IAB-MT is indicated through the value of a second information field in the first message, the second information field is in an enumerated format, and the type of the IAB-MT is indicated through the enumerated format.

For example, the second information field may be identified by 2bits, such as estimated local-area, wide-area, estimated local-area, or estimated wide-area. The type of the current IAB-MT is indicated by selecting a value (value) in the IAB-MT.

Or, as another optional embodiment of the present application, the type of the IAB-MT is indicated by whether a third information field exists in the first message;

for example, the third information field may be identified by 1bit, such as estimated { true }; when the third information field exists (existence can only be true), the type of the IAB-MT is wide-area or local-area.

Or, as another optional embodiment of the present application, in a case that the first message includes an IAB node indication field, the type of the IAB-MT is indicated by whether a fourth information field exists.

For another example, a new fourth information field is introduced, when an IAB node indication field (indicating that the node is an IAB node) appears in the first message, if the fourth information field exists, it indicates that the type of the IAB-MT is the first type (wide-area or local-area); if the fourth information field does not exist, the IAB-MT is of the second type (local-area or wide-area).

As another optional embodiment of the present application, in a case that the first message includes an IAB node indication field, setting the IAB node indication field to a selected format;

and the type of the IAB-MT is indicated through the value of the IAB node indication domain.

In other words, the embodiment of the present application modifies the IAB node indication field, changes the enumerated format of the IAB node indication field into the selected format, and the IAB node selects the value represented by the corresponding type to report the value; the IAB node indication field directly indicates the type of IAB-MT and implicitly indicates that the node is an IAB node.

In summary, in the embodiment of the present application, the type of the IAB-MT is indicated by the first message, so that a CU of the IAB host node can distinguish the type of the IAB-MT, and thus, the capability of the IAB node can be accurately known, and the IAB node can be effectively controlled; or, the first message contains the minimum capability set supported by the first information field indication IAB-MT, so that the capability of the IAB node can be directly indicated, and the IAB node can be effectively controlled.

As shown in fig. 2, an embodiment of the present application further provides a capability obtaining method, applied to a self-backhauled IAB host node, including:

step 201, receiving a first message sent by an IAB node; wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

Among them, the types of IAB-MT include wide-area (wide-area) type and local-area (local-area) type.

Optionally, when the first message includes a first information field, multiple minimum capability sets need to be predefined, where the first information field indicates a sequence number of a certain minimum capability set, and the minimum capability set corresponding to the sequence number indicated by the first information field is the minimum capability set supported by the IAB-MT. In this case, the type of the IAB-MT may not be distinguished, and the minimum capability set supported by the IAB-MT is directly indicated through the first information field, so that the capability of the IAB node can be directly indicated, and the IAB node can be effectively controlled.

Optionally, the first information field is in integer format, and indicates the minimum capability set supported by the MT of the IAB node through the integer; wherein the integer indicates the sequence number of one of the minimum capability sets. For example, the first information field is interger {1,2, …, max _ minimum _ set }, where max _ minimum _ set represents the number of all minimum capability sets.

As an optional embodiment of the present application, if the first message is used to indicate the type of the IAB-MT, the first message is further used to indicate at least one of the following:

the type indicated by the first message corresponds to the minimum capability set supported by the IAB-MT;

and whether the IAB-MT corresponding to the type indicated by the first message has other capabilities to be reported except the minimum capability set supported by the IAB-MT.

For example, the first message indicates that the type of the IAB-MT is the wide-area type, and then the first message is further used to indicate the minimum capability set supported by the IAB-MT of the wide-area type, and/or whether the IAB-MT of the wide-area type has other capabilities to report in addition to the minimum capability set supported by the IAB-MT of the wide-area type.

For another example, the first message indicates that the type of the IAB-MT is a local-area type, and the first message is further used to indicate a minimum capability set supported by the local-area type IAB-MT, and/or whether the local-area type IAB-MT has other capabilities to report besides the minimum capability set supported by the local-area type IAB-MT.

In the embodiment of the present application, the capability information of the IAB-MT mainly includes two types, which are:

a) the minimum set of capabilities, which is partly the most basic functionality, must be supported by all terminals.

b) Capabilities other than the minimum set of capabilities that it supports; the capability requires the terminal to be selected before a certain time node, and before the time node, if the terminal does not support a certain function, the corresponding capability bit is set to be 0; alternatively, for optional functions, set 1 is supported and set 0 is not supported.

As another optional embodiment of the present application, the first message is a radio resource control, RRC, message. The RRC message may be a new RRC message or an enhancement of an existing RRC message. In the case that the RRC message is an existing RRC message, the RRC message may be any one of:

RRC setup complete (RRCSetupComplete) message;

a terminal information response (UEInformationResponse) message;

RRC reconfiguration complete (rrcreconfigurable complete) message.

As another optional embodiment of the present application, the type of the IAB-MT is indicated in the first message by a value of a second information field; and when the type of the IAB-MT is indicated through the value of a second information field in the first message, the second information field is in an enumerated format, and the type of the IAB-MT is indicated through the enumerated format.

For example, the second information field may be identified by 2bits, such as estimated local-area, wide-area, estimated local-area, or estimated wide-area. The type of the current IAB-MT is indicated by selecting a value (value) in the IAB-MT.

Or, as another optional embodiment of the present application, the type of the IAB-MT is indicated by whether a third information field exists in the first message;

for example, the third information field may be identified by 1bit, such as estimated { true }; when the third information field exists (existence can only be true), the type of the IAB-MT is wide-area or local-area.

Or, as another optional embodiment of the present application, in a case that the first message includes an IAB node indication field, the type of the IAB-MT is indicated by whether a fourth information field exists.

For another example, a new fourth information field is introduced, when an IAB node indication field (indicating that the node is an IAB node) appears in the first message, if the fourth information field exists, it indicates that the type of the IAB-MT is the first type (wide-area or local-area); if the fourth information field does not exist, the IAB-MT is of the second type (local-area or wide-area).

As another optional embodiment of the present application, in a case that the first message includes an IAB node indication field, setting the IAB node indication field to a selected format;

and the type of the IAB-MT is indicated through the value of the IAB node indication domain.

In other words, the embodiment of the present application modifies the IAB node indication field, changes the enumerated format of the IAB node indication field into the selected format, and the IAB node selects the value represented by the corresponding type to report the value; the IAB node indication field directly indicates the type of IAB-MT and implicitly indicates that the node is an IAB node.

In summary, in the embodiment of the present application, the type of the IAB-MT is indicated by the first message, so that a CU of the IAB host node can distinguish the type of the IAB-MT, and thus, the capability of the IAB node can be accurately known, and the IAB node can be effectively controlled; or, the first message contains the minimum capability set supported by the first information field indication IAB-MT, so that the capability of the IAB node can be directly indicated, and the IAB node can be effectively controlled.

In order to more clearly describe the capability reporting method and the capability acquiring method provided in the embodiments of the present application, the following description is made with reference to an example.

Example 1

As shown in FIG. 3, the capability interaction flow includes:

step 31, a new IAB node starts to access the network, firstly, the IAB-MT sends an RRC setting request message to an IAB-donor-CU (CU of an IAB host node);

step 32, the IAB-donor-CU replies an RRC setting message to the IAB-MT;

step 33, the IAB-MT replies an RRC setting completion message to the IAB-donor-CU after receiving the RRC setting completion message;

a) the message carries an IAB (access point) indication domain (set to true), which indicates that the newly accessed equipment is an IAB;

b) in addition, the RRC setup complete message also carries a new domain (e.g., an IAB type indication domain); or an extension of some already existing domain, such as an extension to the IAB node indication domain;

the field may be represented by 2bits, such as estimated local-area, wide-area, estimated local-area, or estimated wide-area. Indicating the type of the current IAB-MT by selecting value in the IAB-MT; alternatively, the format of the field may be represented by 1bit, such as estimated { true }; when the indicator exists (the existence can be true), the IAB-MT is the wide-area or the local-area.

Step 34, assuming that the current message indicates that the IAB node is local-area IAB-MT, the meaning is: there is extra capability to report via the capability signalling procedure of the UE. After the network knows that the node is a local-area IAB, the network can initiate a capability request message to the IAB when needed.

Step 35, the IAB receives the capability request information, and returns the other capabilities except the minimum capability set through the terminal capability information.

After accessing the network, the IAB node needs to acquire an IP address allocated by the network side to perform connection related to F1 signaling. When the IAB node acquires an IP address in an IAB-donor-CU based manner, it needs to send an IP address request message to the IAB-donor-CU to request one or more IP addresses. That is, after IAB-MT setup is completed, the IAB may send IP address request information to CUs of the IAB node, which may be frequently triggered, thereby increasing resource overhead.

As shown in fig. 4, an embodiment of the present application further provides an IP address requesting method applied to a self-backhauled IAB node, including:

step 401, sending an IP address request message to an integrated unit CU (IAB-donor-CU) of an IAB host node and starting an IP request prohibit timer; wherein the IAB node prohibits sending IP address request messages during the operation of the IP request prohibit timer.

The embodiment of the application limits the sending condition of the IP address request message by introducing the IP request forbidding timer, effectively reduces the triggering frequency of the message and saves resources.

As an alternative embodiment, the IP address request message is an RRC message decoupled from an RRC configuration/reconfiguration message; the decoupling means that the IP address request message and the RRC configuration/reconfiguration message are not related and do not affect each other.

Or, the IP address request message is enhanced terminal assistance information (UEAssistanceInformation);

or, the IP address request message is an RRC reconfiguration complete (rrcreconfigurable complete) message.

As an alternative embodiment, step 401 comprises:

after an RRC setting completion message in an initialization (integration) phase of an IAB node, sending an IP address request message to a CU of the IAB host node;

or,

after the initialization (integration) of the IAB node is completed, an IP address request message is sent to the CU of the IAB host node.

Optionally, the timing length of the IP request prohibit timer is determined by a protocol definition or a predefined determination or a network configuration determination or a network pre-configuration.

As an alternative embodiment, the method further comprises:

and after the IP request prohibition timer is overtime, if the IAB node has a new requirement for the IP address request, sending an IP address request message to a CU of the IAB host node and restarting the IP request prohibition timer.

In order to more clearly describe the IP address requesting method provided in this embodiment, the following description is made with reference to an example.

Example two

As shown in fig. 5, the IP address request process includes:

step 51, the IAB-MT is set to be finished, and an IP address request message can be sent to the IAB-donor-CU at any time later;

and step 52, after the IAB sends the IP address request message to the IAB-donor-CU, starting an IP request prohibition timer.

a) The value of the IP request prohibit timer is defined by the protocol (pre) or configured by the network (pre).

b) During the period of the IP request prohibit timer running, prohibiting any IP address request message from being sent;

c) when the IP request prohibit timer expires, if the IAB node has a new request for an IP address, the IAB node may resend the IP address request message and restart the IP request prohibit timer.

And step 53, after receiving the IP address request message, the IAB-donor-CU returns the information required by the IAB through the RRC reconfiguration message.

In summary, the embodiment of the present application introduces the IP request prohibit timer to limit the sending condition of the IP address request message, thereby effectively reducing the triggering frequency of the message and saving resources.

It should be noted that the capability interaction method provided by the embodiment of the present application and the IP address request method can be used in combination, and the following description is made in combination with an example alignment.

Example three

As shown in fig. 6, it includes the following steps:

step 61, a new IAB node starts to access the network, firstly, the IAB-MT sends an RRC setting request message to an IAB-donor-CU (CU of an IAB host node);

step 62, the IAB-donor-CU replies an RRC setting message to the IAB-MT;

step 63, the IAB-MT replies an RRC setting completion message to the IAB-donor-CU after receiving the RRC setting completion message;

a) the message carries an IAB (access point) indication domain (set to true), which indicates that the newly accessed equipment is an IAB;

b) in addition, the RRC setup complete message also carries a new domain (e.g., an IAB type indication domain); or an extension of some already existing domain, such as an extension to the IAB node indication domain;

the field may be represented by 2bits, such as estimated local-area, wide-area, or estimated local-area, or estimated wide-area. Indicating the type of the current IAB-MT by selecting value in the IAB-MT; alternatively, the format of the field may be represented by 1bit, such as estimated { true }; when the indicator exists (the existence can be true), the IAB-MT is the wide-area or the local-area.

Step 64, the IAB-MT is set to be finished, and an IP address request message can be sent to the IAB-donor-CU at any time later; and when the IAB sends an IP address request message to the IAB-donor-CU, starting an IP request prohibition timer.

a) The value of the IP request prohibit timer is defined by the protocol (pre) or configured by the network (pre).

b) During the period of the IP request prohibit timer running, prohibiting any IP address request message from being sent;

c) when the IP request prohibit timer expires, if the IAB node has a new request for an IP address, the IAB node may resend the IP address request message and restart the IP request prohibit timer.

And step 65, after receiving the IP address request message, the IAB-donor-CU returns the information required by the IAB through the RRC reconfiguration message.

In summary, the embodiment of the application indicates the type of the IAB-MT through the first message, so that the CU of the IAB host node can distinguish the type of the IAB-MT, thereby accurately knowing the capability of the IAB node and effectively controlling the IAB node; or, the first message contains the minimum capability set supported by the first information domain indication IAB-MT, so that the capability of the IAB node can be directly indicated and the IAB node can be effectively controlled; in addition, the sending condition of the IP address request message is limited by introducing an IP request forbidding timer, so that the triggering frequency of the message is effectively reduced, and the resources are saved.

As shown in fig. 7, an apparatus 700 for reporting capability is further provided in an embodiment of the present application, and is applied to a self-backhauled IAB node, where the IAB node includes an IAB-MT, including:

a first sending module 701, configured to send a first message to a centralized unit CU of an IAB host node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

Optionally, in the foregoing embodiment of the present application, if the first message is used to indicate the type of the IAB-MT, the first message is further used to indicate at least one of the following:

the type indicated by the first message corresponds to the minimum capability set supported by the IAB-MT;

and whether the IAB-MT corresponding to the type indicated by the first message has other capabilities to be reported except the minimum capability set supported by the IAB-MT.

Optionally, in the foregoing embodiment of the present application, the first message is a radio resource control RRC message.

Optionally, in the foregoing embodiment of the present application, the RRC message is any one of:

an RRC setup complete message;

a terminal information response message;

RRC reconfiguration complete message.

Optionally, in the foregoing embodiment of the present application, the type of the IAB-MT is indicated by a value of a second information field in the first message;

or,

indicating the type of the IAB-MT by whether a third information field exists in the first message;

or,

and indicating the type of the IAB-MT through whether a fourth information field exists or not under the condition that the first message contains an IAB node indication field.

Optionally, in the foregoing embodiment of the present application, when the type of the IAB-MT is indicated by a value of a second information field in the first message, the second information field is in an enumerated format, and the type of the IAB-MT is indicated by the enumerated format.

Optionally, in the foregoing embodiment of the present application, the first information field is in an integer format, and indicates, through an integer, a minimum capability set supported by the MT of the IAB node; wherein the integer indicates the sequence number of one of the minimum capability sets.

Optionally, in the foregoing embodiment of the present application, when the first message includes an IAB node indication field, the IAB node indication field is set to a selected format;

and the type of the IAB-MT is indicated through the value of the IAB node indication domain.

The capability reporting device provided in this embodiment of the application can implement each process implemented by the capability reporting device in the capability reporting method, and is not described here again to avoid repetition.

According to the method and the device, the type of the IAB-MT is indicated through the first message, so that the CU of the IAB host node can distinguish the type of the IAB-MT, the capability of the IAB node can be accurately known, and the IAB node can be effectively controlled; or, the first message contains the minimum capability set supported by the first information field indication IAB-MT, so that the capability of the IAB node can be directly indicated, and the IAB node can be effectively controlled.

As shown in fig. 8, an embodiment of the present application further provides a capability obtaining apparatus 800, applied to a self-backhauled IAB host node, including:

a receiving module 801, configured to receive a first message sent by an IAB node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

Optionally, in the foregoing embodiment of the present application, if the first message is used to indicate the type of the IAB-MT, the first message is further used to indicate at least one of the following:

the type indicated by the first message corresponds to the minimum capability set supported by the IAB-MT;

and whether the IAB-MT corresponding to the type indicated by the first message has other capabilities to be reported except the minimum capability set supported by the IAB-MT.

Optionally, in the foregoing embodiment of the present application, the first message is a radio resource control RRC message.

Optionally, in the foregoing embodiment of the present application, the RRC message is any one of:

an RRC setup complete message;

a terminal information response message;

RRC reconfiguration complete message.

Optionally, in the foregoing embodiment of the present application, the type of the IAB-MT is indicated by a value of a second information field in the first message;

or,

indicating the type of the IAB-MT by whether a third information field exists in the first message;

or,

and indicating the type of the IAB-MT through whether a fourth information field exists or not under the condition that the first message contains an IAB node indication field.

Optionally, in the foregoing embodiment of the present application, when the type of the IAB-MT is indicated by a value of a second information field in the first message, the second information field is in an enumerated format, and the type of the IAB-MT is indicated by the enumerated format.

Optionally, in the foregoing embodiment of the present application, the first information field is in an integer format, and indicates, through an integer, a minimum capability set supported by the MT of the IAB node; wherein the integer indicates the sequence number of one of the minimum capability sets.

Optionally, in the foregoing embodiment of the present application, when the first message includes an IAB node indication field, the IAB node indication field is set to a selected format;

and the type of the IAB-MT is indicated through the value of the IAB node indication domain.

The capability obtaining device provided in the embodiment of the present application can implement each process implemented by the capability obtaining device in the embodiment of the capability obtaining method, and is not described here again to avoid repetition.

According to the method and the device, the type of the IAB-MT is indicated through the first message, so that the CU of the IAB host node can distinguish the type of the IAB-MT, the capability of the IAB node can be accurately known, and the IAB node can be effectively controlled; or, the first message contains the minimum capability set supported by the first information field indication IAB-MT, so that the capability of the IAB node can be directly indicated, and the IAB node can be effectively controlled.

As shown in fig. 9, an IP address requesting apparatus 900 applied to a self-backhauled IAB node according to an embodiment of the present application includes:

a second sending module 901, configured to send an IP address request message to a centralized unit CU of an IAB host node;

the starting module is used for starting an IP request forbidding timer;

wherein the IAB node prohibits sending IP address request messages during the operation of the IP request prohibit timer.

Optionally, in the foregoing embodiment of the present application, the IP address request message is an RRC message decoupled from an RRC configuration/reconfiguration message;

or, the IP address request message is enhanced terminal assistance information;

or, the IP address request message is an RRC reconfiguration complete message.

Optionally, in the foregoing embodiment of the present application, sending an IP address request message to a CU of an IAB host node includes:

after an RRC setting completion message in an initialization phase of an IAB node, sending an IP address request message to a CU of the IAB host node;

or,

after initialization of the IAB node is complete, an IP address request message is sent to the CUs of the IAB host node.

Optionally, in the above embodiments of the present application, the timing length of the IP request prohibit timer is determined by a protocol definition or a predefined determination or a network configuration determination or a network pre-configuration determination.

Optionally, in the above embodiment of the present application, the apparatus further includes:

a third sending module, configured to send an IP address request message to a CU of an IAB host node if the IAB node has a new demand for an IP address request after the IP request prohibit timer expires;

and the restarting module is used for restarting the IP request forbidding timer.

The IP address requesting device provided in the embodiment of the present application can implement each process implemented by the IP address requesting device in the above IP address requesting method, and is not described here again to avoid repetition.

The embodiment of the application limits the sending condition of the IP address request message by introducing the IP request forbidding timer, effectively reduces the triggering frequency of the message and saves resources.

The capability reporting device, the capability acquiring device and/or the IP address requesting device in the embodiment of the present application may be devices, or may be components, integrated circuits, or chips in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine or a self-service machine, and the like, and the embodiments of the present application are not particularly limited.

The capability reporting device, the capability acquiring device and/or the IP address requesting device in the embodiment of the present application may be devices having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

Optionally, an embodiment of the present application further provides a self-backhauled IAB node, which includes a processor, a memory, and a program or an instruction stored in the memory and executable on the processor, where the program or the instruction, when executed by the processor, implements each process of the above capability reporting method embodiment, and can achieve the same technical effect, and details are not repeated here to avoid repetition.

Optionally, an embodiment of the present application further provides a self-feedback IAB node, where the IAB node is an IAB host node, and the IAB node includes a processor, a memory, and a program or an instruction stored in the memory and capable of running on the processor, and when the program or the instruction is executed by the processor, the program or the instruction implements each process of the above capability obtaining method embodiment, and can achieve the same technical effect, and in order to avoid repetition, the detailed description is not repeated here again

Optionally, an embodiment of the present application further provides a self-backhauled IAB node, which includes a processor, a memory, and a program or an instruction stored in the memory and executable on the processor, where the program or the instruction, when executed by the processor, implements each process of the above-mentioned IP address request method embodiment, and can achieve the same technical effect, and details are not described here to avoid repetition.

Fig. 10 is a hardware structure diagram of an IAB node for implementing various embodiments of the present application. The IAB node 1000 includes, but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010.

Those skilled in the art will appreciate that IAB node 1000 may further comprise a power supply (e.g., a battery) for supplying power to various components, and the power supply may be logically connected to processor 1010 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The electronic device structure shown in fig. 10 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is not repeated here.

The radio frequency unit 1001 is configured to send a first message to a central unit CU of an IAB host node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

Or, the radio frequency unit 1001 is configured to send an IP address request message to the central unit CU of the IAB host node and start an IP request prohibition timer;

wherein the IAB node prohibits sending IP address request messages during the operation of the IP request prohibit timer.

According to the method and the device, the type of the IAB-MT is indicated through the first message, so that the CU of the IAB host node can distinguish the type of the IAB-MT, the capability of the IAB node can be accurately known, and the IAB node can be effectively controlled; or, the first message contains the minimum capability set supported by the first information domain indication IAB-MT, so that the capability of the IAB node can be directly indicated and the IAB node can be effectively controlled; in addition, the sending condition of the IP address request message is limited by introducing an IP request forbidding timer, so that the triggering frequency of the message is effectively reduced, and the resources are saved.

It should be understood that, in the embodiment of the present application, the radio frequency unit 1001 may be used for receiving and sending signals during a message transmission or a call, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 1010; in addition, the uplink data is transmitted to the base station. In general, radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. Further, the radio frequency unit 1001 may also communicate with a network and other devices through a wireless communication system.

The electronic device provides wireless broadband internet access to the user through the network module 1002, such as assisting the user in sending and receiving e-mails, browsing web pages, and accessing streaming media.

The audio output unit 1003 may convert audio data received by the radio frequency unit 1001 or the network module 1002 or stored in the memory 1009 into an audio signal and output as sound. Also, the audio output unit 1003 can also provide audio output related to a specific function performed by the IAB node 1000 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 1003 includes a speaker, a buzzer, a receiver, and the like.

The input unit 1004 is used to receive an audio or video signal. The input Unit 1004 may include a Graphics Processing Unit (GPU) 10041 and a microphone 10042, the Graphics processor 10041 Processing image data of still pictures or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 1006. The image frames processed by the graphic processor 10041 may be stored in the memory 1009 (or other storage medium) or transmitted via the radio frequency unit 1001 or the network module 1002. The microphone 10042 can receive sound and can process such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 1001 in case of a phone call mode.

IAB node 1000 also includes at least one sensor 1005 such as light sensors, motion sensors, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 10061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 10061 and/or the backlight when the IAB node 1000 moves to the ear. As one type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the posture of an electronic device (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), and vibration identification related functions (such as pedometer, tapping); the sensors 1005 may also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be described in detail herein.

The display unit 1006 is used to display information input by the user or information provided to the user. The Display unit 1006 may include a Display panel 10061, and the Display panel 10061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 1007 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device. Specifically, the user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071, also referred to as a touch screen, may collect touch operations by a user on or near the touch panel 10071 (e.g., operations by a user on or near the touch panel 10071 using a finger, a stylus, or any other suitable object or attachment). The touch panel 10071 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 1010, and receives and executes commands sent by the processor 1010. In addition, the touch panel 10071 may be implemented by various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 10071, the user input unit 1007 can include other input devices 10072. Specifically, the other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a track ball, a mouse, and a joystick, which are not described herein again.

Further, the touch panel 10071 can be overlaid on the display panel 10061, and when the touch panel 10071 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 1010 to determine the type of the touch event, and then the processor 1010 provides a corresponding visual output on the display panel 10061 according to the type of the touch event. Although in fig. 10, the touch panel 10071 and the display panel 10061 are two independent components for implementing the input and output functions of the electronic device, in some embodiments, the touch panel 10071 and the display panel 10061 may be integrated to implement the input and output functions of the electronic device, and the implementation is not limited herein.

Interface unit 1008 interfaces external devices to IAB node 1000. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. Interface unit 1008 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within IAB node 1000 or may be used to transmit data between IAB node 1000 and an external device.

The memory 1009 may be used to store software programs as well as various data. The memory 1009 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, and the like), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 1009 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 1010 is a control center of the electronic device, connects various parts of the entire electronic device using various interfaces and lines, and performs various functions of the electronic device and processes data by operating or executing software programs and/or modules stored in the memory 1009 and calling data stored in the memory 1009, thereby integrally monitoring the electronic device. Processor 1010 may include one or more processing units; preferably, the processor 1010 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 1010.

IAB node 1000 may also include a power supply (e.g., a battery) to power the various components, which may preferably be logically coupled to processor 1010 via a power management system to manage charging, discharging, and power consumption management functions via the power management system.

In addition, IAB node 1000 includes some functional blocks not shown, which are not described herein.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above capability reporting method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above capability obtaining method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above-mentioned IP address request method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, to implement each process of the capability reporting method embodiment, and achieve the same technical effect, and in order to avoid repetition, the description is omitted here.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above capability obtaining method embodiment, and can achieve the same technical effect, and is not described herein again to avoid repetition.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above-mentioned IP address request method embodiment, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (31)

1. A capability reporting method is applied to a self-backhauled IAB node, the IAB node includes an IAB-MT, and the method comprises the following steps:

sending a first message to a Centralized Unit (CU) of an IAB host node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

2. The method of claim 1, wherein if the first message is used to indicate the type of the IAB-MT, the first message is further used to indicate at least one of:

the type indicated by the first message corresponds to the minimum capability set supported by the IAB-MT;

and whether the IAB-MT corresponding to the type indicated by the first message has other capabilities to be reported except the minimum capability set supported by the IAB-MT.

3. The method of claim 1, wherein the first message is a Radio Resource Control (RRC) message.

4. The method according to claim 3, wherein the RRC message is any one of the following:

an RRC setup complete message;

a terminal information response message;

RRC reconfiguration complete message.

5. The method according to claim 1 or 2,

indicating the type of the IAB-MT through the value of a second information field in the first message;

or,

indicating the type of the IAB-MT by whether a third information field exists in the first message;

or,

and indicating the type of the IAB-MT through whether a fourth information field exists or not under the condition that the first message contains an IAB node indication field.

6. The method of claim 5, wherein when the type of the IAB-MT is indicated by a value of a second information field in the first message, the second information field is in an enumerated format, and the type of the IAB-MT is indicated by the enumerated format.

7. The method of claim 1 wherein the first information field is in integer format, indicating by integer the minimum set of capabilities supported by the MT of the IAB node; wherein the integer indicates the sequence number of one of the minimum capability sets.

8. The method according to claim 1 or 2,

setting the IAB node indication domain to be a selected format under the condition that the first message contains the IAB node indication domain;

and the type of the IAB-MT is indicated through the value of the IAB node indication domain.

9. A capability obtaining method applied to a self-backhauled IAB host node is characterized by comprising the following steps:

receiving a first message sent by an IAB node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

10. The method of claim 9, wherein if the first message is used to indicate the type of IAB-MT, the first message is further used to indicate at least one of:

the type indicated by the first message corresponds to the minimum capability set supported by the IAB-MT;

and whether the IAB-MT corresponding to the type indicated by the first message has other capabilities to be reported except the minimum capability set supported by the IAB-MT.

11. The method of claim 9, wherein the first message is an RRC message.

12. The method according to claim 11, wherein the RRC message is any one of:

an RRC setup complete message;

a terminal information response message;

RRC reconfiguration complete message.

13. The method according to claim 9 or 10,

indicating the type of the IAB-MT through the value of a second information field in the first message;

or,

indicating the type of the IAB-MT by whether a third information field exists in the first message;

or,

and indicating the type of the IAB-MT through whether a fourth information field exists or not under the condition that the first message contains an IAB node indication field.

14. The method of claim 13, wherein when the type of the IAB-MT is indicated by a value of a second information field in the first message, the second information field is in an enumerated format, and the type of the IAB-MT is indicated by the enumerated format.

15. The method of claim 9 wherein the first information field is in integer format, and indicates a minimum set of capabilities supported by the MT of the IAB node via an integer; wherein the integer indicates the sequence number of one of the minimum capability sets.

16. The method according to claim 9 or 10, wherein in case the first message contains an IAB node indication field, setting the IAB node indication field to a selected format;

and the type of the IAB-MT is indicated through the value of the IAB node indication domain.

17. An IP address requesting method applied to a self-backhauled IAB node, comprising:

sending an IP address request message to a centralized unit CU of an IAB host node and starting an IP request prohibition timer;

wherein the IAB node prohibits sending IP address request messages during the operation of the IP request prohibit timer.

18. The method of claim 17,

the IP address request message is an RRC message decoupled from an RRC configuration/reconfiguration message;

or, the IP address request message is enhanced terminal assistance information;

or, the IP address request message is an RRC reconfiguration complete message.

19. The method of claim 17 wherein sending an IP address request message to a centralized unit, CU, of an IAB host node comprises:

after an RRC setting completion message in an initialization phase of an IAB node, sending an IP address request message to a CU of the IAB host node;

or,

after initialization of the IAB node is complete, an IP address request message is sent to the CUs of the IAB host node.

20. The method of claim 17, wherein a timing length of the IP request prohibit timer is determined by a protocol definition or a predefined determination or a network configuration determination or a network pre-configuration.

21. The method of claim 17, further comprising:

and after the IP request prohibition timer is overtime, if the IAB node has a new requirement for the IP address request, sending an IP address request message to a CU of the IAB host node and restarting the IP request prohibition timer.

22. A capability reporting apparatus applied to a self-backhauled IAB node, the IAB node comprising an IAB-MT, the apparatus comprising:

a first sending module, configured to send a first message to a centralized unit CU of an IAB host node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

23. The apparatus of claim 22, wherein if the first message is used to indicate the type of IAB-MT, the first message is further used to indicate at least one of:

the type indicated by the first message corresponds to the minimum capability set supported by the IAB-MT;

and whether the IAB-MT corresponding to the type indicated by the first message has other capabilities to be reported except the minimum capability set supported by the IAB-MT.

24. The apparatus of claim 22 or 23,

indicating the type of the IAB-MT through the value of a second information field in the first message;

or,

indicating the type of the IAB-MT by whether a third information field exists in the first message;

or,

and indicating the type of the IAB-MT through whether a fourth information field exists or not under the condition that the first message contains an IAB node indication field.

25. A capability obtaining apparatus applied to a self-backhauled IAB host node, comprising:

a receiving module, configured to receive a first message sent by an IAB node;

wherein the first message is used for indicating the type of the IAB-MT, and/or the first message comprises a first information field used for indicating the minimum capability set supported by the IAB-MT.

26. The apparatus of claim 25, wherein if the first message is used to indicate the type of IAB-MT, the first message is further used to indicate at least one of:

the type indicated by the first message corresponds to the minimum capability set supported by the IAB-MT;

and whether the IAB-MT corresponding to the type indicated by the first message has other capabilities to be reported except the minimum capability set supported by the IAB-MT.

27. The apparatus of claim 25 or 26,

indicating the type of the IAB-MT through the value of a second information field in the first message;

or,

indicating the type of the IAB-MT by whether a third information field exists in the first message;

or,

and indicating the type of the IAB-MT through whether a fourth information field exists or not under the condition that the first message contains an IAB node indication field.

28. An IP address requesting device applied to a self-backhauled IAB node, comprising:

a second sending module, configured to send an IP address request message to a CU, which is a central unit of an IAB host node;

the starting module is used for starting an IP request forbidding timer;

wherein the IAB node prohibits sending IP address request messages during the operation of the IP request prohibit timer.

29. The apparatus of claim 28, further comprising:

a third sending module, configured to send an IP address request message to a CU of an IAB host node if the IAB node has a new demand for an IP address request after the IP request prohibit timer expires;

and the restarting module is used for restarting the IP request forbidding timer.

30. A self-backhauled IAB node, comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the capability reporting method according to any of claims 1 to 8; or, the program or instructions, when executed by the processor, implement the steps of the capability acquisition method of any of claims 9 to 16; alternatively, the program or instructions, when executed by the processor, implement the steps of the IP address requesting method of any of claims 17-21.

31. A readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the capability reporting method according to any one of claims 1 to 8; or the program or instructions, when executed by a processor, implement the steps of the capability acquisition method of any of claims 9-16; alternatively, the program or instructions, when executed by a processor, implement the steps of the IP address requesting method of any of claims 17-21.

Images