Communication method, communication device, communication system, storage medium, and program product

Abstract

Embodiments of the present disclosure relate to a communication method, a communication device, a communication system, a storage medium, and a program product. The communication method can be executed by a first node. The method comprises: performing coordinated processing on quality of service (QoS) flows having an association relationship. In the present disclosure, the first node performs coordinated processing on QoS flows having an association relationship, so that the implementation of the requirements for coordinated transmission between different QoS flows is facilitated, thereby avoiding the waste of radio resources, and ensuring the user experience.

Description

Communication method, communication device, communication system, storage medium and program product TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and in particular to a communication method, a communication device, a communication system, a storage medium and a program product. BACKGROUND

[0002] To realize the differentiation of various data flows, a quality of service (QoS) scheme is introduced in a 5th generation (5G) communication system, so as to provide network services with different service qualities for different service requirements. A core network device can establish one or more protocol data unit (PDU) sessions, and multiple data flows with different QoS requirements, referred to as QoS flows, can be transmitted in each PDU session.

[0003] SUMMARY

[0004] For multi-modal services, if there is an association relationship between multiple QoS flows, but only part of the QoS flows are successfully established, the application layer may discard the received data packets, which not only wastes wireless resources, but also affects user experience.

[0005] Embodiments of the present disclosure provide a communication method, a communication device, a communication system, a storage medium and a program product.

[0006] According to a first aspect of embodiments of the present disclosure, a communication method is provided, which is performed by a first node, and the method comprises: performing coordinated processing on service quality (QoS) flows having an association relationship.

[0007] According to a second aspect of embodiments of the present disclosure, a communication method is provided, which is performed by a second node, and the method comprises: sending first information, the first information being used to indicate QoS flows having an association relationship, the QoS flows having an association relationship being processed by the first node in a coordinated manner.

[0008] According to a third aspect of embodiments of the present disclosure, a first node is provided, comprising: a processing module configured to perform coordinated processing on QoS flows having an association relationship.

[0009] According to a fourth aspect of embodiments of the present disclosure, a second node is provided, comprising: a transceiver module configured to send first information, the first information being used to indicate QoS flows having an association relationship, the QoS flows having an association relationship being processed by the first node in a coordinated manner.

[0010] According to a fifth aspect of the embodiments of the present disclosure, a communication device is provided, comprising: one or more processors; and wherein the communication device is configured to perform the communication method according to the first aspect or the second aspect.

[0011] According to a sixth aspect of the embodiments of the present disclosure, a communication system is provided, comprising a first node and a second node; the first node is configured to implement the communication method according to the first aspect; and the second node is configured to implement the communication method according to the second aspect.

[0012] According to a seventh aspect of the embodiments of the present disclosure, a storage medium is provided, which stores instructions, when the instructions are executed on a communication device, the communication device performs the communication method according to any one of the first aspect to the third aspect.

[0013] According to an eighth aspect of the embodiments of the present disclosure, a computer program product is provided, comprising a computer program, when the computer program is executed by a processor, the communication method according to the first aspect or the second aspect is implemented.

[0014] According to a ninth aspect of the embodiments of the present disclosure, a computer program is provided, comprising code, when the code is executed by a processor, the communication method according to the first aspect or the second aspect is implemented.

[0015] According to a tenth aspect of the embodiments of the present disclosure, a chip or chip system is provided, comprising a processing circuit, the processing circuit is configured to perform the communication method according to the first aspect or the second aspect.

[0016] According to the embodiments of the present disclosure, the first node processes the QoS flows with an association relationship in a cooperative manner, which facilitates to meet the requirement of cooperative transmission between different QoS flows, avoids waste of wireless resources, and guarantees user experience. BRIEF DESCRIPTION OF DRAWINGS

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

[0018] FIG. 1A is an architecture schematic diagram of a communication system according to an embodiment of the present disclosure.

[0019] FIG. 1B is a simplified PDU session establishment flow schematic diagram according to an embodiment of the present disclosure.

[0020] FIGS. 2A to 2D are interaction schematic diagrams of a communication method according to an embodiment of the present disclosure.

[0021] FIG. 3A is a flow schematic diagram of a communication method performed by a first node according to an embodiment of the present disclosure.

[0022] FIG. 3B is a flow diagram illustrating a method for performing communication by a second node according to an embodiment of the present disclosure.

[0023] FIG. 4A is another flow diagram illustrating a method for performing communication by a first node according to an embodiment of the present disclosure.

[0024] FIG. 4B is another flow diagram illustrating a method for performing communication by a second node according to an embodiment of the present disclosure.

[0025] FIG. 5A is a structural diagram of a first node according to an embodiment of the present disclosure.

[0026] FIG. 5B is a structural diagram of a second node according to an embodiment of the present disclosure.

[0027] FIG. 6 is a structural diagram of a communication device according to an embodiment of the present disclosure.

[0028] FIG. 7 is a structural diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] Embodiments of the present disclosure provide a communication method, a communication device, a communication system, a storage medium and a program product.

[0030] In a first aspect, embodiments of the present disclosure provide a communication method performed by a first node, including: performing coordinated processing on QoS flows having an association relationship.

[0031] In embodiments of the present disclosure, the first node performs coordinated processing on QoS flows having an association relationship, which facilitates the requirement of coordinated transmission between different QoS flows, avoids waste of wireless resources, and guarantees user experience.

[0032] In some embodiments of the first aspect, the QoS flows having the association relationship are indicated by first information, which is obtained by the first node from a second node.

[0033] In some embodiments of the first aspect, the first node is a first access network device, and the second node is a terminal, a core network device or a second access network device; or the first node is a distributed unit of the first access network device, and the second node is a centralized unit of the first access network device.

[0034] In some embodiments of the first aspect, the first access network device is a target base station, and the second access network device is an original base station; or the first access network device is a secondary base station, and the second access network device is a primary base station; or the first access network device is a current serving base station, and the second access network device is an original serving base station.

[0035] In some embodiments of the first aspect, in some embodiments, the first information further indicates at least one of: a requirement of the cooperative processing; a policy of the cooperative processing.

[0036] In some embodiments of the first aspect, in some embodiments, the requirement of the cooperative processing comprises: a transmission time difference between the QoS flows with the association relationship satisfies a first threshold.

[0037] In some embodiments of the first aspect, in some embodiments, the method further comprises: sending second information to the second node, the second information indicating a result of the cooperative processing.

[0038] In some embodiments of the first aspect, in some embodiments, the second information further indicates a reason of the result of the cooperative processing.

[0039] In some embodiments of the first aspect, in some embodiments, the method further comprises: receiving third information, the third information indicating a support capability of the second node for the requirement of the cooperative processing of the QoS flow, the second node being a terminal or a core network device.

[0040] In some embodiments of the first aspect, in some embodiments, the method further comprises: receiving fourth information, the fourth information indicating a support capability of the second node for the cooperative processing, the second node being a second access network device.

[0041] In the embodiments of the present disclosure, the access network devices can interact with each other to exchange capability information, so that in the case that the first access network device does not support the cooperative processing or the first access network device does not perform the cooperative processing on the QoS flow for the consideration of local resources or load balancing, the second access network device can perform the cooperative processing on the QoS flows with the association relationship, so as to guarantee the requirement of the cooperative transmission between different QoS flows and avoid the waste of wireless resources.

[0042] In some embodiments of the first aspect, in some embodiments, the method further comprises: sending fifth information, the fifth information indicating a support capability of the first node for the cooperative processing.

[0043] In a second aspect, the embodiments of the present disclosure provide a communication method, performed by a second node, the method comprising: sending first information, the first information indicating QoS flows with an association relationship, the QoS flows with the association relationship being processed cooperatively by a first node.

[0044] In some embodiments of the second aspect, in some embodiments, the first node is a first access network device, and the second node is a terminal, a core network device, or a second access network device; or the first node is a distributed unit of the first access network device, and the second node is a centralized unit of the first access network device.

[0045] In some embodiments of the second aspect, in some embodiments, the first access network device is a target base station, and the second access network device is an original base station; or the first access network device is a secondary base station, and the second access network device is a primary base station; or the first access network device is a current serving base station, and the second access network device is an original serving base station.

[0046] In some embodiments of the second aspect, in some embodiments, the first information further indicates at least one of: a requirement for the cooperative processing; a policy of the cooperative processing.

[0047] In some embodiments of the second aspect, in some embodiments, the requirement for the cooperative processing comprises that a transmission time difference between the QoS flows having the association relationship satisfies a first threshold.

[0048] In some embodiments of the second aspect, in some embodiments, the method further comprises: receiving second information sent by the first node, the second information being used to indicate a result of the cooperative processing.

[0049] In some embodiments of the second aspect, in some embodiments, the second information is further used to indicate a reason for the result of the cooperative processing.

[0050] In some embodiments of the second aspect, in some embodiments, the method further comprises: sending third information, the third information being used to indicate a support capability of the second node for a requirement for the cooperative processing of a sending QoS flow, the second node being a terminal or a core network device.

[0051] In some embodiments of the second aspect, in some embodiments, the method further comprises: sending fourth information, the fourth information being used to indicate a support capability of the second node for the cooperative processing, the second node being a second access network device.

[0052] In some embodiments of the second aspect, in some embodiments, the method further comprises: receiving fifth information, the fifth information being used to indicate a support capability of the first node for the cooperative processing.

[0053] In a third aspect, the embodiments of the present disclosure provide a first node, comprising: a processing module configured to cooperatively process quality of service (QoS) flows having an association relationship.

[0054] In some embodiments of the third aspect, in some embodiments, the QoS flows having the association relationship are indicated by first information, the first information being obtained by the third node from a second node.

[0055] In some embodiments of the third aspect, in some embodiments, the first node is a first access network device, and the second node is a terminal, a core network device, or a second access network device; or the first node is a distributed unit of the first access network device, and the second node is a centralized unit of the first access network device.

[0056] In some embodiments of the third aspect, in some embodiments, the first access network device is a target base station, and the second access network device is an original base station; or the first access network device is a secondary base station, and the second access network device is a primary base station; or the first access network device is a current serving base station, and the second access network device is an original serving base station.

[0057] In some embodiments of the third aspect, in some embodiments, the first information further indicates at least one of the following: a requirement for the cooperative processing; a policy for the cooperative processing.

[0058] In some embodiments of the third aspect, in some embodiments, the requirement for the cooperative processing comprises that a transmission time difference between the QoS flows having the association relationship satisfies a first threshold.

[0059] In some embodiments of the third aspect, in some embodiments, the method further comprises: sending second information to the second node, the second information being used to indicate a result of the cooperative processing.

[0060] In some embodiments of the third aspect, in some embodiments, the second information is further used to indicate a reason for the result of the cooperative processing.

[0061] In some embodiments of the third aspect, in some embodiments, the first node further comprises: a transceiver configured to receive third information, the third information being used to indicate a support capability of the second node for a requirement for the cooperative processing of the sending QoS flow, the second node being a terminal or a core network device.

[0062] In some embodiments of the third aspect, in some embodiments, the transceiver is further configured to receive fourth information, the fourth information being used to indicate a support capability of the second node for the cooperative processing, the second node being a second access network device.

[0063] In some embodiments of the third aspect, in some embodiments, the transceiver is further configured to send fifth information, the fifth information being used to indicate a support capability of the first node for the cooperative processing.

[0064] In a fourth aspect, an embodiment of the present disclosure provides a second node, comprising: a transceiver configured to send first information, the first information being used to indicate QoS flows having an association relationship, the QoS flows having the association relationship being cooperatively processed by a first node.

[0065] In some embodiments of the fourth aspect, the first node is a first access network device, and the second node is a terminal, a core network device, or a second access network device; or the first node is a distributed unit of the first access network device, and the second node is a centralized unit of the first access network device.

[0066] In some embodiments of the fourth aspect, the first access network device is a target base station, and the second access network device is an original base station; or the first access network device is a secondary base station, and the second access network device is a primary base station; or the first access network device is a current serving base station, and the second access network device is an original serving base station.

[0067] In some embodiments of the fourth aspect, the first information is further used to indicate at least one of the following: a requirement for the cooperative processing; a policy for the cooperative processing.

[0068] In some embodiments of the fourth aspect, the requirement for the cooperative processing comprises that a transmission time difference between the QoS flows having the association relationship satisfies a first threshold.

[0069] In some embodiments of the fourth aspect, the method further comprises: receiving second information sent by the first node, the second information being used to indicate a result of the cooperative processing.

[0070] In some embodiments of the fourth aspect, the second information is further used to indicate a reason for the result of the cooperative processing.

[0071] In some embodiments of the second aspect, the method further comprises: sending third information, the third information being used to indicate a support capability of the second node for a cooperative processing requirement of a sending QoS flow, the second node being a terminal or a core network device.

[0072] In some embodiments of the fourth aspect, the method further comprises: sending fourth information, the fourth information being used to indicate a support capability of the second node for the cooperative processing, the second node being a second access network device.

[0073] In some embodiments of the fourth aspect, the method further comprises: receiving fifth information, the fifth information being used to indicate a support capability of the first node for the cooperative processing.

[0074] In a fifth aspect, an embodiment of the present disclosure provides a communication device, comprising: one or more processors; wherein the communication device is configured to perform the communication method according to the first aspect or the second aspect.

[0075] In a sixth aspect, an embodiment of the present disclosure provides a communication system, comprising: a first node and a second node; the first node is configured to implement the communication method according to the first aspect; and the second node is configured to implement the communication method according to the second aspect.

[0076] In a seventh aspect, an embodiment of the present disclosure provides a storage medium, which stores instructions, when the instructions are run on a communication device, cause the communication device to perform the communication method according to the first aspect or the second aspect.

[0077] In an eighth aspect, an embodiment of the present disclosure provides a program product, when the program product is executed by a communication device, cause the communication device to perform the communication method according to the first aspect or the second aspect.

[0078] In a ninth aspect, an embodiment of the present disclosure provides a computer program, when the computer program is run on a computer, cause the computer to perform the method described in the optional implementation manner of the first aspect or the second aspect.

[0079] In a tenth aspect, an embodiment of the present disclosure provides a chip or a chip system. The chip or the chip system comprises a processing circuit configured to perform the method described in the optional implementation manner of the first aspect or the second aspect.

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

[0081] The embodiments of the present disclosure propose a communication method, a communication device, a communication system, a storage medium and a program product. In some embodiments, the terms of the communication method, the QoS flow processing method, the coordinated scheduling method of QoS flow, the joint admission control method of QoS flow, etc. can be replaced with each other, and the terms of the communication system, the coordinated scheduling system, the joint admission control system, etc. can be replaced with each other.

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

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

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

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

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

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

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

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

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

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

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

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

[0094] In some embodiments, an apparatus and the like can be interpreted as an entity, and can also be interpreted as virtual, and the name thereof is not limited to the name recited in the embodiments, and the terms "apparatus", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", and the like can be replaced with each other.

[0095] In some embodiments, "network" can be interpreted as an apparatus (for example, an access network device, a core network device, and the like) included in the network.

[0096] In some embodiments, the terms “network devices,” “access network devices (AN devices),” “radio access network devices (RAN devices),” “base stations (BSs),” “radio base stations,” “fixed stations,” “nodes,” “access network nodes,” “access points,” “transmission points (TPs),” “reception points (RPs),” “transmission / reception points (TRPs),” “panels,” “antenna panels,” “antenna arrays,” “cells,” “macro cells,” “small cells,” “femtocells,” “pico cells,” “sectors,” “cell groups,” “serving cells,” “carriers,” “component carriers,” “bandwidth parts (BWPs),” and the like can be used interchangeably.

[0097] In some embodiments, the terms "terminal," "terminal device," "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," and so on can be replaced with each other.

[0098] In some embodiments, the access network device, the core network device, or the network device can be replaced with a terminal. For example, the embodiments of the present disclosure can also be applied to a structure in which communication between the access network device, the core network device, or the network device and the terminal is replaced with communication between a plurality of terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal can also be configured to have all or part of the functions of the access network device. In addition, the terms "uplink," "downlink," and the like can also be replaced with terms corresponding to the inter-terminal communication (e.g., "side"). For example, the uplink channel, the downlink channel, and the like can be replaced with the side channel, and the uplink, the downlink, and the like can be replaced with the sidelink.

[0099] In some embodiments, the terminal can be replaced with the access network device, the core network device, or the network device. In this case, the access network device, the core network device, or the network device can also be configured to have all or part of the functions of the terminal.

[0100] In some embodiments, the data, information, etc. can be acquired in compliance with the laws and regulations of the country where the location is situated.

[0101] In some embodiments, the data, information, etc. can be acquired after obtaining the consent of the user.

[0102] In addition, each element, each row, or each column in the table of the embodiments of the present disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0103] FIG. 1A is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG. 1A, the communication system 100 includes a first node 101 and a second node 102.

[0104] In some embodiments, the first node is configured to perform coordinated processing on QoS flows having an association relationship.

[0105] In some embodiments, the coordinated processing can be understood as coordinated scheduling, joint scheduling, joint admission control, unified scheduling, unified processing, etc.

[0106] In some embodiments, the QoS flows having an association relationship can be understood as QoS flows having a coordinated processing requirement, QoS flows having a joint admission control requirement, or QoS flows having a unified processing requirement.

[0107] In some embodiments, the first node is configured to acquire the association relationship between the QoS flows.

[0108] In some embodiments, the first node is configured to send a result of the coordinated processing.

[0109] In some embodiments, the first node is configured to send a support capability of the first node for the coordinated processing.

[0110] In some embodiments, the name of the first node is not limited, and it can be, for example, a “coordinated processing node”, a “coordinated scheduling node”, a “QoS flow processing node”, a “joint scheduling node”, a “joint admission control node”, etc.

[0111] In some embodiments, the second node is configured to send the association relationship between the QoS flows.

[0112] In some embodiments, the second node is configured to receive a result of the coordinated processing.

[0113] In some embodiments, the second node is configured to send a support capability of the second node for reporting whether the QoS flows have a coordinated processing requirement.

[0114] In some embodiments, the second node is configured to send a support capability of the second node for reporting the association relationship between the QoS flows.

[0115] In some embodiments, the second node is configured to send its support capability for the collaborative processing.

[0116] In some embodiments, the second node is configured to perform the collaborative processing on the QoS flows with the association relationship.

[0117] In some embodiments, the second node is not limited, for example, it can be a "service initiation node", a "service management node", a "session management node", a "QoS flow management node", etc.

[0118] In some embodiments, the first node can be a first access network device, a distributed unit (DU) of the first access network device, etc.

[0119] In some embodiments, the second node can be a second access network device, a central unit (CU) of the first access network device, a terminal, a core network device, etc.

[0120] In some embodiments, when the first node is a first access network device, the second node can be a second access network device, a terminal or a core network device.

[0121] In some embodiments, taking a 5G core network device as an example, the core network device can be an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a unified data management (UDM), a user plane function (UPF), etc.

[0122] In some embodiments, when the first access network device includes a CU and a DU, the first node is a DU of the first access network device, and the second node is a CU of the first access network device.

[0123] In an example, the first node is an access network device A, and the second node is an access network device B. The collaborative processing process includes: (1) the access network device A can send its support capability for the collaborative processing to the access network device B; (2) the access network device B can send the association relationship between the QoS flows to the access network device A when the access network device A supports the collaborative processing; (3) the access network device A performs the collaborative processing on the QoS flows with the association relationship; and (4) the access network device A sends the result of the collaborative processing to the access network device B.

[0124] In an example, the access network device B can support or not support the coordinated processing of the QoS flows with the association relationship.

[0125] In an example, the access network device B can obtain the association relationship between the QoS flows from the terminal, the core network device or the access network device C.

[0126] In an example, in the dual connectivity scenario, the access network device A is a secondary base station and the access network device B is a primary base station.

[0127] In an example, in the handover scenario, the access network device A is a target base station and the access network device B is an original base station.

[0128] In an example, in the RRC reestablishment scenario, the access network device A is a current serving base station and the access network device B is an original serving base station.

[0129] In an example, the first node is a DU of the access network device A, the second node is a CU of the access network device A, and the coordinated processing procedure includes: (1) the CU can send the association relationship between the QoS flows to the DU; (2) the DU performs the coordinated processing of the QoS flows with the association relationship; and (3) the DU sends the result of the coordinated processing to the CU.

[0130] In an example, the first node is the access network device A, and the second node is a terminal, and the coordinated processing procedure includes: (1) the terminal can send its support capability for reporting whether the QoS flow has the coordinated processing requirement to the access network device A; (2) in the case that the terminal supports reporting whether the QoS flow has the coordinated processing requirement, the access network device A sends its support capability for the coordinated processing to the terminal; (3) the terminal can send the association relationship between the QoS flows to the access network device A; (4) the access network device A performs the coordinated processing of the QoS flows with the association relationship; and (5) the access network device A sends the result of the coordinated processing to the terminal.

[0131] In an example, the first node is the access network device A, and the second node is a core network device, and the coordinated processing procedure includes: (1) the core network device can send its support capability for sending whether the QoS flow has the coordinated processing requirement to the access network device A; (2) in the case that the core network device supports sending whether the QoS flow has the coordinated processing requirement, the access network device A sends its support capability for the coordinated processing to the core network device; (3) in the case that the access network device A supports the coordinated processing, the core network device can send the association relationship between the QoS flows to the access network device A; (4) the access network device A performs the coordinated processing of the QoS flows with the association relationship; and (5) the access network device A sends the result of the coordinated processing to the core network device.

[0132] In some embodiments, the terminal includes at least one of a mobile phone, a wearable device, an Internet of Things device, a communication-capable automobile, a smart automobile, a tablet (Pad), a wireless transceiver-equipped computer, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and the like, but is not limited thereto.

[0133] In some embodiments, the access network device is at least one of a node or device that accesses a terminal to a wireless network, and can include an evolved NodeB (eNB), a next generation eNB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an Open RAN, a Cloud RAN, a base station in other communication systems, an access node in a Wi-Fi system, and the like, but is not limited thereto.

[0134] In some embodiments, the technical solutions of the present disclosure can be applied to an Open RAN architecture, in which case, the interfaces between network devices or within network devices involved in the embodiments of the present disclosure can become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0135] In some embodiments, the access network device can be composed of a CU and a DU, where the CU can also be referred to as a control unit. The CU-DU structure can split the protocol layers of the network device, with some of the protocol layers being controlled by the CU and the rest of the protocol layers being distributed in the DU. The CU controls the DU, but is not limited thereto.

[0136] In some embodiments, the core network device can be one device including the first network element, or can be multiple devices or device groups each including the first network element. The network element can be virtual or physical. The core network includes at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC), for example.

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

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

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

[0140] Hereinafter, terms related to the present disclosure are explained and interpreted.

[0141] I. Multi-modal service

[0142] Multi-modal service refers to a service involving data of multiple modalities, such as augmented reality (AR), virtual reality (VR), cloud game service, and the like. The data of multiple modalities can include audio data, video data, text data, haptic data, and the like, which have a correlation relationship in time and space. For example, when a human body touches objects with different surface textures and materials, the touch feeling is different, and thus the haptic data has a correlation relationship with image data of the object surface. For another example, a video of a user is collected by a camera, and audio of the user for the video is collected by a recording device, and thus the video data has a correlation relationship with the audio data.

[0143] In some embodiments, the multi-modal data can be obtained from the same device or from different devices.

[0144] In some embodiments, the transmission of data streams of different modalities involves different QoS requirements, and thus the different QoS streams of the multi-modal service can have a correlation relationship.

[0145] II. QoS flow

[0146] When a terminal initiates a service request, a core network device establishes a corresponding PDU session. There can be multiple QoS flows in one PDU session, and each QoS flow is identified by a QoS flow ID (QFI). In one PDU session, the QFI of each QoS flow is unique. An access network device maps the QoS flow to a radio bearer (RB), and the QoS flow and the RB can be in a many-to-one mapping relationship or a one-to-one mapping relationship.

[0147] FIG. 1B is a simplified PDU session establishment process. As shown in FIG. 1B, the PDU session establishment process includes:

[0148] In step S1101, the UE initiates a PDU session establishment request to the SMF through the base station and the AMF.

[0149] In step S1102, the SMF obtains the subscription data of the UE from the UDM after receiving the request.

[0150] In step S1103, the SMF obtains the policy rule for the type of user from the PCF after receiving the request.

[0151] In step S1104, the SMF establishes a session with the UPF to establish a user plane connection after receiving the request.

[0152] In step S1105, the SMF initiates a PDU session resource request to the base station.

[0153] In step S1106, the base station sets the corresponding radio resource after receiving the request.

[0154] In step S1107, the base station sends a PDU session resource response to the SMF.

[0155] In step S1108, the SMF updates the UPF to establish a tunnel from the UPF to the base station after receiving the response.

[0156] In some embodiments, after the PDU session is established, a tunnel is generated between the UE, the AN, and the UPF, through which the UE reaches the UPF to connect to a target data network (DN).

[0157] In some embodiments, the QoS flow is managed by the SMF, and the creation and modification of the QoS flow can be triggered by the terminal, the PCF, the UDM, etc., and the deletion of the QoS flow can be triggered by the terminal, the PCF, etc.

[0158] In some embodiments, during the PDU session establishment process, if only part of the QoS flows are successfully established among multiple QoS flows, the application layer can only receive data packets of the successfully established QoS flows. However, due to the association relationship between the multiple QoS flows, part of the QoS flows have not been successfully established. Therefore, for the application layer, it is meaningless to only receive data packets of the successfully established part of the QoS flows, and the application layer may discard the received data packets, which not only causes waste of wireless resources, but also affects user experience.

[0159] The embodiments of the present disclosure provide a communication method, a communication device, a communication system, a storage medium, and a program product. The first node processes the QoS flows having an association relationship in coordination, which facilitates the demand for coordinated transmission between different QoS flows, avoids waste of wireless resources, and ensures user experience.

[0160] FIG. 2A is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2A, the present disclosure relates to a communication method. The communication method is performed by the communication system 100 and includes steps S2101 to S2106.

[0161] In the embodiments of the present disclosure, the communication system includes a terminal A, an access network device A, and a core network device A.

[0162] In step S2101, the terminal A sends third information.

[0163] In some embodiments, the access network device A receives the third information.

[0164] In some embodiments, the third information is used to indicate the support capability of terminal A for whether the sending QoS flow has a cooperative processing requirement.

[0165] In some embodiments, the third information is used to indicate the support capability of terminal A for the association relationship between the sending QoS flows.

[0166] In some embodiments, the third information is used to indicate whether the sending QoS flow supported by terminal A has a cooperative processing requirement. Alternatively, the third information is used to indicate whether the sending QoS flow not supported by terminal A has a cooperative processing requirement.

[0167] In some embodiments, the third information is used to indicate whether the association relationship between the sending QoS flows is supported by terminal A. Alternatively, the third information is used to indicate whether the association relationship between the sending QoS flows is not supported by terminal A.

[0168] In some embodiments, step S2101 can be performed after terminal A and access network device A complete RRC connection establishment, can be performed in a registration process, or can be performed after registration is completed.

[0169] In step S2102, access network device A sends fifth information.

[0170] In some embodiments, terminal A receives the fifth information.

[0171] In some embodiments, the fifth information is used to indicate the support capability of access network device A for cooperative processing.

[0172] In some embodiments, the fifth information is used to indicate that access network device A supports cooperative processing, or the fifth information is used to indicate that access network device A does not support cooperative processing.

[0173] In some embodiments, the fifth information is used to indicate the support capability of access network device A for cooperative processing of the QoS flow of terminal A.

[0174] In some embodiments, the fifth information is used to indicate that access network device A supports cooperative processing of the QoS flow of terminal A. Alternatively, the fifth information is used to indicate that access network device A does not support cooperative processing of the QoS flow of terminal A.

[0175] In some embodiments, the fifth information is used to indicate the support capability of access network device A for cooperative processing of the QoS flow of the terminal accessing cell A.

[0176] In some embodiments, the fifth information is used to indicate that access network device A supports cooperative processing of the QoS flow of the terminal accessing cell A, or the fifth information is used to indicate that access network device A does not support cooperative processing of the QoS flow of the terminal accessing cell A.

[0177] In some embodiments, the access network device A sends the fifth information in a case that the third information is used to indicate whether the terminal A supports sending whether the QoS flow has a cooperative processing requirement.

[0178] In some embodiments, in a case that the third information indicates whether the terminal A supports sending whether the QoS flow has a cooperative processing requirement, and the fifth information indicates that the access network device A does not support cooperative processing of the QoS flow, the terminal A can acquire the capability information (i.e., the fourth information) of the access network device B to realize switching from the access network device A to the access network device B or adding the access network device B, wherein the access network device B supports cooperative processing of the QoS flow.

[0179] In some embodiments, in a case that the fifth information indicates that the access network device A supports cooperative processing of the QoS flow, the access network device A can consider whether to acquire the fourth information of other access network devices based on local resources and / or load balancing conditions.

[0180] In some embodiments, in a case that the third information is used to indicate whether the terminal A supports sending whether the QoS flow has a cooperative processing requirement, the access network device can not send the fifth information.

[0181] In some embodiments, the access network device A sends the fifth information in a case that the third information is used to indicate an association relationship between the QoS flows supported by the terminal A.

[0182] In some embodiments, the step S2101 and the step S2102 are processes of exchanging capability information between the terminal and the access network device A, and the two can be executed in sequence.

[0183] In the step S2103, the terminal A sends a message A.

[0184] In some embodiments, the access network device A receives the message A.

[0185] In some embodiments, the core network device A receives the message A.

[0186] In some embodiments, the message A is used to request establishment of a PDU session.

[0187] In some embodiments, the message A is used to request modification of a PDU session.

[0188] In some embodiments, the message A can be a PDU session establishment request message or a PDU session modification request message.

[0189] In some embodiments, the message A carries the first information.

[0190] In some embodiments, the first information is used to indicate the QoS flow that needs to be established.

[0191] In some embodiments, the first information is used to indicate whether the established QoS flow has a cooperative processing requirement.

[0192] In some embodiments, the first information is used to indicate the QoS flow in the established QoS flow that has a cooperative processing requirement.

[0193] In some embodiments, the first information is used to indicate the QoS flow in the established QoS flow that has an association relationship.

[0194] In some embodiments, the first information can be at least one of service identification information (service ID), identification information of a PDU session (PDU session ID), and identification information of a QoS flow (QFI).

[0195] In some embodiments, the first information can also be combined with at least one of the service identification information, the PDU session identification information, and the QoS flow identification information to indicate the QoS flow that has an association relationship.

[0196] In an example, the first information is combined with the service identification information to indicate the QoS flow that has an association relationship.

[0197] In an example, the first information can be a first value or a second value, the first value is used to indicate that there is an association relationship, and the second value is used to indicate that there is no association relationship. In a case where the first information is the first value, the first information is combined with the service identification information to indicate that all the QoS flows associated with the service indicated by the service identification information have an association relationship. In a case where the first information is the second value, the first information is combined with the service identification information to indicate that none of the QoS flows associated with the service indicated by the service identification information has an association relationship.

[0198] In an example, the first information can be empty or a QFI, the first information being empty indicates that there is no association relationship, and the first information being the QFI indicates that there is an association relationship and the QoS flow that has an association relationship is the QoS flow indicated by the QFI. In a case where the first information is the QFI, the first information is combined with the service identification information to indicate that, among the QoS flows associated with the service indicated by the service identification information, the QoS flow indicated by the QFI has an association relationship.

[0199] In an example, the first information is combined with the PDU session identity information to indicate the QoS flows having the associated relationship. In a case that the first information is a first value, the first information is combined with the PDU session identity information to indicate that all the QoS flows within the PDU session have the associated relationship. In a case that the first information is a second value, the first information is combined with the PDU session identity information to indicate that none of the QoS flows within the PDU session have the associated relationship.

[0200] In some embodiments, the first information is further used to indicate a requirement of the collaborative processing and / or a policy of the collaborative processing.

[0201] In some embodiments, the requirement of the collaborative processing is used to indicate a condition that needs to be met by the data packets in the QoS flow during transmission.

[0202] In some embodiments, the policy of the collaborative processing is used to indicate a policy of establishment of mapping of the QoS flow to the radio bearer.

[0203] In some embodiments, the requirement of the collaborative processing can be understood as a threshold of the collaborative processing, a requirement of the collaborative processing, etc.

[0204] In some embodiments, the requirement of the collaborative processing includes at least one of the following:

[0205] (1) a transmission time difference between the QoS flows having the associated relationship satisfies a first threshold;

[0206] (2) a transmission time difference between a first QoS flow and a second QoS flow in the QoS flows having the associated relationship satisfies the first threshold;

[0207] (3) the transmission of the first QoS flow is faster than the transmission of the second QoS flow by x milliseconds.

[0208] In some embodiments, a priority of the first QoS flow is greater than a priority of the second QoS flow.

[0209] In some embodiments, a QFI value of the first QoS flow is greater than a QFI value of the second QoS flow.

[0210] In some embodiments, the policy of the collaborative processing includes at least one of the following:

[0211] (1) mapping of all the QoS flows having the associated relationship to the radio bearer is established;

[0212] (2) mapping of all the QoS flows having the associated relationship and having a priority greater than a second threshold to the radio bearer is established;

[0213] (3) mapping of at least n QoS flows having the associated relationship to the radio bearer is established.

[0214] In step S2104, the core network device A sends a message B.

[0215] In some embodiments, the access network device receives the message B.

[0216] In some embodiments, the message B is used to request establishment of wireless resources for the PDU session.

[0217] In some embodiments, the message B is used to request modification of wireless resources for the PDU session.

[0218] In some embodiments, the message B can be a PDU session resource establishment request message or a PDU session resource modification request message.

[0219] In step S2105, the access network device A performs coordinated processing on the QoS flows with the associated relationship according to the first information.

[0220] In some embodiments, in the case that the first information indicates the QoS with the associated relationship, the access network device can perform the coordinated processing on the QoS flows with the associated relationship based on its own implementation, and the access network device A can also perform the coordinated processing on the QoS flows with the associated relationship based on the protocol specified coordinated processing strategy and coordinated processing requirement.

[0221] In some embodiments, in the case that the first information indicates the coordinated processing strategy and the coordinated processing requirement, the access network device A performs the coordinated processing on the QoS flows with the associated relationship according to the indication of the first information.

[0222] In step S2106, the access network device A sends second information.

[0223] In some embodiments, the terminal A receives the second information.

[0224] In some embodiments, the second information is used to indicate the result of the coordinated processing on the QoS flows with the associated relationship by the access network device A.

[0225] In some embodiments, the second information is also used to indicate the cause of the coordinated processing result.

[0226] In an example, the second information is used to indicate that the coordinated processing result is a failure, and is also used to indicate that the cause of the failure of the coordinated processing is that the establishment of the QoS flows with the associated relationship fails due to the failure to guarantee the coordinated processing.

[0227] In the embodiments of the present disclosure, steps S2101 to S2102 are processes of interacting capability information between the terminal A and the access network device A, step S2103 is a process of the terminal A sending the first information, and step S2106 is a process of the terminal A receiving the second information sent by the access network device A.

[0228] In some embodiments, the terminal A in steps S2101, S2102, S2103 and S2106 described above can be replaced by the core network device A.

[0229] In some embodiments, the access network device A can send fifth information to the core network device A.

[0230] In some embodiments, the core network device A can receive the fifth information, in which case the access network device A and the core network device A can exchange capability information with each other.

[0231] In some embodiments, the fifth information sent by the access network device A to the core network device A can be carried in an NG setup request (ng setup request) message, a radio access network configuration update (ran configuration update) message or an AMF configuration update acknowledge (amf configuration update acknowledge) message.

[0232] In some embodiments, the core network device A can send third information to the access network device A.

[0233] In some embodiments, the third information sent by the core network device A is used to indicate the support capability of the core network device A for the requirement of cooperative processing between QoS flows.

[0234] In some embodiments, the third information sent by the core network device A is used to indicate the support capability of the core network device A for the association relationship between QoS.

[0235] In some embodiments, the third information sent by the core network device A can be carried in an NG setup response (ng setup response) message, a radio access network configuration update acknowledge (ran configuration update acknowledge) message or an AMF configuration update (amf configuration update) message.

[0236] In some embodiments, the core network device A can send a PDU session resource setup request message carrying the first information to the access network device A.

[0237] In some embodiments, the core network device A can also send, to the access network device A, a PDU session modification request message carrying the first information.

[0238] In some embodiments, the first information sent by the core network device A can be acquired from the terminal A through non-access stratum (NAS) signaling.

[0239] In some embodiments, the access network device A can send, to the core network device A, a PDU session resource setup response message carrying the second information.

[0240] In some embodiments, the second information sent by the access network device A to the core network device A can also be carried in a PDU session resource modification response message.

[0241] In some embodiments, the core network device A can send the received second information to the terminal A through NAS signaling.

[0242] The communication method related to the embodiments of the present disclosure can include at least one of steps S2101 to S2106. For example, step S2101 can be implemented as an independent embodiment. For example, step S2102 can be implemented as an independent embodiment. For example, step S2103 can be implemented as an independent embodiment. For example, step S2104 can be implemented as an independent embodiment. For example, step S2105 can be implemented as an independent embodiment. For example, step S2106 can be implemented as an independent embodiment. For example, steps S2103, S2104 and S2105 can be combined and implemented as an independent embodiment. For example, steps S2105 and S2106 can be combined and implemented as an independent embodiment.

[0243] FIG. 2B is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2B, the embodiment of the present disclosure relates to a communication method. The communication method is performed by the communication system 100 and includes steps S2201 to S2209.

[0244] In the embodiment of the present disclosure, for the dual connectivity scenario, the communication system includes a terminal A, an access network device A, an access network device B, and a core network device A. The access network device A is a secondary base station, and the access network device B is a primary base station.

[0245] In step S2201, the terminal A sends third information.

[0246] In some embodiments, the primary base station receives the third information.

[0247] Optional implementation of step S2201 can refer to optional implementation of step S2101 in FIG. 2A, other associated parts in embodiments involved in FIG. 2A, and details are not described herein.

[0248] In step S2202, the master base station sends the fifth information.

[0249] In some embodiments, the terminal A receives the fifth information.

[0250] In some embodiments, the secondary base station receives the fifth information.

[0251] In some embodiments, the fifth information sent by the master base station to the secondary base station can be carried in an inter-base station interface (such as Xn) establishment request message, for example, an Xn interface establishment request (xn setup request) message.

[0252] In some embodiments, the fifth information sent by the master base station to the secondary base station can be carried in a radio access network node configuration update (ng-ran node configuration update) message.

[0253] Optional implementation of step S2202 can refer to optional implementation of step S2102 in FIG. 2A, other associated parts in embodiments involved in FIG. 2A, and details are not described herein.

[0254] In step S2203, the secondary base station sends the fourth information.

[0255] In some embodiments, the master base station receives the fourth information.

[0256] In some embodiments, the fourth information is used to indicate the support capability of the secondary base station for the coordinated processing of the QoS flow.

[0257] In some embodiments, the fourth information is used to indicate the support capability of the secondary base station for the coordinated processing of the QoS flow of the terminal A.

[0258] In some embodiments, the fourth information is used to indicate the support capability of the secondary base station for the coordinated processing of the QoS flow of the terminal accessing the cell A.

[0259] In some embodiments, the fourth information indicates that the secondary base station supports the coordinated processing of the QoS flow with the associated relationship.

[0260] In some embodiments, the fourth information can be carried in an inter-base station interface establishment response message, for example, an Xn interface establishment response (xn setup response) message.

[0261] In some embodiments, the fourth information can also be carried in a wireless access network node configuration update acknowledge (ng-ran node configuration update acknowledge) message.

[0262] In some embodiments, the step S2202 and the step S2203 are a capability information interaction process between the primary base station and the secondary base station.

[0263] In the step S2204, the terminal A sends a message A.

[0264] In some embodiments, the primary base station receives the message A.

[0265] In some embodiments, the core network device receives the message A.

[0266] In some embodiments, the first information is carried in the message A.

[0267] The optional implementation of the step S2204 can refer to the optional implementation of the step S2103 in FIG. 2A, other associated parts in the embodiments involved in FIG. 2A, and the like, which will not be described here.

[0268] In the step S2205, the core network device A sends a message B.

[0269] In some embodiments, the primary base station receives the message B.

[0270] The optional implementation of the step S2205 can refer to the optional implementation of the step S2104 in FIG. 2A, other associated parts in the embodiments involved in FIG. 2A, and the like, which will not be described here.

[0271] In the step S2206, the primary base station sends a message C.

[0272] In some embodiments, the secondary base station receives the message C.

[0273] In some embodiments, the message C is used to request to add the secondary base station.

[0274] In some embodiments, the message C is used to request to modify the secondary base station.

[0275] In some embodiments, the message C is a secondary base station addition request (S-node addition request) message or a secondary base station modification request (S-node modification request) message.

[0276] In some embodiments, the first information is carried in the message C.

[0277] In some embodiments, in a case where the primary base station itself does not support the coordinated processing of the QoS flow and there is a secondary base station supporting the coordinated processing of the QoS flow, the primary base station can send message C to trigger a secondary base station addition procedure or a secondary base station modification procedure.

[0278] In some embodiments, in a case where the primary base station itself supports the coordinated processing of the QoS flow but considers local resources or load balancing, the primary base station can send message C to trigger a secondary base station addition procedure.

[0279] In step S2207, the secondary base station performs the coordinated processing of the QoS flow with the association relationship according to the first information.

[0280] The optional implementation of step S2207 can refer to the optional implementation of step S2105 in FIG. 2A, other associated parts in the embodiments involved in FIG. 2A, which will not be repeated here.

[0281] In step S2208, the secondary base station sends message D.

[0282] In some embodiments, the primary base station receives message D.

[0283] In some embodiments, message D is a response message of message C.

[0284] In some embodiments, message D is a secondary base station addition request acknowledgement (S-node addition request acknowledgement) message or a secondary base station modification request acknowledgement (S-node modification request acknowledgement) message.

[0285] In some embodiments, the second information is carried in message D.

[0286] In step S2209, the primary base station sends the second information.

[0287] In some embodiments, the terminal A receives the second information.

[0288] In some embodiments, the second information sent by the primary base station can be carried in an RRC reconfiguration message, and the terminal A performs corresponding configuration according to the RRC reconfiguration message to complete the addition or modification of the secondary base station.

[0289] In some embodiments, in a case where the addition or modification of the secondary base station is completed, the terminal A and the secondary base station complete the data packet transmission of the QoS flow with the association relationship.

[0290] The communication method related to the embodiments of the present disclosure can include at least one of steps S2201 to S2209. For example, step S2201 can be implemented as an independent embodiment. For example, step S2202 can be implemented as an independent embodiment. For example, step S2203 can be implemented as an independent embodiment. For example, step S2204 can be implemented as an independent embodiment. For example, step S2205 can be implemented as an independent embodiment. For example, step S2206 can be implemented as an independent embodiment. For example, step S2207 can be implemented as an independent embodiment. For example, step S2208 can be implemented as an independent embodiment. For example, step S2209 can be implemented as an independent embodiment. For example, step S2204, step S2205 and step S2206 can be combined to be implemented as an independent embodiment. For example, step S2205, step S2206 and step S2207 can be combined to be implemented as an independent embodiment. For example, step S2207 and step S2208 can be combined to be implemented as an independent embodiment.

[0291] FIG. 2C is an interaction schematic diagram of a communication method provided by an embodiment of the present disclosure. As shown in FIG. 2C, the embodiment of the present disclosure relates to a communication method, which is performed by the communication system 100 and includes steps S2301 to S2309.

[0292] In the embodiment of the present disclosure, for the handover scenario, the communication system includes a terminal A, an access network device A, an access network device B, and a core network device A. The access network device A is a target base station, and the access network device B is a source base station.

[0293] In step S2301, the terminal A sends third information.

[0294] In some embodiments, the source base station receives the third information.

[0295] The optional implementation of step S2301 can refer to the optional implementation of step S2201 of FIG. 2B, other associated parts in the embodiments related to FIG. 2B, which will not be described here.

[0296] In step S2302, the source base station sends fifth information.

[0297] In some embodiments, the terminal A receives the fifth information.

[0298] In some embodiments, the target base station receives the fifth information.

[0299] The optional implementation of step S2302 can refer to the optional implementation of step S2202 of FIG. 2B, other associated parts in the embodiments related to FIG. 2B, which will not be described here.

[0300] In step S2303, the target base station sends the fourth information.

[0301] In some embodiments, the original base station receives the fourth information.

[0302] Optional implementation of step S2303 can be referred to optional implementation of step S2203 in FIG. 2B, other associated parts in embodiments related to FIG. 2B, and the like, which will not be repeated here.

[0303] In step S2304, the terminal A sends the message A.

[0304] Optional implementation of step S2304 can be referred to optional implementation of step S2204 in FIG. 2B, other associated parts in embodiments related to FIG. 2B, and the like, which will not be repeated here.

[0305] In step S2305, the core network device A sends the message B.

[0306] Optional implementation of step S2305 can be referred to optional implementation of step S2205 in FIG. 2B, other associated parts in embodiments related to FIG. 2B, and the like, which will not be repeated here.

[0307] In step S2306, the original base station sends the message E.

[0308] In some embodiments, the target base station receives the message E.

[0309] In some embodiments, the message E is used to request switching from the original base station to the target base station.

[0310] In some embodiments, the message E is a handover request message.

[0311] In some embodiments, the first information is carried in the message E.

[0312] In some embodiments, for the RRC reestablishment scenario, the message E is used to request obtaining the UE context. For example, the message A is a UE context obtaining request message.

[0313] Optional implementation of step S2306 can be referred to optional implementation of step S2206 in FIG. 2B, other associated parts in embodiments related to FIG. 2B, and the like, which will not be repeated here.

[0314] In step S2307, the target base station performs collaborative processing on the QoS flows having the association relationship according to the first information.

[0315] Optional implementation of step S2307 can be referred to optional implementation of step S2207 in FIG. 2B, other associated parts in embodiments related to FIG. 2B, and the like, which will not be repeated here.

[0316] In step S2308, the target base station sends a message F.

[0317] In some embodiments, the original base station receives the message F.

[0318] In some embodiments, the message F is a response message of the message E.

[0319] In some embodiments, the message F is a handover request acknowledge message.

[0320] In some embodiments, the second information is carried in the message F.

[0321] In some embodiments, for the RRC reestablishment scenario, the message F is used to respond to the acquisition of the UE context. For example, the message F is an acquisition of UE context response message.

[0322] The optional implementation of step S2308 can refer to the optional implementation of step S2208 of FIG. 2B, other associated parts in the embodiments involved in FIG. 2B, which will not be repeated here.

[0323] In step S2309, the original base station sends the second information.

[0324] In some embodiments, the terminal A receives the second information.

[0325] In some embodiments, the second information sent by the original base station can be carried in an RRC reconfiguration message, and the terminal A performs corresponding configuration according to the RRC reconfiguration message to complete the handover from the original base station to the target base station.

[0326] In some embodiments, in the case that the terminal A is handed over from the original base station to the target base station, the terminal A and the target base station complete the packet transmission of the QoS flow having the associated relationship.

[0327] The optional implementation of step S2309 can refer to the optional implementation of step S2209 of FIG. 2B, other associated parts in the embodiments involved in FIG. 2B, which will not be repeated here.

[0328] The communication method related to the embodiments of the present disclosure can include at least one of steps S2301 to S2309. For example, step S2301 can be implemented as an independent embodiment. For example, step S2302 can be implemented as an independent embodiment. For example, step S2303 can be implemented as an independent embodiment. For example, step S2304 can be implemented as an independent embodiment. For example, step S2305 can be implemented as an independent embodiment. For example, step S2306 can be implemented as an independent embodiment. For example, step S2307 can be implemented as an independent embodiment. For example, step S2308 can be implemented as an independent embodiment. For example, step S2309 can be implemented as an independent embodiment. For example, step S2304, step S2305, and step S2306 can be combined to be implemented as an independent embodiment. For example, step S2305, step S2306, and step S2307 can be combined to be implemented as an independent embodiment. For example, step S2307 and step S2308 can be combined to be implemented as an independent embodiment.

[0329] FIG. 2D is an interaction schematic diagram of a communication method provided by an embodiment of the present disclosure. As shown in FIG. 2D, the embodiment of the present disclosure relates to a communication method. The communication method is performed by the communication system 100 and includes steps S2401 to S2403.

[0330] In the embodiment of the present disclosure, the communication system includes an access network device A, and the access network device A includes a CU and a DU.

[0331] In step S2401, the CU sends first information.

[0332] In some embodiments, the first information sent by the CU can be obtained from a terminal or a core network device.

[0333] The optional implementation of step S2401 can refer to the optional implementation of step S2103 of FIG. 2A, other associated parts in the embodiments related to FIG. 2A, which will not be repeated here.

[0334] In step S2402, the DU performs cooperative processing on QoS flows having an association relationship according to the first information.

[0335] The optional implementation of step S2402 can refer to the optional implementation of step S2105 of FIG. 2A, other associated parts in the embodiments related to FIG. 2A, which will not be repeated here.

[0336] In step S2403, the DU sends second information.

[0337] In some embodiments, the CU receives the second information.

[0338] The optional implementation of step S2403 can refer to the optional implementation of step S2106 in FIG. 2A, other associated parts in the embodiments involved in FIG. 2A, and details are not described herein.

[0339] The communication method involved in the embodiments of the present disclosure can include at least one of steps S2401 to S2403. For example, step S2401 can be implemented as an independent embodiment. For example, step S2402 can be implemented as an independent embodiment. For example, step S2403 can be implemented as an independent embodiment. For example, step S2401 and step S2402 can be combined and implemented as an independent embodiment. For example, step S2402 and step S2403 can be combined and implemented as an independent embodiment.

[0340] In some embodiments, the terms “co-processing”, “co-scheduling”, “joint admission control”, “unified scheduling”, and the like can be replaced with each other.

[0341] In some embodiments, the names of information and the like are not limited to the names described in the embodiments, and the terms “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, “chip”, and the like can be replaced with each other.

[0342] In some embodiments, the terms “carrying”, “including”, “containing”, “packaging”, and the like can be replaced with each other.

[0343] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, “RAN-based”, and the like can be replaced with each other.

[0344] In some embodiments, "acquire", "obtain", "get", "receive", "transmit", "bidirectionally transmit", "send and / or receive" can be replaced by each other, which can be interpreted as receiving from other subjects, acquiring from protocols, acquiring from higher layers, obtaining by self-processing, autonomously implementing, and the like.

[0345] In some embodiments, the terms "send", "transmit", "report", "transmit", "request", "bidirectionally transmit", "send and / or receive", and the like can be replaced by each other.

[0346] In some embodiments, the terms "issue", "return", "feedback", "response", "reply", and the like can be replaced by each other.

[0347] In some embodiments, the terms "certain", "preset", "preset", "set", "indicated", "certain", "arbitrary", "first", and the like can be replaced by each other. "Certain A", "preset A", "preset A", "set A", "indicated A", "certain A", "arbitrary A", "first A" can be interpreted as A specified in advance in protocols and the like, can be interpreted as A obtained by setting, configuring, or indicating, and the like, can be interpreted as certain A, certain A, arbitrary A, or first A, and the like, but are not limited thereto.

[0348] In some embodiments, determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values (for example, comparison with a predetermined value), but is not limited thereto.

[0349] FIG. 3A is a flow diagram of a communication method performed by a first node according to an embodiment of the present disclosure. As shown in FIG. 3A, the embodiment of the present disclosure relates to a communication method performed by a first node. The above-mentioned communication method includes steps S3101 to S3106.

[0350] In the embodiment of the present disclosure, the first node is any one of the access network device A, the secondary base station, the target base station, and the DU in the above-mentioned embodiments.

[0351] In step S3101, third information is received.

[0352] The optional implementation of step S3101 can refer to the optional implementation of step S2301 in FIG. 2A, the optional implementation of step S2201 in FIG. 2B, the optional implementation of step S2301 in FIG. 2C, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, and will not be described here.

[0353] In step S3102, the fifth information is sent.

[0354] The optional implementation of step S3102 can refer to the optional implementation of step S2302 in FIG. 2A, the optional implementation of step S2202 in FIG. 2B, the optional implementation of step S2302 in FIG. 2C, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, and will not be described here.

[0355] In step S3103, the fourth information is sent.

[0356] The optional implementation of step S3103 can refer to the optional implementation of step S2203 in FIG. 2B, the optional implementation of step S2303 in FIG. 2C, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, and will not be described here.

[0357] In step S3104, the first information is received.

[0358] The optional implementation of step S3104 can refer to the optional implementation of step S2303 in FIG. 2A, the optional implementation of step S2206 in FIG. 2B, the optional implementation of step S2306 in FIG. 2C, the optional implementation of step S2401 in FIG. 2D, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, other associated parts in the embodiments related to FIG. 2D, and will not be described here.

[0359] In step S3105, the QoS flows with the association relationship are processed cooperatively according to the first information.

[0360] The optional implementation of step S3105 can refer to the optional implementation of step S2305 in FIG. 2A, the optional implementation of step S2207 in FIG. 2B, the optional implementation of step S2307 in FIG. 2C, the optional implementation of step S2402 in FIG. 2D, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, other associated parts in the embodiments related to FIG. 2D, which will not be repeated here. In step S3106, the second information is sent.

[0361] In step S3106, the second information is sent.

[0362] The optional implementation of step S3106 can refer to the optional implementation of step S2306 in FIG. 2A, the optional implementation of step S2208 in FIG. 2B, the optional implementation of step S2308 in FIG. 2C, the optional implementation of step S2403 in FIG. 2D, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, other associated parts in the embodiments related to FIG. 2D, which will not be repeated here.

[0363] FIG. 3B is a flow diagram of a communication method performed by a second node according to an embodiment of the present disclosure. As shown in FIG. 3B, the embodiments of the present disclosure relate to a communication method, which is performed by a second node. The above-mentioned communication method comprises steps S3201 to S3205.

[0364] In the embodiments of the present disclosure, the second node is any one of the terminal A, the master base station, the original base station, and the CU in the above-mentioned embodiments.

[0365] In step S3201, the third information is sent.

[0366] The optional implementation of step S3201 can refer to the optional implementation of step S2301 in FIG. 2A, the optional implementation of step S2201 in FIG. 2B, the optional implementation of step S2301 in FIG. 2C, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, which will not be repeated here.

[0367] In step S3202, the fifth information is received.

[0368] The optional implementation of step S3202 can refer to the optional implementation of step S2302 in FIG. 2A, the optional implementation of step S2202 in FIG. 2B, the optional implementation of step S2302 in FIG. 2C, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, and the like, which will not be repeated here.

[0369] In step S3203, fourth information is received.

[0370] The optional implementation of step S3203 can refer to the optional implementation of step S2203 in FIG. 2B, the optional implementation of step S2303 in FIG. 2C, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, and the like, which will not be repeated here.

[0371] In step S3204, first information is sent.

[0372] The optional implementation of step S3204 can refer to the optional implementation of step S2303 in FIG. 2A, the optional implementation of step S2206 in FIG. 2B, the optional implementation of step S2306 in FIG. 2C, the optional implementation of step S2401 in FIG. 2D, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, other associated parts in the embodiments related to FIG. 2D, and the like, which will not be repeated here.

[0373] In step S3205, second information is received.

[0374] The optional implementation of step S3205 can refer to the optional implementation of step S2306 in FIG. 2A, the optional implementation of step S2208 in FIG. 2B, the optional implementation of step S2308 in FIG. 2C, the optional implementation of step S2403 in FIG. 2D, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, other associated parts in the embodiments related to FIG. 2D, and the like, which will not be repeated here.

[0375] FIG. 4A is a flow diagram of a communication method performed by a first node according to an embodiment of the present disclosure. As shown in FIG. 4A, the embodiment of the present disclosure relates to a communication method, which is performed by a first node. The above-mentioned communication method comprises step S4101.

[0376] In step S4101, QoS flows having an association relationship are processed cooperatively.

[0377] The optional implementation of step S4101 can refer to the optional implementation of step S2305 in FIG. 2A, the optional implementation of step S2207 in FIG. 2B, the optional implementation of step S2307 in FIG. 2C, the optional implementation of step S2402 in FIG. 2D, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, other associated parts in the embodiments related to FIG. 2D, and details are not described herein again. In step S3106, the second information is sent.

[0378] FIG. 4B is a flow diagram of a method for performing communication on a second node side, according to an embodiment of the present disclosure. As shown in FIG. 4B, the embodiments of the present disclosure relate to a method for performing communication, by a second node. The above-mentioned method for performing communication comprises step S4201.

[0379] In step S4201, the first information is sent.

[0380] The optional implementation of step S3204 can refer to the optional implementation of step S2303 in FIG. 2A, the optional implementation of step S2206 in FIG. 2B, the optional implementation of step S2306 in FIG. 2C, the optional implementation of step S2401 in FIG. 2D, other associated parts in the embodiments related to FIG. 2A, other associated parts in the embodiments related to FIG. 2B, other associated parts in the embodiments related to FIG. 2C, other associated parts in the embodiments related to FIG. 2D, and details are not described herein again.

[0381] In the following, the technical solutions of the embodiments of the present disclosure are exemplarily described through specific embodiments.

[0382] In some embodiments, for the newly added multi-modal service application scenarios in the network, the cooperative scheduling processing of the base station is increased.

[0383] In some embodiments, the base station (the first node) obtains the cooperative scheduling information (the first information) from other nodes (the second node), and performs cooperative scheduling processing on the QoS flow according to the first information.

[0384] In some embodiments, the first information includes the QoS flow to be established and the association relationship between the QoS flows.

[0385] In some embodiments, the association relationship can be indicated by an ID, wherein a QoS flow belongs to an ID, and the QoS flows with the same ID have the demand for cooperative scheduling or the demand for admission control.

[0386] In some embodiments, the ID indicating the association relationship is unique in a PDU session.

[0387] In some embodiments, the first information is further used to indicate the requirement of the coordinated scheduling among the QoS flows.

[0388] In some embodiments, the requirement of the coordinated scheduling among the QoS flows includes a time offset of the coordinated scheduling among the QoS flows. In some embodiments, the time offset of the coordinated scheduling among the QoS flows can be understood as that QoS flow 2 is x ms faster than QoS flow 1, or can be understood as that QoS flow 1 is y ms slower than QoS flow 2, or can be understood as that the transmission time difference between the two QoS flows is no more than z ms.

[0389] In some embodiments, the first information is further used to indicate the policy of the coordinated scheduling.

[0390] In some embodiments, the first information is further used to indicate the priority of one or more QoS flows. In some embodiments, if the priority of the QoS flow is not indicated, then the priority is not distinguished.

[0391] In some embodiments, the policy of the coordinated scheduling includes at least one of the following: (1) all the QoS flows with the association relationship need to be successfully established; (2) all the QoS flows with the association relationship and with high priority need to be successfully established; (3) at least n QoS flows with the association relationship need to be successfully established.

[0392] In some embodiments, the first information is further used to indicate the uplink / downlink service. In some embodiments, the first information is obtained from the core network for the uplink / downlink service; in some embodiments, the first information is obtained from the core network for the uplink service, and the core network obtains it from the UE through NAS signaling. In some embodiments, the first information is obtained from the UE.

[0393] In some embodiments, whether the QoS flows belonging to the same service have the requirement of the coordinated scheduling can be expressed by the service ID. Mode 1: reporting 0 means not having the requirement of the coordinated scheduling; reporting a non-0 means having the requirement of the coordinated scheduling; mode 2: reporting empty or not reporting means not having the requirement of the coordinated scheduling; otherwise, means having the requirement of the coordinated scheduling.

[0394] In some embodiments, if the association relationship is only indicated by 0 or 1, then the QoS flows with the association relationship can be reported in the bitmap format for multiple QoS flows.

[0395] In some embodiments, if a separate information field is used for reporting, then SRB3 can be used to report to the secondary node (SN).

[0396] In some embodiments, the base station sends the result of the admission control (the second information) to the second node.

[0397] In some embodiments, the second information is used for whether the result of the admission control is successful.

[0398] In some embodiments, the second information is further used for indicating the cause of the admission control result, such as: the cause of the failure is that the Qos flow establishment fails due to the inability to guarantee the coordinated scheduling.

[0399] In some embodiments, the base station sends the first information and / or the second information of the admission control to the third node.

[0400] In some embodiments, the third node is another gNB.

[0401] In some embodiments, the first information and / or the second information is sent to the third node for the coordinated scheduling of the third node.

[0402] In some embodiments, in the case that the above scenario is a handover scenario, the first node is the original base station; the third node is the target base station, and the first information is carried in the handover request message.

[0403] In some embodiments, in the case that the above scenario is an auxiliary base station addition / change / modification scenario, the first node is the primary base station, the third node is the auxiliary base station, and the first information is carried in the SN addition / modification request message.

[0404] In some embodiments, in the case that the above scenario is an RRC resume / RRC reestablishment scenario, the first node is the original serving base station; the third node is the existing serving base station, and the first information is carried in the UE context acquisition message.

[0405] In some embodiments, the third node sends the result of the coordinated scheduling.

[0406] In some embodiments, the CU node of the base station sends the first information to the DU node for the DU to perform reasonable scheduling.

[0407] In some embodiments, the UE reports the capability to the base station, indicating the capability of supporting the reporting of the coordinated scheduling requirement of the Qos flow in the uplink traffic.

[0408] In some embodiments, the base station reports to the core network the capability of supporting the coordinated scheduling of the Qos flow.

[0409] In some embodiments, the capability of the Qos flow coordinated scheduling can be per base station (preferred), or per cell; or per UE.

[0410] In some embodiments, the base station can inform the core network that it has the capability in the ng setup request; the core network can inform the base station that it has the capability in the ng setup response.

[0411] In some embodiments, the base station can inform the core network that it has the capability in the ran configuration update; the core network can inform the base station that it has the capability in the ran configuration update acknowledge.

[0412] In some embodiments, the core network can inform the base station that it has the capability in the amf configuration update; the base station can inform the core network that it has the capability in the amf configuration update acknowledge.

[0413] In some embodiments, the base stations can interact whether they have the support capability for Qos flow co-scheduling.

[0414] In some embodiments, the capability of Qos flow co-scheduling can be per base station (preferred), or per cell; or per UE.

[0415] In some embodiments, the first base station can inform the target base station that it has the capability in the xn setup request; the second base station can inform the first base station that it has the capability in the xn setup response.

[0416] In some embodiments, the first base station can inform the target base station that it has the capability in the ng-ran node configuration update; the second base station can inform the first base station that it has the capability in the ng-ran node configuration update acknowledge.

[0417] The embodiments of the present disclosure further provide a device for implementing any of the above methods, for example, a terminal is provided, and the terminal includes units or modules for implementing the steps performed by the terminal in any of the above methods. For another example, another network device is provided, and the network device includes units or modules for implementing the steps performed by the network device (for example, an access network device, a core network function node, a core network device, etc.) in any of the above methods.

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

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

[0420] FIG. 5A is a structural schematic diagram of a first node according to an embodiment of the present disclosure. As shown in FIG. 5A, the first node 5100 can include a processing module 5101. In some embodiments, the processing module 5101 is configured to perform cooperative processing on quality of service (QoS) flows having an association relationship. In some embodiments, the first node can further include a transceiver module configured to perform at least one of the communication steps (for example, steps S3101, S3102, and S3103, but not limited thereto) performed by the first node in any of the above methods, and details are not described herein.

[0421] In some embodiments, the first node is any of the access network device A, the secondary base station, the target base station, or the DU in the above embodiments.

[0422] FIG. 5B is an exemplary structural diagram of the second node, provided by an embodiment of the present disclosure. As shown in FIG. 5B, the second node 5200 can include a transceiver module 5201. In some embodiments, the transceiver module 5201 is configured to send first information, the first information being used to indicate a QoS flow having an association relationship, the QoS flow having the association relationship being processed cooperatively by the first node. In some embodiments, the transceiver module 5201 can be configured to perform at least one of the communication steps (for example, steps S3201 and S3202, but not limited to) of sending and / or receiving performed by the second node in any of the above methods, which will not be described here.

[0423] In some embodiments, the second node is any of the terminal A, the master base station, the original base station, and the CU in the above embodiments.

[0424] In some embodiments, the transceiver module described above can include a sending module and / or a receiving module. The sending module and the receiving module can be separate or integrated together. Alternatively, the transceiver module described above can be replaced by a transceiver.

[0425] FIG. 6 is a structural diagram of a communication device, provided by an embodiment of the present disclosure. The communication device 6100 can be any of the first node, the second node, and the fourth node, and can be a chip, a chip system, or a processor supporting the first node to implement any of the above methods, and can be a chip, a chip system, or a processor supporting the second node to implement any of the above methods, and can be a chip, a chip system, or a processor supporting the fourth node to implement any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments, and specific implementation can be referred to the descriptions in the above method embodiments.

[0426] As shown in FIG. 6, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a special-purpose processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (for example, a base station, a baseband chip, a terminal device, a terminal device chip, a DU, or a CU), execute programs, and process data of the programs. Optionally, the communication device 6100 is configured to perform any of the above methods. Optionally, the one or more processors 6101 are configured to invoke instructions to cause the communication device 6100 to perform any of the above methods.

[0427] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (for example, step S3101, step S3201, but not limited to) in the above-described method, and the processor 6101 performs at least one of the other steps (for example, step S3105, but not limited to). In optional embodiments, the transceiver 6102 can include a receiver and / or a transmitter, which can be separate or integrated together. Optionally, the terms transceiver, transceiving unit, transceiver, transceiving circuit, interface circuit, interface, etc. can be replaced with each other, and the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced with each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced with each other.

[0428] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memory 6103 can also be outside the communication device 6100. In optional embodiments, the communication device 6100 can include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected with the memory 6103, and the interface circuit 6104 can be used to receive data from the memory 6103 or other devices, and can be used to send data to the memory 6103 or other devices. For example, the interface circuit 6104 can read the data stored in the memory 6103 and send the data to the processor 6101.

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

[0430] Figure 7 is a structural schematic diagram of a chip according to an embodiment of the present disclosure. For the case where the communication device 6100 can be a chip or a chip system, the structural schematic diagram of the chip 7100 shown in Figure 7 can be referred to, but not limited thereto.

[0431] The chip 7100 comprises one or more processors 7101. The chip 7100 is configured to perform any of the above methods.

[0432] In some embodiments, the chip 7100 further comprises one or more interface circuits 7102. Optionally, the terms interface circuit, interface, transceiver pin, and the like can replace each other. In some embodiments, the chip 7100 further comprises one or more memories 7103 for storing data. Optionally, all or part of the memory 7103 can be outside the chip 7100. Optionally, the interface circuit 7102 is connected with the memory 7103, the interface circuit 7102 can be configured to receive data from the memory 7103 or other devices, and the interface circuit 7102 can be configured to send data to the memory 7103 or other devices. For example, the interface circuit 7102 can read the data stored in the memory 7103 and send the data to the processor 7101.

[0433] In some embodiments, the interface circuit 7102 performs at least one of the communication steps (for example, step S3101, step S3201, but not limited to this) such as sending and / or receiving in the above methods. The interface circuit 7102 performing the communication steps such as sending and / or receiving in the above methods means that the interface circuit 7102 performs data interaction between the processor 7101, the chip 7100, the memory 7103, or the transceiver device. In some embodiments, the processor 7101 performs at least one of the other steps (for example, step S3105, but not limited to this).

[0434] The modules and / or devices described in each of the embodiments of the virtual device, the physical device, the chip, and the like can be combined or separated as appropriate. Optionally, part or all of the steps can also be performed by multiple modules and / or devices in cooperation, which is not limited here.

[0435] The embodiments of the present disclosure also propose a storage medium, and the storage medium stores instructions. When the instructions run on the communication device 6100, the communication device 6100 performs any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices. Optionally, the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a transitory storage medium.

[0436] The embodiments of the present disclosure also propose a program product, and the program product is executed by the communication device 6100, so that the communication device 6100 performs any of the above methods. Optionally, the program product is a computer program product.

[0437] The embodiments of the present disclosure further provide a computer program, which, when running on a computer, enables the computer to perform any of the above methods.

[0438] Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the present application cover any and all variations of the application that come within the scope of the following claims and their equivalents. It is intended that the specification and examples be considered exemplary only, with the true scope and spirit of the application being indicated by the following claims.

[0439] It is to be understood that the application is not limited to particular details described herein and as illustrated in the figures and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application should, therefore, be determined not with reference to the above description, but instead with reference to the appended claims, along with their full scope of equivalents.

Claims

1. A communication method, performed by a first node, the method comprising: coordinately processing quality of service (QoS) flows having a correlation relationship.

2. The method of claim 1, wherein, The QoS flows having the correlation relationship are indicated by first information, which is acquired by the first node from a second node.

3. The method of claim 2, wherein, The first node is a first access network device, and the second node is a terminal, a core network device, or a second access network device; or The first node is a distributed unit of the first access network device, and the second node is a centralized unit of the first access network device.

4. The method of claim 3, wherein, The first access network device is a target base station, and the second access network device is a source base station; or the first access network device is a secondary base station, and the second access network device is a primary base station; or the first access network device is a current serving base station, and the second access network device is a source serving base station.

5. The method according to any one of claims 2 to 4, wherein, The first information is further used to indicate at least one of: a requirement of the coordinately processing; and a policy of the coordinately processing.

6. The method of claim 5, wherein, The requirement of the coordinately processing comprises: a transmission time difference between the QoS flows having the correlation relationship satisfies a first threshold.

7. The method according to any one of claims 1 to 6, wherein, The method further comprises: sending second information to the second node, the second information being used to indicate a result of the coordinately processing.

8. The method of claim 7, wherein, The second information is further used to indicate a reason of the result of the coordinately processing.

9. The method according to any one of claims 1 to 8, wherein, The method further comprises: receiving third information, the third information being used to indicate a support capability of the second node for a requirement of the coordinately processing, the second node being a terminal or a core network device.

10. The method according to any one of claims 1 to 9, wherein, The method further comprises: receiving fourth information, the fourth information being used to indicate a support capability of the second node for the coordinately processing, the second node being a second access network device.

11. The method according to any one of claims 1 to 10, wherein, The method further comprises: sending fifth information, the fifth information being used to indicate a support capability of the first node for the coordinately processing. 12.A communication method, performed by a second node, the method comprising: sending first information, the first information being used to indicate QoS flows having a correlation relationship, the QoS flows having the correlation relationship being coordinately processed by a first node. 13.The method of claim 12, the first node being a first access network device, and the second node being a terminal, a core network device, or a second access network device; or The first node being a distributed unit of the first access network device, and the second node being a centralized unit of the first access network device.

14. The method of claim 12 or 13, wherein, The first access network device being a target base station, and the second access network device being a source base station; or the first access network device being a secondary base station, and the second access network device being a primary base station; or the first access network device being a current serving base station, and the second access network device being a source serving base station.

15. The method according to any one of claims 12 to 14, wherein, The first information is further used to indicate at least one of: a requirement of the coordinately processing; and a policy of the coordinately processing.

16. The method of claim 15, wherein, The requirement of the coordinately processing comprises: a transmission time difference between the QoS flows having the correlation relationship satisfies a first threshold.

17. The method according to any one of claims 12 to 16, wherein, The method further comprises: receiving second information sent by the first node, the second information being used to indicate a result of the coordinately processing.

18. The method of claim 17, wherein, The second information is further used to indicate a cause of a result of the cooperative processing.

19. The method according to any one of claims 12 to 18, wherein, The method further includes: sending third information, the third information being used to indicate a support capability of the second node for a cooperative processing requirement of a QoS flow, the second node being a terminal or a core network device.

20. The method of any one of claims 12 to 19, wherein, The method further includes: sending fourth information, the fourth information being used to indicate a support capability of the second node for the cooperative processing, the second node being a second access network device.

21. The method of any one of claims 12 to 20, wherein, The method further includes: receiving fifth information, the fifth information being used to indicate a support capability of the first node for the cooperative processing. 22.A first node, comprising: a processing module configured to cooperatively process quality of service (QoS) flows having an association relationship. 23.A second node, comprising: a transceiver module configured to send first information, the first information being used to indicate QoS flows having an association relationship, the QoS flows having the association relationship being cooperatively processed by a first node. 24.A communication device, comprising: one or more processors; wherein the communication device is configured to perform the communication method of any one of claims 1 to 21. 25.A communication system, comprising a first node and a second node; the first node is configured to implement the communication method of any one of claims 1 to 11; and the second node is configured to implement the communication method of any one of claims 12 to 21. 26.A storage medium, the storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method of any one of claims 1 to 21. 27.A computer program product, comprising a computer program that, when executed by a processor, implements the communication method of any one of claims 1 to 21.

Images