Quality-of-service configuration method and communication apparatus

Abstract

Provided in the present disclosure are a quality-of-service (QoS) configuration method and a communication apparatus. The QoS configuration method comprises: receiving first information from a first access network device or from a second core network device, wherein the first information comprises a first parameter, the first parameter is used for indicating a backhaul capability of a first relay node, the first relay node may comprises the first access network device and a first mobile terminal, and the second core network device provides a service to the first mobile terminal; and sending, to the first access network device on the basis of the first parameter, a QoS parameter between a terminal device and a first core network device, wherein there is a communication connection between the terminal device and the first access network device.

Description

Service Quality Configuration Methods and Communication Devices

[0001] This application claims priority to Chinese Patent Application No. 202410572348.1, filed on May 9, 2024, entitled "Service Quality Configuration Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and more particularly to a method and apparatus for configuring Quality of Service (QoS). Background Technology

[0003] For vehicle-mounted relays (VMR), such as relay nodes deployed in vehicles or aircraft, the relay nodes provide wireless coverage for terminal devices inside the vehicle or aircraft to overcome poor wireless signal conditions. Relay nodes can access macro base stations via wireless backhaul. Macro base stations can also be called macro stations, serving base stations, or donor base stations.

[0004] In terrestrial networks, core network (CN) equipment can indicate the QoS requirements of a terminal device to the serving base station. The serving base station can then configure corresponding air interface resources based on these QoS requirements to ensure that the air interface resources meet the QoS needs of the terminal device.

[0005] However, if a relay node communicates with its serving base station using a non-terrestrial network (NTN), the core network equipment corresponding to the terminal device is unaware that the relay node is communicating via NTN. In other words, the core network equipment corresponding to the terminal device is unaware that the relay node might be performing backhaul (BH) via NTN. This can lead to inaccurate and unreasonable QoS requirements indicated by the core network equipment corresponding to the terminal device for the terminal device. Summary of the Invention

[0006] This application provides a QoS configuration method and communication device, which enables the core network equipment corresponding to the terminal equipment to configure more accurate and reasonable QoS parameters for the terminal equipment.

[0007] To achieve the above objectives, this application adopts the following technical solution:

[0008] A first aspect provides a QoS configuration method applied to a first core network device. The method includes: receiving first information from a first access network device or from a second core network device. The first information includes a first parameter indicating the backhaul capability of a first relay node. The first relay node may include the first access network device and a first mobile terminal (MT), and the second core network device provides services to the first MT. Second information is sent to the first access network device based on the first parameter. The second information indicates QoS parameters between the terminal device and the first core network device, and the terminal device and the first access network device have a communication connection.

[0009] This application informs the core network equipment corresponding to the terminal equipment of the backhaul capability of the first relay node, enabling the core network equipment corresponding to the terminal equipment to configure more accurate and reasonable QoS parameters for the terminal equipment.

[0010] In one possible design, the first information comes from the second core network device, and the first information also includes at least one of the following parameters: the identifier of the first access network device; the identifier of the first MT; or, the address parameter of the first access network device.

[0011] This application provides that the first information may include some parameters that enable the core network equipment providing services to the terminal equipment to know which relay node the first information is associated with, thereby configuring more accurate and reasonable QoS parameters for the terminal equipment connected to that relay node.

[0012] In one possible design, the method may further include: receiving third information from a third access network device when a first condition is met. The third information may include a second parameter. This second parameter indicates the backhaul capability of the third access network device. The third access network device has a communication connection with the terminal device. The second information is sent to the third access network device based on the second parameter. The first condition includes at least one of the following: the terminal device has a communication connection with the first access network device, switching to a communication connection between the terminal device and the third access network device; the terminal device undergoes an RRC re-establishment to the third access network device.

[0013] This application enables the configuration of more accurate and reasonable QoS parameters for terminal devices when switching or reconnecting to new access network devices.

[0014] In one possible design, the backhaul capability of the first relay node may include the backhaul method adopted by the first relay node and / or QoS parameters related to the first MT. The backhaul method adopted by the first relay node may include: NTN backhaul method and / or terrestrial network (TN) backhaul method.

[0015] This application provides various possible information contained in the first parameter so that the core network equipment providing services to the terminal equipment can configure more accurate and reasonable QoS parameters for the terminal equipment based on the information contained in the first parameter.

[0016] In one possible design, the backhaul capability of the second relay node may include the backhaul method adopted by the second relay node and / or QoS parameters related to the second MT. The backhaul method adopted by the second relay node may include: NTN backhaul method and / or TN backhaul method.

[0017] This application provides various possible information contained in the second parameter so that the core network equipment providing services to the terminal equipment can configure more accurate and reasonable QoS parameters for the terminal equipment based on the information contained in the second parameter.

[0018] In one possible design, the method may further include sending fourth information to the second core network device. The fourth information is used to indicate QoS parameters between the first access network device and the first core network device.

[0019] This application sends QoS parameters between the first access network device and the first core network device to the second core network device, so that the second core network device can determine more reasonable QoS parameters to meet the QoS requirements of the terminal device.

[0020] In one possible design, the method may further include sending tenth information to a first access network device. The tenth information is used to instruct a fourth core network device to provide services to the terminal device.

[0021] This application can proactively trigger the first access network device to switch core network devices in order to avoid QoS performance degradation.

[0022] In one possible design, the method may also include: identifying the fourth core network device.

[0023] In one possible design, the method may further include: receiving fifth information from a first access network device. This fifth information is used to indicate a third core network device that provides services to the first MT. Determining a fourth core network device may include: determining the fourth core network device based on the fifth information.

[0024] This application can trigger changes to the UE's core network based on changes in the MT's core network equipment, thus avoiding QoS performance degradation.

[0025] In one possible design, the method may further include receiving sixth information from the first access network device. The sixth information includes information for indicative of the second core network device and information for indicative of the first MT.

[0026] In this application, the core network of the UE and the core network of the MT can synchronize information with each other so that the core networks can communicate with each other and improve communication efficiency.

[0027] Secondly, a QoS configuration method is provided, applied to a first relay node or a second core network device. The first relay node includes a first access network device and a first MT (Mobile Terminal), and the second core network device provides services to the first MT. The method includes: determining the backhaul capability corresponding to the first access network device; and sending first information to the first core network device. The first information may include a first parameter, which indicates the backhaul capability adopted by the first relay node. The first information is also used to trigger the first core network device to configure QoS parameters between the terminal device and the first core network device. The terminal device and the first access network device have a communication connection, and the first core network device provides services to the terminal device.

[0028] This application informs the core network equipment corresponding to the terminal equipment of the backhaul capability of the first relay node, enabling the core network equipment corresponding to the terminal equipment to configure more accurate and reasonable QoS parameters for the terminal equipment.

[0029] In one possible design, the method is applied to a second core network device, and the first information further includes at least one of the following parameters: the identifier of the first access network device; the identifier of the first MT; or, the address parameter of the first access network device.

[0030] In one possible design, the backhaul capability of the first relay node includes the backhaul method adopted by the first relay node and / or QoS parameters related to the first MT. The backhaul method adopted by the first relay node may include: NTN backhaul method and / or TN backhaul method.

[0031] In one possible design, the method is applied to a second core network device, and the method may further include: receiving fourth information from a first core network device or from a first MT. The fourth information is used to indicate QoS parameters between the first access network device and the first core network device.

[0032] In one possible design, the method may further include sending fourth information to a second access network device, wherein the second access network device has a communication connection with the first MT.

[0033] In one possible design, the method may further include sending seventh information to the second access network device. The seventh information is used to indicate QoS parameters between the first core network device and the second core network device.

[0034] In one possible design, the method may further include: obtaining QoS parameters between the first core network device and the second core network device; determining QoS parameters between the first MT and the second core network based on the QoS parameters between the first access network device and the first core network device, and the QoS parameters between the first core network device and the second core network device; and sending an eighth message to the second access network device. The eighth message is used to indicate the QoS parameters between the first MT and the second core network.

[0035] In one possible design, the method may further include: acquiring QoS parameters between the second access network device and the second core network device, and QoS parameters between the first core network device and the second core network device. The second access network device has a communication connection with the first MT. Based on the QoS parameters between the first access network device and the first core network device, the second access network device and the second core network device, and the first core network device and the second core network device, the QoS parameters between the first MT and the second access network device are determined. A ninth message is sent to the second access network device. The ninth message indicates the QoS parameters between the first MT and the second access network device.

[0036] In one possible design, the method is applied to a first relay node, and the method may further include sending fourth information to a second access network device or a second core network device. This fourth information is used to indicate QoS parameters between the first access network device and the first core network device. The second access network device has a communication connection with the first MT.

[0037] In one possible design, the method may further include: sending fifth information to a first core network device or a second access network device. The fifth information is used to instruct a third core network device to provide services to the first MT. And / or, receiving tenth information from the first core network device. The tenth information is used to instruct a fourth core network device to provide services to the terminal device.

[0038] Thirdly, a QoS configuration method is provided, applied to a second access network device. The method includes: receiving seventh information from a second core network device. This seventh information indicates QoS parameters between a first relay node (MT) and the second access network device. The first relay node includes both the first access network device and the first MT. Based on the QoS parameters between the first MT and the second access network device, the radio bearer corresponding to the first MT is configured.

[0039] This application allows the second core network device to configure the QoS parameters between the first MT and the second core network device, enabling the access network device to determine the QoS parameters between the first MT and the second access network device based on these QoS parameters. This reduces the computational load on the access network device and lowers the computational requirements of the access network device.

[0040] In one possible design, the method may further include: identifying a third core network device, wherein the third core network device provides services to the first MT; and sending fifth information, which is used to instruct the third core network device.

[0041] In one possible design, the method may further include receiving fifth information. This fifth information is used to instruct a third core network device to provide services to the first MT.

[0042] Fourthly, a QoS configuration method is provided, applied to a second access network device. The method includes: receiving fourth information, which indicates QoS parameters between a first access network device and a first core network device. The first core network device provides services to a terminal device, and the terminal device has a communication connection with the first access network device. Receiving seventh information, which indicates QoS parameters between the first core network device and a second core network device. The second core network device provides services to a first MT. Obtaining QoS parameters between the second access network device and the second core network device. Determining QoS parameters between the first MT and the second access network device based on the QoS parameters between the first access network device and the first core network device, the second access network device and the second core network device, and the first core network device and the second core network device. Configuring the radio bearer corresponding to the first MT based on the QoS parameters between the first MT and the second access network device.

[0043] This application allows the second core network device to configure the QoS parameters between the first MT and the second core network device, enabling the access network device to determine the QoS parameters between the first MT and the second access network device based on these QoS parameters. This reduces the computational load on the access network device and lowers the computational requirements of the access network device.

[0044] In one possible design, the method may further include: identifying a third core network device, wherein the third core network device provides services to the first MT; and sending fifth information, which is used to instruct the third core network device.

[0045] In one possible design, the method may further include receiving fifth information. This fifth information is used to instruct a third core network device to provide services to the first MT.

[0046] Fifthly, a QoS configuration method is provided, applied to a second access network device. The method includes: receiving eighth information, which indicates QoS parameters between a first access network device and a second core network device. The first core network device provides services to a terminal device, the terminal device has a communication connection with the first access network device, and the second core network device provides services to a first MT. The method further includes: obtaining QoS parameters between the second access network device and the second core network device; determining QoS parameters between the first MT and the second access network device based on the QoS parameters between the first access network device and the second core network device; and configuring the radio bearer corresponding to the first MT based on the QoS parameters between the first MT and the second access network device.

[0047] This application allows the second core network device to configure the QoS parameters between the first MT and the second core network device, enabling the access network device to determine the QoS parameters between the first MT and the second access network device based on these QoS parameters. This reduces the computational load on the access network device and lowers the computational requirements of the access network device.

[0048] In one possible design, the method may further include: identifying a third core network device, wherein the third core network device provides services to the first MT; and sending fifth information, which is used to instruct the third core network device.

[0049] In one possible design, the method may further include receiving fifth information. This fifth information is used to instruct a third core network device to provide services to the first MT.

[0050] Sixthly, a QoS configuration method is provided, applied to a third access network device. The method includes: determining the backhaul mode corresponding to the third access network device; sending third information, which may include a second parameter indicating the backhaul mode adopted by the third access network device; and triggering a first core network device to configure QoS parameters between the terminal device and the first core network device. The terminal device and the third access network device have a communication connection, and the first core network device provides services to the terminal device.

[0051] This application enables the configuration of more accurate and reasonable QoS parameters for terminal devices when switching or reconnecting to new access network devices.

[0052] In one possible design, the method may further include: switching the terminal device's communication connection with the first access network device to a communication connection between the terminal device and the third access network device; or, the terminal device performing an RRC re-establishment to the third access network device.

[0053] In one possible design, the backhaul capability of the third access network device can include the backhaul method adopted by the third access network device, which can include NTN backhaul and / or TN backhaul. If the third access network device is a second trunk node, its backhaul capability can include QoS parameters related to the MT of the second trunk node.

[0054] A seventh aspect provides a communication device configured in a first core network device, comprising: a transceiver unit for receiving first information from a first access network device or from a second core network device. The first information includes first parameters indicating the backhaul capability of a first relay node. The first relay node may include the first access network device and a first MT (Medium-Transmitter), and the second core network device provides services to the first MT. A processing unit is configured to control the transceiver unit to send second information to the first access network device based on the first parameters. The second information indicates QoS parameters between a terminal device and the first core network device, and the terminal device and the first access network device have a communication connection.

[0055] This application informs the core network equipment corresponding to the terminal equipment of the backhaul capability of the first relay node, enabling the core network equipment corresponding to the terminal equipment to configure more accurate and reasonable QoS parameters for the terminal equipment.

[0056] In one possible design, the first information comes from the second core network device, and the first information also includes at least one of the following parameters: the identifier of the first access network device; the identifier of the first MT; or, the address parameter of the first access network device.

[0057] In one possible design, the transceiver unit is further configured to receive third information from the third access network device when a first condition is met. The third information may include a second parameter. This second parameter indicates the backhaul capability of the third access network device. The third access network device has a communication connection with the terminal device. The processing unit is further configured to control the transceiver unit to send the second information to the third access network device based on the second parameter. The first condition includes at least one of the following: the terminal device has a communication connection with the first access network device, and the connection is switched to the third access network device; the terminal device undergoes an RRC re-establishment to the third access network device.

[0058] In one possible design, the backhaul capability of the first relay node may include the backhaul method adopted by the first relay node and / or QoS parameters related to the first MT. The backhaul method adopted by the first relay node may include: NTN backhaul method and / or TN backhaul method.

[0059] In one possible design, the backhaul capability of the second relay node may include the backhaul method adopted by the second relay node and / or QoS parameters related to the second MT. The backhaul method adopted by the second relay node may include: NTN backhaul method and / or TN backhaul method.

[0060] In one possible design, the transceiver unit is also used to send fourth information to the second core network device. This fourth information is used to indicate the QoS parameters between the first access network device and the first core network device.

[0061] In one possible design, the transceiver unit is also used to: send tenth information to the first access network device. This tenth information is used to instruct the fourth core network device, which provides services to the terminal device.

[0062] In one possible design, the processing unit is also used to: determine the fourth core network device.

[0063] In one possible design, the transceiver unit is further configured to: receive fifth information from the first access network device. This fifth information is used to instruct a third core network device to provide services to the first MT. The processing unit is further configured to: determine a fourth core network device based on the fifth information.

[0064] In one possible design, the transceiver unit is further configured to: receive sixth information from the first access network device. The sixth information includes information for indicative of the second core network device and information for indicative of the first MT.

[0065] Eighthly, a communication device is provided, configured in a first relay node or a second core network device. The first relay node includes a first access network device and a first MT (Mobile Terminal), and the second core network device provides services to the first MT. The device includes: a processing unit for determining the backhaul capability corresponding to the first access network device; and a transceiver unit for sending first information to the first core network device. The first information may include first parameters indicating the backhaul capability adopted by the first relay node. The first information also triggers the first core network device to configure QoS parameters between a terminal device and the first core network device. The terminal device has a communication connection with the first access network device, and the first core network device provides services to the terminal device.

[0066] This application informs the core network equipment corresponding to the terminal equipment of the backhaul capability of the first relay node, enabling the core network equipment corresponding to the terminal equipment to configure more accurate and reasonable QoS parameters for the terminal equipment.

[0067] In one possible design, the communication device is configured on the second core network device, and the first information further includes at least one of the following parameters: the identifier of the first access network device; the identifier of the first MT; or, the address parameter of the first access network device.

[0068] In one possible design, the backhaul capability of the first relay node includes the backhaul method adopted by the first relay node and / or QoS parameters related to the first MT. The backhaul method adopted by the first relay node may include: NTN backhaul method and / or TN backhaul method.

[0069] In one possible design, the communication device is configured in the second core network equipment, and the transceiver unit is further configured to receive fourth information from the first core network equipment or from the first MT. The fourth information is used to indicate QoS parameters between the first access network equipment and the first core network equipment.

[0070] In one possible design, the transceiver unit is also used to send fourth information to the second access network device. The second access network device has a communication connection with the first MT.

[0071] In one possible design, the transceiver unit is also used to send seventh information to the second access network device. This seventh information is used to indicate the QoS parameters between the first core network device and the second core network device.

[0072] In one possible design, the transceiver unit is further configured to acquire QoS parameters between the first core network device and the second core network device. The processing unit is further configured to determine the QoS parameters between the first MT and the second core network based on the QoS parameters between the first access network device and the first core network device, and the QoS parameters between the first core network device and the second core network device. The transceiver unit is further configured to send eighth information to the second access network device. The eighth information is used to indicate the QoS parameters between the first MT and the second core network.

[0073] In one possible design, the transceiver unit is further configured to acquire QoS parameters between the second access network device and the second core network device, as well as QoS parameters between the first core network device and the second core network device. The second access network device has a communication connection with the first MT. The processing unit is further configured to determine the QoS parameters between the first MT and the second access network device based on the QoS parameters between the first access network device and the first core network device, the second access network device and the second core network device, and the first core network device and the second core network device. The transceiver unit is further configured to send a ninth message to the second access network device. The ninth message indicates the QoS parameters between the first MT and the second access network device.

[0074] In one possible design, the communication device is configured at the first relay node, and the transceiver unit is further configured to send fourth information to the second access network device or the second core network device. This fourth information is used to indicate the QoS parameters between the first access network device and the first core network device. The second access network device has a communication connection with the first MT.

[0075] In one possible design, the transceiver unit is further configured to: send fifth information to a first core network device or a second access network device, wherein the fifth information is used to instruct a third core network device to provide services to the first MT; and / or receive tenth information from the first core network device, wherein the tenth information is used to instruct a fourth core network device to provide services to the terminal device.

[0076] A ninth aspect provides a communication apparatus configured in a second access network device, comprising: a transceiver unit for receiving seventh information from a second core network device. The seventh information is used to indicate QoS parameters between a first relay node and the second access network device. A first relay node includes the first access network device and the first MT. A processing unit is configured to configure a radio bearer corresponding to the first MT based on the QoS parameters between the first MT and the second access network device.

[0077] This application allows the second core network device to configure the QoS parameters between the first MT and the second core network device, enabling the access network device to determine the QoS parameters between the first MT and the second access network device based on these QoS parameters. This reduces the computational load on the access network device and lowers the computational requirements of the access network device.

[0078] In one possible design, the processing unit is further configured to identify a third core network device, which provides services to the first MT. The transceiver unit is also configured to send fifth information, which instructs the third core network device.

[0079] In one possible design, the transceiver unit is also used to receive fifth information. This fifth information is used to instruct a third core network device to provide services to the first MT.

[0080] A tenth aspect provides a communication apparatus configured in a second access network device, comprising: a transceiver unit configured to receive fourth information. The fourth information indicates QoS parameters between the first access network device and a first core network device. The first core network device provides services to a terminal device, and the terminal device has a communication connection with the first access network device. The transceiver unit is further configured to receive seventh information. The seventh information indicates QoS parameters between the first core network device and a second core network device. The second core network device provides services to a first MT. The transceiver unit is further configured to acquire QoS parameters between the second access network device and the second core network device. A processing unit is configured to determine QoS parameters between the first MT and the second access network device based on the QoS parameters between the first access network device and the first core network device, the QoS parameters between the second access network device and the second core network device, and the QoS parameters between the first core network device and the second core network device. The processing unit is further configured to configure a radio bearer corresponding to the first MT based on the QoS parameters between the first MT and the second access network device.

[0081] This application allows the second core network device to configure the QoS parameters between the first MT and the second core network device, enabling the access network device to determine the QoS parameters between the first MT and the second access network device based on these QoS parameters. This reduces the computational load on the access network device and lowers the computational requirements of the access network device.

[0082] In one possible design, the processing unit is further configured to identify a third core network device, which provides services to the first MT. The transceiver unit is also configured to send fifth information, which instructs the third core network device.

[0083] In one possible design, the transceiver unit is also used to receive fifth information. This fifth information is used to instruct a third core network device to provide services to the first MT.

[0084] Eleventhly, a communication device is provided, configured in a second access network device, comprising: a transceiver unit, configured to receive eighth information. The eighth information is used to indicate QoS parameters between a first access network device and a second core network device. The first core network device provides services to a terminal device, the terminal device has a communication connection with the first access network device, and the second core network device provides services to a first MT. The transceiver unit is further configured to acquire QoS parameters between the second access network device and the second core network device. A processing unit is configured to determine QoS parameters between the first MT and the second access network device based on the QoS parameters between the first access network device and the second core network device. The processing unit is further configured to configure a radio bearer corresponding to the first MT based on the QoS parameters between the first MT and the second access network device.

[0085] This application allows the second core network device to configure the QoS parameters between the first MT and the second core network device, enabling the access network device to determine the QoS parameters between the first MT and the second access network device based on these QoS parameters. This reduces the computational load on the access network device and lowers the computational requirements of the access network device.

[0086] In one possible design, the processing unit is further configured to identify a third core network device, which provides services to the first MT. The transceiver unit is also configured to send fifth information, which instructs the third core network device.

[0087] In one possible design, the transceiver unit is also used to receive fifth information. This fifth information is used to instruct a third core network device to provide services to the first MT.

[0088] In a twelfth aspect, a communication apparatus is provided, configured in a third access network device, comprising: a processing unit for determining a backhaul mode corresponding to the third access network device; and a transceiver unit for transmitting third information. The third information may include a second parameter indicating the backhaul mode adopted by the third access network device. The third information is also used to trigger a first core network device to configure QoS parameters between a terminal device and the first core network device. The terminal device and the third access network device have a communication connection, and the first core network device provides services to the terminal device.

[0089] This application enables the configuration of more accurate and reasonable QoS parameters for terminal devices when switching or reconnecting to new access network devices.

[0090] In one possible design, the processing unit is also used to establish a connection with the terminal device based on handover; or to re-establish a connection with the terminal device via RRC.

[0091] In one possible design, the backhaul capability of the third access network device can include the backhaul method adopted by the third access network device, which can include NTN backhaul and / or TN backhaul. If the third access network device is a second trunk node, its backhaul capability can include QoS parameters related to the MT of the second trunk node.

[0092] In a thirteenth aspect, a communication apparatus is provided, configured in a first core network device, comprising: a transceiver for receiving first information from a first access network device or from a second core network device. The first information includes a first parameter indicating the backhaul capability of a first relay node. The first relay node may include the first access network device and a first MT (Medium-Transmitter), and the second core network device provides services to the first MT. A processor is configured to control the transceiver to send second information to the first access network device based on the first parameter. The second information indicates QoS parameters between a terminal device and the first core network device, and the terminal device and the first access network device have a communication connection.

[0093] This application informs the core network equipment corresponding to the terminal equipment of the backhaul capability of the first relay node, enabling the core network equipment corresponding to the terminal equipment to configure more accurate and reasonable QoS parameters for the terminal equipment.

[0094] In one possible design, the first information comes from the second core network device, and the first information also includes at least one of the following parameters: the identifier of the first access network device; the identifier of the first MT; or, the address parameter of the first access network device.

[0095] In one possible design, the transceiver is further configured to receive third information from the third access network device when a first condition is met. The third information may include a second parameter. This second parameter indicates the backhaul capability of the third access network device. The third access network device has a communication connection with the terminal device. The processor is further configured to control the transceiver to send the second information to the third access network device based on the second parameter. The first condition includes at least one of the following: the terminal device has a communication connection with the first access network device, and the connection is switched to a communication connection between the terminal device and the third access network device; the terminal device undergoes an RRC re-establishment to the third access network device.

[0096] In one possible design, the backhaul capability of the first relay node may include the backhaul method adopted by the first relay node and / or QoS parameters related to the first MT. The backhaul method adopted by the first relay node may include: NTN backhaul method and / or TN backhaul method.

[0097] In one possible design, the backhaul capability of the second relay node may include the backhaul method adopted by the second relay node and / or QoS parameters related to the second MT. The backhaul method adopted by the second relay node may include: NTN backhaul method and / or TN backhaul method.

[0098] In one possible design, the transceiver is also used to send fourth information to the second core network device. This fourth information indicates the QoS parameters between the first access network device and the first core network device.

[0099] In one possible design, the transceiver is also used to send a tenth message to the first access network device. This tenth message instructs the fourth core network device to provide services to the terminal device.

[0100] In one possible design, the processor is also used to: determine the fourth core network device.

[0101] In one possible design, the transceiver is further configured to: receive fifth information from the first access network device. This fifth information is used to instruct a third core network device to provide services to the first MT. The processor is further configured to: determine a fourth core network device based on the fifth information.

[0102] In one possible design, the transceiver is also used to: receive sixth information from the first access network device. The sixth information includes information for indicative of the second core network device and information for indicative of the first MT.

[0103] In a fourteenth aspect, a communication apparatus is provided, configured in a first relay node or a second core network device. The first relay node includes a first access network device and a first MT (Mobile Terminal), and the second core network device provides services to the first MT. The apparatus includes: a processor for determining the backhaul capability corresponding to the first access network device; and a transceiver for sending first information to the first core network device. The first information may include a first parameter indicating the backhaul capability adopted by the first relay node. The first information is also used to trigger the first core network device to configure QoS parameters between a terminal device and the first core network device. The terminal device has a communication connection with the first access network device, and the first core network device provides services to the terminal device.

[0104] This application informs the core network equipment corresponding to the terminal equipment of the backhaul capability of the first relay node, enabling the core network equipment corresponding to the terminal equipment to configure more accurate and reasonable QoS parameters for the terminal equipment.

[0105] In one possible design, the communication device is configured on the second core network device, and the first information further includes at least one of the following parameters: the identifier of the first access network device; the identifier of the first MT; or, the address parameter of the first access network device.

[0106] In one possible design, the backhaul capability of the first relay node includes the backhaul method adopted by the first relay node and / or QoS parameters related to the first MT. The backhaul method adopted by the first relay node may include: NTN backhaul method and / or TN backhaul method.

[0107] In one possible design, the communication device is configured in the second core network device, and the transceiver is further configured to receive fourth information from the first core network device or from the first MT. The fourth information is used to indicate QoS parameters between the first access network device and the first core network device.

[0108] In one possible design, the transceiver is also used to send fourth information to a second access network device, which has a communication connection with the first MT.

[0109] In one possible design, the transceiver is also used to send a seventh message to the second access network device. This seventh message indicates the QoS parameters between the first core network device and the second core network device.

[0110] In one possible design, the transceiver is further configured to acquire QoS parameters between the first core network device and the second core network device. The processor is further configured to determine the QoS parameters between the first MT and the second core network based on the QoS parameters between the first access network device and the first core network device, and the QoS parameters between the first core network device and the second core network device. The transceiver is further configured to send an eighth message to the second access network device. This eighth message indicates the QoS parameters between the first MT and the second core network.

[0111] In one possible design, the transceiver is further configured to acquire QoS parameters between the second access network device and the second core network device, as well as QoS parameters between the first core network device and the second core network device. The second access network device has a communication connection with the first MT. The processor is further configured to determine the QoS parameters between the first MT and the second access network device based on the QoS parameters between the first access network device and the first core network device, the QoS parameters between the second access network device and the second core network device, and the QoS parameters between the first core network device and the second core network device. The transceiver is also configured to send a ninth message to the second access network device. This ninth message indicates the QoS parameters between the first MT and the second access network device.

[0112] In one possible design, the communication device is configured at the first relay node, and the transceiver is further configured to send fourth information to the second access network device or the second core network device. This fourth information indicates the QoS parameters between the first access network device and the first core network device. The second access network device has a communication connection with the first MT.

[0113] In one possible design, the transceiver is also used to: send fifth information to a first core network device or a second access network device. The fifth information is used to instruct a third core network device to provide services to the first MT. And / or, receive tenth information from the first core network device. The tenth information is used to instruct a fourth core network device to provide services to the terminal device.

[0114] In a fifteenth aspect, a communication apparatus is provided, configured in a second access network device, comprising: a transceiver for receiving seventh information from a second core network device. The seventh information is used to indicate QoS parameters between a first relay node and the second access network device. A first relay node includes the first access network device and the first MT. A processor is configured to configure a radio bearer corresponding to the first MT based on the QoS parameters between the first MT and the second access network device.

[0115] This application allows the second core network device to configure the QoS parameters between the first MT and the second core network device, enabling the access network device to determine the QoS parameters between the first MT and the second access network device based on these QoS parameters. This reduces the computational load on the access network device and lowers the computational requirements of the access network device.

[0116] In one possible design, the processor is also used to identify a third core network device, which provides services to the first MT. The transceiver is also used to transmit fifth information, which is used to instruct the third core network device.

[0117] In one possible design, the transceiver is also used to receive a fifth message. This fifth message is used to instruct a third core network device to provide services to the first MT.

[0118] In a sixteenth aspect, a communication apparatus is provided, configured in a second access network device, comprising: a transceiver for receiving fourth information. The fourth information indicates QoS parameters between a first access network device and a first core network device. The first core network device provides services to a terminal device, and the terminal device has a communication connection with the first access network device. The transceiver is further configured to receive seventh information. The seventh information indicates QoS parameters between the first core network device and a second core network device. The second core network device provides services to a first MT. The transceiver is further configured to acquire QoS parameters between the second access network device and the second core network device. A processor is configured to determine QoS parameters between the first MT and the second access network device based on the QoS parameters between the first access network device and the first core network device, the QoS parameters between the second access network device and the second core network device, and the QoS parameters between the first core network device and the second core network device. The processor is further configured to configure a radio bearer corresponding to the first MT based on the QoS parameters between the first MT and the second access network device.

[0119] This application allows the second core network device to configure the QoS parameters between the first MT and the second core network device, enabling the access network device to determine the QoS parameters between the first MT and the second access network device based on these QoS parameters. This reduces the computational load on the access network device and lowers the computational requirements of the access network device.

[0120] In one possible design, the processor is also used to identify a third core network device, which provides services to the first MT. The transceiver is also used to transmit fifth information, which is used to instruct the third core network device.

[0121] In one possible design, the transceiver is also used to receive a fifth message. This fifth message is used to instruct a third core network device to provide services to the first MT.

[0122] In a seventeenth aspect, a communication apparatus is provided, configured in a second access network device, comprising: a transceiver for receiving eighth information. The eighth information is used to indicate QoS parameters between a first access network device and a second core network device. The first core network device provides services to a terminal device, the terminal device has a communication connection with the first access network device, and the second core network device provides services to a first MT. The transceiver is further configured to acquire the QoS parameters between the second access network device and the second core network device. A processor is configured to determine the QoS parameters between the first MT and the second access network device based on the QoS parameters between the first access network device and the second core network device. The processor is further configured to configure a radio bearer corresponding to the first MT based on the QoS parameters between the first MT and the second access network device.

[0123] This application allows the second core network device to configure the QoS parameters between the first MT and the second core network device, enabling the access network device to determine the QoS parameters between the first MT and the second access network device based on these QoS parameters. This reduces the computational load on the access network device and lowers the computational requirements of the access network device.

[0124] In one possible design, the processor is also used to identify a third core network device, which provides services to the first MT. The transceiver is also used to transmit fifth information, which is used to instruct the third core network device.

[0125] In one possible design, the transceiver is also used to receive a fifth message. This fifth message is used to instruct a third core network device to provide services to the first MT.

[0126] Eighteenth aspect: A communication apparatus is provided, configured in a third access network device, comprising: a processor for determining a backhaul mode corresponding to the third access network device; and a transceiver for transmitting third information. The third information may include a second parameter indicating the backhaul mode adopted by the third access network device. The third information is also used to trigger a first core network device to configure QoS parameters between a terminal device and the first core network device. The terminal device and the third access network device have a communication connection, and the first core network device provides services to the terminal device.

[0127] This application enables the configuration of more accurate and reasonable QoS parameters for terminal devices when switching or reconnecting to new access network devices.

[0128] In one possible design, the processor is also used to establish a connection with the terminal device based on a handover; or to re-establish a connection with the terminal device via RRC.

[0129] In one possible design, the backhaul capability of the third access network device can include the backhaul method adopted by the third access network device, which can include NTN backhaul and / or TN backhaul. If the third access network device is a second trunk node, its backhaul capability can include QoS parameters related to the MT of the second trunk node.

[0130] In some examples, the aforementioned communication device may be a terminal, or a communication module in a terminal, or a chip in a terminal that is responsible for communication functions, such as a modem chip (also known as a baseband chip), or a system-on-chip (SoC) or system-in-package (SIP) chip containing a modem module.

[0131] In some examples, the aforementioned communication device may be an access network device, or a module (e.g., a circuit, chip, or chip system) within the access network device, or a logical node, logical module, or software that can implement all or part of the functions of the access network device.

[0132] In some examples, the aforementioned communication device may be a core network device, or a module (e.g., a circuit, chip, or chip system) within a core network device, or a logical node, logical module, or software capable of implementing all or part of the functions of the core network device.

[0133] Nineteenthly, a communication system is provided. The system includes a first core network device performing any of the methods described in the first aspect, a first relay node and / or a second core network device performing any of the methods described in the second aspect, and a second access network device performing any of the methods described in the third, fourth, or fifth aspects. In some examples, the system may further include a third access network device performing any of the methods described in the sixth aspect.

[0134] In a twentieth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions; when the computer instructions are executed on a computer, the computer causes the computer to perform a communication method as designed in any of the foregoing aspects.

[0135] In a twenty-first aspect, a computer program product is provided. The computer program product includes a computer program or instructions that, when executed on a computer, cause the computer to perform a communication method as designed in any of the foregoing aspects.

[0136] The beneficial effects of the methods in any of the second to twenty-first aspects mentioned above can be referred to the description of the beneficial effects of the methods in the first aspect, and will not be repeated here. Attached Figure Description

[0137] Figure 1 is a schematic diagram of the architecture of the communication system used in the embodiments of this application;

[0138] Figure 2 is a schematic diagram of a VMR scene provided in an embodiment of this application;

[0139] Figure 3 is a schematic diagram of a relay network structure provided in an embodiment of this application;

[0140] Figure 4 is a schematic diagram of another relay network structure provided in an embodiment of this application;

[0141] Figure 5 is a schematic diagram of another relay network structure provided in an embodiment of this application;

[0142] Figure 6 is a schematic diagram of a QoS configuration method provided in an embodiment of this application;

[0143] Figure 7 is a schematic diagram of another QoS configuration method provided by an embodiment of this application;

[0144] Figure 8 is a schematic diagram of QoS between devices provided in an embodiment of this application;

[0145] Figure 9 is a schematic diagram of another QoS configuration method provided by an embodiment of this application;

[0146] Figure 10 is a schematic diagram of a core network device switching method provided in an embodiment of this application;

[0147] Figure 11 is a schematic diagram of another core network device switching method provided by an embodiment of this application;

[0148] Figure 12 is a schematic diagram of a core network device synchronization method provided in an embodiment of this application;

[0149] Figure 13 is a schematic diagram of another core network device synchronization method provided in an embodiment of this application;

[0150] Figure 14 is a schematic diagram of another core network device synchronization method provided by an embodiment of this application;

[0151] Figure 15 is a schematic diagram of another QoS configuration method provided by an embodiment of this application;

[0152] Figure 16 is a schematic diagram of another QoS configuration method provided by an embodiment of this application;

[0153] Figure 17 is a schematic diagram of another core network device switching method provided by an embodiment of this application;

[0154] Figure 18 is a schematic diagram of another core network device switching method provided in an embodiment of this application;

[0155] Figure 19 is a schematic diagram of a relay network structure in an open wireless access network scenario provided by an embodiment of this application;

[0156] Figure 20 is a schematic diagram of another QoS configuration method provided by an embodiment of this application;

[0157] Figure 21 is a schematic diagram of a communication device provided in an embodiment of this application;

[0158] Figure 22 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0159] Figure 1 is a schematic diagram of the architecture of a communication system 1000 provided in an embodiment of this application. As shown in Figure 1, the communication system 1000 includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110), and may also include at least one terminal (120a-120j in Figure 1, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). The terminal 120 is wirelessly connected to the RAN node 110. Terminals and RAN nodes can be interconnected via wired or wireless means. The communication system 1000 may also include a core network 200. The RAN node 110 is connected to the core network 200 via wireless or wired means. The core network equipment in core network 200 and the RAN node 110 in RAN 100 can be independent and different physical devices, or they can be the same physical device that integrates the logical functions of the core network equipment and the logical functions of the RAN node. Communication system 1000 may also include Internet 300.

[0160] RAN100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, a 6th generation (6G) radio access system, or a future radio access system as defined in the 3rd generation partnership project (3GPP). RAN100 can also include two or more of the above-mentioned different radio access systems. RAN100 can also be an open RAN (O-RAN).

[0161] RAN nodes, also known as radio access network equipment, RAN entities, or access nodes, are used to help terminals access communication systems wirelessly. In one application scenario, an RAN node can be a base station (BS), an evolved NodeB (eNodeB / eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6G mobile communication system, or a base station in a future mobile communication system. RAN nodes can be macro base stations (as shown in Figure 1, 110a), micro base stations or indoor stations (as shown in Figure 1, 110b), relay nodes, or master nodes.

[0162] In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing different functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). Here, the CU performs the functions of the base station's Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP), and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU performs the functions of the base station's Radio Link Control (RANC) and Medium Access Control (MAC) layers, and can also perform some or all of the physical layer functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception. The CU and DU can be two independent RAN nodes or integrated into the same RAN node, such as within a baseband unit (BBU). The RU can be included in radio frequency equipment, such as in a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0163] In different systems, RAN nodes may have different names. For example, in an open radio access network (O-RAN) system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). The RAN nodes in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. For example, an RAN node can be a server loaded with the corresponding software modules. The embodiments of this application do not limit the specific technology or device form used in the RAN nodes. For ease of description, a base station is used as an example of a RAN node in the following description.

[0164] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0165] In some examples, the core network 200 may include any core network device such as the access and mobility management function (AMF) entity, the session management function (SMF) entity, the user plane function (UPF) entity, the sensing service control function (SSCF), the sensing data processing function (SDPF), and the unified data management (UDM).

[0166] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0167] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminals 120j that access the wireless access network 100 through 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol. In this case, relative to 110a, 120i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with base station functions, and 120a-120j in Figure 1 can be called communication devices with terminal functions.

[0168] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0169] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0170] In a wireless communication system, communication devices are included, and these devices can communicate wirelessly using air interface resources. These communication devices can include network devices and terminal devices; network devices can also be called base station devices. Air interface resources can include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources. These communication devices can also be called communication apparatuses.

[0171] The solutions provided in this application can be applied to wireless communication between communication devices. Wireless communication can include: wireless communication between network devices and terminals, wireless communication between network devices, and wireless communication between terminals. In this application, the term "wireless communication" can also be simply referred to as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission."

[0172] Referring to a VMR scenario shown in Figure 2, assuming VMR 220 is deployed on a moving vehicle, VMR 220 accesses the host node 230 via wireless backhaul, and simultaneously provides wireless coverage for the terminal 210 inside the vehicle. The host node 230 can be considered the serving base station of VMR 220. Relay nodes in a VMR scenario can include a mobile terminal (MT) component and a relay unit (DU) component. When a relay node faces its parent node, it acts as a mobile terminal (MT). When a relay node faces its child node, it acts as a network device (DU). It can be understood that the parent node can be considered the node one hop above the relay node, and the child node can be considered the node one hop below the relay node. It can be understood that terminal 210 in Figure 2 can be terminal 120 in Figure 1, VMR 220 can be a wireless relay node, and host node 230 can be RAN node 110a in Figure 1.

[0173] It is clear that "mobile terminal" and "terminal device" have the same meaning and can both be referred to as "terminal". To facilitate the distinction between an independent terminal and the terminal function implemented in a relay device, in the embodiments of this application, an independent terminal is referred to as a terminal device or UE, and the terminal function implemented in a relay device is referred to as MT.

[0174] For mobile relay nodes, to enhance their capabilities, the functionality of the CU (Curricular Unit Control) is introduced, enabling them to possess complete access network equipment functions. For example, such relay nodes could be called Wireless Access and Backhaul (WAB) nodes. Of course, relay nodes with complete access network equipment and MT (Mobile Transmission) functions can also be called NR (Relay Node, RN), 5G RN, etc. This application does not limit the specific names of such relay nodes in its embodiments.

[0175] Next, each embodiment of this application will be described using a relay node with complete access network equipment functions and MT functions as an example, referred to as a WAB node.

[0176] Referring to the network structure shown in Figure 3, a WAB node can include complete access network equipment functions and MT functions. Access network equipment functions include gNB functions, meaning a WAB node can include both MT and gNB components. It can be understood that in a CU / DU separation architecture, gNB functions can be implemented through CU functions plus DU functions. A UE can access the WAB-gNB via the Uu interface. For the WAB node, the WAB-MT can encapsulate control plane or user plane data sent by the UE within a WAB-MT protocol data unit (PDU) session. This data is sent from the WAB-MT to its serving gNB via the Uu interface, and forwarded by the serving gNB to the WAB-MT's core network equipment, such as the WAB-MT's UPF. The Uu interface between the WAB-MT and its serving gNB corresponds to the backhaul link. It can be understood that the serving gNB of the MT in Figure 3 is the same as the serving gNB of the WAB-MT. The Uu interface can represent the communication interface established between the terminal and the access network equipment. In Figure 3, UPF 2 is the UPF of WAB-MT, and AMF 2 is the AMF of WAB-MT.

[0177] The WAB core network can include the WAB-MT's AMF and UPF, etc. It can be understood that the WAB core network is the core network equipment providing services to the WAB-MT. The WAB-MT's serving gNB and the WAB's AMF can have an N2 interface, and the WAB-MT's serving gNB and the WAB-MT's UPF can have an N3 interface. The WAB-MT's UPF can parse the packet header information of the data sent by the WAB-MT to obtain the packet header related to the UE. Then, it sends the data to the UE's core network equipment according to Internet Protocol (IP) routing. The UE's core network can include the UE's AMF and UE's UPF, etc. It can be understood that the UE's core network is the core network equipment providing services to the UE. The WAB-MT's AMF can communicate with the UE's AMF and UE's UPF through the N6 interface, and the WAB-MT's UPF can also communicate with the UE's AMF and UE's UPF through the N6 interface. In some examples, the core network equipment providing services to the UE and the core network equipment providing services to WAB-MT may be the same core network equipment or different core network equipment; this application does not limit this. The N2 and N3 interfaces mentioned above can also be collectively referred to as next-generation (NG) interfaces. The NG interface can be considered as the communication interface between the access network equipment and the core network equipment. In Figure 3, UPF 1 is the UE's UPF, and AMF 1 is the UE's AMF.

[0178] Logically, an N2 interface is established between the WAB-gNB and the UE's AMF, and an N3 interface is established between the WAB-gNB and the UE's UPF. A PDU session, i.e., the UE PDU session in Figure 3, is established between the UE and its UPF. This UE PDU session is used to send the UE's user plane data. However, it is clear that the UE's user plane data is actually wrapped in the WAB-MT's PDU session. This data is treated as WAB-MT data during the return transmission. Only after the WAB-MT's UPF parses the data packet to obtain the UE's header will it be forwarded to the UE's UPF based on IP routing. Control plane data transmitted between the WAB-gNB and the UE's AMF is also implemented through a similar process; for ease of description, this embodiment will not be elaborated upon here. The WAB-MT's PDU session, i.e., the MT PDU session in Figure 3, can be implemented through communication between the WAB-MT and its serving gNB, and between the WAB-MT's serving gNB and its UPF.

[0179] It is understandable that the UE's AMF can also be called the WAB-gNB's AMF.

[0180] In some embodiments, WAB-MT is allowed to backhaul via NTN or terrestrial network (TN). In some examples, when backhauling via TN, the UE's core network equipment can indicate the UE's quality of service (QoS) requirements to the UE's serving gNB. This allows the serving gNB to configure appropriate air interface resources to meet the UE's QoS requirements.

[0181] In other examples, if NTN is used for backhaul, such as via satellite, this scenario is applicable to areas without terrestrial network coverage, for example, where relay nodes are deployed on aircraft and backhaul can be achieved via satellite. Referring to Figure 3, this means that the Uu interface between WAB-MT and its serving gNB may be implemented via satellite communication.

[0182] The satellite's operating modes can include transparent mode and regenerative mode. Transparent mode indicates that the satellite is used for transparent forwarding and does not perform protocol stack processing. For example, referring to the network architecture shown in Figure 4, the satellite's operating mode in this architecture can be transparent mode. Similar to Figure 3, the difference is that the satellite can provide Uu interface communication for WAB-MT. The satellite can also connect to a ground-based gateway station via a microwave link, and then communicate with the WAB-MT's serving gNB through the gateway station. Therefore, for WAB-MT, a logical Uu interface can be considered to have been established through the satellite, the gateway station, and the WAB-MT's serving gNB.

[0183] For example, referring to the network architecture shown in Figure 5, the satellite's operating mode can be regeneration mode. Similar to Figure 3, the difference is that the satellite has protocol stack processing capabilities, requiring processing of received messages to generate new messages for transmission. In this regeneration mode, the WAB-MT serving gNB can be deployed on the satellite, and the WAB-MT serving gNB on the satellite can establish a Uu interface with WAB-MT. The satellite then transmits the data back to the ground gateway station via a microwave link. The gateway station then sends the data to the WAB-MT core network equipment, such as the WAB-MT AMF and WAB-MT UPF, via IP routing. In this network architecture, the gateway station can be considered to act as an IP forwarder. Logically, the N2 and N3 interfaces can still be considered to be established between the WAB-MT serving gNB and the WAB-MT core network equipment.

[0184] In related technologies, UEs can access the network via satellite. However, due to the long distance between the UE and the satellite and the large propagation delay, the terminal's core network can currently indicate a specific QoS parameter to the terminal's serving gNB. This QoS parameter is not entirely determined based on the UE's subscription information. For example, the QoS parameter for access via NTN can be identified by the 5G quality of service identifier (5QI). For instance, a 5QI value of 10 corresponds to a packet delay budget (PDB) of 1100 milliseconds (ms). Of course, the above 5QI value and corresponding PDB value are only one possible example, and this application does not limit the scope of the embodiments.

[0185] However, current technology does not consider the introduction of relay nodes in satellite communication. Therefore, in communication scenarios where the UE uses a relay node for backhaul, the UE's core network equipment will not know whether the relay node's MT (Mean Transmission Mode) uses NTN (Network Transmission Mode). Consequently, the UE's core network will be unable to configure accurate QoS parameters for the UE.

[0186] Therefore, this application provides a QoS configuration method that informs the core network device corresponding to the terminal device of the backhaul capability of the first relay node, so that the core network device corresponding to the terminal device can configure more accurate and reasonable QoS parameters for the terminal device.

[0187] The QoS configuration method and QoS configuration device will be further described below with reference to the accompanying drawings. It is understood that this application uses network devices and terminals as examples of the execution subjects in the interactive illustration, but this application does not limit the execution subjects of the interactive illustration. For example, the method executed by the network device in this application can also be implemented by modules (e.g., circuits, chips, or chip systems) in the network device, or by logical nodes, logical modules, or software that can implement all or part of the functions of the network device; the method executed by the terminal in this application can also be implemented by the communication module in the terminal or by circuits or chips (such as modem chips (also known as baseband chips), or SoC chips containing modem cores, or SIP chips) in the terminal responsible for communication functions. The network device can include access network devices and core network devices.

[0188] In the embodiments of this application, the term "wireless communication" can also be abbreviated as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0189] Figure 6 is a schematic diagram of a QoS configuration method provided in an embodiment of this application.

[0190] This QoS configuration process can be applied to, but is not limited to, the communication scenarios shown in Figures 1 to 5. The method may include the following steps:

[0191] S101, the first relay node or the second core network device sends the first information to the first core network device.

[0192] Accordingly, the first core network device receives the first information from the first relay node or from the second core network device.

[0193] In some embodiments, the first core network device can be considered as the core network device providing services to the terminal device. For example, the core network device of the UE in Figures 3 to 5 can be the UE's AMF (Advanced Management Function). The first relay node can be a relay node with complete access network device functions and MT (Mobile Transmission) functions. For example, the first relay node can be a WAB (Web Application Block) node. The first relay node can include the first access network device and the first MT. It is understood that the first relay node can also be called a relay node with access network device functions, a mobile relay node, etc., and the name of the first relay node is not limited in this application embodiment. The second core network device can be considered as the core network device providing services to the first MT. For example, the core network device of the WAB in Figures 3 to 5 can be the AMF of the WAB-MT.

[0194] It is understood that in the following embodiments, the first relay node will be described as a WAB node, and the first access network device can be a WAB-gNB, and the first MT can be a WAB-MT. The WAB-gNB can provide access services to the UE, and the WAB-MT can provide backhaul.

[0195] In some examples, the first information may include a first parameter. This first parameter may be used to indicate the backhaul capability of the first relay node. The backhaul capability of the first relay node may include the backhaul method adopted by the first relay node. Alternatively, the backhaul capability of the first relay node may include QoS parameters related to the first MT. Or, the backhaul capability of the first relay node may include both the backhaul method adopted by the first relay node and QoS parameters related to the first MT.

[0196] In some examples, the backhaul method used by the first relay node may include NTN backhaul. Alternatively, the backhaul method used by the first relay node may include TN backhaul. Or, the backhaul method used by the first relay node may include both NTN and TN backhaul. For example, the first MT may employ dual connectivity. For the two different connections in this dual connectivity, one connection may employ NTN backhaul, and the other connection may employ TN backhaul. It is understood that the first parameter can indicate whether the first relay node uses NTN or TN backhaul. In other examples, the QoS parameters associated with the first MT may be the QoS parameters between the first MT and its serving access network device. Alternatively, the QoS parameters associated with the first MT may be the QoS parameters between the first MT and the second core network device. It is understood that the serving access network device in the embodiments of this application will be described using a serving gNB as an example, but the embodiments of this application are not limited to this, and the serving access network device may also be any other possible access network device.

[0197] This application provides various possible information contained in the first parameter so that the core network device providing services to the terminal device can configure more accurate and reasonable QoS parameters for the terminal device based on the information contained in the first parameter.

[0198] In some embodiments, when a first relay node sends first information to a first core network device, it may be that the first relay node determines its backhaul capability and sends the first information to the first core network device through a first access network device within the first relay node. For example, the first relay node determining its backhaul capability may be that it determines whether it uses an NTN backhaul mode or a TN backhaul mode. And / or, the first relay node determines QoS parameters related to the first MT.

[0199] In other embodiments, when the second core network device sends the first information to the first core network device, the second core network device may determine the backhaul capability of the first relay node and send the first information to the first core network device. It is understood that since the second core network device provides services to the first MT, it can obtain the backhaul capability of the first relay node.

[0200] In some examples, the first relay node or the second core network device might be triggered to send the first information to the first core network device when the backhaul capability of the first relay node changes. In other examples, the first relay node or the second core network device might be triggered to send the first information to the first core network device when the first relay node accesses the network for the first time, such as when a WAB node accesses the network.

[0201] In some embodiments, when the first information originates from a second core network device, the first information may further include an identifier of a first access network device. For example, the identifier of the first access network device may be an identifier of a WAB-gNB. In other embodiments, the first information may further include an identifier of a first MT. In still other embodiments, the first information may further include address parameters of the first access network device. For example, the address parameters of the first access network device may be an IP address, or other possible information used to represent the address of the first access network device.

[0202] In some examples, the first information may also include: the identifier of the first access network device and the identifier of the first MT; or, the identifier of the first access network device and the address parameters of the first access network device; or, the address parameters of the first access network device and the identifier of the first MT; or, the identifier of the first access network device, the address parameters of the first access network device, and the identifier of the first MT.

[0203] In some examples, the identifier can be an identity (ID) or an index.

[0204] This application embodiment also provides some parameters that the first information may include, which can enable the core network equipment providing services to the terminal equipment to know which relay node the first information is related to, and thus configure more accurate and reasonable QoS parameters for the terminal equipment connected to the relay node.

[0205] S102, the first core network device sends the second information to the first relay node device.

[0206] For example, the first core network device can send second information to the first access network device. Correspondingly, the first relay node can receive the second information from the first core network device. Taking the first relay node as a WAB node as an example, the first core network device can send the second information to the WAB-gNB, and the WAB-gNB can receive the second information from the first core network device. This second information can be used to indicate the QoS parameters between the terminal device and the first core network device.

[0207] In some embodiments, the first core network device can determine the QoS parameters between the terminal device and the first core network device based on the first parameters in the first information received in S101. That is, the first core network device can dynamically configure reasonable QoS parameters for the terminal device based on whether the first relay node uses NTN or TN backhaul, and / or QoS parameters related to the first MT. This allows the first core network device to inform the first access network device of these reasonable QoS parameters.

[0208] It is understood that the terminal device in each embodiment of this application can be considered to have a communication connection with the first access network device. Alternatively, it can be considered that the terminal device has been connected to the first access network device, or that the first access network device provides services to the terminal device, or that the first access network device serves the terminal device, etc.

[0209] This application embodiment informs the core network device corresponding to the terminal device of the backhaul capability of the first relay node, enabling the core network device corresponding to the terminal device to configure more accurate and reasonable QoS parameters for the terminal device.

[0210] In the QoS configuration method provided in this application embodiment, considering that the access network device may switch during the movement of the terminal device, such as the access network device serving the terminal device may change, the method may further include: when a first condition is met, the first core network device receives third information from the third access network device. The third information includes a second parameter, which is used to indicate the backhaul capability of the third access network device. The first core network device sends the second information to the third access network device based on the second parameter.

[0211] In some embodiments, the third access network device can be considered as the new access network device after the terminal device performs an access network device handover. That is, the terminal device originally had a communication connection with the first access network device, but after the terminal device performs an access network device handover during movement, it can switch to a connection with the third access network device. In other words, the third access network device has a communication connection with the terminal device. In some examples, the third access network device can be a gNB. In other examples, the third access network device can be an access network device included in another relay device. For example, the second relay device can include the third access network device and the second MT. It is understood that the second relay device, similar to the first relay device, can also be a WAB node.

[0212] It is understandable that when the first core network device receives third information from the third access network device, the second information sent by the first core network device can be determined based on the second parameters. In other words, the first core network device can determine the QoS parameters between the terminal device and the first core network device based on the second parameters in the third information, such as the backhaul capability of the third access network device.

[0213] In other embodiments, when a terminal device switches from a first access network device to a third access network device, or re-establishes RRC to a third access network device, if the core network device of the terminal device also changes, for example, from a first core network device to a fourth core network device, then the fourth core network device receives third information from the third access network device. The fourth core network device can send second information to the third access network device based on second parameters.

[0214] In some examples, when the third access network is a second relay device, the backhaul capability of the third access network device can also be considered as the backhaul capability of the second relay device. The backhaul capability of the second relay node may include the backhaul method adopted by the second relay node and / or QoS parameters related to the second MT. It can be understood that the backhaul capability of the second relay node is similar to that of the first relay node. For details, please refer to the description of the relevant embodiments of the backhaul capability of the first relay node, which will not be repeated here.

[0215] In some embodiments, the first condition may be that the terminal device has a communication connection with the first access network device, and then switches to having a communication connection with the third access network device. That is, the terminal device undergoes a switch of access network devices, from the first access network device to the third access network device. It is understood that this process can be controlled by the access network device. For example, when the terminal device is moving, the first access network device may determine that the terminal device is about to move to a location or area where the first access network device cannot provide service. In this case, the first access network device can determine the potential third access network device based on its specific implementation and control the switch of access network devices. This allows the terminal device to continue communication services through the third access network device after moving to the appropriate area.

[0216] In other embodiments, the first condition may be that the terminal device re-establishes an RRC connection to the third access network device. It is understood that this process can be controlled by the terminal device; for example, if the terminal device determines that the RRC link is broken or the RRC connection has failed, the terminal device determines to reconnect via RRC. It is understood that "reconnection" and "re-establishment" have the same meaning, both referring to re-establishing the RRC connection.

[0217] It is understood that when any of the above possible first conditions are met, the third access network device can send its backhaul capability to the first core network device so that the first core network device can re-determine the QoS parameters of the terminal device.

[0218] The embodiments of this application can enable more accurate and reasonable QoS parameters to be configured for terminal devices when switching or reconnecting to new access network devices.

[0219] In the QoS configuration method provided in this application embodiment, when the device sending the first information is a first access network device, the first information in S101 may also include a third parameter, which can be used to indicate that the access network device sending the first information is a first access network device of a first relay node.

[0220] For example, a WAB-gNB sends first information to a first core network device, which includes a third parameter. This third parameter can indicate that the gNB sending the first information is a WAB-gNB. Alternatively, the third parameter can indicate that the gNB sending the first information belongs to a WAB node. In this case, the first core network device can also be triggered to determine the QoS parameters between the terminal device and the first core network device, and the first core network device can send second information to the first access network device.

[0221] In other words, if the first core network device receives the third parameter, it can assume that the terminal device accessed the network through the first relay node. In this case, the first core network device can determine more reasonable QoS parameters for the terminal device.

[0222] Similarly, the third information sent by the third access network device can also include a fourth parameter. This fourth parameter can be used to indicate that the access network device sending the third information is the third access network device of the second relay node. For example, the fourth parameter can indicate that the gNB sending the third information is WAB-gNB.

[0223] In this embodiment of the application, when the first core network node determines that the device sending the first information or the third information is a relay device with access network device function and MT function, more accurate and reasonable QoS parameters can be configured for the terminal device.

[0224] Figure 7 is a schematic diagram of another QoS configuration method provided by an embodiment of this application.

[0225] This QoS configuration process can be applied to, but is not limited to, the communication scenarios shown in Figures 1 to 5. It can be understood that this QoS configuration method can configure QoS parameters between the first MT and the second access network device. The second access network device can be an access network device serving the first MT. In some examples, the second access network device can also be referred to as the serving access network device, serving base station, host access network device, host base station, host (donor), etc., of the first MT; this embodiment does not impose such limitations. It can be assumed that the second access network device and the first MT have a communication connection. In some examples, the second access network device can also be referred to as a WAB-donor, which can transmit the service data of the WAB-MT.

[0226] The method may include the following steps:

[0227] The following embodiments of this application will describe how the second access network device obtains the fourth information in different ways, such as method 1 and method 2.

[0228] Method 1:

[0229] S201, the first core network device sends the fourth information to the second core network device.

[0230] Accordingly, the second core network device receives fourth information from the first core network device. This fourth information can be used to indicate QoS parameters between the first access network device and the first core network device.

[0231] In some embodiments, referring to FIG8, the QoS parameters between the terminal device and the first relay node can be referred to as QoS 0, such as the QoS parameters between the UE and the WAB node. The QoS parameters between the first relay node and the second access network device can be referred to as QoS 1, such as the QoS parameters between the WAB node and the serving access network device of WAB-MT. The QoS parameters between the second access network device and the second core network device can be referred to as QoS 2, such as the QoS parameters between the serving access network device of WAB-MT and the core network device of WAB-MT. The QoS parameters between the second core network device and the first core network device can be referred to as QoS 3, such as the QoS parameters between the core network device of WAB-MT and the core network device of the UE. Therefore, the QoS parameters between the first access network device and the first core network device indicated by the fourth information can be considered as QoS 1 + QoS 2 + QoS 3.

[0232] In some examples, the first core network device can employ a QoS monitoring mechanism to determine the QoS parameters between the first access network device and the first core network device. It is understood that the specific implementation process of the QoS monitoring mechanism can refer to relevant technologies, and will not be elaborated upon here. Those skilled in the art should understand that a QoS monitoring mechanism can be used by a core network device to determine the QoS parameters between the core network device and a certain access network device. Wherein, the certain access network device and the core network device have a communication connection.

[0233] S202, the second core network device sends the fourth information to the second access network device.

[0234] Accordingly, the second access network device receives the fourth information from the second core network device. In other words, the second core network device can forward the fourth information received in S201 to the second access network device.

[0235] In some embodiments, the second core network device may also send the identification information of the first relay node to the second core network. The identification information of the first relay node may include the ID of the first access network device, the ID of the first MT, and / or the IP address of the first access network device, etc. In various embodiments of this application, the identification information may be carried in the same signaling as the fourth information, or may be carried in different signaling. This application does not limit this, and subsequent embodiments will not elaborate further.

[0236] Method 2:

[0237] S203, the first relay node sends the fourth information to the second access network device.

[0238] Accordingly, the second access network device receives fourth information from the first relay node. In some examples, the first access network device may send the fourth information to the second access network device. In other examples, the first MT may send the fourth information to the second access network device. In some examples, the first relay node may also send its identification information, such as the ID of the first access network device, the ID of the first MT, and / or the IP address of the first access network device, to the second access network device.

[0239] In some embodiments, the QoS parameters between the first access network device and the first core network device may be determined and communicated to the first relay node by the first core network device using a QoS monitoring mechanism before S203.

[0240] It is understandable that the process of the second access network device obtaining the fourth information can be carried out using either method 1 or method 2 mentioned above.

[0241] S204, the second core network device sends the seventh information to the second access network device.

[0242] Accordingly, the second access network device receives the seventh information from the second core network device. This seventh information can be used to indicate the QoS parameters between the first and second core network devices, such as QoS 3. In some examples, taking the first core network device as the UE's UPF and the second core network device as the WAB-MT's UPF, the UE's UPF and the WAB-MT's UPF can interact via IP routing. The QoS parameters of this IP route can be obtained by the WAB-MT's SMF. The specific implementation process of the WAB-MT's SMF obtaining the QoS parameters between the UE's UPF and the WAB-MT's UPF can be found in related technologies, and will not be elaborated upon here. The WAB-MT's SMF can send the obtained QoS parameters between the UE's UPF and the WAB-MT's UPF to the WAB-MT's AMF, so that the WAB-MT's AMF can send these QoS parameters to the second access network device. It can be understood that the QoS parameters between the UE's UPF and the WAB-MT's UPF are the aforementioned QoS 3.

[0243] It is understandable that, considering the second access network device may have already obtained QoS 3, or QoS 3 may be pre-configured in the second access network device, step S204 can be an optional step.

[0244] S205, the second access network device determines the QoS parameters between the first MT and the second access network device.

[0245] In some embodiments, the second access network device can obtain QoS 1+QoS 2+QoS 3 according to method 1 or method 2. The second access network device can pre-configure or pre-obtain QoS 3, or the second access network device can obtain QoS 3 based on S204. In some examples, the second core network device can also use a QoS monitoring mechanism to determine QoS 2 and inform the second access network device of QoS 2. Therefore, the second access network device can determine the QoS parameters between the first MT and the second access network device, i.e., QoS 1, based on QoS 1+QoS 2+QoS 3, QoS 3, and QoS 2.

[0246] In some examples, the second access network device can configure the data radio bearer (DRB) corresponding to the first MT according to QoS 1. The QoS parameters corresponding to this DRB can meet the QoS requirements between the terminal device and the first core network device.

[0247] In this embodiment of the application, the QoS parameters between the first MT and the second access network device can be configured by the second access network device, so that the DRB configured based on the QoS parameters can meet the QoS requirements between the terminal device and the first core network device.

[0248] Figure 9 is a schematic diagram of another QoS configuration method provided by an embodiment of this application.

[0249] This QoS configuration process can be applied to, but is not limited to, the communication scenarios shown in Figures 1 to 5. It can be understood that this QoS configuration method can configure QoS parameters between the first MT and the second access network device. The method may include the following steps:

[0250] The following embodiments of this application will describe how the second core network device obtains the fourth information in different ways, such as method 3 and method 4.

[0251] Method 3:

[0252] S301, the first core network device sends the fourth information to the second core network device. Correspondingly, the second core network device receives the fourth information from the first core network device.

[0253] It is understood that the implementation process of S301 is similar to that of S201. For details, please refer to the description of S201. The embodiments of this application will not be repeated here.

[0254] Method 4:

[0255] S302, the first relay node sends the fourth message to the second core network device. Correspondingly, the second core network device receives the fourth message from the first relay node.

[0256] In some examples, the first MT may send fourth information to the second access network device. In some examples, the first relay node may also send its identification information, such as the ID of the first access network device, the ID of the first MT, and / or the IP address of the first access network device, to the second core network device.

[0257] It is understood that the implementation process of S302 is similar to that of S203, the difference being that the device receiving the fourth information is different. For details, please refer to the description of S203. The embodiments of this application will not be repeated here.

[0258] It should be understood that the process of the second core network device obtaining the fourth information can be carried out using one of the methods described above, either method 3 or method 4.

[0259] The following embodiments of this application will describe, through Case 1 and Case 2, how the second core network device participates in the process of determining the QoS parameters between the first MT and the second access network device.

[0260] Scenario 1:

[0261] S303, the second core network device obtains the QoS parameters between the second access network device and the second core network device, as well as the QoS parameters between the first core network device and the second core network device.

[0262] In some examples, the second core network device can acquire QoS 2 and QoS 3. Of course, the specific acquisition process for QoS 2 and QoS 3 can be found in the description of the foregoing embodiments, and will not be repeated here.

[0263] S304, the second core network device determines the QoS parameters between the first MT and the second access network device based on the QoS parameters between the first access network device and the first core network device, the QoS parameters between the second access network device and the second core network device, and the QoS parameters between the first core network device and the second core network device.

[0264] In some examples, the second core network device can determine QoS 1 based on QoS 2 and QoS 3 obtained in S303, and QoS 1+QoS 2+QoS 3 obtained in S301 or S302. This implementation process is similar to S205, the difference being the executing entity, and will not be described in detail in the embodiments of this application.

[0265] S305, the second core network device sends the ninth information to the second access network device.

[0266] Accordingly, the second access network device receives the ninth information from the second core network device. This ninth information can be used to indicate QoS parameters between the first MT and the second access network device, such as QoS 1.

[0267] This application embodiment can configure the QoS parameters between the first MT and the second access network device through the second core network device, which can reduce the computing power requirements of the access network device.

[0268] Scenario 2:

[0269] S306, the second core network device obtains the QoS parameters between the first core network device and the second core network device.

[0270] In some examples, the second core network device can obtain QoS 3. The specific process for obtaining QoS 3 can be found in the description of the foregoing embodiments, and will not be repeated here.

[0271] S307, the second core network device determines the QoS parameters between the first MT and the second core network based on the QoS parameters between the first access network device and the first core network device, and the QoS parameters between the first core network device and the second core network device.

[0272] In some cases, the second core network device can determine QoS 1+QoS 2 based on QoS 3 obtained in S303 and QoS 1+QoS 2+QoS 3 obtained in S301 or S302.

[0273] S308, the second core network device sends the eighth information to the second access network device.

[0274] Accordingly, the second access network device receives the eighth information from the second core network device. This eighth information can be used to indicate the QoS parameters between the first MT and the second core network, such as QoS 1 + QoS 2.

[0275] S309, the second access network device determines the QoS parameters between the first MT and the second access network device based on the eighth information.

[0276] In some embodiments, the second access network device can determine QoS 1 based on QoS 1 + QoS 2 and QoS 2 obtained in S308. The process by which the second access network device obtains QoS 2 can be referred to the description in the foregoing embodiments, and will not be repeated here.

[0277] This application embodiment can configure the QoS parameters between the first MT and the second core network device through the second core network device, so that the access network device can determine the QoS parameters between the first MT and the second access network device based on the QoS parameters, thereby reducing the computational load of the access network device and reducing the demand on the computing power of the access network device.

[0278] Figure 10 is a schematic diagram of a core network device switching method provided in an embodiment of this application.

[0279] This core network device handover process can be applied to, but is not limited to, the communication scenarios shown in Figures 1 to 5. It can be understood that this core network device handover method can be applied to the process of switching a first core network device to another core network device. Considering scenarios involving terminal device movement, the first core network device providing services to the terminal device may become unsuitable for providing services due to the terminal device's movement; therefore, switching the first core network device can be considered. This method may include the following steps:

[0280] S401, the first core network device determines the fourth core network device.

[0281] In some cases, the first core network device can determine the fourth core network device. For example, the first core network device determines that a terminal device needs to switch core network devices and identifies a fourth core network device that can provide services to the terminal device. For instance, if the terminal device is moving, the first core network device can determine that the terminal device may soon move out of its service range, meaning it will no longer be able to provide services to the terminal device. The first core network device can then determine a new core network device, such as a fourth core network device, based on the direction of the terminal device's movement.

[0282] In other cases, if a terminal device performs backhaul communication through a first relay node during its movement, a handover of the second core network device may occur. In this situation, the first core network device can also trigger a handover based on the handover of the second core network device. The first core network device can determine a new core network device, such as a fourth core network device.

[0283] In some embodiments, the fourth core network device may be a new AMF or UPF that provides services to terminal devices.

[0284] S402, the first core network device sends the tenth information to the first relay node.

[0285] Accordingly, the first relay node receives the tenth information from the first core network device. This tenth information can be used to instruct the fourth core network device. In some examples, the first access network device, belonging to the first relay node, may receive the tenth information from the first core network device. This allows the first access network device to perform a core network device handover based on the tenth information. For example, the first access network device can establish a communication interface with the fourth core network device. Alternatively, if a communication interface has already been established between the first access network device and the fourth core network device, the first access network device can perform a terminal device handover to achieve a core network device handover. That is, the first access network device switches its interface with the first core network device to its interface with the fourth core network device.

[0286] In some embodiments, the first core network device may also send tenth information to the second core network device, so that the second core network device can perform a handover based on the tenth information. This implementation process can be referred to the description of the embodiment in FIG11 below.

[0287] In this embodiment, the first core network device can actively trigger the switching of the core network device and notify the first access network device connected to it, so that the first access network device can switch the core network device in a timely manner and avoid the situation where the core network device cannot provide services to the terminal device.

[0288] In the core network device handover method provided in this application embodiment, for the handover of the first core network device based on the handover of the second core network device, the first core network device is triggered to perform a handover. The method may further include: the first core network device receiving fifth information from the first access network device or the second core network device. The first core network device determining the fourth core network device may include: determining the fourth core network device based on the fifth information.

[0289] In some embodiments, the first access network device or the second core network device may determine a third core network device, which may be a core network device providing services to the first MT. It can be assumed that the first MT needs to switch from being connected to the second core network device to being connected to the third core network device. The first access network device or the second core network device may send fifth information to the first core network device, which may be used to instruct the third core network device. Based on the fifth information, the first core network device determines that the first MT needs to switch core network devices, causing the first core network device to trigger the determination of a fourth core network device.

[0290] In some cases, the second core network device can determine the third core network device based on implementation changes, such as when the first relay node connected to the terminal device changes, for example, switching to a third access network device. In such cases, the third access network device may not be suitable for communication with the second core network device, and the second core network device can determine the third core network device, which may be more suitable for communication with the third access network device. In other cases, the first relay node may still be connected to the terminal device, but it may also be moving. In such cases, the second core network device may no longer be suitable for communication with the first relay node, thus triggering the second core network device to determine the third core network device.

[0291] In other examples, where the first relay node remains connected to the terminal device, one scenario is that the second core network device, after identifying the third core network device, can inform the first MT of the third core network device's information. The first MT then informs the first access network device of the third core network device's information through the internal communication process of the first relay node. Another scenario is that the second access network device is actually aware of the switch from the second core network device to the third core network device. This is because the first relay node interacts with the second core network device through the backhaul link of the second access network device. Therefore, the device actually connected to the second core network device is the second access network device. In this case, the second access network device can inform the first MT of the third core network device's information or through the Xn interface between access network devices. If the second access network device informs the first MT of the third core network device's information, the first MT informs the first access network device of the third core network device's information through its internal communication process, ensuring that the first access network device is aware of the third core network device's information.

[0292] This application embodiment can trigger the switching of the core network equipment providing services to the terminal equipment when the core network equipment providing services to the first MT is switched, thereby realizing timely switching of core network equipment, improving communication efficiency, and avoiding the situation where the core network equipment cannot provide services to the terminal.

[0293] Figure 11 is a schematic diagram of another core network device switching method provided by an embodiment of this application.

[0294] This core network device handover process can be applied to, but is not limited to, the communication scenarios shown in Figures 1 to 5. It can be understood that this core network device handover method can be applied to the process of switching a second core network device to another core network device. Considering the scenario where the first relay node may move, the second core network device providing services to the first MT may no longer be suitable for providing services to the first MT due to the movement of the first MT. Therefore, switching the second core network device can be considered. This method may include the following steps:

[0295] S501, the second core network equipment determines the third core network equipment.

[0296] In some instances, the second core network device can determine the third core network device. For example, the second core network device may determine that the first MT needs to switch core network devices and identify a third core network device that can provide services to the first MT. In other instances, a switchover of the first core network device may occur during the movement of the first MT. In this case, the second core network device can also trigger a switchover of its own device based on the switchover of the first core network device.

[0297] In some embodiments, the third core network device may be a new AMF or UPF, etc., that provides services to the first MT.

[0298] It is understood that the implementation process of S501 is similar to that of S401. Please refer to the description related to S401. The embodiments of this application will not be repeated here.

[0299] S502, the second core network device sends the fifth information to the second access network device.

[0300] Accordingly, the second access network device receives fifth information from the second core network device. This fifth information can be used to instruct the third core network device. In some examples, the second access network device performs a core network device handover based on the fifth information. For instance, the second access network device may establish a communication interface with the third core network device. Alternatively, if a communication interface has already been established between the second access network device and the third core network device, the second access network device may perform a communication interface handover to achieve the core network device handover. That is, the second access network device switches its interface with the second core network device to its interface with the third core network device.

[0301] In this embodiment, the second core network device can actively trigger the switching of the core network device and notify the second access network device connected to it. This allows the second access network device to switch the core network device in a timely manner, avoiding a situation where the core network device cannot provide services to the first MT.

[0302] In the core network device handover method provided in this application embodiment, the handover of the second core network device is triggered based on the handover of the first core network device. The method may further include: the second core network device receiving tenth information from the first MT or the first core network device. The second core network device determining the third core network device may include: determining the third core network device based on the tenth information.

[0303] In some embodiments, the first MT or the first core network device can determine the fourth core network device. It can be assumed that the terminal device needs to switch from being connected to the first core network device to being connected to the fourth core network device. The first access network device or the first core network device can send tenth information to the second core network device, which can be used to instruct the fourth core network device. Based on the tenth information, the second core network device determines that the terminal device needs to switch core network devices, causing the second core network device to trigger the determination of the third core network device.

[0304] In some examples, the first core network device can determine the fourth core network device based on implementation details, as described in the aforementioned embodiments, which will not be repeated here. In other examples, the first relay node can determine the fourth core network device. Considering that the first access network device, which has a communication connection with the terminal device, also participates in the process of switching from the first core network device to the fourth core network device, such as the first access network device re-establishing its communication interface with the fourth core network device, it can be assumed that the first access network device is aware that the first core network device has switched to the fourth core network device. The first access network device can inform the first MT of the fourth core network information through internal communication within the first relay node, so that the first MT can send the tenth information to the second core network device.

[0305] This application embodiment can trigger the switching of the core network equipment providing services to the first MT when the core network equipment providing services to the terminal equipment is switched, thereby realizing timely switching of the core network equipment, improving communication efficiency, and avoiding the situation where the core network equipment cannot provide backhaul services to the terminal.

[0306] Figure 12 is a schematic diagram of a core network device synchronization method provided in an embodiment of this application.

[0307] The core network device synchronization process can be applied to, but is not limited to, the communication scenarios shown in Figures 1 to 5. In any of the above embodiments, communication between the first core network and the second core network considers that the first core network device needs to know the information of the second core network device in advance before it can send relevant information to the second core network device. Therefore, the first core network device can obtain the information of the second core network device using the method shown in Figure 12. The information of the second core network device can be used to identify the second core network device. This method may include the following steps:

[0308] S601, the second access network device or the second core network device sends the eleventh message to the first relay node.

[0309] Accordingly, the first relay node receives eleventh information from the second access network device or the second core network device. This eleventh information can be used to instruct the second core network device. It is understood that if the first MT does not know which core network device it is connected to, the second core network device can inform the first MT of its own information. Of course, the second access network device typically maintains this information regarding which core network device the first MT is connected to. Therefore, the second access network device can also inform the first MT of information from the second core network device.

[0310] Of course, S601 can be an optional step. That is to say, the first MT may also know in advance which core network devices it is connected to, that is, the first MT may know in advance the ID, IP address, etc. of the core network devices it is connected to.

[0311] S602, the first relay node sends the sixth message to the first core network device.

[0312] Accordingly, the first core network device receives sixth information from the first relay node. This sixth information can be used to indicate the second core network device. For example, the sixth information may include information indicating the second core network device and information indicating the first MT. The information indicating the second core network device may include the ID and / or IP address of the second core network device. The information indicating the first MT may include the ID and / or IP address of the first MT.

[0313] In some cases, considering that the sixth information may be sent by the first access network device, the sixth information may also carry information for indicating the first access network device, such as the ID of the first access network device.

[0314] In this embodiment, the first core network device can obtain relevant information about the second core network device so as to communicate with the second core network device based on the information, thereby improving communication efficiency.

[0315] Figure 13 is a schematic diagram of another core network device synchronization method provided by an embodiment of this application.

[0316] The core network device synchronization process can be applied to, but is not limited to, the communication scenarios shown in Figures 1 to 5. In any of the above embodiments, communication between the first core network and the second core network considers that the second core network device needs to know the information of the first core network device in advance before it can send relevant information to the first core network device. Therefore, the second core network device can obtain the information of the first core network device using the method shown in Figure 13. The information of the first core network device can be used to identify the first core network device. This method may include the following steps:

[0317] S701, the first relay node sends the twelfth message to the second core network device.

[0318] Accordingly, the second core network device receives twelfth information from the first relay node. This twelfth information can be used to indicate the first core network device. For example, the twelfth information may include information indicating the first core network device and information indicating the first access network device. The information indicating the first core network device may include the ID and / or IP address of the first core network device. The information indicating the first access network device may include the ID and / or IP address of the first access network device.

[0319] In some cases, considering that the twelfth message may be sent by the first MT, the twelfth message may also carry information for indicating the first MT, such as the ID of the first MT.

[0320] In this embodiment, the second core network device can obtain relevant information about the first core network device so as to communicate with the first core network device based on the information, thereby improving communication efficiency.

[0321] The following embodiments of this application will be described in more detail using the following examples: the first relay device is a WAB node, the first access network device is a WAB-gNB, the first MT is a WAB-MT, the first core network device is the UE's AMF, the second core network device is the WAB-MT's AMF, and the second access network device is a WAB-donor.

[0322] Figure 14 is a schematic diagram of another core network device synchronization method provided by an embodiment of this application.

[0323] It is understandable that the AMF of the WAB-MT and the AMF of the UE generally do not interact. Therefore, the core networks need to be aware of each other's presence so that they can send information to each other in some schemes. The core network device synchronization process includes Scheme 1 and Scheme 2, where Scheme 1 is used for synchronizing the AMF of the WAB-MT with the AMF of the UE, and Scheme 2 is used for synchronizing the AMF of the UE with the AMF of the WAB-MT. Scheme 1 and Scheme 2 will be described separately below, and the method may include the following steps:

[0324] Option 1:

[0325] S801, WAB-MT sends the twelfth message to WAB-MT's AMF.

[0326] Accordingly, the AMF of the WAB-MT receives the twelfth piece of information from the WAB-MT. In some embodiments, the AMF of the UE can also be considered as the AMF of the WAB-gNB. Since the WAB-MT and the WAB-gNB belong to the same node, such as the WAB node, it can be assumed that the WAB-MT knows the relevant information of the UE's AMF.

[0327] In some cases, WAB-MT can send a twelfth message to its AMF via the WAB-donor. This twelfth message can be a non-access stratum (NAS) message. This NAS message can be considered as being transparently transmitted to the WAB-MT's AMF via the WAB-donor. The WAB-donor will not process this NAS message.

[0328] In other examples, the S801 can send radio resource control (RRC) messages to the WAB-donor via the WAB-MT, and the WAB-donor can then send NG application protocol (AP) messages to the AMF of the WAB-MT.

[0329] In some examples, the twelfth piece of information may indicate the ID of the UE's AMF and / or the IP address of the UE's AMF. The twelfth piece of information may also include the ID of the WAB-gNB and / or the IP address of the WAB-gNB to indicate which WAB-gNB the UE's AMF is associated with.

[0330] In other examples, since the twelfth piece of information is sent by the WAB-MT, it may also include the WAB-MT's ID. For instance, the WAB-MT's ID could be a temporary mobile subscriber identity (TMSI), a generic public subscription identifier (GPSI), or a subscription permanent identifier (SUPI) transmitted in the NAS message. Alternatively, the WAB-MT's ID could be a cell radio network temporary identifier (C-RNTI) carried in the RRC message, or it could be an NGAP UE ID. It's understandable that the NGAP UE ID can be used to indicate the WAB-MT because the WAB-MT can be considered a special type of UE.

[0331] It is clear that the AMF of the WAB-MT can determine, based on the twelfth information, that the WAB-MT is associated with a gNB, the identifier of the gNB, and the AMF connected to the gNB, i.e., the AMF of the UE.

[0332] Of course, the specific implementation process of Scheme 1 can be referred to the various embodiments corresponding to Figure 13, and the embodiments of this application will not be repeated here.

[0333] Option 2:

[0334] S802, the AMF or WAN-donor of WAB-MT sends the eleventh message to WAB-MT.

[0335] Accordingly, the WAB-MT receives the eleventh message from its AMF or WAN-donor. In some examples, the eleventh message can be implemented by the WAB-MT's AMF sending a NAS message to the WAB-MT. Alternatively, the eleventh message can be implemented by the WAB-MT's AMF sending an NGAP message to the WAB-donor, and the WAB-donor sending an RRC message to the WAB-MT. It can be understood that the message types in S802 are similar to those in S801, but the content is different; therefore, they can be considered different RRC messages, different NGAP messages, and different NAS messages. This eleventh message may include the ID of the WAB-MT's AMF and / or the IP address of the WAB-MT's AMF.

[0336] It's understandable that the WAB-MT might not know which AMF it's connected to. However, the WAB-MT's serving base station can maintain this information. Therefore, the WAB-MT's AMF information can be communicated to it through its AMF or WAN-donor.

[0337] Of course, S802 can also be an optional step, and WAB-MT can also learn about the ID, IP address and other information of WAB-MT's AMF when establishing a connection with WAB-MT's AMF.

[0338] S803, WAB-gNB sends the sixth message to the UE's AMF.

[0339] Accordingly, the UE's AMF receives the sixth information from the WAB-gNB. In some cases, since the WAB-gNB and WAB-MT belong to the same node, it can be assumed that the information received by WAB-MT in S802 can also be obtained by the WAB-gNB. The WAB-gNB can send an NG message to the UE's AMF, which can carry the ID of the WAB-MT's AMF and / or the IP address of the WAB-MT's AMF. The NG message can also carry TMSI, GPSI, SUPI, NGAP UE ID, etc., to indicate which WAB-MT the AMF belongs to.

[0340] In other examples, since the sixth piece of information is sent by the WAB-gNB, it may also include the WAB-gNB's ID and / or IP address.

[0341] It is clear that the UE's AMF can determine, based on the sixth information, that the WAB-gNB is associated with an MT, the identifier of the MT, and the AMF connected to the MT, i.e., the AMF of the WAB-MT.

[0342] Of course, the specific implementation process of Scheme 2 can be referred to the various embodiments corresponding to Figure 12, and the embodiments of this application will not be repeated here.

[0343] As can be seen from Figure 14, Schemes 1 and 2 enable the AMF of the WAB-MT to detect the presence of the AMF of the UE, and / or the AMF of the UE to detect the presence of the AMF of the WAB-MT, so that information can be exchanged between the two AMFs.

[0344] Figure 15 is a schematic diagram of another QoS configuration method provided by an embodiment of this application.

[0345] The QoS configuration process can involve the UE's AMF configuring QoS parameters for the UE, and this method may include the following steps:

[0346] In this embodiment of the application, the UE's AMF can obtain the first information through scheme 3 or scheme 4, so as to configure the corresponding QoS parameters for the UE.

[0347] Option 3:

[0348] S901, WAB determines the WAB's backhaul capability.

[0349] In some examples, the WAB node can determine its own backhaul method, i.e., the backhaul method used by the WAB-MT, such as NTN backhaul or TN backhaul. TN backhaul can also mean that NTN backhaul is not used. S901 can be executed when the backhaul method used by the WAB changes, or S901 can be executed when the WAB node first accesses the network; this embodiment of the application does not limit this.

[0350] S902, WAB-gNB sends the first information to the UE's AMF.

[0351] Accordingly, the UE's AMF receives the first information from the WAB-gNB. In some examples, this first information may indicate the backhaul method used by the WAB-MT. In other examples, the first information may also indicate that the gNB sending the first information uses a WAB architecture, i.e., the gNB is a WAB-gNB. In this case, S901 can be an optional step, i.e., S901 can be omitted. It is understood that either or more of these two cases can trigger the UE's AMF to configure QoS parameters for the UE.

[0352] In some examples, the first message can be an interface-level message, such as an NG setup request message when the WAB-gNB establishes an NG interface with the UE's AMF, or a RAN configuration update message used to update the NG interface configuration. In other examples, the first message can be a UE-level message, such as an NG message used to establish or modify the PDU session configuration for the UE.

[0353] For interface-level messages, the WAB-gNB can be triggered to send the first message to the UE's AMF even before the UE is connected to the WAB-gNB. This message informs the AMF of any potential UE which backhaul method the gNB will use, i.e., which backhaul method subsequent UEs connecting to the gNB will use. For UE-level messages, the WAB-gNB needs to wait until the UE connects to the gNB before sending the first message to the UE's AMF to inform the UE which backhaul method it will use.

[0354] In some examples, the initial information may also carry QoS parameters related to WAB-MT, such as QoS 1, QoS 1+QoS2, etc. This can be used by the UE's AMF as a reference when configuring QoS parameters for the UE.

[0355] Option 4:

[0356] S903, the AMF of WAB-MT determines the backhaul capability of WAB.

[0357] In some examples, the AMF of the WAB-MT can determine the backhaul method used by the WAB-MT. It is understood that in the various embodiments of this application, the backhaul method used by the UE, the backhaul method used by the WAB-gNB, and the backhaul method used by the WAB-MT can be understood to have the same meaning.

[0358] It is understood that the process of S903 is similar to that of S901. For details, please refer to the description of S901. The embodiments of this application will not be repeated here.

[0359] S904, the AMF of WAB-MT sends the first message to the AMF of UE.

[0360] Accordingly, the UE's AMF receives first information from the WAB-MT's AMF. In some cases, this first information may indicate the backhaul method used by the WAB-MT. In other cases, the first information may also indicate the WAB-gNB's ID, the WAB-gNB's IP address, and / or the WAB-MT's ID. For example, the first information may indicate the WAB-gNB's ID and IP address because these parameters are recognizable by the UE's AMF. Of course, if the first information indicates the WAB-MT's ID, then the UE's AMF needs to know the binding relationship between the WAB-MT and the WAB-gNB.

[0361] In some examples, the first information may also carry QoS parameters related to WAB-MT, such as QoS 1, QoS 1+QoS 2, etc.

[0362] It should be understood that Scheme 1 in Figure 14 can be executed before S904 so that the AMF of WAB-MT is aware of the existence of the AMF of UE and can interact with the AMF of UE.

[0363] Through scheme 3 or scheme 4 above, the UE's AMF can obtain the first information in order to execute subsequent steps.

[0364] S905, the UE's AMF sends the second information to the WAB-gNB.

[0365] Accordingly, the WAB-gNB receives the second information from the UE's AMF. In some examples, the UE's AMF can configure corresponding QoS parameters for the UE based on the backhaul method adopted by the UE and / or whether WAB access is available, such as QoS 0+QoS 1+QoS 2+QoS 3. This QoS parameter is then communicated to the WAB-gNB so that the WAB-gNB can set the DRB between the WAB-gNB and the UE based on this parameter.

[0366] In some examples, the second information can be carried by the request message via a PDU session resource.

[0367] In some possible embodiments, considering that the UE may undergo gNB handover (HO) or RRC re-establishment to a new gNB during mobility, the new gNB may be the aforementioned third access network device. In this case, the new gNB may also indicate its backhaul capabilities to the UE's AMF, so that the UE's AMF can indicate the UE's QoS parameters to the new gNB. Therefore, embodiments of this application may further include the following optional steps:

[0368] S906, the UE switches the access network device it is connected to.

[0369] In some cases, the UE can perform a gNB handover, such as switching from the WAB-gNB to the UE's new gNB. The UE's new gNB can also belong to a specific WAB node. Alternatively, the UE may decide to perform an RRC re-establishment to the UE's new gNB.

[0370] S907, the UE's new gNB sends third information to the UE's AMF.

[0371] Accordingly, the UE's AMF receives third information from the UE's new gNB. In some cases, this third information is similar to the first information, except that it indicates the UE's new gNB's backhaul capability and / or indicates whether the UE's new gNB is a gNB of the WAB.

[0372] In some examples, this third information may be carried in a path switch request message or in a PDU session resource modification indication.

[0373] S908, the UE's AMF sends a second message to the UE's new gNB.

[0374] Accordingly, the UE's new gNB receives the second information from the UE's AMF. It can be understood that the second information in S908 can be generated based on the third information. The implementation process of S908 is similar to that of S905, the difference being the receiver; for details, please refer to the description of S905, which will not be repeated here in this application's embodiments.

[0375] It is understood that the specific implementation process of each step in Figure 15 can be referred to the description of the relevant embodiments in Figure 6, and the embodiments of this application will not be repeated here.

[0376] Using the scheme shown in Figure 15, the UE's AMF can configure more reasonable QoS parameters for the UE based on the UE's backhaul method.

[0377] Figure 16 is a schematic diagram of another QoS configuration method provided by an embodiment of this application.

[0378] This embodiment of the application considers that the QoS parameters between the UE and its UPF can be divided into multiple QoS parameter segments as shown in Figure 8. Taking PDB as an example of QoS parameters, QoS 2 and QoS 3 are PDBs for core network communication, which can be provided through the wired network and objectively determined by the network status. QoS 0 and QoS 1 are for air interface wireless communication, and this PDB is related to the allocation of air interface resources. Therefore, the WAB-donor needs to configure reasonable air interface resources for the WAB-MT to ensure that the QoS parameters between the UE and its UPF are satisfied.

[0379] The allocation of air interface resources can be continuously adjusted according to changes in services. For example, during the initial network setup phase, the WAB-gNB can establish a default DRB for the UE, and the WAB-donor can also establish a default DRB for the WAB-MT. Of course, with changes in the number of UEs accessing the network, the number of services, and the potential impact of UE mobility, the resource configuration corresponding to the DRB may also need to be dynamically adjusted.

[0380] In some examples, for adjustments to QoS 0, the UE's AMF can employ a QoS monitoring mechanism to measure the PDB between the UE's serving gNB (i.e., WAB-gNB) and the UE's UPF, such as QoS 1+QoS 2+QoS 3. The UE's AMF can then inform the WAB-gNB of QoS 1+QoS 2+QoS 3. When QoS parameters for the UE's PDU session need to be added or modified, the UE's AMF can configure QoS 0+QoS 1+QoS 2+QoS 3 and inform the WAB-gNB of QoS 0+QoS 1+QoS 2+QoS 3. The WAB-gNB can then determine QoS 0 based on QoS 0+QoS 1+QoS 2+QoS 3 and QoS 1+QoS 2+QoS 3.

[0381] Regarding QoS 1, considering that the serving gNB of the WAB-MT, i.e., the WAB-donor, is unaware of the QoS parameters between the UE and its UPF, as well as the QoS parameters between the WAB-donor and the UE's UPF, the WAB-donor cannot obtain QoS 1 and cannot guarantee the end-to-end QoS parameters of the UE. Based on this, the embodiments of this application solve this problem through the method shown in Figure 16. This method may include the following steps:

[0382] This application describes how to determine QoS 1 through Scheme 5 and Scheme 6. The difference between Scheme 5 and Scheme 6 is that the WAN-MT AMF in Scheme 5 is not used to calculate QoS parameters, while the WAN-MT AMF in Scheme 6 is used to calculate QoS parameters.

[0383] For option 5:

[0384] This application provides two different methods for the WAB-donor to obtain fourth information for determining QoS 1, such as scheme 5.1 or scheme 5.2.

[0385] Option 5.1:

[0386] S1001, the UE's AMF sends the fourth message to the WAB-MT's AMF.

[0387] Accordingly, the AMF of the WAB-MT receives fourth information from the AMF of the UE. In some cases, this fourth information is used to indicate the QoS parameters between the WAB-gNB and the UPF of the UE, such as QoS 1 + QoS 2 + QoS 3.

[0388] It is understandable that Scheme 2 in Figure 14 can be executed before S1001 so that the UE's AMF knows the WAB-MT's AMF and that the UE's AMF and the WAB-MT's AMF can interact.

[0389] S1002, WAB-MT's AMF sends the fourth message to WAB-donor.

[0390] Accordingly, the WAB-donor receives the fourth information from the AMF of the WAB-MT. In some examples, the AMF of the WAB-MT may also send the ID of the WAB-gNB, the IP address of the WAB-gNB, and / or the ID of the WAB-MT to the WAB-donor to indicate which WAB the fourth information is for. It is understood that the WAB-donor can connect to multiple WAB nodes.

[0391] It can be assumed that Scheme 5.1 is WAB-MT's AMF informing WAB-donor of the fourth information.

[0392] Option 5.2:

[0393] S1003, the WAB node sends the fourth message to the WAB-donor.

[0394] Accordingly, the WAB-donor receives a fourth piece of information from the WAB node. In some examples, this fourth piece of information can be implemented by the WAB-gNB sending an Xn message to the WAB-donor. In other examples, this fourth piece of information can be implemented by the WAB-MT sending an RRC message to the WAB-donor. In some examples, the Xn message or RRC message may also carry the WAB-gNB ID, the WAB-gNB IP address, and / or the WAB-MT ID to indicate which WAB the fourth piece of information is intended for.

[0395] It can be assumed that Scheme 5.2 involves the WAB node informing the WAB-donor of the fourth piece of information.

[0396] In the various embodiments of this application, the QoS parameters indicated by the fourth information can be understood as the QoS requirements between the WAB-gNB and the UE's UPF. It can be considered that the scenario in this embodiment is that the DRB between the WAB-MT and the WAB-donor has been established, but some UEs may access the WAB-gNB. This will cause the DRB configuration between the WAB-MT and the WAB-donor to need adjustment. Optionally, in this process, the DRB configuration between the WAB-gNB and the UE can be considered fixed. The WAB-MT's AMF needs to know the QoS requirements between the WAB-gNB and the UE's UPF, and based on these QoS requirements, configure reasonable QoS parameters for the WAB-MT to the WAB-donor. This is to adjust the DRB configuration between the WAB-MT and the WAB-donor to meet the QoS requirements in the fourth information.

[0397] S1004, WAB-MT's AMF sends the seventh message to WAB-donor.

[0398] Accordingly, the WAB-donor receives the seventh information from the AMF of the WAB-MT. This seventh information can indicate QoS 3. It is understood that the AMF of the WAB-MT and the AMF of the UE communicate via IP routing. The QoS parameters corresponding to this IP route, i.e., QoS 3, can be obtained by the SMF of the WAB-MT, and this QoS 3 can be communicated to the AMF of the WAB-MT. In some examples, the AMF of the WAB-MT can also send the ID of the WAB-gNB, the IP address of the WAB-gNB, and / or the ID of the WAB-MT to the WAB-donor to indicate which WAB the seventh information is for.

[0399] It is worth noting that S1004 is an optional step, and QoS 3 can also be pre-configured in the WAB-donor. This embodiment of the application does not limit this.

[0400] S1005, WAB-donor determines the QoS parameters between WAB-MT and WAB-donor.

[0401] In some cases, the WAB-donor can determine QoS 2 through a QoS monitoring mechanism. For example, the AMF of the WAB-MT uses a QoS monitoring mechanism to measure QoS 2 and informs the WAB-donor of this QoS 2. The WAB-donor can determine QoS 1 based on QoS 1 + QoS 2 + QoS 3 obtained from Scheme 5.1 or Scheme 5.2, QoS 3 obtained or pre-configured by S1004, and QoS 2.

[0402] It is understood that the specific implementation process of each step in Scheme 5 can be referred to the description of the relevant embodiments in Figure 7, and the embodiments of this application will not be repeated here.

[0403] For option 6:

[0404] S1006, the UE's AMF or WAB-MT sends the fourth information to the WAB-MT's AMF.

[0405] Accordingly, the AMF of WAB-MT receives the fourth information from the AMF of UE or WAB-MT. It can be understood that, in the case where the AMF of UE sends the fourth information to the AMF of WAB-MT, Scheme 2 in Figure 14 can be executed before S1006, so that the AMF of UE knows the AMF of WAB-MT, and that the AMF of UE and the AMF of WAB-MT can interact.

[0406] In some cases, the UE's AMF or WAB-MT can also send the WAB-gNB ID, the WAB-gNB IP address, and / or the WAB-MT ID to the WAB-MT's AMF to indicate which WAB this fourth piece of information is for.

[0407] In this embodiment of the application, the AMF of WAB-MT can participate in the calculation of QoS parameters to different degrees, which will be described in Scheme 6.1 and Scheme 6.2 respectively.

[0408] Option 6.1:

[0409] S1007, the AMF of WAB-MT obtains the QoS parameters between WAB-donor and WAB-MT's AMF, as well as the QoS parameters between the UE's AMF and WAB-MT's AMF. For example, the AMF of WAB-MT obtains QoS 2 and QoS 3.

[0410] S1008, WAB-MT determines the QoS parameters between WAB-MT and WAB-donor. For example, WAB-MT's AMF determines QoS 1 based on QoS 1 + QoS 2 + QoS 3, QoS 2, and QoS 3.

[0411] S1009, WAB-MT's AMF sends the ninth message to WAB-donor.

[0412] Accordingly, the WAB-donor receives the ninth message from the AMF (Active Message Function) of the WAB-MT. In some cases, this ninth message may be an NG (Not Required) message, such as a PDU (Personal Data Unit) session resource modification request. This ninth message is used to indicate QoS 1.

[0413] Option 6.2:

[0414] S1010, the AMF of the WAB-MT obtains the QoS parameters between the AMF of the UE and the AMF of the WAB-MT. For example, the AMF of the WAB-MT obtains QoS 3.

[0415] S1011, WAB-MT determines the QoS parameters between WAB-MT and its AMF. For example, WAB-MT's AMF determines QoS 1+QoS 2 based on QoS 1+QoS 2+QoS 3 and QoS 3.

[0416] S1012, WAB-MT's AMF sends the eighth message to WAB-donor.

[0417] Accordingly, the WAB-donor receives the eighth message from the AMF (Active Message Function) of the WAB-MT. In some cases, this eighth message may be an NG (Not Required) message, such as a PDU (Personal Data Unit) session resource modification request. This eighth message is used to indicate QoS 1+QoS 2.

[0418] S1013, WAB-donor determines the QoS parameters between WAB-MT and WAB-donor based on the eighth information.

[0419] For example, the WAB-donor determines QoS 1 based on QoS 1 + QoS 2 and QoS 2. The method by which the WAB-donor obtains QoS 2 can be referred to the description in the foregoing embodiments, and will not be repeated here.

[0420] It is understood that the specific implementation process of each step in Scheme 6 can be referred to the description of the relevant embodiments in Figure 9, and the embodiments of this application will not be repeated here.

[0421] S1014, WAB-donor configures the DRB between WAB-MT and WAB-donor.

[0422] For example, the WAB-donor configuration configures the radio bearer between WAB-MT and WAB-donor according to QoS 1.

[0423] In the method shown in Figure 16 above, QoS 0 can be assumed to remain unchanged during the determination of QoS 1. This process of determining QoS parameters allows the WAB-donor to know the air interface QoS parameters that can guarantee the end-to-end QoS of the UE, thereby enabling the WAB-MT to configure the corresponding resources more reasonably to ensure the end-to-end QoS requirements of the UE.

[0424] Figure 17 is a schematic diagram of another core network device switching method provided by an embodiment of this application.

[0425] The core network equipment switching method may include the following steps:

[0426] The embodiments of this application will describe, in Scheme 7 and Scheme 8, how the UE's AMF knows that the core network equipment of WAB-MT has changed.

[0427] Option 7:

[0428] This application provides several methods for WAB nodes to obtain the fifth information, such as scheme 7.1 and scheme 7.2.

[0429] Option 7.1:

[0430] S1101, the AMF of WAB-MT can determine if the AMF and / or UPF of WAB-MT have changed.

[0431] In some cases, the AMF (Advanced Feature Function) of WAB-MT (before the change) can determine that the AMF of WAB-MT needs to be changed, and / or the AMF of WAB-MT can determine that the UPF (Upgraded Feature Function) of WAB-MT needs to be changed or has already been changed. Alternatively, the AMF of WAB-MT (after the change) can determine that the AMF of WAB-MT has already been changed, and / or determine that the UPF of WAB-MT needs to be changed or has already been changed.

[0432] Among them, the reasons for core network equipment changes may be related to the geographical location of WAB-MT. For example, during the movement of WAB-MT, the distance between WAB-MT and the AMF and / or UPF of the source WAB-MT gradually increases.

[0433] S1102, the AMF of WAB-MT sends the fifth message to WAB-MT.

[0434] Accordingly, WAB-MT receives the fifth information from the WAB-MT's AMF. For example, the fifth information could be a NAS message. This fifth information could indicate the new WAB-MT's AMF and / or the new WAB-MT's UPF. For instance, it could indicate the new WAB-MT's AMF ID, the new WAB-MT's AMF IP address, the new WAB-MT's UPF ID, and / or the new WAB-MT's UPF IP address.

[0435] It is understandable that Scheme 7.1 corresponds to the WAB node directly obtaining the fifth information from the core network equipment.

[0436] Option 7.2:

[0437] S1103, the WAB-donor can determine if the AMF and / or UPF of the WAB-MT has changed.

[0438] It's understandable that, since the WAB-donor is the service gNB for the WAB-MT, it will participate in the process of changing the WAB-MT's AMF and / or UPF to re-establish the N2 interface with the new WAB-MT AMF and / or the N3 interface with the new WAB-MT UPF. Therefore, the WAB-donor can determine when the WAB-MT's AMF and / or UPF has changed.

[0439] S1104, WAB-donor sends the fifth message to the WAB node.

[0440] Accordingly, the WAB node receives the fifth message from the WAB-donor. For example, the fifth message can be sent from the WAB-donor to the WAB-gNB via an Xn message. Alternatively, the fifth message can be sent from the WAB-donor to the WAB-MT via an RRC message.

[0441] It is understandable that in Scheme 7.2, the corresponding WAB node obtains the fifth information through the WAB-donor.

[0442] S1105, the WAB-gNB sends the fifth information to the UE's AMF. Correspondingly, the UE's AMF receives the fifth information from the WAB-gNB.

[0443] It is understandable that the UE's AMF in Scheme 7 obtains the fifth information from WAB-gNB.

[0444] Option 8:

[0445] S1106, the AMF of WAB-MT can determine if the AMF and / or UPF of WAB-MT have changed.

[0446] It is understood that the execution process of S1106 is the same as that of S1101. For details, please refer to the description of S1101. The embodiments of this application will not be repeated here.

[0447] S1107, the AMF of WAB-MT sends the fifth message to the AMF of UE.

[0448] Accordingly, the UE's AMF receives the fifth piece of information from the WAB-MT's AMF. In some examples, the WAB-MT's AMF can also send the WAB-gNB's ID, WAB-gNB's IP address, and / or the WAB-MT's ID to the UE's AMF to indicate which WAB's corresponding core network device has changed. In some examples, considering that the receiving end is the UE's AMF, the WAB-gNB's ID and IP address can be used so that the UE's AMF can directly identify it.

[0449] Before S1107, Scheme 1 in Figure 14 can be executed so that the AMF of WAB-MT knows the AMF of UE and that there is interaction between the AMF of WAB-MT and the AMF of UE.

[0450] It is understandable that the UE's AMF in Scheme 8 obtains the fifth information from the AMF of WAB-MT.

[0451] Of course, steps S1101 to S1107 can all be considered optional. In other words, subsequent steps can be executed directly.

[0452] S1108, UE's AMF determines that UE's AMF has changed.

[0453] In some cases, the UE's AMF can be changed based on changes to the WAB-MT core network equipment, triggering a change in the UE's AMF. In other cases, the UE's AMF can be determined directly based on the implementation, indicating that the UE's AMF needs to be changed. In this case, steps S1101 to S1107 above do not need to be executed.

[0454] S1109, the UE's AMF sends the tenth message to the WAB-gNB.

[0455] Accordingly, the WAB-gNB receives the tenth information from the UE's AMF. This tenth information can indicate the new UE's AMF. In some cases, the tenth information can trigger the establishment of a new NG interface between the WAB-gNB and the new UE's AMF. In other cases, if an NG interface already exists between the WAB-gNB and the new UE's AMF, the tenth information can trigger the UE served by the WAB-gNB to perform an NG handover, switching the UE to the new UE's AMF.

[0456] In some examples, the tenth information may include the new UE's AMF ID and / or the new UE's AMF IP address. Additionally, the tenth information may include an NGAP UE ID. This NGAP UE ID is understood to be used to identify the UE connected to the WAB-gNB.

[0457] S1110, the UE's AMF determines that the UE's UPF has changed.

[0458] In some cases, the UE's AMF can perform UPF relocation. It's understood that S1110 can be an optional step. Of course, S1110 can also be performed before S1109, in which case the tenth information in S1109 can also indicate the new UE's UPF. For example, the tenth information can also include the ID of the new UE's UPF and / or the IP address of the new UE's UPF.

[0459] It is understood that the specific implementation process of each step in Figure 17 can be referred to the description of the relevant embodiments in Figure 10, and the embodiments of this application will not be repeated here.

[0460] Figure 18 is a schematic diagram of another core network device switching method provided in an embodiment of this application.

[0461] The core network equipment switching method may include the following steps:

[0462] The embodiments of this application will describe, in Scheme 9 and Scheme 10, how the AMF of WAB-MT knows that the core network equipment of the UE has changed.

[0463] Option 9:

[0464] S1201, the WAB node can determine when the AMF and / or UPF of WAB-MT has changed.

[0465] Similar to the WAB-donor, the WAB-gNB is the serving gNB of the UE. Therefore, during changes to the UE's AMF and / or UPF, the WAB-gNB participates in establishing the corresponding N2 and / or N3 interfaces. Thus, the WAB-gNB can determine when the UE's AMF and / or UPF has changed.

[0466] S1202, WAB-MT sends the tenth message to WAB-MT's AMF.

[0467] Accordingly, the AMF of the WAB-MT receives the tenth information from the WAB-MT. This tenth information can indicate the AMF of the new UE and / or the UPF of the new UE. A detailed description of the tenth information can be found in the corresponding embodiment in Figure 17, and will not be repeated here.

[0468] It is understandable that Scheme 9 corresponds to the AMF of WAB-MT obtaining the tenth information from WAB-MT.

[0469] Option 10:

[0470] S1203, the UE's AMF determines that the UE's AMF and / or UPF have changed.

[0471] It is understood that the implementation process of S1203 is similar to that of S1101, the difference being the executing entity and the entity determining the change. For details, please refer to the description of S1101; this embodiment will not be repeated here.

[0472] S1204, the UE's AMF sends the tenth message to the WAB-MT's AMF.

[0473] Accordingly, the AMF of the WAB-MT receives the tenth information from the AMF of the UE. In some examples, the UE's AMF can also send the WAB-gNB ID, the WAB-gNB IP address, and / or the WAB-MT ID to the AMF of the WAB-MT to indicate which WAB the core network device corresponding to the UE has changed. In some examples, considering that the receiving end is the AMF of the WAB-MT, the WAB-MT ID can be used so that the AMF of the WAB-MT can directly identify it.

[0474] Scheme 2 in Figure 14 can be executed before S1204 so that the UE's AMF knows the WAB-MT's AMF and that the UE's AMF and the WAB-MT's AMF can interact.

[0475] It is understandable that Scheme 10 corresponds to the AMF of WAB-MT obtaining the tenth information from the AMF of the UE.

[0476] Of course, steps S1201 to S1204 can all be considered optional. In other words, subsequent steps can be executed directly.

[0477] S1205, WAB-MT's AMF has been determined to have changed.

[0478] In some cases, the AMF of the WAB-MT can be changed based on changes to the UE's core network equipment, triggering a change in the WAB-MT's AMF. In other cases, the AMF of the WAB-MT can be determined directly based on the implementation, indicating that the WAB-MT's AMF needs to be changed. In this case, steps S1201 to S1104 above do not need to be executed.

[0479] S1206, WAB-MT's AMF sends the fifth message to WAB-donor.

[0480] Accordingly, the WAB-donor receives the fifth message from the AMF of the WAB-MT. This fifth message can indicate the new AMF of the WAB-MT. In some examples, the fifth message can trigger the establishment of a new NG interface between the WAB-donor and the new AMF of the WAB-MT. In other examples, if the NG interface between the WAB-donor and the new AMF of the WAB-MT already exists, the fifth message can trigger the WAB-MT served by the WAB-donor to perform an NG switch, switching the WAB-MT to the new AMF of the WAB-MT.

[0481] In some examples, the fifth piece of information may include the ID of the new WAB-MT's AMF and / or the IP address of the new WAB-MT's AMF. Additionally, the fifth piece of information may include the NGAP UE ID. It is understood that this NGAP UE ID is used to identify the WAB-MT.

[0482] S1207, WAB-MT's AMF determines that WAB-MT's UPF has changed.

[0483] In some cases, the AMF of WAB-MT can perform UPF redirection. It is understood that S1207 can be an optional step. Of course, S1207 can also be executed before S1206, in which case the fifth information in S1206 can also indicate the new WAB-MT UPF. For example, the fifth information can also include the ID of the new WAB-MT UPF and / or the IP address of the new WAB-MT UPF.

[0484] It is understood that the specific implementation process of each step in Figure 18 can be referred to the description of the relevant embodiments in Figure 11, and the embodiments of this application will not be repeated here.

[0485] The methods shown in Figures 17 and 18 above can accommodate situations where changes occur in the core network equipment and trigger interface updates, which helps to ensure the QoS requirements of the UE.

[0486] It is understandable that when a UE or WAB node moves, the transmission path between it and the source core network equipment may become too long, which may lead to a decrease in QoS performance. Therefore, the QoS performance can be avoided by changing the core network equipment.

[0487] Figure 19 is a schematic diagram of a relay network structure in an open wireless access network scenario provided by an embodiment of this application.

[0488] This application embodiment can also be considered for application in O-RAN scenarios, which may include a radio access network intelligent controller (RIC). The RIC can be used to collect network information and perform necessary optimization tasks. The RIC communicates with the CUs and DUs of each access network node via an E2 interface, which can be considered a logical interface. The RIC can directly control the DUs of the access network node, or indirectly control their DUs through the CUs of the access network node.

[0489] In some examples, the RIC can function solely as a forwarding node. That is, in conjunction with the implementation processes of the above embodiments, the RIC acts as an intermediate node when the first relay node communicates with other devices. For instance, the first relay node first sends the data to be sent to the RIC, and then the RIC forwards the data to the corresponding device, or vice versa.

[0490] In other examples, the RIC can be used as part of data processing, such as for determining various QoS parameters, like QoS 1, QoS 1+QoS 2, QoS 0+QoS 1+QoS 2+QoS 3, etc. Specifically, the RIC can directly indicate QoS 0+QoS 1+QoS 2+QoS 3 to the first relay node via the E2 interface; alternatively, the RIC can indicate QoS 0+QoS 1+QoS 2+QoS 3 to the second access network device via the E2 interface, and the second access network device can then indicate QoS 0+QoS 1+QoS 2+QoS 3 to the first relay node via an RRC message. The RIC can also directly indicate QoS 1 or QoS 1+QoS 2 to the second access network device via the E2 interface.

[0491] Of course, for the CU and DU in the access network device in Figure 19, as well as the interfaces between the CUs of different devices, relevant technologies can be referenced, and the embodiments of this application will not be described in detail.

[0492] Of course, the implementation process in the O-RAN scenario can be referred to the descriptions of the foregoing embodiments, and will not be repeated here.

[0493] It is understood that the access network nodes involved in the various embodiments of this application can be access network nodes under a CU / DU separation architecture. That is, the access network node can include CU and DU. It is understood that the CU and DU of each device in Figure 19 can be considered as CU and DU supporting O-RAN functions.

[0494] Figure 20 is a schematic diagram of another QoS configuration method provided by an embodiment of this application.

[0495] Referring to Figure 20, taking the determination of QoS 0+QoS 1+QoS 2+QoS 3 by RIC as an example, where the first relay node can be a WAB node, the first access network device can be a WAB-gNB, the first MT can be a WAB-MT, and the second access network device can be a WAB-donor, this method can include the following steps:

[0496] In this embodiment of the application, the RIC can obtain the first information through scheme 11 or scheme 12, so as to configure the corresponding QoS parameters for the UE.

[0497] Option 11:

[0498] S1301, WAB determines WAB's backhaul capability.

[0499] It is understood that the processes of S1301 and S901 are similar. For details, please refer to the description of S901. The embodiments of this application will not be repeated here.

[0500] S1302, WAB-gNB sends the first message to RIC.

[0501] Accordingly, the RIC receives the first information from the WAB-gNB. It can be understood that the process of S1301 is similar to that of S901, the difference being the receiving end of the first information. For details, please refer to the description of S901; this embodiment will not be repeated here.

[0502] Option 12:

[0503] S1303, WAB-donor determines the WAB's backhaul capability.

[0504] It is understood that the processes S1303 and S903 are similar, the difference being the executing entity. For details, please refer to the description of S903; the embodiments in this application will not be repeated here.

[0505] S1304, WAB-donor sends the first message to RIC.

[0506] Accordingly, the RIC receives the first information from the WAB-donor. It can be understood that the processes in S1304 and S904 are similar, the difference being the receiving end and the sending end of the first information. For details, please refer to the description of S904; this embodiment will not be repeated here.

[0507] Through scheme 11 or scheme 12 described above, RIC can obtain the first information in order to execute subsequent steps.

[0508] S1305, RIC sends the second message to WAB-gNB.

[0509] It is understood that the processes S1305 and S905 are similar, the difference being the executing entity. For details, please refer to the description of S905; the embodiments in this application will not be repeated here.

[0510] Of course, Figure 20 only uses RIC to determine QoS 0+QoS 1+QoS 2+QoS 3. In other embodiments, RIC can also be used to determine other QoS parameters, such as QoS 1, QoS 1+QoS 2, etc. The implementation process is similar to the aforementioned embodiments, except that the entity performing the determination of QoS parameters is replaced by RIC. Accordingly, RIC can receive various information required to determine QoS parameters.

[0511] In the various embodiments described above in this application, the QoS parameters involved may include PDB, packet error rate (PER), guaranteed bit rate (GBR), etc., and are not limited to these parameters in the embodiments of this application.

[0512] It is understood that each of the above embodiments of this application can be implemented independently or in combination with each other; there is no absolute subordinate relationship between the embodiments, and they can be combined with each other under any conditions to obtain the corresponding effect.

[0513] It is understood that, in order to achieve the functions in the above embodiments, the core network equipment, access network equipment, and terminal include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0514] Figures 21 and 22 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of terminals, core network devices, or access network devices in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be the terminal 120 shown in Figure 1, the base station 110 shown in Figure 1, the core network device in the core network 200 shown in Figure 1, or a module (such as a chip) applied to the terminal, core network device, or access network device.

[0515] As shown in Figure 21, the communication device 2100 includes a processing unit 2110 and a transceiver unit 2120. The communication device 2100 is used to implement the functions of the terminal, core network device, or access network device in the method embodiments shown in Figures 6, 7, 9 to 18, and 20.

[0516] When the communication device 2100 is used to implement the function of the first core network device in the method embodiment shown in FIG6: the transceiver unit 2120 is used to receive first information from the first access network device or from the second core network device; the processing unit 2110 is used to control the transceiver unit 2120 to send second information based on the first parameters.

[0517] When the communication device 2100 is used to implement the function of the first relay node or the second core network device in the method embodiment shown in FIG6: the processing unit 2110 is used to determine the backhaul capability corresponding to the first access network device; the transceiver unit 2120 is used to send the first information to the first core network device.

[0518] For a more detailed description of the above-mentioned processing unit 2110 and transceiver unit 2120, please refer to the method embodiment shown in FIG6 and the relevant descriptions of the embodiments in FIG7, FIG9 to FIG18 and FIG20.

[0519] As shown in Figure 22, the communication device 2200 includes a processor 2210 and an interface circuit 2220. The processor 2210 and the interface circuit 2220 are coupled together. It is understood that the interface circuit 2220 can be a transceiver or an input / output interface. Optionally, the communication device 2200 may also include a memory 2230 for storing instructions executed by the processor 2210, or storing input data required by the processor 2210 to execute instructions, or storing data generated after the processor 2210 executes instructions. Sometimes, the interface circuit 2220 can also be understood as part of the processor 2210, in which case the communication device 2200 includes the processor 2210.

[0520] When the communication device 2200 is used to implement the methods shown in Figures 6, 7, 9 to 18 and 20, the processor 2210 is used to implement the functions of the processing unit 2110, and the interface circuit 2220 is used to implement the functions of the transceiver unit 2120.

[0521] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from the access network device, which can be understood as the information being first received by other modules in the terminal (such as an RF module or antenna), and then sent to the terminal chip by these modules. The terminal chip sends information to the access network device, which can be understood as the information being first sent to other modules in the terminal (such as an RF module or antenna), and then sent to the access network device by these modules.

[0522] When the aforementioned communication device is a chip applied to an access network device, the access network device chip implements the functions of the access network device in the above method embodiments. The access network device chip receives information from a terminal or core network device, which can be understood as the information being first received by other modules (such as radio frequency modules or antennas) in the access network device, and then sent to the access network device chip by these modules. The access network device chip sends information to a terminal or core network device, which can be understood as the information being sent down to other modules (such as radio frequency modules or antennas) in the terminal or core network device, and then sent back to the terminal or core network device by these modules.

[0523] When the aforementioned communication device is a chip used in core network equipment, the core network equipment chip implements the functions of the core network equipment in the above method embodiments. The core network equipment chip receives information from the access network equipment, which can be understood as the information being first received by other modules (such as radio frequency modules or antennas) in the core network equipment, and then sent to the core network equipment chip by these modules. The core network equipment chip sends information to the access network equipment, which can be understood as the information being sent down to other modules (such as radio frequency modules or antennas) in the access network equipment, and then sent back to the access network equipment by these modules.

[0524] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0525] It is understood that the processor in the embodiments of this application can be a central processing unit, or other general-purpose processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0526] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. The processor and storage medium can also exist as discrete components in a base station or terminal.

[0527] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0528] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0529] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0530] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0531] In this application, the base station sends downlink signals or downlink information to the terminal, with the downlink information carried on the downlink channel; the terminal sends uplink signals or uplink information to the base station, with the uplink information carried on the uplink channel. To communicate with the base station, the terminal needs to establish a radio connection on a cell controlled by the base station. The cell with which the terminal has established a radio connection is called the terminal's serving cell. When the terminal communicates with this serving cell, it is also susceptible to interference from signals from neighboring cells.

[0532] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0533] The terms "first" and "second," etc., used in the specification and drawings of the embodiments of this application are used to distinguish different objects or to distinguish different processing of the same object. The terms "first" and "second," etc., can distinguish identical or similar items with substantially the same function and effect. For example, "first device" and "second device" are merely to distinguish different devices and do not limit their order. Those skilled in the art will understand that the terms "first" and "second," etc., do not limit the quantity or execution order, and that "first" and "second," etc., do not necessarily imply that they are different.

[0534] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of the embodiments of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0535] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0536] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of the embodiments of this application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of the embodiments of this application, the sequence number of each process does not imply 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 this application.

[0537] It is understood that in the embodiments of this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a time, nor do they require a judgment action during implementation, nor do they imply any other limitations.

[0538] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0539] In the embodiments of this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined to form new embodiments, implementation methods, methods, or implementation approaches based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of the embodiments of this application.

Claims

1. A method for configuring Quality of Service (QoS), characterized in that, Applied to a first core network device, the method includes: Receive first information from a first access network device or from a second core network device, wherein the first information includes a first parameter, the first parameter being used to indicate the backhaul capability of the first relay node, the first relay node including the first access network device and a first mobile terminal MT, and the second core network device providing services to the first MT; Based on the first parameter, a second message is sent to the first access network device. The second message is used to indicate the QoS parameters between the terminal device and the first core network device. The terminal device and the first access network device have a communication connection.

2. The method according to claim 1, characterized in that, The first information comes from the second core network device, and the first information also includes at least one of the following parameters: The identifier of the first access network device; The identifier of the first MT; The address parameters of the first access network device.

3. The method according to claim 1, characterized in that, The method further includes: When the first condition is met, third information is received from the third access network device, wherein the third information includes a second parameter, the second parameter being used to indicate the backhaul capability of the third access network device, and the third access network device having a communication connection with the terminal device; The second information is sent to the third access network device based on the second parameter; The first condition includes at least one of the following: The terminal device has a communication connection with the first access network device, and then switches to having a communication connection between the terminal device and the third access network device; The terminal device re-establishes itself to the third access network device via RRC.

4. The method according to any one of claims 1-3, characterized in that, The backhaul capability of the first relay node includes the backhaul method adopted by the first relay node and / or QoS parameters related to the first MT. The backhaul method used by the first relay node includes: non-terrestrial network (NTN) backhaul method and / or TN backhaul method for terrestrial networks.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Send a fourth message to the second core network device, the fourth message being used to indicate the QoS parameters between the first access network device and the first core network device.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: The tenth information is sent to the first access network device, the tenth information being used to instruct the fourth core network device to provide services to the terminal device.

7. The method according to claim 6, characterized in that, The method further includes: Identify the fourth core network device.

8. The method according to claim 7, characterized in that, The method further includes: The system receives fifth information from the first access network device, the fifth information being used to instruct a third core network device, the third core network device providing services to the first MT; The determination of the fourth core network device includes: The fourth core network device is determined based on the fifth piece of information.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: The system receives a sixth piece of information from the first access network device, the sixth piece of information including information for indicating the second core network device and information for indicating the first MT.

10. A method for configuring Quality of Service (QoS), characterized in that, The method is applied to a first relay node or a second core network device, wherein the first relay node includes a first access network device and a first mobile terminal (MT), and the second core network device provides services to the first MT. The method includes: Determine the backhaul capability corresponding to the first access network device; Send first information to the first core network device. The first information includes a first parameter, which is used to indicate the backhaul capability adopted by the first relay node. The first information is also used to trigger the first core network device to configure QoS parameters between the terminal device and the first core network device. The terminal device has a communication connection with the first access network device, and the first core network device provides services to the terminal device.

11. The method according to claim 10, characterized in that, The method is applied to the second core network device, and the first information further includes at least one of the following parameters: The identifier of the first access network device; The identifier of the first MT; The address parameters of the first access network device.

12. The method according to claim 10 or 11, characterized in that, The backhaul capability of the first relay node includes the backhaul method adopted by the first relay node and / or QoS parameters related to the first MT. The backhaul method adopted by the first relay node includes: non-terrestrial network (NTN) backhaul method and / or terrestrial network (TN) backhaul method.

13. The method according to any one of claims 10-12, characterized in that, The method is applied to the second core network device, and the method further includes: The device receives fourth information from the first core network device or from the first MT, the fourth information being used to indicate QoS parameters between the first access network device and the first core network device.

14. The method according to claim 13, characterized in that, The method further includes: sending the fourth information to a second access network device, wherein the second access network device has a communication connection with the first MT.

15. The method according to claim 14, characterized in that, The method further includes: A seventh message is sent to the second access network device, the seventh message being used to indicate the QoS parameters between the first core network device and the second core network device.

16. The method according to claim 13, characterized in that, The method further includes: Obtain the QoS parameters between the first core network device and the second core network device; Based on the QoS parameters between the first access network device and the first core network device, and the QoS parameters between the first core network device and the second core network device, the QoS parameters between the first MT and the second core network are determined. Send an eighth message to the second access network device, wherein the eighth message is used to indicate the QoS parameters between the first MT and the second core network.

17. The method according to claim 13, characterized in that, The method further includes: The QoS parameters between the second access network device and the second core network device, and the QoS parameters between the first core network device and the second core network device are obtained, wherein the second access network device has a communication connection with the first MT; Based on the QoS parameters between the first access network device and the first core network device, the QoS parameters between the second access network device and the second core network device, and the QoS parameters between the first core network device and the second core network device, the QoS parameters between the first MT and the second access network device are determined. A ninth message is sent to the second access network device, the ninth message being used to indicate the QoS parameters between the first MT and the second access network device.

18. The method according to claim 10, characterized in that, The method is applied to the first relay node, and the method further includes: The fourth information is sent to the second access network device or the second core network device. The fourth information is used to indicate the QoS parameters between the first access network device and the first core network device, wherein the second access network device has a communication connection with the first MT.

19. The method according to any one of claims 10-18, characterized in that, The method further includes: Send a fifth message to a first core network device or a second access network device, the fifth message being used to instruct the third core network device to provide services to the first MT; and / or, The system receives tenth information from the first core network device, the tenth information being used to instruct the fourth core network device to provide services to the terminal device.

20. A communication device, characterized in that, It includes a module for performing the method of any one of claims 1 to 9, or a module for performing the method of any one of claims 10 to 19.

21. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 9, or to implement the method as described in any one of claims 10 to 19, through logic circuits or executing code instructions.

22. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 9, or the method as described in any one of claims 10 to 19.

23. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the communication device, they implement the method as described in any one of claims 1 to 9, or the method as described in any one of claims 10 to 19.

Images