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

Abstract

Disclosed in embodiments of the present disclosure are a communication method, a communication device, a communication system, and a storage medium. The method executed by a terminal comprises: receiving first quality of service (QoS) rule configuration information, the first QoS rule configuration information comprising a mapping relationship between a first data stream and a first radio bearer; determining a second radio bearer associated with the first data stream; and the second radio bearer being different from the first radio bearer, and sending a first end marker packet in the second radio bearer, wherein the first end marker packet is generated on the basis of a packet data convergence protocol (PDCP). Thus, data remapping is performed by a PDCP layer.

Description

Communication methods, communication equipment, communication systems and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system and storage medium. Background Technology

[0002] In communication systems, there may be services that only transmit data between terminals and access network equipment. Summary of the Invention

[0003] With technological advancements, it may be necessary to terminate the data channel between the terminal and the access network device. How to achieve data remapping for data channels that do not include the Service Data Adaptation Protocol (SDAR) layer is a problem that this disclosure aims to solve.

[0004] This disclosure provides a communication method, communication device, communication system, and storage medium.

[0005] A first aspect of this disclosure provides a communication method, which is executed by a terminal, and the method includes:

[0006] Receive first Quality of Service (QoS) rule configuration information, which includes the mapping relationship between the first data stream and the first radio bearer;

[0007] Determine the second radio bearer associated with the first data stream;

[0008] The second radio bearer differs from the first radio bearer in that it transmits a first end-of-carrier packet, which is generated based on the Packet Data Convergence Protocol (PDCP).

[0009] A second aspect of this disclosure provides a communication method, which is executed by a network device, and the method includes:

[0010] Send first Quality of Service (QoS) rule configuration information, which includes the mapping relationship between the first data stream and the first radio bearer;

[0011] Determine the second radio bearer associated with the first data stream;

[0012] The second radio bearer differs from the first radio bearer in that it receives a first end-of-carrier packet, which is generated based on the Packet Data Convergence Protocol (PDCP).

[0013] A third aspect of this disclosure provides a terminal, the terminal comprising:

[0014] The transceiver module is used to receive first QoS rule configuration information, which includes the mapping relationship between the first data stream and the first radio bearer.

[0015] The processing module is used to determine the second radio bearer associated with the first data stream;

[0016] Unlike the first wireless bearer, the transceiver module described above is also used to send a first end-of-carrier packet in the second wireless bearer, wherein the first end-of-carrier packet is generated based on the Packet Data Convergence Protocol (PDCP).

[0017] A fourth aspect of this disclosure provides a network device, the network device comprising:

[0018] The transceiver module is used to send first QoS rule configuration information, which includes the mapping relationship between the first data stream and the first radio bearer.

[0019] The processing module is used to determine the second radio bearer associated with the first data stream;

[0020] The second radio bearer differs from the first radio bearer in that the transceiver module is also used to receive a first end-of-carrier packet in the second radio bearer, wherein the first end-of-carrier packet is generated based on the Packet Data Convergence Protocol (PDCP).

[0021] A fifth aspect of this disclosure provides a communication device, which includes one or more processors;

[0022] The processor is configured to perform the method as described in the first aspect above, or to perform the method as described in the second aspect above.

[0023] A sixth aspect of this disclosure provides a communication system including a terminal and a network device, wherein the terminal is configured to perform the method described in the first aspect above, and the network device is configured to perform the method described in the second aspect above.

[0024] A seventh aspect of this disclosure provides a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect above, or to perform the method described in the second aspect above.

[0025] An eighth aspect of this disclosure provides a computer program product including a computer program that, when executed by a processor, implements the method described in the first aspect above, or implements the method described in the second aspect above.

[0026] The solution proposed in this disclosure allows the terminal to send an end marker packet on the original radio bearer via the PDCP layer when it determines that the radio bearer associated with the first data stream has changed. This indicates to the network device that the remapping of the first data stream has been completed based on the PDCP layer, thereby providing conditions for improving the reliability of the data channel terminated at the terminal and access network equipment and expanding the service scope of the communication system application. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0028] Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure;

[0029] Figures 1B-1C are schematic diagrams of the Radio only bearer protocol architecture provided in the embodiments of this disclosure;

[0030] Figure 2 is an interactive schematic diagram of the communication method provided in an embodiment of this disclosure;

[0031] Figures 3A-3B are schematic flowcharts of the communication method provided in the embodiments of this disclosure;

[0032] Figure 4A is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure;

[0033] Figure 4B is a schematic diagram of the structure of an access network device provided in an embodiment of this disclosure;

[0034] Figure 5A is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure;

[0035] Figure 5B is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0036] This disclosure provides communication methods, communication devices, communication systems, and storage media.

[0037] In a first aspect, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:

[0038] Receive first Quality of Service (QoS) rule configuration information, wherein the first QoS rule configuration information includes the mapping relationship between the first data stream and the first radio bearer;

[0039] Determine the second radio bearer associated with the first data stream;

[0040] The second radio bearer differs from the first radio bearer in that it transmits a first end-of-carrier packet, which is generated based on the Packet Data Convergence Protocol (PDCP).

[0041] In the above embodiments, when the terminal determines that the radio bearer associated with the first data stream has changed, it can send an end marker packet on the original radio bearer through the PDCP layer to indicate to the network device that the remapping of the first data stream has been completed based on the PDCP layer, thereby providing conditions for improving the reliability of the data channel terminated at the terminal and access network equipment and expanding the service scope of the communication system application.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the determination that the first data stream has been associated with a second radio bearer includes:

[0043] Before receiving the first QoS rule configuration information, if the mapping relationship between the first data stream and the radio bearer has not been configured and a default radio bearer has been configured, the second radio bearer associated with the first data stream is determined to be the default radio bearer.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the determination that the first data stream has been associated with a second radio bearer includes:

[0045] Based on the received second QoS rule configuration information, the second radio bearer associated with the first data stream is determined, wherein the second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

[0046] In the above embodiments, the terminal can determine the original radio bearer corresponding to the first data stream based on whether it has received other mapping relationships corresponding to the first data stream before receiving the first QoS rule configuration information, so as to send the first end marker packet on the original radio bearer, thereby ensuring that the network device can reliably receive the first end marker packet.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the first end marker packet mentioned above includes identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; service type identifier.

[0048] In the above embodiments, the first end marker packet can include various identification information of the first data stream, thereby ensuring that the network device can accurately determine which data stream has been remapped, and providing reliability and accuracy of data transmission between the terminal and the network device.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the second wireless bearer is only associated with the first data stream, and the first end-of-transmission packet does not contain identification information of the first data stream.

[0050] In the above embodiments, if the second wireless bearer is only associated with the first data stream, then the identification information of the first data stream may not be included in the first end-of-transmission marker packet, thereby reducing the resources occupied by transmitting the first end-of-transmission marker packet.

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

[0052] Based on the instructions of the network device, determine whether the end-of-band packet in each radio bearer contains identification information of the associated data stream.

[0053] In the above embodiments, the terminal can determine whether the end-of-band marker packet in each radio bearer needs to carry the identification information of the associated data stream according to the instructions of the network device, thereby ensuring that the terminal and the network device have a consistent understanding of the content in the radio bearer.

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

[0055] Receive downlink data packets, which include a reflection QoS indication;

[0056] The corresponding uplink data stream is determined based on the identification information in the downlink data packet;

[0057] The uplink data packet to radio bearer mapping relationship is not configured. The uplink data packet is mapped to the fourth radio bearer, where the fourth radio bearer corresponds to the downlink data packet.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes: transmitting a second end-of-carry packet generated based on PDCP in a third radio bearer.

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

[0060] Receive downlink data packets, the downlink data packets including a reflection QoS indication;

[0061] The corresponding uplink data stream is determined based on the identification information in the downlink data packet;

[0062] The uplink data packet to radio bearer mapping relationship is not configured. The uplink data packet is mapped to the fourth radio bearer, where the fourth radio bearer corresponds to the downlink data packet.

[0063] In the above embodiments, if the downlink data packet received by the terminal includes a reflection QoS indication, the terminal can remap the uplink data packet corresponding to the downlink data packet to the fourth radio bearer corresponding to that downlink data packet. This achieves PDCP-based reflection QoS functionality, providing conditions for improving the reliability of the data channel terminating between the terminal and network equipment.

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

[0065] It is configured with a default bearer and transmits third end-of-carrier packets based on PDCP in the default radio bearer.

[0066] In the above embodiments, after the terminal completes the remapping of the uplink data packet based on the reflection QoS indication, it sends a second end marker in the original radio bearer (third radio bearer or default radio bearer) corresponding to the uplink data packet, thereby ensuring that the network device and the terminal have a consistent understanding of the radio bearer situation associated with the uplink data packet, and improving the reliability of uplink data transmission.

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

[0068] Store the mapping relationship between uplink data packets and the fourth radio bearer.

[0069] In the above embodiments, after the terminal completes the remapping of uplink data packets based on the reflection QoS indication, it can store the remapped mapping relationship, thereby providing conditions for the reliable transmission of subsequent uplink data packets.

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

[0071] Send capability information, which indicates whether PDCP-based reflection QoS is supported.

[0072] In the above embodiments, the terminal reports to the network device whether it supports PDCP-based reflection QoS, thereby providing conditions for the network device to perform accurate resource scheduling based on the terminal's capabilities.

[0073] Secondly, embodiments of this disclosure provide a communication method, which is executed by a network device, the method comprising:

[0074] Send first Quality of Service (QoS) rule configuration information, wherein the first QoS rule configuration information includes the mapping relationship between the first data stream and the first radio bearer;

[0075] Determine the second radio bearer associated with the first data stream.

[0076] The second radio bearer differs from the first radio bearer in that it receives a first end-of-carrier packet, which is generated based on the Packet Data Convergence Protocol (PDCP).

[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the determination that the first data stream has been associated with a second radio bearer includes:

[0078] Before sending the first QoS rule configuration information, the mapping relationship between the first data stream and the wireless bearer is not configured, and a default bearer is configured. The default wireless bearer is determined to be the second wireless bearer.

[0079] In conjunction with some embodiments of the second aspect, in some embodiments, the determination that the first data stream has been associated with a second radio bearer includes:

[0080] Based on the sent second QoS rule configuration information, the second radio bearer associated with the first data stream is determined, wherein the second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

[0081] In conjunction with some embodiments of the second aspect, in some embodiments, the first end marker packet mentioned above includes identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; type identifier of the service to which it belongs.

[0082] In conjunction with some embodiments of the second aspect, in some embodiments, the second wireless bearer is only associated with the first data stream, and the first end-of-transmission packet does not contain identification information of the first data stream.

[0083] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0084] Send indication information, which indicates whether the end-of-band packet in each radio bearer contains the identification information of the corresponding data stream.

[0085] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0086] Send downlink data packets, which include a reflection QoS indication;

[0087] The corresponding uplink data packet is determined based on the identification information in the downlink data packet;

[0088] Determine the third radio bearer corresponding to the uplink data stream;

[0089] Receive end marker packets generated based on PDCP in the third radio bearer.

[0090] In conjunction with some embodiments of the second aspect, in some embodiments, if a mapping relationship corresponding to an uplink data packet has been configured, then the radio bearer indicated in the mapping relationship can be determined as a third radio bearer.

[0091] In conjunction with some embodiments of the second aspect, in some embodiments, if the bearer corresponding to the uplink data packet is not configured and the terminal is configured with a default wireless bearer, then the default wireless bearer can be determined as the third wireless bearer.

[0092] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0093] Receive capability information, whereby the capability information is used to indicate whether PDCP-based reflection QoS is supported.

[0094] Thirdly, embodiments of this disclosure provide a terminal, the terminal comprising:

[0095] The transceiver module is used to receive first QoS rule configuration information, wherein the first QoS rule configuration information includes the mapping relationship between the first data stream and the first radio bearer.

[0096] The processing module is used to determine the second radio bearer associated with the first data stream.

[0097] Unlike the first wireless bearer, the transceiver module described above is also used to send a first end-of-carrier packet in the second wireless bearer, wherein the first end-of-carrier packet is generated based on the Packet Data Convergence Protocol (PDCP).

[0098] In conjunction with some embodiments of the third aspect, in some embodiments, the above-described processing module is further configured to:

[0099] Before receiving the first QoS rule configuration information, if the mapping relationship between the first data stream and the radio bearer has not been configured and a default radio bearer has been configured, the second radio bearer associated with the first data stream is determined to be the default radio bearer.

[0100] In conjunction with some embodiments of the third aspect, in some embodiments, the above-described processing module is further configured to:

[0101] Based on the received second QoS rule configuration information, the second radio bearer associated with the first data stream is determined, wherein the second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

[0102] In conjunction with some embodiments of the third aspect, in some embodiments, the first end marker packet mentioned above includes identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; service type identifier.

[0103] In conjunction with some embodiments of the third aspect, in some embodiments, the second wireless bearer is only associated with the first data stream, and the first end marker packet does not contain the identification information of the first data stream.

[0104] In conjunction with some embodiments of the third aspect, in some embodiments, the above-described processing module is further configured to:

[0105] Based on the instructions of the network device, determine whether the end-of-band packet in each radio bearer contains identification information of the associated data stream.

[0106] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module described above is further configured to receive downlink data packets, the downlink data packets including a reflection QoS indication;

[0107] The aforementioned processing module is also used to determine the corresponding uplink data stream based on the identification information in the downlink data packet;

[0108] Since the mapping relationship between uplink data packets and radio bearers is not configured, the above processing module is also used to map uplink data packets to a fourth radio bearer, wherein the fourth radio bearer corresponds to downlink data packets.

[0109] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module described above is further configured to transmit a second end-of-carrier packet generated based on PDCP in a third radio bearer.

[0110] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module described above is further configured to receive downlink data packets, the downlink data packets including a reflection QoS indication;

[0111] The aforementioned processing module is also used to determine the corresponding uplink data stream based on the identification information in the downlink data packet;

[0112] Since the mapping relationship between uplink data packets and radio bearers is not configured, the above processing module is also used to map uplink data packets to a fourth radio bearer, wherein the fourth radio bearer corresponds to downlink data packets.

[0113] In conjunction with some embodiments of the third aspect, in some embodiments, a default bearer is configured, and the aforementioned processing module is further configured to send a third end-of-carrier packet generated based on PDCP in the default radio bearer.

[0114] In conjunction with some embodiments of the third aspect, in some embodiments, the above-mentioned processing module is further used to store the mapping relationship between uplink data packets and the fourth radio bearer.

[0115] In conjunction with some embodiments of the third aspect, in some embodiments, the aforementioned transceiver module is further configured to send capability information, wherein the capability information is used to indicate whether PDCP-based reflection QoS is supported.

[0116] Fourthly, embodiments of this disclosure provide a network device, the network device comprising:

[0117] The transceiver module is used to send first QoS rule configuration information, wherein the first QoS rule configuration information includes the mapping relationship between the first data stream and the first radio bearer;

[0118] The processing module is used to determine the second radio bearer associated with the first data stream.

[0119] The second radio bearer differs from the first radio bearer in that the transceiver module is also used to receive a first end-of-carrier packet in the second radio bearer, wherein the first end-of-carrier packet is generated based on the Packet Data Convergence Protocol (PDCP).

[0120] In conjunction with some embodiments of the fourth aspect, in some embodiments, before sending the first QoS rule configuration information, the mapping relationship between the first data stream and the wireless bearer is not configured, and a default bearer is configured, the above processing module is further used to determine that the default wireless bearer is the second wireless bearer.

[0121] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described processing module is further configured to:

[0122] Based on the sent second QoS rule configuration information, the second radio bearer associated with the first data stream is determined, wherein the second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

[0123] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first end marker packet mentioned above includes identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; type identifier of the service to which it belongs.

[0124] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second wireless bearer is associated only with the first data stream, and the first end-of-transmission packet does not contain identification information of the first data stream.

[0125] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described transceiver module is further used for:

[0126] Send indication information, which indicates whether the end-of-band packet in each radio bearer contains the identification information of the corresponding data stream.

[0127] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module described above is further configured to send downlink data packets, the downlink data packets including a reflection QoS indication;

[0128] The aforementioned processing module is also used to determine the corresponding uplink data packet based on the identification information in the downlink data packet;

[0129] The aforementioned processing module is also used to determine the third radio bearer corresponding to the uplink data stream;

[0130] The aforementioned transceiver module is also used to receive end marker packets generated based on PDCP in the third radio bearer.

[0131] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module described above is further configured to receive capability information, wherein the capability information is used to indicate whether PDCP-based reflection QoS is supported.

[0132] Fifthly, embodiments of this disclosure provide a communication device, which includes one or more processors; wherein the communication device is used to execute the first aspect and optional implementations of the first aspect, or to execute the second aspect and optional implementations of the second aspect.

[0133] In a sixth aspect, embodiments of this disclosure provide a communication system comprising: a terminal and a network device; wherein the network device is configured to perform the method described in the first aspect and optional implementations thereof, and the terminal is configured to perform the method described in the second aspect and optional implementations thereof.

[0134] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementations, or to perform the method described in the second aspect and its optional implementations.

[0135] Eighthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method described in the first aspect and its optional implementations, or to perform the method described in the second aspect and its optional implementations.

[0136] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the method as described in the first aspect and optional implementations of the first aspect, or to perform the method as described in the second aspect and optional implementations of the second aspect.

[0137] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the method described according to the first aspect and optional implementations thereof, or configured to perform the method described according to the second aspect and optional implementations thereof.

[0138] It is understood that the aforementioned terminals, network devices, 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 this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0139] This disclosure provides a communication method, a communication device, a communication system, and a storage medium. In some embodiments, the terms "communication method" and "information processing method" can be used interchangeably; the terms "communication method apparatus" and "information processing apparatus" can be used interchangeably; and the terms "message transmission system" and "information processing system" can be used interchangeably.

[0140] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0141] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0142] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0143] In this disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the aforementioned," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular or a plural expression.

[0144] In the embodiments of this disclosure, "multiple" refers to two or more.

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

[0146] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless 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). The same applies when there are more branches such as A, B, C, etc.

[0147] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0148] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0149] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0150] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0151] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0152] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "body", etc.

[0153] In some embodiments, "network" can be interpreted as devices included in the network, such as access network devices, core network devices, etc.

[0154] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)," "base station (BS)," "radio base station," or "fixed station." In some embodiments, it may also be understood as "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," or "bandwidth part (BWP)."

[0155] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "Narrow Band-Internet of Things (NB-IoT) device," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," etc.

[0156] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0157] 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, core network device, or network device may also be configured to have all or some of the functions of the terminal.

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

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

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

[0161] As shown in Figure 1A, the communication system 100 includes a terminal 101 and a network device 102.

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

[0163] In some embodiments, network device 102 may be an access network device and / or a core network device.

[0164] In some embodiments, network device 102 may be a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

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

[0166] In some embodiments, the core network equipment may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network equipment. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0167] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Protocol Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0168] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0169] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0170] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0171] In some embodiments, data transmission can occur between a terminal (UE) and a data network (DN), whereby the network establishes a Packet Data Unit (PDU) session between the UE and the DN for transmitting data between the UE and the DN.

[0172] In some embodiments, services in a communication system can take many forms. The data consumer and the data source are no longer limited to the Data Network and the UE, but can also be between the UE and network devices (such as access network devices).

[0173] In some embodiments, the service resides solely between the UE and the access network equipment (e.g., a base station). This means the service data source is located at the UE (including data distributedly stored on the UE side, or data directly generated or collected on the UE side), and the final destination of the service data, i.e., the consumer, is the base station. Alternatively, the service data source is located at the base station (including data distributedly stored on the base station side, or data directly generated or collected on the base station side), and the final destination of the service data, i.e., the consumer, is the UE. The aforementioned data may include, for example,: artificial intelligence (AI) model data in the Radio Access Network (RAN), AI model training data, sensing result data, data from applications deployed at the edge on the base station side, data that needs to be stored or processed on the base station side, data deployed on satellites, etc.

[0174] For example, in Artificial Intelligence (AI) services, AI model data might be generated by the base station itself, or the base station itself might act as the consumer of the AI ​​model, using it for AI inference to enhance air interface performance. Similarly, the base station might use AI training data to train the AI ​​model, making it the consumer of the training data. Alternatively, the AI ​​training data could come from data collected by the base station itself, making it the source of the training data.

[0175] Alternatively, in a sensing service, the base station can collect a large amount of sensing data based on its wireless sensing capabilities, such as 3D point cloud data, which includes spatial information and velocity information of the sensed objects. In this case, the base station is the source of the sensing data, and if the sensing data is sent to the terminal, then the UE is the consumer of the data.

[0176] In some embodiments, for other services deployed at the base station, such as video, the base station can be understood as the data source, and the terminal downloading the video is the data consumer. The network can use distributed storage to pre-store large amounts of data at the base station.

[0177] In some embodiments, services that utilize the storage and computing capabilities of a base station may simply be services that utilize the base station's storage and computing capabilities. For example, in Extended Reality (XR) services, the terminal can send data to the base station for computation and then send it back to the terminal. In this case, the base station is the data consumer, and the UE is the data source.

[0178] Alternatively, for services deployed on satellites, the base stations are also deployed on satellites, which reduces service implementation complexity. In this case, the service terminates between the UE and the satellite (base station).

[0179] In some embodiments, if data transmission occurs only between the UE and the base station, establishing a data channel using existing PDU sessions would require extensive signaling interactions between core network elements, such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), and Policy Control Function (PCF) elements, resulting in low efficiency in establishing PDU sessions. However, for services between the UE and gNB, the involvement of these network elements is not required, allowing for the establishment of a data channel terminating between the UE and the base station.

[0180] In some embodiments, a data channel terminating between the UE and the base station can be referred to as a radio-only bearer. Its core difference from the existing PDU Session is that it does not involve core network elements.

[0181] In some embodiments, the protocol stack design for a radio-only bearer may not include an SDAP layer. The architecture of the radio-only bearer protocol on the terminal side may be as shown in Figures 1B and 1C.

[0182] In some embodiments, as shown in Figure 1B, the terminal can directly map uplink (UL) packets to the data radio bearer (DRB) based on Quality of Service (QoS) rules without going through any protocol layer or applying flow marking. The DRB is then submitted to the Packet Data Convergence Protocol layer for processing.

[0183] In some embodiments, as shown in FIG1C, the terminal can configure QoS rules at the PDCP layer, and the PDCP layer completes the mapping of UL packets to AS QoS flow, with no flow marking applied.

[0184] In the architecture of the Radio-only bearer protocol shown in Figures 1B and 1C, Protocol A represents the application protocol, such as an AI protocol or a perception protocol, and is used to process application layer data. The Service Data Adaptation Protocol (SDAR) layer is used for mapping between QoS streams and DRBs in user plane data transmission, and marking QoS stream IDs. The Packet Data Convergence Protocol layer is primarily responsible for ensuring the reliability and integrity of data transmission. This includes implementing packet data compression and decompression, verifying the reliability and integrity of data transmission, and adapting between the IP layer and the physical layer. The Radio Link Control (RLC) layer is responsible for data transmission control on the radio link, including data segmentation and reassembly, retransmission control, and sequencing control, to ensure reliable data transmission on the radio link. The Media Access Control (MAC) layer is responsible for controlling the physical medium connecting to the physical layer. When sending data, the MAC layer can determine whether data can be sent and add control information to the data, sending it to the physical layer in a specified format. The Physical (PHY) layer is responsible for the transmission of bit streams, that is, the sending and receiving of signals.

[0185] In some embodiments, if a QoS flow is remapped from one radio bearer (RB) to another, for example, from Data Radio Bearer (DRB) #1 to DRB #2, it is necessary to determine how to ensure that packets are delivered in order. Additionally, for radio-only bearer services, it is necessary to determine how to implement reflective QoS, that is, how to determine the mapping relationship between uplink QoS flow and DRB based on the mapping relationship between downlink QoS flow and DRB.

[0186] The communication method proposed in this disclosure provides a remapping method for Radio-only bearers, which is used to remap data generated in the Radio Access Network (RAN), thereby improving the reliability of radio bearers terminated at base stations and terminals and expanding the range of services supported by the communication system.

[0187] The communication methods, communication devices, communication systems, and storage media provided in this disclosure will now be described in detail with reference to the accompanying drawings.

[0188] Figure 2 is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 2, the communication method involved in this embodiment is executed by a communication system, which may include a terminal and network devices. The method is described below, and as shown in Figure 2, the method includes:

[0189] Step S2101: Send the second QoS rule configuration information.

[0190] The second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

[0191] In some embodiments, the second QoS rule configuration information can be used to configure a list of access layer quality of service (QoS) rules, wherein the QoS rules are used to indicate the mapping relationship between access layer protocol packets and radio bearers.

[0192] In some embodiments, access layer QoS rules are rules established in the access layer of a communication system to ensure the quality of data transmission. QoS rules may include specific quality of service requirements, such as bandwidth, latency, and packet loss rate.

[0193] In some embodiments, QoS rules can be used to indicate the mapping relationship between access layer protocol packets and DRBs.

[0194] In some embodiments, since the communication system can support multiple types of application protocols, in order to distinguish the data packets corresponding to different protocols, QoS rules can also be used to indicate the mapping relationship between data packets of different access layer application protocols and DRBs.

[0195] In some embodiments, the terminal may receive second QoS rule configuration information sent by the network device. The terminal can use the above configuration in either an inactive or connected state.

[0196] In some embodiments, the terminal may be a regular terminal, a non-terrestrial network (NTN) terminal, or any other type of terminal, which is not limited in this disclosure.

[0197] In some embodiments, the terminal may filter the first data stream based on the packet filter associated with the first data stream in the second QoS rule configuration information.

[0198] In some embodiments, QoS rules may include a set of packet filter sets. Packet filter sets are used to identify and classify data packets in the network. Through a series of matching rules, data packets that meet specific conditions can be grouped into the same data stream and processed and managed uniformly. This enables fine-grained control over different data streams and optimizes the utilization of network resources.

[0199] In some embodiments, the terminal may map the first data stream to the second radio bearer according to the second QoS rule configuration information.

[0200] In some embodiments, if the network device has not configured the mapping relationship of the first data stream for the terminal, or the terminal has just connected to the network and has not yet received the configuration from the network device, but the terminal is configured with a default wireless bearer, then the terminal can determine the default wireless bearer as the second wireless bearer associated with the first data stream. That is, the first data stream is mapped to the default wireless bearer, thereby ensuring reliable data transmission.

[0201] Step S2102: Send the first QoS rule configuration information.

[0202] The first QoS rule configuration information includes the mapping relationship between the first data stream and the first radio bearer.

[0203] In some embodiments, the network device may send the first QoS rule configuration information to the terminal when the first data stream needs to be remapped (i.e., remapped from the second radio bearer to the first radio bearer); or when the second QoS rule configuration information becomes invalid; or when the second QoS rule configuration information is updated.

[0204] In step S2103, the first radio bearer is different from the second radio bearer, and the first end marker packet is sent in the second radio bearer.

[0205] The first end marker data packet is generated based on PDCP.

[0206] In some embodiments, terms such as "end marker", "end identifier", "termination identifier", "end sign", "end mark", "end sign", "end identifier", and "end mark" can all be used to indicate that the current data stream transmission has ended (completed). In some scenarios, the above terms can be used interchangeably.

[0207] In some embodiments, after receiving the first QoS rule configuration information, if the first radio bearer associated with the first data flow indicated in the first QoS rule configuration information is different from the second radio bearer that the terminal has determined is associated with the first data flow, then the terminal can determine that the first data flow needs to be remapped (or determine that the radio bearer mapped by the first data flow has changed), and thus can send an end marker packet in the second radio bearer (the original radio bearer) that the first data flow is associated with, to indicate to the network device that the first data flow has ended on the second radio bearer.

[0208] In some embodiments, if the terminal has not been configured with a mapping relationship between the first data stream and the radio bearer before receiving the first QoS rule configuration information, and the terminal is configured with a default radio bearer, then in order to ensure the transmission of the first data stream, the terminal can map the first data stream onto the default radio bearer. That is, the second radio bearer associated with the first data stream is the default radio bearer.

[0209] In some embodiments, if the terminal has received the second QoS rule configuration information before receiving the first QoS rule configuration information, then the terminal can determine the association between the first data stream and the second radio bearer based on the configured second QoS rule configuration information.

[0210] In some embodiments, if the data mapping function of the data transmission channel terminating between the terminal and the access network device is implemented by the PDCP layer, then after the PDCP layer of the terminal determines that the radio bearer of the first data stream has been remapped (that is, the radio bearer associated with the first data stream has changed), it can send a first end marker packet in the second radio bearer corresponding to the first data stream before the change (original).

[0211] In some embodiments, terms such as "the end-of-term tag packet is generated based on PDCP", "the PDCP layer sends the end-of-term tag packet", and "the PDCP entity sends the end-of-term tag packet" can all be used to indicate that the end-of-term tag packet is generated at the PDCP layer. In some scenarios, the above terms can be used interchangeably.

[0212] In some implementations, the aforementioned end marker can be a PDCP Protocol Data Unit (PDU). This end marker may not carry a sequence number (SN), allowing the network device to determine that it has received an end marker packet upon receiving a control PDU without an SN.

[0213] In some embodiments, the end marker packet may also include indication information to indicate whether the end marker packet is a Data PDU or a Control PDU.

[0214] In some embodiments, the aforementioned end marker packet may occupy one byte or two bytes of the original radio bearer, etc., and this disclosure does not limit this.

[0215] In some embodiments, since multiple data streams may be mapped in the second wireless bearer, in order to ensure that the network device can accurately determine which data stream the first end-of-transmission packet corresponds to, the terminal may carry the identification information of the first data stream in the first end-of-transmission packet.

[0216] In some embodiments, since QoS rule identifiers can be used to classify and label data streams, the identification information of the first data stream can be the QoS rule identifier (ID) configured by the network device for the first data stream.

[0217] In some embodiments, the QoS rule ID carried in the first end marker packet may be the QoS rule ID corresponding to the first data stream indicated in the first QoS configuration information; or it may be the QoS rule ID corresponding to the first data stream indicated in the second QoS configuration information; or it may include both the QoS rule ID corresponding to the first data stream indicated in the first QoS configuration information and the QoS rule ID corresponding to the first data stream indicated in the second QoS configuration information. This disclosure does not limit this.

[0218] In some embodiments, the identification information of the first data flow may also be the QoS flow identifier corresponding to the first data flow.

[0219] In some embodiments, since different types of services correspond to different data streams, in this embodiment of the disclosure, the service type identifier of the service to which the first data stream belongs can also be used to indicate the first data stream. That is, the identifier information of the first data stream may also include the service type identifier.

[0220] In some embodiments, the business type identifier may be, for example, AI ID#1, or AI ID#1, or perception business ID#1, etc., and this disclosure does not limit it.

[0221] In some embodiments, if the second radio bearer is only associated with the first data stream, the network device can directly determine that it has received the first data stream after receiving the second radio bearer. Therefore, in order to reduce the resource consumption of transmitting the first end-of-transmission marker packet, the terminal may not carry the identification information of the first data stream in the first end-of-transmission marker packet.

[0222] In some embodiments, to ensure that the terminal and the network device maintain a consistent understanding regarding whether the end-of-band marker needs to carry identification information of the data stream, the network device may also instruct the terminal whether the end-of-band marker packet in each radio bearer contains identification information of the mapped data stream. Accordingly, the terminal can determine whether the end-of-band marker packet in each radio bearer contains identification information of the associated data stream based on the instruction from the network device.

[0223] In some embodiments, the network device may send an indication message to the terminal individually for each radio bearer to indicate whether the identification information of the associated (corresponding) data stream is carried in the end-of-transmission packet of that radio bearer.

[0224] In some embodiments, the network device may also send a uniform indication to the terminal for all radio bearers, indicating whether to carry the identification information of the associated data stream in the end-of-charge packet of each radio bearer. Accordingly, if the uniform indication carries the identification information of the associated data stream, then the terminal needs to carry the identification information of the associated data stream in the end-of-charge packet generated for each radio bearer. Alternatively, if the uniform indication does not carry the identification information of the associated data stream, then the terminal does not need to carry the identification information of the associated data stream in the end-of-charge packet generated for each radio bearer.

[0225] In some embodiments, the terminal may carry identification information of the first data stream in the header of the first end-of-transmission packet in the second radio bearer; or, carry identification information of the first data stream in a designated field of the first end-of-transmission packet.

[0226] In some embodiments, after the network device sends the first QoS rule configuration information, if the first QoS rule configuration information includes a mapping relationship between the first data stream and the first radio bearer, then the network device can determine the second radio bearer associated with the first data stream (the second QoS rule configuration information indicates the mapping relationship between the first data stream and the second radio bearer) based on the second QoS rule configuration information that was sent before sending the first QoS rule configuration information. Then, it can determine that the terminal will send an end marker packet in the second radio bearer based on the PDCP protocol.

[0227] In some embodiments, after the network device sends the first QoS rule configuration information, if the first QoS rule configuration information includes a mapping relationship between the first data stream and the first radio bearer, and the network device did not configure the mapping relationship between the first data stream and the radio bearer before sending the first QoS rule configuration information, and the terminal is configured with a default radio bearer, then the network device can determine that the terminal will send an end marker packet in the default radio bearer based on the PDCP protocol.

[0228] In some embodiments, if the network device does not receive the first end-of-transmission packet in the second radio bearer (or the default radio bearer), it can be determined that the terminal's remapping of the first data stream has failed, or that the terminal (temporarily) does not support the data remapping function, etc. This ensures reliable data transmission between the terminal and the network device.

[0229] Step S2104: Send capability information.

[0230] The capability information is used to indicate whether PDCP-based reflection QoS is supported. Alternatively, it can indicate whether the PDCP-based reflection QoS function is available. Or, it can request to enable the PDCP-based reflection QoS function. Or, it can request to start the PDCP-based reflection QoS function, etc., and this disclosure does not limit this to any specific instance.

[0231] In some embodiments, the terminal's capability information can assist network devices in performing more accurate resource scheduling. In this embodiment, the terminal can report to the network device whether it supports PDCP-based reflection QoS. This enables the network device to accurately determine whether to use PDCP-based reflection QoS for the terminal based on this capability information.

[0232] In some embodiments, capability information may indicate that the terminal supports PDCP-based reflection QoS. Alternatively, it may indicate that the PDCP-based reflection QoS function is available. Or, it may indicate that the PDCP-based reflection QoS function has been enabled, or request activation of the PDCP-based reflection QoS function, etc.

[0233] In some embodiments, the capability information may also indicate that the terminal does not support PDCP-based reflection QoS. Alternatively, it may indicate that the PDCP-based reflection QoS function is unavailable. Or, it may indicate that the PDCP-based reflection QoS function has been disabled. Or, it may request the deactivation of the PDCP-based reflection QoS function, etc.

[0234] Step S2105: Send downlink data packets.

[0235] In some embodiments, the downlink data packet includes a reflective QoS indication.

[0236] In some embodiments, the network device may include a reflective QoS indication in the downlink data packets sent to the terminal if the terminal's capability information indicates that it supports PDCP-based reflective QoS, or indicates that PDCP-based reflective QoS is available. This avoids the problem of wasting transmission resources by including a reflective QoS indication in the downlink data packets when the terminal does not support PDCP-based reflective QoS, or when PDCP-based reflective QoS is unavailable.

[0237] In some embodiments, a network device may carry a Reflective QoS indication in the header of a downlink data packet. For example, the value of a bit in the header of the downlink data packet may indicate whether Reflective QoS is required. A value of 1 indicates that Reflective QoS is required, otherwise it is not, and so on. This disclosure does not limit the specific implementation of carrying a Reflective QoS indication in the downlink data packet.

[0238] In some embodiments, the Reflective QoS indicator is used to indicate the mapping of the uplink QoS flow to the DRB based on downlink data packets. Therefore, when the terminal receives a downlink data packet that includes the Reflective QoS indicator, it needs to determine the mapping of the corresponding uplink data packet to the DRB based on the identification information of the downlink data packets received within the DRB.

[0239] In some embodiments, the network device sends downlink data packets to the terminal.

[0240] In some embodiments, if the capability information sent by the terminal indicates that it does not support PDCP-based reflective QoS, or indicates that PDCP-based reflective QoS is unavailable, then the network device may not carry the reflective QoS indication in the downlink data packet.

[0241] Step S2106: Determine the corresponding uplink data packet based on the identification information in the downlink data packet.

[0242] In some embodiments, the terminal and network device can determine the uplink data packet containing the same identification information based on the identification information in the downlink data packet header, such as the flow identifier, QoS rule ID, or service type ID.

[0243] In some embodiments, if the terminal does not support PDCP-based reflective QoS, or if PDCP-based reflective QoS is unavailable, but the received downlink data packet includes a reflective QoS indication, then the terminal does not need to determine the corresponding uplink data packet based on the identification information in the downlink data packet.

[0244] In step S2107, the third radio bearer associated with the uplink data packet is different from the fourth radio bearer associated with the downlink data packet, so the uplink data packet is mapped to the fourth radio bearer.

[0245] In some embodiments, if an uplink data packet has been configured to be mapped to a third radio bearer, the terminal may remap the uplink data packet to the fourth radio bearer since the third radio bearer is different from the fourth radio bearer that receives the downlink data packet and the downlink data packet includes a reflective QoS indication.

[0246] Step S2108: Transmit a second end marker packet generated based on PDCP in the third radio bearer.

[0247] In some embodiments, to promptly notify the network device that the transmission of the uplink data packet mapped to the third radio bearer has ended, the terminal can send a second end-of-transmission marker packet generated based on PDCP on the third radio bearer. This ensures that the network device and the terminal maintain a consistent understanding of the radio bearer mapped to the uplink data packet, improving the reliability of uplink data transmission.

[0248] In some implementations, the terminal may carry uplink data packet identification information in the header of the second end-of-transmission packet to ensure that the network device can accurately determine which uplink data packet the second end-of-transmission packet corresponds to.

[0249] In some embodiments, if no mapping relationship between uplink data packets and radio bearers is configured, the terminal can map uplink data packets to a fourth radio bearer, wherein the fourth radio bearer corresponds to downlink data packets.

[0250] In some embodiments, if no mapping relationship between uplink data packets and radio bearers is configured and the terminal is configured with the default configuration, the terminal can send a third end marker packet generated based on PDCP in the default radio bearer after mapping the uplink data packets to the fourth radio bearer.

[0251] In some implementations, the terminal can carry uplink data packet identification information in the header of the third end-of-transmission packet to ensure that the network device can accurately determine which uplink data packet the third end-of-transmission packet corresponds to.

[0252] In some embodiments, after mapping uplink data packets to a fourth radio bearer, the terminal may store the mapping relationship between the uplink data packets and the fourth radio bearer.

[0253] In some embodiments, if the terminal does not support PDCP-based reflective QoS, or if PDCP-based reflective QoS is unavailable, but the received downlink data packet includes a reflective QoS indication, the terminal may not map the corresponding uplink data packet to the fourth radio bearer and may not send an end-of-life marker packet via the PDCP layer on the original radio bearer. Therefore, if the network device does not receive an end-of-life marker packet on the original radio bearer, it can determine that the terminal does not support reflective QoS, or that the terminal's reflective QoS is currently unavailable.

[0254] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2108. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2102+S2103 may be implemented as an independent embodiment, step S2104 may be implemented as an independent embodiment, step S2105 may be implemented as an independent embodiment, step S2105+S2106+S2107 may be implemented as an independent embodiment, step S2105+S2106+S2107+S2108 may be implemented as an independent embodiment, step S2104+S2105+S2106+S2107+S2108 may be implemented as an independent embodiment, etc., but not limited thereto.

[0255] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0256] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0257] In this embodiment of the disclosure, when the terminal determines that the radio bearer associated with the first data stream has changed, it can send an end marker packet on the original radio bearer through the PDCP layer to indicate to the network device that the remapping of the first data stream has been completed based on the PDCP layer, thereby providing conditions for improving the reliability of the data channel terminated at the terminal and access network device and expanding the service scope of the communication system application.

[0258] Figure 3A is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the communication method involved in this embodiment is executed by a terminal, and as shown in Figure 3A, the method includes:

[0259] Step S3101: Receive the first Quality of Service (QoS) rule configuration information.

[0260] The first QoS rule configuration information includes the mapping relationship between the first data stream and the first radio bearer.

[0261] Step S3102: Determine the second radio bearer associated with the first data stream.

[0262] In step S3103, the second radio bearer is different from the first radio bearer, and a first end marker packet is sent in the second radio bearer.

[0263] The first end marker packet is generated based on the Packet Data Convergence Protocol (PDCP).

[0264] In some embodiments, determining that the second radio bearer associated with the first data stream includes:

[0265] Before receiving the first QoS rule configuration information, if the mapping relationship between the first data stream and the radio bearer has not been configured and a default radio bearer has been configured, the second radio bearer associated with the first data stream is determined to be the default radio bearer.

[0266] In some embodiments, determining that the second radio bearer associated with the first data stream includes:

[0267] Based on the received second QoS rule configuration information, the second radio bearer associated with the first data stream is determined, wherein the second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

[0268] In some embodiments, the first end marker packet includes identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; service type identifier.

[0269] In some embodiments, the second radio bearer is associated only with the first data stream, and the first end-of-transmission packet does not contain identification information of the first data stream.

[0270] In some embodiments, the above method further includes:

[0271] Based on the instructions of the network device, determine whether the end-of-band packet in each radio bearer contains identification information of the associated data stream.

[0272] In some embodiments, the above method further includes:

[0273] Receive downlink data packets, which include a reflection QoS indication;

[0274] The corresponding uplink data stream is determined based on the identification information in the downlink data packet;

[0275] The uplink data packet to radio bearer mapping relationship is not configured. The uplink data packet is mapped to the fourth radio bearer, where the fourth radio bearer corresponds to the downlink data packet.

[0276] In some embodiments, the method further includes transmitting a second end-of-carry packet generated based on PDCP in a third radio bearer.

[0277] In some embodiments, the above method further includes:

[0278] Receive downlink data packets, the downlink data packets including a reflection QoS indication;

[0279] The corresponding uplink data stream is determined based on the identification information in the downlink data packet;

[0280] The uplink data packet to radio bearer mapping relationship is not configured. The uplink data packet is mapped to the fourth radio bearer, where the fourth radio bearer corresponds to the downlink data packet.

[0281] In some embodiments, the above method further includes:

[0282] It is configured with a default bearer and transmits third end-of-carrier packets based on PDCP in the default radio bearer.

[0283] In some embodiments, the method further includes storing a mapping relationship between uplink data packets and a fourth radio bearer.

[0284] In some embodiments, the above method further includes:

[0285] Send capability information, which indicates whether PDCP-based reflection QoS is supported.

[0286] In this embodiment of the disclosure, when the terminal determines that the radio bearer associated with the first data stream has changed, it can send an end marker packet on the original radio bearer through the PDCP layer to indicate to the network device that the remapping of the first data stream has been completed based on the PDCP layer. This provides conditions for improving the reliability of the data channel terminating at the terminal and access network device and for expanding the service scope of the communication system application.

[0287] Figure 3B is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the communication method involved in this embodiment is executed by a network device system, and as shown in Figure 3B, the method includes:

[0288] Step S3201: Send the first Quality of Service (QoS) rule configuration information.

[0289] The first QoS rule configuration information includes the mapping relationship between the first data stream and the first radio bearer;

[0290] Step S3202: Determine the second radio bearer associated with the first data stream.

[0291] In step S3203, the second radio bearer is different from the first radio bearer, and the first end marker packet is received in the second radio bearer.

[0292] The first end marker packet is generated based on the Packet Data Convergence Protocol (PDCP).

[0293] In some embodiments, determining that the second radio bearer associated with the first data stream includes:

[0294] Before sending the first QoS rule configuration information, the mapping relationship between the first data stream and the wireless bearer is not configured, and a default bearer is configured. The default wireless bearer is determined to be the second wireless bearer.

[0295] In some embodiments, determining that the second radio bearer associated with the first data stream includes:

[0296] Based on the sent second QoS rule configuration information, the second radio bearer associated with the first data stream is determined, wherein the second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

[0297] In some embodiments, the first end marker packet includes identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; type identifier of the service to which it belongs.

[0298] In some embodiments, the second radio bearer is associated only with the first data stream, and the first end-of-transmission packet does not contain identification information of the first data stream.

[0299] In some embodiments, the method further includes: sending indication information, which indicates whether the end-of-charge packet in each radio bearer contains identification information of the corresponding data stream.

[0300] In some embodiments, the above method further includes:

[0301] Send downlink data packets, which include a reflection QoS indication;

[0302] The corresponding uplink data packet is determined based on the identification information in the downlink data packet;

[0303] Determine the third radio bearer corresponding to the uplink data stream;

[0304] Receive end marker packets generated based on PDCP in the third radio bearer.

[0305] In some embodiments, if a mapping relationship corresponding to an uplink data packet has been configured, the radio bearer indicated in the mapping relationship can be determined as a third radio bearer.

[0306] In some embodiments, if the bearer corresponding to the uplink data packet is not configured and the terminal is configured with a default wireless bearer, then the default wireless bearer can be determined as the third wireless bearer.

[0307] In some embodiments, the above method further includes:

[0308] Receive capability information, whereby the capability information is used to indicate whether PDCP-based reflection QoS is supported.

[0309] In this embodiment of the disclosure, after the network device configures the first radio bearer associated with the first data stream for the terminal, if it determines that the radio bearer associated with the first data stream has changed, it can receive an end marker packet on the original radio bearer through the PDCP layer. This allows it to determine that the terminal has implemented the remapping of the first data stream based on the PDCP layer, providing conditions for improving the reliability of the data channel terminating at the terminal and the access network device and expanding the service scope of the communication system application.

[0310] The communication method provided in this disclosure will be further described below with reference to the following embodiments.

[0311] If the UE receives the access layer QoS rule configuration, the UE determines whether data flow remapping has occurred. If remapping has occurred, the UE's PDCP layer sends an end marker in the original radio bearer.

[0312] In some implementations, the terminal can be a regular commercial terminal, an NTN terminal, or a low-cost terminal. The above QoS rule configuration can be used in either inactive or connected states.

[0313] In some implementations, the aforementioned QoS rule includes mapping rules between access layer protocol packets and radio bearers. A data flow is a data flow determined based on the packet filtering rules in the QoS rule. A data flow may have a flow identifier, such as a QoS flow ID, a service type ID, or a QoS rule ID.

[0314] In some implementations, the aforementioned end marker is a PDCP control PDU. The end marker does not carry a serial number (SN). The end marker contains indication information to indicate whether it is a Data PDU or a Control PDU. The end marker occupies one byte.

[0315] In some implementations, the aforementioned end marker carries identification information for the data flow. This could include the data flow ID, QoS rule ID, or service type ID.

[0316] In some implementations, if only one data stream is mapped in the original radio bearer, the end marker may not carry the data stream's identification information, such as the data stream's ID or QoS rule ID.

[0317] In some implementations, network devices can be configured to allow each radio bearer's end marker to carry data stream identification information.

[0318] In some implementations, if the UE receives an access layer QoS rule configuration, which includes a mapping relationship configuration between an application protocol layer data stream and a radio bearer, and if the UE has not previously configured this mapping relationship between the data stream and the radio bearer, and the UE has a default bearer configured, then the UE's PDCP layer can send an end marker in the original default bearer.

[0319] In some implementations, if the UE receives an access layer QoS rule configuration, which includes a mapping relationship configuration between an application protocol layer data stream and a radio bearer, and if the UE previously stored such a mapping relationship between the application protocol layer data stream and the radio bearer, but the mapping relationship is different from the one received this time, then the UE's PDCP layer can send an end marker in the radio bearer to which the data stream was originally mapped.

[0320] In some implementations, if the UE's PDCP layer receives a downlink data packet with a reflective QoS indication in the packet header, the UE's PDCP layer determines the corresponding application protocol data uplink data packet based on the identification information in the packet header (such as flow identifier, QoS rule ID, or service type ID). If the radio bearer mapped to the application protocol data uplink data packet is different from that of the downlink data packet, the UE can map the uplink data packet to the radio bearer corresponding to the downlink data packet and store the mapping relationship. Then, the UE's PDCP layer sends an end marker to the original radio bearer of the uplink data packet.

[0321] In some implementations, if the identification information of downlink data packets (such as flow ID, QoS rule ID, or service type ID) is the same as that of uplink data packets, they are considered to belong to the same service flow.

[0322] In some implementations, if the UE's PDCP layer receives a downlink data packet with a reflective QoS indication in the packet header, the UE determines the corresponding application protocol data uplink data packet based on the identification information in the packet header. If the application protocol data uplink data packet is not configured to be mapped to a radio bearer, but is configured with a default bearer, the UE maps the uplink data packet to the radio bearer corresponding to the downlink data packet and stores the mapping relationship. Then, the UE's PDCP layer sends an end marker to the default bearer.

[0323] In some embodiments, the UE may report capability information to the network device, indicating whether it supports PDCP layer Reflective QoS.

[0324] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0325] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0326] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0327] Figure 4A is a schematic diagram of the structure of a terminal proposed in an embodiment of this disclosure. As shown in Figure 4A, the terminal 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc.

[0328] In some embodiments, the transceiver module is configured to receive first Quality of Service (QoS) rule configuration information, wherein the first QoS rule configuration information includes a mapping relationship between a first data stream and a first radio bearer.

[0329] The aforementioned processing module is used to determine the second wireless bearer associated with the first data stream.

[0330] Unlike the first wireless bearer, the transceiver module described above is also used to send a first end-of-carrier packet in the second wireless bearer, wherein the first end-of-carrier packet is generated based on the Packet Data Convergence Protocol (PDCP).

[0331] In some embodiments, the above-described processing module is further configured to:

[0332] Before receiving the first QoS rule configuration information, if the mapping relationship between the first data stream and the radio bearer has not been configured and a default radio bearer has been configured, the second radio bearer associated with the first data stream is determined to be the default radio bearer.

[0333] In some embodiments, the above-described processing module is further configured to:

[0334] Based on the received second QoS rule configuration information, the second radio bearer associated with the first data stream is determined, wherein the second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

[0335] In some embodiments, the first end marker packet includes identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; service type identifier.

[0336] In some embodiments, the second radio bearer is associated only with the first data stream, and the first end-of-transmission packet does not contain identification information of the first data stream.

[0337] In some embodiments, the above-described processing module is further configured to:

[0338] Based on the instructions of the network device, determine whether the end-of-band packet in each radio bearer contains identification information of the associated data stream.

[0339] In some embodiments, the transceiver module described above is further configured to receive downlink data packets, the downlink data packets including a reflection QoS indication;

[0340] The aforementioned processing module is also used to determine the corresponding uplink data stream based on the identification information in the downlink data packet;

[0341] Since the mapping relationship between uplink data packets and radio bearers is not configured, the above processing module is also used to map uplink data packets to a fourth radio bearer, wherein the fourth radio bearer corresponds to downlink data packets.

[0342] In some embodiments, the transceiver module described above is further configured to transmit a second end-of-carry packet generated based on PDCP in a third radio bearer.

[0343] In some embodiments, the transceiver module described above is further configured to receive downlink data packets, the downlink data packets including a reflection QoS indication;

[0344] The aforementioned processing module is also used to determine the corresponding uplink data stream based on the identification information in the downlink data packet;

[0345] Since the mapping relationship between uplink data packets and radio bearers is not configured, the above processing module is also used to map uplink data packets to a fourth radio bearer, wherein the fourth radio bearer corresponds to downlink data packets.

[0346] In some embodiments, a default bearer is configured, and the aforementioned processing module is further configured to send a third end-of-carrier packet generated based on PDCP in the default radio bearer.

[0347] In some embodiments, the above-described processing module is further configured to store the mapping relationship between uplink data packets and the fourth radio bearer.

[0348] In some embodiments, the transceiver module described above is further configured to send capability information, wherein the capability information is used to indicate whether PDCP-based reflection QoS is supported.

[0349] Optionally, the transceiver module described above is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, which will not be elaborated here.

[0350] Optionally, the above processing module is used to perform at least one of the other steps executed by the terminal in any of the above methods, which will not be elaborated here.

[0351] Figure 4B is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. As shown in Figure 4B, the network device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc.

[0352] In some embodiments, the transceiver module is configured to send first Quality of Service (QoS) rule configuration information, wherein the first QoS rule configuration information includes a mapping relationship between a first data stream and a first radio bearer;

[0353] The aforementioned processing module is used to determine the second wireless bearer associated with the first data stream.

[0354] The second radio bearer differs from the first radio bearer in that the transceiver module is also used to receive a first end-of-carrier packet in the second radio bearer, wherein the first end-of-carrier packet is generated based on the Packet Data Convergence Protocol (PDCP).

[0355] In some embodiments, before sending the first QoS rule configuration information, if the mapping relationship between the first data stream and the radio bearer is not configured and a default bearer is configured, the above processing module is further configured to determine that the default radio bearer is the second radio bearer.

[0356] In some embodiments, the processing module is further configured to determine the second radio bearer associated with the first data stream based on the sent second QoS rule configuration information, wherein the second QoS rule configuration information includes a mapping relationship between the first data stream and the second radio bearer.

[0357] In some embodiments, the first end marker packet includes identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; type identifier of the service to which it belongs.

[0358] In some embodiments, the second radio bearer is associated only with the first data stream, and the first end-of-transmission packet does not contain identification information of the first data stream.

[0359] In some embodiments, the transceiver module is further configured to send indication information, which indicates whether the end-of-transmitter packet in each radio bearer contains identification information of the corresponding data stream.

[0360] In some embodiments, the transceiver module described above is further configured to send downlink data packets, the downlink data packets including a reflection QoS indication;

[0361] The aforementioned processing module is also used to determine the corresponding uplink data packet based on the identification information in the downlink data packet;

[0362] The aforementioned processing module is also used to determine the third radio bearer corresponding to the uplink data stream;

[0363] The aforementioned transceiver module is also used to receive end marker packets generated based on PDCP in the third radio bearer.

[0364] In some embodiments, the transceiver module described above is further configured to receive capability information, wherein the capability information is used to indicate whether PDCP-based reflection QoS is supported.

[0365] Optionally, the transceiver module described above is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device in any of the above methods, which will not be elaborated here.

[0366] Optionally, the above processing module is used to perform at least one of the other steps performed by the network device in any of the above methods, which will not be elaborated here.

[0367] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 can be a network device (e.g., an access network device), a terminal (e.g., a user equipment), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0368] As shown in Figure 5A, the communication device 5100 includes one or more processors 5101. The processor 5101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The communication device 5100 is used to execute any of the above methods.

[0369] In some embodiments, the communication device 5100 further includes one or more memories 5102 for storing instructions. Optionally, all or part of the memories 5102 may also be located outside the communication device 5100.

[0370] In some embodiments, the communication device 5100 further includes one or more transceivers 5103. When the communication device 5100 includes one or more transceivers 5103, the transceivers 5103 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., at least one of steps S2101, S2102, S2103, S2104, S2105, etc.), and the processor 5101 performs other steps (e.g., at least one of S2106, S217, etc.).

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

[0372] In some embodiments, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102, and the interface circuit 5104 can be used to receive signals from the memory 5102 or other devices, and can be used to send signals to the memory 5102 or other devices. For example, the interface circuit 5104 can read instructions stored in the memory 5102 and send the instructions to the processor 5101.

[0373] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components 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, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0374] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of chip 5200 shown in Figure 5B, but it is not limited thereto.

[0375] Chip 5200 includes one or more processors 5201, which are used to perform any of the above methods.

[0376] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, the interface circuit 5202 is connected to memory 5203, and the interface circuit 5202 can be used to receive signals from memory 5203 or other devices, and the interface circuit 5202 can be used to send signals to memory 5203 or other devices. For example, the interface circuit 5202 can read instructions stored in memory 5203 and send the instructions to processor 5201.

[0377] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 5201 performs at least one of the other steps.

[0378] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0379] In some embodiments, chip 5200 further includes one or more memories 5203 for storing instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200.

[0380] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 5100, cause the communication device 5100 to perform 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0381] This disclosure also provides a program product that, when executed by the communication device 5100, causes the communication device 5100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0382] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0383] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

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

[0385] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0386] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Receive first Quality of Service (QoS) rule configuration information, wherein the first QoS rule configuration information includes the mapping relationship between the first data stream and the first radio bearer; It is determined that the first data stream is associated with a second radio bearer; The second radio bearer differs from the first radio bearer in that it transmits a first end-of-life marker packet, wherein the first end-of-life marker packet is generated based on the Packet Data Convergence Protocol (PDCP).

2. The method as described in claim 1, characterized in that, The step of determining that the first data stream is associated with a second wireless bearer includes: Before receiving the first QoS rule configuration information, if the mapping relationship between the first data stream and the radio bearer has not been configured and a default radio bearer has been configured, the default radio bearer is determined to be the second radio bearer.

3. The method as described in claim 1, characterized in that, The step of determining that the first data stream is associated with a second wireless bearer includes: Based on the received second QoS rule configuration information, the second radio bearer associated with the first data stream is determined, wherein the second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

4. The method according to any one of claims 1-3, characterized in that, The first end marker packet contains identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; service type identifier.

5. The method as described in claim 4, characterized in that, The second radio bearer is associated only with the first data stream, and the first end marker packet does not contain the identification information of the first data stream.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Based on the instructions of the network device, determine whether the end-of-band packet in each radio bearer contains the identification information of the corresponding data stream.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Receive downlink data packets, the downlink data packets including a reflection QoS indication; The corresponding uplink data packet is determined based on the identification information in the downlink data packet; The third radio bearer associated with the uplink data packet is different from the fourth radio bearer associated with the downlink data packet, and the uplink data packet is mapped to the fourth radio bearer.

8. The method as described in claim 7, characterized in that, The method further includes: A second end-of-carry packet based on PDCP is transmitted in the third radio bearer.

9. The method according to any one of claims 1-6, characterized in that, The method further includes: Receive downlink data packets, the downlink data packets including a reflection QoS indication; The corresponding uplink data stream is determined based on the identification information in the downlink data packet; If the mapping relationship between the uplink data packet and the radio bearer is not configured, the uplink data packet will be mapped to a fourth radio bearer, wherein the fourth radio bearer corresponds to the downlink data packet.

10. The method as described in claim 9, characterized in that, The method further includes: It is configured with a default bearer, in which a third end-of-transmission packet based on PDCP is transmitted.

11. The method according to any one of claims 7-10, characterized in that, The method further includes: Store the mapping relationship between the uplink data packets and the fourth radio bearer.

12. The method according to any one of claims 7-11, characterized in that, The method further includes: Send capability information, wherein the capability information is used to indicate whether PDCP-based reflection QoS is supported.

13. A communication method, characterized in that, include: Send first Quality of Service (QoS) rule configuration information, the first QoS rule configuration information including the mapping relationship between the first data stream and the first radio bearer; It is determined that the first data stream is associated with a second radio bearer; The second radio bearer differs from the first radio bearer in that it receives a first end-of-life marker packet, wherein the first end-of-life marker packet is generated based on the Packet Data Convergence Protocol (PDCP).

14. The method as described in claim 13, characterized in that, The step of determining that the first data stream is associated with a second wireless bearer includes: Before sending the first QoS rule configuration information, the mapping relationship between the first data stream and the wireless bearer is not configured, and a default bearer is configured. The default wireless bearer is determined to be the second wireless bearer.

15. The method as described in claim 13, characterized in that, The step of determining that the first data stream is associated with a second wireless bearer includes: Based on the sent second QoS rule configuration information, the second radio bearer associated with the first data stream is determined, wherein the second QoS rule configuration information includes the mapping relationship between the first data stream and the second radio bearer.

16. The method as described in any one of claims 13-14, characterized in that, The first end marker packet contains the identification information of the first data stream, and the identification information is at least one of the following: QoS stream identifier; QoS rule identifier; type identifier of the service to which it belongs.

17. The method as described in claim 16, characterized in that, The second radio bearer is associated only with the first data stream, and the first end marker packet does not contain the identification information of the first data stream.

18. The method according to any one of claims 13-17, characterized in that, The method further includes: Send indication information, which is used to indicate whether the end marker packet in each radio bearer contains the identification information of the corresponding data stream.

19. The method according to any one of claims 13-18, characterized in that, The method further includes: Send downlink data packets, the downlink data packets including a reflection QoS indication; The corresponding uplink data packet is determined based on the identification information in the downlink data packet; Determine the third radio bearer corresponding to the uplink data stream; The third radio bearer receives an end marker packet generated based on PDCP.

20. The method as described in claim 19, characterized in that, The method further includes: Receive capability information, wherein the capability information is used to indicate whether PDCP-based reflection QoS is supported.

21. A terminal, characterized in that, The terminal includes: The transceiver module is used to receive first QoS rule configuration information, wherein the first QoS rule configuration information includes the mapping relationship between the first data stream and the first radio bearer; The processing module is used to determine the second radio bearer associated with the first data stream; The second radio bearer is different from the first radio bearer. The transceiver module is further configured to send a first end marker packet in the second radio bearer, wherein the first end marker packet is generated based on the Packet Data Convergence Protocol (PDCP).

22. A network device, characterized in that, The network device includes: The transceiver module is used to send first QoS rule configuration information, which includes a mapping relationship between a first data stream and a first radio bearer. The processing module is used to determine the second radio bearer associated with the first data stream; The second radio bearer is different from the first radio bearer. The transceiver module is further configured to receive a first end-of-carrier packet in the second radio bearer, wherein the first end-of-carrier packet is generated based on the Packet Data Convergence Protocol (PDCP).

23. A communication device, characterized in that, The communication device includes: One or more processors; The processor is used to execute the communication method according to any one of claims 1-12 and 13-20.

24. A communication system, characterized in that, The device includes a terminal and a network device, wherein the terminal is configured to implement the communication method according to any one of claims 1-12, and the network device is configured to implement the communication method according to any one of claims 13-20.

25. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-12, 13-20.

26. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the communication method according to any one of claims 1-12 and 13-20.

Images