Authorization method and apparatus

Abstract

Disclosed in embodiments of the present invention are an authorization method and an apparatus, applicable to the scenario supporting integrated access and backhaul (IAB). The method comprises: a first node receives first information from a second node, the first information being information related to authorization of a mobile IAB node; and the first node determines, on the basis of the first information, whether the mobile IAB node is authorized to provide service to a terminal device. By implementing the embodiments of the present invention, a first node can obtain information related to authorization of a mobile IAB node, the first node determines, on the basis of the information, whether the mobile IAB node is authorized to provide service to a terminal device, and the terminal device can use the service provided by the mobile IAB node, such that the terminal device can obtain better communication connection by means of the mobile IAB node, thereby ensuring the service continuity and an access success rate of the terminal device, and improving user experience.

Description

Authorization method and apparatus thereof TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and in particular to an authorization method and apparatus thereof. BACKGROUND

[0002] In the related art, in an initial integration scenario of mobile IAB (Integrated access and backhaul), an IAB-MT (IAB-Mobile Termination) in a mobile IAB node (Mobile IAB-node, also called MBSR or VMR) and an IAB-DU (IAB-distributed unit) in the mobile IAB node can be integrated into different donor-CUs (donor-centralized unit, also called donor-control unit). In a migration scenario of mobile IAB, the IAB-MT in the mobile IAB node and the IAB-DU in the mobile IAB node can also be migrated to different donor-CUs.

[0003] However, when the donor-CU of the IAB-MT is different from the donor-CU of the IAB-DU, how to make the mobile IAB nodes corresponding to the IAB-MT and the IAB-DU provide services to terminal devices has become a problem to be solved.

[0004] SUMMARY

[0005] The present disclosure provides an authorization method and apparatus thereof.

[0006] According to a first aspect of the present disclosure, an authorization method is provided, the method is performed by a first node, and the method comprises:

[0007] receiving first information from a second node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node;

[0008] determining, according to the first information, whether the mobile IAB node is authorized to provide services to a terminal device.

[0009] According to a second aspect of the present disclosure, an authorization method is provided, the method is performed by a second node, and the method comprises:

[0010] sending first information to a first node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0011] According to a third aspect of embodiments of the disclosure, a method for authorization is provided, the method is performed by a third node, and the method comprises:

[0012] sending, to a second node, identification information for the authorization request, the identification information being used by the second node to send first information to a first node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device.

[0013] According to a fourth aspect of embodiments of the disclosure, a method for authorization is provided, the method is performed by a third node, and the method comprises:

[0014] sending, by a second node, first information to a first node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device.

[0015] According to a fifth aspect of embodiments of the disclosure, a method for authorization is provided, the method is performed by a third node, and the method comprises:

[0016] sending, to a first node, third information, the third information being used by the first node to send second information to a second node, the second information being used by the second node to send first information to the first node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device.

[0017] According to a sixth aspect of embodiments of the disclosure, a method for authorization is provided, the method is used in a communication system, and the method comprises:

[0018] sending, by a second node, first information to a first node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node;

[0019] receiving, by the first node, the first information, and determining, by the first node, whether the mobile IAB node is authorized to provide service to a terminal device according to the first information.

[0020] According to a seventh aspect of embodiments of the disclosure, a first communication apparatus is provided, the apparatus comprises:

[0021] a transceiver, configured to receive, from a second node, first information, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node;

[0022] a processing module, configured to determine, according to the first information, whether the mobile IAB node is authorized to provide services to a terminal device.

[0023] According to an eighth aspect of an embodiment of the present disclosure, a first communication apparatus is provided, the apparatus comprising:

[0024] a transceiver, configured to send, to a first node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0025] According to a ninth aspect of an embodiment of the present disclosure, a third communication apparatus is provided, the apparatus comprising:

[0026] a transceiver, configured to send, to a second node, identification information for an authorization request, wherein the identification information is used by the second node to send, to a first node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0027] According to a tenth aspect of an embodiment of the present disclosure, a fourth communication apparatus is provided, the apparatus comprising:

[0028] a transceiver, configured to send, to a first node via a second node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0029] According to an eleventh aspect of an embodiment of the present disclosure, a fifth communication apparatus is provided, the apparatus comprising:

[0030] a transceiver, configured to send, to a first node, third information used by the first node to send, to a second node, second information used by the second node to send, to the first node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0031] According to a twelfth aspect of an embodiment of the present disclosure, a communication apparatus is provided, comprising:

[0032] one or more processors;

[0033] The processor is configured to invoke instructions to enable the communication device to perform the optional implementation manners of the first aspect, the second aspect, the third aspect, the fourth aspect, and the fifth aspect.

[0034] According to a thirteenth aspect of the embodiments of the present disclosure, a communication system is provided, comprising: a first node and a second node, wherein the first node is configured to implement the authorization method of the first aspect, and the second node is configured to implement the authorization method of the second aspect.

[0035] According to a fourteenth aspect of the embodiments of the present disclosure, a storage medium is provided, which stores instructions, when the instructions run on a communication device, enable the communication device to perform the optional implementation manners of the first aspect, the second aspect, the third aspect, the fourth aspect, and the fifth aspect.

[0036] According to the technical solutions of the present disclosure, the first node can obtain information related to the authorization of the mobile IAB node, so as to facilitate the first node to determine whether the mobile IAB node is authorized to provide services to the terminal device according to the information, and facilitate the terminal device to use the services provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, ensure the service continuity and access success rate of the terminal device, and improve the user experience. BRIEF DESCRIPTION OF DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following describes the drawings required for the embodiments, and the following drawings are only some embodiments of the present disclosure, and do not specifically limit the protection scope of the present disclosure.

[0038] FIG. 1a is an example diagram of an integrated access and backhaul (IAB) architecture according to an embodiment of the present disclosure;

[0039] FIG. 1b is an example diagram of an integrated access and backhaul (IAB) architecture according to an embodiment of the present disclosure;

[0040] FIG. 1c is an example diagram of signaling during IAB-node integration according to an embodiment of the present disclosure;

[0041] FIG. 1d is an example diagram of a donor-CU of an IAB-MT and a donor-CU of an IAB-DU before migration according to an embodiment of the present disclosure;

[0042] FIG. 1e is an example diagram of a donor-CU of an IAB-MT and a donor-CU of an IAB-DU after partial migration according to an embodiment of the present disclosure;

[0043] FIG. 2 is an architecture diagram of a communication system 200, according to embodiments of the present disclosure;

[0044] FIG. 3 is an architecture diagram of a communication system 300, according to embodiments of the present disclosure;

[0045] FIG. 4a is an interaction diagram of an authorization method, according to embodiments of the present disclosure;

[0046] FIG. 4b is an interaction diagram of an authorization method, according to embodiments of the present disclosure;

[0047] FIG. 4c is an interaction diagram of an authorization method, according to embodiments of the present disclosure;

[0048] FIG. 5a is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0049] FIG. 5b is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0050] FIG. 5c is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0051] FIG. 6a is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0052] FIG. 6b is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0053] FIG. 6c is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0054] FIG. 7a is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0055] FIG. 7b is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0056] FIG. 7c is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0057] FIG. 8a is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0058] FIG. 8b is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0059] FIG. 8c is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0060] FIG. 8d is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0061] FIG. 8e is a flow diagram of an authorization method, according to embodiments of the present disclosure;

[0062] FIG. 9a is a structural schematic diagram of a communication apparatus 9100 according to an embodiment of the present disclosure;

[0063] FIG. 9b is a structural schematic diagram of a communication apparatus 9200 according to an embodiment of the present disclosure;

[0064] FIG. 9c is a structural schematic diagram of a chip 9300 according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0065] The embodiments of the present disclosure provide an authorization method and apparatus.

[0066] In a first aspect, the embodiments of the present disclosure provide an authorization method, the method is performed by a first node, and the method comprises:

[0067] receiving first information from a second node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node;

[0068] determining, according to the first information, whether the mobile IAB node is authorized to provide services to a terminal device.

[0069] In the above embodiments, the first node can obtain information related to authorization of a mobile IAB node, so that the first node can determine, according to the information, whether the mobile IAB node is authorized to provide services to a terminal device, and the terminal device can use the services provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, guarantee service continuity and access success rate of the terminal device, and improve user experience.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the first information comprises at least one of the following information:

[0071] authorization information;

[0072] an identifier of an integrated access and backhaul node (IAB-node ID);

[0073] information for indicating authorization failure.

[0074] In some embodiments, the information for indicating authorization failure can be a cause value in a request failure, for example, the cause value is set as “unauthorized”.

[0075] In the above embodiments, through one or more of the authorization information, the IAB-node ID and the information for indicating authorization failure in the first information, the first node can more accurately determine whether the mobile IAB node is authorized to provide services to the terminal device.

[0076] In some embodiments of the first aspect, in some embodiments, the IAB-node ID comprises any one of the following:

[0077] a global identity of an integrated access and backhaul mobile termination (IAB-MT);

[0078] a terminal identity (UE ID) of the IAB-MT over an Xn interface application protocol (XnAP);

[0079] a UE ID of the IAB-MT over a next generation interface application protocol (NGAP);

[0080] a UE ID of the IAB-MT over a F1 interface application protocol (F1AP);

[0081] a backhaul adaptation protocol (BAP) address.

[0082] In the above embodiments, the IAB-node ID can make the first node more certain which mobile IAB node is authorized to provide services to the terminal device or is not authorized to provide services to the terminal device, and can improve the accuracy of the judgment of the first node.

[0083] In some embodiments of the first aspect, in some embodiments, the first node is a F1-terminating-donor-CU (in the present disclosure, the F1-terminating-donor-CU refers to a donor-CU connected with an IAB-DU of an IAB-node, which can also be referred to as a F1-terminating-donor, an IAB-donor, or an IAB-donor-CU), and the second node is a RRC-terminating-donor-CU (in the present disclosure, the RRC-terminating-donor-CU refers to a donor-CU connected with an IAB-MT of an IAB-node, which can also be referred to as a RRC-terminating-donor, an IAB-donor, or an IAB-donor-CU); or,

[0084] the first node is a F1-terminating-donor-CU, and the second node is an access and mobility management function (AMF); or,

[0085] the first node is a F1-terminating-donor-CU, and the second node is an integrated access and backhaul node (IAB-node) (in the present disclosure, the IAB-node can also be an MBSR, a VMR, or a mobile IAB-node).

[0086] In some embodiments combined with the first aspect, in some embodiments, the receiving the first information from the second node comprises:

[0087] sending second information to the second node, the second information being used by the second node to send the first information to the first node.

[0088] In the above embodiments, the first node can send the second information to the second node, so that the second node sends the above-mentioned first information to the first node in response to the second information of the first node, thereby ensuring that the first node can obtain information related to the authorization of the mobile IAB node, facilitating the first node to determine whether the mobile IAB node is authorized to provide services to the terminal device according to the information, facilitating the terminal device to use the services provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, ensuring the service continuity and access success rate of the terminal device, and improving the user experience.

[0089] In some embodiments combined with the first aspect, in some embodiments, the second information comprises at least one of the following information:

[0090] an IAB-node ID, used to indicate the identity of an integrated access and backhaul node IAB-node or an IAB-MT or an integrated access and backhaul distributed unit IAB-DU in the IAB-node, which makes the authorization request;

[0091] an authorization information request indication;

[0092] request information related to authorization.

[0093] In the above embodiments, by sending one or more of the IAB-node ID, the authorization information request indication, and the request information related to authorization to the second node, the second node can send the first information to the first node, thereby ensuring that the first node can obtain information related to the authorization of the mobile IAB node, facilitating the first node to determine whether the mobile IAB node is authorized to provide services to the terminal device according to the information, facilitating the terminal device to use the services provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, ensuring the service continuity and access success rate of the terminal device, and improving the user experience.

[0094] In some embodiments combined with the first aspect, in some embodiments, the first node is an F1-terminating-donor-CU, and the second node is an access and mobility management function AMF; and the sending the second information to the second node comprises:

[0095] receiving third information from a third node;

[0096] According to the third information, the second information is sent to the second node.

[0097] In the above embodiment, the first node receives third information from the third node, and sends the second information to the second node according to the third information, so that the first node can send one or more of the IAB-node ID, the authorization information request indication, and the request information related to the authorization to the second node, which can help the second node to send the first information to the first node, so as to ensure that the first node can obtain the information related to the authorization of the mobile IAB node, so as to facilitate the first node to determine whether the mobile IAB node is authorized to provide services to the terminal device according to the information, and facilitate the terminal device to use the services provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, ensure the service continuity and access success rate of the terminal device, and improve the user experience.

[0098] In combination with some embodiments of the first aspect, in some embodiments, the third information includes at least one of the following information:

[0099] The identifier of the second node, used to indicate the identifier of a donor-CU of an IAB-DU;

[0100] The IAB-node ID.

[0101] In some embodiments, the identifier of the second node can be an NG-RAN node ID of the second node; in other embodiments, the identifier of the second node can be a cell identifier (NCGI, NR cell global identity) under the second node and an NG-RAN node ID length, which can be determined according to the CGI and the gNB length.

[0102] In the above embodiment, the first node can accurately send the second information to the second node through the identifier of the second node and / or the IAB-node ID, so as to improve the accuracy of the first node in providing information to the second node.

[0103] In combination with some embodiments of the first aspect, in some embodiments, the third node is any one of the following:

[0104] The IAB-node;

[0105] The RRC-terminating-donor-CU.

[0106] In a second aspect, the embodiments of the present disclosure provide an authorization method, which is performed by a second node, and the method comprises:

[0107] sending first information to a first node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device.

[0108] In the above embodiments, the first node can obtain information related to authorization of a mobile IAB node, so that the first node can determine whether the mobile IAB node is authorized to provide service to a terminal device according to the information, and the terminal device can use the service provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, ensure service continuity and access success rate of the terminal device, and improve user experience.

[0109] In some embodiments in combination with the second aspect, in some embodiments, the first information includes at least one of the following information:

[0110] authorization information;

[0111] an identity of an integrated access and backhaul node, IAB-node ID;

[0112] information indicating authorization failure.

[0113] In some embodiments in combination with the second aspect, in some embodiments, the IAB-node ID includes any one of the following:

[0114] a global identity of an integrated access and backhaul mobile terminal, IAB-MT;

[0115] a terminal identity of the IAB-MT on an Xn interface application protocol, XnAP, UE ID;

[0116] a UE ID of the IAB-MT on a next generation interface application protocol, NGAP;

[0117] a UE ID of the IAB-MT on an F1 interface application protocol, F1AP;

[0118] a backhaul adaptation protocol address, BAP address.

[0119] In some embodiments in combination with the second aspect, in some embodiments, the first node is an F1-terminating-donor-CU, and the second node is an RRC-terminating-donor-CU; or the first node is an F1-terminating-donor-CU, and the second node is an access and mobility management function, AMF.

[0120] In some embodiments of the second aspect, the sending the first information to the first node comprises:

[0121] receiving second information sent by the first node, and sending the first information to the first node according to the second information.

[0122] In some embodiments of the second aspect, the second information comprises at least one of:

[0123] an IAB-node ID, used to indicate an identity of an Integrated Access and Backhaul node (IAB-node) or an IAB-MT or an Integrated Access and Backhaul Distributed Unit (IAB-DU) in the IAB-node, for which the authorization request is made;

[0124] an authorization information request indication;

[0125] request information related to authorization.

[0126] In some embodiments of the second aspect, the sending the first information to the first node comprises:

[0127] receiving, from a third node, identification information for the authorization request, and sending the first information to the first node according to the identification information.

[0128] In some embodiments of the second aspect, the third node is any one of:

[0129] an Integrated Access and Backhaul node (IAB-node);

[0130] an IAB-MT;

[0131] an IAB-DU;

[0132] an Operation Administration and Maintenance (OAM);

[0133] a donor Central Unit (CU) of the IAB-MT.

[0134] In some embodiments of the second aspect, the identification information comprises at least one of:

[0135] a Next Generation Radio Access Network node ID (NG-RAN node ID), used to indicate an identity of a donor-CU of the IAB-DU;

[0136] a New Radio Cell Global ID (NCGI) and a NG-RAN node ID length, used to indicate an identity of a donor-CU of the IAB-DU;

[0137] IAB-node ID, used to indicate an identity of the IAB-node, or an IAB-MT or an IAB-DU in the IAB-node.

[0138] With reference to the second aspect, in some embodiments, the first node is an F1-terminating-donor-CU, and the second node is an integrated access and backhaul node, IAB-node.

[0139] With reference to the second aspect, in some embodiments, the sending, to the first node, of the first information comprises:

[0140] receiving, from a third node, the first information, and sending the first information to the first node.

[0141] With reference to the second aspect, in some embodiments, the third node is a donor-CU of the IAB-MT.

[0142] In a third aspect, the embodiments of the present disclosure provide an authorization method, the method is performed by a third node, and the method comprises:

[0143] sending, to a second node, identification information for an authorization request, the identification information being used by the second node to send, to a first node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0144] In the above embodiments, by sending, by the third node, the identification information for the authorization request to the second node, the first node can obtain the information related to the authorization of the mobile IAB node, so as to facilitate the first node to determine whether the mobile IAB node is authorized to provide services to the terminal device according to the information, and facilitate the terminal device to use the services provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, ensure the service continuity and access success rate of the terminal device, and improve the user experience.

[0145] With reference to the third aspect, in some embodiments, the first information comprises at least one of the following information:

[0146] authorization information;

[0147] an identity of an integrated access and backhaul node, IAB-node ID;

[0148] information used to indicate an authorization failure.

[0149] In some embodiments of the third aspect, in some embodiments, the IAB-node ID comprises any one of the following:

[0150] a global identity of an integrated access and backhaul mobile termination, IAB-MT;

[0151] a terminal identity, UE ID, of the IAB-MT over an Xn interface application protocol, XnAP;

[0152] a UE ID of the IAB-MT over a next generation interface application protocol, NGAP;

[0153] a UE ID of the IAB-MT over a F1 interface application protocol, F1AP;

[0154] a backhaul adaptation protocol address, BAP address.

[0155] In some embodiments of the third aspect, in some embodiments, the identity information comprises at least one of the following:

[0156] a next generation radio access network node identity, NG-RAN node ID, indicating an identity of a donor central unit, CU, of an integrated access and backhaul distributed unit, IAB-DU;

[0157] a new generation cell global identity, NCGI, and a length of the NG-RAN node ID, indicating the identity of the donor-CU of the IAB-DU;

[0158] an IAB-node ID, indicating an identity of an integrated access and backhaul node, IAB-node, or an IAB-MT or an IAB-DU in the IAB-node.

[0159] In some embodiments of the third aspect, in some embodiments, the first node is a F1-terminating-donor-CU, the second node is a radio resource control-terminating-donor-CU, and the third node is an IAB-MT or an operation administration and maintenance, OAM; or the first node is a F1-terminating-donor-CU, the second node is an AMF, and the third node is an IAB-MT or a radio resource control-terminating-donor-CU.

[0160] In a fourth aspect, the embodiments of the present disclosure provide an authorization method, the method is performed by a third node, and the method comprises:

[0161] sending, by a second node, first information to a first node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device.

[0162] In the above embodiments, the third node sends the first information to the first node through the second node, which enables the first node to obtain information related to authorization of a mobile IAB node, facilitates the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device according to the information, and facilitates the terminal device to use the service provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, ensures service continuity and access success rate of the terminal device, and improves user experience.

[0163] In combination with some embodiments of the fourth aspect, in some embodiments, the first information includes at least one of the following information:

[0164] authorization information;

[0165] an identifier of an integrated access and backhaul node, IAB-node ID;

[0166] information indicating authorization failure.

[0167] In combination with some embodiments of the fourth aspect, in some embodiments, the IAB-node ID includes any of the following:

[0168] a global identifier of an integrated access and backhaul mobile terminal, IAB-MT;

[0169] a terminal identifier, UE ID, of the IAB-MT on an Xn interface application protocol, XnAP;

[0170] a UE ID of the IAB-MT on a next generation interface application protocol, NGAP;

[0171] a UE ID of the IAB-MT on an F1 interface application protocol, F1AP;

[0172] a backhaul adaptation protocol address, BAP address.

[0173] In combination with some embodiments of the fourth aspect, in some embodiments, the first node is an F1-terminating-donor-CU, the second node is an integrated access and backhaul node, IAB-node, and the third node is a donor-CU of an IAB-MT.

[0174] In a fifth aspect, the embodiments of the present disclosure provide an authorization method, the method being performed by a third node, and the method comprising:

[0175] sending, to the first node, third information, the third information being used for the first node to send, to a second node, second information, the second information being used for the second node to send, to the first node, first information, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used for the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device.

[0176] In the above embodiments, the third node sends, to the first node, the third information, which can make the first node send, to the second node, the second information, and the second node sends, to the first node, the first information according to the second information, so that the first node can obtain the information related to authorization of the mobile IAB node, which facilitates the first node to determine whether the mobile IAB node is authorized to provide service to the terminal device according to the information, and facilitates the terminal device to use the service provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, ensures service continuity and access success rate of the terminal device, and improves user experience.

[0177] In some embodiments in combination with the fifth aspect, in some embodiments, the first information includes at least one of the following information:

[0178] authorization information;

[0179] an identity of an integrated access and backhaul node, IAB-node ID;

[0180] information used for indicating authorization failure.

[0181] In some embodiments in combination with the fifth aspect, in some embodiments, the IAB-node ID includes any one of the following:

[0182] a global identity of an integrated access and backhaul mobile terminal, IAB-MT;

[0183] a terminal identity, UE ID, of the IAB-MT on an Xn interface application protocol, XnAP;

[0184] a UE ID of the IAB-MT on a next generation interface application protocol, NGAP;

[0185] a UE ID of the IAB-MT on an F1 interface application protocol, F1AP;

[0186] a backhaul adaptation protocol address, BAP address.

[0187] In some embodiments in combination with the fifth aspect, in some embodiments, the third information includes at least one of the following information:

[0188] an identity of the second node, used to indicate an identity of a donor central unit, donor-CU, hosting an integrated access and backhaul distributed unit, IAB-DU;

[0189] IAB-node ID.

[0190] In some embodiments of the fifth aspect, the first node is an F1-terminating-donor-CU, the second node is an AMF, and the third node is an IAB-node or an RRC-terminating-donor-CU.

[0191] In a sixth aspect, the embodiments of the present disclosure provide an authorization method for a communication system, the method comprising:

[0192] The second node sends first information to the first node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node.

[0193] The first node receives the first information and determines, according to the first information, whether the mobile IAB node is authorized to provide services to a terminal device.

[0194] In the above embodiments, the first node can obtain information related to authorization of a mobile IAB node, so that the first node can determine, according to the information, whether the mobile IAB node is authorized to provide services to a terminal device, and the terminal device can use the services provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, ensuring service continuity and access success rate of the terminal device and improving user experience.

[0195] In a seventh aspect, the embodiments of the present disclosure provide a first communication device, the device comprising:

[0196] The transceiver module is configured to receive first information from a second node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node.

[0197] The processing module is configured to determine, according to the first information, whether the mobile IAB node is authorized to provide services to a terminal device.

[0198] In an eighth aspect, the embodiments of the present disclosure provide a second communication device, the device comprising:

[0199] The transceiver module is configured to send first information to the first node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0200] In a ninth aspect, an embodiment of the present disclosure provides a third communication device, which comprises:

[0201] The transceiver module is configured to send identification information for authorization request to the second node, the identification information being used by the second node to send first information to the first node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0202] In a tenth aspect, an embodiment of the present disclosure provides a fourth communication device, which comprises:

[0203] The transceiver module is configured to send first information to the first node through the second node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0204] In an eleventh aspect, an embodiment of the present disclosure provides a fifth communication device, which comprises:

[0205] The transceiver module is configured to send third information to the first node, the third information being used by the first node to send second information to the second node, the second information being used by the second node to send first information to the first node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device.

[0206] In a twelfth aspect, an embodiment of the present disclosure provides a first node, comprising: one or more processors; wherein the processor is configured to invoke instructions to cause the first node to perform the optional implementation manners of the first aspect.

[0207] In a thirteenth aspect, an embodiment of the present disclosure provides a second node, comprising: one or more processors; wherein the processor is configured to invoke instructions to cause the second node to perform the optional implementation manners of the second aspect.

[0208] In a fourteenth aspect, an embodiment of the present disclosure provides a first network element, comprising: one or more processors; wherein the processor is configured to invoke instructions to cause the first network element to perform the optional implementation manners of the third aspect.

[0209] In a fifteenth aspect, the embodiments of the present disclosure provide a third node, comprising: one or more processors; wherein the processor is configured to invoke instructions to cause the third node to perform the method described in the optional implementation manners of the fourth aspect and the fifth aspect.

[0210] In a sixteenth aspect, the embodiments of the present disclosure provide a communication system, comprising: a first node and a second node, wherein the first node is configured to perform the method described in the optional implementation manners of the first aspect, and the second node is configured to perform the method described in the optional implementation manners of the second aspect.

[0211] In a seventeenth aspect, the embodiments of the present disclosure provide a storage medium, which stores instructions, when the instructions run on a communication device, cause the communication device to perform the method described in the optional implementation manners of the first aspect, the second aspect, the third aspect, the fourth aspect, and the fifth aspect.

[0212] In an eighteenth aspect, the embodiments of the present disclosure provide a program product, when the program product is executed by a communication device, causes the communication device to perform the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, and the fifth aspect.

[0213] In a nineteenth aspect, the embodiments of the present disclosure provide a computer program, when the computer program runs on a computer, causes the computer to perform the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, and the fifth aspect.

[0214] In a twentieth aspect, the embodiments of the present disclosure provide a chip or a chip system. The chip or the chip system comprises processing circuitry configured to perform the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, and the fifth aspect.

[0215] It can be understood that the first node, the second node, the first network element, the communication device, the communication device, the communication system, the storage medium, the program product, the computer program, the chip or the chip system are all used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method, which will not be described here.

[0216] The embodiments of the present disclosure propose an authorization method and an apparatus thereof. In some embodiments, the authorization method and the information processing method, the communication method, and the like can be replaced with each other, the authorization apparatus and the information processing apparatus, the communication apparatus, and the like can be replaced with each other, and the information processing system, the communication system, and the like can be replaced with each other.

[0217] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing part of the steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, part or all steps of different embodiments can be combined arbitrarily, an embodiment can be combined with optional implementation of other embodiments.

[0218] In each embodiment of the present disclosure, the terms and / or descriptions between the embodiments are consistent if there is no special description and logical conflict, and can be referred to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0219] The terms used in the embodiments of the present disclosure are only for the purpose of describing the specific embodiments, and not as a limitation on the present disclosure.

[0220] In the embodiments of the present disclosure, unless otherwise specified, the elements expressed in singular form, such as "one", "a", "the", "above", "said", "preceding", "this" and the like, can represent "one and only one", and can also represent "one or more", "at least one" and the like. For example, in the case of using articles such as "a", "an", "the" and the like in English, the noun after the article can be understood as singular expression, and can also be understood as plural expression.

[0221] In the embodiments of the present disclosure, "a plurality of" means two or more.

[0222] In some embodiments, the terms "at least one of", "one or more", "a plurality of", "multiple" and the like can be replaced with each other.

[0223] In some embodiments, "at least one of A, B", "A and / or B", "in one case A, in another case B", "responsive to case A, responsive to case B" and the like, can be interpreted to include both cases, A and B, in some embodiments, A (A is performed regardless of B), in some embodiments, B (B is performed regardless of A), in some embodiments, selected from the group consisting of A and B (the selection between A and B is an option), in some embodiments, A and B (both A and B are performed).

[0224] In some embodiments, "A or B" and the like, can be interpreted to include both cases, A and B, in some embodiments, A (A is performed regardless of B), in some embodiments, B (B is performed regardless of A), in some embodiments, selected from the group consisting of A and B (the selection between A and B is an option).

[0225] In some embodiments, the prefix words "first", "second" and the like in the disclosure do not limit the position, order, priority, number or content of the described objects, and the description of the described objects should be understood in the context of the claims or embodiments, and should not be construed as redundant limitations. For example, the described object is "field", and the ordinal words before "field" in "first field" and "second field" do not limit the position or order between "fields", and "first" and "second" do not limit whether the "fields" modified by them are in the same message or not, nor do they limit the order of "first field" and "second field". For another example, the described object is "level", and the ordinal words before "level" in "first level" and "second level" do not limit the priority between "levels". For another example, the number of described objects is not limited by ordinal words, and can be one or more. For example, "first device", where the number of "devices" can be one or more. In addition, objects modified by different prefix words can be the same or different, for example, the described object is "device", and "first device" and "second device" can be the same device or different devices, and their types can be the same or different; for another example, the described object is "information", and "first information" and "second information" can be the same information or different information, and their contents can be the same or different.

[0226] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A, or indirectly indicating A.

[0227] In some embodiments, the terms "in response to", "in response to determining", "in the case of", "when", "when", "if", "if" and the like can be replaced with each other.

[0228] In some embodiments, the terms "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not lower than", "above", and the like can be replaced with each other, and the terms "less than", "less than or equal to", "not greater than", "fewer than", "fewer than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", "below", and the like can be replaced with each other.

[0229] In some embodiments, the apparatuses and devices can be interpreted as physical or virtual, and their names are not limited to the names described in the embodiments, and in some cases can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", and the like.

[0230] In some embodiments, "network" can be interpreted as an apparatus included in the network, such as an access network device, a core network device, and the like.

[0231] In some embodiments, an “access network device (AN device)” can also be referred to as a “radio access network device (RAN device),” a “base station (BS),” a “radio base station,” a “fixed station,” and in some embodiments can also be understood as a “node,” an “access point,” a “transmission point (TP),” a “reception point (RP),” a “transmission / reception point (TRP),” a “panel,” an “antenna panel,” an “antenna array,” a “cell,” a “macro cell,” a “small cell,” a “femto cell,” a “pico cell,” a “sector,” a “cell group,” a “serving cell,” a “carrier,” a “component carrier,” a “bandwidth part (BWP),” and the like.

[0232] In some embodiments, a "terminal" or "terminal device" can be referred to as a "user equipment" (UE), a "user terminal," a "mobile station" (MS), a "mobile terminal" (MT), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, and / or the like.

[0233] In some embodiments, data, information and / or the like can be obtained in compliance with laws and regulations of the country in which the data, information and / or the like is obtained.

[0234] In some embodiments, data, information and / or the like can be obtained after consent is given by a user.

[0235] Further, each element, each row, or each column in a table of an embodiment of the present disclosure can be implemented as an independent embodiment, and a combination of any element, any row, or any column can be implemented as an independent embodiment.

[0236] In a New Radio (NR) system, Integrated access and backhaul (IAB) supports millimeter wave base stations for wireless access and backhaul, which can effectively reduce the need for new fiber deployment when deploying dense networks, making wireless relaying in NG-RAN (NG Radio Access Network) possible. Among them, the relay node is called IAB-node (IAB node), which supports wireless access and backhaul through NR. The termination node of the network side NR backhaul is called IAB-donor (IAB donor), which is a gNB (5G network base station) with additional IAB functions. Backhaul can be performed through single-hop or multi-hop.

[0237] As shown in FIG. 1a and FIG. 1b, NG-RAN can support IAB by connecting IAB-node wirelessly to a gNB (called IAB-donor) capable of serving IAB-node. Among them, the IAB-donor includes an IAB-donor-CU (centralized unit, also called control unit) and one or more IAB-donor-DU (distributed unit). When the gNB-CU-CP (control plane of CU) and the gNB-CU-UP (user plane of CU) are separated, the IAB-donor can include an IAB-donor-CU-CP, multiple IAB-donor-CU-UPs, and multiple IAB-donor-DUs. Among them, the IAB-node connects to the upstream IAB-node or IAB-donor-DU through a subset of terminal functions of the NR Uu interface (called IAB-MT function in IAB-node). The IAB-node provides wireless backhaul to downstream IAB-nodes and terminal devices through network functions of the NR Uu interface (called IAB-DU function of IAB-node). Among them, AMF in FIG. 1a is the abbreviation of Access and Mobility Management function, and its Chinese meaning is access and mobility management function; UPF in FIG. 1a is the abbreviation of User Plane Function, and its Chinese meaning is user plane function.

[0238] The F1-C traffic between IAB-node and IAB-donor-CU is backhauled through IAB-donor-DU and optional intermediate hop IAB-node. The F1-U traffic between IAB-node and IAB-donor-CU is backhauled through IAB-donor-DU and optional intermediate hop IAB-node.

[0239] In some embodiments, in the integrated scenario of mobile IAB, such as initial integration, the IAB-MT and IAB-DU can be integrated into different donor-CUs. For example, as shown in FIG. 1c, the Fl-terminating-donor-CU can be the donor-CU for the IAB-DU (Mobile IAB-distributed unit, mIAB distributed unit, also called mIAB-DU) in the mobile IAB node. The RRC-terminating-donor-CU can be the donor-CU for the IAB-MT (also called mIAB-MT) in the mobile IAB node. Optionally, as shown in FIG. 1c, the steps of the initial integration include, but are not limited to, the following steps 1 to step 3: step 1, the mIAB-MT accesses the network as a terminal (UE) through the RRC-terminating-donor-CU; step 2, the mIAB-DU sends an Fl connection establishment request to the Fl-terminating-donor-CU to establish an Fl connection between the mIAB-DU and the Fl-terminating-donor-CU. The Fl connection establishment request includes, for example, the UE ID (XnAP UE ID) of the mIAB-MT on the XnAP, and the Fl connection establishment request can also include an identifier indicating the donor-CU of the mIAB-MT; step 3, the Fl-terminating-donor-CU sends a TMM (Transport Migration Management) procedure to the RRC-terminating-donor-CU to establish a transport channel.

[0240] In some embodiments, after the initial integration, after partial migration or DC migration (DU migration), the IAB-MT and IAB-DU can also be migrated to different donor-CUs. For example, as shown in FIG. 1d, before migration, the donor-CU of the IAB-MT is the IAB-donor-CU 1, and the donor-DU of the IAB-DU is the IAB-donor-DU 1. As shown in FIG. 1e, after partial migration, the IAB-MT is migrated to the IAB-donor-CU 2, and the IAB-DU is migrated to the IAB-donor-CU 1, so that the IAB-MT and the IAB-DU are migrated to different donor-CUs.

[0241] In some embodiments, for MBSR (also called Mobile IAB-node), the subscription information stored in the home public land mobile network (HPLMN) indicates whether it is authorized to operate as MBSR, and the corresponding location and time periods.

[0242] In some embodiments, when MBSR roaming is supported, a roaming agreement between visited public land mobile network (VPLMN) and HPLMN regarding MBSR operation is in place, and the 5GC can make use of it for authorization of MBSR in VPLMN. MBSR (IAB-DU) can use IAB-node integration procedure or inter-IAB-donor gNB mobility procedure to integrate into VPLMN to provide service (When MBSR roaming is supported, a roaming agreement between VPLMN and HPLMN regarding MBSR operation is in place, and the 5GC can make use of it for authorization of MBSR in VPLMN. MBSR (IAB-DU) can use IAB-node integration procedure or inter-IAB-donor gNB mobility procedure to integrate into VPLMN to provide service).

[0243] In some embodiments, the MBSR (IAB-UE) is assumed to be configured with preferred PLMN lists and forbidden PLMNs by the HPLMN for the MBSR operation.

[0244] In some embodiments, when the MBSR (IAB-UE) performs initial registration to a serving public land mobile network (PLMN), it indicates a request to operate as a MBSR. The AMF authorizes the MBSR based on subscription information and provides a MBSR authorization indication to the NG-RAN. The MBSR establishes a connection to an OAM (Operation Administration and Maintenance) system using configuration information for MBSR operation.

[0245] In some embodiments, as part of the registration procedure, the AMF of the MBSR can indicate to the MBSR IAB-UE (also referred to as IAB-MT) that it is not allowed to act as a MBSR IAB node and in this case the AMF does not include a MBSR authorization indication to the host gNB. The AMF can provide the indication in the registration accept (if the PLMN allows the MBSR IAB-UE to register in the PLMM) or in the registration reject (if the PLMN does not allow the MBSR IAB-UE to register in the PLMN).

[0246] However, when the donor-CU of the IAB-MT is different from the donor-CU of the IAB-DU, how to make the corresponding mobile IAB nodes of the IAB-MT and the IAB-DU provide services to the terminal device has become a problem to be solved.

[0247] To this end, the embodiments of the present disclosure propose an authorization method and apparatus thereof, which can make the first node obtain information related to the authorization of the mobile IAB node, facilitate the first node to determine whether the mobile IAB node is authorized to provide services to the terminal device according to the information, and facilitate the terminal device to use the services provided by the mobile IAB node, so that the terminal device can obtain better communication connection through the mobile IAB node, guarantee the service continuity and access success rate of the terminal device, and improve the user experience.

[0248] In order to better understand the authorization method disclosed in the embodiments of the present disclosure, first, the communication system to which the embodiments of the present disclosure are applicable will be described below.

[0249] FIG. 2 is a schematic architecture diagram of a communication system according to an embodiment of the present disclosure. As shown in FIG. 2, the communication system 200 includes a first node 201 and a second node 202.

[0250] In some embodiments, the first node 201 includes at least one of an F1-terminating-donor-CU, an RRC-terminating-donor-CU, but is not limited thereto. Optionally, the F1-terminating-donor-CU can be a donor-CU for an IAB-DU in a mobile IAB node (also called mIAB-DU). The RRC-terminating-donor-CU can be a donor-CU for an IAB-MT (also called mIAB-MT) in a mobile IAB node. Wherein, the mobile IAB node can be a movable IAB node.

[0251] In some embodiments, the second node 202 includes at least one of an RRC-terminating-donor-CU, an F1-terminating-donor-CU, but is not limited thereto.

[0252] For example, the first node 201 can be an F1-terminating-donor-CU, and the second node 202 can be an RRC-terminating-donor-CU. Alternatively, for example, the first node 201 can be an RRC-terminating-donor-CU, and the second node 202 can be an F1-terminating-donor-CU.

[0253] FIG. 3 is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG. 3, the communication system 300 includes a first node 301, a second node 302, and a third node 303.

[0254] In some embodiments, the first node 301 includes at least one of an F1-terminating-donor-CU, an RRC-terminating-donor-CU, but is not limited thereto. Optionally, the F1-terminating-donor-CU can be a donor-CU for an IAB-DU in a mobile IAB node. The RRC-terminating-donor-CU can be a donor-CU for an IAB-MT (also called mIAB-MT) in a mobile IAB node. Wherein, the mobile IAB node can be a movable IAB node.

[0255] In some embodiments, the second node 302 includes at least one of an RRC-terminating-donor-CU, a first network element, an integrated access and backhaul node (IAB-node), but is not limited thereto. The network element can be virtual or physical. The first network element can be one of the core network devices, which can be one device including all or part of the first network element, the second network element, etc., or a plurality of devices or device groups including all or part of the first network element, the second network element, etc. The core network includes at least one of an evolved packet core (EPC), a 5G core network (5GCN), a next generation core (NGC).

[0256] In some embodiments, the first network element is an access and mobility management function (AMF).

[0257] In some embodiments, the first network element is a core network control plane entity, mainly responsible for user mobility management, including: registration and temporary identifier allocation; maintaining IDLE and CONNECT states and state migration; handover in the CONNECT state; paging triggering in the IDLE state of the user, etc.

[0258] In some embodiments, the second network element is a user plane function (UPF).

[0259] In some embodiments, the second network element is a core network user plane function entity, responsible for forwarding user data packets, and also performs statistics on user data packets for functions such as charging.

[0260] In some embodiments, the third node 303 includes at least one of an IAB-MT, an OAM, an RRC-terminating-donor-CU, and an IAB-node, but is not limited thereto.

[0261] In some embodiments, the OAM is mainly used for detecting the link quality and service quality of the operator network.

[0262] For example, the first node 301 can be an F1-terminating-donor-CU, the second node 302 can be an RRC-terminating-donor-CU, and the third node 303 can be an IAB-MT.

[0263] Exemplarily, the first node 301 can be an F1-terminating-donor-CU, the second node 302 can be an RRC-terminating-donor-CU, and the third node 303 can be an OAM.

[0264] Exemplarily, the first node 301 can be an F1-terminating-donor-CU, the second node 302 can be a first network element, and the third node 303 can be an RRC-terminating-donor-CU.

[0265] Exemplarily, the first node 301 can be an F1-terminating-donor-CU, the second node 302 can be a first network element, and the third node 303 can be an IAB-MT.

[0266] Exemplarily, the first node 301 can be an F1-terminating-donor-CU, the second node 302 can be a first network element, and the third node 303 can be an IAB-node.

[0267] Exemplarily, the first node 301 can be an F1-terminating-donor-CU, the second node 302 can be an IAB-node, and the third node 303 can be an RRC-terminating-donor-CU.

[0268] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions proposed in the embodiments of the present disclosure. It can be known by those skilled in the art that, with the evolution of system architecture and the appearance of new business scenarios, the technical solutions proposed in the embodiments of the present disclosure are also applicable to similar technical problems.

[0269] The following embodiments of the present disclosure can be applied to the communication system 100 shown in FIG. 2 or part of the subject, or can be applied to the communication system 200 shown in FIG. 3 or part of the subject, but are not limited thereto. The subjects shown in FIG. 2 are exemplary, and the communication system can include all or part of the subjects in FIG. 2, or can include other subjects other than FIG. 2. The subjects shown in FIG. 3 are exemplary, and the communication system can include all or part of the subjects in FIG. 3, or can include other subjects other than FIG. 3. The number and form of each subject is arbitrary, each subject can be physical or virtual, the connection relationship between each subject is exemplary, each subject can not be connected or can be connected, and the connection can be in any way, can be direct connection or indirect connection, can be wired connection or wireless connection.

[0270] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), system using other communication methods, next-generation system expanded based thereon, and the like. Further, a plurality of systems can be applied in combination (for example, combination of LTE or LTE-A and 5G, and the like).

[0271] The terminal device in each embodiment of the present disclosure is an entity for receiving or transmitting signals on the user side, such as a mobile phone. The terminal device can also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), and the like. The terminal device can be a car, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, a wireless terminal device in smart home, and the like. Embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal device.

[0272] FIG. 4a is an interaction schematic diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 4a, the embodiment of the present disclosure relates to an authorization method, which can be applied to the communication system 200 described above, and the method comprises:

[0273] In step S4101, the first node 201 sends second information to the second node 202.

[0274] In some embodiments, the second information can be authorization request information. In some embodiments, the second information includes at least one of the following information: an IAB-node ID, which is used to indicate the identity of an IAB-node or an IAB-MT or an IAB-DU in the IAB-node for which an authorization request is made; an authorization information request indication; and request information related to authorization. Exemplarily, the request information related to authorization can be a Transport Migration Management request message.

[0275] In step S4102, the second node 202 sends first information to the first node 201 according to the second information sent by the second node 202.

[0276] In some embodiments, the first node 201 can be a F1-terminating-donor-CU, and the second node 202 can be a RRC-terminating-donor-CU. The second node 202 sends the first information to the first node 201 in response to the second information sent by the first node 201, and the second information can include at least one of an IAB-node ID and an authorization information request indication. Optionally, in an implementation, the second node 202 can receive the first information from an AMF through an NGAP message. The RRC-terminating-donor-CU is a donor-CU of an IAB-MT in an IAB-node. If the RRC-terminating-donor-CU (the second node 202) and the F1-terminating-donor-CU (the first node 201) are different NG-RAN nodes, the second node 202 determines a gNB ID of the first node 202. For example, the second node 202 can determine the gNB ID of the F1-terminating-donor-CU through an XnAP message received from the first node 201, i.e., the F1-terminating-donor-CU sends an XnAP message to the RRC-terminating-donor-CU, and the XnAP message includes the second information, which includes a UE ID of the IAB-MT and is used to indicate an ID of the F1-terminating-donor-CU of the IAB-DU co-located with the IAB-MT, which is allocated to the IAB-MT (or IAB-node); and the IAB-MT UE ID is an XnAP UE ID.

[0277] In some embodiments, the second node 202 sends the first information to the first node 201 through an XnAP message.

[0278] In some embodiments, the first information can be information related to authorization of a mobile IAB node. In some embodiments, the first information can include at least one of the following information: authorization information; an identification of an integrated access and backhaul node, IAB-node ID; and information used to indicate authorization failure. The IAB-node ID is used to indicate an identification of the IAB-node, or an IAB-DU or an IAB-MT in the IAB-node.

[0279] In some embodiments, the information used to indicate authorization failure can be a cause value in a request failure, e.g., a cause value set as “unauthorized”.

[0280] In some embodiments, the terms “authorization information”, “mobile IAB authorization information” and the like can be replaced with each other.

[0281] In some embodiments, the first node 201 can be an F1-terminating-donor-CU, and the second node 202 can be an RRC-terminating-donor-CU. The second node 202 sends the first information to the first node 201 in response to the second information sent by the first node 201, the second information can include authorization-related request information (Transport Migration Management request), and the authorization-related request information can be a transport migration management request message. For example, the second node 202 sends the transport migration management request message to the first node 201.

[0282] In step S4103, the first node 201 determines whether the mobile IAB node is authorized to provide services to the terminal device according to the first information.

[0283] In some embodiments, after the first node 201 receives the first information sent by the second node 202, the first node 201 can save the first information, such as at least one of the authorization information, the IAB-node ID and the information for indicating the authorization failure in the first information, and the first node 201 can use the first information for the mobile IAB-DU accordingly. For example, the first node 201 can store the received mobile IAB authorization information in the UE context and use it for the mobile IAB-MT accordingly.

[0284] In some embodiments, the first node 201 can be a Fl-terminating-donor-CU, the second node 202 can be a RRC-terminating-donor-CU, if the mobile IAB authorization information element (IE) is set to "unauthorized", the Fl-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node does not serve any terminal devices if supported, if the mobile IAB authorization information element (IE) is set to "authorized", the Fl-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node can serve terminal devices if supported. For example, if the mobile IAB-MT's mobile IAB authorization IE is set to "unauthorized", the NG-RAN node shall initiate actions to ensure that the mobile IAB node does not serve any terminal devices if supported. Wherein the service can be understood as the service provided by the mobile IAB node, for example, the IAB-DU of the mobile IAB node can establish an Fl connection with the donor-CU of the IAB-DU, the mobile IAB node broadcasts that it is a mobile IAB node and can provide services for terminal devices, or the mobile IAB node provides services for terminal devices to access, etc.

[0285] In some embodiments, the first node 201 can be an F1-terminating-donor-CU, and the second node 202 can be an RRC-terminating-donor-CU. The second node 202 sends the first information to the first node 201 in response to the second information sent by the first node 201, and the second information can include the authorization-related request information (for example, the authorization-related request information is the transport migration management related request information, and the information is included in the Transport Migration Management request message). For example, the second node 202 sends the first node 201 a transport migration management request message. If the authorization information of the requested IAB-MT is “unauthorized”, the RRC-terminating-donor-CU sends the F1-terminating-donor-CU the first information, which can include a transport migration management rejection message carrying a cause value of “unauthorized”. The F1-terminating-donor-CU can determine whether the mobile IAB node is authorized to provide services to the terminal device according to the first information. For example, the F1-terminating-donor-CU determines that the mobile IAB node is not authorized to provide services to the terminal device according to the received transport migration management rejection message. If the authorization information of the requested IAB-MT is “authorized”, the RRC-terminating-donor-CU sends the F1-terminating-donor-CU a transport migration management feedback message in response to the transport migration management request message. For example, the F1-terminating-donor-CU determines that the mobile IAB node is authorized to provide services to the terminal device according to the received transport migration management feedback message.

[0286] In some embodiments, if the transport migration management procedure has been completed and the authorization information has changed (for example, the authorization information changes from “authorized” to “unauthorized” or the authorization information changes from “unauthorized” to “authorized”), the RRC-terminating-donor-CU sends the F1-terminating-donor-CU an XnAP message including information indicating authorization update.

[0287] In some embodiments, other optional implementations described before or after the description corresponding to FIG. 4a can be referred to.

[0288] FIG. 4b is an interaction schematic diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 4b, the embodiment of the present disclosure relates to an authorization method, which can be applied to the communication system 300, and the method comprises the following steps:

[0289] In step S4201, the third node 303 sends identification information for authorization request to the second node 302.

[0290] In some embodiments, the identification information for authorization request comprises at least one of the following information:

[0291] a next generation wireless access network node identifier NG-RAN node ID, used to indicate an identifier of a donor central unit of an integrated access and backhaul distributed unit IAB-DU;

[0292] a new radio cell global identifier NCGI and a length of the NG-RAN node ID, used to indicate an identifier of a donor-CU of the IAB-DU;

[0293] an IAB-node ID, used to indicate an identifier of an integrated access and backhaul node IAB-node or an IAB-MT or an IAB-DU in the IAB-node.

[0294] In some embodiments, the terms of “NG-RAN node ID”, “gNB ID” and the like can be replaced with each other.

[0295] In some embodiments, the third node 303 can be any one of the following: an IAB-node; an IAB-MT; an IAB-DU; an operation management and maintenance OAM; a donor-CU of an IAB-MT.

[0296] In step S4202, the second node 302 sends first information to the first node 301 according to the identification information for authorization request.

[0297] In some embodiments, the first information is information related to authorization of a mobile integrated access and backhaul IAB node. In some embodiments, the first information comprises at least one of the following information: authorization information; an IAB-node ID; information used to indicate authorization failure.

[0298] In some embodiments, the information used to indicate authorization failure can be a cause value in a request failure, for example, the cause value is set to “unauthorized”.

[0299] In some embodiments, the IAB-node ID comprises any of: a global identity of the IAB-MT; a terminal identity UE ID (i.e. XnAP UE ID) of the IAB-MT on an Xn interface application protocol XnAP; a UE ID (i.e. NGAP UE ID) of the IAB-MT on a next generation interface application protocol NGAP; a UE ID (F1AP UE ID) of the IAB-MT on a F1 interface application protocol F1AP; a backhaul adaptation protocol address (BAP address).

[0300] In some embodiments, the first node 301 can be a F1-terminating-donor-CU, the second node 302 can be a RRC-terminating-donor-CU, and the third node 303 can be an IAB-MT or an OAM.

[0301] In some embodiments, the first node 301 can be a F1-terminating-donor-CU, the second node 302 can be an AMF, and the third node 303 can be a RRC-terminating-donor-CU or an IAB-MT.

[0302] At step S4203, the first node 301 determines whether the mobile IAB node is authorized to provide services to the terminal device according to the first information.

[0303] In some embodiments, the first node 301 receives the first information sent by the second node 302, and can save the first information, such as at least one of the authorization information, the IAB-node ID and the information for indicating authorization failure in the first information. The first node 301 can correspondingly use the first information for the mobile IAB-DU. For example, the first node 301 can store the received mobile IAB authorization information in a UE context, and correspondingly use it for the mobile IAB-MT.

[0304] In some embodiments, the information for indicating authorization failure can be a cause value in the request failure, such as a cause value set to “unauthorized”.

[0305] In some embodiments, the first node 301 can be an F1-terminating-donor-CU, and the second node 302 can be an RRC-terminating-donor-CU. If the mobile IAB authorization information element (IE) is set to "unauthorized", the F1-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node does not serve any terminal devices if supported. For example, if the mobile IAB-MT's mobile IAB authorization IE is set to "unauthorized", the NG-RAN node shall initiate actions to ensure that the mobile IAB node does not serve any terminal devices if supported. Here, the service can be understood as the service provided by the mobile IAB node, for example, the service provided by the mobile IAB node for terminal device access, and the like.

[0306] In some embodiments, if the transmission migration management procedure has been completed, and the authorization information changes (for example, from "authorized" to "unauthorized"), the RRC-terminating-donor-CU sends an XnAP message to the F1-terminating-donor-CU, and the XnAP message includes information indicating authorization update.

[0307] In some embodiments, other optional implementations described before or after the description corresponding to FIG. 4b can be referred to.

[0308] FIG. 4c is an interaction schematic diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 4c, the embodiment of the present disclosure relates to an authorization method, which can be applied to the communication system 300 described above, and the method comprises:

[0309] In step S4301, the third node 303 sends first information to the second node 302.

[0310] In some embodiments, the first information can be mobile IAB node authorization related information. In some embodiments, the first information can include at least one of the following information: authorization information; an integrated access and backhaul node identifier IAB-node ID; and information indicating authorization failure. The IAB-node ID is an identifier for indicating an IAB-node, or an IAB-DU or an IAB-MT in the IAB-node.

[0311] In some embodiments, the information indicating authorization failure can be a cause value in a request failure, for example, the cause value is set to "unauthorized".

[0312] In some embodiments, the terms "authorization information", "mobile IAB authorization information", and the like can be replaced with each other.

[0313] In some embodiments, the third node 303 can be a donor-CU for the IAB-MT. For example, the third node 303 can be a RRC-terminating-donor-CU, and the second node 302 can be an IAB-node. In one implementation, the RRC-terminating-donor-CU sends the first information to the IAB-MT in the IAB-node through an RRC message. That is, the IAB-MT in the IAB-node receives the first information from the RRC-terminating-donor-CU through the RRC message.

[0314] At step S4302, the second node 302 sends the first information to the first node 301.

[0315] In some embodiments, the first node 301 can be a F1-terminating-donor-CU.

[0316] In some embodiments, the second node 302 can be an IAB-node. In one implementation, the IAB-DU in the IAB-node sends the first information to the F1-terminating-donor-CU through an F1AP message.

[0317] In some embodiments, the IAB-node can also be an MBSR, a VMR, or a mobile IAB-node.

[0318] At step S4303, the first node 301 determines whether the mobile IAB node is authorized to provide service to the terminal device according to the first information.

[0319] In some embodiments, after receiving the first information sent by the second node 302, the first node 301 can save the first information, such as at least one of the authorization information, the IAB-node ID, and the information indicating authorization failure in the first information, and the first node 301 can use the first information for the mobile IAB-DU accordingly. For example, the first node 301 can store the received mobile IAB authorization information in a UE context and use it for the mobile IAB-MT accordingly.

[0320] In some embodiments, the information indicating authorization failure can be a cause value in a request failure, such as a cause value set to “unauthorized”.

[0321] In some embodiments, the first node 301 can be a F1-terminating-donor-CU, the second node 302 can be an IAB-node, if the mobile IAB authorization information element (IE) of the IAB-MT is set to "unauthorized", the F1-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node does not serve any terminal devices if supported. Illustratively, if the mobile IAB authorization IE of the IAB-MT is set to "unauthorized", the NG-RAN node shall initiate actions to ensure that the mobile IAB node does not serve any terminal devices if supported, if the mobile IAB authorization information element (IE) is set to "authorized", the F1-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node can serve terminal devices if supported. Wherein, the service can be understood as the service provided by the mobile IAB node, for example, the IAB-DU of the mobile IAB node can establish an F1 connection with the donor-CU of the IAB-DU, the mobile IAB node broadcasts that it is a mobile IAB node and can provide services for terminal devices, or the mobile IAB node provides services for terminal devices to access, etc.

[0322] In some embodiments, if the transmission migration management procedure has been executed and completed, and the authorization information changes (for example, from the authorization information being "authorized" to "unauthorized", or from the authorization information being "unauthorized" to "authorized"), the RRC-terminating-donor-CU sends an XnAP message to the F1-terminating-donor-CU, and the XnAP message includes information for indicating authorization update.

[0323] In some embodiments, reference can be made to the other optional implementation modes described before or after the description corresponding to FIG. 4c.

[0324] FIG. 5a is a flow diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 5a, the present embodiment of the present disclosure relates to an authorization method, which can be executed by a first node, and the above-mentioned method includes but is not limited to the following steps.

[0325] Step S5101, the first node receives first information from the second node, the first information being information related to the authorization of the mobile integrated access and backhaul IAB node.

[0326] In some embodiments, the first information comprises at least one of the following: authorization information; an identity of an integrated access and backhaul node, IAB-node ID; information indicating authorization failure. Wherein the IAB-node ID is an identity for indicating an IAB-node, or an IAB-DU or an IAB-MT in the IAB-node.

[0327] In some embodiments, the IAB-node ID can comprise any of the following: a global identity of an integrated access and backhaul mobile terminal, IAB-MT; a terminal identity of the IAB-MT on an Xn interface application protocol, XnAP (i.e. XnAP UE ID); a UE ID of the IAB-MT on a next generation interface application protocol, NGAP (i.e. NGAP UE ID); a UE ID of the IAB-MT on a F1 interface application protocol, F1AP (i.e. F1AP UE ID); a BAP address.

[0328] In some embodiments, the IAB-node ID can comprise a global identity of an IAB-MT, which can be a generic public subscription identifier (GPSI) for example, but is not limited thereto.

[0329] In some embodiments, the information indicating authorization failure can be a cause value in a request failure, such as a cause value set to “unauthorized”.

[0330] In some embodiments, the first node can be an F1-terminating-donor-CU, the second node can be an RRC-terminating-donor-CU, and the first information is included in an XnAP message sent by the RRC-terminating-donor-CU to the F1-terminating-donor-CU.

[0331] In some embodiments, the first node can be an F1-terminating-donor-CU, the second node can be an AMF first network element, and the first information is included in an NGAP message sent by the AMF to the F1-terminating-donor-CU.

[0332] In some embodiments, the first node can be an F1-terminating-donor-CU, the second node can be an IAB-node, and the first information is included in a F1AP message sent by an IAB-DU in the IAB-node to the F1-terminating-donor-CU.

[0333] At step S5102, the first node receives and saves the first information, and determines whether the mobile IAB node is authorized to provide services to the terminal device according to the first information.

[0334] In some embodiments, the first node receives the first information sent by the second node, can save the first information, for example, save at least one of the authorization information, the IAB-node ID and the information for indicating the authorization failure in the first information, and the first node can use the first information for the mobile IAB-DU accordingly. For example, the first node can store the received mobile IAB authorization information in the UE context, and use it for the mobile IAB-MT or the mobile IAB-node accordingly.

[0335] In some embodiments, the first node can be an F1-terminating-donor-CU, and the second node can be an RRC-terminating-donor-CU. If the mobile IAB authorization information element (IE) is set to “not authorized”, the F1-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node does not provide services for any terminal device if supported. For example, if the mobile IAB authorization IE of the mobile IAB-MT is set to “not authorized”, the NG-RAN node shall initiate actions to ensure that the mobile IAB node does not provide services for any terminal device if supported. Wherein, the services can be understood as services provided by the mobile IAB node, for example, the IAB-DU of the mobile IAB node can establish an F1 connection with the donor-CU of the IAB-DU, the mobile IAB node broadcasts that it is a mobile IAB node and can provide services for terminal devices, or the mobile IAB node provides services for terminal devices to access, etc.

[0336] In some embodiments, the first node can be an F1-terminating-donor-CU, and the second node can be an RRC-terminating-donor-CU. If the authorization information element (IE) in the first information is set to “authorized”, the F1-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node will provide services for terminal devices or specific terminal devices if supported, for example, the IAB-DU of the mobile IAB node can establish an F1 connection with the donor-CU of the IAB-DU, the mobile IAB node broadcasts that it is a mobile IAB node and can provide services for terminal devices, or the mobile IAB node provides services for terminal devices to access.

[0337] In some embodiments, the set value of the authorization information element (IE) can be "unauthorized", "authorized", or other named names, which are used to indicate whether the mobile IAB node is authorized to provide services to the terminal device, and the present disclosure does not make any limitation hereon.

[0338] In some embodiments, the first node can be an F1-terminating-donor-CU, and the second node can be an RRC-terminating-donor-CU. The second node receives the second information sent by the first node, and sends the first information to the first node. The second information can include one or more of the following: authorization-related request information (Transport Migration Management request), authorization information request indication, and IAB-node ID. The authorization-related request information can be a transport migration management request message. The IAB-node ID can be used to indicate the IAB-node for which the authorization is requested, or the identity of the IAB-MT or IAB-DU in the IAB-node. For example, the second node sends a transport migration management request message to the first node. If the authorization information of the requested IAB-MT is "unauthorized", the RRC-terminating-donor-CU sends the first information to the F1-terminating-donor-CU, which can include a transport migration management rejection message carrying a cause value of "unauthorized". The F1-terminating-donor-CU can determine whether the mobile IAB node is authorized to provide services to the terminal device according to the first information. For example, the F1-terminating-donor-CU determines that the mobile IAB node is not authorized to provide services to the terminal device according to the received transport migration management rejection message.

[0339] In some embodiments, if the transport migration management procedure has been completed, and the authorization information has changed (for example, from "authorized" to "unauthorized", or from "unauthorized" to "authorized"), the RRC-terminating-donor-CU sends an XnAP message to the F1-terminating-donor-CU, which includes information indicating authorization update.

[0340] FIG. 5b is a flow diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 5b, the present embodiment of the present disclosure relates to an authorization method, which can be executed by a first node. The method includes, but is not limited to, the following steps.

[0341] Step S5201, the first node sends second information to the second node.

[0342] In some embodiments, the second information can be authorization request information. In some embodiments, the second information includes at least one of the following information: IAB-node ID, used to indicate the IAB-node of the authorization request, or the identity of the IAB-MT or IAB-DU in the IAB-node; authorization information request indication; authorization-related request information. Exemplarily, the authorization-related request information can be a transport migration management request message.

[0343] In some embodiments, the first node can be an F1-terminating-donor-CU, and the second node can be an RRC-terminating-donor-CU. Exemplarily, the F1-terminating-donor-CU can send the second information to the RRC-terminating-donor-CU, and the second information can include an IAB-node ID, for example, the IAB-node ID can be a UE ID of an IAB-MT, used to indicate the F1-terminating-donor-CU of the IAB-DU in the IAB-MT to allocate an ID to the IAB-MT (or IAB-node). Wherein, the IAB-MT UE ID can be an XnAP UE ID.

[0344] In some embodiments, the second information can be an XnAP message, or the second information can be included in an XnAP message. Optionally, the F1-terminating-donor-CU can send the second information to the RRC-terminating-donor-CU through the XnAP message.

[0345] In some embodiments, the first node can be an F1-terminating-donor-CU, and the second node can be an RRC-terminating-donor-CU. Exemplarily, the F1-terminating-donor-CU can send the second information to the RRC-terminating-donor-CU, and the second information can include authorization-related request information, for example, the authorization-related request information can be a transport migration management request message. Optionally, in an implementation manner, the F1-terminating-donor-CU can send the transport migration management request message to the RRC-terminating-donor-CU.

[0346] At step S5202, the second node sends the first information to the first node according to the second information.

[0347] In some embodiments, the first node can be a F1-terminating-donor-CU, the second node can be a RRC-terminating-donor-CU, and the second information can include an IAB-node ID, which can be an IAB-MT UE ID, indicating an ID assigned by the F1-terminating-donor-CU of the IAB-DU co-located with the IAB-MT to the IAB-MT (or IAB-node). After receiving the XnAP message sent by the F1-terminating-donor-CU, the RRC-terminating-donor-CU can determine the gNB ID of the F1-terminating-donor-CU, and the RRC-terminating-donor-CU can send the first information to the F1-terminating-donor-CU according to the gNB ID of the F1-terminating-donor-CU and / or the IAB-node ID. The gNB ID can be determined according to the XnAP message, and the IAB-node ID is used to determine a specific IAB-MT, and thus the authorization information corresponding to the specific IAB-MT can be obtained.

[0348] In some embodiments, the first node can be a F1-terminating-donor-CU, the second node can be a RRC-terminating-donor-CU, and the second information can include authorization-related request information. For example, the authorization-related request information can be a Transport Migration Management request. After receiving the Transport Migration Management request sent by the F1-terminating-donor-CU, the RRC-terminating-donor-CU can send the first information to the F1-terminating-donor-CU according to the Transport Migration Management request.

[0349] In some embodiments, the authorization information of the requested IAB-MT can be included in the transmission migration management request message. For example, if the authorization information of the requested IAB-MT is "unauthorized", the RRC-terminating-donor-CU sends the first information to the F1-terminating-donor-CU, and the first information can include a transmission migration management rejection message carrying a cause value of "unauthorized". If the authorization information of the requested IAB-MT is "authorized", the RRC-terminating-donor-CU sends the first information to the F1-terminating-donor-CU, and the first information can include a transmission migration management acceptance message carrying a cause value of "authorized".

[0350] In step S5203, the first node determines whether the mobile IAB node is authorized to provide services to the terminal device according to the first information.

[0351] In the embodiments of the present disclosure, the implementation of step S5203 can be implemented by part or all of the manners in step S5102 in the above-mentioned embodiments, which will not be limited here and will not be repeated.

[0352] FIG. 5c is a flowchart of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 5c, the present embodiment of the present disclosure relates to an authorization method, which can be executed by a first node, and the above-mentioned method includes but is not limited to the following steps.

[0353] In step S5301, the first node receives third information from a third node.

[0354] In some embodiments, the third information can include at least one of the following information: an identifier of a second node, an identifier of a donor-CU for indicating an IAB-DU; and an IAB-node ID.

[0355] In some embodiments, the identifier of the second node can be an NG-RAN node ID of the second node; in other embodiments, the identifier of the second node can be a cell identifier (such as NCGI, NR cell global identifity) and an NG-RAN node ID length of the second node, and the NG-RAN node ID can be determined according to the CGI and the gNB length.

[0356] In some embodiments, the first node can be an F1-terminating-donor-CU. In some embodiments, the third node can be any one of the following: an IAB-node; an RRC-terminating-donor-CU.

[0357] At step S5302, the first node sends, to the second node, the second information according to the third information.

[0358] In some embodiments, the second information can be an authorization request information. In some embodiments, the second information includes at least one of the following: an IAB-node ID, an identity of an IAB-node or an IAB-MT or an IAB-DU in the IAB-node, used to indicate the authorization request; an authorization information request indication; and request information related to authorization. Exemplarily, the request information related to authorization can be a Transport Migration Management request message.

[0359] In some embodiments, the first node can be an F1-terminating-donor-CU, the second node can be an AMF, and the third node can be an RRC-terminating-donor-CU. Exemplarily, the F1-terminating-donor-CU receives the third information from the RRC-terminating-donor-CU, and the third information can include an IAB-node ID and / or an AMF ID, and the IAB-node ID can be an IAB-MT UE ID.

[0360] In some embodiments, the third information can be an XnAP message. Alternatively, the third information can be included in an XnAP message. Exemplarily, the F1-terminating-donor-CU can receive the third information, IAB-MT UE ID and / or AMF ID, from the RRC-terminating-donor-CU through an XnAP message.

[0361] In some embodiments, the first node can be a F1-terminating-donor-CU, the second node can be an AMF, and the third node can be an IAB-node. For example, the F1-terminating-donor-CU receives the third information from the IAB-node, and the third information can include an IAB-node ID and / or an AMF ID, and the IAB-node ID can be an IAB-MT UE ID. The IAB-MT UE ID and / or the AMF ID can be received by the IAB-node from the AMF or the RRC-terminating-donor-CU.

[0362] In some embodiments, the third information can be an F1AP message. Alternatively, the third information can be included in an F1AP message. For example, the F1-terminating-donor-CU can receive the third information, i.e., the IAB-MT UE ID and / or the AMF ID (the identity of the AMF), from the RRC-terminating-donor-CU via an F1AP message.

[0363] In some embodiments, the second information can be an NGAP message. Alternatively, the second information can be included in an NGAP message. For example, after receiving the third information, the F1-terminating-donor-CU can send an NGAP message to the AMF according to the AMF ID in the third information, and the NGAP message can include the IAB-MT UE ID and / or an authorization information request. Optionally, the authorization information request can be used to request the second node to send the mobile IAB node authorization related information to the first node after receiving the authorization information request. The mobile IAB node is the IAB node associated with the IAB-MT UE ID in the NGAP message.

[0364] In step S5303, the first node receives the first information from the second node.

[0365] In some embodiments, after receiving the second information sent by the first node, the second node sends the first information to the first node according to the second information.

[0366] In some embodiments, the first node can be a F1-terminating-donor-CU, and the second node can be an AMF. After receiving the second information, the AMF can send the first information to the F1-terminating-donor-CU according to the IAB-MT UE ID and / or the authorization information request in the second information.

[0367] In some embodiments, the first information can be an NGAP message. Alternatively, the first information can be included in an NGAP message. For example, after receiving the second information, the AMF can send the first information to the F1-terminating-donor-CU through an NGAP message according to the IAB-MT UE ID and / or authorization information in the second information.

[0368] At step S5304, the first node determines whether the mobile IAB node is authorized to provide services to the terminal device according to the first information.

[0369] In embodiments of the present disclosure, the implementation of step S5304 can be implemented in part or all of the manners in steps S5102 in the above embodiments, which will not be limited herein and will not be described again.

[0370] FIG. 6a is a flowchart of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 6a, the present embodiment relates to an authorization method, which can be performed by a second node. The method includes but is not limited to the following steps.

[0371] At step S6101, the second node receives second information sent by the first node.

[0372] In some embodiments, the first node is an F1-terminating-donor-CU, and the second node is an RRC-terminating-donor-CU. Alternatively, the first node is an F1-terminating-donor-CU, and the second node is an AMF.

[0373] In some embodiments, the F1-terminating-donor-CU refers to a donor-CU connected to the IAB-DU of the IAB-node, which can also be referred to as an F1-terminating-donor, an IAB-donor, or an IAB-donor-CU.

[0374] In some embodiments, the RRC-terminating-donor-CU refers to a donor-CU connected to the IAB-MT of the IAB-node, which can also be referred to as an RRC-terminating-donor, an IAB-donor, or an IAB-donor-CU.

[0375] In some embodiments, the second information comprises at least one of the following: an IAB-node ID, used to indicate the IAB-node for which the authorization request is made, or an identity of an IAB-MT or an IAB-DU in the IAB-node; an authorization information request indication; and request information related to authorization.

[0376] At step S6102, the second node sends the first information to the first node according to the second information.

[0377] In the embodiments of the present disclosure, the first information is information related to authorization of the mobile IAB-node, and the first information is used by the first node to determine whether the mobile IAB-node is authorized to provide services to the terminal device. The optional implementation manners can be referred to the optional implementation manners of step S5102 in FIG. 5a, step S5203 in FIG. 5b, step S5304 in FIG. 5c, and other associated parts in the embodiments related to FIG. 5a, FIG. 5b, and FIG. 5c, which will not be repeated here.

[0378] In some embodiments, the first information comprises at least one of the following: authorization information; an IAB-node ID of the integrated access and backhaul node; and information used to indicate authorization failure.

[0379] In some embodiments, the IAB-node ID comprises any of the following: a global identity of the IAB-MT; a terminal identity UE ID of the IAB-MT on an Xn interface application protocol XnAP; a UE ID of the IAB-MT on a next generation interface application protocol NGAP; a UE ID of the IAB-MT on a F1 interface application protocol F1AP; and a BAP address.

[0380] In some embodiments, the information used to indicate authorization failure can be a cause value in the request failure, for example, the cause value is set to “unauthorized”.

[0381] FIG. 6b is a flow diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 6b, the embodiments of the present disclosure relate to an authorization method, which can be performed by a second node, and the above method comprises but is not limited to the following steps.

[0382] At step S6201, the second node receives identity information for an authorization request from a third node.

[0383] In some embodiments, the first node is an F1-terminating-donor-CU, and the second node is an RRC-terminating-donor-CU; or the first node is an F1-terminating-donor-CU, and the second node is an AMF.

[0384] In some embodiments, the identification information includes at least one of the following: an NG-RAN node ID, which is used to indicate the identity of the donor-CU of the IAB-DU; an NCGI and an NG-RAN node ID length, which are used to indicate the identity of the donor-CU of the IAB-DU; an IAB-node ID, which is used to indicate the identity of the IAB-node, or the IAB-MT or the IAB-DU in the IAB-node.

[0385] In some embodiments, the third node is any one of the following: an IAB-node; an IAB-MT; an IAB-DU; an OAM; a donor-CU of an IAB-MT.

[0386] In the embodiments of the present disclosure, the implementation of step S6201 can be implemented by part or all of the manners in step S4201 in the above-mentioned embodiments respectively, which will not be limited here, and will not be repeated.

[0387] In step S6202, the second node sends first information to the first node according to the identification information for the authorization request.

[0388] In the embodiments of the present disclosure, the first information is information related to the authorization of the mobile IAB node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to the terminal device. The optional implementation manners can be referred to the optional implementation manners of step S5102 in FIG. 5a, step S5203 in FIG. 5b, step S5304 in FIG. 5c, and other associated parts in the embodiments involved in FIG. 5a, FIG. 5b, and FIG. 5c, which will not be repeated here.

[0389] In the embodiments of the present disclosure, the implementation of step S6202 can be implemented by part or all of the manners in step S4202 in the above-mentioned embodiments respectively, which will not be limited here, and will not be repeated.

[0390] FIG. 6c is a flow diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 6c, the embodiments of the present disclosure relate to an authorization method, which can be performed by a second node, and the above-mentioned method includes but is not limited to the following steps.

[0391] In step S6301, the second node receives the first information from the third node.

[0392] In some embodiments, the second node is an IAB-node, and the third node is a donor-CU of an IAB-MT. For example, the donor-CU of the IAB-MT can be an RRC-terminating-donor-CU.

[0393] In some embodiments, the first information can be included in an RRC message. For example, the IAB-MT in the IAB-node receives the first information from the RRC-terminating-donor-CU through the RRC message.

[0394] In step S6302, the second node sends the first information to the first node.

[0395] In some embodiments, the first node is an F1-terminating-donor-CU, the second node is an IAB-node, and the third node is a donor-CU of an IAB-MT. The first information sent by the second node to the first node can be included in an F1AP message. For example, the IAB-DU in the IAB-node sends the first information to the F1-terminating-donor-CU through the F1AP message.

[0396] In the embodiments of the present disclosure, the first information is information related to the authorization of the mobile IAB node, and the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to the terminal device. The optional implementation can refer to the optional implementation of step S5102 in FIG. 5a, step S5203 in FIG. 5b, step S5304 in FIG. 5c, and other associated parts in the embodiments related to FIG. 5a, FIG. 5b, and FIG. 5c, which will not be repeated here.

[0397] FIG. 7a is a flow diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 7a, the embodiments of the present disclosure relate to an authorization method, which can be performed by a third node. The method includes but is not limited to the following steps.

[0398] In step S7101, the third node sends identification information for authorization request to the second node.

[0399] In the embodiments of the present disclosure, the identification information for authorization request is used by the second node to send the first information to the first node. The optional implementation can refer to step S6202 in FIG. 6b and other associated parts in the embodiments related to FIG. 6b, which will not be repeated here.

[0400] In an embodiment of the disclosure, the first information is information related to authorization of a mobile integrated access and backhaul (IAB) node, and the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to the terminal device. The optional implementation manners can be referred to the optional implementation manners of step S5102 in FIG. 5a, step S5203 in FIG. 5b, step S5304 in FIG. 5c, and other associated parts in the embodiments related to FIG. 5a, FIG. 5b, and FIG. 5c, which will not be repeated here.

[0401] In some embodiments, the first information includes at least one of the following: authorization information; an identifier of an integrated access and backhaul node (IAB-node ID); and information indicating authorization failure.

[0402] In some embodiments, the information indicating authorization failure can be a cause value in a request failure, for example, the cause value is set to “unauthorized”.

[0403] In some embodiments, the IAB-node ID includes any of the following: a global identifier of an integrated access and backhaul mobile terminal (IAB-MT); a terminal identifier (UE ID) of the IAB-MT on an Xn interface application protocol (XnAP); a UE ID of the IAB-MT on a next generation interface application protocol (NGAP); a UE ID of the IAB-MT on a F1 interface application protocol (F1AP); and a backhaul adaptation protocol address (BAP address).

[0404] In some embodiments, the above-mentioned identifier information includes at least one of the following: a next generation radio access network node identifier (NG-RAN node ID) indicating an identifier of a donor central unit (donor-CU) of an integrated access and backhaul distributed unit (IAB-DU); a new radio cell global identifier (NCGI) and a length of the NG-RAN node ID indicating an identifier of the donor-CU of the IAB-DU; and an IAB-node ID indicating an identifier of an integrated access and backhaul node (IAB-node) or an IAB-MT or an IAB-DU in the IAB-node.

[0405] In some embodiments, the first node is an F1-terminating-donor-CU, the second node is a radio resource control-terminating-donor-CU (RRC-terminating-donor-CU), and the third node is an IAB-MT or an operation administration and maintenance (OAM).

[0406] In some embodiments, the first node is an F1-terminating-donor-CU, the second node is an access and mobility management function (AMF), and the third node is an IAB-MT or a radio resource control-terminating-donor-CU (RRC-terminating-donor-CU).

[0407] FIG. 7b is a flow diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 7b, the embodiment of the present disclosure relates to an authorization method, which can be performed by a third node, and the above-mentioned method includes but is not limited to the following steps.

[0408] In step S7201, the third node sends first information to the second node.

[0409] In the embodiment of the present disclosure, after receiving the first information sent by the third node, the second node sends the first information to the first node. That is, the second node can receive the first information from the third node and send the first information to the first node. The optional implementation manner can refer to the optional implementation manner of step S6301 in FIG. 6c and other associated parts in the embodiments related to FIG. 6c, which will not be described here.

[0410] In the embodiment of the present disclosure, the first information is information related to authorization of a mobile integrated access and backhaul (IAB) node, and the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device. The optional implementation manner can refer to the optional implementation manner of step S5102 in FIG. 5a, step S5203 in FIG. 5b, step S5304 in FIG. 5c, and other associated parts in the embodiments related to FIG. 5a, FIG. 5b, and FIG. 5c, which will not be described here.

[0411] In some embodiments, the above-mentioned first information includes at least one of the following information: authorization information; an integrated access and backhaul node identifier (IAB-node ID); and information indicating authorization failure.

[0412] In some embodiments, the above-mentioned IAB-node ID includes any one of the following: a global identifier of an integrated access and backhaul mobile terminal (IAB-MT); a terminal identifier (UE ID) of the IAB-MT on an Xn interface application protocol (XnAP); a UE ID of the IAB-MT on a next generation interface application protocol (NGAP); a UE ID of the IAB-MT on an F1 interface application protocol (F1AP); and a backhaul adaptation protocol address (BAP address).

[0413] In some embodiments, the information indicating authorization failure can be a cause value in a request failure, for example, the cause value is set to “unauthorized”.

[0414] In some embodiments, the first node is an F1-terminating-donor-CU, the second node is an integrated access and backhaul node (IAB-node), and the third node is a donor-CU of the IAB-MT.

[0415] FIG. 7c is a flow diagram of an authorization method according to an embodiment of the present disclosure. As shown in FIG. 7c, the embodiment of the present disclosure relates to an authorization method, which can be performed by a third node, and the above-mentioned method includes but is not limited to the following steps.

[0416] In step S7301, the third node sends third information to the first node.

[0417] In the embodiment of the present disclosure, the third information is used by the first node to send second information to the second node. The optional implementation thereof can be found in the optional implementation of step S5302 of FIG. 5c and other associated parts in the embodiments related to FIG. 5c, which will not be repeated here.

[0418] In the embodiment of the present disclosure, the second information is used by the second node to send first information to the first node. The optional implementation thereof can be found in the optional implementation of step S5303 of FIG. 5c and other associated parts in the embodiments related to FIG. 5c, which will not be repeated here.

[0419] In the embodiment of the present disclosure, the first information is information related to authorization of a mobile integrated access and backhaul (IAB) node, and the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device. The optional implementation thereof can be found in step S5102 of FIG. 5a, step S5203 of FIG. 5b, the optional implementation of step S5304 of FIG. 5c, and other associated parts in the embodiments related to FIG. 5a, FIG. 5b, and FIG. 5c, which will not be repeated here.

[0420] In some embodiments, the first information includes at least one of the following: authorization information; an identifier of an integrated access and backhaul node (IAB-node ID); and information indicating authorization failure.

[0421] In some embodiments, the IAB-node ID includes any of the following: a global identifier of an integrated access and backhaul mobile terminal (IAB-MT); a terminal identifier (UE ID) of the IAB-MT on an Xn interface application protocol (XnAP); a UE ID of the IAB-MT on a next generation interface application protocol (NGAP); a UE ID of the IAB-MT on an F1 interface application protocol (F1AP); and a backhaul adaptation protocol address (BAP address).

[0422] In some embodiments, the information for indicating the authorization failure can be a cause value in the request failure, for example, the cause value is set as "unauthorized".

[0423] In some embodiments, the third information includes at least one of the following information: an identity of the second node, an identity of a host centralized unit donor-CU of the integrated access and backhaul distributed unit IAB-DU, and an IAB-node ID.

[0424] In some embodiments, the first node is an F1-terminating-donor-CU, the second node is an access and mobility management function AMF, and the third node is an integrated access and backhaul node IAB-node or a radio resource control-terminating-donor-CU.

[0425] Optionally, the authorization method of the embodiments of the present disclosure can be implemented based on an Xn-based solution. For example, the donor-CU of the IAB-MT sends authorization information (such as information related to the authorization of the mobile IAB node) to the donor-CU of the IAB-DU. The donor-CU of the IAB-MT can obtain the gNB-ID of the donor-CU of the IAB-DU in the following ways: way 1, obtaining the gNB-ID of the donor-CU of the IAB-DU through OAM configuration; way 2, obtaining the gNB-ID of the donor-CU of the IAB-DU through reporting of the IAB-MT; and way 3, obtaining the gNB-ID of the donor-CU of the IAB-DU through the donor-CU of the IAB-DU. FIG. 8a is a flowchart of an authorization method according to an embodiment of the present disclosure. It should be noted that the steps in FIG. 8a omit the content irrelevant to the present disclosure. As shown in FIG. 8a, the embodiments of the present disclosure relate to an authorization method, and the method includes but is not limited to the following steps.

[0426] In step S8101, the RRC-terminating-donor-CU receives the mobile IAB authorization information (Mobile IAB Authorized info) from the AMF through an NGAP message.

[0427] The RRC-terminating-donor-CU is the donor-CU of the IAB-MT in the IAB-node.

[0428] Step S8102, if the RRC-terminating-donor-CU and the F1-terminating-donor-CU are different NG-RAN nodes, the RRC-terminating-donor-CU determines the gNB ID of the F1-terminating-donor-CU.

[0429] In the embodiments of the present disclosure, the RRC-terminating-donor-CU determines the gNB ID of the F1-terminating-donor-CU, including at least one of the following manners:

[0430] Step S8102a, the RRC-terminating-donor-CU obtains the gNB ID of the F1-terminating-donor-CU through the IAB-MT, that is, the IAB-MT sends the gNB ID of the F1-terminating-donor-CU to the RRC-terminating-donor-CU through an RRC message;

[0431] Step S8102b, the RRC-terminating-donor-CU obtains the gNB ID of the F1-terminating-donor-CU through OAM;

[0432] Step S8102c, the RRC-terminating-donor-CU determines the gNB ID of the F1-terminating-donor-CU through an XnAP message received from the F1-terminating-donor-CU, and the F1-terminating-donor-CU sends the XnAP message to the RRC-terminating-donor-CU, wherein the XnAP message includes the IAB-MT UE ID, which is used to indicate the ID of the F1-terminating-donor-CU of the IAB-DU co-located with the IAB-MT allocated to the IAB-MT (or IAB-node);

[0433] The IAB-MT UE ID is an XnAP UE ID.

[0434] Step S8103, the RRC-terminating-donor-CU sends the mobile IAB authorization information to the F1-terminating-donor-CU through an XnAP message.

[0435] Among them, the F1-terminating-donor-CU receives the mobile IAB authorization information, saves the received mobile IAB authorization information, and uses it for mobile IAB-DU accordingly. If the mobile IAB authorization IE is set to "unauthorized", the F1-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node does not serve any terminal if supported.

[0436] Optionally, the authorization method of the embodiment of the present disclosure can be implemented based on the NG solution. For example, the AMF of the IAB-MT sends the authorization information to the donor-CU of the IAB-DU, and the AMF can obtain the gNB ID of the donor-CU of the IAB-DU in the following ways: way 1, the IAB-node informs the AMF through the NAS message; way 2, the donor-CU of the IAB-MT informs the AMF through the NGAP message; way 3, the donor-CU of the IAB-DU requests the authorization information from the AMF through the NGAP message (wherein the donor-CU of the IAB-DU can obtain the AMF ID through the IAB-node or the donor-CU of the IAB-MT). FIG. 8b is a flow diagram of an authorization method according to an embodiment of the present disclosure. It should be noted that the steps in FIG. 8b omit the content irrelevant to the present disclosure. As shown in FIG. 8b, the embodiment of the present disclosure relates to an authorization method, and the above method includes but is not limited to the following steps.

[0437] Step S8201, the AMF determines the gNB ID of the F1-terminating-donor-CU, and the coexisting IAB-MT UE ID of the IAB-DU corresponding to the F1-terminating-donor-CU.

[0438] Among them, the AMF determines the gNB ID of the F1-terminating-donor-CU, and the coexisting IAB-MT UE ID of the IAB-DU corresponding to the F1-terminating-donor-CU includes at least one of the following ways:

[0439] Step S8201a, the AMF receives the IAB-MT UE ID and / or F1-terminating-donor-CU gNB ID from the RRC-terminating-donor-CU through the NAGP message;

[0440] Step S8201b, the AMF receives the IAB-MT UE ID and / or F1-terminating-donor-CU gNB ID from the IAB-MT through the NAS message.

[0441] Step S8202, the AMF sends an NGAP message to the F1-terminating-donor-CU according to the F1-terminating-donor-CU gNB ID, wherein the NGAP message includes the IAB-MT UE ID and / or the mobile IAB authorization information.

[0442] The F1-terminating-donor-CU receives the mobile IAB authorization information and saves the received mobile IAB authorization information, and uses it for mobile IAB-DU accordingly. If the mobile IAB authorization IE of the IAB-MT is set to "unauthorized", the F1-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node does not serve any terminals if supported.

[0443] Optionally, the authorization method of the embodiment of the present disclosure can be implemented based on the NG solution. For example, the AMF of the IAB-MT sends the authorization information to the donor-CU of the IAB-DU, and the AMF can obtain the gNB ID of the donor-CU of the IAB-DU in the following ways: way 1, the IAB-node informs the AMF through the NAS message; way 2, the donor-CU of the IAB-MT informs the AMF through the NGAP message; way 3, the donor-CU of the IAB-DU requests the authorization information from the AMF through the NGAP message (wherein the donor-CU of the IAB-DU can obtain the AMF ID through the IAB-node or the donor-CU of the IAB-MT). FIG. 8c is a flow diagram of an authorization method according to an embodiment of the present disclosure. It should be noted that the steps in FIG. 8c omit the content irrelevant to the present disclosure. As shown in FIG. 8c, the embodiment of the present disclosure relates to an authorization method, and the above-mentioned method includes but is not limited to the following steps.

[0444] Step S8301, the F1-terminating-donor-CU determines the identity of the AMF, wherein the AMF is the AMF of the IAB-MT, and the F1-terminating-donor-CU is the donor-CU of the IAB-DU co-located with the IAB-MT.

[0445] The "F1-terminating-donor-CU determines the identity of the AMF" includes at least one of the following ways:

[0446] Step S8301a, the F1-terminating-donor-CU receives the IAB-MT UE ID and / or AMF ID from the RRC-terminating-donor-CU through an XnAP message;

[0447] Step S8301b, the F1-terminating-donor-CU receives the IAB-MT UE ID and / or AMF ID from the IAB-node through an F1AP message, in some embodiments, the IAB-MT UE ID and / or AMF ID can be received by the IAB-node from the AMF or the RRC-terminating-donor-CU.

[0448] Step S8302, the F1-terminating-donor-CU sends an NGAP message to the AMF according to the identification of the AMF, wherein the NGAP message includes the IAB-MT UE ID and / or an authorized information request.

[0449] Step S8303, the AMF receives and sends mobile IAB authorization information to the F1-terminating-donor-CU through an NGAP message according to the IAB-MT UE ID and / or the authorized information request.

[0450] In some embodiments, the F1-terminating-donor-CU receives the mobile IAB authorization information, saves the received mobile IAB authorization information, and uses it for mobile IAB-DU accordingly. If the mobile IAB authorization IE of the IAB-MT is set to "unauthorized", the F1-terminating-donor-CU should initiate operations to ensure that the mobile IAB node does not provide services for any terminal if supported.

[0451] Optionally, the authorization method of the embodiments of the present disclosure can be implemented based on the F1AP solution. For example, the IAB-MT obtains authorization information from the donor-CU of the IAB-MT, and the IAB-DU sends authorization information to the donor-CU of the IAB-DU. FIG. 8d is a flow diagram of an authorization method according to an embodiment of the present disclosure. It should be noted that the steps in FIG. 8d omit content irrelevant to the present disclosure. As shown in FIG. 8d, the embodiments of the present disclosure relate to an authorization method, and the above method includes but is not limited to the following steps.

[0452] Step S8401, the IAB-MT in the IAB-node receives the mobile IAB authorization information from the RRC-terminating-donor-CU through an RRC message.

[0453] Step S8402, the IAB-DU in the IAB-node sends the mobile IAB authorization information to the F1-terminating-donor-CU through an F1AP message;

[0454] In some embodiments, the F1-terminating-donor-CU receives the mobile IAB authorization information, saves the received mobile IAB authorization information, and uses it accordingly for the mobile IAB-DU. If the mobile IAB authorization IE of the IAB-MT is set to “not authorized”, the F1-terminating-donor-CU shall initiate actions to ensure that the mobile IAB node does not serve any terminals if supported.

[0455] Optionally, the authorization information is saved in the donor-CU of the IAB-MT all the time, and when the donor-CU of the IAB-DU applies for transmission resources to the donor-CU of the IAB-MT, the donor-CU of the IAB-MT can agree or refuse the request of the donor-CU of the IAB-DU according to the received authorization information. For example, FIG. 8e is a flowchart of an authorization method according to an embodiment of the present disclosure. It should be noted that the steps in FIG. 8e omit the content irrelevant to the present disclosure. As shown in FIG. 8e, the present embodiment of the present disclosure relates to an authorization method, and the above method includes but is not limited to the following steps.

[0456] Step S8501, the F1-terminating-donor-CU sends a transport migration management request message to the RRC-terminating-donor-CU.

[0457] Step S8502, if the requested authorization information of the IAB-MT is “not authorized”, the RRC-terminating-donor-CU sends a transport migration management reject message to the F1-terminating-donor-CU, and the reject message carries a cause value of “not authorized”.

[0458] In some embodiments, if the transmission migration management procedure has been executed and completed, and the authorization information changes, the RRC-terminating-donor-CU sends an XnAP message to the F1-terminating-donor-CU, the XnAP message including information indicating authorization update.

[0459] In the embodiments of the present disclosure, part or all of the steps, and optional implementation manners thereof, can be combined with part or all of the steps in other embodiments, or combined with optional implementation manners of other embodiments.

[0460] The embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device including units or modules for implementing the steps performed by the network device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0461] It should be understood that the division of each unit or module in the above apparatus is only a logical function division, and all or part of them can be integrated into a physical entity or physically separated in actual implementation. In addition, the units or modules in the apparatus can be implemented in the form of processor calling software: for example, the apparatus includes a processor, the processor is connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to realize any of the above methods or realize the functions of each unit or module of the above apparatus, wherein the processor is a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory in the apparatus or a memory outside the apparatus. Alternatively, the units or modules in the apparatus can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be realized by the design of hardware circuit. The above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are realized by the design of the logical relationship of elements in the circuit; for another example, in another implementation, the above hardware circuit is a programmable logic device (PLD), and a field programmable gate array (FPGA) is taken as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of part or all of the above units or modules. All units or modules of the above apparatus can be all implemented in the form of processor calling software, or all implemented in the form of hardware circuit, or part implemented in the form of processor calling software and the remaining part implemented in the form of hardware circuit.

[0462] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), and the like. In another implementation, the processor can implement certain functions through a logical relationship of hardware circuit, and the logical relationship of the hardware circuit is fixed or can be reconfigured. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit. It can be understood that the processor loads instructions to implement the functions of the above part or all units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like.

[0463] FIG. 9a is a structural schematic diagram of a communication apparatus according to an embodiment of the present disclosure. The communication apparatus 9100 shown in FIG. 9a can include at least one of a transceiver module 9101, a processing module 9102, and the like. The communication apparatus 9100 can be a first node, or an apparatus in the first node, or an apparatus that can be used in matching with the first node. Alternatively, the communication apparatus 9100 can be a second node, or an apparatus in the second node, or an apparatus that can be used in matching with the second node. Alternatively, the communication apparatus 9100 can be a third node, or an apparatus in the third node, or an apparatus that can be used in matching with the third node.

[0464] The communication apparatus 9100 is a first node: the transceiver 9101 is configured to receive, from a second node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, and the processor 9102 is configured to determine, according to the first information, whether the mobile IAB node is authorized to provide service to a terminal device. Optionally, the transceiver 9101 is configured to perform at least one of transmission, reception, and / or communication steps of the first node in any of the methods described above, which will not be repeated here. The processor 9102 is configured to perform at least one of the other steps of the first node in any of the methods described above, which will not be repeated here.

[0465] The communication apparatus 9100 is a second node: the transceiver 9101 is configured to transmit, to a first node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device. Optionally, the transceiver 9101 is configured to perform at least one of transmission, reception, and / or communication steps of the second node in any of the methods described above, which will not be repeated here. The processor 9102 is configured to perform at least one of the other steps of the second node in any of the methods described above, which will not be repeated here.

[0466] The communication apparatus 9100 is a third node: the transceiver 9101 is configured to transmit, to a second node, identification information for an authorization request, wherein the identification information is used by the second node to transmit, to a first node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device. Alternatively, the transceiver 9101 is configured to transmit, to a first node via a second node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device. Alternatively, the transceiver 9101 is configured to transmit, to a first node, third information for the first node to transmit, to a second node, second information for the second node to transmit, to the first node, first information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device. Optionally, the transceiver 9101 is configured to perform at least one of transmission, reception, and / or communication steps of the third node in any of the methods described above, which will not be repeated here. The processor 9102 is configured to perform at least one of the other steps of the third node in any of the methods described above, which will not be repeated here.

[0467] In some embodiments, the transceiving module can include a transmitting module and / or a receiving module, which can be separate or integrated together. Optionally, the transceiving module can be mutually replaced with a transceiver.

[0468] In some embodiments, the processing module can be one module or include multiple sub-modules. Optionally, the multiple sub-modules perform all or part of the steps required to be performed by the processing module. Optionally, the processing module can be mutually replaced with a processor.

[0469] FIG. 9b is a structural schematic diagram of a communication apparatus according to an embodiment of the present disclosure. The communication apparatus 9200 can be a network device (for example, an access network device, a core network device, etc., such as a first node, a second node, a third node), a chip, a chip system, or a processor supporting the network device to implement any of the above methods. The communication apparatus 9200 can be used to implement the methods described in the above method embodiments, and details can be referred to the descriptions in the above method embodiments.

[0470] As shown in FIG. 9b, the communication apparatus 9200 includes one or more processors 9201. The processor 9201 can be a general-purpose processor or a special-purpose processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication apparatus (for example, a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process data of the programs. The communication apparatus 9200 is used to execute any of the above methods.

[0471] In some embodiments, the communication apparatus 9200 further includes one or more memories 9202 for storing instructions. Optionally, all or part of the memory 9202 can also be outside the communication apparatus 9200.

[0472] In some embodiments, the communication apparatus 9200 further includes one or more transceivers 9203. When the communication apparatus 9200 includes one or more transceivers 9203, the transceiver 9203 performs at least one of the communication steps such as transmitting and / or receiving in the above methods, and the processor 9201 performs at least one of the other steps.

[0473] In some embodiments, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Optionally, the terms of transceiver, transceiving unit, transceiver, transceiving circuit, etc. can be mutually replaced, the terms of transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be mutually replaced, and the terms of receiver, receiving unit, receiver, receiving circuit, etc. can be mutually replaced.

[0474] In some embodiments, the communication apparatus 9200 can include one or more interface circuits 9204. Optionally, the interface circuits 9204 are connected to the memory 9202, and are configured to receive signals from the memory 9202 or other devices, and are configured to send signals to the memory 9202 or other devices. For example, the interface circuits 9204 can read instructions stored in the memory 9202 and transmit the instructions to the processor 9201.

[0475] The communication apparatus 9200 in the above embodiments can be a network device or a terminal, but the scope of the communication apparatus 9200 described in the present disclosure is not limited thereto, and the structure of the communication apparatus 9200 can not be limited by FIG. 9b. The communication apparatus can be a standalone device or can be part of a larger device. For example, the communication apparatus can be: 1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, which can optionally also include storage means for storing data, programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, and the like; (6) other devices, and the like.

[0476] FIG. 9c is a structural schematic diagram of a chip 9300 according to an embodiment of the present disclosure. For the case where the communication apparatus 9200 is a chip or a chip system, the structural schematic diagram of the chip 9300 shown in FIG. 9c can be referred to, but is not limited thereto.

[0477] The chip 9300 includes one or more processors 9301, and the chip 9300 is configured to execute any of the above methods.

[0478] In some embodiments, the chip 9300 further includes one or more interface circuits 9302. Optionally, the interface circuits 9302 are connected to the memory 9303, and the interface circuits 9302 can be configured to receive signals from the memory 9303 or other devices, and can be configured to send signals to the memory 9303 or other devices. For example, the interface circuits 9302 can read instructions stored in the memory 9303 and transmit the instructions to the processor 9301.

[0479] In some embodiments, the interface circuits 9302 perform at least one of the communication steps such as transmitting and / or receiving in the above methods, and the processor 9301 performs at least one of the other steps.

[0480] In some embodiments, the terms interface circuit, interface, transceiver pin, and transceiver can be replaced by each other.

[0481] In some embodiments, chip 9300 also includes one or more memories 9303 for storing instructions. Optionally, all or some of the memories 9303 can be external to chip 9300.

[0482] The disclosure further provides a storage medium having stored thereon instructions which, when executed by a communication apparatus 9200, cause the communication apparatus 9200 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but this is not a limitation, as the storage medium can be any medium that can store data which can be accessed by a computing device. Optionally, the storage medium can be a non-transitory storage medium, but this is not a limitation, as the storage medium can be a transitory storage medium.

[0483] The disclosure further provides a program product which, when executed by a communication apparatus 9200, causes the communication apparatus 9200 to perform any of the methods described above. Optionally, the program product is a computer program product.

[0484] The disclosure further provides a computer program which, when executed on a computer, causes the computer to perform any of the methods described above.

[0485] In the embodiments described above, all or some of the steps can be implemented by software, hardware or firmware, or any combination thereof. When implemented by software, all or some of the steps can be implemented by one or more computer programs. When the one or more computer programs are loaded into and executed by a computer, all or some of the procedures or functions described above can be performed. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatuses. The one or more computer programs can be stored in a computer readable storage medium when implemented using a hardware description language (HDL) or a hardware design language (HDL), and stored medium can be included in a server, a data center, or other data storage devices. The computer readable storage medium can be any available medium or a combination of one or more available media including a portable or fixed computer readable storage medium, a volatile or non-volatile storage medium, or a storage device integrated into a server, a data center, or other data storage devices. The computer readable storage medium can be a magnetic medium (e.g., a floppy diskette, a hard disk drive, a magnetic tape), an optical medium (e.g., a compact disc (CD), a DVD), a semiconductor medium (e.g., a solid state disk (SSD)), or the like.

[0486] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software manner depends on the specific application and design constraints of the technical solution. The skilled person can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the disclosure.

[0487] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0488] The above is only a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present disclosure, which should be covered within the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

A method of authorization, characterized in that The method is performed by a first node, and the method comprises: receiving first information from a second node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node; determining, according to the first information, whether the mobile IAB node is authorized to provide service to a terminal device. The method of claim 1, wherein The first information comprises at least one of the following: authorization information; an identity of an integrated access and backhaul node, IAB-node ID; information indicating authorization failure. The method of claim 2, wherein The IAB-node ID comprises any of the following: a global identity of an integrated access and backhaul mobile terminal, IAB-MT; a terminal identity, UE ID, of the IAB-MT on an Xn interface application protocol, XnAP; a UE ID of the IAB-MT on a next generation interface application protocol, NGAP; a UE ID of the IAB-MT on a F1 interface application protocol, F1AP; a backhaul adaptation protocol address, BAP address. The method of any of claims 1 to 3, wherein the first node is a F1-terminating-donor-CU, and the second node is a radio resource control-terminating-donor-CU, RRC-terminating-donor-CU; or the first node is a F1-terminating-donor-CU, and the second node is an access and mobility management function, AMF; or the first node is a F1-terminating-donor-CU, and the second node is an integrated access and backhaul node, IAB-node. The method of claim 1, wherein The receiving first information from a second node comprises: sending second information to the second node, the second information being used by the second node to send the first information to the first node. The method of claim 5, wherein The second information comprises at least one of the following: an IAB-node ID, used to indicate an identity of an integrated access and backhaul node, IAB-node, or an IAB-MT or an integrated access and backhaul distributed unit, IAB-DU, in the IAB-node, in an authorization request; authorization information request indication; request information related to authorization. The method as claimed in claim 5 or 6, characterized in that The first node is a F1-terminating-donor-CU, and the second node is an AMF; and the sending second information to the second node comprises: receiving third information from a third node; sending the second information to the second node according to the third information. The method of claim 7, wherein The third information comprises at least one of the following: an identity of the second node, used to indicate an identity of a host donor-CU of an IAB-DU; an IAB-node ID. The method of claim 7 or 8, wherein The third node is any of the following: an IAB-node; an RRC-terminating-donor-CU. A method of authorization, characterized in that The method is performed by a second node, and the method comprises: sending first information to a first node, the first information being information related to authorization of a mobile integrated access and backhaul, IAB, node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device. The method of claim 10, wherein The first information comprises at least one of the following: authorization information; an integrated access and backhaul node identifier, IAB-node ID; information indicating authorization failure. The method of claim 11, wherein The IAB-node ID comprises any of the following: a global identifier of an integrated access and backhaul mobile terminal, IAB-MT; a terminal identifier, UE ID, of the IAB-MT on an Xn interface application protocol, XnAP; a UE ID of the IAB-MT on a next generation interface application protocol, NGAP; a UE ID of the IAB-MT on a F1 interface application protocol, F1AP; a backhaul adaptation protocol address, BAP address. The method of any of claims 10-12, wherein: the first node is a F1-terminating-donor-CU and the second node is a radio resource control-terminating-donor-CU, RRC-terminating-donor-CU; or the first node is a F1-terminating-donor-CU and the second node is an access and mobility management function, AMF. The method of claim 13, wherein The sending of the first information to the first node comprises: receiving second information sent by the first node and sending the first information to the first node according to the second information. The method of claim 14, wherein The second information comprises at least one of the following: an IAB-node ID, used to indicate an integrated access and backhaul node, IAB-node, for which authorization is requested, or an IAB-MT in the IAB-node or an identifier of an integrated access and backhaul distributed unit, IAB-DU; authorization information request indication; request information related to authorization. The method of claim 13, wherein The sending of the first information to the first node comprises: receiving identification information for authorization request from a third node and sending the first information to the first node according to the identification information. The method of claim 16, wherein The third node is any of the following: an integrated access and backhaul node, IAB-node; an IAB-MT; an IAB-DU; an operation administration and maintenance, OAM; a donor-CU of the IAB-MT. The method of claim 16 or 17, wherein The identification information comprises at least one of the following: a next generation radio access network node identifier, NG-RAN node ID, used to indicate an identifier of a donor-CU of an IAB-DU; a new generation cell global identifier, NCGI, and a length of the NG-RAN node ID, used to indicate an identifier of the donor-CU of the IAB-DU; an IAB-node ID, used to indicate an IAB-node, or an IAB-MT in the IAB-node or an IAB-DU. The method of any of claims 10-12, wherein: The first node is an F1-terminating-donor-CU, and the second node is an integrated access and backhaul node (IAB-node). The method of claim 19, wherein The sending of the first information to the first node comprises: The third node receives the first information from the second node and sends the first information to the first node. The method of claim 20, wherein The third node is a donor-CU of an IAB-MT. A method of authorization, characterized in that The method is performed by a third node, and the method comprises: The third node sends identification information for an authorization request to a second node, the identification information being used by the second node to send first information to a first node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device. The method of claim 22, wherein The first information comprises at least one of the following information: authorization information; an identity of an integrated access and backhaul node (IAB-node ID); information indicating authorization failure. The method of claim 23, wherein The IAB-node ID comprises any one of the following: a global identity of an integrated access and backhaul mobile terminal (IAB-MT); a terminal identity (UE ID) of the IAB-MT on an Xn interface application protocol (XnAP); a UE ID of the IAB-MT on a next generation interface application protocol (NGAP); a UE ID of the IAB-MT on an F1 interface application protocol (F1AP); and a backhaul adaptation protocol address (BAP address). The method of claim 22, wherein The identification information comprises at least one of the following information: a next generation radio access network node identity (NG-RAN node ID) used to indicate an identity of a donor-CU of an integrated access and backhaul distributed unit (IAB-DU); a new cell global identity (NCGI) and a length of the NG-RAN node ID used to indicate the identity of the donor-CU of the IAB-DU; and an IAB-node ID used to indicate an identity of an integrated access and backhaul node (IAB-node) or an IAB-MT or an IAB-DU in the IAB-node. The method of any one of claims 22 to 25, wherein: the first node is an F1-terminating-donor-CU, the second node is a radio resource control-terminating-donor-CU (RRC-terminating-donor-CU), and the third node is an IAB-MT or an operation administration and maintenance (OAM); or the first node is an F1-terminating-donor-CU, the second node is an access and mobility management function (AMF), and the third node is an IAB-MT or a radio resource control-terminating-donor-CU (RRC-terminating-donor-CU). A method of authorization, characterized in that The method is performed by a third node, and the method comprises: sending, by a second node, first information to a first node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device. The method of claim 27, wherein The first information includes at least one of the following: authorization information; an identity of an integrated access and backhaul node (IAB-node ID); information indicating authorization failure. The method of claim 28 wherein The IAB-node ID includes any of the following: a global identity of an integrated access and backhaul mobile terminal (IAB-MT); a terminal identity of the IAB-MT on an Xn interface application protocol (XnAP); a terminal identity of the IAB-MT on a next generation interface application protocol (NGAP); a terminal identity of the IAB-MT on an F1 interface application protocol (F1AP); a backhaul adaptation protocol address (BAP address). The method of any of claims 27-29, wherein: the first node is an F1-terminating-donor-CU, the second node is an integrated access and backhaul node (IAB-node), and the third node is a donor-CU of the IAB-MT. A method of authorization, characterized in that The method is performed by a third node, and the method includes: sending, to a first node, third information for the first node to send second information to a second node, the second information being used by the second node to send first information to the first node, the first information being information related to authorization of a mobile integrated access and backhaul (IAB) node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide service to a terminal device. The method of claim 31, wherein The first information includes at least one of the following: authorization information; an identity of an integrated access and backhaul node (IAB-node ID); information indicating authorization failure. The method of claim 32, wherein The IAB-node ID includes any of the following: a global identity of an integrated access and backhaul mobile terminal (IAB-MT); a terminal identity of the IAB-MT on an Xn interface application protocol (XnAP); a terminal identity of the IAB-MT on a next generation interface application protocol (NGAP); a terminal identity of the IAB-MT on an F1 interface application protocol (F1AP); a backhaul adaptation protocol address (BAP address). The method of any one of claims 31 to 33, wherein The third information includes at least one of the following: an identity of the second node, indicating an identity of a host centralized unit (donor-CU) of an integrated access and backhaul distributed unit (IAB-DU); an IAB-node ID. The method of any of claims 31-34, wherein: The first node is an F1-terminating-donor-CU, the second node is an AMF, and the third node is an IAB-node or an RRC-terminating-donor-CU. A method of authorization, characterized in that The method is used for a communication system, and the method comprises: The second node sends first information to the first node, the first information being information related to authorization of a mobile IAB node. The first node receives the first information and determines whether the mobile IAB node is authorized to provide services to a terminal device according to the first information. A first communication device, characterized in that The apparatus comprises: The transceiver module is configured to receive first information from a second node, the first information being information related to authorization of a mobile IAB node. The processing module is configured to determine whether the mobile IAB node is authorized to provide services to a terminal device according to the first information. A second communication device, characterized in that The apparatus comprises: The transceiver module is configured to send first information to a first node, the first information being information related to authorization of a mobile IAB node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device. A third communication device, characterized in that The apparatus comprises: The transceiver module is configured to send identification information for an authorization request to a second node, the identification information being used by the second node to send first information to a first node, the first information being information related to authorization of a mobile IAB node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device. A fourth communication device, characterized in that The apparatus comprises: The transceiver module is configured to send first information to a first node through a second node, the first information being information related to authorization of a mobile IAB node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device. A fifth communication device, characterized in that The apparatus comprises: The transceiver module is configured to send third information to a first node, the third information being used by the first node to send second information to a second node, the second information being used by the second node to send first information to the first node, the first information being information related to authorization of a mobile IAB node, wherein the first information is used by the first node to determine whether the mobile IAB node is authorized to provide services to a terminal device. A communication device, characterized by The apparatus comprises: One or more processors; The processor is configured to invoke instructions to cause the communication apparatus to perform the authorization method of any one of claims 1-9, 10-21, 22-26, 27-30, and 31-35. A communication system characterized by The apparatus comprises: A first node and a second node, wherein the first node is configured to implement the authorization method of any one of claims 1-9, and the second node is configured to implement the authorization method of any one of claims 10-21. A storage medium storing instructions, the instructions comprising: When the instructions are run on a communications device, cause the communications device to perform the method of authorizing of any of claims 1-9, 10-21, 22-26, 27-30, 31-35.

Images