Node authorization method, communication device and communication system

Abstract

The present disclosure relates to a node authorization method, a communication device, and a communication system, the method comprising: receiving a first message sent by a second node, the first message comprising first information of the second node; and a second message is sent to the third node, the second message comprises the first information, the second message is used for obtaining authorization information of the second node, and the authorization information is used for determining whether the second node is authorized to provide service for the terminal. Therefore, whether the first node can provide service authorization for the terminal or not can be realized, and the second node can be effectively managed according to the authorization information of the second node.

Description

Node authorization method, communication device, and communication system Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a node authorization method, communication equipment, and a communication system. Background Art

[0002] Integrated access and backhaul (IAB) supports millimeter wave base stations for wireless access and backhaul, effectively reducing the need for additional fiber deployment when deploying dense networks.

[0003] Summary of the Invention

[0004] The method disclosed in the present invention can be used to solve the technical problem of "how to authorize a node including an access network part and a terminal part".

[0005] The embodiments of the present disclosure provide a node authorization method, a communication device, and a communication system.

[0006] According to a first aspect of an embodiment of the present disclosure, a node authorization method is provided, which is performed by a first node. The method includes:

[0007] receiving a first message sent by a second node, where the first message includes first information of the second node;

[0008] A second message is sent to a third node, where the second message includes the first information, and the second message is used to obtain authorization information of the second node, where the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

[0009] According to a second aspect of an embodiment of the present disclosure, a node authorization method is provided, which is performed by a third node. The method includes:

[0010] receiving a second message sent by the first node, where the second message includes the first information of the second node;

[0011] According to the second message, authorization information of the second node is acquired, where the authorization information is used to determine whether the second node is authorized to provide a service to the terminal.

[0012] According to a third aspect of an embodiment of the present disclosure, a node authorization method is provided, which is performed by a second node. The method includes:

[0013] A first message is sent to a first node, where the first message includes first information of the second node, and the first message is used to obtain authorization information of the second node, where the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

[0014] According to a fourth aspect of an embodiment of the present disclosure, a node authorization method is proposed, including:

[0015] The second node sends a first message to the first node, where the first message includes first information of the second node;

[0016] The first node sends the second message to the third node, where the second message includes the first information;

[0017] The third node obtains authorization information of the second node according to the second message, where the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

[0018] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided, serving as a first node, including:

[0019] A transceiver module is used to receive a first message sent by a second node, where the first message includes first information of the second node; and send a second message to a third node, where the second message includes the first information. The second message is used to obtain authorization information of the second node, and the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

[0020] According to a sixth aspect of an embodiment of the present disclosure, a communication device is provided, serving as a third node, including:

[0021] a transceiver module, configured to receive a second message sent by the first node, where the second message includes the first information of the second node;

[0022] A processing module is used to obtain authorization information of the second node according to the second message, wherein the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

[0023] According to a seventh aspect of an embodiment of the present disclosure, a communication device is provided, serving as a second node, including:

[0024] The transceiver module is used to send a first message to the first node, where the first message includes first information of the second node. The first message is used to obtain authorization information of the second node, and the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

[0025] According to a ninth aspect of an embodiment of the present disclosure, a communication device is provided, serving as a first node, including:

[0026] one or more processors;

[0027] one or more memories storing executable instructions,

[0028] When the one or more processors execute the executable instructions in the memory, the first node executes the node authorization method according to the embodiment of the first aspect.

[0029] According to a tenth aspect of an embodiment of the present disclosure, a communication device is provided, serving as a third node, including:

[0030] one or more processors;

[0031] one or more memories storing executable instructions,

[0032] Wherein, when the one or more processors execute the executable instructions in the memory, the third node execution right is enabled to perform the node authorization method according to the embodiment of the second aspect.

[0033] According to an eleventh aspect of the embodiments of the present disclosure, a communication device is provided, used as a second node, including:

[0034] one or more processors;

[0035] one or more memories storing executable instructions,

[0036] When the one or more processors execute the executable instructions in the memory, the second node executes the node authorization method according to the embodiment of the third aspect.

[0037] According to the twelfth aspect of the embodiments of the present disclosure, a communication system is proposed, including a first node, a third node, and a second node, wherein the first node is configured to implement the node authorization method described in the embodiment of the first aspect, the third node is configured to implement the node authorization method described in the embodiment of the second aspect, and the second node is configured to implement the node authorization method described in the embodiment of the third aspect.

[0038] According to the thirteenth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the node authorization method described in any one of the first, second, and third aspects.

[0039] In an embodiment of the present disclosure, a first node can receive a first message sent by a second node, the first message including first information of the second node, and send a second message including the first information to a third node. The second message can be used to obtain authorization information of the second node, thereby enabling authorization of whether the second node can provide services to the terminal, and then based on the authorization information of the second node, the second node can be effectively managed. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The above and / or additional aspects and advantages of the present disclosure will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0041] 1A-1C are schematic diagrams showing the architecture of a communication system according to an embodiment of the present disclosure;

[0042] 2A-2C are interactive diagrams illustrating a node authorization method according to an embodiment of the present disclosure;

[0043] 3A-3D are flowcharts illustrating a method for authorizing a node according to an embodiment of the present disclosure;

[0044] 4A-4F are flowcharts illustrating a method for authorizing a node according to an embodiment of the present disclosure;

[0045] FIG5 is an interactive schematic diagram of a node authorization method according to an embodiment of the present disclosure;

[0046] FIG6 is an interactive diagram illustrating a VMR authorization method according to an embodiment of the present disclosure;

[0047] FIG7A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0048] FIG7B is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0049] FIG7C is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0050] FIG8A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0051] FIG8B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0052] The embodiments of the present disclosure provide a node authorization method, a communication device, and a communication system.

[0053] In a first aspect, an embodiment of the present disclosure provides a node authorization method, which is performed by a first node. The method includes:

[0054] receiving a first message sent by a second node, where the first message includes first information of the second node;

[0055] A second message is sent to a third node, where the second message includes the first information, and the second message is used to obtain authorization information of the second node, where the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

[0056] In the above embodiment, the first node can receive a first message sent by the second node, the first message including the first information of the second node, and send a second message containing the first information to the third node. The second message can be used to obtain the authorization information of the second node, thereby realizing authorization of whether the second node can provide services to the terminal, and then based on the authorization information of the second node, the second node can be effectively managed.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0058] Receive authorization information of the second node sent by the third node or the second node.

[0059] In the above embodiment, the first node can determine whether the second node is authorized to provide services to the terminal based on the authorization information of the second node, thereby effectively managing the second node.

[0060] With reference to some embodiments of the first aspect, in some embodiments, sending the second message to the third node includes:

[0061] selecting the third node according to the first information;

[0062] The second message is sent to the third node.

[0063] In the above embodiment, by selecting the third node according to the first information and sending the second message to the selected third node, the success rate of node authorization can be improved.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, selecting the third node according to the first information includes:

[0065] A third node supporting a node authorization function is selected from a plurality of third nodes according to the first information.

[0066] In the above embodiment, the accuracy of selecting the third node can be improved, thereby improving the success rate of node authorization.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes one or more of the following:

[0068] Type indication information of the second node;

[0069] functions supported by the second node;

[0070] services supported by the second node;

[0071] The relay mode supported by the second node.

[0072] In the above embodiment, the first information may include one or more items, thereby meeting different requirements.

[0073] In combination with some embodiments of the first aspect, in some embodiments, the second message is a next generation application protocol (NGAP) message.

[0074] In the above embodiment, resources are saved by sending the first information to the third node by multiplexing the NGAP message.

[0075] In conjunction with some embodiments of the first aspect, in some embodiments, the authorization information includes one or more of the following:

[0076] authorizing the second node to provide services to the terminal;

[0077] not authorizing the second node to provide services to the terminal;

[0078] Authorizing the second node to provide functions for the terminal;

[0079] Not authorizing the second node to provide functions for the terminal;

[0080] authorizing the second node to provide services to the terminal;

[0081] not authorizing the second node to provide services to the terminal;

[0082] authorizing the second node to provide a relay mode for the terminal;

[0083] The relay mode provided by the second node to the terminal is not authorized.

[0084] In the above embodiment, the third node can send the above authorization information to the first node and the second node, so that the first node can determine whether the second node is authorized to provide services to the terminal based on the authorization information, or determine which functions or services or relay methods are authorized, thereby authorizing the functions of the second node, ensuring that the second node can accurately provide services to the terminal, and the first node can effectively manage the functions of the second node based on the authorization information.

[0085] In a second aspect, an embodiment of the present disclosure provides a node authorization method, which is performed by a third node. The method includes:

[0086] receiving a second message sent by the first node, where the second message includes the first information of the second node;

[0087] According to the second message, authorization information of the second node is acquired, where the authorization information is used to determine whether the second node is authorized to provide a service to the terminal.

[0088] In the above embodiment, the third node can obtain the authorization information of the second node according to the second message, thereby realizing authorization of whether the second node can provide services to the terminal.

[0089] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0090] The authorization information is sent to the second node and / or the first node.

[0091] In the above embodiment, the third node can send the authorization information to the second node and / or the first node in a flexible manner, and the first node can manage the second node according to the authorization information, and the second node can determine whether it is authorized to provide services to the terminal according to the authorization information.

[0092] In conjunction with some embodiments of the first aspect, in some embodiments, sending the authorization information to the second node and / or the first node includes:

[0093] Sending a non-access stratum (NAS) message to the second node, where the NAS message includes the authorization information, and / or sending an NGAP message to the first node, where the NGAP message includes the authorization information.

[0094] In the above embodiment, the authorization information may be sent to the second node by multiplexing a NAS message, and the authorization information may be sent to the first node by multiplexing a NGAP message, thereby saving resources.

[0095] 、

[0096] In conjunction with some embodiments of the first aspect, in some embodiments, obtaining the authorization information of the second node according to the second message includes at least one of the following:

[0097] acquiring the authorization information from a fourth node according to the type indication information of the second node included in the first information;

[0098] The authorization information is obtained from the fourth node according to one or more of the functions, services, and relay modes supported by the second node contained in the first information.

[0099] In the above embodiment, by sending the type indication information of the second node to the fourth node and obtaining the authorization information of the second node returned by the fourth node, the authorization of the second node according to the type indication information of the second node is realized. By sending one or more of the functions, services, and relay modes supported by the second node to the fourth node, the fourth node can determine the authorization of the second node according to one or more of the functions, services, and relay modes supported by the second node, and return it to the third node, thereby realizing authorization of whether the second node provides services to the terminal.

[0100] In conjunction with some embodiments of the first aspect, in some embodiments, the authorization information includes one or more of the following:

[0101] authorizing the second node to provide services to the terminal;

[0102] not authorizing the second node to provide services to the terminal;

[0103] Authorizing the second node to provide functions for the terminal;

[0104] Not authorizing the second node to provide functions for the terminal;

[0105] authorizing the second node to provide services to the terminal;

[0106] not authorizing the second node to provide services to the terminal;

[0107] authorizing the second node to provide a relay mode for the terminal;

[0108] The relay mode provided by the second node to the terminal is not authorized.

[0109] In the above embodiment, the third node can send the above authorization information to the first node and the second node, so that the first node can determine whether the second node is authorized to provide services to the terminal based on the authorization information, or determine which functions or services or relay methods are authorized, thereby effectively managing the second node.

[0110] In a third aspect, an embodiment of the present disclosure provides a node authorization method, which is performed by a second node. The method includes:

[0111] A first message is sent to a first node, where the first message includes first information of the second node, and the first message is used to obtain authorization information of the second node, where the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

[0112] In the above embodiment, by sending a first message to the first node, the first node sends a second message to the third node, and the second message includes the first information of the second node, so that the third node can obtain the authorization information of the second node based on the second message, thereby realizing authorization of whether the second node provides services to the terminal.

[0113] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0114] Receive the authorization information sent by the third node or the first node.

[0115] In the above embodiment, the second node can determine whether it is authorized to provide services to the terminal based on the authorization information. If it is authorized to provide services to the terminal, the second node can work as an access network device and the terminal can access the network through the second node.

[0116] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0117] The second node switches from accessing the first node to accessing the target first node, and sends the authorization information to the target first node; or

[0118] The terminal part of the second node and the first node connected to the access network part of the second node are different. The first node connected to the terminal part of the second node sends the authorization information to the first node connected to the access network part of the second node.

[0119] In the above embodiment, when a change occurs to the first node to which the second node is connected, the second node can notify the target first node of the second node's authorization information, thereby enabling the target first node to effectively manage the second node. Alternatively, when the second node's terminal portion is different from the first node to which the access network portion is connected, the first node to which the second node's terminal portion is connected can send authorization information to the first node to which the second node's access network portion is connected, thereby enabling the first node to which the second node's access network portion is connected to obtain the second node's authorization information in a timely manner.

[0120] In conjunction with some embodiments of the first aspect, in some embodiments, the authorization information includes one or more of the following:

[0121] authorizing the second node to provide services to the terminal;

[0122] not authorizing the second node to provide services to the terminal;

[0123] Authorizing the second node to provide functions for the terminal;

[0124] Not authorizing the second node to provide functions for the terminal;

[0125] authorizing the second node to provide services to the terminal;

[0126] not authorizing the second node to provide services to the terminal;

[0127] authorizing the second node to provide a relay mode for the terminal;

[0128] The relay mode provided by the second node to the terminal is not authorized.

[0129] In the above embodiment, the second node can determine whether the second node is authorized to provide services to the terminal based on the authorization information, or determine which functions or services or relay modes are authorized, thereby ensuring that the second node can accurately provide services to the terminal.

[0130] In a fourth aspect, an embodiment of the present disclosure provides a node authorization method, including:

[0131] The second node sends a first message to the first node, where the first message includes first information of the second node;

[0132] The first node sends the second message to the third node, where the second message includes the first information;

[0133] The third node obtains authorization information of the second node based on the second message, and the authorization information is used to determine whether the second node is authorized to provide services to the terminal. In the above embodiment, the second node sends the first message to the first node, the first node sends the second message to the third node, and the third node obtains the authorization information of the second node based on the second message, thereby authorizing the second node to provide services to the terminal.

[0134] In the fifth aspect, an embodiment of the present disclosure proposes a communication device, which is used as a first node. The above-mentioned communication device includes at least one of a transceiver module and a processing module: wherein the above-mentioned communication device is used to execute the first aspect and the optional implementation method of the first aspect.

[0135] In a sixth aspect, an embodiment of the present disclosure proposes a communication device used as a third node, wherein the communication device includes at least one of a transceiver module and a processing module: wherein the communication device is used to execute the second aspect.

[0136] In the seventh aspect, an embodiment of the present disclosure proposes a communication device, which is used as a second node. The above-mentioned communication device includes at least one of a transceiver module and a processing module: wherein the above-mentioned communication device is used to execute the third aspect and the optional implementation method of the third aspect.

[0137] In an eighth aspect, an embodiment of the present disclosure proposes a communication device, which is used as a first node. The above-mentioned first node includes: one or more processors; wherein, the first node is used to execute the first aspect and the optional implementation method of the first aspect.

[0138] In a ninth aspect, an embodiment of the present disclosure proposes a communication device used as a third node, and the above-mentioned third node includes: one or more processors; wherein, the third node is used to execute the second aspect and the optional implementation method of the second aspect.

[0139] In the tenth aspect, an embodiment of the present disclosure proposes a communication device used as a second node, and the above-mentioned second node includes: one or more processors; wherein, the second node is used to execute the third aspect and the optional implementation method of the third aspect.

[0140] In the eleventh aspect, an embodiment of the present disclosure proposes a communication system, including a first node, a third node, and a second node, wherein the first node is configured to implement the method described in the first aspect and the optional implementation of the first aspect, the third node is configured to implement the method described in the second aspect and the optional implementation of the second aspect, and the second node is configured to implement the method described in the third aspect and the optional implementation of the third aspect.

[0141] In the twelfth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect, and the optional implementation of the third aspect.

[0142] In the thirteenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect, and the optional implementation of the third aspect.

[0143] In the fourteenth aspect, an embodiment of the present disclosure proposes a computer program, which, when running on a computer, enables the computer to execute the method described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect, and the optional implementation of the third aspect.

[0144] In a fifteenth aspect, an embodiment of the present disclosure provides a chip or chip system. The chip or chip system includes a processing circuit configured to execute the method described in accordance with the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect, and the optional implementation of the third aspect.

[0145] It is understandable that the above-mentioned communication devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0146] The disclosed embodiments provide a node authorization method, communication device, and communication system. In some embodiments, the node authorization method, information processing method, and communication method are interchangeable; the information transmission device, information processing device, and communication device are interchangeable; and the information processing system and communication system are interchangeable.

[0147] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0148] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0149] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0150] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0151] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0152] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0153] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0154] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0155] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0156] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0157] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0158] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0159] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0160] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0161] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, it can also be called device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, language such as "uplink" and "downlink" can also be replaced by language corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0162] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0163] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0164] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0165] As shown in FIG1 , a communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .

[0166] In some embodiments, the terminal 101 includes, for example, a second node or a terminal functional part in the second node, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, 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 a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0167] In some embodiments, the second node may include a terminal function part (or called terminal part), an access network function part (or called access network part), etc. Optionally, if the second node is not authorized to provide services to the terminal, the second node is only used as the terminal 101.

[0168] In some embodiments, the second node includes, for example, any one of “VMR”, “mobile IAB”, and “mobile base station relay (MBSR)”, but is not limited thereto.

[0169] Exemplarily, the VMR may include a VMR access network part, a VMR-MT, a core network function part (eg, part of the UPF), a local data network, and the like.

[0170] In some embodiments, the terms "VMR-MT", "vehicle-mounted relays mobile terminal (VMR-MT)", "VMR terminal part" and the like may be used interchangeably.

[0171] In some embodiments, terms such as "VMR access network part", "VMR-gNB", "vehicle-mounted relays generation nodeB (VMR-gNB)", and "VMR-RAN" can be used interchangeably.

[0172] Exemplarily, mobile IAB may include mobile IAB-gNB, mobile IAB-MT, etc.

[0173] In some embodiments, the terms "mobile IAB-MT", "mobile IAB terminal part", etc. can be used interchangeably.

[0174] In some embodiments, terms such as "mobile IAB-gNB", "mobile IAB access network part", and "mobile IAB-RAN" can be used interchangeably.

[0175] Exemplarily, MBSR may include MBSR-gNB, MBSR-MT, etc.

[0176] In some embodiments, the terms "MBSR-MT", "MBSR UE", "MBSR terminal part", etc. can be used interchangeably.

[0177] In some embodiments, terms such as "MBSR-gNB", "MBSR-RAN", "MBSR access network part", etc. can be used interchangeably.

[0178] In some embodiments, the access network device 102 is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of a first node, an evolved NodeB (eNB) in a 5G communication system, a next generation eNB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto. In some embodiments, the first node may manage the accessed second node. Illustratively, the first node is, for example, a VMR-donor, a mobile IAB-donor, an MBSR-donor, and the like.

[0179] In some embodiments, if the second node is authorized to provide services to the terminal, the second node may serve as the access network device 102, but is not limited thereto. In other words, the access network device 102 may include the second node, or include the access network functional part of the second node.

[0180] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0181] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0182] In some embodiments, the core network device 103 may be a single device including a third node, a fourth node, etc., or may be a plurality of devices or a device group including all or part of the third node, the fourth node, etc. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0183] In some embodiments, the first node may serve as the core network device 103, but is not limited thereto.

[0184] In some embodiments, the first node may be independent of the core network device 103 .

[0185] In some embodiments, the first node may be part of the core network device 103 .

[0186] In some embodiments, the third node has an authentication management function. Exemplarily, the third node has a node authorization function and can initiate a node authorization process.

[0187] In some embodiments, the third node includes, for example, an authentication management function (AMF) network element, other nodes with node authorization functions, etc.

[0188] In some embodiments, the third node may be independent of the core network device 103 .

[0189] In some embodiments, the third node may be part of the core network device 103 .

[0190] In some embodiments, the fourth node may store authorization information of the terminal. Exemplarily, the fourth node includes, for example, a unified data management (UDM) function or other nodes that store authorization information of the terminal.

[0191] In some embodiments, the fourth node may be independent of the core network device 103 .

[0192] In some embodiments, the fourth node may be part of the core network device 103 .

[0193] In some embodiments, the third node may obtain the authorization information of the first node from the fourth node.

[0194] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0195] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0196] The 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 (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0197] In some embodiments, IAB can support millimeter wave base stations for wireless access and backhaul, effectively reducing the need for additional fiber deployment in dense network deployments and enabling wireless relay in NG-RAN. The relay node, referred to as an IAB-node, supports wireless access and backhaul over NR. Optionally, the network-side NR backhaul termination node, referred to as an IAB-donor, is a gNB with IAB functionality.

[0198] In some embodiments, backhaul may be performed via a single hop or multiple hops.

[0199] In some embodiments, as shown in Figure 1B , the NG-RAN can support IAB by wirelessly connecting to a gNB capable of serving the IAB-node (referred to as an IAB-donor) via an IAB-node. The IAB-donor may include one IAB-donor-CU and one or more IAB-donor-DUs. When the gNB-CU-CP and gNB-CU-UP are separated, the IAB-donor may include one IAB-donor-CU-CP, multiple IAB-donor-CU-UPs, and multiple IAB-donor-DUs. The IAB-node can connect to an upstream IAB-node or IAB-donor-DU via a subset of terminal functions on the NR Uu interface (referred to as the IAB-MT function in the IAB-node). The IAB-node can provide wireless backhaul to downstream IAB-nodes and terminals via network functions on the NR Uu interface (referred to as the IAB-DU function in the IAB-node).

[0200] In some embodiments, the F1-C traffic between the IAB-node and the IAB-donor-CU may be backhauled via the IAB-donor-DU and an optional intermediate hop IAB-node.

[0201] In some embodiments, the F1-U traffic between the IAB-node and the IAB-donor-CU is backhauled via the IAB-donor-DU and an optional intermediate hop IAB-node.

[0202] In some embodiments, Mobile IAB may also be referred to as VMR, because VMR can be deployed on mobile vehicles, such as cars, buses, airplanes, etc., to support more deployment scenarios, such as local service access, local communication, etc.

[0203] In some embodiments, the IAB-node (VMR) may include an IAB-DU (ie, DU part) and an IAB-MT (ie, terminal part). Exemplarily, the DU part of the IAB may be referred to as an access network part.

[0204] In some embodiments, as shown in Figure 1C , a VMR may include an access network component (VMR-gNB), a terminal component (VMR-MT), a local user port function (local UPF), and local network data. The VMR may be connected to a VMR donor node (VMR-donor), which in turn may be connected to the core network.

[0205] In some embodiments, when the mobile IAB-MT performs initial registration with the serving public land mobile network (PLMN), it indicates in the request that it is a mobile IAB. The AMF can authorize the mobile IAB based on the subscription information and provide a mobile IAB authorization indication to the NG-RAN.

[0206] In some embodiments, as part of the registration process, the AMF to which the mobile IAB is connected may indicate to the IAB-MT that the IAB-node is not allowed to act as a mobile IAB node. In this case, the AMF does not send a mobile IAB authorization indication to the donor-gNB. Optionally, the AMF may provide an indication in the Registration Accept (if the PLMN allows the IAB-MT to register in the PLMN) or the Registration Reject (if the PLMN does not allow the IAB-MT to register in the PLMN).

[0207] Because the functions and services provided by VMR are different from those of mobile IAB, the mobile IAB authorization mechanism does not support VMR authorization.

[0208] Based on this, the present disclosure proposes a node authorization method.

[0209] FIG2A is an interactive diagram illustrating a node authorization method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to a node authorization method for a communication system 100, the method comprising:

[0210] Step S2101: The second node sends a first message to the first node.

[0211] In some embodiments, the first message may be a radio resource control (RRC) message. Exemplarily, the RRC message may be an RRC setup complete message.

[0212] In some embodiments, the terminal portion of the second node sends the first message to the first node.

[0213] In some embodiments, the first node receives a first message sent by the second node.

[0214] In some embodiments, the first node may be the first node to which the second node accesses.

[0215] In some embodiments, the first node may be the first node to which a terminal portion of the second node accesses.

[0216] In some embodiments, the first message may include first information of the second node.

[0217] In some embodiments, the first information may be used to assist the first node in selecting a third node, so that the first node selects a suitable AMF to register the second node (for example, an authorization process may be included).

[0218] In some embodiments, the first information may include one or more of the following: type indication information of the second node; functions supported by the second node; services supported by the second node; and relay modes supported by the second node.

[0219] Exemplarily, the type indication information of the second node can be used to indicate what type of device the second node is, for example, the type indication information of the second node is used to indicate that the second node is a VMR device, so that the first node selects a suitable core network node (e.g., AMF) for the second node to perform further operations (e.g., performing registration, authentication and / or authorization processes).

[0220] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0221] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high or upper layers, obtaining by self-processing, autonomous implementation, etc.

[0222] In some embodiments, the terms "access," "connect," and the like may be used interchangeably.

[0223] Step S2102: The first node sends a second message to the third node.

[0224] In some embodiments, the second message may be an NGAP message. Exemplarily, the NGAP message may be an initial UE message.

[0225] In some embodiments, the second message may include the first information of the second node.

[0226] In some embodiments, the first node may select a third node based on the first information and send a second message to the third node.

[0227] Optionally, the first node may select a third node that supports the node authorization function from multiple third nodes based on the first information. Exemplarily, if there are multiple third nodes that support the node authorization function, the third node may be selected randomly or based on a policy (e.g., network load).

[0228] Exemplarily, if the first information includes type indication information of the second node, the first node may consider that the second node wants to authorize information and may select a third node having a node authorization function from multiple third nodes.

[0229] Exemplarily, if the first information includes type indication information of the second node, the first node selects a third node that supports the type of authorization according to the type indication information and performs a further authorization process.

[0230] Exemplarily, if the first information includes second node type indication information as VMR, the first node selects a third node (such as AMF) that supports VMR authorization as the core network node connected to the second node, and authorizes the second node.

[0231] In some embodiments, the second node may access the core network through a third node.

[0232] In some embodiments, the terminal portion in the second node accesses the core network through a third node.

[0233] In some embodiments, the third node may receive the second message sent by the first node.

[0234] In some embodiments, the second message may be used to obtain authorization information of the second node.

[0235] In some embodiments, the third node may obtain authorization information of the second node according to the second message, wherein the authorization information may be used to determine whether the second node is authorized to provide services to the terminal.

[0236] In some embodiments, the third node can send the type indication information of the second node contained in the first information to the fourth node. The fourth node can find the authorization information of the second node based on the type indication information of the second node, and send the authorization information of the second node to the third node, so that the third node can receive the authorization information sent by the fourth node.

[0237] In some embodiments, the third node may obtain the authorization information of the second node from the fourth node based on one or more of the functions, services, and relay modes supported by the second node contained in the first information.

[0238] Exemplarily, the third node can send one or more of the functions, services, and relay modes supported by the second node to the fourth node, and the fourth node can send the second node's authorization information to the third node based on one or more of the functions, services, and relay modes supported by the second node, so that the third node can receive the authorization information sent by the fourth node.

[0239] In some embodiments, the authorization information may include one or more of the following:

[0240] authorizing the second node to provide services to the terminal;

[0241] The second node is not authorized to provide services to the terminal;

[0242] Authorize the second node to provide functions for the terminal;

[0243] The functions provided by the second node to the terminal are not authorized;

[0244] Authorizing the second node to provide services to the terminal;

[0245] Not authorizing the second node to provide services to the terminal;

[0246] Authorize the second node to provide a relay mode for the terminal;

[0247] The relay mode provided by the second node to the terminal is not authorized.

[0248] Exemplarily, the authorization information may be indication information that may indicate whether the second node is authorized to provide services for the terminal. Exemplarily, the authorization information may specifically include the functions for which the second node is authorized or unauthorized. Exemplarily, the authorization information may specifically include the services for which the second node is authorized or unauthorized. Exemplarily, the authorization information may specifically include the relay modes for which the second node is authorized or unauthorized.

[0249] In some embodiments, the authorization information may be authorized by function, and the functions that the second node may be authorized or unauthorized may include one or more of the following:

[0250] The second node has the access network device DU function;

[0251] The second node has the access network device CU-UP function;

[0252] The second node has the function of access network equipment;

[0253] The second node has UPF functionality;

[0254] The second node has a local data network function;

[0255] The second node has N3IWF.

[0256] In some embodiments, the authorization information may be authorized by service, and the services for which the second node may be authorized or not authorized may include one or more of the following:

[0257] local services;

[0258] local exchange services;

[0259] UP services;

[0260] CP services;

[0261] Non-3GPP access services;

[0262] Protocol data unit (PDU) session echo service.

[0263] In some embodiments, the local service refers to a service that the second node can support for the terminal to access a local service through the second node, so as to reduce the service latency;

[0264] In some embodiments, the local switching service means that at least two terminals served by the second node can communicate directly through the second node without passing through the core network, thereby reducing communication latency;

[0265] In some embodiments, the UP service refers to a service in which the second node provides a user plane;

[0266] In some embodiments, the CP service refers to a service provided by the second node to provide a control plane;

[0267] In some embodiments, the non-3GPP access service means that the second node can support the terminal to access the second node through a non-3GPP access technology and connect to the core network through the second node. The non-3GPP access technology includes but is not limited to: Wi-Fi, Bluetooth.

[0268] In some embodiments, the PDU session backhaul service means that the second node can serve as a backhaul network for information interaction between the terminal and the core network through the logical channel of the PDU session, wherein the terminal is a terminal that accesses the core network through the second node.

[0269] In some embodiments, the authorization information may be authorized in a relay manner, and the relay manners in which the second node may be authorized or unauthorized may include one or more of the following:

[0270] Layer 2 relay;

[0271] Layer 3 relay;

[0272] multi-hop;

[0273] Single hop.

[0274] Step S2103: The third node sends the authorization information of the second node to the first node.

[0275] In some embodiments, the third node may send an NGAP message to the first node, and the NGAP message may include authorization information of the second node. Exemplarily, the NGAP message may be a UE context establishment request message or a UE context modification request message.

[0276] In some embodiments, the first node receives authorization information of the second node sent by the third node.

[0277] In some embodiments, the first node may determine the services that the second node can provide to the terminal based on the authorization information of the second node, thereby managing the second node.

[0278] In some embodiments, the first node can determine whether the second node is authorized to provide services to the terminal based on the authorization information. If it is authorized to provide services to the terminal, it can be considered that the second node can work as an access network device, and the terminal can access the network through the second node. The first node can determine the specific services that can be provided to the terminal based on the authorization information, thereby managing the second node.

[0279] Step S2104: The third node sends the authorization information of the second node to the second node.

[0280] In some embodiments, the third node may send a NAS message to the second node, and the NAS message may include authorization information of the second node.

[0281] In some embodiments, the second node receives authorization information of the second node sent by the third node.

[0282] Optionally, the terminal part of the second node receives the authorization information of the second node sent by the third node.

[0283] In some embodiments, the first node can determine whether the second node can provide services to the terminal based on the authorization information. If the authorization information indicates that the second node can provide services to the terminal, it can determine which services the second node can provide to the terminal, so that the second node can provide corresponding services to the terminal.

[0284] In some embodiments, “the second node can provide services to other terminals” includes at least one of the following:

[0285] The terminal part of the second node may send the first information to the first node when the RRC is established;

[0286] The second node may establish at least one cell to provide services for the terminal;

[0287] When the network does not support multi-hop, the terminal part of the second node cannot access the cell provided by other VMR devices.

[0288] In some embodiments, the second node can determine whether it is authorized to provide services to the terminal based on the authorization information. If authorized to provide services to the terminal, it can be considered that the second node can operate as an access network device, and the terminal can access the network through the second node. The second node can determine the specific services that can be provided to the terminal based on the authorization information. Exemplarily, the second node being authorized to provide services to the terminal can be understood as the terminal portion of another second node or the UE can access the network through the second node.

[0289] In some embodiments, the second node is not authorized to provide services to the terminal, which means that the second node cannot work as an access network device and can only be used as a terminal.

[0290] Exemplarily, the second node is a VMR. If the VMR is not authorized to provide services to the terminal, that is, the VMR cannot function as an access network device, the VMR may perform at least one of the following operations:

[0291] Move the terminal being served to another available base station or VMR;

[0292] When the RRC connection is established, no VMR indication is provided to the VMR-donor;

[0293] No logical connection establishment related to non-VMR-MT between the VMR-donor and the VMR-donor will be initiated.

[0294] In some embodiments, when a first node switches from accessing a first node to accessing a target first node, the first node may send authorization information of the second node to the target first node. That is, when a first node accessed by the second node switches from a source first node to a target first node, the second node may send authorization information of the second node to the target first node.

[0295] Exemplarily, the second node accessing the first node can be that the terminal part of the second node accesses the first node, the terminal part of the second node switches from accessing the first node to the target first node, and the terminal part of the second node can send the authorization information of the second node to the target first node. Optionally, the authorization information can be transmitted by an XnAP message.

[0296] In some embodiments, when the terminal part of the second node and the first node connected to the access network part of the second node are different, the first node connected to the terminal part of the second node can send second node authorization information to the first node connected to the access network part of the second node. Optionally, the authorization information can be transmitted by an XnAP message.

[0297] In some embodiments, steps S2103 and S2104 may be executed in an interchanged order or simultaneously.

[0298] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2104. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, step S2104 may be implemented as an independent embodiment, step S2101 and step S2102 may be implemented as independent embodiments, step S2101, step S2102, and step S2103 may be implemented as independent embodiments, and step S2101, step S2102, and step S2104 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0299] In some embodiments, one or more of these steps may be omitted or replaced in different embodiments.

[0300] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0301] FIG2B is an interactive diagram illustrating a node authorization method according to an embodiment of the present disclosure. As shown in FIG2B , the present disclosure embodiment relates to a node authorization method for a communication system 100, the method comprising:

[0302] Step S2201: The second node sends a first message to the first node.

[0303] The optional implementation of step S2201 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0304] Step S2202: The first node sends a second message to the third node.

[0305] The optional implementation of step S2202 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0306] Step S2203: The third node sends the authorization information of the second node to the first node.

[0307] The optional implementation of step S2203 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0308] Step S2204: The first node sends authorization information of the second node to the second node.

[0309] In some embodiments, the second node may receive the authorization information of the second node sent by the first node.

[0310] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2204. For example, step S2201 may be implemented as an independent embodiment, step S2202 may be implemented as an independent embodiment, step S2203 may be implemented as an independent embodiment, step S2204 may be implemented as an independent embodiment, step S2201 and step S2202 may be implemented as independent embodiments, and steps S2201, S2202, and S2203 may be implemented as independent embodiments, but are not limited thereto.

[0311] In some embodiments, one or more of these steps may be omitted or replaced in different embodiments.

[0312] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0313] FIG2C is an interactive diagram illustrating a node authorization method according to an embodiment of the present disclosure. As shown in FIG2C , the present disclosure embodiment relates to a node authorization method for a communication system 100, the method comprising:

[0314] Step S2301: The second node sends a first message to the first node.

[0315] The optional implementation of step S2201 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0316] Step S2302: The first node sends a second message to the third node.

[0317] The optional implementation of step S2202 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0318] Step S2303: The third node sends the authorization information of the second node to the second node.

[0319] The optional implementation of step S2203 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0320] Step S2304: The second node sends authorization information of the second node to the first node.

[0321] In some embodiments, the first node may receive authorization information of the second node sent by the second node.

[0322] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S2301 to S2304. For example, step S2301 may be implemented as an independent embodiment, step S2302 may be implemented as an independent embodiment, step S2303 may be implemented as an independent embodiment, step S2304 may be implemented as an independent embodiment, step S2301 and step S2302 may be implemented as independent embodiments, and steps S2301, S2302, and S2303 may be implemented as independent embodiments, but are not limited thereto.

[0323] In some embodiments, one or more of these steps may be omitted or replaced in different embodiments.

[0324] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0325] FIG3A is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to a node authorization method, which can be executed by a second node, and the method includes:

[0326] Step S3101, sending the first message.

[0327] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0328] In some embodiments, the second node sends the first message to the first node, but is not limited thereto, and the first message may also be sent to other entities.

[0329] Optionally, the first information included in the first message can be used by the first node to select the third node. For optional implementations, see the optional implementations of step S2102 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be repeated here.

[0330] Step S3102: Obtain authorization information of the second node.

[0331] The optional implementation of step S3102 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0332] In some embodiments, the second node may receive authorization information sent by the third node or the first node, but is not limited thereto and may also receive authorization information sent by other entities.

[0333] In some embodiments, the second node obtains authorization information specified by the protocol.

[0334] In some embodiments, the second node obtains authorization information from upper layer(s).

[0335] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, and steps S3101 and S3102 may be implemented as independent embodiments, but are not limited thereto.

[0336] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0337] FIG3B is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a node authorization method, which is executed by a second node, and the method includes:

[0338] Step S3201: Send a first message to a first node.

[0339] Optional implementations of step S3201 can be found in step S2101 of FIG. 2 , optional implementations of step S3101 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0340] Step S3202: Receive authorization information of the second node sent by the third node.

[0341] Optional implementations of step S3202 can be found in step S2104 of FIG. 2 , optional implementations of step S3102 of FIG. 3A , and other related parts of the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0342] Step S3203: In response to the authorization information indicating that the second node is authorized to provide services to the terminal, determine the services provided by the second node to the terminal.

[0343] The optional implementation of step S3203 can be found in step S2104 of FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0344] For a detailed description of steps S3201 - S3203 , please refer to the embodiment shown in FIG. 2 .

[0345] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3204. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, step S3203 may be implemented as an independent embodiment, and step S3201 and step S3202 may be implemented as independent embodiments, but are not limited thereto.

[0346] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0347] FIG3C is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a node authorization method, which is executed by a second node, and the method includes:

[0348] Step S3301: Send a first message to a first node.

[0349] The optional implementation of step S3301 can refer to step S2101 in Figure 2, the optional implementation of step S3101 in Figure 3A, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0350] Step S3302: Receive authorization information of the second node sent by the third node.

[0351] The optional implementation of step S3302 can be found in step S2104 of FIG. 2 , the optional implementation of step S3102 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 , FIG. 3A , and FIG. 3B , which will not be described in detail here.

[0352] Optionally, the second node may also receive authorization information sent by other entities. For example, the second node may receive authorization information sent by the first node.

[0353] Exemplarily, the second node being authorized to provide services to the terminal can be understood as the terminal part of other second nodes or the UE can access the network through the second node.

[0354] Step S3303: The second node switches from accessing the first node to accessing the target first node, and sends authorization information to the target first node.

[0355] The optional implementation of step S3303 can be found in step S2104 of FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0356] For a detailed description of steps S3301-S3303, please refer to the embodiment of FIG2 above.

[0357] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3303. For example, step S3301 can be implemented as an independent embodiment, step S3302 can be implemented as an independent embodiment, step S3303 can be implemented as an independent embodiment, step S3303 can be implemented as an independent embodiment, step S3301 and step S3302 can be implemented as independent embodiments, and steps S3301, S3302, and S3303 can be implemented as independent embodiments, but are not limited thereto.

[0358] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0359] Figure 3D is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in Figure 3D, the embodiment of the present disclosure relates to a node authorization method, which is executed by a second node, and the method includes:

[0360] Step S3401: Send first information to the first node.

[0361] The optional implementation of step S3401 can be found in the optional implementation of step S2101 in Figure 2, step S3101 in Figure 3A, step S3201 in Figure 3B, step S3301 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0362] In some embodiments, the first message may be an RRC message. Exemplarily, the RRC message may be an RRC setup complete message.

[0363] In some embodiments, the terminal portion of the second node sends the first message to the first node.

[0364] In some embodiments, the first node receives a first message sent by the second node.

[0365] In some embodiments, the first node may be the first node to which the second node accesses.

[0366] In some embodiments, the first node may be the first node to which a terminal portion of the second node accesses.

[0367] In some embodiments, the first message may include first information of the second node.

[0368] In some embodiments, the first information may be used to assist the first node in selecting a third node, so that the first node selects a suitable AMF to register the second node (for example, an authorization process may be included).

[0369] In some embodiments, the first information may include one or more of the following: type indication information of the second node; functions supported by the second node; services supported by the second node; and relay modes supported by the second node.

[0370] Exemplarily, the type indication information of the second node may be used to indicate the type of device of the second node. For example, the type indication information of the second node is used to indicate that the second node is a VMR device.

[0371] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0372] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high or upper layers, obtaining by self-processing, autonomous implementation, etc.

[0373] In some embodiments, the terms "access," "connect," and the like may be used interchangeably.

[0374] FIG4A is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a node authorization method, which is executed by a first node and includes:

[0375] Step S4101, obtain the first message.

[0376] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0377] In some embodiments, the first node receives the first information sent by the second node, but is not limited thereto and may also receive the first information sent by other entities.

[0378] In some embodiments, the first node obtains first information specified by a protocol.

[0379] In some embodiments, the first node obtains the first information from an upper layer(s).

[0380] Step S4102, sending the first message.

[0381] The optional implementation of step S4102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0382] In some embodiments, the first node sends the first information to the third node, but is not limited thereto, and the first information may also be sent to other entities.

[0383] Optionally, the first information is used by the third node to obtain the authorization information of the second node. For optional implementations, see the optional implementations of step S2102 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0384] Step S4103: Obtain authorization information of the second node.

[0385] The optional implementation of step S4103 can refer to the optional implementation of step S2103 above, which will not be repeated here.

[0386] In some embodiments, the first node receives authorization information of the second node sent by the third node, but is not limited thereto. The first node may also receive authorization information of the second node sent by other entities, such as authorization information sent by the second node.

[0387] In some embodiments, the first node obtains authorization information specified by the protocol.

[0388] In some embodiments, the first node obtains authorization information from upper layer(s).

[0389] In this implementation manner or example, optional modes or optional examples can be combined arbitrarily.

[0390] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S4101 and S4102. For example, step S4101 may be implemented as an independent embodiment, step S4102 may be implemented as an independent embodiment, and steps S4101 and S4102 may be implemented as independent embodiments, but are not limited thereto.

[0391] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0392] FIG4B is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a node authorization method, which is executed by a first node and includes:

[0393] Step S4201: Receive a first message sent by a second node.

[0394] The optional implementation of step S4201 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0395] Step S4202: Select a third node according to the first information of the second node included in the first message.

[0396] The optional implementation of step S4202 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0397] Step S4203: Send a second message to the third node.

[0398] The optional implementation of step S4203 can refer to the optional implementation of step S2102 above, which will not be repeated here.

[0399] Optionally, the first information is used by the third node to obtain the authorization information of the second node. For optional implementations, see the optional implementations of step S2102 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0400] Step S4204: Receive authorization information of the second node sent by the third node.

[0401] The optional implementation of step S4204 can refer to the optional implementation of step S2103 above, which will not be repeated here.

[0402] In some embodiments, the first node may receive authorization information of the second node sent by a third node, but is not limited thereto. The first node may also receive authorization information of the second node sent by another entity. For example, the first node may receive authorization information of the second node sent by the second node. In this embodiment or example, the optional methods or optional examples may be arbitrarily combined.

[0403] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S4201 to S4204. For example, step S4201 may be implemented as an independent embodiment, step S4202 may be implemented as an independent embodiment, step S4203 may be implemented as an independent embodiment, step S4204 may be implemented as an independent embodiment, step S4201 and step S4202 may be implemented as independent embodiments, and step S4201, step S4202, and step S4203 may be implemented as independent embodiments, but are not limited thereto.

[0404] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0405] Figure 4C is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in Figure 4C, the embodiment of the present disclosure relates to a node authorization method, which is executed by a first node, and the method includes:

[0406] Step S4301: Receive a first message sent by a second node.

[0407] The optional implementation of step S4301 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0408] In some embodiments, the terminal portion of the second node sends the first message to the first node.

[0409] In some embodiments, the first node receives a first message sent by the second node.

[0410] In some embodiments, the first node may be the first node to which the second node accesses.

[0411] In some embodiments, the first node may be the first node to which a terminal portion of the second node accesses.

[0412] In some embodiments, the first information may be used to assist the first node in selecting a third node, so that the first node selects a suitable AMF to register the second node (for example, an authorization process may be included).

[0413] In some embodiments, the first information may include one or more of the following: type indication information of the second node; functions supported by the second node; services supported by the second node; and relay modes supported by the second node.

[0414] Exemplarily, the type indication information of the second node may be used to indicate the type of device of the second node. For example, the type indication information of the second node is used to indicate that the second node is a VMR device.

[0415] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high or upper layers, obtaining by self-processing, autonomous implementation, etc.

[0416] In some embodiments, the terms "access," "connect," and the like may be used interchangeably.

[0417] Step S4302: Send a second message to the third node.

[0418] The optional implementation of step S4302 can refer to the optional implementation of the above-mentioned step S2102, step S4102 of Figure 4A, step S4203 of Figure 4B, and other related parts in the embodiments involved in Figures 2, 4A, and 4B, which will not be repeated here.

[0419] In some embodiments, the second message may include the first information of the second node.

[0420] In some embodiments, the first node may select a third node based on the first information and send a second message to the third node.

[0421] Optionally, the first node may select a third node supporting the node authorization function from multiple third nodes based on the first information. Exemplarily, if there are multiple third nodes supporting the node authorization function, a third node may be randomly selected.

[0422] Exemplarily, if the first information includes type indication information of the second node, the first node may consider that the second node wants to authorize information and may select a third node having a node authorization function from multiple third nodes.

[0423] In some embodiments, the second node may access the core network through a third node.

[0424] In some embodiments, the third node may receive the second message sent by the first node.

[0425] In some embodiments, the second message may be used to obtain authorization information of the second node.

[0426] In some embodiments, the authorization information may include one or more of the following:

[0427] authorizing the second node to provide services to the terminal;

[0428] The second node is not authorized to provide services to the terminal;

[0429] Authorize the second node to provide functions for the terminal;

[0430] The functions provided by the second node to the terminal are not authorized;

[0431] Authorizing the second node to provide services to the terminal;

[0432] Not authorizing the second node to provide services to the terminal;

[0433] Authorize the second node to provide a relay mode for the terminal;

[0434] The relay mode provided by the second node to the terminal is not authorized.

[0435] Exemplarily, the authorization information may be indication information that may indicate whether the second node is authorized to provide services for the terminal. Exemplarily, the authorization information may specifically include the functions for which the second node is authorized or unauthorized. Exemplarily, the authorization information may specifically include the services for which the second node is authorized or unauthorized. Exemplarily, the authorization information may specifically include the relay modes for which the second node is authorized or unauthorized.

[0436] In some embodiments, the authorization information may be authorized by function, and the functions that the second node may be authorized or unauthorized may include one or more of the following:

[0437] The second node has the access network device DU function;

[0438] The second node has the access network device CU-UP function;

[0439] The second node has the function of access network equipment;

[0440] The second node has UPF functionality;

[0441] Local data network capabilities;

[0442] N3IWF.

[0443] In some embodiments, the authorization information may be authorized by service, and the services for which the second node may be authorized or not authorized may include one or more of the following:

[0444] local services;

[0445] local exchange services;

[0446] UP services;

[0447] CP services;

[0448] Non-3GPP access services;

[0449] PDU session backhaul service.

[0450] In some embodiments, the authorization information may be authorized in a relay manner, and the relay manners in which the second node may be authorized or unauthorized may include one or more of the following:

[0451] Layer 2 relay;

[0452] Layer 3 relay;

[0453] multi-hop;

[0454] Single hop.

[0455] Optionally, the first information is used by the third node to obtain the authorization information of the second node. For optional implementations, see the optional implementations of step S2102 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0456] In this implementation manner or example, optional modes or optional examples can be combined arbitrarily.

[0457] The node authorization method involved in the embodiment of the present disclosure may include at least one of steps S4301 and S4302. For example, step S4301 may be implemented as an independent embodiment, and step S4302 may be implemented as an independent embodiment, but are not limited thereto.

[0458] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0459] Figure 4D is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in Figure 4D, the embodiment of the present disclosure relates to a node authorization method, which is executed by a third node, and the method includes:

[0460] Step S4401, obtain the second message.

[0461] The optional implementation of step S4401 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0462] In some embodiments, the third node receives the first information sent by the first node, but is not limited thereto and may also receive the first information sent by other entities.

[0463] In some embodiments, the third node obtains first information specified by the protocol.

[0464] In some embodiments, the third node obtains the first information from an upper layer(s).

[0465] Step S4402: Send authorization information of the second node.

[0466] The optional implementation of step S4402 can refer to the optional implementation of step S2103 and step S2104 in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0467] In some embodiments, the third node sends the authorization information of the second node to the first node, but is not limited thereto, and the first information may also be sent to other entities.

[0468] In some embodiments, the third node sends the authorization information of the second node to the second node, but is not limited thereto, and the first information may also be sent to other entities.

[0469] The node authorization method involved in the embodiment of the present disclosure may include at least one of steps S4401 to S4402. For example, step S4401 may be implemented as an independent embodiment, and step S4402 may be implemented as an independent embodiment, but are not limited thereto.

[0470] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0471] Figure 4E is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in Figure 4E, the embodiment of the present disclosure relates to a node authorization method, which is executed by a third node, and the method includes:

[0472] Step S4501: Receive a second message sent by the first node.

[0473] The optional implementation of step S4501 can refer to the optional implementation of step S2101 in Figure 2, step S4401 in Figure 4D, and other related parts in the embodiments involved in Figures 2 and 4D, which will not be repeated here.

[0474] Step S4502: Obtain authorization information of the second node according to the second message.

[0475] The optional implementation of step S4502 can refer to the optional implementation of the above-mentioned step S2102 and other related parts in the embodiment involved in Figure 2, and will not be repeated here.

[0476] Step S4503: Send authorization information to the second node and the first node.

[0477] The optional implementation of step S4502 can refer to the optional implementation of step S2103 and step S2104 mentioned above, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0478] In some embodiments, the third node may send the authorization information of the second node to the second node or the first node.

[0479] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S4501 to S4503. For example, step S4501 may be implemented as an independent embodiment, step S4502 may be implemented as an independent embodiment, step S4503 may be implemented as an independent embodiment, and steps S4501 and S4502 may be implemented as independent embodiments, but are not limited thereto.

[0480] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0481] Figure 4F is a flow chart of a node authorization method according to an embodiment of the present disclosure. As shown in Figure 4F, the embodiment of the present disclosure relates to a node authorization method, which is executed by a third node, and the method includes:

[0482] Step S4601: Receive a second message sent by the first node.

[0483] The optional implementation of step S4601 can refer to the optional implementation of step S2101 in Figure 2, step S4401 in Figure 4D, and other related parts in the embodiments involved in Figures 2 and 4D, which will not be repeated here.

[0484] In some embodiments, the third node may receive the first message sent by the first node.

[0485] In some embodiments, the second message may include the first information of the second node.

[0486] Step S4602: Obtain authorization information of the second node according to the second message.

[0487] The optional implementation of step S4602 can refer to the optional implementation of the above-mentioned step S2102 and other related parts in the embodiment involved in Figure 2, and will not be repeated here.

[0488] In some embodiments, the third node may obtain authorization information of the second node according to the second message, where the authorization information may be used to indicate whether the second node is authorized to provide services to the terminal.

[0489] In some embodiments, the third node can send the type indication information of the second node contained in the first information to the fourth node. The fourth node can find the authorization information of the second node based on the type indication information of the second node, and send the authorization information of the second node to the third node, so that the third node can receive the authorization information sent by the fourth node.

[0490] Exemplarily, the type indication information of the second node may be used to indicate the type of device of the second node. For example, the type indication information of the second node is used to indicate that the second node is a VMR device.

[0491] In some embodiments, the third node may obtain the authorization information of the second node from the fourth node based on one or more of the functions, services, and relay modes supported by the second node contained in the first information.

[0492] Exemplarily, the third node can send one or more of the functions, services, and relay modes supported by the second node to the fourth node, and the fourth node can send the second node's authorization information to the third node based on one or more of the functions, services, and relay modes supported by the second node, so that the third node can receive the authorization information sent by the fourth node.

[0493] In some embodiments, the authorization information may include one or more of the following:

[0494] authorizing the second node to provide services to the terminal;

[0495] The second node is not authorized to provide services to the terminal;

[0496] Authorize the second node to provide functions for the terminal;

[0497] The functions provided by the second node to the terminal are not authorized;

[0498] Authorizing the second node to provide services to the terminal;

[0499] Not authorizing the second node to provide services to the terminal;

[0500] Authorize the second node to provide a relay mode for the terminal;

[0501] The relay mode provided by the second node to the terminal is not authorized.

[0502] Exemplarily, the authorization information may be indication information that may indicate whether the second node is authorized to provide services for the terminal. Exemplarily, the authorization information may specifically include the functions for which the second node is authorized or unauthorized. Exemplarily, the authorization information may specifically include the services for which the second node is authorized or unauthorized. Exemplarily, the authorization information may specifically include the relay modes for which the second node is authorized or unauthorized.

[0503] In some embodiments, the authorization information may be authorized by function, and the functions that the second node may be authorized or unauthorized may include one or more of the following:

[0504] The second node has the access network device DU function;

[0505] The second node has the access network device CU-UP function;

[0506] The second node has the function of access network equipment;

[0507] The second node has UPF functionality;

[0508] Local data network capabilities;

[0509] N3IWF.

[0510] In some embodiments, the authorization information may be authorized by service, and the services for which the second node may be authorized or not authorized may include one or more of the following:

[0511] local services;

[0512] local exchange services;

[0513] UP services;

[0514] CP services;

[0515] Non-3GPP access services;

[0516] PDU session backhaul service.

[0517] In some embodiments, the authorization information may be authorized in a relay manner, and the relay manners in which the second node may be authorized or unauthorized may include one or more of the following:

[0518] Layer 2 relay;

[0519] Layer 3 relay;

[0520] multi-hop;

[0521] Single hop.

[0522] The node authorization method involved in the embodiment of the present disclosure may include at least one of steps S4601 to S4602. For example, step S4601 may be implemented as an independent embodiment, and step S4602 may be implemented as an independent embodiment, but is not limited thereto.

[0523] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0524] Figure 5 is an interactive diagram of a node authorization method according to an embodiment of the present disclosure. As shown in Figure 5, the embodiment of the present disclosure relates to a node authorization method for a communication system including a second node, a first node, and a third node. The method includes:

[0525] Step S5101: The second node sends a first message to the first node.

[0526] The optional implementation of step S5101 can refer to the optional implementation of the above-mentioned step S2101, which will not be repeated here.

[0527] Step S5102: The first node sends a second message to the third node.

[0528] The optional implementation of step S5102 can refer to the optional implementation of the above step S2102, which will not be repeated here.

[0529] Step S5103: Obtain authorization information of the second node according to the second message.

[0530] The optional implementation of step S5103 can refer to the optional implementation of the above-mentioned step S2102, which will not be repeated here.

[0531] The node authorization method involved in the embodiments of the present disclosure may include at least one of steps S5101 to S5103. For example, step S5101 may be implemented as an independent embodiment, step S5102 may be implemented as an independent embodiment, step S5103 may be implemented as an independent embodiment, and steps S5101 and S5102 may be implemented as independent embodiments, but are not limited thereto.

[0532] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0533] Taking the second node as VMR, the first node as VMR-donor, and the third node as AMF as an example, the following is an exemplary introduction to the above method.

[0534] 1. VMR AMF selection: The VMR provides VMR instructions and / or auxiliary information to the network so that the VMR-donor can select an appropriate AMF to register the UE (including the authorization process). The auxiliary information includes whether the VMR supports specific functions, services, and / or relay modes.

[0535] 2. The core network can authorize the VMR in the following ways:

[0536] Method 1: authorization by function, such as gNB-DU function, gNB-CU-UP function, gNB function, UPF function, local data network function, N3IWF, etc.

[0537] Method 2: Authorize by service, such as local service, local switch service, UP service, CP service, multi-access, etc.

[0538] Mode 3: authorization based on relay mode, for example, L2 relay, L3 relay, multi-hop, single hop, etc.

[0539] 3. Nodes related to the VMR can obtain the VMR authorization information from the core network in the following ways:

[0540] The AMF sends the VMR authorization information to the VMR donor through an NGAP message.

[0541] The AMF sends the VMR authorization information to the VMR through a NAS message.

[0542] During the switching or migration process, the source VMR-donor sends the VMR authorization information to the target VMR-donor through an XnAP message.

[0543] During the handover or migration process, the VMR may send VMR authorization information to the target VMR-donor via an RRC message, an XnAP message, or an F1AP message.

[0544] The following description is made in conjunction with FIG6 , which is a schematic diagram of the interaction of the VMR authorization method according to an embodiment of the present disclosure. As shown in FIG6 :

[0545] Step S601: The VMR-MT sends an RRC message to the VMR-donor. The RRC message may include a VMR indication and / or auxiliary information. The VMR indication and / or auxiliary information may be used for AMF selection.

[0546] In some embodiments, the RRC message is an RRC setup complete message.

[0547] The auxiliary information may include at least one of the following information:

[0548] Supported function indications, for example, gNB onboard, UPF onboard, CU-UP onboard, DN onboard, N3IWF onboard;

[0549] Supported service indications, for example, localservice, localswitch;

[0550] Supported relay modes, such as L2 relay, L3 relay, multi-hop, and signle-hop.

[0551] In step S602, the VMR-donor sends an NGAP message to the selected AMF. The NGAP message may include the VMR indication and / or auxiliary information received in step 601. The VMR indication and / or auxiliary information is used by the AMF to initiate the corresponding authorization process to obtain VMR authorization information.

[0552] In some embodiments, the NGAP message is an initialUEmessage message.

[0553] In step S603, the AMF sends an NGAP message to the VMR-donor, where the NGAP message includes VMR authorization information. The VMR-donor determines whether the VMR can provide corresponding services and / or transmission mechanisms for other UEs based on the VMR authorization information.

[0554] In some embodiments, the VMR authorization information is an indication message, ie, {authorized, not-authorized}.

[0555] In some other embodiments, the VMR authorization information is authorized by function, that is, the VMR authorization information includes authorizations for the following functions:

[0556] gNB-DU function{authorized, not-authorized}

[0557] gNB-CU-UP function{authorized, not-authorized}

[0558] gNB function{authorized, not-authorized}

[0559] UPF function{authorized, not-authorized}

[0560] local Data network function{authorized, not-authorized}

[0561] N3IWF{authorized, not-authorized}

[0562] In other embodiments, the VMR authorization information is authorized by service, that is, the VMR authorization information includes authorization of the following services:

[0563] local service{authorized, not-authorized}

[0564] local switch service{authorized, not-authorized}

[0565] UP service{authorized, not-authorized}

[0566] CP service{authorized, not-authorized}

[0567] In some other embodiments, the VMR authorization information is authorized in a relay manner, that is, the VMR authorization information includes the following relay manner authorizations:

[0568] L2 relay{authorized, not-authorized}

[0569] L3 relay{authorized, not-authorized}

[0570] multi-hop{authorized, not-authorized}

[0571] single hop{authorized, not-authorized}

[0572] In step S604, the AMF sends a NAS message to the VMR. The NGAP message includes VMR authorization information. Based on this VMR authorization information, the VMR-donor determines whether the VMR can provide the corresponding service and / or transport mechanism for other UEs. The content of the VMR authorization information is consistent with that described in step 603 and is not further described here.

[0573] For example, if the VMR is authorized to provide services to the terminal, the X in VMR-X can represent the gNB, that is, VMR-X is the VMR-gNB.

[0574] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0575] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0576] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0577] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. 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 a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above 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), etc.

[0578] Figure 7A is a schematic diagram of the structure of a communication device proposed in an embodiment of the present disclosure. The communication device can be used as a first node. As shown in Figure 7A, the communication device 7100 may include: at least one of a transceiver module 7101, a processing module 7102, etc. In some embodiments, the transceiver module is used to receive a first message sent by a second node, the first message including the first information of the second node; and send a second message to a third node, the second message including the first information, the second message being used to obtain authorization information of the second node, and the authorization information being used to determine whether the second node is authorized to provide services to the terminal. Optionally, the processing module is used to select the third node based on the first information. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving (for example, step S2102, but not limited thereto) performed by the first node in any of the above methods, which will not be repeated here. Optionally, the processing module is used to perform at least one of the other steps performed by the first node in any of the above methods, which will not be repeated here.

[0579] Figure 7B is a structural diagram of a communication device proposed in an embodiment of the present disclosure. The communication device can be used as a third node. As shown in Figure 7B, the communication device 7200 may include: at least one of a transceiver module 7201, a processing module 7202, etc. In some embodiments, the above-mentioned transceiver module is used to receive a second message sent by the first node, and the second message includes the first information of the second node; the above-mentioned processing module is used to obtain the authorization information of the second node according to the second message, wherein the authorization information is used to determine whether the second node is authorized to provide services to the terminal. Optionally, the above-mentioned processing module is used to execute at least one of the communication steps such as sending and / or receiving (for example, steps S2103, S2104, but not limited to this) performed by the third node in any of the above methods, which will not be repeated here.

[0580] Figure 7C is a schematic diagram of the structure of a communication device proposed in an embodiment of the present disclosure. The communication device can be used as a second node. As shown in Figure 7C, the communication device 7300 may include: at least one of a transceiver module 7301 and a processing module 7302. In some embodiments, the transceiver module is configured to send a first message to a first node, the first message including first information about the second node, the first message being used to obtain authorization information of the second node, and the authorization information being used to determine whether the second node is authorized to provide a service to the terminal. Optionally, the processing module is configured to determine, based on the authorization information, a service to be provided to the terminal and provide the service to the terminal. Optionally, the transceiver module is configured to perform at least one of the communication steps (such as sending and / or receiving) performed by the second node in any of the above methods (such as step S2101, but not limited thereto), which are not further described here. Optionally, the processing module is configured to perform at least one of the other steps (such as step S3203, but not limited thereto) performed by the second node in any of the above methods, which are not further described here.

[0581] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0582] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0583] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0584] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated 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 device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform any of the above methods.

[0585] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0586] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, steps S2103 and S2104, but not limited thereto), and the processor 8101 performs at least one of the other steps (for example, step S3023, but not limited thereto).

[0587] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0588] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0589] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0590] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8200 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0591] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0592] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 7201.

[0593] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, steps S2103, S2104, but not limited to these), and the processor 8201 performs at least one of the other steps (for example, step S3203, but not limited to this).

[0594] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0595] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0596] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0597] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0598] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A node authorization method, characterized in that: Executed by the first node, the method includes: receiving a first message sent by a second node, where the first message includes first information of the second node; A second message is sent to a third node, where the second message includes the first information, and the second message is used to obtain authorization information of the second node, where the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

2. The method according to claim 1, characterized in that Also includes: Receive authorization information of the second node sent by the third node or the second node.

3. The method according to any one of claims 1 to 2, wherein sending the second message to the third node comprises: Selecting the third node according to the first information; The second message is sent to the third node.

4. The method according to claim 3, characterized in that The selecting the third node according to the first information includes: A third node having a function of supporting node authorization is selected from a plurality of third nodes according to the first information.

5. The method according to any one of claims 1 to 4, characterized in that The first information includes one or more of the following: Type indication information of the second node; functions supported by the second node; services supported by the second node; The relay mode supported by the second node.

6. The method according to any one of claims 1 to 5, characterized in that The second message is a Next Generation Application Protocol NGAP message.

7. The method according to any one of claims 1 to 6, characterized in that The authorization information includes one or more of the following: authorizing the second node to provide services to the terminal; not authorizing the second node to provide services to the terminal; Authorizing the second node to provide a function for the terminal; Not authorizing the function provided by the second node for the terminal; authorizing the second node to provide a service for the terminal; not authorizing the service provided by the second node to the terminal; Authorizing the second node to provide a relay mode for the terminal; The relay mode provided by the second node to the terminal is not authorized.

8. A node authorization method, characterized in that: Executed by a third node, the method includes: receiving a second message sent by the first node, where the second message includes first information of the second node; According to the second message, authorization information of the second node is acquired, where the authorization information is used to determine whether the second node is authorized to provide a service to the terminal.

9. The method according to claim 8, characterized in that Also includes: The authorization information is sent to the second node and / or the first node.

10. The method according to claim 9, characterized in that The sending the authorization information to the second node and / or the first node includes: Send a non-access layer NAS message to the second node, where the NAS message includes the authorization information, and / or send a next generation application protocol NGAP message to the first node, where the NGAP message includes the authorization information.

11. The method according to any one of claims 8 to 10, characterized in that: The acquiring, according to the second message, authorization information of the second node includes at least one of the following: acquiring the authorization information from a fourth node according to the type indication information of the second node included in the first information; The authorization information is obtained from a fourth node according to one or more of the functions, services, and relay modes supported by the second node contained in the first information.

12. The method according to any one of claims 8 to 11, characterized in that The authorization information includes one or more of the following: authorizing the second node to provide services to the terminal; not authorizing the second node to provide services to the terminal; Authorizing the second node to provide a function for the terminal; Not authorizing the function provided by the second node for the terminal; authorizing the second node to provide a service for the terminal; not authorizing the service provided by the second node to the terminal; Authorizing the second node to provide a relay mode for the terminal; The relay mode provided by the second node to the terminal is not authorized.

13. A node authorization method, characterized in that: Executed by the second node, the method includes: A first message is sent to a first node, where the first message includes first information of the second node, where the first message is used to obtain authorization information of the second node, and where the authorization information is used to determine whether the second node is authorized to provide services to a terminal.

14. The method according to claim 13, characterized in that Also includes: The authorization information sent by the third node or the first node is received.

15. The method according to any one of claims 13 to 14, characterized in that Also includes: The second node switches from accessing the first node to accessing a target first node, and sends the authorization information to the target first node; or, The terminal part of the second node and the first node connected to the access network part of the second node are different. The first node connected to the terminal part of the second node sends the authorization information to the first node connected to the access network part of the second node.

16. The method according to any one of claims 13 to 15, characterized in that The authorization information includes one or more of the following: authorizing the second node to provide services to the terminal; not authorizing the second node to provide services to the terminal; Authorizing the second node to provide a function for the terminal; Not authorizing the function provided by the second node for the terminal; authorizing the second node to provide a service for the terminal; not authorizing the service provided by the second node to the terminal; Authorizing the second node to provide a relay mode for the terminal; The relay mode provided by the second node to the terminal is not authorized.

17. A node authorization method, characterized in that: The method comprises: The second node sends a first message to the first node, where the first message includes first information of the second node; The first node sends the second message to a third node, where the second message includes the first information; The third node acquires authorization information of the second node according to the second message, where the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

18. A communication device, characterized in that: Used as the first node, including: A transceiver module is used to receive a first message sent by a second node, the first message including first information of the second node; send a second message to a third node, the second message including the first information, the second message is used to obtain authorization information of the second node, and the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

19. A communication device, characterized in that: Used as a third node, including: A transceiver module, configured to receive a second message sent by the first node, where the second message includes first information of the second node; A processing module is used to obtain authorization information of the second node according to the second message, wherein the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

20. A communication device, characterized in that: Used as a second node, including: The transceiver module is used to send a first message to a first node, wherein the first message includes first information of the second node, the first message is used to obtain authorization information of the second node, and the authorization information is used to determine whether the second node is authorized to provide services to the terminal.

21. A communication device, characterized in that: Used as the first node, including: one or more processors; one or more memories storing executable instructions, When the one or more processors execute the executable instructions in the memory, the first node executes the node authorization method according to any one of claims 1-7.

22. A communication device, characterized in that: Used as a third node, including: one or more processors; one or more memories storing executable instructions, When the one or more processors execute the executable instructions in the memory, the third node executes the node authorization method described in any one of claims 8-12.

23. A communication device, characterized in that: Used as a second node, including: one or more processors; one or more memories storing executable instructions, When the one or more processors execute the executable instructions in the memory, the second node executes the node authorization method according to any one of claims 13-16.

24. A communication system, characterized in that: The invention comprises a first node, a third node and a second node, wherein the first node is configured to implement the node authorization method described in any one of claims 1 to 7, the third node is configured to implement the node authorization method described in any one of claims 8 to 12, and the second node is configured to implement the node authorization method described in any one of claims 13 to 16.

25. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is enabled to execute the node authorization method according to any one of claims 1 to 7, claims 8 to 12, or claims 13 to 16.

Images