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

Abstract

The embodiment of the invention relates to a communication method, communication equipment, a communication system, a storage medium and a program product. The communication method can be executed by a first node, and the method comprises the step of carrying out cooperative processing on quality of service (QoS) flows with an incidence relation. In the present disclosure, the first node performs cooperative processing on the QoS flows having the association relationship, which is convenient to realize the demand of cooperative transmission between different QoS flows, avoids the waste of wireless resources, and ensures the user experience.

Description

Technical Field

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

[0002] In order to achieve differentiation of various data flows, the fifth generation (5G) communication system introduces the quality of service (QoS) solution, so as to provide network services with different service qualities for various business needs. The core network equipment can establish one or more protocol data unit (PDU) sessions, and each PDU session can transmit multiple data flows with different QoS requirements, which are called QoS flows. Summary of the invention

[0003] For multimodal services, if multiple QoS flows are associated with each other but only some QoS flows are successfully established, the application layer may discard the received data packets, which not only wastes wireless resources but also affects the user experience.

[0004] The embodiments of the present disclosure provide a communication method, a communication device, a communication system, a storage medium, and a program product.

[0005] According to a first aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a first node. The method includes: collaboratively processing quality of service QoS flows having an associated relationship.

[0006] According to the second aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a second node. The method includes: sending first information, where the first information is used to indicate a QoS flow with an associated relationship, and the QoS flow with an associated relationship is collaboratively processed by the first node.

[0007] According to a third aspect of an embodiment of the present disclosure, a first node is proposed, comprising: a processing module configured to collaboratively process quality of service QoS flows having an associated relationship.

[0008] According to the fourth aspect of an embodiment of the present disclosure, a second node is proposed, comprising: a transceiver module, configured to send first information, wherein the first information is used to indicate a QoS flow with an associated relationship, and the QoS flow with an associated relationship is collaboratively processed by the first node.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising: one or more processors; wherein the communication device is used to execute the communication method of the first aspect or the second aspect.

[0010] According to a sixth aspect of an embodiment of the present disclosure, a communication system is proposed, including a first node and a second node; the first node is configured to implement the communication method as in the first aspect; the second node is configured to implement the communication method as in the second aspect.

[0011] According to a seventh aspect of an embodiment of the present disclosure, a storage medium is proposed, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes a communication method as described in any one of the first to third aspects.

[0012] According to an eighth aspect of an embodiment of the present disclosure, a computer program product is proposed, including a computer program, which implements the communication method of the first aspect or the second aspect when the computer program is executed by a processor.

[0013] According to a ninth aspect of an embodiment of the present disclosure, a computer program is proposed. The computer program includes codes, and when the codes are executed by a processor, the communication method of the first aspect or the second aspect is implemented.

[0014] According to a tenth aspect of an embodiment of the present disclosure, a chip or a chip system is provided, wherein the chip or the chip system includes a processing circuit, and the processing circuit is configured to execute the communication method of the first aspect or the second aspect.

[0015] In the disclosed embodiment, the first node performs collaborative processing on QoS flows with associated relationships, thereby facilitating the realization of collaborative transmission requirements between different QoS flows, avoiding waste of wireless resources, and ensuring user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings required for describing the embodiments are introduced below. The following drawings are only some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

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

[0018] Figure 1B It is a simplified schematic diagram of a PDU session establishment process according to an embodiment of the present disclosure.

[0019] FIG. 2A to FIG. 2D It is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0020] Figure 3A It is a flow chart of a first node executing a communication method according to an embodiment of the present disclosure.

[0021] Figure 3BIt is a flow chart of a second node executing a communication method according to an embodiment of the present disclosure.

[0022] Figure 4A This is another flowchart of a first node executing a communication method according to an embodiment of the present disclosure.

[0023] Figure 4B It is another flowchart diagram of a second node executing a communication method according to an embodiment of the present disclosure.

[0024] Figure 5A It is a structural diagram of a first node provided according to an embodiment of the present disclosure.

[0025] Figure 5B It is a structural diagram of a second node provided according to an embodiment of the present disclosure.

[0026] Figure 6 It is a structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0027] Figure 7 It is a structural schematic diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0029] In a first aspect, an embodiment of the present disclosure provides a communication method executed by a first node, the method comprising: collaboratively processing QoS flows having an associated relationship.

[0030] In the disclosed embodiment, the first node performs collaborative processing on QoS flows with associated relationships, thereby facilitating the realization of collaborative transmission requirements between different QoS flows, avoiding waste of wireless resources, and ensuring user experience.

[0031] In combination with some embodiments of the first aspect, in some embodiments, the QoS flows with an associated relationship are indicated by first information, and the first information is obtained by the first node from the second node.

[0032] In combination with some embodiments of the first 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 distribution unit of the first access network device, and the second node is a centralized unit of the first access network device.

[0033] In combination with some embodiments of the first aspect, in some embodiments, the first access network device is the target base station, and the second access network device is the original base station; or, the first access network device is the auxiliary base station, and the second access network device is the main base station; or, the first access network device is the current serving base station, and the second access network device is the original serving base station.

[0034] In combination with some embodiments of the first aspect, in some embodiments, the first information is further used to indicate at least one of the following: the requirement for the collaborative processing; the strategy for the collaborative processing.

[0035] In combination with some embodiments of the first aspect, in some embodiments, the requirement for collaborative processing includes: a transmission time difference between the associated QoS flows satisfies a first threshold.

[0036] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending second information to the second node, where the second information is used to indicate a result of the collaborative processing.

[0037] In combination with some embodiments of the first aspect, in some embodiments, the second information is also used to indicate the reason for the result of the collaborative processing.

[0038] In combination with some embodiments of the first aspect, in some embodiments, the method also includes: receiving third information, wherein the third information is used to indicate whether the second node has the ability to support collaborative processing requirements for sending QoS flows, and the second node is a terminal or a core network device.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving fourth information, where the fourth information is used to indicate the support capability of the second node for the collaborative processing, and the second node is a second access network device.

[0040] In the disclosed embodiments, access network devices may exchange capability information to achieve a situation where, when the first access network device does not support collaborative processing or the first access network device does not perform collaborative processing on QoS flows due to local resources or load balancing, the second access network device may perform collaborative processing on QoS flows with associated relationships to ensure the requirements for collaborative transmission between different QoS flows and avoid waste of wireless resources.

[0041] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending fifth information, where the fifth information is used to indicate the support capability of the first node for the collaborative processing.

[0042] In a second aspect, an embodiment of the present disclosure provides a communication method executed by a second node, the method comprising: sending first information, wherein the first information is used to indicate a QoS flow with an associated relationship, and the QoS flow with an associated relationship is collaboratively processed by the first node.

[0043] In combination with 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 distribution unit of the first access network device, and the second node is a centralized unit of the first access network device.

[0044] In combination with some embodiments of the second aspect, in some embodiments, the first access network device is the target base station, and the second access network device is the original base station; or, the first access network device is the auxiliary base station, and the second access network device is the main base station; or, the first access network device is the current serving base station, and the second access network device is the original serving base station.

[0045] In combination with some embodiments of the second aspect, in some embodiments, the first information is also used to indicate at least one of the following: the requirement for the collaborative processing; the strategy for the collaborative processing.

[0046] In combination with some embodiments of the second aspect, in some embodiments, the requirement for collaborative processing includes: the transmission time difference between the associated QoS flows satisfies a first threshold.

[0047] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: receiving second information sent by the first node, where the second information is used to indicate a result of the collaborative processing.

[0048] In combination with some embodiments of the second aspect, in some embodiments, the second information is also used to indicate the reason for the result of the collaborative processing.

[0049] In combination with some embodiments of the second aspect, in some embodiments, the method also includes: sending third information, wherein the third information is used to indicate whether the second node has the ability to support collaborative processing requirements for sending QoS flows, and the second node is a terminal or a core network device.

[0050] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending fourth information, where the fourth information is used to indicate the support capability of the second node for the collaborative processing, and the second node is a second access network device.

[0051] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: receiving fifth information, where the fifth information is used to indicate the support capability of the first node for the collaborative processing.

[0052] In a third aspect, an embodiment of the present disclosure provides a first node, comprising: a processing module configured to collaboratively process quality of service QoS flows having an associated relationship.

[0053] In combination with some embodiments of the third aspect, in some embodiments, the QoS flows with an associated relationship are indicated by first information, and the first information is obtained by the third node from the second node.

[0054] In combination with 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 distribution unit of the first access network device, and the second node is a centralized unit of the first access network device.

[0055] In combination with some embodiments of the third aspect, in some embodiments, the first access network device is the target base station, and the second access network device is the original base station; or, the first access network device is the auxiliary base station, and the second access network device is the main base station; or, the first access network device is the current serving base station, and the second access network device is the original serving base station.

[0056] In combination with some embodiments of the third aspect, in some embodiments, the first information is also used to indicate at least one of the following: the requirement for the collaborative processing; the strategy for the collaborative processing.

[0057] In combination with some embodiments of the third aspect, in some embodiments, the requirement for collaborative processing includes: the transmission time difference between the associated QoS flows satisfies a first threshold.

[0058] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: sending second information to the second node, where the second information is used to indicate a result of the collaborative processing.

[0059] In combination with some embodiments of the third aspect, in some embodiments, the second information is also used to indicate the reason for the result of the collaborative processing.

[0060] In combination with some embodiments of the third aspect, in some embodiments, the first node also includes: a transceiver module, configured to receive third information, wherein the third information is used to indicate whether the second node has the ability to support collaborative processing requirements for sending QoS flows, and the second node is a terminal or a core network device.

[0061] In combination with some embodiments of the third aspect, in some embodiments, the transceiver module is further configured to: receive fourth information, where the fourth information is used to indicate the support capability of the second node for the collaborative processing, and the second node is a second access network device.

[0062] In combination with some embodiments of the third aspect, in some embodiments, the transceiver module is further configured to: send fifth information, where the fifth information is used to indicate the support capability of the first node for the collaborative processing.

[0063] In a fourth aspect, an embodiment of the present disclosure provides a second node, comprising: a transceiver module, configured to send first information, wherein the first information is used to indicate a QoS flow with an associated relationship, and the QoS flow with an associated relationship is collaboratively processed by the first node.

[0064] In combination with some embodiments of the fourth 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 distribution unit of the first access network device, and the second node is a centralized unit of the first access network device.

[0065] In combination with some embodiments of the fourth aspect, in some embodiments, the first access network device is the target base station, and the second access network device is the original base station; or, the first access network device is the auxiliary base station, and the second access network device is the main base station; or, the first access network device is the current serving base station, and the second access network device is the original serving base station.

[0066] In combination with some embodiments of the fourth aspect, in some embodiments, the first information is also used to indicate at least one of the following: the requirement for the collaborative processing; the strategy for the collaborative processing.

[0067] In combination with some embodiments of the fourth aspect, in some embodiments, the requirement for collaborative processing includes: the transmission time difference between the associated QoS flows satisfies a first threshold.

[0068] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: receiving second information sent by the first node, where the second information is used to indicate a result of the collaborative processing.

[0069] In combination with some embodiments of the fourth aspect, in some embodiments, the second information is also used to indicate the reason for the result of the collaborative processing.

[0070] In combination with some embodiments of the second aspect, in some embodiments, the method also includes: sending third information, wherein the third information is used to indicate whether the second node has the ability to support collaborative processing requirements for sending QoS flows, and the second node is a terminal or a core network device.

[0071] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: sending fourth information, where the fourth information is used to indicate the support capability of the second node for the collaborative processing, and the second node is a second access network device.

[0072] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: receiving fifth information, where the fifth information is used to indicate the support capability of the first node for the collaborative processing.

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

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

[0075] In a seventh aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the communication method of the first aspect or the second aspect.

[0076] In an eighth aspect, an embodiment of the present disclosure provides a program product. When the program product is executed by a communication device, the communication device executes the communication method of the first aspect or the second aspect.

[0077] In a ninth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first aspect or the second aspect.

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

[0079] It is understandable that the above communication devices, communication systems, storage media, program products, computer programs, chips or chip systems are all used to execute the methods 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 methods, which will not be repeated here.

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

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

[0082] In each embodiment of the present disclosure, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment based on their internal logical relationships.

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

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

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

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

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

[0088] In some embodiments, the recording method of "A or B" may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). When there are more branches such as A, B, C, etc., the above is also similar.

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

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

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

[0092] In some embodiments, terms such as "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", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "no more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

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

[0094] In some embodiments, "network" may be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

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

[0096] 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 the like can be used interchangeably.

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

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

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

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

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

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

[0103] In some embodiments, the first node is used to collaboratively process QoS flows having an associated relationship.

[0104] In some embodiments, collaborative processing may be understood as collaborative scheduling, joint scheduling, joint admission control, unified scheduling, unified processing, and the like.

[0105] In some embodiments, the QoS flows with associated relationships may be understood as QoS flows with collaborative processing requirements, QoS flows with joint admission control requirements, and QoS flows with unified processing requirements.

[0106] In some embodiments, the first node is used to obtain an association relationship between QoS flows.

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

[0108] In some embodiments, the first node is configured to send its own support capability for collaborative processing.

[0109] In some embodiments, the name of the first node is not limited, and it may be, for example, a "co-processing node", "co-scheduling node", "QoS flow processing node", "joint scheduling node", "joint admission control node", etc.

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

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

[0112] In some embodiments, the second node is used to send its own support capability for reporting whether the QoS flow has the collaborative processing requirement.

[0113] In some embodiments, the second node is used to send its own support capability for reporting the association relationship between QoS flows.

[0114] In some embodiments, the second node is used to send its own support capability for collaborative processing.

[0115] In some embodiments, the second node is used to collaboratively process QoS flows having an associated relationship.

[0116] In some embodiments, the name of the second node is not limited, and it may be, for example, a "service initiation node", "service management node", "session management node", "QoS flow management node", etc.

[0117] In some embodiments, the first node may be a first access network device, a distributed unit (DU) of the first access network device, or the like.

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

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

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

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

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

[0123] In one example, the access network device B may support collaborative processing of QoS flows with associated relationships, or may not support collaborative processing of QoS flows with associated relationships.

[0124] In one example, the access network device B may obtain the association relationship between QoS flows from the terminal, the core network device or the access network device C.

[0125] In an example, in a dual-connection scenario, access network device A is a secondary base station, and access network device B is a primary base station.

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

[0127] In one example, in an RRC reconstruction scenario, access network device A is the current serving base station, and access network device B is the original serving base station.

[0128] In one example, the first node is the DU of access network device A, and the second node is the CU of access network device A. The collaborative processing process includes: (1) the CU can send the association relationship between QoS flows to the DU; (2) the DU performs collaborative processing on the QoS flows with the association relationship; (3) the DU sends the result of the collaborative processing to the CU.

[0129] In one example, the first node is access network device A, the second node is a terminal, and the collaborative processing process includes: (1) the terminal can send to the access network device A whether it has the ability to support collaborative processing requirements for reporting QoS flows; (2) when the terminal supports reporting whether the QoS flows have collaborative processing requirements, the access network device A sends to the terminal its ability to support collaborative processing; (3) the terminal can send to the access network device A the association relationship between QoS flows; (4) the access network device A performs collaborative processing on the QoS flows with associated relationships; (5) the access network device A sends the results of the collaborative processing to the terminal.

[0130] In one example, the first node is access network device A, the second node is core network device, and the collaborative processing process includes: (1) the core network device can send to access network device A whether it has the ability to support collaborative processing requirements for sending QoS flows; (2) when the core network device supports whether the sending QoS flows have collaborative processing requirements, access network device A sends to the core network device its ability to support collaborative processing; (3) when access network device A supports collaborative processing, the core network device can send to access network device A the association relationship between QoS flows; (4) access network device A performs collaborative processing on QoS flows with associated relationships; (5) access network device A sends the results of collaborative processing to the core network device.

[0131] In some embodiments, the terminal includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited to these.

[0132] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (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 base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0133] In some embodiments, the technical solution of the present disclosure may be applicable to the Open RAN architecture. In this case, the interfaces between or within network devices involved in the embodiments of the present disclosure may become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.

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

[0135] In some embodiments, the core network device may be a device including a first network element, or may be a plurality of devices or a group of devices, each including a first network element. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0136] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. A person skilled in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0137] The following embodiments of the present disclosure can be applied to Figure 1A The communication system 100, or a portion thereof, is shown but is not limited thereto. Figure 1A The various entities shown are examples, and the communication system may include Figure 1A All or part of the subject, and may also include Figure 1A For entities other than the above, the number and form of each entity are arbitrary, and the connection relationship between the entities is an example. The entities may be connected or disconnected, and the connection may be in any manner, which may be direct or indirect, and may be wired or wireless.

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

[0139] The following describes and explains the terms involved in the present disclosure.

[0140] 1. Multimodal services.

[0141] Multimodal services refer to services involving data of multiple modalities, such as augmented reality (AR), virtual reality (VR), cloud gaming services, etc. Data of multiple modalities may include audio data, video data, text data, tactile data, etc. These data are associated with each other in time and space. For example, when a person touches an object with different surface textures and materials, the touch sensation is different, so the tactile data is associated with the image data on the surface of the object. For another example, if a user's video is captured by a camera, and the user's audio of the video is captured by a recording device, then the video data is associated with the audio data.

[0142] In some embodiments, multimodal data may be obtained from the same device or from different devices.

[0143] In some embodiments, the transmission of data streams of different modes involves different QoS requirements, and therefore, different QoS streams of a multimodal service may be associated with each other.

[0144] 2. QoS flow.

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

[0146] Figure 1B It is a simplified PDU session establishment process, such as Figure 1B As shown, the PDU session establishment process includes:

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

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

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

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

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

[0152] In step S1106, after receiving the request, the base station sets corresponding wireless resources.

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

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

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

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

[0157] In some embodiments, during the PDU session establishment process, if only some of the multiple QoS flows are successfully established, the application layer can only receive data packets of the successfully established QoS flows. However, since the multiple QoS flows are associated with each other, some of the multiple QoS flows have not been successfully established. Therefore, it is meaningless for the application layer to only receive data packets of some of the successfully established QoS flows. The application layer may discard the received data packets, which not only results in a waste of wireless resources, but also affects the user experience.

[0158] 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 performs collaborative processing on QoS flows with associated relationships to facilitate the demand for collaborative transmission between different QoS flows, avoid waste of wireless resources, and ensure user experience.

[0159] Figure 2A FIG. 1 is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. Figure 2A As shown, the embodiment of the present disclosure relates to a communication method. Executed by the communication system 100, the communication method includes steps S2101 to S2106.

[0160] In the embodiment of the present disclosure, the communication system includes terminal A, access network device A, and core network device A.

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

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

[0163] In some embodiments, the third information is used to indicate whether terminal A has the capability to support the collaborative processing requirements for sending the QoS flow.

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

[0165] In some embodiments, the third information is used to indicate whether terminal A supports sending QoS flow with co-processing requirement. Alternatively, the third information is used to indicate whether terminal A does not support sending QoS flow with co-processing requirement.

[0166] In some embodiments, the third information is used to indicate that terminal A supports sending association relationships between QoS flows. Alternatively, the third information is used to indicate that the terminal does not support sending association relationships between QoS flows.

[0167] In some embodiments, step S2101 may be performed after terminal A and access network device A complete the RRC connection establishment, or may be performed during the registration process, or may be performed after the registration is completed.

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

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

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

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

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

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

[0174] In some embodiments, the fifth information is used to indicate the support capability of access network device A for collaborative processing of QoS flows of terminals accessing cell A.

[0175] In some embodiments, the fifth information is used to indicate that access network device A supports collaborative processing of QoS flows of terminals accessing cell A, or the fifth information is used to indicate that access network device A does not support collaborative processing of QoS flows of terminals accessing cell A.

[0176] In some embodiments, when the third information is used to indicate whether terminal A supports sending QoS flow with collaborative processing requirements, access network device A sends fifth information.

[0177] In some embodiments, when the third information indicates whether terminal A supports sending QoS flows with collaborative processing requirements and the fifth information indicates that access network device A does not support collaborative processing of QoS flows, terminal A can obtain capability information of access network device B (i.e., the fourth information) to switch from access network device A to access network device B, or add access network device B, where access network device B supports collaborative processing of QoS flows.

[0178] In some embodiments, when the fifth information indicates that access network device A supports collaborative processing of QoS flows, access network device A may consider whether to obtain the fourth information of other access network devices based on local resources and / or load balancing conditions.

[0179] In some embodiments, when the third information is used to indicate whether terminal A does not support sending a QoS flow with a collaborative processing requirement, the access network device may not send the fifth information.

[0180] In some embodiments, when the third information is used to indicate that terminal A supports sending an association relationship between QoS flows, access network device A sends fifth information.

[0181] In some embodiments, step S2101 and step S2102 are processes in which the terminal and access network device A exchange capability information with each other, and the two can be executed in an exchanged order.

[0182] In step S2103, terminal A sends message A.

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

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

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

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

[0187] In some embodiments, message A may be a PDU session establishment request message or a PDU session modification request message.

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

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

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

[0191] In some embodiments, the first information is used to indicate a QoS flow having a co-processing requirement among the established QoS flows.

[0192] In some embodiments, the first information is used to indicate a QoS flow having an associated relationship among established QoS flows.

[0193] In some embodiments, the first information may 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).

[0194] In some embodiments, the first information may also be combined with at least one of the service identification information, the PDI session identification information, and the identification information of the QoS flow to indicate a QoS flow with an associated relationship.

[0195] In one example, the first information is combined with the service identification information to indicate QoS flows with an associated relationship.

[0196] In one example, the first information may 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. When the first information is the first value, the first information is combined with the service identification information to indicate that all QoS flows associated with the service indicated by the service identification information have an association relationship. When 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 have an association relationship.

[0197] In one example, the first information may be empty or QFI. The empty first information indicates that there is no association relationship. The QFI first information indicates that there is an association relationship and the QoS flow with the association relationship is the QoS flow indicated by the QFI. In the case where the first information is QFI, the first information is combined with the service representation 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.

[0198] In one example, the first information is combined with the PDU session identification information to indicate QoS flows with an associated relationship. When the first information is a first value, the first information is combined with the PDU session identification information to indicate that all QoS flows in the PDU session have an associated relationship. When the first information is a second value, the first information is combined with the PDU session identification information to indicate that none of the QoS flows in the PDU session have an associated relationship.

[0199] In some embodiments, the first information is further used to indicate a requirement for collaborative processing and / or a strategy for collaborative processing.

[0200] In some embodiments, the co-processing requirement is used to indicate conditions that data packets in a QoS flow need to meet during transmission.

[0201] In some embodiments, the co-processing policy is used to indicate an establishment policy for mapping of QoS flows to radio bearers.

[0202] In some embodiments, the demand for collaborative processing may be understood as a threshold for collaborative processing, a requirement for collaborative processing, and the like.

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

[0204] (1) The transmission time difference between the associated QoS flows meets the first threshold;

[0205] (2) The transmission time difference between the first QoS flow and the second QoS flow in the associated QoS flow satisfies the first threshold;

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

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

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

[0209] In some embodiments, the co-processing strategy includes at least one of the following:

[0210] (1) All mappings of associated QoS flows to radio bearers are established;

[0211] (2) Mapping of all QoS flows with priorities greater than a second threshold among the associated QoS flows to radio bearers is established;

[0212] (3) The mapping of at least n QoS flows among the associated QoS flows to radio bearers is fully established.

[0213] In step S2104, core network device A sends message B.

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

[0215] In some embodiments, message B is used to request establishment of radio resources for a PDU session.

[0216] In some embodiments, message B is used to request modification of radio resources for a PDU session.

[0217] In some embodiments, message B may be a PDU session resource establishment request message or a PDU session resource modification request message.

[0218] In step S2105, access network device A performs collaborative processing on associated QoS flows according to the first information.

[0219] In some embodiments, when the first information indicates QoS with an associated relationship, the access network device can collaboratively process the QoS flow with an associated relationship based on its own implementation, and the access network device A can also collaboratively process the QoS flow with an associated relationship based on the collaborative processing strategy and collaborative processing requirements specified in the protocol.

[0220] In some embodiments, when the first information indicates a collaborative processing strategy and a collaborative processing requirement, the access network device A performs collaborative processing on the QoS flows having an associated relationship according to the instruction of the first information.

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

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

[0223] In some embodiments, the second information is used to indicate the result of collaborative processing performed by access network device A on QoS flows with associated relationships.

[0224] In some embodiments, the second information is further used to indicate the cause of the collaborative processing result.

[0225] In one example, the second information is used to indicate that the result of the collaborative processing is a failure, and is also used to indicate that the reason for the failure of the collaborative processing is that the collaborative processing cannot be guaranteed, resulting in the failure to establish the QoS flow with the associated relationship.

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

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

[0228] In some embodiments, access network device A may send fifth information to core network device A.

[0229] In some embodiments, the core network device A may receive the fifth information. In this case, the access network device A and the core network device A may exchange capability information with each other.

[0230] In some embodiments, the fifth information sent by access network device A to core network device A can be carried in an NG setup request message, a radio access network configuration update message, or an AMF configuration update acknowledgement message.

[0231] In some embodiments, core network device A may send third information to access network device A.

[0232] In some embodiments, the third information sent by the core network device A is used to indicate whether the core network device A has the capability to support the collaborative processing requirements for sending the QoS flow.

[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 sending the association relationship between QoS.

[0234] In some embodiments, the third information sent by the core network device A can be carried in an NG setup response message, a radio access network configuration update confirmation message, or an AMF configuration update message.

[0235] In some embodiments, core network device A may send a PDU session resource establishment request message carrying first information to access network device A.

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

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

[0238] In some embodiments, access network device A may send a PDU session resource establishment response message carrying second information to core network device A.

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

[0240] In some embodiments, core network device A may send the received second information to terminal A via NAS signaling.

[0241] The communication method involved in the embodiments of the present disclosure may 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, step S2103, step S2104 and step S2105 can be combined to be implemented as an independent embodiment. For example, step S2105 and step S2106 can be combined to be implemented as an independent embodiment.

[0242] Figure 2B FIG. 1 is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. Figure 2B As shown, the embodiment of the present disclosure relates to a communication method. Executed by the communication system 100, the communication method includes steps S2201 to S2209.

[0243] In the embodiment of the present disclosure, for a dual connection 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.

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

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

[0246] The optional implementation of step S2201 can be found in Figure 2A Optional implementation of step S2101, Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0247] In step S2202, the primary base station sends fifth information.

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

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

[0250] In some embodiments, the fifth information sent by the primary base station to the secondary base station may 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.

[0251] In some embodiments, the fifth information sent by the primary base station to the secondary base station may be carried in a radio access network node configuration update message.

[0252] The optional implementation of step S2202 can be found in Figure 2A Optional implementation of step S2102, Figure 2A Other related parts in the embodiments involved will not be described in detail here.

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

[0254] In some embodiments, the primary base station receives the fourth information.

[0255] In some embodiments, the fourth information is used to indicate a supporting capability of the secondary base station for collaborative processing of the QoS flow.

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

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

[0258] In some embodiments, the fourth information indicates that the secondary base station supports collaborative processing of QoS flows having an associated relationship.

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

[0260] In some embodiments, the fourth information may also be carried in a radio access network node configuration update acknowledgement message.

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

[0262] In step S2204, terminal A sends message A.

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

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

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

[0266] The optional implementation of step S2204 can be found in Figure 2A Optional implementation of step S2103, Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0267] In step S2205, core network device A sends message B.

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

[0269] The optional implementation of step S2205 can be found in Figure 2A Optional implementation of step S2104, Figure 2A Other related parts in the embodiments involved will not be described in detail here.

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

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

[0272] In some embodiments, the message C is used to request adding a secondary base station.

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

[0274] In some embodiments, the message C is an S-node addition request message or an S-node modification request message.

[0275] In some embodiments, message C carries first information.

[0276] In some embodiments, when the primary base station itself does not support collaborative processing of QoS flows, and there is a secondary base station that supports collaborative processing of QoS flows, the primary base station may send a message C to trigger a secondary base station adding process or a secondary base station modifying process.

[0277] In some embodiments, when the primary base station itself supports collaborative processing of QoS flows but takes local resources or load balancing into consideration, the primary base station may send a message C to trigger a secondary base station adding process.

[0278] In step S2207, the secondary base station performs collaborative processing on the associated QoS flows according to the first information.

[0279] The optional implementation of step S2207 can be found in Figure 2A Optional implementation of step S2105, Figure 2A Other related parts in the embodiments involved will not be described in detail here.

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

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

[0282] In some embodiments, message D is a response message to message C.

[0283] In some embodiments, the message D is an S-node addition request acknowledgement message or an S-node modification request acknowledgement message.

[0284] In some embodiments, message D carries second information.

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

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

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

[0288] In some embodiments, when the addition or modification of the secondary base station is completed, the data packet transmission of the QoS flow with the associated relationship is completed between the terminal A and the secondary base station.

[0289] The communication method involved in the embodiment of the present disclosure may 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 as an independent embodiment. For example, step S2205, step S2206 and step S2207 can be combined as an independent embodiment. For example, step S2207 and step S2208 can be combined as an independent embodiment.

[0290] Figure 2C FIG. 1 is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. Figure 2C As shown, the embodiment of the present disclosure relates to a communication method. Executed by the communication system 100, the communication method includes steps S2301 to S2309.

[0291] In the embodiment of the present disclosure, for the handover scenario, the communication system includes terminal A, access network device A, access network device B, and core network device A. Access network device A is the target base station, and access network device B is the original base station.

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

[0293] In some embodiments, the original base station receives the third information.

[0294] The optional implementation of step S2301 can be found in Figure 2B Optional implementation of step S2201, Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0295] In step S2302, the original base station sends fifth information.

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

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

[0298] The optional implementation of step S2302 can be found in Figure 2B Optional implementation of step S2202, Figure 2B Other related parts in the embodiments involved will not be described in detail here.

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

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

[0301] The optional implementation of step S2303 can be found in Figure 2B Optional implementation of step S2203, Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0302] In step S2304, terminal A sends message A.

[0303] The optional implementation of step S2304 can be found in Figure 2B Optional implementation of step S2204, Figure 2B Other related parts in the embodiments involved will not be described in detail here.

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

[0305] The optional implementation of step S2305 can be found in Figure 2B Optional implementation of step S2205, Figure 2B Other related parts in the embodiments involved will not be described in detail here.

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

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

[0308] In some embodiments, the message E is used to request a handover from an original base station to a target base station.

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

[0310] In some embodiments, message E carries first information.

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

[0312] The optional implementation of step S2306 can be found in Figure 2B Optional implementation of step S2206, Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0313] In step S2307, the target base station performs collaborative processing on the associated QoS flows according to the first information.

[0314] The optional implementation of step S2307 can be found in Figure 2B Optional implementation of step S2207, Figure 2B Other related parts in the embodiments involved will not be described in detail here.

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

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

[0317] In some embodiments, message F is a response message to message E.

[0318] In some embodiments, the message F is a handover request acknowledgement message.

[0319] In some embodiments, message F carries second information.

[0320] In some embodiments, for the RRC reestablishment scenario, message F is used to respond to obtaining UE context. For example, message F is a obtain UE context response message.

[0321] The optional implementation of step S2308 can be found in Figure 2B Optional implementation of step S2208, Figure 2B Other related parts in the embodiments involved will not be described in detail here.

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

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

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

[0325] In some embodiments, when terminal A switches from an original base station to a target base station, data packet transmission of a QoS flow having an associated relationship is completed between terminal A and the target base station.

[0326] The optional implementation of step S2309 can be found in Figure 2B Optional implementation of step S2209, Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0327] The communication method involved in the embodiment of the present disclosure may 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 as an independent embodiment. For example, step S2305, step S2306 and step S2307 can be combined as an independent embodiment. For example, step S2307 and step S2308 can be combined as an independent embodiment.

[0328] Figure 2D FIG. 1 is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. Figure 2D As shown, the embodiment of the present disclosure relates to a communication method. Executed by the communication system 100, the communication method includes steps S2401 to S2403.

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

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

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

[0332] The optional implementation of step S2401 can be found in Figure 2A Optional implementation of step S2103, Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0333] In step S2402, the DU performs collaborative processing on the associated QoS flows according to the first information.

[0334] The optional implementation of step S2402 can be found in Figure 2A Optional implementation of step S2105, Figure 2A Other related parts in the embodiments involved will not be described in detail here.

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

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

[0337] The optional implementation of step S2403 can be found in Figure 2A Optional implementation of step S2106, Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0338] The communication method involved in the embodiment of the present disclosure may 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 to be implemented as an independent embodiment. For example, step S2402 and step S2403 can be combined to be implemented as an independent embodiment.

[0339] In some embodiments, the terms "co-processing", "co-scheduling", "joint admission control", "unified scheduling", etc. can be used interchangeably.

[0340] In some embodiments, the names of information, etc. are not limited to the names recorded in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "code element", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0341] In some embodiments, the terms "carry", "include", "comprises", "encapsulate", etc. can be used interchangeably.

[0342] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

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

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

[0345] In some embodiments, terms such as "send", "return", "feedback", "response", and "answer" can be used interchangeably.

[0346] In some embodiments, terms such as "certain", "preset", "preset", "set", "indicated", "some", "any", and "first" can be interchangeable, and "specific A", "preset A", "preset A", "set A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-defined in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., and can also be interpreted as specific A, some A, any A, or first A, etc., but is not limited to this.

[0347] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), 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 to this.

[0348] Figure 3A FIG. 1 is a flow chart of a first node executing a communication method according to an embodiment of the present disclosure. Figure 3A As shown, the embodiment of the present disclosure relates to a communication method, which is executed by a first node. The above communication method includes steps S3101 to S3106.

[0349] 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 embodiments.

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

[0351] The optional implementation of step S3101 can be found in Figure 2A Optional implementation of step S2301, Figure 2B Optional implementation of step S2201, Figure 2COptional implementation of step S2301, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved will not be described in detail here.

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

[0353] The optional implementation of step S3102 can be found in Figure 2A Optional implementation of step S2302, Figure 2B Optional implementation of step S2202, Figure 2C Optional implementation of step S2302, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved will not be described in detail here.

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

[0355] The optional implementation of step S3103 can be found in Figure 2B Optional implementation of step S2203, Figure 2C Optional implementation of step S2303, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved will not be described in detail here.

[0356] In step S3104, first information is received.

[0357] The optional implementation of step S3104 can be found in Figure 2A Optional implementation of step S2303, Figure 2B Optional implementation of step S2206, Figure 2C Optional implementation of step S2306, Figure 2D Optional implementation of step S2401, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved, Figure 2D Other related parts in the embodiments involved will not be described in detail here.

[0358] In step S3105, collaborative processing is performed on the associated QoS flows according to the first information.

[0359] The optional implementation of step S3105 can be found in Figure 2A Optional implementation of step S2305, Figure 2B Optional implementation of step S2207, Figure 2C Optional implementation of step S2307, Figure 2D Optional implementation of step S2402, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved, Figure 2D Other related parts in the embodiments involved are not described in detail here. In step S3106, the second information is sent.

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

[0361] The optional implementation of step S3106 can be found in Figure 2A Optional implementation of step S2306, Figure 2B Optional implementation of step S2208, Figure 2C Optional implementation of step S2308, Figure 2D Optional implementation of step S2403, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved, Figure 2D Other related parts in the embodiments involved will not be described in detail here.

[0362] Figure 3B FIG. 1 is a flow chart of a second node executing a communication method according to an embodiment of the present disclosure. Figure 3B As shown, the embodiment of the present disclosure relates to a communication method, which is executed by a second node. The above communication method includes steps S3201 to S3205.

[0363] In the embodiment of the present disclosure, the second node is any device among the terminal A, the main base station, the original base station, and the CU in the above embodiments.

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

[0365] The optional implementation of step S3201 can be found in Figure 2A Optional implementation of step S2301, Figure 2B Optional implementation of step S2201, Figure 2C Optional implementation of step S2301, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved will not be described in detail here.

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

[0367] The optional implementation of step S3202 can be found in Figure 2A Optional implementation of step S2302, Figure 2B Optional implementation of step S2202, Figure 2C Optional implementation of step S2302, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved will not be described in detail here.

[0368] In step S3203, the fourth information is received.

[0369] The optional implementation of step S3203 can be found in Figure 2B Optional implementation of step S2203, Figure 2C Optional implementation of step S2303, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved will not be described in detail here.

[0370] In step S3204, the first information is sent.

[0371] The optional implementation of step S3204 can be found in Figure 2A Optional implementation of step S2303, Figure 2B Optional implementation of step S2206, Figure 2C Optional implementation of step S2306, Figure 2D Optional implementation of step S2401, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved, Figure 2D Other related parts in the embodiments involved will not be described in detail here.

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

[0373] The optional implementation of step S3205 can be found in Figure 2A Optional implementation of step S2306, Figure 2B Optional implementation of step S2208, Figure 2C Optional implementation of step S2308, Figure 2D Optional implementation of step S2403, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved, Figure 2D Other related parts in the embodiments involved will not be described in detail here.

[0374] Figure 4A FIG. 1 is a flow chart of a communication method performed by a first node side according to an embodiment of the present disclosure. Figure 4A As shown, the embodiment of the present disclosure relates to a communication method, which is executed by a first node. The communication method includes step S4101.

[0375] In step S4101, QoS flows with associated relationships are collaboratively processed.

[0376] The optional implementation of step S4101 can be found in Figure 2A Optional implementation of step S2305, Figure 2B Optional implementation of step S2207, Figure 2C Optional implementation of step S2307, Figure 2D Optional implementation of step S2402, Figure 2A Other related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved, Figure 2D Other related parts in the embodiments involved are not described in detail here. In step S3106, the second information is sent.

[0377] Figure 4B FIG. 1 is a flow chart of a second node side executing a communication method according to an embodiment of the present disclosure. Figure 4B As shown, the embodiment of the present disclosure relates to a communication method, which is executed by a second node. The communication method includes step S4201.

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

[0379] The optional implementation of step S3204 can be found in Figure 2A Optional implementation of step S2303, Figure 2B Optional implementation of step S2206, Figure 2C Optional implementation of step S2306, Figure 2D Optional implementation of step S2401, Figure 2AOther related parts in the embodiments involved, Figure 2B Other related parts in the embodiments involved, Figure 2C Other related parts in the embodiments involved, Figure 2D Other related parts in the embodiments involved will not be described in detail here.

[0380] In the following, the technical solution of the embodiment of the present disclosure is exemplarily described through specific implementation methods.

[0381] In some embodiments, coordinated scheduling processing of base stations is added for newly added multimodal service application scenarios in the network.

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

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

[0384] In some embodiments, the association relationship may be indicated by an ID, which indicates that a QoS flow belongs to an ID. In this case, QoS flows with the same ID have a requirement for coordinated scheduling or a requirement for admission control.

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

[0386] In some embodiments, the first information is also used to indicate a requirement for coordinated scheduling between QoS flows.

[0387] In some embodiments, the requirement for coordinated scheduling between QoS flows includes the time deviation of coordinated scheduling between QoS flows. In some embodiments, the time deviation of coordinated scheduling between QoS flows can be understood as QoS flow 2 is xms faster than QoS flow 1, or as QoS flow 1 is yms slower than QoS flow 2, or as the transmission time difference between the two QoS flows is no greater than z ms.

[0388] In some embodiments, the first information is also used to indicate a collaborative scheduling strategy.

[0389] In some embodiments, the first information is also used for the priority of one or more QoS flows. In some embodiments, when the priority of the QoS flow is not indicated, the priority is not distinguished.

[0390] In some embodiments, the collaborative scheduling strategy includes at least one of the following: (1) all QoS flows with associated relationships need to be successfully established; (2) all QoS flows with high priority among the QoS flows with associated relationships are successfully established; (3) at least n QoS flows with associated relationships are successfully established.

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

[0392] In some embodiments, the service ID can be used to express whether the QoS flows belonging to the same service have a coordinated scheduling requirement. Mode 1: Reporting 0 means no coordinated scheduling requirement; reporting non-zero means coordinated scheduling requirement; Mode 2: Reporting empty or no report means no coordinated scheduling requirement; otherwise, coordinated scheduling requirement is present.

[0393] In some embodiments, when the association relationship is indicated only by 0 or 1, the QoS flows with the association relationship may be reported in a bitmap format for multiple QoS flows.

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

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

[0396] In some embodiments, the second information is used to determine whether the result of the admission control is successful.

[0397] In some embodiments, the second information is also used to indicate the cause of the admission control result, for example: the cause of the failure is that the coordinated scheduling cannot be guaranteed, resulting in the failure of QoS flow establishment.

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

[0399] In some embodiments, the third node is other gNB.

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

[0401] In some embodiments, when the above scenario is a switching 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 switching request message.

[0402] In some embodiments, when the above scenario is a scenario such as adding / changing / modifying a secondary base station, the first node is a primary base station, the third node is a secondary base station, and the first information is carried in the SN adding / modifying request message.

[0403] In some embodiments, when the above scenario is an RRC resume / RRC re-establishment 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.

[0404] In some embodiments, the third node sends a result of the co-scheduling.

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

[0406] In some embodiments, the UE reports a capability to the base station, indicating that it supports the capability of reporting that the QoS flow in its uplink service has a coordinated scheduling requirement.

[0407] In some embodiments, the base station reports to the core network, which can support the collaborative scheduling capability of Qosflow.

[0408] In some embodiments, the QoS flow coordinated scheduling capability may be per base station (preferably), or per cell; or per UE.

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

[0410] In some embodiments, the base station may notify the core network in a RAN Configuration Update that it has this capability; the core network may notify the base station in a RAN Configuration Update Acknowledge that it has this capability.

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

[0412] In some embodiments, base stations may interact with each other to determine whether they have the capability to support QoS flow coordinated scheduling.

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

[0414] In some embodiments, the first base station may notify the target base station that it has the capability in an xn setup request; and the second base station may notify the first base station that it has the capability in an xn setup response.

[0415] In some embodiments, the first base station can notify the target base station that it has the capability in the NG-RAN Node Configuration Update; the second base station can notify the first base station that it has the capability in the NG-RAN Node Configuration Update Acknowledge.

[0416] The embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a terminal is proposed, and the terminal includes a unit or module for implementing each step executed by the terminal in any of the above methods. For another example, another network device is also proposed, including a unit or module for implementing each step executed by a network device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0417] It should be understood that the division of the units or modules in the above device is only a division of logical functions, and in actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. In addition, the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above hardware circuits 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 some or all of the above units or modules are realized by designing the logical relationship of the components in the circuit; for example, in another implementation, the above hardware circuit can be realized by a programmable logic device (PLD), taking a field programmable gate array (FPGA) 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 some or all of the above units or modules. All units or modules of the above devices can be realized in the form of a processor calling software, or in the form of a hardware circuit, or in part by a processor calling software, and the rest by a hardware circuit.

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

[0419] Figure 5A is a schematic diagram of the structure of the first node proposed in the embodiment of the present disclosure. Figure 5A As shown, the first node 5100 may include: a processing module 5101. In some embodiments, the processing module 5101 is used to perform collaborative processing on the quality of service QoS flows with an associated relationship. In some embodiments, the first node may also include a transceiver module, which is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S3101, step S3102, step S3103, but not limited thereto) executed by the first node in any of the above methods, which will not be repeated here.

[0420] In some embodiments, 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 embodiments.

[0421] Figure 5B is an exemplary structural diagram of a second node provided according to an embodiment of the present disclosure. Figure 5BAs shown, the second node 5200 may include a transceiver module 5201. In some embodiments, the transceiver module 5201 is used to send the first information, the first information is used to indicate the QoS flow with the associated relationship, and the QoS flow with the associated relationship is collaboratively processed by the first node. In some embodiments, the transceiver module 5201 can be configured to perform at least one of the communication steps such as sending and / or receiving performed by the second node in any of the above methods (for example, step S3201, step S3202, but not limited thereto), which will not be repeated here.

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

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

[0424] Figure 6 6100 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 6100 may be any one of the first node, the second node, and the fourth node, or may be a chip, a chip system, or a processor that supports the first node to implement any of the above methods, or may be a chip, a chip system, or a processor that supports the second node to implement any of the above methods, or may be a chip, a chip system, or a processor that supports the fourth node to implement any of the above methods. The communication device 6100 may be used to implement the method described in the above method embodiment, and may refer to the description in the above method embodiment for details.

[0425] like Figure 6 As shown, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and the communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute the program, and process the data of the program. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to call instructions so that the communication device 6100 executes any of the above methods.

[0426] 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 such as sending and / or receiving in the above method (for example, step S3101, step S3201, but not limited thereto), and the processor 6101 performs at least one of the other steps (for example, step S3105, but not limited thereto). In an optional embodiment, the transceiver 6102 may include a receiver and / or a transmitter, and the receiver and the transmitter may be separated or integrated together. Optionally, the terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc. may be replaced with each other, the terms such as transmitter, transmitting unit, transmitter, transmitting circuit, etc. may be replaced with each other, and the terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.

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

[0428] The communication device 6100 described in the above embodiments may 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 may not be limited thereto. Figure 6 The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0429] Figure 7 6100 is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. Figure 7The structure diagram of the chip 7100 is shown, but is not limited to this.

[0430] The chip 7100 includes one or more processors 7101. The chip 7100 is configured to execute any of the above methods.

[0431] In some embodiments, the chip 7100 further includes one or more interface circuits 7102. Optionally, the terms such as interface circuit, interface, transceiver pin, etc. can be interchangeable. In some embodiments, the chip 7100 further includes 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 to the memory 7103, and the interface circuit 7102 can be used to receive data from the memory 7103 or other devices, and the interface circuit 7102 can be used 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.

[0432] In some embodiments, the interface circuit 7102 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S3101, step S3201, but not limited thereto). The interface circuit 7102 performs the communication steps such as sending and / or receiving in the above method, for example, 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 thereto).

[0433] The modules and / or devices described in the embodiments such as virtual devices, physical devices, chips, etc. can be combined or separated as needed. Optionally, some or all steps can also be performed by multiple modules and / or devices in collaboration, which is not limited here.

[0434] The embodiment of the present disclosure also proposes a storage medium, on which instructions are stored. When the instructions are executed on the communication device 6100, the communication device 6100 executes 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 temporary storage medium.

[0435] The embodiment of the present disclosure further provides a program product, and when the program product is executed by the communication device 6100, the communication device 6100 executes any of the above methods. Optionally, the program product is a computer program product.

[0436] The embodiment of the present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any of the above methods.

[0437] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present invention are indicated by the following claims.

[0438] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A communication method, performed by a first node, the method comprising: Collaboratively process QoS flows with associated relationships.

2. The method according to claim 1, wherein: The associated QoS flow is indicated by first information, where the first information is acquired by the first node from the second node.

3. The method according to 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 distribution unit of a first access network device, and the second node is a centralized unit of the first access network device.

4. The method according to claim 3, wherein: 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 an auxiliary base station, and the second access network device is a main 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.

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 the following: the need for said collaborative processing; The collaborative processing strategy.

6. The method according to claim 5, wherein: The requirements for collaborative processing include: The transmission time difference between the associated QoS flows meets 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, where the second information is used to indicate a result of the collaborative processing.

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

9. The method according to any one of claims 1 to 8, wherein: The method further comprises: Receive third information, where the third information is used to indicate whether the second node has a support capability for collaborative processing requirements for sending a QoS flow, where the second node is a terminal or a core network device.

10. The method according to any one of claims 1 to 9, wherein: The method further comprises: Fourth information is received, where the fourth information is used to indicate a support capability of a second node for the collaborative processing, and the second node is a second access network device.

11. The method according to any one of claims 1 to 10, wherein: The method further comprises: Send fifth information, where the fifth information is used to indicate the support capability of the first node for the collaborative processing.

12. A communication method, performed by a second node, the method comprising: First information is sent, where the first information is used to indicate QoS flows with an associated relationship, and the QoS flows with an associated relationship are collaboratively processed by the first node.

13. The method according to claim 12, 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 distribution unit of a first access network device, and the second node is a centralized unit of the first access network device.

14. The method according to claim 12 or 13, wherein: 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 an auxiliary base station, and the second access network device is a main 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.

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 the following: the need for said collaborative processing; The collaborative processing strategy.

16. The method according to claim 15, wherein: The requirements for collaborative processing include: The transmission time difference between the associated QoS flows meets a first threshold.

17. The method according to any one of claims 12 to 16, wherein: The method further comprises: Second information sent by the first node is received, where the second information is used to indicate a result of the collaborative processing.

18. The method according to claim 17, wherein: The second information is further used to indicate a reason for a result of the collaborative processing.

19. The method according to any one of claims 12 to 18, wherein: The method further comprises: Send third information, where the third information is used to indicate whether the second node has the support capability for the collaborative processing requirement for sending the QoS flow, and the second node is a terminal or a core network device.

20. The method according to any one of claims 12 to 19, wherein: The method further comprises: Send fourth information, where the fourth information is used to indicate a support capability of a second node for the collaborative processing, and the second node is a second access network device.

21. The method according to any one of claims 12 to 20, wherein: The method further comprises: Fifth information is received, where the fifth information is used to indicate a support capability of the first node for the collaborative processing.

22. A first node, comprising: The processing module is configured to collaboratively process the quality of service (QoS) flows having an associated relationship.

23. A second node, comprising: The transceiver module is configured to send first information, where the first information is used to indicate QoS flows with an associated relationship, and the QoS flows with an associated relationship are collaboratively processed by the first node.

24. A communication device comprising: one or more processors; Wherein, the communication device is used to execute the communication method described in 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 according to any one of claims 1 to 11; the second node is configured to implement the communication method according to any one of claims 12 to 21.

26. A storage medium storing instructions, wherein when the instructions are executed on a communication device, the communication device executes the communication method according to any one of claims 1 to 21.

27. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the communication method according to any one of claims 1 to 21 is implemented.

Images