Communication method and communication apparatus

Abstract

The present application provides a communication method, comprising: a first network device receives first indication information used for indicating that a relay node is an unlicensed node and / or used for indicating that a first communication interface cannot be established; and the first network device determines, on the basis of the first indication information, that the first communication interface cannot be established, wherein the first communication interface is a logic interface between the first network device and an access network node part of the relay node. Therefore, when the relay node is in an unlicensed state, the first network device determines that the first communication interface cannot be established with the access network node part of the relay node, which is conducive to managing a communication interface of the access network node part of the relay node in the unlicensed state. In addition, not establishing the first communication interface can reduce unnecessary signaling overhead.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application with application number 202410381924.4 filed with the State Intellectual Property Office of China on March 29, 2024, and priority to the Chinese patent application with invention name “Communication Method and Communication Device”, as well as priority to the Chinese patent application with application number 202410552203.5 filed with the State Intellectual Property Office of China on April 29, 2024, and priority to the Chinese patent application with invention name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0003] In the topic of mobile communication topology enhancement, a new architecture based on wireless access and backhaul (WAB) is being studied. The application scenario of the WAB architecture can be a vehicle mounted relay (VMR), that is, a relay node is deployed in a vehicle (or even on an airplane) to provide wireless coverage for terminals in the vehicle to overcome the problem of poor wireless signals in the vehicle. The relay node accesses the macro base station (also called the donor access network node) through wireless backhaul. Among them, the relay node in the WAB architecture can be called a WAB node.

[0004] After being authorized to join the network, a WAB node can function as a relay node for backhaul. However, this approach does not consider the impact of other relay node states (e.g., unauthorized, transitioning from authorized to unauthorized, or vice versa) on the communication interfaces (e.g., NG or Xn interfaces) of the relay node's access network node. Therefore, managing the communication interfaces of the relay node's access network node when the relay node is in states other than authorized has become a pressing issue. Summary of the Invention

[0005] The present application provides a communication method, which can manage the communication interface of the access network node part of the relay node when the relay node is in a state other than the authorized state.

[0006] In a first aspect, a communication method is provided. The method may be performed by a first network device, or by a component of the first network device (e.g., a chip, circuit, or chip system). This application does not limit this.

[0007] The communication method includes: receiving first indication information, wherein the first indication information is used to indicate that the relay node is an unauthorized node and / or is used to indicate that a first communication interface cannot be established; determining that the first communication interface cannot be established based on the first indication information; wherein the relay node includes a mobile terminal part and an access network node part, and the first communication interface is a logical interface between the first network device and the access network node part.

[0008] Based on the above technical solution, taking the first network device executing the communication method as an example for explanation, after receiving the first indication information, the first network device can determine based on the first indication information that the first communication interface cannot be established with the access network node part of the relay node, wherein the first indication information can directly indicate that the first communication interface cannot be established, or can indirectly indicate that the first communication interface cannot be established by indicating that the relay node is an unauthorized node. As a result, when the relay node is in an unauthorized state, the first network device can determine that the first communication interface cannot be established with the access network node part of the relay node, so as to facilitate the management of the communication interface of the access network node part of the relay node when the relay node is in an unauthorized state. In addition, not establishing the first communication interface can reduce unnecessary signaling overhead.

[0009] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: receiving a first request message, the first request message being used to request establishment of the first communication interface; sending a first response message, the first response message indicating that establishment of the first communication interface failed, or the first response message indicating release or suspension of the first communication interface.

[0010] Exemplarily, the first network device may be a second access network node or a second core network device, and the relay node may send a first request message to the first network device, and the first network device may indicate to the relay node through a first response message that the first communication interface has failed to be established, that the first communication interface has been released, or that the first communication interface has been suspended; alternatively, the first access network node may send a first request message to the first network device, and the first network device may indicate to the first access network node through a first response message that the first communication interface has failed to be established, that the first communication interface has been released, or that the first communication interface has been suspended.

[0011] Based on the above technical solution, when the first network device determines that the first communication interface cannot be established based on the first indication information, if the first network device receives the first request message requesting to establish the first communication interface, the first network device can feedback a first response message indicating that the establishment of the first communication interface failed, so that the establishment request of the first communication interface is rejected based on the unauthorized status of the relay node. Or,

[0012] A first communication interface has been established between the first network device and the access network node portion of the relay node. That is, after receiving the first request message, the first network device has established the first communication interface with the access network node portion of the relay node in response to the first request message. However, after learning, based on the first indication information, that the first communication interface cannot be established with the access network node portion of the relay node, the first network device instructs, through the first response message, to release or suspend the first communication interface, thereby achieving the release or suspension of the first communication interface based on the unauthorized state of the relay node.

[0013] In combination with the first aspect, in certain implementations of the first aspect, the first response message includes a first cause value, and the first cause value is used to indicate that the reason why the first communication interface failed to be established, released, or suspended is: the relay node is an unauthorized node.

[0014] Based on the above technical solution, the first network device can carry the first cause value in the first response message, so that the relay node can know the reason why the first communication interface failed to be established, released, or suspended based on the first cause value carried in the received first response message.

[0015] Optionally, the first cause value may not be carried in the first response message. For example, the first network device may send the first cause value to the relay node through other messages.

[0016] In combination with the first aspect, in certain implementations of the first aspect, if the first network device is a second access network node or a second core network device, the method further includes: determining not to forward the first request message to the first access network node or the relay node based on the first indication information, wherein the second access network node is the host access network node accessed by the relay node, the first access network node is an adjacent access network node of the relay node other than the host access network node, and the second core network device is a core network device serving the relay node.

[0017] Based on the above technical solution, when the first network device is a host access network node accessed by a relay node or a core network device serving a relay node, after receiving the first request message sent by the relay node, the first network device can determine not to forward the first request message to the adjacent access network node based on the unauthorized status of the relay node, or, after receiving the first request message sent by the first access network node, the first network device can determine not to forward the first request message to the relay node based on the unauthorized status of the relay node. That is, the host access network node or the core network device serving the relay node rejects the request to establish the first communication interface based on the unauthorized status of the relay node. There is no need to forward the first request message to the opposite end (such as the first access network node or the relay node), and the first network device rejects the request to establish the first communication interface based on the unauthorized status of the relay node, thereby reducing unnecessary signaling overhead.

[0018] In combination with the first aspect, in certain implementations of the first aspect, if the first network device is a first access network node or a second access network node, the method further includes: determining not to initiate a request to establish the first communication interface, wherein the second access network node is a host access network node accessed by the relay node, and the first access network node is an adjacent access network node of the relay node other than the host access network node.

[0019] Based on the above technical solution, when the first network device is a host access network node to which the relay node accesses, or an adjacent access network node of the relay node other than the host access network node, the first network device can determine not to actively initiate a request to establish a first communication interface based on the unauthorized status of the relay node, thereby avoiding rejection after initiating the request and reducing signaling overhead.

[0020] In combination with the first aspect, in certain implementations of the first aspect, the first indication information indicating that the relay node is an unauthorized node includes: the first indication information indicating that the relay node is updated from an authorized node to an unauthorized node, and receiving the first indication information includes: receiving the first indication information from the relay node through the first communication interface.

[0021] In combination with the first aspect, in some implementations of the first aspect, before receiving the first indication information, the method further includes: establishing the first communication interface with the relay node.

[0022] Based on the above technical solution, one situation in which the above-mentioned first indication information indicates that the relay node is an unauthorized node is: the first indication information indicates that the relay node is updated from an authorized node to an unauthorized node, that is, the relay node is updated from an authorized state to an unauthorized state, so that when the relay node is in the authorized state, the first network device can establish a first communication interface with the access network node portion of the relay node. In this case, the first network device can receive the first indication information from the relay node via the first communication interface, which can be understood as the relay node sending the first indication information to the first network device via the first communication interface, thereby reducing the complexity of transmitting the first indication information.

[0023] In combination with the first aspect, in certain implementations of the first aspect, if the first network device is a first access network node or a first core network device, receiving the first indication information includes: receiving the first indication information from a second access network node; and / or receiving the first indication information from a second core network device, wherein the second access network node is a host access network node accessed by the relay node, the first access network node is an adjacent access network node of the relay node other than the host access network node, the first core network device is a core network device serving a terminal device, the terminal device is a terminal device for which access service is provided by the relay node, and the second core network device is a core network device serving the relay node.

[0024] Based on the above technical solution, when the first network device is a host access network node to which a relay node accesses, or a core network device serving a terminal device, the first network device can receive the above-mentioned first indication information from different devices (such as a second access network node or a second core network device), thereby improving the flexibility of the solution.

[0025] In combination with the first aspect, in certain implementations of the first aspect, if the first network device is a second access network node, the receiving of the first indication information includes: receiving the first indication information from a second core network device, wherein the second access network node is the host access network node to which the relay node accesses, and the second core network device is a core network device serving the relay node.

[0026] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving second indication information, the second indication information being used to indicate that the relay node is updated to an authorized node, and / or being used to indicate that establishment of the first communication interface is allowed.

[0027] Based on the above technical solution, when a relay node is updated from an unauthorized state to an authorized state, the first network device can be notified through second indication information that a first communication interface can be established between the first network device and the access network node portion of the relay node. For example, the second indication information can directly indicate that the first communication interface can be established, or it can indirectly indicate that the first communication interface can be established by indicating that the relay node is an authorized node. This allows the first network device to determine that the first communication interface can be established between the first network device and the access network node portion of the relay node when the relay node is updated from an unauthorized state to an authorized state, thereby facilitating the management of the communication interface of the access network node portion of the relay node when the relay node is updated from an unauthorized state to an authorized state.

[0028] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: receiving a second request message, the second request message being used to request establishment of the first communication interface; and sending a second response message according to the second indication information, the second response message indicating establishment of the first communication interface.

[0029] Based on the above technical solution, when the first network device determines that the establishment of the first communication interface is allowed based on the second indication information, if the first network device receives a second request message requesting the establishment of the first communication interface, the first network device can feedback a second response message, instructing the establishment of the first communication interface, so that the establishment request of the first communication interface is accepted based on the authorization status of the relay node.

[0030] Exemplarily, the first network device may be a second access network node or a second core network device, then the relay node may send a second request message to the first network device, and the first network device may instruct the relay node to establish a first communication interface through a second response message; or, the first access network node may send a second request message to the first network device, and the first network device may instruct the first access network node to establish a first communication interface through a second response message.

[0031] In combination with the first aspect, in certain implementations of the first aspect, if the first network device is a second access network node or a second core network device, the method further includes: determining to forward the second request message to the first access network node or the relay node based on the second indication information, wherein the second access network node is the host access network node accessed by the relay node, and the first access network node is an adjacent access network node of the relay node other than the host access network node.

[0032] In combination with the first aspect, in certain implementations of the first aspect, if the first network device is a first access network node or a second access network node, the method further includes: determining, based on the second indication information, to initiate a request to establish the first communication interface, wherein the second access network node is the host access network node to which the relay node accesses, and the first access network node is an adjacent access network node of the relay node other than the host access network node.

[0033] Based on the above technical solution, when the first network device is a host access network node to which the relay node accesses, or an adjacent access network node of the relay node other than the host access network node, the first network device can determine to actively initiate a request to establish a first communication interface based on the authorization status of the relay node, without the need for a request from the relay node, thereby reducing signaling overhead.

[0034] In combination with the first aspect, in certain implementations of the first aspect, if the first network device is a first access network node or a first core network device, the receiving of the second indication information includes: receiving the second indication information from the second access network node; and / or receiving the second indication information from the second core network device, wherein the second access network node is the host access network node accessed by the relay node, the first access network node is the adjacent access network node of the relay node other than the host access network node, the first core network device is a core network device serving the terminal device, the terminal device is a terminal device for which access service is provided by the relay node, and the second core network device is a core network device serving the relay node.

[0035] Based on the above technical solution, when the first network device is a host access network node to which a relay node accesses, or a core network device serving a terminal device, the first network device can receive the above-mentioned second indication information from different devices (such as a second access network node or a second core network device), thereby improving the flexibility of the solution.

[0036] In combination with the first aspect, in certain implementations of the first aspect, if the first network device is a second access network node, the receiving of the second indication information includes: receiving the second indication information from a second core network device, wherein the second access network node is the host access network node to which the relay node accesses, and the second core network device is a core network device serving the relay node.

[0037] In a second aspect, a communication method is provided. The method can be performed by a second core network device, or by a component of the second core network device (e.g., a chip, circuit, or chip system). This application does not limit this.

[0038] The communication method includes: authenticating a relay node and determining that the relay node is an unauthorized node; sending first indication information to a first network device, the first indication information being used to indicate that the relay node is an unauthorized node, and / or being used to indicate that a first communication interface cannot be established, wherein the relay node includes a mobile terminal part and an access network node part, the first communication interface is a logical interface between the first network device and the access network node part, the second core network device is a core network device serving the relay node, the first network device includes at least one of the following: a first access network node, a second access network node, or a first core network device, the second access network node is a host access network node accessed by the relay node, the first access network node is an adjacent access network node of the relay node other than the host access network node, the first core network device is a core network device serving a terminal device, and the terminal device is a terminal device provided with access service by the relay node.

[0039] Based on the above technical solution, the communication method is executed by the second core network device as an example for explanation. When the second core network device determines that the relay node is an unauthorized node (or determines that the relay node is in an unauthorized state), it can notify the first network device through the first indication information that the first communication interface cannot be established with the relay node, wherein the first indication information can directly indicate that the first communication interface cannot be established, or it can indirectly indicate that the first communication interface cannot be established by indicating that the relay node is an unauthorized node. Thereby, when the relay node is in an unauthorized state, the first network device can be informed based on the first indication information that the first communication interface cannot be established with the access network node part of the relay node, so as to facilitate the management of the communication interface of the access network node part of the relay node when the relay node is in an unauthorized state. In addition, not establishing the first communication interface can reduce unnecessary signaling overhead.

[0040] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: establishing a first protocol data unit PDU session with the relay node, the first PDU session being used to carry data of the first communication interface, or the first PDU session being used to carry data of the first communication interface and data other than the data of the first communication interface.

[0041] Based on the above technical solution, the second core network device can establish a first PDU session with the relay node. The first PDU session can be a PDU session dedicated to carrying data of the first communication interface, or it can be a general PDU session that can be used to carry data of the first communication interface and data other than the data of the first communication interface. That is, when the relay node is in an unauthorized state, it does not affect the establishment of the first PDU session. When the first PDU session is a general PDU session, the transmission performance of data other than the data of the first communication interface is improved.

[0042] In a third aspect, a communication method is provided. The method can be performed by a second core network device, or by a component of the second core network device (e.g., a chip, circuit, or chip system). This application does not limit this.

[0043] The communication method includes: authenticating a relay node and determining that the relay node is an unauthorized node; and determining, based on the relay node being an unauthorized node, that establishment of a first protocol data unit (PDU) session fails, releasing or deactivating the established first PDU session, wherein the first PDU session is used to carry data of the first communication interface, or the first PDU session is used to carry data of the first communication interface and data other than the data of the first communication interface, wherein the relay node includes a mobile terminal part and an access network node part, the first communication interface is a logical interface between the first network device and the access network node part, the second core network device is a core network device serving the relay node, and the first network device includes at least one of the following: a first access network node, a second access network node, or a first core network device, the second access network node is a host access network node accessed by the relay node, the first access network node is an adjacent access network node of the relay node other than the host access network node, the first core network device is a core network device serving a terminal device, and the terminal device is a terminal device for which access service is provided by the relay node.

[0044] Based on the above technical solution, the communication method is executed by the second core network device as an example for explanation. When the second core network device determines that the relay node is an unauthorized node (or determines that the relay node is in an unauthorized state), it can determine not to establish the first PDU session, or for the case where the first PDU session has been established, the second core network device can release or deactivate the established first PDU session. By determining that the establishment of the first PDU session fails, releasing or deactivating the established first PDU session, it is achieved that the first communication interface is not established, so as to facilitate the management of the communication interface of the access network node part of the relay node when the relay node is in an unauthorized state. In addition, not establishing the first communication interface can reduce unnecessary signaling overhead.

[0045] In combination with the third aspect, in certain implementations of the third aspect, before determining that the establishment of the first protocol data unit PDU session fails, the method further includes: receiving a third request message, wherein the third request message is used to request establishment of the first PDU session with the relay node.

[0046] In combination with the third aspect, in certain implementations of the third aspect, third indication information is sent, where the third indication information is used to indicate that the first PDU session requested to be established by the relay node is deactivated.

[0047] Based on the above technical solution, the second core network device can notify the first PDU session to be deactivated through the third indication information, so that the relay node is informed that the first PDU session is deactivated.

[0048] In combination with the second aspect or the third aspect, in certain implementations of the second aspect or the third aspect, the method further includes: determining that the relay node is updated from an unauthorized node to an authorized node.

[0049] Based on the above technical solution, the second core network device can re-authenticate the relay node to obtain the authorization status of the relay node from unauthorized to authorized, so as to obtain the authorization status of the relay node in real time and timely adjust the communication interface strategy of the access network node part of the relay node under different authorization statuses of the relay node.

[0050] In combination with the second aspect or the third aspect, in certain implementations of the second aspect or the third aspect, if the relay node is in an RRC connected state, the method further includes: sending second indication information to the first network device, the second indication information being used to indicate that the relay node is updated to an authorized node, and / or the second indication information being used to indicate that the first network device allows establishment of the first communication interface with the relay node.

[0051] Based on the above technical solution, when the relay node is updated from an unauthorized state to an authorized state, the second core network device can notify the first network device through the second indication information that a first communication interface can be established between the relay node and the access network node portion. For example, the second indication information can directly indicate that the first communication interface is allowed to be established, or it can indirectly indicate that the first communication interface is allowed to be established by indicating that the relay node is an authorized node. This allows the first network device to determine that a first communication interface can be established between the relay node and the access network node portion when the relay node is updated from an unauthorized state to an authorized state, so as to facilitate the management of the communication interface of the access network node portion of the relay node when the relay node is updated from an unauthorized state to an authorized state.

[0052] In combination with the second aspect or the third aspect, in certain implementations of the second aspect or the third aspect, if the relay node is in an RRC connected state, the method further includes: determining to establish or activate a PDU session for carrying the first communication interface based on the relay node being updated from an unauthorized node to an authorized node.

[0053] Based on the above technical solution, when the relay node is updated from an unauthorized state to an authorized state, the second core network device can establish or activate a PDU session for carrying the first communication interface so that the data of the first communication interface can be carried on the PDU session.

[0054] In combination with the second aspect or the third aspect, in certain implementations of the second aspect or the third aspect, if the relay node is in an RRC idle state or an RRC inactive state, the method further includes: sending a paging message to the relay node, the paging message including fourth indication information, and the fourth indication information is used to indicate that the relay node is updated from an unauthorized node to an authorized node.

[0055] Based on the above technical solution, when the relay node is updated from an unauthorized state to an authorized state, if the relay node is in an RRC idle state or an RRC inactive state, the paging message sent in the paging process can carry information indicating that the relay node is updated from an unauthorized node to an authorized node, so that after the relay node receives the paging message, it can know its own authorization status and clarify the subsequent process.

[0056] In a fourth aspect, a communication method is provided. The method may be executed by a relay node or by a component of a relay node (eg, a chip, a circuit, or a chip system). This application does not limit this.

[0057] The communication method includes: receiving first information, where the first information indicates that the relay node is an unauthorized node; determining not to initiate a first protocol data unit (PDU) session establishment request based on the first information, or determining not to initiate a first communication interface establishment request based on the first information, wherein the relay node includes a mobile terminal part and an access network node part, the first communication interface is a logical interface between a first network device and the access network node part, the first PDU session is used to carry data of the first communication interface, or the first PDU session is used to carry data of the first communication interface and data other than the data of the first communication interface, the first network device includes at least one of the following: a first access network node, a second access network node, or a first core network device, the second access network node is a host access network node accessed by the relay node, the first access network node is an adjacent access network node of the relay node other than the host access network node, the first core network device is a core network device serving a terminal device, and the terminal device is a terminal device for which access service is provided by the relay node.

[0058] Based on the above technical solution, using a relay node executing the communication method as an example, upon learning that it is in an unauthorized state, the relay node determines not to initiate a request to establish a first PDU session, or determines not to initiate a request to establish a first communication interface. This avoids establishing the first communication interface, thereby facilitating management of the communication interface of the access network node portion of the relay node when the relay node is in an unauthorized state. Furthermore, not establishing the first communication interface reduces unnecessary signaling overhead.

[0059] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first information indicating that the relay node is an unauthorized node includes: the first information indicating that the relay node is updated from an authorized node to an unauthorized node.

[0060] In combination with the fourth aspect, in certain implementations of the fourth aspect, if a second PDU session has been established, the method further includes: requesting to release or deactivate the second PDU session, wherein the second PDU session is used to carry data of the first communication interface, or the second PDU session is used to carry data of the first communication interface and data other than the data of the first communication interface.

[0061] In combination with the fourth aspect, in certain implementations of the fourth aspect, before the request to release or deactivate the first PDU session, the method also includes: switching the terminal device in the RRC connected state that is accessing the relay node to a first cell according to the first information, and the first cell is a cell managed by an access network node other than the relay node.

[0062] Based on the above technical solution, the relay node switches the connected UE to a cell not managed by the relay node, thereby preventing service interruption of the UE and improving service continuity of the UE.

[0063] In a fifth aspect, a communication method is provided. The method can be executed by a relay node or by a component of the relay node (such as a chip or circuit or chip system). This application does not limit this.

[0064] The communication method includes: receiving a paging message, the paging message including fourth indication information, the fourth indication information being used to indicate that the relay node is updated from an unauthorized node to an authorized node; based on the fourth indication information, initiating a first protocol data unit (PDU) session establishment request, wherein the first PDU session is used to carry data of the first communication interface, or the first PDU session is used to carry data of the first communication interface and data other than the data of the first communication interface, and the relay node includes a mobile terminal part and an access network node part.

[0065] Based on the above technical solution, taking the relay node executing the communication method as an example for explanation, the paging message carries the authorization status of the relay node to inform the relay node, so that the relay node can directly initiate a request to establish a first PDU session for carrying data of the first communication interface, instead of first restoring the connection through the registration update process to obtain an updated authorization status from the core network device of the relay node, and then requesting to establish the first PDU session, so that the relay node in the RRC idle state or inactive state can obtain the latest authorization status, so as to establish the first PDU session for carrying data of the first communication interface.

[0066] In a sixth aspect, a communication method is provided. The method can be performed by a second core network device, or by a component of the second core network device (e.g., a chip, circuit, or chip system). This application is not limited to this.

[0067] The communication method includes: authenticating a relay node and determining that the relay node is an unauthorized node; based on the relay node being an unauthorized node, sending second information to the relay node, the second information being used to indicate at least one of the following: instructing the relay node to enter an RRC idle state, instructing the relay node to enter an inactive state, or instructing the relay node to deregister, wherein the relay node includes a mobile terminal part and an access network node part, and the second core network device is a core network device serving the relay node.

[0068] Based on the above technical solution, the second core network device instructs the relay node to enter the RRC idle state / inactive state based on the unauthorized state of the relay node, or instructs the relay node to deregister, so that the relay node cannot initiate PDU session establishment, thereby making the access network node part of the relay node in the unauthorized state unable to communicate with the first network device.

[0069] In a seventh aspect, a communication device is provided, which is used to execute the method provided in the first aspect. Specifically, the communication device may include units and / or modules, such as a processing unit and an acquisition unit, for executing the method provided in any one of the above implementations of the first aspect.

[0070] In one implementation, the transceiver unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0071] In another implementation, the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit; the processing unit may be at least one processor, processing circuit or logic circuit.

[0072] In an eighth aspect, a communication device is provided, which is used to perform the method provided in the second, third, or sixth aspects. Specifically, the communication device may include units and / or modules, such as a processing unit and an acquisition unit, for performing the method provided in the second, third, or sixth aspects.

[0073] In one implementation, the transceiver unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0074] In another implementation, the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit; the processing unit may be at least one processor, processing circuit or logic circuit.

[0075] In a ninth aspect, a communication device is provided, which is used to execute the methods provided in the fourth and fifth aspects. Specifically, the communication device may include units and / or modules, such as a processing unit and an acquisition unit, for executing the methods provided in the fourth and fifth aspects.

[0076] In one implementation, the transceiver unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0077] In another implementation, the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit; the processing unit may be at least one processor, processing circuit or logic circuit.

[0078] In a tenth aspect, the present application provides a processor for executing the method provided in any one of the implementations of the first to sixth aspects above.

[0079] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0080] In the eleventh aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, and the program code includes a method for executing any one of the implementation methods of the first to sixth aspects above.

[0081] In a twelfth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method provided in any one of the implementations of the first to sixth aspects above.

[0082] In the thirteenth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in the memory through the communication interface and executes the method provided by any one of the implementation methods of the first to sixth aspects above.

[0083] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided in any one of the implementation methods of the first to sixth aspects above.

[0084] In a fourteenth aspect, a communication system is provided, comprising the communication device described in the seventh aspect and the communication device described in the eighth aspect. Optionally, the communication system further comprises the communication device described in the ninth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] FIG1 is a schematic diagram of a communication system 100 to which an embodiment of the present application is applicable.

[0086] FIG2 is a schematic diagram of a WAB network architecture.

[0087] FIG3 is a schematic diagram of a VRM scenario.

[0088] FIG4 is a schematic diagram of an IAB network.

[0089] FIG5 is a schematic flow chart of an IAB node accessing the network.

[0090] FIG6 is a schematic flowchart of establishing a PDU session.

[0091] FIG7 is a schematic diagram of another WAB network architecture.

[0092] FIG8 is a schematic diagram of an ORAN architecture.

[0093] FIG9 is a schematic flow chart of a communication method provided in this application.

[0094] FIG10 is a schematic flowchart of another communication method provided in the present application.

[0095] FIG11 is a schematic flowchart of another communication method provided in the present application.

[0096] FIG12 is a schematic flowchart of another communication method provided in the present application.

[0097] FIG13 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application.

[0098] FIG14 is a schematic diagram of another communication device 20 provided in an embodiment of the present application.

[0099] FIG15 is a schematic diagram of a chip system 30 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0100] In order to facilitate understanding of the embodiments of the present application, the following explanations are made.

[0101] First, in this application, "used to indicate" can include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must include A.

[0102] The information indicated by the indication information is referred to as the information to be indicated. During the specific implementation process, there are many ways to indicate the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or transmission timing of these sub-information can be the same or different. The specific transmission method is not limited in this application. The transmission period and / or transmission timing of these sub-information can be predefined, for example, according to a protocol, or can be configured by the transmitting device through sending configuration information to the receiving device.

[0103] Second, "at least one" shown in the present application refers to one or more, and "more than one" refers to two or more. In addition, in the embodiments of the present application, "first", "second" and various digital numbers (for example, "#1", "#2", etc.) are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of each process below does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe solutions other than the embodiments of the present application. In addition, in the embodiments of the present application, words such as "S910", "S920" are only identifications made for the convenience of description, and do not limit the order of execution steps.

[0104] Third, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0105] Fourth, the term "storage" used in the embodiments of this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, a processor, or a communication device. The memory may be any type of storage medium, and this application is not limited thereto.

[0106] Fifth, the "protocol" involved in the embodiments of the present application may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems. This application does not limit this.

[0107] Sixth, in the embodiments of the present application, "under the circumstances", "when", and "if" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

[0108] Seventh, in the embodiments of this application, various terms and English abbreviations, such as radio resource control (RRC), are provided for ease of description and should not constitute any limitation on this application. This application does not exclude the possibility of defining other terms in existing or future protocols that can achieve the same or similar functions.

[0109] Eighth, the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0110] Ninth, in the embodiments of the present application, there is no limitation on the names of messages and devices, as long as they can implement the corresponding functions.

[0111] The technical solution in this application will be described below with reference to the accompanying drawings.

[0112] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solutions of the embodiments of the present application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication system or other communication systems.

[0113] To facilitate understanding of the embodiments of the present application, the communication system to which the embodiments of the present application apply will first be described in detail using the communication system shown in FIG1 as an example. FIG1 is a schematic diagram of a communication system 100 to which the embodiments of the present application apply. As shown in FIG1 , the communication system 100 may include at least one access network device, such as the access network device 110 shown in FIG1 ; the communication system 100 may also include at least one terminal device, such as the terminal device 120 shown in FIG1 ; and the communication system 100 may also include at least one core network (CN) device, such as the core network device 130 shown in FIG1 . The access network device 110 and the terminal device 120 may communicate via a wireless link, and the access network device 110 and the core network device 130 may communicate via a wireless link. Each communication device, such as the access network device 110, the terminal device 120, and the core network device 130, may be configured with multiple antennas. For each communication device in the communication system 100, the configured multiple antennas may include at least one transmit antenna for sending signals and at least one receive antenna for receiving signals. Therefore, communication devices in the communication system 100, such as the access network device 110 and the terminal device 120, can communicate using multi-antenna technology.

[0114] As an example and not a limitation, the access network device and the terminal device in the scenario shown in Figure 1 can communicate in a variety of ways, such as communication between the access network device and the terminal device through a point-to-point transmission method, communication between the access network device and the terminal device through a multi-hop (or relay) transmission method, communication between multiple access network devices and terminal devices through dual connectivity (DC) or multi-connection transmission methods, etc. In the embodiments of the present application, no limitation is imposed on the communication method between the access network device and the terminal device. For example, the transmission between the access network device and the terminal device can be uplink, downlink, access link, backhaul link or sidelink, etc.

[0115] The terminal equipment in the embodiments of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, a user equipment (UE), a terminal, a wireless communication device, a user agent, or a user device. The terminal equipment may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future-evolved public land mobile network (PLMN), etc., and the embodiments of the present application are not limited thereto.

[0116] As an example and not a limitation, in the embodiments of the present application, wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0117] Furthermore, in the embodiments of the present application, the terminal device may also be a terminal device in an IoT system, whose main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects humans and machines and things. In the embodiments of the present application, IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.

[0118] The access network device (or referred to as an access network node (NG-RAN-node)) in the embodiment of the present application can be any device with wireless transceiver capabilities used to communicate with a terminal device. The device includes but is not limited to: an evolved Node B (eNB), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home evolved NodeB (HeNB, or home Node B, HNB), a baseband unit (BBU), an access point (AP) in a wireless fidelity (WIFI) system, a wireless relay device, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It can also be a gNB in ​​a 5G or NR system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DPU). unit, DU), etc., and can also be a device that communicates with a terminal device in a future communication system, such as a gNB in ​​a future communication system.

[0119] In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some gNB functions, while the DU implements some gNB functions. For example, the CU is responsible for processing non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. Because RRC layer information ultimately becomes PHY layer information, or is converted from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by both the DU and the AAU. It is understood that an access network device can be a device that includes one or more of a CU node, a DU node, or an AAU node. In addition, the CU may be classified as a network device in an access network (radio access network, RAN), or may be classified as a network device in a core network (core network, CN), which is not limited in this application.

[0120] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, the radio access network may also be an open radio access network (open RAN, ORAN) architecture. In the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0121] The core network equipment part in the embodiment of the present application may include but is not limited to the following NFs: user plane function (UPF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management function (UDM), unified data repository function (UDR), network data analytics function (NWDAF), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), network slice selection function (NSSF), etc. Among them, AMF, SMF, UPF, NEF, AUSF, NRF, PCF, NSSF, and UDM can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.

[0122] It should be understood that the above naming is defined only to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 5G networks and other future networks. For example, in future communication networks, some or all of the above network elements may continue to use 5G terminology, or may adopt other names.

[0123] As an example and not a limitation, in an embodiment of the present application, the CN device is used to provide user connection, user management, and service carrying, and provides an interface to the external network as a bearer network. This application mainly involves the AMF network element (or AMF, AMF device, AMF unit, etc.) in the core network. AMF is a control plane network function provided by the operator network, which is responsible for access control and mobility management of terminal devices accessing the operator network, such as mobile status management, allocation of user temporary identity, authentication and authorization of users, and other functions.

[0124] In an embodiment of the present application, a terminal device, an access network device or a core network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU) and memory (also known as main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system or a Windows operating system. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application. As long as it is possible to communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application can be a terminal device or a network device, or a functional module in the terminal device or network device that can call and execute a program.

[0125] In addition, various aspects or features of the present application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used in this application covers computer programs that can be accessed from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0126] It should be understood that Figure 1 uses the communication between an access network device and a terminal device, and between an access network device and a core network device, as examples to simply illustrate a communication scenario in which the present application can be applied, and does not limit other scenarios in which the present application can be applied. It should also be understood that Figure 1 is merely a simplified schematic diagram for ease of understanding, and the communication system may also include other network devices or other terminal devices, which are not shown in Figure 1.

[0127] The access network device 110, the terminal device 120, and the core network device 130 in Figure 1 can be applied to the integrated access and backhaul (IAB) IAB network architecture. The relay node is an IAB node, and in some cases the IAB node can also have mobility. The IAB network architecture is based on the CU-DU separation architecture. The IAB node (IAB-node) includes a mobile terminal (MT) part and a DU part. When the IAB-node faces its parent node, the IAB-node acts as a terminal device, that is, as an MT; when the IAB-node faces its child node (the child node may be another IAB-node, or an ordinary UE), the IAB-node is regarded as a network device, that is, as a DU.

[0128] For ease of understanding, the IAB network is briefly described with reference to Figure 2. As shown in Figure 2, the IAB donor node (IAB-donor) is an access network element with full access network node (gNB) functionality, including a CU and DU (as shown in Figure 2, for example, IAB-donor-CU and IAB-donor-DU). The IAB-donor is connected to the core network serving the UE (e.g., a 5G core network).

[0129] Taking uplink transmission as an example, after a UE accesses the access network equipment portion of an IAB node (such as the IAB-node-DU of IAB-node2 in Figure 2), the MT portion of the same IAB node (such as the IAB-node-MT of IAB-node2 in Figure 2) backhauls the UE's data to the access network equipment portion of the previous-hop IAB node (such as the IAB-node-DU of IAB-node1 in Figure 2). The MT portion of the previous-hop node (such as the IAB-node-MT of IAB-node1 in Figure 2) then backhauls the data to the IAB-node-DU of the previous-hop. This continues in this order. Each hop's wireless backhaul is completed over the NR air interface (Uu) until it reaches the IAB-donor-DU. After that, the data is sent via a wired connection to the IAB-donor-CU and then to the core network serving the UE. Downlink transmission is similar and will not be further described here.

[0130] It should be understood that the IAB architecture is a layer 2 relay architecture, because the IAB-node only has the DU function of the access network node and no CU function. In the 3rd generation partnership project (3GPP) Rel-19, a network based on layer 3 relay will be studied, and the relay node has complete access network node functions. At the same time, similar to the IAB architecture, the relay node also needs to have MT functions to provide backhaul. In the topology enhancement topic of Rel-19, a new architecture of WAB is being studied, and Rel-19 will name the access network equipment that supports WAB as WAB node. It should be noted that this application does not impose any restrictions on the name of the device, as long as it can realize the corresponding function. For example, the access network equipment that supports WAB technology can also be called WAB equipment, mobile WAB node, or first node, etc. For the convenience of description, the access network equipment that supports WAB will be referred to as WAB node below.

[0131] For ease of understanding, the following briefly introduces the WAB network architecture with reference to Figure 3.

[0132] As shown in Figure 3, the WAB node consists of two parts: the gNB and the mobile equipment (MT). The gNB portion of the WAB node can be referred to as the WAB-gNB, and the MT portion can be referred to as the WAB-MT. This means that the WAB node includes both gNB functionality (optionally, it can also include CU and DU functionality, as the gNB can have a CU / DU split architecture) and MT functionality.

[0133] For example, the UE accesses the WAB-gNB through the Uu port, and then the WAB-MT wraps the UE's control plane or user plane data in the WAB-MT's PDU session, and sends it to the WAB-MT_UPF through the Uu port of the WAB-MT through the N3 tunnel between the host access network node (donor) and the UPF serving the WAB-MT (i.e., WAB-MT_UPF in Figure 3). Then, the WAB-MT_UPF removes the header information of the WAB-MT-related data packet, revealing the UE-related header information, and sends it to the core network serving the UE (e.g., the AMF serving the UE, the SMF serving the UE, or the UPF serving the UE) according to IP routing. Logically, a NAS connection is established between the UE and the AMF serving the UE (i.e., the core network of the UE in Figure 3) for transmitting control plane data; a PDU session is established between the UE and the UPF serving the UE (i.e., the core network of the UE in Figure 3) for transmitting user plane data. The two types of data of the UE mentioned above are both wrapped in the PDU session of WAB-MT and transmitted to the core network of the UE.

[0134] It should be understood that the core network serving the UE in the embodiment of the present application includes core network elements such as the AMF serving the UE and the UPF serving the UE. Hereinafter, the core network serving the UE may also be referred to as the core network of the UE, for example, the AMF serving the UE may also be referred to as the AMF of the UE, which can be abbreviated as UE_AMF; for example, the UPF serving the UE may also be referred to as the UPF of the UE, which can be abbreviated as UE_UPF.

[0135] In addition, in the embodiment of the present application, the core network serving WAB-MT includes core network elements such as the AMF serving WAB-MT and the UPF serving WAB-MT. Hereinafter, the core network serving WAB-MT may also be referred to as the core network of WAB-MT, for example, the AMF serving WAB-MT may also be referred to as the AMF of WAB-MT, which can be abbreviated as WAB-MT_AMF; for example, the UPF serving WAB-MT may also be referred to as the UPF of WAB-MT, which can be abbreviated as WAB-MT_UPF.

[0136] As an example and not a limitation, the main scenario of the WAB network architecture is the VMR scenario, that is, relay nodes are deployed in vehicles (or even aircraft) to provide wireless coverage for UEs inside the vehicle to overcome the problem of poor wireless signals inside the vehicle. The relay nodes access the macro base station (host access network node, also known as donor) through wireless backhaul, as shown in Figure 4. Figure 4 is a schematic diagram of a VRM.

[0137] From the above description of the IAB and WAB architectures, we can see that in the IAB architecture, the IAB-node-MT helps backhaul UE data. However, the UE data does not need to be enclosed in the IAB-node-MT's PDU session. Instead, it is directly carried on the IAB-node-MT's Layer 2 logical channel and reaches the IAB-donor through hop-by-hop logical channel mapping. The IAB-donor sees the UE data. In the WAB architecture, UE data is directly enclosed in the WAB-MT's PDU session. During the WAB-MT backhaul process, this data is considered the WAB-MT's own user plane data. After this data reaches the donor via the WAB-MT's data radio bearer (DRB), the donor only sees the WAB-MT data, not the UE data. Only after it is sent to the UPF serving the WAB-MT will the WAB-MT-related packet header information be stripped, revealing the UE-related packet header information, and then forwarded to the UE's core network.

[0138] The above example illustrates how the UE communicates with the UE's core network under the WAB network architecture. The interface-level data transmission between the WAB-gNB and the UE's core network (such as AMF) is similar. It also needs to be transmitted through the WAB-MT PDU session to the UPF serving the WAB-MT, and then routed to the AMF serving the UE.

[0139] To facilitate understanding of the embodiments of the present application, some basic concepts involved in the present application are briefly explained.

[0140] 1. IAB node integration process: Taking the network integration process of IAB-node2 as an example, IAB-node1 is the parent node of IAB-node2 and is already in the network.

[0141] As shown in Figure 5, the network access process for IAB-node2 includes the following stages:

[0142] 1) Phase 1 (Phase 1): The IAB-donor will carry the IAB support (iab-support) information element in the system information block 1 (SIB1) broadcast of the cell that supports IAB-MT access. The IAB-MT will only choose to access the cell that broadcasts the iab-support information element in SIB1. The IAB-MT accesses the cell in a manner similar to that of an ordinary UE, establishes an RRC connection with the IAB-donor, and indicates that it is an IAB node when establishing the RRC connection. For example, the IAB-MT carries the IAB-Node Indication (iab-Node Indication) information element in the RRC setup complete message (i.e., message 5 (msg5)) to indicate that it is an IAB node.

[0143] When the IAB-donor-CU sends the initial UE message (initial UE messagege) to the core network (e.g., AMF network element), it also carries the iab-NodeIndication information element. The AMF authenticates the IAB-MT and carries the IAB Authorized information element in the message (initial context setup request) instructing the IAB-donor-CU to establish the UE initial context for the IAB-MT. If the authentication is successful, the value of the IAB Authorized information element is authorized, otherwise the IAB Authorized is not authorized. The process shown in Figure 5 is the network access process of the IAB node. It is assumed that the value of IAB Authorized is authorized and the subsequent steps are performed.

[0144] 2) Phase 2-1: The IAB-donor-CU configures the backhaul link RLC channel (BH RLC Channel) for the IAB-node through RRC messages and performs routing configuration.

[0145] Specifically, only a default BH RLC Channel and a default route are configured at this time for use when the F1 interface is initially established (i.e., used in Phase 3 described below). After the F1 interface is established, more BH RLC Channels and routing paths can be configured to the IAB-node through the F1-C message for use by subsequent F1-C messages and F1-U user plane data.

[0146] 3) Phase 2-2: Perform routing updates on the node (IAB-node 1) between the IAB-node and the IAB-donor, informing these nodes how to select the next-hop link and next-hop RLC channel when receiving a data packet from or sending a data packet to IAB-node 2.

[0147] 4) Phase 3: The IAB-node-DU uses the default configuration obtained in Phase 2-1 and / or Phase 2-2 to send an F1 setup request message to the IAB-donor-CU. This message carries the cell configuration information of the IAB-node-DU and requests the establishment of the F1 interface. The IAB-donor-CU responds with an F1 setup response message to the IAB-node-DU to activate the cell and complete the F1 interface establishment. At this point, the IAB-node-DU is activated and can provide services to the UE and the next-hop IAB-node-MT.

[0148] In Release 18, the mobile IAB-node network access process is similar to the IAB-node access process described in Figure 5 above. The mobile IAB-node only replaces some indication information with that of the IAB. The mobile IAB-node and IAB-node are two different types of nodes. Both the IAB-donor and the AMF need to be upgraded to support providing services for the mobile IAB-node. Therefore, a new mobile IAB-Support information element is introduced in SIB1. For example, in msg5, the mobile IAB-Node Indication information element is introduced. Upon receiving this information, the IAB-donor will seek an AMF that supports mobile IAB functionality for authentication and carry the mobile IAB-Node Indication information element in the UE Initial Message. If authentication is successful, the AMF will indicate that the value of the mobile IAB Authorized information element in the Initial Context message is "Authorized."

[0149] 2. PDU Session Establishment: In mobile communication systems, a session refers to the information exchange between a UE and a data network using an IP address. In 5G networks, session management is performed at the granularity of protocol data unit (PDU) sessions. PDU sessions are used to provide PDU connectivity services between the UE and the data network (DN), supporting the exchange of PDUs between the UE and the data network. Therefore, the PDU session establishment process is only involved when the UE initiates data services. In NR, a UE supports the establishment of multiple PDU sessions.

[0150] For ease of understanding, the process of establishing a PDU session is briefly described with reference to FIG6 .

[0151] As shown in Figure 6, PDU session establishment includes the following steps:

[0152] S610: The UE sends a PDU session establishment request message to the AMF through the connected gNB.

[0153] For example, the UE sends an uplink non-access stratum (NAS) message containing a PDU session establishment request message to the AMF through the gNB it accesses. Furthermore, upon receiving the PDU session establishment request message, the AMF sends the PDU session establishment request message to the SMF, which then determines whether the PDU session requested by the UE is established.

[0154] S620: The AMF sends a PDU session resource setup request message to the gNB to which the UE is connected.

[0155] For example, after receiving the indication from the SMF to establish a PDU session, the AMF sends an N2 interface protocol (NG application protocol, NGAP) message to the gNB accessed by the UE. The NGAP message includes a list of PDU sessions to be established, a list of quality of service (QoS) flows for each PDU session, quality attributes of each QoS flow, and a PDU session establishment accept message returned to the UE. The PDU session establishment accept message is carried in the NAS PDU and the gNB will not parse it.

[0156] S630: The gNB to which the UE accesses sends an RRC reconfiguration message to the UE.

[0157] For example, the gNB maps the QoS flow to the DRB based on the quality attributes of the QoS flow indicated in the PDU Session Resource Establishment Request message and sends an RRC Reconfiguration message to the UE to initiate the DRB establishment request and notify the core network that the PDU session establishment has been accepted (i.e., a PDU Session Establishment Accept message). Furthermore, after completing the DRB establishment, the UE responds with an RRC Reconfiguration Complete message to the gNB.

[0158] S640: The gNB sends a PDU session resource setup response message to the AMF to indicate that the PDU session is successfully established.

[0159] Through the above steps S610 to S640, the end-to-end (e.g., between the UE and the UPF of the core network) PDU session is transmitted through DRB on the air interface, and between the gNB and the UPF of the core network is transmitted through the N3 tunnel (i.e., general packet radio service (GPRS) user plane tunneling protocol (GPRS tunneling protocol-user plane, GTP-U) tunnel).

[0160] It should be understood that the process shown in Figure 6 is for UE to request PDU session establishment, which is also applicable to WAB-MT requesting PDU session establishment. For the process of WAB-MT requesting PDU session establishment, please refer to Figure 6. For example, if WAB-MT requests PDU session establishment, WAB-MT can be equivalent to the UE in the PDU session establishment process shown in Figure 6 above, and the WAB-donor accessed by WAB-MT can be equivalent to the gNB in ​​the PDU session establishment process shown in Figure 6 above. The core network serving WAB-MT can be equivalent to the AMF and UPF in the PDU session establishment process shown in Figure 6 above, which will not be repeated here.

[0161] 3. WAB network architecture backhauls the NG and / or Xn interfaces of the WAB-gNB: Specifically, the backhaul process of the NG and / or Xn interfaces of the WAB-gNB includes the following two implementation methods:

[0162] Implementation #1: The anchor points of both the N2 interface and the Xn interface are at the UPF serving the WAB-MT. The WAB-MT can request to establish a dedicated or universal PDU session as the backhaul link for the logical Xn interface (i.e., carrying Xn-C and / or Xn-U data) and / or N2 (also known as NG) interface (i.e., carrying NG-C and / or NG-U data) of the WAB-gNB.

[0163] It can be understood that in the case shown in implementation #1, the anchor point for data interaction between the WAB-gNB and the AMF serving the UE and / or the neighboring station is located at the UPF serving the WAB-MT. Taking the WAB-gNB sending Xn data to the neighboring station as an example, the Xn data sent by the WAB-gNB to the neighboring station will be transmitted to the UPF serving the WAB-MT via the PDU session used by the WAB-MT to carry the Xn interface, and then routed to the corresponding neighboring station by the UPF serving the WAB-MT via IP. The WAB-gNB sending N2 data is similar, except that the N2 data is routed to the AMF serving the UE via IP via the UPF serving the WAB-MT.

[0164] Implementation #2: The anchor point of the N2 interface is at the UPF serving the WAB-MT, and the anchor point of the Xn interface is at the donor access network node (WAB-donor). The Xn data between the WAB-gNB and the neighboring station can also be forwarded by the donor access network node. The WAB-MT can request to establish a PDU session to carry the logical Xn interface of the WAB-gNB (i.e., carry Xn-C and / or Xn-U data). However, after the donor access network node receives the Xn data from the WAB-gNB through the WAB-MT's DRB (associated with the PDU session carrying the Xn interface), it will forward it directly to the corresponding neighboring station instead of continuing to transmit it to the N3 tunnel associated with the DRB to be sent to the UPF serving the WAB-MT.

[0165] The above, in conjunction with Figure 1, briefly describes the scenarios in which the communication method provided in the embodiments of the present application can be applied, as well as the basic concepts that may be involved in the embodiments of the present application. The basic concepts also describe the IAB node network access process. As can be seen from the IAB node network access process shown above, the IAB node can only establish an F1 interface with the IAB-donor and provide access services to the UE after being authorized by the core network. Therefore, if the WAB node network access process refers to this IAB node network access process, the WAB node also needs to be authorized before the WAB-gNB portion can be activated. The current WAB-gNB's NG and / or Xn interface backhaul process does not consider the impact of the WAB node's authorization status on the NG and / or Xn interfaces established by the WAB-gNB, resulting in the inability to manage the WAB-gNB's NG and / or Xn interfaces when the WAB node is unauthorized or the WAB node's authorization status changes.

[0166] In order to solve the problems existing in the above-mentioned WAB node network access process, the present application provides a communication method, so as to realize the management of the NG and / or Xn interface of the WAB-gNB when the WAB node is in an initial unauthorized state or the authorized state changes.

[0167] It should be understood that the communication method provided in the embodiments of the present application can be applied to a relay system, for example, the WAB network system shown in FIG3 .

[0168] As an example and not a limitation, the WAB network system used in this application is shown in Figure 7, including: WAB-gNB, a donor access network node (donor-gNB), other access network nodes (other-gNB) and a core network (CN). Among them, the WAB-gNB includes a WAB-MT part and a WAB-gNB part. The WAB-gNB provides access services for the UE and the WAB-MT provides backhaul. The donor-gNB is a host gNB that supports WAB access and can transmit the service data of the WAB-MT. The other-gNB is a neighboring station (non-donor-gNB) of the WAB-gNB. The CN can be understood as the 5G core network (5GC), which is used to authenticate terminal devices, manage mobility, and manage PDU sessions. It includes functional entities or network elements such as the access and mobility management function AMF, the session management function SMF, and the user plane function UPF. In this application, it mainly involves the core network serving the WAB-MT and the core network serving the UE.

[0169] As shown in Figure 7, for a WAB-gNB, neighboring stations include donor-gNBs and other-gNBs. Data on the N2 interface between the WAB-gNB and the AMF serving the UE (e.g., WAB-gNB and UE_AMF in Figure 7), or data on the Xn interface between the WAB-gNB and neighboring stations (e.g., Xn interface between the WAB-gNB and the donor gNB, or Xn interface between the WAB-gNB and other gNBs in Figure 7), must be backhauled via the WAB-MT PDU session (e.g., WAB-MT PDU session between the WAB-MT and WAB-MT_UPF in Figure 7). For implementation #1 described in the basic concepts above, IP routing is performed via the UPF serving the WAB-MT to the AMF serving the UE or neighboring station. For implementation #2 described in the basic concepts above, the N2 interface implementation is the same as implementation #1, and data on the Xn interface can be directly forwarded to the other-gNB after reaching the donor-gNB via the WAB-MT Uu interface.

[0170] In addition, it should be noted that in the embodiments of the present application, the radio access network may be an ORAN architecture. As shown in FIG8 , the WAB-gNB, donor-gNB, and other-gNB described above may be ORAN architectures. The ORAN architecture shown in FIG8 includes a RAN intelligent controller (RIC), a gNB-CU, and a gNB-DU. The RIC is responsible for collecting network information and performing necessary optimization tasks. It communicates with the gNB-CU and gNB-DU via the E2 interface. That is, the O-RIC can directly control the gNB-DU or control the IAB-DU through the gNB-CU. The gNB-CU supports O-RAN functions, including the gNB-CU, other-gNB-CU, and WAB-CU. The gNB-DU supports O-RAN functions, including the gNB-DU, donor-gNB-DU, and WAB-DU. Interactions between the WAB-gNB, donor-gNB, and other-gNB can also be achieved through the RIC.

[0171] It should also be understood that the embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application. As long as it is possible to communicate according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application can be a device or a network element, or a functional module in the device or network element that can call and execute the program.

[0172] FIG9 is a schematic flow chart of a communication method provided by the present application, which includes the following steps:

[0173] S910: A first network device receives first indication information from a second network device. Correspondingly, the second network device sends the first indication information to the first network device.

[0174] Specifically, the first indication information is used to indicate that the relay node is an unauthorized node, and / or the first indication information is used to indicate that the first communication interface cannot be established.

[0175] Exemplarily, in an embodiment of the present application, a relay node is a node comprising a mobile terminal portion and an access network node portion, wherein the mobile terminal portion is used to implement the function of the relay node as a terminal device, and the access network node portion is used to implement the function of the relay node as an access network device. The relay node in this embodiment may also be referred to as a WAB node, a mobile WAB node, or a first node, etc. In this embodiment, there is no limitation on the name of the device or node, as long as it can implement the corresponding function. For example, when the communication method is applied to the WAB architecture shown in Figure 7, the relay node may be the WAB node shown in Figure 7.

[0176] In addition, in the embodiment of the present application, the first network device includes at least one of the following:

[0177] The first access network node, the second access network node, or the first core network device, the second access network node is the host access network node accessed by the relay node, the first access network node is the adjacent access network node of the relay node other than the host access network node, the first core network device is the core network device serving the terminal device, and the terminal device is a terminal device provided with access service by the relay node.

[0178] First access network node: In the embodiments of this application, the first access network node refers to a donor access network node, which is used to provide access network device-side functions. The first access network node can be referred to as a donor-gNB, etc. In this embodiment, there is no limitation on the name of the device or node; it only needs to be able to perform the corresponding functions. For example, when the communication method is applied to the WAB architecture shown in Figure 7, the first access network node can be the donor gNB shown in Figure 7.

[0179] Second access network node: In the embodiments of this application, the second access network node refers to an access network node other than the donor access network node in a WAB neighboring station. The second access network node can be referred to as, for example, other-gNB. In this embodiment, there is no limitation on the name of the device or node; it only needs to be able to perform the corresponding function. For example, when the communication method is applied to the WAB architecture shown in Figure 7, the second access network node can be the other gNB shown in Figure 7.

[0180] First core network device: The first core network device in the embodiment of the present application is a core network element serving the terminal device, which is used to provide services such as mobility management and / or session management for the terminal device. For example, the first core network device includes core network elements such as AMF, SMF or UPF serving the second terminal. The first core network device can be called a core network element serving the terminal device (CN of UE). In this embodiment, there is no limitation on the name of the first core network device, as long as it can implement the corresponding function. For example, when the communication method is applied to the WAB architecture shown in Figure 7, the first core network device can be the UE_AMF and UE_UPF shown in Figure 7.

[0181] In addition, in the embodiment of the present application, the core network element serving the relay node is referred to as a second core network device. The second core network device is used to provide services such as mobility management and / or session management for the relay node. For example, the second core network device includes core network elements such as AMF, SMF, or UPF serving the first terminal. The second core network device can be called a core network element serving the first terminal (CN of WAB-MT). In this embodiment, there is no limitation on the name of the first network element, as long as it can implement the corresponding function. For example, when the communication method is applied to the WAB architecture shown in Figure 7, the second core network device can be the WAB-MT_AMF and WAB-MT_UPF shown in Figure 7.

[0182] Exemplarily, the second core network device may authenticate the relay node, determine the authorization status of the relay node, and notify the first access network node and / or relay node through indication information. Specifically, the manner in which the second core network device authenticates the relay node and notifies the first access network node and / or relay node through indication information will be described in detail below in conjunction with FIG. 10 , and will not be described in detail here.

[0183] In addition, the terminal device in the embodiment of the present application refers to a terminal device that is not a relay node. For example, when the communication method provided below is applied to the WAB architecture shown in FIG7 , the terminal device may be the UE shown in FIG7 .

[0184] In this embodiment, the first core network device serving the terminal device and the second core network device serving the relay node may be the same or different core network devices. For example, a core network device may serve both the terminal device and the relay node.

[0185] Specifically, in order to transmit data, the access network node part of the relay node can establish a communication interface #1 (such as N2 interface, NG interface, etc.) with the first core network device; the access network node part of the relay node can also establish a communication interface #2 (such as Xn interface) with the first access network node; the access network node part of the relay node can also establish a communication interface #3 (such as Xn interface) with the second access network node.

[0186] In this embodiment, the aforementioned communication interface #1, communication interface #2, and communication interface #3 may be collectively referred to as a first communication interface. The first communication interface is a logical interface between a first network device (e.g., a first access network node, a second access network node, or a first core network device) and the access network node portion of a relay node. In this embodiment, the logical interface between the first network device and the access network node portion of the relay node may also be referred to as a logical connection between the first network device and the access network node portion of the relay node. That is, the communication interface may be referred to as a communication connection, and the communication connection may be understood as a communication connection based on the communication interface.

[0187] For example, when the communication method is applied to the WAB architecture shown in Figure 7, the communication interface #1 between the access network node part of the relay node and the first core network device can be the NG interface between the WAB-gNB and the UE_AMF shown in Figure 7; the communication interface #2 between the access network node part of the relay node and the first access network node can be the Xn interface between the WAB-gNB and the host gNB shown in Figure 7; the communication interface #3 between the access network node part of the relay node and the second access network node can be the Xn interface between the WAB-gNB and other gNBs shown in Figure 7.

[0188] As a possible implementation, if the first network device is a first access network node or a first core network device, the second network device may be a second access network node and / or a second core network device. The first network device receiving the first indication information includes: receiving the first indication information from the second access network node; and / or receiving the first indication information from the second core network device.

[0189] In this implementation, the first network device may receive the first indication information in the following manner:

[0190] Exemplarily, the second access network node and / or the second core network device may obtain the first core network device from operation administration and maintenance (OAM); or,

[0191] The second access network node and / or the second core network device may determine other core network devices with which it can communicate nearby as possible first core network devices. For the second access network node, the other core network devices with which it can communicate nearby may be core network devices with which it has an NG interface or with which it is IP-reachable; for the second core network device, the other core network devices with which it can communicate nearby may be core network devices with which it is IP-reachable between the second core network device and the second core network device.

[0192] After the second access network node and / or the second core network device learns about the first core network device, the second access network node and / or the second core network device sends the relay node information and the first indication information to the first core network device. The relay node information includes but is not limited to at least one of the following information:

[0193] Information such as the gNB ID of the relay node, the IP address of the relay node used to establish the NG interface, or the IP address of the security gateway of the relay node used to establish the NG interface.

[0194] Similarly, the second access network node and / or the second core network device may obtain the first access network node from the OAM, or,

[0195] The second access network node and / or the second core network device may determine other nearby access network nodes with which it can communicate as possible first access network nodes. For the second access network node, the other nearby access network nodes with which it can communicate may be access network nodes with which an Xn interface exists or with which an IP address is reachable; for the second core network device, the other nearby access network nodes with which it can communicate may be access network nodes with which an NG interface exists or with which an IP address is reachable.

[0196] After the second access network node and / or the second core network device learns of the first access network node, the second access network node and / or the second core network device sends the relay node information and the first indication information to the first access network node.

[0197] As another possible implementation, if the first network device is a second access network node, the second network device may be a second core network device. That is, the first network device receiving the first indication information includes: receiving the first indication information from the second core network device.

[0198] As an example and not a limitation, the above-mentioned first indication information indicating that the relay node is an unauthorized node includes: the authorization state of the relay node at the time of initial access is the unauthorized state, and the second network device can indicate to the first network device through the first indication information that the relay node is an unauthorized node; or, the first indication information indicating that the relay node is an unauthorized node includes: the relay node is updated from the authorized state to the unauthorized state, and after the relay node is updated to the unauthorized state, the second network device can indicate to the first network device through the first indication information that the relay node is updated from the authorized node to the unauthorized node.

[0199] It should be understood that when the first indication information indicates that the relay node has been updated from an authorized node to an unauthorized node, the access network node portion of the relay node may have already established a first communication interface with the first network device while the relay node is in the authorized state. In this case, the first indication information may be sent to the first network device via the established first communication interface. For example, upon learning that the relay node has been updated from an authorized node to an unauthorized node, the relay node may notify the second access network node of the update via the first communication interface using the first indication information.

[0200] Furthermore, after receiving the first indication information, the first network device may determine based on the first indication information that the first communication interface cannot be established with the access network node portion of the relay node. The method flow shown in FIG9 further includes:

[0201] S920: The first network device determines that the first communication interface cannot be established.

[0202] As a possible implementation method, when the first network device determines that the first communication interface cannot be established, if the first network device receives a first request message for requesting to establish the first communication interface, the first network device may indicate the failure to establish the first communication interface through a first response message, or the first response message may indicate the release or suspension of the first communication interface.

[0203] Exemplarily, the first network device may be a second access network node or a second core network device, and the relay node may send a first request message to the first network device, and the first network device may indicate to the relay node through a first response message that the first communication interface has failed to be established, that the first communication interface has been released, or that the first communication interface has been suspended; alternatively, the first access network node may send a first request message to the first network device, and the first network device may indicate to the first access network node through a first response message that the first communication interface has failed to be established, that the first communication interface has been released, or that the first communication interface has been suspended.

[0204] It should be noted that, in the case where the first response message is used to indicate the release or suspension of the first communication interface, the first communication interface has already been established between the first network device and the access network node part of the relay node. That is, after receiving the first request message, the first network device has already established the first communication interface with the access network node part of the relay node in response to the first request message, and after knowing that the first communication interface cannot be established with the access network node part of the relay node based on the first indication information, the first network device indicates the release or suspension of the first communication interface through the first response message. In the case where the first response message is used to indicate the failure to establish the first communication interface, the first network device may be, after receiving the first request message, sending the first response message to the relay node in response to the first request message, indicating the failure to establish the first communication interface.

[0205] Exemplarily, the first response message may include a first cause value. If the first response message indicates that the first communication interface fails to be established, the first cause value is used to indicate the reason for the failure to establish the first communication interface. For example, the first cause value is used to indicate that the reason for the failure to establish the first communication interface is: the relay node is an unauthorized node; or,

[0206] If the first response message indicates that the first communication interface is released or suspended, the first cause value is used to indicate the reason why the first communication interface is released or suspended. For example, the first cause value is used to indicate that the reason why the first communication interface is released or suspended is: the relay node is an unauthorized node.

[0207] In this embodiment, the first cause value may also be referred to as indication information #1, which indicates the reason why the first communication interface fails to be established, is released, or is suspended.

[0208] In addition, in this implementation, if the first network device is a second access network node or a second core network device, and the first network device determines, based on the first indication information, that it cannot establish a first communication interface with the access network node portion of the relay node, then after the first network device receives the first request message from the relay node, the first network device determines not to forward the first request message to the first access network node. Alternatively, after the first network device receives the first request message from the first access network node, the first network device determines not to forward the first request message to the relay node.

[0209] For example, based on the implementation method #2 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concept above, the relay node first transmits the XnAP message carrying the Xn setup request message sent to the first access network node to the second access network node through the DRB used to carry the PDU session of the Xn interface (e.g., general / dedicated PDU session). After the second access network node recognizes that it is the Xn data of the relay node, it will not continue to forward it to the first access network node based on the unauthorized status of the relay node. Or,

[0210] For example, based on the implementation method #2 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concepts above, the first access network node first transmits the XnAP message carrying the Xn establishment request message sent to the relay node to the second access network node through the Xn interface. The second access network node will not continue to forward it to the relay node based on the unauthorized status of the relay node.

[0211] For another example, based on implementation method #1 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concepts above, the relay node first transmits the XnAP message carrying the Xn setup request message sent to the first access network node to the second core network device through the PDU session used to carry the Xn interface (e.g., a general / dedicated PDU session). After the second core network device recognizes that it is the Xn data of the relay node, it will not continue to forward it to the first access network node based on the unauthorized status of the relay node.

[0212] For another example, based on implementation method #1 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concepts above, the first access network node first transmits the XnAP message carrying the Xn establishment request message sent to the relay node to the second core network device. The second core network device will not continue to forward it to the relay node based on the unauthorized status of the relay node.

[0213] As another possible implementation, when the first network device determines that the first communication interface cannot be established, if the first network device is the first access network node or the second access network node, the first network device determines not to actively initiate a request to establish the first communication interface.

[0214] Optionally, the authorization state of the relay node may be updated from the unauthorized state to the authorized state, and the method flow shown in FIG9 may further include:

[0215] S930: The first network device receives second indication information from the second network device. Accordingly, the second network device sends the second indication information to the first network device.

[0216] Specifically, the second indication information is used to indicate that the relay node is an authorized node, and / or the second indication information is used to indicate that establishment of the first communication interface is allowed.

[0217] As a possible implementation, if the first network device is a first access network node or a first core network device, the second network device may be a second access network node and / or a second core network device. That is, the first network device receiving the second indication information includes: receiving the second indication information from the second access network node; and / or receiving the second indication information from the second core network device.

[0218] In this implementation, the manner in which the second access network node and / or the second core network device determines the first network device and sends the second indication information to the first network device can refer to the description in the above step S910 about the second access network node and / or the second core network device determining the first network device and sending the first indication information to the first network device, which will not be repeated here.

[0219] As another possible implementation, if the first network device is a second access network node, the second network device may be a second core network device. That is, the first network device receiving the second indication information includes: receiving the second indication information from the second core network device.

[0220] Exemplarily, after receiving the second indication information, the first network device can determine that the first communication interface can be established based on the second indication information.

[0221] As a possible implementation, when the first network device determines that the first communication interface can be established, if the first network device receives a second request message for requesting establishment of the first communication interface, the first network device may instruct establishment of the first communication interface through a second response message.

[0222] Exemplarily, the first network device may be a second access network node or a second core network device, then the relay node may send a second request message to the first network device, and the first network device may instruct the relay node to establish a first communication interface through a second response message; or, the first access network node may send a second request message to the first network device, and the first network device may instruct the first access network node to establish a first communication interface through a second response message.

[0223] In addition, in this implementation, if the first network device is a second access network node or a second core network device, and the first network device determines, based on the second indication information, that a first communication interface can be established with the access network node portion of the relay node, after the first network device receives the second request message from the relay node, the first network device determines that the second request message can be forwarded to the first access network node. Alternatively, after the first network device receives the second request message from the first access network node, the first network device determines to forward the second request message to the relay node.

[0224] For example, based on the implementation method #2 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concept above, the relay node first transmits the XnAP message carrying the Xn setup request message sent to the first access network node to the second access network node through the DRB used to carry the PDU session of the Xn interface (e.g., a general / dedicated PDU session). After the second access network node recognizes that it is the Xn data of the relay node, it continues to forward the XnAP message to the first access network node based on the authorization status of the relay node. Or,

[0225] For example, based on the implementation method #2 of the backhaul process of the NG and / or Xn interface of WAB-gNB in ​​the basic concepts above, the first access network node first transmits the XnAP message carrying the Xn establishment request message sent to the relay node to the second access network node through the Xn interface, and the second access network node continues to forward the XnAP message to the relay node based on the authorization status of the relay node.

[0226] For another example, based on implementation method #1 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concepts above, the relay node first transmits the XnAP message carrying the Xn setup request message sent to the first access network node to the second core network device through the PDU session used to carry the Xn interface (e.g., a general / dedicated PDU session). After the second core network device recognizes that it is the Xn data of the relay node, it continues to forward the XnAP message to the first access network node based on the authorization status of the relay node.

[0227] For another example, based on implementation method #1 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concepts above, the first access network node first transmits the XnAP message carrying the Xn establishment request message sent to the relay node to the second core network device, and the second core network device continues to forward the XnAP message to the relay node based on the authorization status of the relay node.

[0228] As another possible implementation, when the first network device determines that the first communication interface can be established, if the first network device is the first access network node or the second access network node, the first network device determines that it can actively initiate a request to establish the first communication interface.

[0229] In the communication method shown in Figure 9, after receiving the first indication information, the first network device can determine based on the first indication information that the first communication interface cannot be established with the access network node portion of the relay node, wherein the first indication information can directly indicate that the first communication interface cannot be established, or can indirectly indicate that the first communication interface cannot be established by indicating that the relay node is an unauthorized node. This allows the first network device to determine that the first communication interface cannot be established with the access network node portion of the relay node when the relay node is in an unauthorized state, thereby facilitating the management of the communication interface of the access network node portion of the relay node when the relay node is in an unauthorized state. In addition, not establishing the first communication interface can reduce unnecessary signaling overhead.

[0230] In addition, when the relay node is updated from an unauthorized state to an authorized state, the first network device can be notified through the second indication information that a first communication interface can be established between the first network device and the access network node portion of the relay node. For example, the second indication information can directly indicate that the first communication interface is allowed to be established, or it can indirectly indicate that the first communication interface is allowed to be established by indicating that the relay node is an authorized node. This allows the first network device to determine that the first communication interface can be established between the first network device and the access network node portion of the relay node when the relay node is updated from an unauthorized state to an authorized state, so as to facilitate the management of the communication interface of the access network node portion of the relay node when the relay node is updated from an unauthorized state to an authorized state.

[0231] The embodiment corresponding to FIG9 mainly considers situations where the relay node is initially in an unauthorized state, is updated from an unauthorized state to an authorized state, or is updated from an authorized state to an unauthorized state. For ease of understanding, several authorization states of the relay node are described below with reference to specific examples.

[0232] Furthermore, for ease of description, in the following embodiments, the relay node is referred to as a WAB node, the mobile terminal portion of the relay node is referred to as a WAB-MT, the access network node portion of the relay node is referred to as a WAB-gNB, the second core network device is referred to as the CN of WAB-MT, the terminal device is referred to as a UE, the first core network device is referred to as the CN of UE, the first access network node is referred to as the donor-gNB, and the second access network node is referred to as the other-gNB. Furthermore, communication interface #1 is referred to as the NG interface, communication interface #2 is referred to as the second Xn interface, and communication interface #3 is referred to as the first Xn interface. The CN of WAB-MT includes, but is not limited to, core network elements such as the AMF, SMF, or UPF serving the WAB-MT; and the CN of UE includes, but is not limited to, core network elements such as the AMF, SMF, or UPF serving the UE.

[0233] It should be noted that the names of devices, nodes, network elements, communication interfaces, or messages in the following embodiments are merely examples and do not constitute any limitation on the scope of protection of this application.

[0234] In the following embodiments, the steps executed by the WAB-gNB may be implemented by the WAB-MT, and the steps executed by the WAB-MT may be implemented by the WAB-gNB. It can be understood that the mobile terminal part and the access network node part in the WAB node are functionally divided, rather than two independent devices, that is, the steps executed by the WAB-gNB and the steps executed by the WAB-MT can be collectively referred to as steps executed by the WAB node.

[0235] In addition, in this application, WAB-gNB in ​​an unauthorized state can be understood as WAB-MT and / or WAB-gNB in ​​an unauthorized state; or, WAB-gNB in ​​an authorized state can be understood as WAB-MT and / or WAB-gNB in ​​an authorized state.

[0236] For example, in the present application, the WAB-gNB being in the unauthorized state may mean that the authentication node determines that the WAB-MT is in the unauthorized state, and / or, the authentication node may determine that the WAB-gNB is in the unauthorized state. For another example, in the present application, the WAB-gNB being in the authorized state may mean that the authentication node determines that the WAB-MT is in the authorized state, and / or, the authentication node may determine that the WAB-gNB is in the authorized state.

[0237] Optionally, if the state of the WAB-gNB is determined by determining the state of the WAB-MT (e.g., unauthorized state or authorized state), the authentication node may be the CN of WAB-MT, which authenticates the WAB-MT and notifies the WAB node, donor-gNB, CN of UE, or other-gNB of the authentication result.

[0238] Optionally, if the WAB-gNB state (e.g., unauthorized or authorized) is determined directly, the authentication node may be the CN of UE and / or the donor-gNB. For example, the authentication node is the CN of UE. After authenticating the WAB-gNB, the CN of UE notifies the WAB-gNB, the CN of WAB-MT, the donor-gNB, or another-gNB of the authentication result. The CN of WAB-MT may manage the WAB-MT's PDU session based on the authentication result. For another example, the authentication node is the donor-gNB. After authenticating the WAB-gNB, the donor-gNB notifies the WAB-gNB, the CN of WAB-MT, the donor-gNB, or another-gNB of the authentication result. The donor-gNB or other-gNB may manage the Xn interface based on the authentication result; the WAB-gNB may manage the NG and Xn interfaces based on the authentication result; and the CN of UE may manage the NG interface based on the authentication result. For example, managing the Xn and / or NG interface may mean allowing the establishment of the Xn and / or NG interface based on the authorization status; or, the CN of WAB-MT may mean allowing the establishment or activation of a backhaul PDU session based on the authorization status. For another example, managing the Xn and / or NG interface may mean not allowing the establishment of the Xn and / or NG interface based on the unauthorized status; or, the CN of WAB-MT may mean not allowing the establishment, release, or deactivation of a backhaul PDU session based on the unauthorized status.

[0239] It should be noted that if the CN of UE and / or donor-gNB authenticates the WAB-gNB, the authentication result can be forwarded to other nodes (such as WAB-gNB or other-gNB) via the CN of WAB-MT. In addition, the CN of WAB-MT can also manage the PDU session of the WAB-MT based on the authentication result.

[0240] For ease of description, the following example uses the CN of WAB-MT authenticating the WAB-MT as an example. If another authentication node (e.g., the CN of UE and / or donor-gNB) authenticates the WAB-gNB, the authentication result can be forwarded by the CN of WAB-MT. For a detailed description, please refer to the description of the CN of WAB-MT obtaining the authentication result in the following embodiment, and will not be repeated here. It should be understood that the present application does not impose any limitations on the WAB node authentication process; authentication of the WAB-MT and / or WAB-gNB can be performed.

[0241] Figure 10 is a schematic flow chart of another communication method provided by the present application. The communication method shown in Figure 10 mainly illustrates how the network side restricts the establishment of the first communication interface when the WAB node is in the initial unauthorized state. It includes the following steps:

[0242] S1010: The WAB-MT sends a registration request message to the CN of WAB-MT. Correspondingly, the CN of WAB-MT receives the registration request message from the WAB-MT.

[0243] For example, in this embodiment, the WAB-MT sends a registration request message to the CN of WAB-MT through the donor-gNB to which it is connected. The registration request message is used to request that the WAB-MT information be registered in the CN of WAB-MT.

[0244] In this embodiment, the WAB-MT may indicate the type of the WAB-MT to the network side during the initial registration request process.

[0245] As an example and not a limitation, in this embodiment, the WAB-MT may indicate the type of the WAB-MT to the network side in the following two implementations:

[0246] As a possible implementation, the WAB-MT carries information #1 in the NAS message that carries the registration request message. This information #1 is used to indicate the type of the WAB-MT. For example, the NAS message carries a WAB indication information element, which is used to indicate that the accessing UE is a WAB node.

[0247] Optionally, in this implementation, the WAB-MT may also indicate its type to the donor-gNB through message 5 (msg5) so that the donor-gNB selects the CN of WAB-MT that supports the WAB node (e.g., selects the AMF that supports the WAB node).

[0248] As another possible implementation, the WAB-MT includes information #1 in the RRC setup complete message carrying the registration request sent to the donor-gNB. Information #1 is used to indicate the type of the WAB-MT. For example, the RRC setup complete message carries a WAB indication information element, which is used to indicate that the accessed UE is a WAB node.

[0249] In this implementation, after the donor-gNB determines the CN of WAB-MT that supports the WAB node, the donor-gNB further indicates to the CN of WAB-MT through an NGAP message (e.g., initial UE message) that the UE requesting access is a WAB node.

[0250] It should be noted that the above two implementation methods are only examples and do not constitute any limitation to the scope of protection of this application. WAB-MT can also indicate its own type to the network side in other ways. For example, WAB-MT carries information #1 in the registration request message; for example, the network side determines the type of WAB-MT based on historical communication data, which will not be repeated here.

[0251] Furthermore, in this embodiment, after receiving the registration request message, the CN of WAB-MT authenticates the WAB node requesting access and determines the authorization status of the WAB node. This embodiment mainly considers the subsequent process when the WAB node is in the unauthorized state. Therefore, the method flow shown in FIG10 further includes:

[0252] S1020, the CN of WAB-MT authenticates the WAB node.

[0253] Specifically, the CN of WAB-MT authenticates the WAB node and determines that the WAB node is in an unauthorized state. The WAB node is the WAB node including the above-mentioned WAB-MT.

[0254] When the CN of WAB-MT determines that the WAB node is in an unauthorized state, the CN of WAB-MT may notify the donor-gNB of the authorization state of the WAB node through a first message #1. The method flow shown in FIG9 further includes:

[0255] S1030: The CN of WAB-MT sends a first message #1 to the donor-gNB. In response, the donor-gNB receives the first message #1 from the CN of WAB-MT.

[0256] Specifically, the first message #1 includes first indication information, which indicates that the WAB node is an unauthorized node. For example, the CN of the WAB-MT may indicate the unauthorized status of the WAB node to the donor-gNB via a downlink NGAP message (such as an Initial Context Setup Request message), i.e., the first message is a downlink NGAP message.

[0257] Optionally, the CN of WAB-MT may also indicate the unauthorized state of the WAB node to the WAB-MT through a downlink message (eg, a downlink NAS message).

[0258] Exemplarily, in this embodiment, in the initial unauthorized state of the WAB node, the network side restricts the establishment of the first communication interface in the following possible ways, but not limited to:

[0259] Method 1.1 for restricting establishment of the first communication interface on the network side: The first network device determines not to establish the first communication interface. The first network device is a peer of the WAB-gNB, such as a CN of UE, other-gNB, or donor-gNB.

[0260] In the case shown in method 1.1, the method flow shown in FIG10 includes the following steps:

[0261] S1001: A first PDU session is established between the WAB-MT and the CN of the WAB-MT.

[0262] Specifically, the first PDU session can be used to carry data of the first communication interface of the WAB node.

[0263] For example, after the WAB node successfully joins the network, a first PDU session for carrying data of the first communication interface of the WAB node is successfully established between the WAB-MT and the CN of WAB-MT. The specific process of establishing the first PDU session can refer to the PDU session establishment process shown in Figure 6 above, which will not be repeated here.

[0264] Optionally, the first PDU session can be a general PDU session, that is, the PDU session can also be used as a backhaul for data other than the first communication interface, such as UE user plane data, or the first PDU session can also be a dedicated PDU session, that is, a PDU session that specifically carries data of the first communication interface.

[0265] S1002: The first network device receives first indication information.

[0266] Please refer to the description of step S910 in the communication method shown in FIG9 , which will not be repeated here.

[0267] For example, for the NG interface, in the case shown in method 1.1, the following steps are further included:

[0268] S1003. The WAB-gNB sends a first request message to the CN of UE. Correspondingly, the CN of UE receives the first request message from the WAB-gNB.

[0269] Specifically, the first request message is used to request the establishment of an NG interface, and the first request message may be an NG establishment request message. Exemplarily, since the first PDU session has been established, the WAB-gNB may send the first request message to the CN of UE through the first PDU session.

[0270] For example, based on the implementation method #1 and / or implementation method #2 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concepts above, the WAB-gNB sends an NGAP message carrying an NG setup request message to the CN of UE through the first PDU session (e.g., general / dedicated PDU session) of the WAB-MT for carrying the NG interface.

[0271] Further, in the case shown in mode 1, it can be seen from the above step S1002 that the CN of UE can be informed that the NG interface cannot be established with the WAB-gNB, so that in the case shown in mode 1, after the CN of UE receives the first request message, it will refuse to establish the NG interface. The method flow shown in Figure 10 also includes:

[0272] S1004: The CN of UE sends a first response message to the WAB-gNB. Correspondingly, the WAB-gNB receives the first response message from the CN of UE.

[0273] Specifically, the first response message indicates that the NG interface is rejected. For example, the CN of UE feeds back the indication of rejecting the NG interface establishment to the WAB node via an NG setup failure message.

[0274] Optionally, the first response message may carry a first cause value, which indicates the reason for the failure to establish the NG interface, for example, the cause value is WAB-node is not authorized.

[0275] For example, for the first Xn interface, in the case shown in method 1.1, the following steps are further included:

[0276] S1005: The WAB-gNB sends a first request message to the donor-gNB. In response, the donor-gNB receives the first request message from the WAB-gNB.

[0277] Specifically, the first request message may be an Xn establishment request message. For example, since the first PDU session has been established, the WAB-gNB may send the first request message through a DRB or SRB donor-gNB used to carry the first PDU session (e.g., a general / dedicated PDU session) of the Xn interface.

[0278] For example, the WAB-gNB sends an XnAP message carrying an Xn setup request message to the donor-gNB through the first PDU session (e.g., general / dedicated PDU session) of the WAB-MT for carrying the Xn interface.

[0279] In this implementation, similar to the NG interface operation described above, the donor-gNB can learn that the Xn interface cannot be established with the WAB-gNB through the method described in step S1002 above. Therefore, in the case shown in method 1, after receiving the Xn establishment request message, the donor-gNB will refuse to establish the Xn interface. The method flow shown in Figure 10 also includes:

[0280] S1006: The donor-gNB sends a first response message to the WAB-gNB. In response, the WAB-gNB receives the first response message from the donor-gNB.

[0281] Specifically, the first response message indicates a refusal to establish the Xn interface. For example, the donor-gNB feeds back an indication of the refusal to establish the Xn interface to the WAB-gNB via an Xn setup failure message.

[0282] Optionally, the first response message may carry a first cause value, which indicates the reason for the failure to establish the Xn interface, for example, the first cause value is WAB-node is not authorized.

[0283] In addition, it should be noted that since the initiator of the Xn interface establishment request between the two access network nodes can be either party, if the donor-gNB is the initiator, then the donor-gNB will not actively initiate an Xn interface establishment request with the WAB-gNB based on the first indication information in the above step S1002.

[0284] For example, for the second Xn interface, in the case shown in method 1.1, the following possibilities are also included:

[0285] Possibility 1: The WAB-gNB sends a first request message to the other-gNB requesting establishment of a second Xn interface. The other-gNB determines that it cannot establish an Xn interface with the WAB-gNB based on the unauthorized status of the WAB, and feeds back a first response message indicating refusal to establish the second Xn interface.

[0286] For example, in the case shown in Possible 1, the method flow shown in FIG10 includes the following steps:

[0287] S1007: The WAB-gNB sends a first request message to the other-gNB. In response, the other-gNB receives the first request message from the WAB-gNB.

[0288] Specifically, the first request message may be an Xn establishment request message. For example, since the first PDU session has been established, the WAB-gNB may send the first request message to the other-gNB through the first PDU session.

[0289] For example, in the case shown in Possible 1, the WAB-gNB may send a first request message to the other-gNB through the following possible implementation methods:

[0290] As a possible implementation, based on implementation #1 of the WAB-gNB backhaul process for the NG and / or Xn interface described in the basic concepts above, the WAB-gNB sends an XnAP message carrying an Xn setup request message to the other-gNB via the first PDU session (e.g., a general / dedicated PDU session) of the WAB-MT used to carry the Xn interface. That is, the first request message may be an XnAP message carrying the Xn setup request message. In this implementation, the WAB-gNB sends the first request message to the other-gNB via the CN of WAB-MT. Based on the unauthorized status of the WAB node, the CN of WAB-MT may also send information #2 to the other gNB when sending the first request message. Information #2 indicates that the WAB node is in an unauthorized state. This can be understood as an implementation in which the other-gNB obtains the first indication information from the CN of WAB-MT. Based on information #2, the other-gNB learns that the WAB node is unauthorized and may then proceed to subsequent steps (e.g., step S1008).

[0291] For example, in this implementation, the CN of WAB-MT adds a flag in the header of the data packet related to the Xn setup request message sent from the WAB-gNB to the other-gNB to indicate that the WAB node is unauthorized. The CN then sends the Xn setup request message to the other gNB. After receiving the Xn setup request message, the other-gNB learns that the WAB node is unauthorized based on the flag.

[0292] As another possible implementation, based on implementation #2 of the backhaul process for the WAB-gNB's NG and / or Xn interfaces in the basic concepts described above, the WAB-gNB may send a first request message to the other-gNB via the donor-gNB. When the donor-gNB forwards the first request message to the donor-gNB, it may notify the other-gNB of the unauthorized status of the WAB node via message #2. This can be understood as an implementation in which the other-gNB obtains the first indication information from the CN of the WAB-MT. Upon learning that the WAB node is unauthorized, the other-gNB may proceed to subsequent steps (e.g., subsequent step S1008).

[0293] For example, in this implementation, the donor-gNB adds a flag to the data packet associated with the Xn setup request message received from the WAB-MT via the DRB or signaling radio bearer (SRB). This flag indicates that the WAB node is in the unauthorized state. The donor-gNB then sends the Xn setup request message to the other gNB. Upon receiving the Xn setup request message, the other-gNB detects that the WAB node is unauthorized based on information #2.

[0294] For example, the donor-gNB may, based on the unauthorized status information of the WAB node, include information #2 indicating the unauthorized status of the WAB node in the first request message received from the DRB or SRB transmitted back by the WAB-MT, thereby indicating the unauthorized status of the WAB node through this information #2. For example, the donor-gNB adds information #2 indicating the unauthorized status of the WAB node to an Xn setup request message sent by the WAB-gNB to the other gNB, and then sends the Xn setup request message to the other gNB. After receiving the Xn setup request message, the other-gNB learns that the WAB node is unauthorized based on information #2 indicating the unauthorized status of the WAB node carried in the Xn setup request message.

[0295] In the case shown in the first possibility, similar to the above-mentioned NG interface operation, the other-gNB may learn that it cannot establish the Xn interface with the WAB-gNB. Therefore, after receiving the Xn establishment request message, the other-gNB will refuse to establish the Xn interface. In the case shown in the first possibility, the method flow shown in FIG10 further includes:

[0296] S1008: The other-gNB sends a first response message to the WAB-gNB. Correspondingly, the WAB-gNB receives the first response message from the other-gNB.

[0297] Specifically, the first response message indicates a refusal to establish the Xn interface. For example, the other-gNB feeds back an indication of the refusal to establish the Xn interface to the WAB-gNB via an Xn setup failure message.

[0298] Optionally, the first response message may carry a first cause value, which indicates the reason for the failure to establish the Xn interface, for example, the first cause value is WAB-node is not authorized.

[0299] Possibility 2: The WAB-gNB sends a first request message to the other-gNB through the CN of WAB-MT requesting to establish a second Xn interface. The CN of WAB-MT determines not to forward the first request message to the other-gNB based on the unauthorized status of the WAB.

[0300] For example, in the case shown in the second possibility, the method flow shown in FIG10 includes the following steps:

[0301] S1009. The WAB-gNB sends a first request message to the CN of WAB-MT. Correspondingly, the CN of WAB-MT receives the first request message from the WAB-gNB.

[0302] Specifically, the first request message may be an Xn establishment request message. For example, since the first PDU session has been established, the WAB-gNB may send the first request message to the CN of the WAB-MT through the first PDU session.

[0303] For example, the WAB-gNB first transmits the XnAP message carrying the Xn setup request message sent to the other-gNB to the CN of the WAB-MT through the first PDU session of the WAB-MT used to carry the Xn interface (e.g., a general / dedicated PDU session).

[0304] In the second possibility, the CN of the WAB-MT may determine that the WAB node is in an unauthorized state through step S1020, thereby determining not to forward the first request message to the other-gNB. In the second possibility, the method flow shown in FIG10 further includes:

[0305] S1091: The CN of the WAB-MT determines not to forward the first request message to the other-gNB.

[0306] For example, after the CN of WAB-MT identifies that the data is Xn data of the WAB-gNB, it determines not to continue forwarding the first request message to the other-gNB based on the unauthorized status of the WAB node.

[0307] Possibility three: The WAB-gNB sends a first request message to the other-gNB through the donor-gNB requesting establishment of a second Xn interface. The donor-gNB determines not to forward the first request message to the other-gNB based on the unauthorized status of the WAB.

[0308] For example, in the case shown in possibility three, the method flow shown in FIG10 includes the following steps:

[0309] S1092: The WAB-gNB sends a first request message to the donor-gNB. In response, the donor-gNB receives the first request message from the WAB-gNB.

[0310] Specifically, the first request message may be an Xn establishment request message. For example, since the first PDU session has been established, the WAB-gNB may send the first request message to the donor-gNB via a DRB or SRB.

[0311] For example, based on implementation method #2 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concepts above, the WAB-gNB first transmits the XnAP message carrying the Xn setup request message sent to the other-gNB to the donor-gNB through the DRB or SRB of the first PDU session (e.g., general / dedicated PDU session) of the WAB-MT used to carry the Xn interface to the donor-gNB.

[0312] In the case shown in the third possibility, the donor-gNB may determine through step S1002 that the WAB node is in the unauthorized state, thereby determining not to forward the first request message to the other-gNB. In the case shown in the third possibility, the method flow shown in FIG10 further includes:

[0313] S1093: The donor-gNB determines not to forward the first request message to the other-gNB.

[0314] For example, after the donor-gNB receives the first request message carrying the Xn establishment request message sent by the WAB-gNB to the other-gNB, the donor-gNB identifies that the Xn data is from the WAB-gNB and does not forward it to the other-gNB based on the unauthorized status of the WAB node.

[0315] In the third possible scenario, after the donor-gNB determines not to forward the Xn setup request message sent by the WAB-gNB to the other-gNB, it may reply to the WAB node with a first response message indicating that the Xn interface establishment failed. For example, the donor-gNB may feedback the Xn interface establishment failure indication to the WAB-gNB via an Xn setup failure message.

[0316] Optionally, the first response message may carry a first cause value, which indicates the reason for the failure to establish the Xn interface, for example, the first cause value is WAB-node is not authorized.

[0317] In addition, it should be noted that since the initiator of the Xn interface establishment request between the two access network nodes can be either party, if the other-gNB is the initiator, then the other-gNB will not actively initiate the Xn interface establishment request with the WAB-gNB based on the first indication information in the above step S1002; or,

[0318] In the second possible scenario, after receiving the Xn Setup Request message sent by other-gNB to WAB-gNB, the CN of WAB-MT does not forward the message to WAB-gNB due to the unauthorized status of the WAB node. Alternatively,

[0319] In the third possible scenario, after receiving the Xn Setup Request message sent by the other-gNB to the WAB-gNB, the donor-gNB may not forward the message to the WAB-gNB due to the unauthorized status of the WAB node, and may instead reply with an Xn Setup Failure message to the other-gNB. Optionally, the Xn Setup Failure message may carry a cause value indicating the cause of the Xn interface establishment failure, such as the first cause value.

[0320] Through the solution shown in approach 1.1, the network side (e.g., the CN of the UE, other-gNB, or donor-gNB) can learn, based on the received first indication information, that it cannot establish the first communication interface with the WAB-gNB. Therefore, upon receiving the WAB-gNB first request message, the network side (e.g., the CN of the UE and / or the donor-gNB) can reject the establishment request. Alternatively, the network side (e.g., the CN of the UE and / or the donor-gNB) can determine not to forward the received first request message based on the unauthorized status of the WAB node. Alternatively, the other-gNB and / or the donor-gNB can determine not to proactively initiate the establishment request for the first communication interface based on the received first indication information, thereby managing the communication interface of the WAB-gNB when the WAB node is in the unauthorized status. Furthermore, not establishing the first communication interface can reduce unnecessary signaling overhead.

[0321] Mode 1.2 of the network side restricting the establishment of the first communication interface: the CN of WAB-MT determines not to establish or deactivate a PDU session for data of the first communication interface.

[0322] In the case shown in method 1.2, the method flow shown in FIG10 includes the following steps:

[0323] S1011 , the CN of WAB-MT determines not to establish or deactivate the first PDU session.

[0324] In this embodiment, the CN of WAB-MT may determine that the establishment of the first PDU session fails based on the unauthorized state of the WAB node, or determine to deactivate the requested first PDU session.

[0325] Optionally, in the case shown in method 1.2, if the CN of WAB-MT authenticates the relay node based on the above step S1020 and determines that the WAB node is an unauthorized node, it may determine not to establish or deactivate the first PDU session after receiving the WAB-MT third request message. The method shown in FIG10 may further include:

[0326] S1012: The WAB-MT sends a third request message to the CN of WAB-MT. Correspondingly, the CN of WAB-MT receives the third request message from the WAB-MT.

[0327] Specifically, the third request message is used to request the establishment of a first PDU session for carrying data of the first communication interface. Exemplarily, the first PDU session may be a general PDU session, that is, the PDU session may also be used as a backhaul for data other than the first communication interface, such as UE user plane data, or the first PDU session may also be a dedicated PDU session, that is, a PDU session specifically for carrying data of the first communication interface.

[0328] Furthermore, after the CN of WAB-MT determines not to establish or deactivate the first PDU session, it may notify the WAB node through third indication information. The method shown in FIG10 may further include:

[0329] S1013: The CN of WAB-MT sends third indication information to the WAB-MT. Correspondingly, the WAB-MT receives the third indication information from the CN of WAB-MT.

[0330] Specifically, the third indication information indicates that the establishment of the first PDU session fails, or indicates that the first PDU session is deactivated.

[0331] For example, if the CN of WAB-MT indicates through the third indication information that the establishment of the first PDU session fails, the CN of WAB-MT can reply to the WAB-MT with a PDU session establishment reject message through a downlink NAS message, where the PDU session establishment reject message is a 5G session management message.

[0332] For another example, if the CN of WAB-MT indicates through the third indication information that the first PDU session is deactivated, the indication can be implemented in the following two ways:

[0333] As a possible implementation, the CN of WAB-MT indicates to the WAB-MT that the PDU session is established but deactivated through an existing or newly added downlink NGAP message that can carry the NAS-PDU. For example, the third indication information is a downlink NAS transport message, that is, the CN of WAB-MT carries a PDU session establishment accpet message with a cause value of deactivation through the NAS-PDU in the downlink NAS transport message.

[0334] As another possible implementation, the CN of WAB-MT first establishes a first PDU session with the WAB-MT, and then activates the first PDU session through the PDU session release process; or, the CN of WAB-MT first establishes the first PDU session with the WAB-MT, and then the donor instructs the CN of the WAB-MT to activate the first PDU session; or, the WAB-MT determines to deactivate the first PDU session.

[0335] Optionally, the CN of WAB-MT may refuse to establish or deactivate all PDU sessions requested by the WAB-MT according to the above method, regardless of whether they are all dedicated PDU sessions (including PDU sessions specifically used to transmit UE service data) or all general PDU sessions.

[0336] Through the solution shown in method 1.2, the CN of WAB-MT determines, based on the unauthorized state of the WAB node, that the PDU session requested by the WAB node has failed to be established, or determines to deactivate the PDU session requested by the WAB node. This prevents the PDU session used to carry data on the first communication interface from transmitting data, eliminating the need to continue the subsequent first communication interface establishment process. This enables management of the WAB-gNB communication interface when the WAB node is in the unauthorized state. Furthermore, not establishing the first communication interface can reduce unnecessary signaling overhead.

[0337] Mode 1.3 of restricting establishment of the first communication interface on the network side: the WAB node determines not to initiate a PDU session establishment request based on the unauthorized state, or determines not to initiate a first communication interface establishment request.

[0338] In the case shown in method 1.3, the method flow shown in FIG10 includes the following steps:

[0339] S1021: The WAB-MT receives first information.

[0340] Specifically, the first information is used to indicate that the WAB node is an unauthorized node.

[0341] As a possible implementation manner, the WAB-MT may receive the first information from the CN of WAB-MT. In this implementation manner, the first information may be a NAS message sent by the CN of WAB-MT to the WAB node.

[0342] As another possible implementation, the WAB-MT may receive first information from the CN of WAB-MT. In this implementation, the first information may be an RRC message sent by the donor-gNB to the relay node. For example, in this implementation, the CN of WAB-MT sends information to the donor-gNB indicating that the WAB node is an unlicensed node. After receiving the indication from the CN of WAB-MT, the donor-gNB indicates to the WAB node that the relay node is an unlicensed node through an RRC message.

[0343] S1022: The WAB node determines not to initiate a first PDU session establishment request, or determines not to initiate a first communication interface establishment request.

[0344] Exemplarily, the WAB node determines not to initiate a general or dedicated PDU session establishment request based on the unauthorized state, for example, the WAB node does not initiate a PDU session establishment request for carrying data of the first communication interface. For another example, the WAB node does not initiate all PDU session establishment requests.

[0345] Exemplarily, if a PDU session (e.g., a general or dedicated PDU session) for carrying data of the first communication interface has been established between the WAB-MT and the CN of WAB-MT, the WAB node determines not to initiate a request to establish the first communication interface based on the unauthorized status of the WAB node.

[0346] Through the solution shown in method 1.3, the WAB-MT determines not to initiate a PDU session establishment request for carrying data on the first communication interface based on the unauthorized state, eliminating the need to continue the subsequent first communication interface establishment process. Alternatively, the WAB-MT determines not to initiate a first communication interface establishment request based on the unauthorized state, thereby managing the communication interface of the WAB-gNB when the WAB node is in the unauthorized state. In addition, not establishing the first communication interface can reduce unnecessary signaling overhead.

[0347] The network side restricts the first communication interface establishment mode 1.4: the CN of WAB-MT instructs the WAB node to enter the idle state / inactive state, or to deregister.

[0348] In the case shown in method 1.4, the method flow shown in FIG10 includes the following steps:

[0349] S1031: The CN of WAB-MT sends second information to the WAB node. Correspondingly, the WAB node receives the second information from the CN of WAB-MT.

[0350] Specifically, the second information is used to indicate at least one of the following:

[0351] Instructing the WAB node to enter the RRC idle state, instructing the WAB node to enter the inactive state, or instructing the WAB node to deregister. For example, in the case shown in method 1.2, after the CN of WAB-MT authenticates the relay node based on the above step S1020 and determines that the WAB node is an unauthorized node, it can instruct the WAB node to enter the RRC idle state, instruct the WAB node to enter the inactive state, or instruct the WAB node to deregister through the second information.

[0352] Through the solution shown in method 1.4, the CN of WAB-MT instructs the WAB node to enter the RRC idle state, inactivate the WAB node, or deregister based on the WAB node's unauthorized state. This prevents the WAB node from initiating PDU session establishment, communicating with the CN of UE, other-gNB, or donor-gNB, and continuing the first communication interface establishment process. This achieves management of the WAB-gNB communication interface when the WAB node is in the unauthorized state. Furthermore, not establishing the first communication interface reduces unnecessary signaling overhead.

[0353] In summary, the communication method shown in Figure 10 prevents the WAB node from establishing a first communication interface between the WAB-gNB and a first network device (e.g., CN of UE, other-gNB, or donor-gNB) when the WAB node is in an unauthorized state. This facilitates management of the communication interface of the access network node portion of the relay node when the relay node is in an unauthorized state. Furthermore, not establishing the first communication interface can reduce unnecessary signaling overhead.

[0354] Figure 11 is a schematic flow chart of another communication method provided by the present application. The communication method shown in Figure 11 mainly illustrates how the network side enables the establishment of the first communication interface when the WAB node changes from an unauthorized state to an authorized state. It includes the following steps:

[0355] The network side enables establishment of the first communication interface mode 2.1: the WAB node is in the RRC connected state.

[0356] Exemplarily, after joining the network, the WAB node is determined by the CN of WAB-MT to be in an unauthorized state. For detailed steps, refer to the description of steps S1010 and S1020 in the communication method shown in FIG10 .

[0357] Optionally, there is a first PDU session with the user plane activated between the WAB-MT and the CN of WAB-MT. The first PDU session can be a general PDU session, that is, the PDU session can also be used as data other than the first communication interface, such as the backhaul of UE user plane data, or the first PDU session can also be a dedicated PDU session, that is, a PDU session specifically carrying data of the first communication interface. There is no limitation on this in this embodiment.

[0358] In the case shown in method 2.1, the method flow shown in FIG11 includes the following steps:

[0359] S1110, the CN of WAB-MT determines that the WAB node becomes in the authorized state.

[0360] It should be noted that this embodiment does not impose any limitation on the reason for the change of the WAB node authorization status.

[0361] S1120: The CN of WAB-MT sends the first message #2 to the donor-gNB. In response, the donor-gNB receives the first message #2 from the CN of WAB-MT.

[0362] Specifically, the first message #2 includes second indication information, where the second indication information indicates the updated authorization status of the WAB node. For example, the CN of the WAB-MT indicates the updated authorization status to the donor-gNB via a downlink NGAP message (e.g., a UE context modification request message).

[0363] Optionally, the CN of WAB-MT may also inform the WAB-MT of the updated authorization status of the WAB node through a downlink NAS message.

[0364] Exemplarily, if the established PDU session does not have the first PDU session for carrying the first communication interface, the WAB-MT may request to establish the first PDU session. The method flow shown in FIG11 may further include:

[0365] S1130: The WAB-MT sends a third request message to the CN of WAB-MT. Correspondingly, the CN of WAB-MT receives the third request message from the WAB-MT.

[0366] Specifically, the third request message is used to request establishment of a first PDU session. Exemplarily, the first PDU session is used to carry data of the first communication interface, or the first PDU session is used to carry data of the first communication interface and data other than the data of the first communication interface.

[0367] For example, in the case shown in method 2.1, the network side can enable the establishment of the first communication interface in the following two ways:

[0368] Method 2.1.1 for enabling establishment of the first communication interface on the network side: Sending an indication to the first network device permitting establishment of the first communication interface. The first network device is a peer end of the WAB-gNB, such as a CN of UE, other-gNB, or donor-gNB.

[0369] In the case shown in method 2.1.1, the method flow shown in Figure 11 includes the following steps:

[0370] S1101: A first network device receives second indication information.

[0371] For step S1101 , reference may be made to the description of step S930 in the communication method shown in FIG9 , and details thereof will not be repeated here.

[0372] For example, for the NG interface, in the case shown in method 2.1.1, the following steps are also included:

[0373] S1102. The WAB-gNB sends a second request message to the CN of UE.

[0374] For the manner in which the WAB-gNB sends the second request message to the CN of UE in step S1102, reference can be made to the description of the WAB-gNB sending the first request message to the CN of UE in step S1003 in the communication method shown in Figure 10, which is not repeated here.

[0375] Furthermore, in the case shown in the method 2.1.1, it can be seen from the above step S1101 that the CN of UE can be informed that an NG interface can be established with the WAB-gNB, so that in the case shown in the method 2.1.1, after the CN of UE receives the second request message, it agrees to establish the NG interface. The method flow shown in Figure 11 also includes:

[0376] S1103: The CN of UE sends a second response message to the WAB-gNB. Correspondingly, the WAB-gNB receives the second response message from the CN of UE.

[0377] Specifically, the second response message indicates that the NG interface is established. For example, the CN of the UE replies with an NG setup response message to the WAB-gNB via the backhaul PDU session.

[0378] For example, for the first Xn interface, in the case shown in method 2.1.1, the following steps are further included:

[0379] S1104: The WAB-gNB sends a second request message to the donor-gNB.

[0380] For the manner in which the WAB-gNB sends the second request message to the donor-gNB in ​​step S1104, reference can be made to the description of the WAB-gNB sending the first request message to the donor-gNB in ​​step S1005 of the communication method shown in FIG10 , and details are omitted here.

[0381] Furthermore, in the case shown in method 2.1.1, as can be seen from the above step S1101, the donor-gNB can be informed that an Xn interface can be established with the WAB-gNB. Therefore, in the case shown in method 2.1.1, after receiving the second request message, the donor-gNB agrees to establish the Xn interface. The method flow shown in Figure 11 also includes:

[0382] S1105: The donor-gNB sends a second response message to the WAB-gNB. In response, the WAB-gNB receives the second response message from the donor-gNB.

[0383] Specifically, the second response message indicates that the Xn interface is established. For example, the donor-gNB replies with an Xn setup response message to the WAB-gNB.

[0384] In addition, it should be noted that since the initiator of the Xn interface establishment request between the two access network nodes can be either party, if the donor-gNB is the initiator, then the donor-gNB determines that it can actively initiate an Xn interface establishment request with the WAB-gNB based on the second indication information in the above step S1101.

[0385] For example, for the second Xn interface, in the case shown in method 2.1.1, the following steps are included:

[0386] S1106. The WAB-gNB sends a second request message to the other-gNB.

[0387] Specifically, the second request message may be an Xn establishment request message. For example, since the first PDU session has been established, the WAB-gNB may send the second request message to the other-gNB through the first PDU session.

[0388] For example, the WAB-gNB may send the first request message to the other-gNB in ​​the following possible implementations:

[0389] As a possible implementation, based on implementation #1 of the WAB-gNB backhaul process for the NG and / or Xn interface described in the basic concepts above, the WAB-gNB sends an XnAP message carrying an Xn setup request message to the other-gNB via the first PDU session (e.g., a general / dedicated PDU session) of the WAB-MT used to carry the Xn interface. That is, the second request message may be an XnAP message carrying the Xn setup request message. In this implementation, the WAB-gNB sends the second request message to the other-gNB via the CN of WAB-MT. The CN of WAB-MT may determine to forward the second request message to the other gNB based on the authorization status of the WAB node. It may also send information #3 to the other gNB, indicating that the WAB node is authorized. This can be understood as an implementation method in which the other-gNB obtains the second indication information from the CN of WAB-MT. The other-gNB learns of the WAB node's authorization based on information #3 and may then proceed to subsequent steps (e.g., step S1107).

[0390] For example, in this implementation, the CN of WAB-MT adds a flag to the header of the data packet related to the Xn setup request message sent by the WAB-gNB to the other-gNB to indicate WAB node authorization, and then sends the Xn setup request message to the other gNB. After receiving the Xn setup request message, the other-gNB obtains the WAB node authorization based on the flag.

[0391] In addition, it should be noted that in this implementation, since the initiator of the Xn interface establishment request between the two access network nodes can be either party, if the other-gNB is the initiator, then the other-gNB determines that it can actively initiate an Xn interface establishment request with the WAB-gNB based on the second indication information in the above step S1101; alternatively, after receiving the Xn establishment request message sent by the other-gNB to the WAB-gNB, the CN of WAB-MT forwards the Xn establishment request message to the WAB-gNB based on the authorization status of the WAB node. The CN of WAB-M can also send the above-mentioned information #3 to the WAB-gNB. This will not be repeated here.

[0392] As another possible implementation, based on implementation #2 of the backhaul process for the WAB-gNB's NG and / or Xn interface in the basic concepts described above, the WAB-gNB may send a second request message to the other-gNB via the donor-gNB. The donor-gNB may determine, based on the authorization status of the WAB node, whether to forward the second request message to the other gNB. The donor-gNB may also send information #3 to the other gNB. Information #3 indicates that the WAB node is in an authorized state. Information #3 is understood as an implementation method for the other-gNB to obtain the second indication information from the donor-gNB. The other-gNB learns of the WAB node's authorization based on information #3 and may then execute subsequent steps (e.g., subsequent step S1107).

[0393] For example, in this implementation, the donor-gNB adds information #3 to the data packet associated with the Xn setup request message received from the DRB or SRB backhauled by the WAB-MT. Information #3 may be a flag indicating that the WAB node is in an authorized state. For example, the donor-gNB adds a flag to the header of the data packet associated with the Xn setup request message sent from the WAB-gNB to the other gNB to indicate that the WAB node is authorized. The donor-gNB then sends the Xn setup request message to the other gNB. Upon receiving the Xn setup request message, the other-gNB learns of the WAB node's authorization based on information #3.

[0394] For example, after receiving the second request message from the DRB or SRB transmitted back by the WAB-MT, the donor-gNB carries information #3 indicating the authorization status of the WAB node in the second request message, thereby indicating the authorization status of the WAB node through this information #3. For example, the donor-gNB adds information #3 indicating the authorization status of the WAB node to the Xn setup request message sent by the WAB-gNB to the other gNB, and then sends the Xn setup request message to the other gNB. After receiving the Xn setup request message, the other-gNB learns about the authorization of the WAB node based on the information #3 indicating the authorization status of the WAB node carried in the Xn setup request message.

[0395] In addition, it should be noted that in this implementation, since the initiator of the Xn interface establishment request between the two access network nodes can be either party, if the other-gNB is the initiator, then in this implementation, the other-gNB determines that it can actively initiate the Xn interface establishment request with the WAB-gNB based on the second indication information in the above step S1101; alternatively, after receiving the Xn establishment request message sent by the other-gNB to the WAB-gNB, the donor-gNB may forward the Xn establishment request message to the WAB-gNB based on the authorization status of the WAB node. The donor-gNB may also send the above-mentioned information #3 to the WAB-gNB. This will not be repeated here.

[0396] Furthermore, the other-gNB learns that an Xn interface can be established with the WAB-gNB. Thus, in the case shown in method 2.1.1, after receiving the second request message, the other-gNB agrees to establish the Xn interface. The method flow shown in FIG11 further includes:

[0397] S1107: The other-gNB sends a second response message to the WAB node. In response, the WAB node receives the second response message from the other-gNB.

[0398] Specifically, the second response message indicates that the Xn interface is agreed to be established. For example, the donor-gNB replies with an Xn setup response message to the WAB node.

[0399] Optionally, the timing of establishing the first communication interface between the WAB-gNB and the first network device (e.g., CN of UE, other-gNB, or donor-gNB) is not limited in this embodiment. It may be that the interface establishment request is initiated immediately after receiving the updated authorization status or indication information, or the interface establishment request is re-initiated only after receiving the update information and determining that the interface establishment failed due to the unauthorized WAB node.

[0400] Mode 2.1.2 of enabling establishment of the first communication interface on the network side: The CN of WAB-MT determines to establish or activate a first PDU session for the WAB-MT to carry data of the first communication interface.

[0401] In the case shown in method 2.1.1, the method flow shown in Figure 11 includes the following steps:

[0402] S1111, the CN of WAB-MT determines to establish or activate a first PDU session.

[0403] Specifically, the CN of the WAB-MT determines to establish or activate a first PDU session for the WAB-MT to carry data of the first communication interface based on the updated authorization status of the WAB node.

[0404] Optionally, the CN of WAB-MT may determine to establish or activate the first PDU session based on a change in the authorization status of the WAB node.

[0405] Optionally, the CN of WAB-MT may determine to establish or activate the first PDU session based on the received NAS message of the PDU session establishment / activation request of the WAB node. For example, the CN of WAB-MT determines to establish or activate the first PDU session after receiving the PDU session establishment request message or service request message sent by the WAB node.

[0406] In step S1112, the CN of WAB-MT sends a request message #1 to the donor-gNB. In response, the donor-gNB receives the request message #1 from the CN of WAB-MT.

[0407] Specifically, request message #1 is used to request the RAN to establish a PDU session resource. For example, the CN of the WAB-MT may send a PDU session resource setup request message to the donor-gNB to request the RAN to establish a first PDU session resource. That is, request message #1 may be a PDU session resource setup request message.

[0408] Furthermore, after receiving the request message #1, the donor-gNB may instruct the establishment of a DRB associated with the first PDU session. The method flow shown in FIG11 further includes:

[0409] In step S1113, the donor-gNB sends message #1 to the WAB-MT. In response, the WAB-MT receives message #1 from the donor-gNB.

[0410] Specifically, message #1 is used to indicate the establishment of a DRB associated with the first PDU session. For example, the donor-gNB may send an RRC reconfiguration message to the WAB-MT to indicate the establishment of a DRB associated with the PDU session.

[0411] Furthermore, in the case shown in method 2.1.2, the process for establishing the first communication interface can refer to the description of establishing the NG interface, the first Xn interface and the second Xn interface in method 2.2.1 above, which will not be repeated here.

[0412] Mode 2.2 of enabling establishment of the first communication interface on the network side: the WAB node is in the RRC idle state or the RRC inactive state.

[0413] In the case shown in method 2.2, the method flow shown in FIG11 includes the following steps:

[0414] S1121, paging WAB-MT.

[0415] As a possible implementation, for a WAB node in an RRC idle state or an RRC inactive state, the CN of WAB-MT serving the WAB-MT may page the WAB-MT in the RRC idle state through a core network paging (CN paging) process.

[0416] As another possible implementation, the donor-gNB can page the WAB-MT in the RRC inactive state through the access network paging (RAN paging) process, so that the WAB-MT can enter the RRC connected state.

[0417] Optionally, for a WAB node in the RRC idle state, the CN of WAB-MT may include the authorization status of the WAB node in a CN paging message to inform the donor-gNB. For example, the CN paging message includes fourth indication information, which is used to indicate that the WAB node is updated from an unauthorized node to an authorized node.

[0418] Furthermore, the donor-gNB can also inform the WAB node of the WAB node authorization status. For example, the CN of WAB-MT first indicates the WAB node authorization status to the donor-gNB through a CN paging message, and the donor-gNB then indicates the WAB node authorization status to the WAB-MT through a control channel.

[0419] Optionally, for a WAB-MT in the RRC inactive state, the CN of the WAB-MT may inform the donor-gNB of the WAB node authorization status via a downlink NGAP message (e.g., a UE context modification request message). Furthermore, the donor-gNB may also inform the WAB-MT of the WAB node authorization status, for example, via a RAN paging message.

[0420] S1122: WAB-MT returns to the connected state.

[0421] Exemplarily, the WAB-MT sends an uplink NAS message to the CN of the WAB-MT to restore to the connected state.

[0422] For example, a registration update may be requested via a service request message. If the updated authorization status of the WAB node is not carried in the above step S1121, the CN of WAB-MT may optionally indicate the status to the WAB-MT via a replied downlink NAS message.

[0423] For example, if the WAB-MT has learned the updated authorization status through the paging process in step S1121, then the first uplink NAS message of the WAB-MT may be a NAS message requesting to establish a PDU session for carrying the NG interface and / or Xn interface.

[0424] As an example and not a limitation, if the WAB-MT obtains the updated authorization status of the WAB node through the above step S1122, the method flow shown in FIG11 further includes:

[0425] S1123: A first PDU session is established between the WAB node and the CN of WAB-MT.

[0426] Exemplarily, the WAB node requests the CN of WAB-MT to establish a first PDU session for carrying the NG interface and / or the Xn interface through an existing PDU session establishment process.

[0427] Optionally, after the first PDU session is successfully established, the establishment process of the first communication interface can refer to the description of the establishment of the NG interface, the first Xn interface and the second Xn interface in the above method 2.2.1, which will not be repeated here.

[0428] The communication method shown in Figure 11 enables the WAB node to establish an NG interface and / or Xn interface between the WAB-gNB and the UE CN and / or neighboring station when the WAB node changes from an unauthorized state to an authorized state, so as to follow the working logic of the WAB node in the authorized state and improve the user experience of the UE.

[0429] Figure 12 is a schematic flow chart of another communication method provided by the present application. The communication method shown in Figure 12 mainly illustrates how the network side manages the established first communication interface when the WAB node changes from an authorized state to an unauthorized state. In this embodiment, it is assumed that the WAB node is currently determined to be in an authorized state by the CN of WAB-MT, wherein the method for obtaining the authorized state can refer to the description of steps S1010 and S1020 in the communication method shown in Figure 10, which will not be repeated here. In addition, it is assumed that there is a first PDU session (dedicated / general PDU session) between the WAB-MT and the CN of WAB-MT for carrying data of the first communication interface, and a first communication interface has been established between the WAB-gNB and the first network device.

[0430] Specifically, the communication method includes the following steps:

[0431] S1210, the CN of WAB-MT determines that the WAB node becomes unauthorized.

[0432] S1220, the CN of WAB-MT sends a downlink NAS message to the WAB-MT.

[0433] Specifically, the CN of the WAB-MT may inform the WAB-MT of the updated unauthorized status of the WAB node through a downlink NAS message.

[0434] Optionally, the updated unauthorized state of the WAB node may also be notified to the donor-gNB through the first message #3. For example, the CN of WAB-MT sends a first message #3 to the donor-gNB. The first message #3 includes first indication information, and the first indication information indicates the updated unauthorized state of the WAB node. For example, the CN of WAB-MT indicates the updated unauthorized state to the donor-gNB through a downlink NGAP message (such as a UE context modification request message).

[0435] S1230: The WAB-gNB performs handover.

[0436] Specifically, when the WAB-gNB learns that the WAB node has changed to an unauthorized state, it must switch the connected UE connected to the WAB-gNB to another cell not managed by the WAB-gNB, for example, to a cell managed by the donor-gNB.

[0437] For example, when the WAB-gNB changes from an authorized state to an unauthorized state, the network side can manage the established first communication interface in the following two ways:

[0438] Method 3.1 of managing the established first communication interface on the network side: removing or suspending the established first communication interface.

[0439] In the case shown in method 3.1, the method flow shown in FIG12 includes the following steps:

[0440] S1201: A first network device receives first indication information.

[0441] Please refer to the description of step S910 in the communication method shown in FIG9 , which will not be repeated here.

[0442] It should be noted that in this embodiment, if the first network device (e.g., donor-gNB, other-gNB, or CN of WAB-MT) proactively initiates the removal or suspension of the established first communication interface, the first network device needs to be informed through the first indication information that the WAB node has become unauthorized. If the WAB-gNB proactively removes or suspends the established first communication interface, then it is not a problem if the first network device is unaware that the WAB node has become unauthorized. In other words, step S1201 is optional.

[0443] For example, for the NG interface, in the case shown in method 3.1, the following steps are further included:

[0444] S1202: WAB-gNB sends request message #2 to CN of UE.

[0445] Specifically, the request message #2 is used to request the release or suspension of the NG interface, and the request message #2 may be an NG release or suspension request message. Exemplarily, since the first PDU session has been established, the WAB node may send the request message #2 to the CN of UE through the first PDU session.

[0446] For example, based on the implementation method #1 and / or implementation method #2 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concepts above, a new NGAP message can be introduced to request the release or suspension (which can also be understood as deactivation) of the NG interface. For example, the newly added NGAP message can be an NGAP removal request message or an NGAP suspend request message, etc. In this embodiment, the name of the message indicating the NG release or suspension request is not limited, and it is sufficient to implement the function of indicating the NG release or suspension.

[0447] The WAB-gNB can request the CN of UE to release or suspend the NG interface through the NGAP message. The CN of UE confirms the release or suspension and then replies to the WAB-gNB.

[0448] S1203: The CN of UE sends a first response message to the WAB-gNB. Correspondingly, the WAB-gNB receives the first response message from the CN of UE.

[0449] Specifically, the first response message indicates the release or suspension of the NG interface. For example, the CN of UE feeds back an instruction to remove the NG interface to the WAB-gNB using an NG Removal Response message. For another example, the CN of UE feeds back an instruction to suspend the NG interface to the WAB-gNB using an NG Suspend Response message.

[0450] In addition, it should be noted that the CN of UE can request the WAB-gNB to release or suspend the NG interface based on the first indication information. The process of the CN of UE requesting the WAB-gNB to release or suspend the NG interface is similar to the above-mentioned WAB-gNB requesting the CN of UE to release or suspend the NG interface based on the first indication information, except that the responding end and the initiating end are opposite.

[0451] For example, for the first Xn interface, in the case shown in method 3.1, the following steps are further included:

[0452] S1204: The WAB-gNB sends a request message #2 to the donor-gNB.

[0453] Specifically, request message #3 is used to request the release or suspension of the Xn interface, and request message #2 may be an Xn release or suspension request message. For example, since the first PDU session has been established, the WAB-gNB may send request message #2 via the DRB or SRB donor-gNB used to carry the first PDU session (e.g., a general / dedicated PDU session) of the Xn interface.

[0454] For example, based on the implementation method #1 and / or implementation method #2 of the backhaul process of the NG and / or Xn interface of the WAB-gNB in ​​the basic concepts above, a new XnAP message can be introduced to request the release or suspension (which can also be understood as deactivation) of the Xn interface. For example, the newly added XnAP message can be an XnAP removal request message or an XnAP suspend request message, etc. In this embodiment, the name of the message indicating the Xn release or suspension request is not limited, and it is sufficient to implement the function of indicating the Xn release or suspension.

[0455] The WAB-gNB can use this XnAP message to request the donor-gNB to release or suspend the NG interface. The donor-gNB confirms the release or suspension and then responds to the WAB-gNB.

[0456] S1205: The donor-gNB sends a first response message to the WAB-gNB. In response, the WAB-gNB receives the first response message from the donor-gNB.

[0457] Specifically, the first response message indicates the release or suspension of the Xn interface. For example, the donor-gNB feeds back an instruction to remove the Xn interface to the WAB-gNB using an Xn Removal Response message. For another example, the donor-gNB feeds back an instruction to suspend the Xn interface to the WAB-gNB using an Xn Suspend Response message.

[0458] In addition, it should be noted that the donor-gNB can request the WAB-gNB to release or suspend the Xn interface based on the first indication information. The process of the donor-gNB requesting the WAB-gNB to release or suspend the Xn interface is similar to the above-mentioned WAB-gNB requesting the donor-gNB to release or suspend the Xn interface based on the first indication information, except that the responding end and the initiating end are opposite.

[0459] For example, for the second Xn interface, in the case shown in method 3.1, the following possibilities are also included:

[0460] Possibility 4: The WAB-gNB sends a request message #2 to the other-gNB requesting the release or suspension of the second Xn interface. The other-gNB determines to release or suspend the second Xn interface based on the unauthorized status of the WAB and feeds back a first response message indicating the release or suspension of the second Xn interface.

[0461] For example, in the case shown in Possible 4, the method flow shown in FIG12 includes the following steps:

[0462] S1206: WAB-gNB sends request message #2 to other-gNB.

[0463] Specifically, request message #2 is used to request the release or suspension of the Xn interface. Request message #2 may be an Xn release or suspension request message. For example, since the first PDU session has been established, the WAB node may send request message #2 to the other-gNB via the first PDU session.

[0464] Request message #2 may be a newly introduced XnAP message, which is used to request the release or suspension (which may also be understood as deactivation) of the Xn interface. For example, the newly added XnAP message may be an XnAP removal request message or an XnAP suspend request message. In this embodiment, there is no limitation on the name of the message indicating the Xn release or suspension request, as long as it can implement the function of indicating the Xn release or suspension.

[0465] The WAB-gNB can use this XnAP message to request other-gNB to release or suspend the NG interface. After other-gNB confirms the release or suspension, it responds to the WAB-gNB.

[0466] For example, the manner in which the WAB-gNB sends the request message #2 to the other-gNB may refer to the description of the WAB-gNB sending the first request message to the other-gNB in ​​step S1007 of method 1.1 in Figure 10 above. For example, the WAB-gNB sends the request message #2 to the other-gNB via the CN of WAB-MT, and the CN of WAB-MT carries the information #2 indicating that the WAB node is in the unauthorized state when forwarding the request message #2 to the other-gNB. For another example, the WAB-gNB sends the request message #2 to the other-gNB via the donor-gNB, and the donor-gNB carries the information #2 indicating that the WAB node is in the unauthorized state when forwarding the request message #2 to the other-gNB. This description is not repeated here.

[0467] S1207: The other-gNB sends a first response message to the WAB-gNB. Correspondingly, the WAB-gNB receives the first response message from the other-gNB.

[0468] Specifically, the first response message indicates the release or suspension of the Xn interface. For example, the other-gNB feeds back the Xn interface removal instruction to the WAB-gNB via an Xn Removal Response message. For another example, the other-gNB feeds back the Xn interface suspension instruction to the WAB-gNB via an Xn Suspend Response message. Optionally, the first response message may carry a first cause value, which indicates the reason for the Xn interface release or suspension. For example, the first cause value is WAB-node is not authorized.

[0469] Possibility 5: The WAB-gNB sends a request message #2 to the other-gNB through the CN of WAB-MT requesting the release or suspension of the second Xn interface. The CN of WAB-MT determines not to forward the request message #2 to the other-gNB based on the unauthorized status of the WAB.

[0470] For example, in the case shown in possible five, the method flow shown in FIG12 includes the following steps:

[0471] S1208: The WAB-gNB sends a request message #2 to the CN of WAB-MT. In response, the CN of WAB-MT receives the request message #2 from the WAB-gNB.

[0472] S1209: The CN of WAB-MT determines not to forward the request message #2 to other-gNB.

[0473] For the description of possibility five, please refer to the description of possibility two in method 1.1 in Figure 10 above. The difference is that the first request message in the above possibility two is replaced by request message #2 in this embodiment, which will not be repeated here.

[0474] Possibility 6: The WAB-gNB sends a request message #2 to the other-gNB through the donor-gNB requesting the release or suspension of the second Xn interface. The donor-gNB determines not to forward the request message #2 to the other-gNB based on the unauthorized status of the WAB.

[0475] For example, in the case shown in possible six, the method flow shown in FIG12 includes the following steps:

[0476] S1291: The WAB-gNB sends a request message #2 to the donor-gNB. In response, the donor-gNB receives the request message #2 from the WAB-gNB.

[0477] S1292: The donor-gNB determines not to forward the request message #2 to the other-gNB.

[0478] For the description of possibility six, please refer to the description of possibility three in method 1.1 in Figure 10 above. The difference is that the first request message in the above possibility three is replaced by request message #2 in this embodiment, which will not be repeated here.

[0479] In the scenario shown in Possible 6, after the donor-gNB determines not to forward Request Message #2 sent by the WAB-gNB to the other-gNB, it may reply to the WAB node with a first response message, indicating the release or suspension of the Xn interface. For example, the donor-gNB may feedback the Xn interface release or suspension instruction to the WAB-gNB via an Xn Removal Response message or an Xn Suspend Response message.

[0480] Optionally, the first response message may carry a first cause value, which indicates the reason for the failure to establish the Xn interface, for example, the first cause value is WAB-node is not authorized.

[0481] In addition, it should be noted that since the initiator of the Xn interface release or suspension request between the two access network nodes can be either party, if the other-gNB is the initiator, then the other-gNB actively initiates the Xn interface release or suspension request with the WAB-gNB based on the first indication information in the above step S1002; or

[0482] In the case shown in the fifth possibility, after receiving the Xn release or suspend request message sent by other-gNB to WAB-gNB, the CN of WAB-MT does not forward it to WAB-gNB based on the unauthorized status of the WAB node; or

[0483] In the sixth possible scenario, after receiving an Xn Release or Suspend Request message sent by the other-gNB to the WAB-gNB, the donor-gNB may not forward the message to the WAB-gNB due to the unauthorized status of the WAB node, and may instead reply with an Xn Removal Response message or an Xn Suspend Response message to the other-gNB. Optionally, the Xn Removal Response message or the Xn Suspend Response message may carry a cause value indicating the reason for releasing or suspending the Xn interface, for example, the first cause value.

[0484] In this implementation, upon learning that the WAB node is in an unauthorized state, the donor-gNB may no longer help the WAB-gNB forward Xn data to the other-gNB, or no longer help the other-gNB forward Xn data to the WAB-gNB, and release or suspend the Xn connection between the donor-gNB and the WAB-gNB.

[0485] Furthermore, in this implementation, after the first communication interface is successfully released or suspended, the first PDU session for data of the first communication interface established by WAB-MT can also be released or deactivated, or even all PDU sessions established by WAB-MT can be released or deactivated.

[0486] Exemplarily, the party requesting to release or deactivate the relevant PDU session can be a WAB-MT, a donor-gNB, or a CN of WAB-MT. The specific release or deactivation process can refer to the description of the release or deactivation process of the PDU session in the current related technology. It is not limited here. This embodiment mainly illustrates that the triggering condition for releasing or deactivating the PDU session is that the WAB node becomes unauthorized or the established first communication interface is released or suspended.

[0487] Optionally, after removing or suspending the established first communication interface, the WAB node may be instructed to enter an idle state, an inactive state, or a deregistered state through indication information #2. In the case shown in method 3.1, the following may also be included:

[0488] S1293, the CN of WAB-MT sends second information to the WAB node. Correspondingly, the WAB node receives the second information indicating the second information from the CN of WAB-MT.

[0489] The description of step S1293 can refer to the description of step S1031 in the communication method shown in Figure 10, and will not be repeated here.

[0490] The network side management has established the first communication interface mode 3.2: the CN of WAB-MT determines to release or deactivate the first PDU session.

[0491] S1211, the CN of WAB-MT determines to release or deactivate the first PDU session.

[0492] In this embodiment, the CN of WAB-MT may determine to release or deactivate the established first PDU session based on the unauthorized state of the WAB node.

[0493] As a possible implementation, the CN of WAB-MT may determine to release or deactivate the first PDU session based on the request of the WAB-MT. For example, in this implementation, the WAB-MT initiates a PDU session release request to the CN of WAB-MT based on the updated unauthorized status, requesting the release of the PDU session used to carry data of the first communication interface, or all established PDU sessions. The request message may be carried in an uplink NAS message, such as a PDU session release request message (5G session management message).

[0494] As another possible implementation, the CN of WAB-MT may determine to release or deactivate the first PDU session based on a request from the donor-gNB. For example, in this implementation, the donor-gNB initiates a PDU session release request to the CN of WAB-MT via an NGAP message, such as a PDU session resource notify message, based on the updated unauthorized status.

[0495] Exemplarily, the CN of WAB-MT determines to release or deactivate the PDU session used to carry data of the first communication interface, or the CN of WAB-MT determines to release or deactivate all established PDU sessions of the WAB-MT.

[0496] S1212: The CN of WAB-MT sends a request message #3 to the donor-gNB. In response, the donor-gNB receives the request message #3 from the CN of WAB-MT.

[0497] Specifically, request message #3 is used to request the RAN to release PDU session resources. For example, the CN of the WAB-MT can send a PDU session resource release message to the donor-gNB, instructing the donor-gNB to release the established PDU session resources.

[0498] Furthermore, after receiving the request message #3, the donor-gNB may instruct the removal of the DRB associated with the PDU session. The method flow shown in FIG12 further includes:

[0499] In step S1213, the donor-gNB sends message #2 to the WAB-MT. In response, the WAB-MT receives message #2 from the donor-gNB.

[0500] Specifically, message #2 is used to instruct the WAB-MT to remove the DRB associated with the first PDU session. For example, the donor-gNB may send an RRC reconfiguration message to the WAB-MT to instruct it to remove the first PDU session association.

[0501] Optionally, before determining to release or deactivate the first PDU session, the first communication interface established between the WAB-gNB and the first network device can be removed first through the process shown in steps 1201 to S1207 in the above method 3.1. In addition, if the CN of WAB-MT determines to release or deactivate the first PDU session based on the request of the WAB-MT, then the first communication interface removal process can be executed before the WAB-MT requests to release or deactivate the first PDU session.

[0502] Optionally, after releasing or deactivating the first PDU session, the second information may be used to instruct the WAB node to enter an idle state, instruct the WAB node to enter an inactive state, or instruct the WAB node to deregister. In the case shown in method 3.2, the following may also be included:

[0503] S1214, the CN of WAB-MT sends the second information to the WAB node. Correspondingly, the WAB node receives the second information from the CN of WAB-MT.

[0504] The description of step S1214 may refer to the description of step S1031 in the communication method shown in FIG10 , and will not be repeated here.

[0505] The network side management has established the first communication interface mode 3.3: the CN of WAB-MT instructs the WAB node to enter the idle state, instructs the WAB node to enter the inactive state, or instructs the WAB node to register.

[0506] In the case shown in method 3.3, the method flow shown in FIG12 includes the following steps:

[0507] S1231, the CN of WAB-MT sends second information to the WAB node, and correspondingly, the WAB node receives the second information from the CN of WAB-MT.

[0508] The description of step S1231 can refer to the description of step S1031 in the communication method shown in FIG10 , and will not be repeated here.

[0509] The communication method shown in Figure 12 allows the first communication interface established between the WAB-gNB and the first network device to be removed or suspended when the WAB node transitions from an authorized state to an unauthorized state, thereby adhering to the WAB node's operating logic in the unauthorized state and reducing unnecessary signaling overhead. Furthermore, before removing the first communication interface, the WAB-gNB can also handover connected UEs to other cells to ensure service continuity for the UEs.

[0510] As described above, at least one of the WAB node, donor-gNB, or other-gNB involved in this implementation example may be an ORAN architecture. The following briefly describes the application of the communication methods shown in Figures 9 to 12 above under the ORAN architecture:

[0511] In the O-RAN architecture, the RIC can directly control both the gNB-CU and the gNB-DU. Therefore, the "WAB-gNB" in the communication method steps shown in Figures 9 to 12 needs to be expanded to "WAB-CU" and "WAB-DU", "donor-gNB" needs to be expanded to "donor-gNB-CU" and "donor-gNB-DU", and "other-gNB" needs to be expanded to "other-gNB-CU" and "other-gNB-DU".

[0512] As a possible implementation, the O-RAN architecture can be extended to the communication methods shown in Figures 9 to 12, involving how the other-gNB obtains the indication information, such as obtaining the first indication information and / or the second indication information. In addition to the other-gNB obtaining the first indication information and / or the second indication information from the donor-gNB or the CN of the WAB-MT, the WAB-gNB or the donor may first indicate the first indication information and / or the second indication information to the RIC via an E2 interface message, and then the RIC may indicate the first indication information and / or the second indication information to the other-gNB via an E2 interface message.

[0513] As another possible implementation, the O-RAN architecture can be extended to the communication method shown in FIG9 or FIG12. Similar to the determination by the donor-gNB of whether to forward Xn data based on the unauthorized status of the WAB node, the WAB-gNB or the donor-gNB may first indicate the latest authorization status of the WAB node to the RIC through an E2 interface message, and then the RIC determines whether to forward the Xn data.

[0514] For example, in the case shown in method 1.1 in Figure 10, the RIC will not continue to forward the Xn setup request message sent by the WAB-gNB or other-gNB to the peer end based on the unauthorized state of the WAB, and will reply to the sender with an indication of the failure to forward the Xn message. Optionally, the reason for the failure can also be provided as the WAB node is unauthorized.

[0515] For example, in the case shown in method 1.1 in Figure 10, after receiving the Xn setup request message sent by the WAB-gNB or other-gNB based on the unauthorized state of the WAB, the RIC can forward the Xn setup request message to the peer end and send information #2 to the peer end to indicate that the WAB node is unauthorized.

[0516] For another example, in the case shown in method 2.1 in Figure 11, the RIC continues to forward the Xn setup request message sent by the WAB-gNB or other-gNB to the peer end based on the authorization status of the WAB, and responds to the sender with an indication of successful forwarding of the Xn message.

[0517] For another example, in the case shown in method 2.1 in Figure 11, after receiving the Xn setup request message sent by the WAB-gNB or other-gNB based on the authorization status of the WAB, the RIC can forward the Xn setup request message to the peer end and send information #3 to the peer end to indicate the WAB node authorization.

[0518] For another example, in the case shown in method 3.1 in Figure 12, the RIC will no longer help the WAB-gNB / other-gNB forward Xn data to the other end based on the unauthorized state of the WAB, and will instruct the donor-gNB or WAB-gNB to release or suspend the Xn connection between them.

[0519] For another example, in the case shown in method 3.1 in Figure 12, the RIC continues to forward the request message #2 (e.g., XnAP removal request message and / or XnAP suspend request message) sent by the WAB-gNB or other-gNB to the peer end based on the unauthorized status of the WAB, and will reply to the sender with an indication of the success of forwarding the request message #2.

[0520] For another example, in the case shown in method 3.1 in Figure 12, the RIC will not continue to forward the request message #2 (such as the XnAP removal request message and / or the XnAP suspend request message) sent by the WAB-gNB or other-gNB to the peer end based on the unauthorized status of the WAB, and will reply to the sender with a response message indicating the release or suspension of the Xn interface. Optionally, the reason for the release or suspension can also be provided as the WAB node is unauthorized.

[0521] For another example, in the case shown in method 3.1 in Figure 12, after receiving the request message #2 (e.g., XnAP removal request message and / or XnAP suspend request message) sent by the WAB-gNB or other-gNB based on the unauthorized status of the WAB, the RIC can forward the request message #2 to the peer end and send information #2 to the peer end to indicate that the WAB node is unauthorized.

[0522] In the O-RAN architecture, the E2 interface relay ensures that the other-gNB receives the indication information from the WAB-gNB or donor-gNB, or the RIC can obtain the latest authorization status of the WAB node, thereby performing corresponding Xn interface management based on the latest authorization status of the WAB node.

[0523] The communication methods illustrated in Figures 9 through 12 above are primarily illustrated using the example of the CN of WAB-MT authenticating the WAB-MT. As previously mentioned, if another authentication node authenticates the WAB-gNB, the authentication result can be forwarded via the CN of WAB-MT. This means that in this application, WAB-MT authentication and WAB-gNB authentication can be performed separately. Separate authorization of the WAB-MT and WAB-gNB, coupled with correlation between their authorization states, can avoid situations where one of the WAB-MT and WAB-gNB is unauthorized while the other is authorized and operational, thereby reducing unnecessary network resource waste and overhead; alternatively, it can improve the flexibility of WAB node implementation.

[0524] Optionally, in addition to the above-mentioned CN of UE and / or donor-gNB, the authentication node of the WAB-gNB can also be a security gateway (SeGW) or other node or device capable of authenticating the WAB-gNB, which is not repeated here.

[0525] For example, when the WAB-MT and WAB-gNB are authenticated separately, the following implementations are included but are not limited to:

[0526] 1) As a possible implementation, the WAB-gNB is authenticated as being in an unauthorized state by the WAB-gNB's authentication node (e.g., at least one of the CN of the UE, the donor-gNB, or the SeGW). The WAB-gNB's authentication node may notify other nodes other than the WAB-gNB's authentication node of the unauthorized state of the WAB-gNB.

[0527] For example, when the authentication node of the WAB-gNB is the SeGW, the SeGW may send the unauthorized status of the WAB-gNB to at least one of the CN of WAB-MT, the CN of UE, the WAB-gNB, the donor-gNB, or the other-gNB, so that the other nodes can manage the WAB-gNB interface or the authentication of the WAB-MT. For specific management methods of the WAB-gNB interface or the authentication of the WAB-MT, reference may be made to the description of WAB-gNB interface management in the communication methods shown in Figures 9 to 12 above. For example, by indicating the unauthorized status of the WAB-gNB, the other nodes may be indirectly instructed not to establish, release, or suspend an interface; or, for example, the other nodes may be directly instructed not to establish, release, or suspend an interface. This description is not repeated here.

[0528] In this implementation, the impact of the unauthorized status of the WAB-gNB on the authentication status of the WAB-MT includes but is not limited to:

[0529] (1.1) After receiving the unauthorized status from the WAB-gNB, the CN of WAB-MT may not authenticate the WAB-MT, or the WAB-gNB's authentication node (e.g., CN of UE, donor-gNB, or SeGW) may instruct the CN of WAB-MT not to authenticate the WAB-MT based on the unauthorized status.

[0530] (1.2) If the WAB-MT has been authorized but has not yet established a PDU session, the CN of the WAB-MT may deauthorize the WAB-MT based on the unauthorized state of the WAB-gNB (or based on the indication information sent by the WAB-gNB authentication node based on the unauthorized state of the WAB-gNB), that is, change the authorized state of the WAB-MT to the unauthorized state, and / or deregister the WAB-MT; or

[0531] The WAB-MT determines to initiate a deauthorization and / or deregistration request based on the unauthorized status of the WAB-gNB (or based on an indication sent by the WAB-gNB's authentication node regarding the unauthorized status of the WAB-gNB); or

[0532] The WAB-MT instructs the CN of WAB-MT to deauthorize and / or deregister the WAB-MT. For example, the WAB-MT sends the unauthorized status of the WAB-gNB received from the authentication node of the WAB-gNB to the CN of WAB-MT, instructing the CN of WAB-MT to deauthorize and / or deregister the WAB-MT. For another example, the WAB-MT instructs the CN of WAB-MT to deauthorize and / or deregister the WAB-MT based on the unauthorized status indication of the WAB-gNB received from the authentication node of the WAB-gNB.

[0533] (1.3) If the WAB-MT has been authorized and has established a PDU session, the established PDU session may be released and / or deactivated, and / or the WAB-MT may be deauthorized and / or deregistered.

[0534] For example, the description of de-authorizing and / or de-registering the WAB-MT may refer to the description of de-authorizing and / or de-registering the WAB-MT in (1.2) above, which will not be repeated here.

[0535] Optionally, the CN of the WAB-MT releases and / or deactivates the PDU session based on the unauthorized state of the WAB-gNB (or based on an indication sent by the WAB-gNB authentication node based on the unauthorized state of the WAB-gNB); or

[0536] The WAB-MT determines to initiate a request for PDU session release and / or deactivation based on the unauthorized status of the WAB-gNB (or based on an indication sent by the WAB-gNB authentication node based on the unauthorized status of the WAB-gNB); or

[0537] The WAB-MT instructs the CN of WAB-MT to release and / or deactivate the PDU session. For example, the WAB-MT sends the unauthorized status of the WAB-gNB received from the authentication node of the WAB-gNB to the CN of WAB-MT, instructing the CN of WAB-MT to release and / or deactivate the PDU session. For another example, the WAB-MT instructs the CN of WAB-MT to release and / or deactivate the PDU session based on the unauthorized status indication of the WAB-gNB received from the authentication node of the WAB-gNB.

[0538] 2) As another possible implementation, the WAB-MT is authenticated as being in an unauthorized state by its authentication node (e.g., CN of WAB-MT). The WAB-MT authentication node may notify other nodes other than the WAB-MT authentication node of the unauthorized state of the WAB-MT.

[0539] For example, the CN of the WAB-MT can send the unauthorized status of the WAB-MT to at least one of the CN of the UE, the SeGW, the WAB-gNB, the donor-gNB, or the other-gNB, so that the other nodes can manage the WAB-gNB interface or the WAB-gNB authentication. For specific WAB-gNB interface management methods, refer to the description of interface management in the communication methods shown in Figures 9 to 12 above. For example, by indicating the unauthorized status of the WAB-MT, indirectly instructing other nodes to determine not to establish, release, or suspend an interface; or directly instructing other nodes not to establish, release, or suspend an interface. This description is not repeated here.

[0540] In this implementation, the impact of the unauthorized status of the WAB-MT on the authentication status of the WAB-gNB includes but is not limited to:

[0541] (2.1) Upon receiving the unauthorized status of the WAB-MT, the WAB-gNB authentication node (e.g., at least one of the CN of UE, donor-gNB, or SeGW) will not authenticate the WAB-gNB. Alternatively, the CN of WAB-MT may instruct the WAB-gNB authentication node not to authenticate the WAB-gNB based on the unauthorized status.

[0542] (2.2) If the WAB-gNB has been authorized but the WAB-gNB has not yet established the N2 and / or Xn interface, the WAB-gNB authentication node may deauthorize the WAB-gNB based on the unauthorized status of the WAB-MT (or based on the indication information sent by the CN of the WAB-MT regarding the unauthorized status of the WAB-MT), and the WAB-gNB will not initiate an interface establishment request or reject the peer's request to establish an interface; or

[0543] After the WAB-gNB authentication node deauthorizes the WAB-gNB, it notifies the WAB-gNB's peer, which then manages the interface to be established (e.g., does not initiate an interface establishment request or rejects the WAB-gNB's request to establish an interface).

[0544] (2.3) If the WAB-gNB has been authorized and the WAB-gNB has an established N2 and / or Xn interface, at least one of the following operations may be performed:

[0545] Handover of the UE connected to the WAB-gNB to another gNB, release of the N2 and / or Xn interface, suspension of the N2 and / or Xn interface, or deauthorization of the WAB-gNB, etc.

[0546] For example, the description of deauthorizing WAB-gNB can refer to the description of deauthorizing WAB-gNB in ​​(2.2) above, which will not be repeated here.

[0547] Optionally, the WAB-gNB initiates an interface release and / or suspension request based on the unauthorized state of the WAB-MT (or based on the indication information sent by the CN of WAB-MT according to the unauthorized state of the WAB-MT); or

[0548] The WAB-gNB allows the interface release and / or suspension request initiated by the peer (e.g., UE CN or neighboring station) based on the unauthorized status of the WAB-MT (or based on the indication information sent by the CN of the WAB-MT based on the unauthorized status of the WAB-MT); or

[0549] The peer end (e.g., UE CN or neighboring station) proactively initiates an interface release and / or suspension request based on the unauthorized state of the WAB-MT (or based on the indication information sent by the CN of WAB-MT based on the unauthorized state of the WAB-MT); or

[0550] The peer end (e.g., UE CN or neighboring station) allows the interface release and / or suspension request initiated by the WAB-gNB based on the unauthorized state of the WAB-MT (or based on the indication information sent by the CN of WAB-MT according to the unauthorized state of the WAB-MT).

[0551] 3) As another possible implementation, the authentication result of the WAB-MT and the authentication result of the WAB-gNB do not affect each other.

[0552] For example, if the WAB-MT is in an unauthorized state, even if the WAB-gNB is in an authorized state, the N2 and / or Xn interfaces of the WAB-gNB will cause the PDU session to be released and / or deactivated, or the PDU session cannot be established, because the WAB-MT is unauthorized.

[0553] For example, if the WAB-gNB is in an unauthorized state and the WAB-MT is in an authorized state, the function of the WAB-MT will not be affected, the PDU session can still be established or user plane data can be transmitted, but the N2 and / or Xn interface of the WAB-gNB cannot be established.

[0554] In summary, when the WAB-MT and WAB-gNB are authenticated separately, if the WAB-gNB is unauthorized, this may result in at least one of the following situations: WAB-MT deactivation, release, deauthorization, or deregistration; if the WAB-MT is unauthorized, this may result in at least one of the following situations: WAB-gNB handover of UE, release of NG and / or Xn interface, suspension of NG and / or Xn interface, or deauthorization. In other words, if the WAB-gNB and / or WAB-MT are unauthorized, both the WAB-gNB and WAB-MT are in an unauthorized state or are not operational.

[0555] It should be understood that for WAB-gNB, regardless of whether the WAB-gNB is in an unauthorized state or is not working due to the unauthorized state of WAB-gNB and / or the unauthorized state of WAB-MT, the WAB-gNB should stop working and not serve the UE. In order not to affect the continuity of the UE service, the WAB-gNB should switch the UE connected to the WAB-gNB to other gNBs before stopping working, such as releasing the NG and / or Xn interface, suspending the NG and / or Xn interface, or deauthorizing, etc.

[0556] For WAB-MT, regardless of whether the WAB-MT is in an unauthorized state or is not working due to the unauthorized state of WAB-gNB and / or the unauthorized state of WAB-MT, the PDU session established by WAB-MT should be released and / or deactivated, or WAB-MT should be deauthorized and / or deregistered.

[0557] For example, WAB-MT related operations can be performed after the WAB-gNB stops working to avoid affecting the service continuity of the UE accessing the WAB-gNB. If the CN serving the WAB-MT (e.g., CN of WAB-MT) determines the timing of executing the above-mentioned related operations (e.g., at least one operation such as releasing or deactivating the PDU session established by the WAB-MT, deauthorizing the WAB-MT, or deregistering the WAB-MT), the CN of WAB-MT can determine the timing of executing the related operations in the following manner to avoid affecting the service continuity of the UE accessing the WAB-gNB:

[0558] The WAB-MT sends instruction information #3 to the CN of the WAB-MT.

[0559] Exemplarily, the indication information #3 is used to indicate that the WAB node has completed processing of the unauthorized WAB-gNB. For example, the indication information #3 is used to indicate at least one of the following: the WAB-gNB has handed over the connected UE to another gNB, the established NG and / or Xn interface has been released, the WAB-gNB is in an unauthorized state, etc.

[0560] Exemplarily, the indication information #3 is used to indicate that the WAB-gNB does not serve any UE.

[0561] Optionally, the indication information #3 may be sent by the WAB-MT to the CN of WAB-MT through a NAS message.

[0562] Optionally, the WAB node may first send the indication information #3 to the donor-gNB, which may then send the indication information #3 to the CN of WAB-MT via an NGAP message. For example, the WAB-MT may send the indication information #3 to the donor-gNB via an RRC message, which may then send the indication information #3 to the CN of WAB-MT via an NGAP message. For another example, if the Xn connection still exists, the WAB-gNB may send the indication information #3 to the donor-gNB via an Xn message, which may then send the indication information #3 to the CN of WAB-MT via an NGAP message.

[0563] Optionally, the indication information #3 may be that the WAB-MT directly instructs the CN of WAB-MT to perform relevant operations based on the fact that the WAB node has completed processing of the unauthorized WAB-gNB or the WAB-gNB is not serving any UE, such as instructing the CN of WAB-MT to perform at least one of the following operations:

[0564] Release the PDU session established by WAB-MT, deactivate the PDU session established by WAB-MT, deauthorize WAB-MT, or deregister WAB-MT, etc.

[0565] It should be understood that the above-mentioned sending method of indication information #3 is only an example and does not constitute any limitation on the scope of protection of this application.

[0566] It should be understood that the size of the serial numbers of the above processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0567] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0568] It should also be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for illustrative description (such as the first network device, the second core network device, or the relay node). It should be understood that the embodiments of the present application do not limit the specific form of the device. For example, devices that can achieve the same function in the future are applicable to the embodiments of the present application.

[0569] It can be understood that in the above-mentioned method embodiments, the methods and operations implemented by the device (such as the first network device, the second core network device, or the relay node) can also be implemented by components of the device (such as chips or circuits).

[0570] The communication method provided in the embodiments of the present application is described in detail above in conjunction with Figures 9 to 12. The above communication method is mainly described from the perspective of the interaction between the first network device, the second core network device, and the relay node. It is understood that in order to implement the above functions, the first network device, the second core network device, or the relay node includes the corresponding hardware structure and / or software modules for performing each function.

[0571] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0572] The communication device provided in this application is described in detail below with reference to Figures 13 to 15. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, reference can be made to the method embodiment above. For the sake of brevity, some contents will not be repeated.

[0573] In the embodiment of the present application, the functional modules of the transmitting device or the receiving device can be divided according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module according to each function.

[0574] Figure 13 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application. The device 10 includes a transceiver module 11 and a processing module 12. The transceiver module 11 can implement corresponding communication functions, and the processing module 12 is used to process data. In other words, the transceiver module 11 is used to perform operations related to receiving and sending, and the processing module 12 is used to perform other operations besides receiving and sending. The transceiver module 11 can also be referred to as a communication interface or a communication unit.

[0575] Optionally, the device 10 may further include a storage module 13, which may be used to store instructions and / or data. The processing module 12 may read the instructions and / or data in the storage module so that the device implements the actions of the devices in the aforementioned method embodiments.

[0576] In one design, the apparatus 10 may correspond to the first network device in the above method embodiment, or a component (such as a chip) of the first network device.

[0577] The device 10 can implement the steps or processes corresponding to those executed by the first network device in the above method embodiment, wherein the transceiver module 11 can be used to perform the transceiver-related operations of the first network device in the above method embodiment, and the processing module 12 can be used to perform the processing-related operations of the first network device in the above method embodiment.

[0578] In one possible implementation, the transceiver module 11 is configured to receive first indication information, where the first indication information indicates that the relay node is an unauthorized node and / or indicates that a first communication interface cannot be established. The processing module 12 is configured to determine, based on the first indication information, that the first communication interface cannot be established. The relay node includes a mobile terminal portion and an access network node portion, and the first communication interface is a logical interface between the first network device and the access network node portion.

[0579] When the device 10 is used to execute the method in FIG. 9 , the transceiver module 11 may be used to execute the steps of sending and receiving information in the method, such as steps S910 and S930 ; the processing module 12 may be used to execute the processing steps in the method, such as step S920 .

[0580] When the device 10 is used to execute the method in Figure 10, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1030, S1002, S1003, S1004, S1005, S1006, S1007, S1008, S1009, and S1092; the processing module 12 can be used to execute the processing steps in the method, such as step S1093.

[0581] When the device 10 is used to execute the method in Figure 11, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1120, S1101, S1102, S1103, S1104, S1105, S1106, S1107, S1112, S1113, and S1121; the processing module 12 can be used to execute the processing steps in the method.

[0582] When the device 10 is used to execute the method in Figure 12, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1201, S1202, S1203, S1204, S1205, S1206, S1207, S1212, S1213, and S1291; the processing module 12 can be used to execute the processing steps in the method, such as step S1292.

[0583] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0584] In another design, the apparatus 10 may correspond to the second core network device in the above method embodiment, or a component (such as a chip) of the second core network device.

[0585] The device 10 can implement the steps or processes corresponding to those executed by the second core network device in the above method embodiment, wherein the transceiver module 11 can be used to execute the transceiver-related operations of the second core network device in the above method embodiment, and the processing module 12 can be used to execute the processing-related operations of the second core network device in the above method embodiment.

[0586] In one possible implementation, the processing module 12 is configured to authenticate the relay node and determine that the relay node is an unauthorized node. The transceiver module 11 is configured to send first indication information to the first network device, where the first indication information is used to indicate that the relay node is an unauthorized node and / or to indicate that the first communication interface cannot be established.

[0587] In another possible implementation, the processing module 12 is configured to authenticate the relay node and determine that the relay node is an unauthorized node. The processing module 12 is configured to determine, based on the relay node being an unauthorized node, that a first protocol data unit (PDU) session establishment failure has occurred, and to release or deactivate the established first PDU session.

[0588] In another possible implementation, processing module 12 is configured to authenticate a relay node and determine that the relay node is an unauthorized node. Processing module 12 is configured to, based on the relay node being an unauthorized node, send second information to the relay node, where the second information is configured to indicate at least one of the following: instructing the relay node to enter an RRC idle state, instructing the relay node to enter an inactive state, or instructing the relay node to deregister, wherein the relay node includes a mobile terminal portion and an access network node portion, and the second core network device is a core network device serving the relay node.

[0589] When the device 10 is used to execute the method in FIG. 9 , the transceiver module 11 may be used to execute the steps of sending and receiving information in the method, such as steps S910 and S930 ; and the processing module 12 may be used to execute the processing steps in the method.

[0590] When the device 10 is used to execute the method in Figure 10, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1010, S1030, S1001, S1012, S1013, S1021, S1009 and S1031; the processing module 12 can be used to execute the processing steps in the method, such as steps S1020, S1091 and S1011.

[0591] When the device 10 is used to execute the method in Figure 11, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1102, S1130, S1112, S1121 and S1123; the processing module 12 can be used to execute the processing steps in the method, such as steps S1110 and S1111.

[0592] When the device 10 is used to execute the method in Figure 12, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1220, S1212, S1208, S1293, S1214 and S1231; the processing module 12 can be used to execute the processing steps in the method, such as steps S1210, S1209 and S1211.

[0593] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0594] In yet another design, the apparatus 10 may correspond to the relay node in the above method embodiment, or be a component (such as a chip) of the relay node.

[0595] The device 10 can implement the steps or processes corresponding to those executed by the relay node in the above method embodiment, wherein the transceiver module 11 can be used to perform the transceiver-related operations of the relay node in the above method embodiment, and the processing module 12 can be used to perform the processing-related operations of the relay node in the above method embodiment.

[0596] In one possible implementation, the transceiver module 11 is configured to receive first information indicating that the relay node is an unauthorized node. The processing module 12 is configured to determine, based on the first information, not to initiate a first protocol data unit (PDU) session establishment request, or to determine, based on the first information, not to initiate a first communication interface establishment request.

[0597] In another possible implementation, the transceiver module 11 is configured to receive a paging message including fourth indication information, the fourth indication information being used to indicate that the relay node has been updated from an unauthorized node to an authorized node. The processing module 12 is configured to initiate a first protocol data unit (PDU) session establishment request based on the fourth indication information.

[0598] When the device 10 is used to execute the method in FIG10 , the transceiver module 11 may be used to execute the steps of sending and receiving information in the method, S1010 , S1001 , S1003 , S1004 , S1005 , S1006 , S1007 , S1008 , S1012 , S1013 , S1021 , and S1031 ; such as step S1022 ;

[0599] When the device 10 is used to execute the method in Figure 11, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1102, S1103, S1104, S1105, S1106, S1107, S1112, S1113, S1121, S1130, S1121 and S1123; the processing module 12 can be used to execute the processing steps in the method, such as step S1122.

[0600] When the device 10 is used to execute the method in Figure 12, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S1202, S1203, S1204, S1205, S1206, S1207, S1212, S1213, S1214, S1208, S1291, S1293, S1220 and S1231; the processing module 12 can be used to execute the processing steps in the method.

[0601] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0602] It should also be understood that the device 10 here is embodied in the form of a functional module. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and memory for executing one or more software or firmware programs, a combined logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 10 may be specifically the mobile management network element in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the mobile management network element in the above-mentioned method embodiments; or, the device 10 may be specifically the terminal device in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the terminal device in the above-mentioned method embodiments. To avoid repetition, it will not be described here.

[0603] The device 10 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the device (such as the first network device, the second core network device, or the relay node) in the above-mentioned method. This function can be implemented by hardware, or it can be implemented by hardware executing the corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment.

[0604] In addition, the transceiver module 11 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing module may be a processing circuit.

[0605] Figure 14 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. Device 20 includes a processor 21, which is configured to execute computer programs or instructions stored in memory 22, or read data / signaling stored in memory 22, to perform the methods described in the above method embodiments. Optionally, there may be one or more processors 21.

[0606] Optionally, as shown in FIG14 , the device 20 further includes a memory 22 for storing computer programs or instructions and / or data. The memory 22 may be integrated with the processor 21 or may be separately provided. Optionally, there may be one or more memories 22.

[0607] Optionally, as shown in Figure 14, the device 20 further includes a transceiver 23, which is used to receive and / or send signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.

[0608] As a solution, the apparatus 20 is used to implement the operations performed by the first network device in each of the above method embodiments.

[0609] As another solution, the apparatus 20 is used to implement the operations performed by the second core network device in each of the above method embodiments.

[0610] As another solution, the device 20 is used to implement the operations performed by the relay node in the above various method embodiments.

[0611] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0612] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0613] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0614] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0615] 15 is a schematic diagram of a chip system 30 provided in an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0616] The logic circuit 31 may be a processing circuit in the chip system 30. The logic circuit 31 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 30 can implement the methods and functions of the various embodiments of the present application. The input / output interface 32 may be an input / output circuit in the chip system 30, outputting information processed by the chip system 30 or inputting data or signaling information to be processed into the chip system 30 for processing.

[0617] As a solution, the chip system 30 is used to implement the operations performed by the first network device, the second core network device, or the relay node in the above various method embodiments.

[0618] For example, the logic circuit 31 is used to implement the processing-related operations performed by the first network device, the second core network device, or the relay node in the above method embodiment; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the first network device, the second core network device, or the relay node in the above method embodiment.

[0619] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the methods executed by the first network device, the second core network device, or the relay node in the above-mentioned method embodiments.

[0620] For example, when the computer program is executed by a computer, the computer can implement the method performed by the first network device, the second core network device, or the relay node in each embodiment of the above method.

[0621] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, implement the methods performed by the first network device, the second core network device, or the relay node in the above-mentioned method embodiments.

[0622] The embodiment of the present application further provides a communication system, comprising the aforementioned first network device and the second core network device. Optionally, the communication system further comprises the aforementioned relay node.

[0623] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0624] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0625] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0626] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0627] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0628] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0629] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0630] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0631] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: Applied to a first network device, the method includes: receiving first indication information, where the first indication information is used to indicate that the relay node is an unauthorized node and / or to indicate that the first communication interface cannot be established; determining, according to the first indication information, that the first communication interface cannot be established; The relay node includes a mobile terminal part and an access network node part, and the first communication interface is a logical interface between the first network device and the access network node part.

2. The method according to claim 1, characterized in that The method further comprises: receiving a first request message, where the first request message is used to request establishment of the first communication interface; A first response message is sent, where the first response message indicates that establishment of the first communication interface fails, or the first response message indicates releasing or suspending the first communication interface.

3. The method according to claim 2, characterized in that The first response message includes a first cause value, and the first cause value is used to indicate that the reason why the first communication interface fails to be established, is released, or is suspended is that the relay node is an unauthorized node.

4. The method according to claim 2 or 3, characterized in that If the first network device is a second access network node or a second core network device, the method further includes: determining not to forward the first request message to the first access network node or the relay node according to the first indication information, The second access network node is the host access network node to which the relay node accesses, the first access network node is the adjacent access network node of the relay node other than the host access network node, and the second core network device is the core network device serving the relay node.

5. The method according to claim 1, wherein If the first network device is a first access network node or a second access network node, the method further includes: determining not to initiate a request to establish the first communication interface, The second access network node is a host access network node to which the relay node accesses, and the first access network node is an adjacent access network node of the relay node other than the host access network node.

6. The method according to any one of claims 1 to 5, characterized in that The first indication information indicating that the relay node is an unauthorized node includes: The first indication information indicates that the relay node is updated from an authorized node to an unauthorized node, Receiving first indication information includes: The first indication information is received from the relay node through the first communication interface.

7. The method according to any one of claims 1 to 6, characterized in that Before receiving the first indication information, the method further includes: The first communication interface is established with the relay node.

8. The method according to any one of claims 1 to 7, characterized in that If the first network device is a first access network node or a first core network device, the receiving the first indication information includes: receiving the first indication information from the second access network node; and / or, receiving the first indication information from the second core network device, Among them, the second access network node is the host access network node accessed by the relay node, the first access network node is the adjacent access network node of the relay node other than the host access network node, the first core network device is the core network device serving the terminal device, the terminal device is the terminal device provided with access service by the relay node, and the second core network device is the core network device serving the relay node.

9. The method according to any one of claims 1 to 7, characterized in that If the first network device is a second access network node, the receiving first indication information includes: receiving the first indication information from the second core network device, The second access network node is a host access network node to which the relay node accesses, and the second core network device is a core network device serving the relay node.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: Second indication information is received, where the second indication information is used to indicate that the relay node is updated to an authorized node and / or is used to indicate that establishment of the first communication interface is allowed.

11. The method according to claim 10, characterized in that The method further comprises: receiving a second request message, where the second request message is used to request establishment of the first communication interface; A second response message is sent according to the second indication information, where the second response message indicates establishing the first communication interface.

12. The method according to claim 11, characterized in that If the first network device is a second access network node or a second core network device, the method further includes: Determine, according to the second indication information, to forward the second request message to the first access network node or the relay node; The second access network node is the host access network node accessed by the relay node, the first access network node is the adjacent access network node of the relay node other than the host access network node, and the second core network device is the core network device serving the relay node.

13. The method according to claim 10, characterized in that If the first network device is a first access network node or a second access network node, the method further includes: Determining, according to the second indication information, to initiate a request to establish the first communication interface, The second access network node is a host access network node to which the relay node accesses, and the first access network node is an adjacent access network node of the relay node other than the host access network node.

14. The method according to any one of claims 10 to 13, characterized in that If the first network device is a first access network node or a first core network device, the receiving second indication information includes: receiving the second indication information from the second access network node; and / or, receiving the second indication information from the second core network device, Among them, the second access network node is the host access network node accessed by the relay node, the first access network node is the adjacent access network node of the relay node other than the host access network node, the first core network device is the core network device serving the terminal device, the terminal device is the terminal device provided with access service by the relay node, and the second core network device is the core network device serving the relay node.

15. The method according to any one of claims 10 to 13, characterized in that If the first network device is a second access network node, the receiving second indication information includes: receiving the second indication information from the second core network device, The second access network node is a host access network node to which the relay node accesses, and the second core network device is a core network device serving the relay node.

16. A communication method, characterized in that: Applied to the second core network device, the method includes: authenticating the relay node and determining that the relay node is an unauthorized node; Sending first indication information to the first network device, where the first indication information is used to indicate that the relay node is an unauthorized node and / or is used to indicate that the first communication interface cannot be established, The relay node includes a mobile terminal part and an access network node part, the first communication interface is a logical interface between the first network device and the access network node part, the second core network device is a core network device serving the relay node, and the first network device includes at least one of the following: A first access network node, a second access network node, or a first core network device, wherein the second access network node is a host access network node accessed by the relay node, the first access network node is an adjacent access network node of the relay node other than the host access network node, the first core network device is a core network device serving a terminal device, and the terminal device is a terminal device to which access service is provided by the relay node.

17. The method according to claim 16, characterized in that The method further comprises: Establish a first protocol data unit (PDU) session with the relay node, where the first PDU session is used to carry data of the first communication interface, or the first PDU session is used to carry data of the first communication interface and data other than the data of the first communication interface.

18. A communication method, characterized in that: Applied to the second core network device, the method includes: authenticating the relay node and determining that the relay node is an unauthorized node; According to the relay node being an unauthorized node, determining that establishment of a first protocol data unit (PDU) session fails, releasing or deactivating the established first PDU session, where the first PDU session is used to carry data of the first communication interface, or the first PDU session is used to carry data of the first communication interface and data other than the data of the first communication interface, The relay node includes a mobile terminal part and an access network node part, the first communication interface is a logical interface between the first network device and the access network node part, the second core network device is a core network device serving the relay node, and the first network device includes at least one of the following: A first access network node, a second access network node, or a first core network device, wherein the second access network node is a host access network node accessed by the relay node, the first access network node is an adjacent access network node of the relay node other than the host access network node, the first core network device is a core network device serving a terminal device, and the terminal device is a terminal device to which access service is provided by the relay node.

19. The method according to claim 18, characterized in that Before determining that the first protocol data unit (PDU) session establishment fails, the method further includes: A third request message is received, where the third request message is used to request establishment of the first PDU session with the relay node.

20. The method according to claim 18 or 19, characterized in that The method further comprises: Send third indication information, where the third indication information is used to indicate that the first PDU session requested to be established by the relay node is deactivated.

21. The method according to any one of claims 16 to 20, characterized in that The method further comprises: It is determined that the relay node is updated from an unauthorized node to an authorized node.

22. The method according to claim 21, characterized in that If the relay node is in an RRC connected state, the method further includes: Sending second indication information to the first network device, where the second indication information is used to indicate that the relay node is updated to an authorized node, and / or, the second indication information is used to indicate that the first network device allows establishment of the first communication interface with the relay node.

23. The method according to claim 21, characterized in that If the relay node is in an RRC connected state, the method further includes: According to the relay node being updated from an unauthorized node to an authorized node, it is determined to establish or activate a PDU session for carrying the first communication interface.

24. The method according to claim 21, wherein If the relay node is in an RRC idle state or an RRC inactive state, the method further includes: A paging message is sent to the relay node, where the paging message includes fourth indication information, and the fourth indication information is used to indicate that the relay node is updated from an unauthorized node to an authorized node.

25. A communication method, characterized in that: Applied to a relay node, the method includes: receiving first information, where the first information indicates that the relay node is an unauthorized node; determining not to initiate a first protocol data unit (PDU) session establishment request based on the first information, or determining not to initiate a first communication interface establishment request based on the first information, The relay node includes a mobile terminal part and an access network node part, the first communication interface is a logical interface between a first network device and the access network node part, the first PDU session is used to carry data of the first communication interface, or the first PDU session is used to carry data of the first communication interface and data other than the data of the first communication interface, and the first network device includes at least one of the following: A first access network node, a second access network node, or a first core network device, wherein the second access network node is a host access network node accessed by the relay node, the first access network node is an adjacent access network node of the relay node other than the host access network node, the first core network device is a core network device serving a terminal device, and the terminal device is a terminal device to which access service is provided by the relay node.

26. The method according to claim 25, characterized in that The first information indicating that the relay node is an unauthorized node includes: The first information indicates that the relay node is updated from an authorized node to an unauthorized node.

27. The method according to claim 26, characterized in that If the second PDU session has been established, the method further includes: Requesting to release or deactivate the second PDU session, The second PDU session is used to carry data of the first communication interface, or the second PDU session is used to carry data of the first communication interface and data other than the data of the first communication interface.

28. The method according to claim 27, characterized in that Before requesting to release or deactivate the first PDU session, the method further includes: According to the first information, the terminal device in the RRC connection state accessing the relay node is switched to the first cell, which is a cell managed by an access network node other than the relay node.

29. A communication device, characterized in that: The communication device includes a processor and a memory, the processor and the memory are coupled, and the memory is used to store a computer program. When the processor runs the computer program, the communication device performs the method according to any one of claims 1 to 17, or the communication device performs the method according to any one of claims 18 to 24, or the communication device performs the method according to any one of claims 25 to 28.

30. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a communication device, the communication device is caused to perform the method according to any one of claims 1 to 28.

31. A computer program product, characterized in that The method comprises computer instructions, which, when executed on a communication device, cause the communication device to perform the method according to any one of claims 1 to 28.

32. A chip, characterized in that: The chip includes a processor and a communication interface. The processor reads and runs instructions through the communication interface. When the chip is installed in a communication device, the communication device executes the method according to any one of claims 1 to 28.

33. A communication system, characterized in that: The communication system includes a first network device and a second core network device, wherein the first network device is used to execute the method according to any one of claims 1 to 17, and the second core network device is used to execute the method according to any one of claims 18 to 24.

34. The communication system according to claim 33, wherein: The communication system further comprises a relay node, wherein the relay node is configured to perform the method according to any one of claims 25-28.

Images