Communication method, communication device, communication system and storage medium

Abstract

Disclosed in the embodiments of the present disclosure are a communication method, a communication device, a communication system and a storage medium. The method, which is executed by a terminal, comprises: receiving configuration information, wherein the configuration information is configured to configure a list of quality of service (QoS) rules for an access stratum, and the QoS rules are configured to indicate a mapping relationship between access stratum protocol data packets and radio bearers. Thus, conditions are provided for establishing a data channel that terminates between an access network device and the terminal.

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, there may be a need to terminate the data channel between the terminal and the access network equipment. How to perform Quality of Service (QoS) mapping on this data transmission 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 configuration information, wherein the configuration information is used to configure the access layer quality of service (QoS) rule list, wherein the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

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

[0008] Send configuration information, wherein the configuration information is used to configure the access layer quality of service (QoS) rule list, wherein the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

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

[0010] The transceiver module is used to receive configuration information, wherein the configuration information is used to configure the access layer quality of service (QoS) rule list, and the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

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

[0012] The transceiver module is used to send configuration information, wherein the configuration information is used to configure the access layer quality of service (QoS) rule list, and the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

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

[0014] 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.

[0015] 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.

[0016] 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.

[0017] 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.

[0018] The solution proposed in this disclosure allows network devices to configure access layer QoS rule lists for terminals, which are used to map data in the RAN to radio bearers, providing conditions for establishing a radio-only bearer between the terminal and the access network device and improving the range of services supported by the communication system. Attached Figure Description

[0019] 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.

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

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

[0022] Figures 2B-2E are schematic diagrams of the Radio only bearer protocol architecture provided in the embodiments of this disclosure;

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

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

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

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

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

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

[0029] In a first aspect, embodiments of this disclosure propose a communication method executed by a terminal, the method comprising: receiving configuration information, wherein the configuration information is used to configure an access layer quality of service (QoS) rule list, wherein the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

[0030] In the above embodiments, the network device can configure an access layer QoS rule list for the terminal to map data in the RAN to the radio bearer, thereby providing conditions for establishing a radio-only bearer between the terminal and the access network device and improving the scope of services supported by the communication system.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, the above-mentioned QoS rules include one or more of the following:

[0032] QoS rule identifier; QoS flow identifier; radio bearer identifier; packet filter set; priority.

[0033] In conjunction with some embodiments of the first aspect, in some embodiments, the number of QoS rules conforming to the first data packet is greater than the number of QoS rules conforming to the second data packet, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

[0034] In the above embodiments, data packets can be processed using QoS rules of different priorities based on the number of QoS rules that meet the requirements, thereby improving the accuracy and reliability of data processing and enhancing the performance of the communication system.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the above-mentioned QoS rule list or the QoS rules correspond to any of the following: a terminal; a radio bearer; a protocol.

[0036] In the above embodiments, the QoS rule list or the QoS rules can be configured based on multiple granularities, which improves the flexibility of the QoS rule list or the QoS rules configuration and provides conditions for improving the reliability of data processing and the flexibility of resource management.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the first QoS rule corresponds to the first radio bearer, and the first QoS rule is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

[0038] In the above embodiments, for QoS rules configured at the radio bearer level, the configuration information of the corresponding QoS rule list can be carried using the SDAP configuration or PDCP configuration corresponding to the radio bearer, thus saving the signaling overhead of QoS rule list configuration.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the identification information of the first QoS rule corresponding to different terminals is different, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

[0040] In the above embodiments, for QoS rules configured at the granularity of wireless bearers, different identification information is configured for different terminals, thereby avoiding data processing anomalies and improving the reliability of the system.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the packet filter described above includes one or more of the following: protocol type; data type; service type; QoS requirements.

[0042] In the above embodiments, multiple factors can be configured for the packet filter, thereby improving the accuracy and reliability of determining the data corresponding to the packet processor.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the above-mentioned QoS rule list includes a second QoS rule, which does not contain a packet filter or contains a general packet filter.

[0044] In the above embodiments, the network device can also configure a default rule for the terminal, ensuring that all data can be reliably processed and improving the performance of the communication system.

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

[0046] Based on the order of each QoS rule in the QoS rule list, determine the QoS flow identifier and / or QoS rule identifier corresponding to each QoS rule.

[0047] In the above embodiments, the terminal can determine the corresponding identification information of a QoS rule according to its order in the QoS rule list, which provides a condition for reducing the amount of information configured in the QoS rule list.

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

[0049] Add the identification information corresponding to the uplink QoS flow to the SDAP or PDCP data packet corresponding to the uplink QoS flow. The identification information includes one or more of the following: QoS flow identifier and QoS rule identifier.

[0050] In the above embodiments, the terminal can add the identification information corresponding to the uplink QoS flow to the corresponding SDAP data packet or PDCP data packet, thereby ensuring that the network device can accurately determine which terminal the received QoS flow comes from, providing a basis for the network device to perform resource scheduling and data processing accurately.

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

[0052] Send configuration information, which is used to configure the access layer quality of service (QoS) rule list, where the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the QoS rules described above include one or more of the following: QoS rule identifier; QoS flow identifier; radio bearer identifier; packet filter set; priority.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the number of QoS rules conforming to the first data packet is greater than the number of QoS rules conforming to the second data packet, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the above-described QoS rule list or QoS rule corresponds to any of the following: terminal; radio bearer; protocol.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the first QoS rule corresponds to the radio bearer, and the first QoS rule is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the identification information of the first QoS rule corresponding to different terminals is different, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the packet filter described above includes one or more of the following: protocol type; data type; service type; QoS requirements.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the above-mentioned QoS rule list includes a second QoS rule, which does not contain a packet filter or contains a general packet filter.

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

[0061] Add the identification information corresponding to the downlink QoS flow to the SDAP or PDCP data packet corresponding to the downlink QoS flow. The identification information includes one or more of the following: QoS flow identifier and QoS rule identifier.

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

[0063] The transceiver module is used to receive configuration information, which is used to configure the access layer quality of service (QoS) rule list. The QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

[0064] In conjunction with some embodiments of the third aspect, in some embodiments, the above-mentioned QoS rules include one or more of the following: QoS rule identifier; QoS flow identifier; radio bearer identifier; packet filter set; priority.

[0065] In conjunction with some embodiments of the third aspect, in some embodiments, the number of QoS rules conforming to the first data packet is greater than the number of QoS rules conforming to the second data packet, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

[0066] In conjunction with some embodiments of the third aspect, in some embodiments, the above-described QoS rule list or the QoS rules correspond to any of the following: a terminal; a radio bearer; a protocol.

[0067] In conjunction with some embodiments of the third aspect, in some embodiments, the first QoS rule corresponds to the first radio bearer, and the first QoS rule is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

[0068] In conjunction with some embodiments of the third aspect, in some embodiments, the identification information of the first QoS rule corresponding to the different terminals is different, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

[0069] In conjunction with some embodiments of the third aspect, in some embodiments, the packet filter described above includes one or more of the following: protocol type; data type; service type; QoS requirements.

[0070] In conjunction with some embodiments of the third aspect, in some embodiments, the above-mentioned QoS rule list includes a second QoS rule, which does not contain a packet filter or contains a general packet filter.

[0071] In conjunction with some embodiments of the third aspect, in some embodiments, the above-described processing module is used to determine the QoS flow identifier and / or QoS rule identifier corresponding to each QoS rule according to the order of each QoS rule in the QoS rule list.

[0072] In conjunction with some embodiments of the third aspect, in some embodiments, the above-mentioned processing module is further configured to add the identification information corresponding to the uplink QoS flow to the SDAP data packet or PDCP data packet corresponding to the uplink QoS flow, wherein the identification information includes one or more of the following: QoS flow identifier, QoS rule identifier.

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

[0074] The transceiver module is used to send configuration information, which is used to configure the access layer quality of service (QoS) rule list. The QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

[0075] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-mentioned QoS rules include one or more of the following: QoS rule identifier; QoS flow identifier; radio bearer identifier; packet filter set; priority.

[0076] In conjunction with some embodiments of the fourth aspect, in some embodiments, the number of QoS rules conforming to the first data packet is greater than the number of QoS rules conforming to the second data packet, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

[0077] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described list of QoS rules or QoS rules correspond to any of the following: a terminal; a radio bearer; a protocol.

[0078] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first QoS rule corresponds to the radio bearer, and the first QoS rule is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

[0079] In conjunction with some embodiments of the fourth aspect, in some embodiments, the identification information of the first QoS rule corresponding to different terminals is different, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

[0080] In conjunction with some embodiments of the fourth aspect, in some embodiments, the packet filter described above includes one or more of the following: protocol type; data type; service type; QoS requirements.

[0081] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-mentioned QoS rule list includes a second QoS rule, which does not contain a packet filter or contains a general packet filter.

[0082] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-mentioned processing module is used to add the identification information corresponding to the downlink QoS flow to the SDAP data packet or PDCP data packet corresponding to the downlink QoS flow, wherein the identification information includes one or more of the following: QoS flow identifier, QoS rule identifier.

[0083] 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.

[0084] 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.

[0085] 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.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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.

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

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

[0097] 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.

[0098] 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.

[0099] 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.

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

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

[0102] 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”.

[0103] 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.

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

[0105] 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)."

[0106] 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.

[0107] 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.

[0108] 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.

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

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

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

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

[0113] 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.

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

[0115] 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.

[0116] 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.

[0117] 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.

[0118] 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).

[0119] 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.

[0120] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​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.

[0121] 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).

[0122] 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.

[0123] 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).

[0124] 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.

[0125] 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.

[0126] 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.

[0127] 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.

[0128] 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.

[0129] 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).

[0130] 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.

[0131] 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.

[0132] The communication method proposed in this disclosure provides a Quality of Service (QoS) mapping method for Radio-only bearers, which maps data generated in the Radio Access Network (RAN) to the corresponding Radio Bearer (RB), providing conditions for establishing Radio-only bearers and improving the service range supported by the communication system.

[0133] 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.

[0134] 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:

[0135] Step S2101: Send configuration information.

[0136] The configuration information is used to configure the access layer Quality of Service (QoS) rule list, where QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers (RBs).

[0137] 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.

[0138] In some embodiments, QoS rules can be used to indicate the mapping relationship between access layer protocol packets and data radio bearers (DRBs).

[0139] 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.

[0140] In some embodiments, the QoS rule list includes at least one QoS rule.

[0141] In some embodiments, the network device may send configuration information to the terminal when the terminal accesses the network. Alternatively, it may send configuration information to the terminal when a data channel needs to be established, such as when establishing a radio-only bearer with the terminal. Or, it may send configuration information to the terminal when updating the QoS rule list (such as deleting, adding, or modifying rules), etc. This disclosure does not limit the scope of the invention.

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

[0143] 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.

[0144] In some embodiments, a QoS rule may include a QoS rule identifier (ID) to uniquely identify a QoS rule.

[0145] In some embodiments, QoS rules may also include QoS flow identifiers. These identifiers can be used to identify and differentiate different data flows in the network. A QoS flow may include one or more packets. QoS flows represent the finest QoS differentiation granularity within a Protocol Data Unit (PDU) session. By assigning different QoS flow IDs to different data flows, fine-grained management and control can be achieved, ensuring that they meet specific quality of service requirements.

[0146] In some embodiments, the QoS rule may also include a radio bearer identifier. This identifier can be used to identify and differentiate different radio bearers. Associated with the QoS rule, it ensures that a specific radio bearer receives the required quality of service guarantees.

[0147] In some embodiments, QoS rules may also 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.

[0148] In some embodiments, QoS rules may also include a precedence. A precedence indicates the priority of a QoS rule, and rules with higher precedence can be applied first when processing network traffic.

[0149] In some embodiments, if the number of QoS rules that the first data packet conforms to is greater than the number of QoS rules that the second data packet conforms to, then the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

[0150] For example, if Packet #1 conforms to multiple QoS rules, while Packet #2 conforms to only one QoS rule (or does not conform to any QoS rule), then the priority of processing Packet #1 using QoS rule #1 is higher than the priority of processing Packet #2 using QoS rule #2.

[0151] In some embodiments, if different data packets belonging to the same data stream conform to different numbers of QoS rules, and the QoS rule stipulates that all data packets in the data stream are processed using the same QoS rule, then the two data packets can be processed using the same QoS rule.

[0152] In some embodiments, the QoS rule list or QoS rule corresponds to any of the following: terminal; radio bearer; protocol.

[0153] In some embodiments, terms such as "QoS rules (list) correspond to terminals", "each terminal is configured with corresponding QoS rules (list)", and "QoS rules (list) are configured on a terminal-by-terminal basis" can all be used to indicate that each terminal can be configured with its own corresponding QoS rules (list). In some scenarios, the above terms can be used interchangeably.

[0154] In some embodiments, if a separate QoS rule (list) is configured for each terminal, the QoS rules (list) for different terminals may be the same or different.

[0155] In some embodiments, the architecture of the Radio Only Bearer protocol is as shown in Figures 2B and 2C. That is, the Radio Only Bearer protocol architecture may have a Service Data Adaptation Protocol (SDAP) layer as shown in Figure 2B, or it may not have an SDAP layer as shown in Figure 2C.

[0156] In the architecture of the Radio-only bearer protocol shown in Figures 2B and 2C, 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.

[0157] As shown in Figure 2B, if the Radio Only Bearer protocol architecture includes an SDAP layer and the QoS rules (list) are configured at the terminal level, then the terminal can directly map uplink (UL) packets to the Access (AS) layer QoS flow and apply QoS flow marking based on the QoS rules without going through any protocol layer. The marked QoS flow is then submitted to the SDAP layer for processing, such as mapping the QoS flow to the Data Bearer (DRB). However, as shown in Figure 2C, if the Radio Only Bearer protocol architecture does not have an SDAP layer, then after mapping UL packets to the AS layer QoS flow and applying QoS flow marking, the terminal can submit the QoS flow to the Packet Data Convergence Protocol (PDCP) layer for processing.

[0158] In the above embodiments, by mapping uplink data packets to the corresponding access layer QoS streams, it can be ensured that data can be transmitted according to predetermined QoS requirements. Furthermore, after mapping the uplink data packets to QoS streams, the data packets are also QoS stream-marked, enabling the network system to identify and process these data packets according to predetermined QoS requirements.

[0159] It should be noted that the QoS rules in Figures 2B and 2C do not represent an independent protocol layer, but only indicate the execution of a packet processing operation.

[0160] In some embodiments, terms such as "QoS rules (list) correspond to radio bearers", "each radio bearer is configured with corresponding QoS rules (list)", and "QoS rules (list) are configured on a per radio bearer basis" can all be used to indicate that a corresponding QoS rule (list) can be configured for each radio bearer. In some scenarios, the above terms can be used interchangeably.

[0161] In some embodiments, if a separate QoS rule (list) is configured for each radio bearer, the QoS rules (list) for different radio bearers may be the same or different.

[0162] In some embodiments, as shown in Figure 2D, if the Radio Only Bearer protocol architecture includes an SDAP layer and the QoS rules (list) are configured at the radio bearer granularity, then the SDAP layer can directly map uplink packets to the data radio bearer based on the QoS rules (list) without applying flow marking. Conversely, as shown in Figure 2E, if the Radio Only Bearer protocol architecture does not have an SDAP layer and the QoS rules (list) are configured at the radio bearer granularity, then the terminal's PDCP layer can directly map uplink packets to the data radio bearer based on the QoS rules (list) without applying flow marking.

[0163] In some embodiments, since QoS rules are configured at the radio bearer level, meaning different radio bearers correspond to different QoS rules, the terminal and network device can directly determine the corresponding data packet processing rules from the radio bearer, and the radio determines the QoS rules based on flow tags. Therefore, flow tags can be used to distinguish different QoS flows, and the terminal can avoid directly mapping uplink data packets to the DRB without applying flow tags. In other words, uplink data packets can be transmitted without distinguishing between different QoS flows.

[0164] In some embodiments, terms such as "QoS rules (list) correspond to protocols", "each protocol is configured with corresponding QoS rules (list)", and "QoS rules (list) are configured on a protocol-by-protocol basis" can all be used to indicate that a corresponding QoS rule (list) can be configured for each protocol. In some scenarios, the above terms can be used interchangeably.

[0165] In some embodiments, if a separate QoS rule (list) is configured for each protocol, the QoS rules (list) for different protocols may be the same or different.

[0166] In other words, network devices can configure different QoS rule lists or different QoS rules for different terminals. Alternatively, network devices can configure different QoS rule lists or different QoS rules for different radio bearers. Or, network devices can configure different QoS rule lists or different QoS rules for different protocols (such as AI protocols, sensing protocols, or Integrated Sensing and Communication I (ISAC) protocols), and so on. In this case, the way the terminal processes the QoS flow based on the QoS rule list can be referred to the relevant descriptions in Figures 2B and 2C above.

[0167] In some embodiments, if a network device configures different QoS rule lists or different QoS rules for different terminals, then the network device can configure a unified QoS rule list for the terminals through Radio Resource Control (RRC) layer messages.

[0168] In some embodiments, if one or more QoS rules are configured separately for each radio bearer, then network devices and terminals can map data packets that satisfy at least one QoS rule corresponding to a radio bearer to that radio bearer.

[0169] In some embodiments, if a QoS rule is configured separately for each protocol, such as the AI ​​protocol, ISAC, and the perception protocol, then the terminal and network device can process the data packets corresponding to a certain protocol using the QoS rule corresponding to that protocol.

[0170] In some embodiments, if the first QoS rule corresponds to the first radio bearer (that is, the first QoS rule is configured for the first radio bearer), the first QoS rule may be included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule may be included in the Packet Data Convergence Protocol (PDCP) configuration.

[0171] In other words, if QoS rules are configured for radio bearers, the corresponding QoS rules can be carried in the SDAP or PDCP configuration of the radio bearer, thereby reducing configuration signaling overhead and saving communication resources.

[0172] In some embodiments, if QoS rules are configured for radio bearers, in order to avoid confusion and conflict, it is necessary to ensure that the identification information of the first QoS rule corresponding to different terminals is different. The identification information includes one or more of the following: QoS rule identifier and QoS flow identifier.

[0173] For example, if the QoS rule identifier (or QoS flow identifier) ​​configured for UE1 and UE2 is the same for a certain radio bearer, then when UE1 and UE2 simultaneously request to use the radio bearer for data transmission, the network device may confuse different QoS rules or QoS flows when processing data packets, causing the data packets to be forwarded or processed incorrectly.

[0174] In the above embodiments, the QoS rules configured for wireless bearers avoid data confusion and conflict by ensuring that different terminals correspond to different QoS rule identifiers and / or different QoS flow identifiers, thus providing conditions for accurate management of network resources and improving the stability of the communication system.

[0175] In some embodiments, the packet filter described above may include one or more of the following: protocol type; data type; service type; QoS requirements.

[0176] In some embodiments, the protocol type included in the packet filter can be used to indicate the protocol type of the data that the packet filter processes. The protocol type can be, for example, an AI protocol, a perception protocol, an ISAC protocol, etc., and this disclosure does not limit this.

[0177] In some embodiments, the data type and / or service type included in the packet filter can be used to indicate the type of data that the packet filter processes, or the type of service to which the data processed by the packet filter belongs. For example, it can be used to indicate that the packet filter is used to process AI models; or to process online AI training data; or to process offline AI training data; or to process AI inference input data; or to process sensing measurement results; or to process sensing channel measurement results; or to process sensing time / / or angle measurement results; or to process sensing position measurement results; or to process sensing auxiliary information; or to process AI signaling; or to process ISAC signaling, etc., which are not limited in this disclosure.

[0178] In some embodiments, the service type corresponding to the data can be defined by a protocol; or it can be configured by network equipment (such as core network equipment) and then sent to the terminal. Alternatively, it can be configured through Operations, Administration, and Maintenance (OAM); or the core network (CN) elements, such as Policy Control and Charging Function (PCRF) elements and Access and Mobility Management Function (AMF) elements, can issue QoS rules based on the defined service type and / or service type to the base station, which then sends them to the terminal, etc. This disclosure does not limit this.

[0179] In some embodiments, the QoS requirements included in the packet filter are used to indicate the QoS requirements of the data to which the packet filter applies. For example, the data to which the packet filter applies may have low latency requirements; or maximum throughput requirements; or highest reliability requirements; or need to meet general service requirements, etc.

[0180] In some embodiments, the QoS rule list above may include a second QoS rule, which may not contain a packet filter or may contain a general packet filter.

[0181] In other words, the QoS rule list configured in a network device can contain a default (or general) QoS rule (such as the second QoS rule). When no other QoS rule is configured on the terminal, all data packets can be processed using this default QoS rule.

[0182] Step S2102: Determine the QoS flow identifier and / or QoS rule identifier corresponding to each QoS rule according to the order of each QoS rule in the QoS rule list.

[0183] In some embodiments, when a QoS rule does not contain a QoS flow identifier and / or a QoS rule identifier, the terminal can determine the corresponding QoS flow identifier and / or QoS rule identifier based on the order of the QoS rule in the QoS rule list. Therefore, network devices do not need to configure the identifier information (QoS flow identifier and / or QoS rule identifier) ​​corresponding to the QoS rule when configuring the QoS rule list, thereby saving the transmission resources occupied by QoS rule configuration.

[0184] In some embodiments, if the QoS rule list is determined and configured by the core network device for the access network device, the access network device may also determine the QoS flow identifier and / or QoS rule identifier corresponding to each QoS rule based on the order of each QoS rule in the QoS rule list.

[0185] Step S2103: Add the identification information corresponding to the uplink QoS flow to the SDAP data packet or PDCP data packet corresponding to the uplink QoS flow.

[0186] The identification information includes one or more of the following: QoS flow identifier and QoS rule identifier.

[0187] In some embodiments, if the QoS rule is configured per UE, since the identification information (QoS flow identifier and / or QoS rule identifier) ​​corresponding to the QoS rule can uniquely identify a terminal, the terminal can provide the identification information corresponding to the QoS rule to the SDAP layer or PDCP layer. That is, the identification information is added to the SDAP data packet or PDCP data packet corresponding to the uplink QoS flow. After receiving the uplink QoS flow, the network device can determine which terminal the QoS flow comes from based on the identification information in the SDAP data packet or PDCP data packet.

[0188] In some embodiments, the terminal adds the identification information corresponding to the uplink QoS flow to which data packet, depending on whether there is an SDAP layer in the protocol architecture. If there is, it adds it to the SDAP data packet; otherwise, it adds it to the PDCP data packet.

[0189] In some embodiments, the terminal may add the identification information corresponding to the uplink QoS flow to the header of the SDAP data packet corresponding to the uplink QoS flow, or to the header of the PDCP data packet.

[0190] In some embodiments, the identification information corresponding to the uplink QoS flow can be added to the beginning position of the corresponding uplink SDAP packet header; or to the beginning position of the corresponding uplink PDCP packet header; or to the end position of the corresponding uplink SDAP packet header; or to the end position of the corresponding uplink PDCP packet header; or to a specified position of the corresponding uplink SDAP packet header; or to a specified position of the corresponding uplink PDCP packet header, etc., and this disclosure does not limit this.

[0191] Step S2104: Add the identification information corresponding to the downlink QoS flow to the SDAP data packet or PDCP data packet corresponding to the downlink QoS flow.

[0192] The identification information includes one or more of the following: QoS flow identifier and QoS rule identifier.

[0193] In some embodiments, if the QoS rule is configured per UE, since the identification information (QoS flow identifier and / or QoS rule identifier) ​​corresponding to the QoS rule can uniquely identify a terminal, the network device can provide the identification information corresponding to the QoS rule to the SDAP layer or PDCP layer. That is, it adds the identification information to the SDAP or PDCP data packet corresponding to the downlink QoS flow, thereby assisting the network device in determining which terminal the QoS flow needs to be sent to based on the identification information in the SDAP or PDCP data packet corresponding to the QoS flow. Correspondingly, the terminal can determine whether the QoS flow is what it needs based on the identification information in the received downlink SDAP or PDCP data packet.

[0194] In some embodiments, the network device adds the identification information corresponding to the downlink QoS flow to which data packet, depending on whether there is an SDAP layer in the protocol architecture. If there is, it adds it to the SDAP data packet; otherwise, it adds it to the PDCP data packet.

[0195] In some embodiments, the identification information corresponding to the downlink QoS flow can be added to the beginning position of the corresponding downlink SDAP packet header; or to the beginning position of the corresponding downlink PDCP packet header; or to the end position of the corresponding downlink SDAP packet header; or to the end position of the corresponding downlink PDCP packet header; or to a specified position of the corresponding downlink SDAP packet header; or to a specified position of the corresponding downlink PDCP packet header, etc., and this disclosure does not limit this.

[0196] In some embodiments, steps S2103 and S2104 can be executed simultaneously, or S2104 can be executed first and then S2103 can be executed. This disclosure does not limit this.

[0197] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2104. For example, step S2101 may be implemented as a standalone embodiment, step S2102 may be implemented as a standalone embodiment, step S2103 may be implemented as a standalone embodiment, step S2104 may be implemented as a standalone embodiment, step S2101+S2102 may be implemented as a standalone embodiment, etc., but is not limited thereto.

[0198] 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.

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

[0200] In this embodiment of the disclosure, the terminal can receive the mapping relationship between access layer protocol data packets and radio bearers configured for it by the network device, which provides conditions for reliably establishing a radio-only bearer between the terminal and the access network device and further improving the service scope of the communication system application.

[0201] 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:

[0202] Step S3101: Receive configuration information, wherein the configuration information is used to configure the access layer quality of service (QoS) rule list, and the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

[0203] In some embodiments, the QoS rules described above include one or more of the following: QoS rule identifier; QoS flow identifier; radio bearer identifier; packet filter set; priority.

[0204] In some embodiments, the number of QoS rules that the first data packet conforms to is greater than the number of QoS rules that the second data packet conforms to, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

[0205] In some embodiments, the above list of QoS rules or the QoS rules correspond to any of the following: terminal; radio bearer; protocol.

[0206] In some embodiments, the first QoS rule corresponds to the first radio bearer, and the first QoS rule is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

[0207] In some embodiments, the identification information of the first QoS rule corresponding to the different terminals is different, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

[0208] In some embodiments, the packet filter described above includes one or more of the following: protocol type; data type; service type; QoS requirements.

[0209] In some embodiments, the QoS rule list above includes a second QoS rule, which either does not contain a packet filter or contains a general packet filter.

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

[0211] Based on the order of each QoS rule in the QoS rule list, determine the QoS flow identifier and / or QoS rule identifier corresponding to each QoS rule.

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

[0213] Add the identification information corresponding to the uplink QoS flow to the SDAP or PDCP data packet corresponding to the uplink QoS flow. The identification information includes one or more of the following: QoS flow identifier and QoS rule identifier.

[0214] In this embodiment of the disclosure, the terminal can receive the mapping relationship between access layer protocol data packets and radio bearers configured for it by the network device, which provides conditions for reliably establishing a radio-only bearer between the terminal and the access network device and further improving the service scope of the communication system application.

[0215] 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:

[0216] Step S3201: Send configuration information, wherein the configuration information is used to configure the access layer quality of service (QoS) rule list, and the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

[0217] In some embodiments, the QoS rules described above include one or more of the following: QoS rule identifier; QoS flow identifier; radio bearer identifier; packet filter set; priority.

[0218] In some embodiments, the number of QoS rules that the first data packet conforms to is greater than the number of QoS rules that the second data packet conforms to, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

[0219] In some embodiments, the above list of QoS rules or QoS rules corresponds to any of the following: terminal; radio bearer; protocol.

[0220] In some embodiments, the first QoS rule corresponds to a radio bearer and is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

[0221] In some embodiments, the identification information of the first QoS rule corresponding to different terminals is different, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

[0222] In some embodiments, the packet filter described above includes one or more of the following: protocol type; data type; service type; QoS requirements.

[0223] In some embodiments, the QoS rule list above includes a second QoS rule, which either does not contain a packet filter or contains a general packet filter.

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

[0225] Add the identification information corresponding to the downlink QoS flow to the SDAP or PDCP data packet corresponding to the downlink QoS flow. The identification information includes one or more of the following: QoS flow identifier and QoS rule identifier.

[0226] In this embodiment of the disclosure, the network device can configure the mapping relationship between access layer protocol data packets and radio bearers for the terminal, thereby providing conditions for reliably establishing a radio-only bearer between the terminal and the access network device and further improving the service scope of the communication system application.

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

[0228] The UE receives a list of access layer Quality of Service (QoS) rules from the base station. These QoS rules can be used to determine the mapping relationship between access layer application protocol data packets and radio bearers.

[0229] In some embodiments, the terminal may be a general commercial terminal, an NTN terminal, or a low-cost terminal, etc.

[0230] In some embodiments, the above configuration can be used in an inactive or connected state.

[0231] In some embodiments, the QoS rule mentioned above may include one or more of the following: QoS rule ID; QoS flow ID; Radio Bearer ID; Packet Filter Set; precedent.

[0232] In some embodiments, the aforementioned precedence is used to determine the priority of a QoS rule. If a packet conforms to one or more QoS rules, the higher-priority QoS rule is preferred.

[0233] In some embodiments, the above QoS rule can be configured in the following ways: Method 1: Per UE configuration; Method 2: Per radio bearer configuration; Method 3: Per protocol configuration.

[0234] In some embodiments, for Method 1, the base station can configure a unified QoS rule list for the terminal through the RRC layer. In this case, the terminal's processing method for QoS flows based on this QoS rule list can be referred to the relevant descriptions in Figures 2B and 2C above.

[0235] In some embodiments, for Method 2, the base station configures one or more QoS rules for each radio bearer individually, and data packets satisfying one of the QoS rules can be mapped to that radio bearer. In this case, the terminal's processing method for the QoS flow based on the QoS rule list can be referred to the relevant descriptions in Figures 2D and 2E above.

[0236] In some embodiments, for Method 3, the base station configures a separate QoS rule for each protocol, such as the AI ​​protocol, ISAC, and / or the sensing protocol. In this case, the terminal's processing of QoS flows based on this QoS rule list can be referred to the relevant descriptions in Figures 2B and 2C above.

[0237] In some embodiments, for the above-described Method 2, QoS rule Per radio bearer configuration, the QoS rule can be included in the SDAP configuration or PDCP configuration of the radio bearer configuration.

[0238] In some embodiments, the above-mentioned packet filter includes one or more of the following: protocol type; data / service type; data QoS requirements.

[0239] In some embodiments, the service types corresponding to different services or business operations can be defined by a protocol or configured by network devices (such as core network devices) and then sent to the terminal. Alternatively, they can be configured via OAM or by CN network elements such as PCRF / AMF issuing QoS rules for defined service types to the base station, which then configures them for the terminal.

[0240] In some embodiments, the QoS rule list configuration described above includes a default QoS rule.

[0241] In some embodiments, the default QoS rule described above may not include a packet filter, or it may include a general filter. When no other QoS rule is configured for the UE, all data packets will use this default QoS rule.

[0242] In some embodiments, the UE can determine its corresponding QoS flow ID / QoS rule ID based on the order of the QoS rule in the QoS rule list. In this way, the network does not need to configure the QoS flow ID and / or QoS rule ID.

[0243] In some embodiments, QoS rule configuration is per UE. After determining the QoS flow ID / QoS rule ID of the QoS flow, the UE provides the QoS flow ID / QoS rule ID to either the SDAP layer or the PDCP layer. Whether it is provided to the SDAP layer or the PDCP layer depends on whether there is an SDAP layer; if there is, it is provided to the SDAP layer, otherwise it is provided to the PDCP layer.

[0244] In some embodiments, the UE may carry a defined QoS flow ID / QoS rule ID in the uplink header of SDAP or PDCP.

[0245] In some embodiments, for QoS rule Per radio bearer configuration, it is necessary to ensure that the QoS rule ID / QoS flow ID Per UE is unique.

[0246] 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.

[0247] 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.

[0248] 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).

[0249] 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.

[0250] In some embodiments, the transceiver module is configured to receive configuration information, wherein the configuration information is used to configure a list of access layer quality of service (QoS) rules, and wherein the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

[0251] In some embodiments, the QoS rules described above include one or more of the following: QoS rule identifier; QoS flow identifier; radio bearer identifier; packet filter set; priority.

[0252] In some embodiments, the number of QoS rules that the first data packet conforms to is greater than the number of QoS rules that the second data packet conforms to, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

[0253] In some embodiments, the above list of QoS rules or the QoS rules correspond to any of the following: terminal; radio bearer; protocol.

[0254] In some embodiments, the first QoS rule corresponds to the first radio bearer, and the first QoS rule is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

[0255] In some embodiments, the identification information of the first QoS rule corresponding to the different terminals is different, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

[0256] In some embodiments, the packet filter described above includes one or more of the following: protocol type; data type; service type; QoS requirements.

[0257] In some embodiments, the QoS rule list above includes a second QoS rule, which either does not contain a packet filter or contains a general packet filter.

[0258] In some embodiments, the processing module described above is configured to determine the QoS flow identifier and / or QoS rule identifier corresponding to each QoS rule based on the order of each QoS rule in the QoS rule list.

[0259] In some embodiments, the processing module is further configured to add the identification information corresponding to the uplink QoS flow to the SDAP data packet or PDCP data packet corresponding to the uplink QoS flow, wherein the identification information includes one or more of the following: QoS flow identifier, QoS rule identifier.

[0260] 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.

[0261] 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.

[0262] 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.

[0263] In some embodiments, the transceiver module is configured to send configuration information, wherein the configuration information is used to configure a list of access layer quality of service (QoS) rules, and wherein the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

[0264] In some embodiments, the QoS rules described above include one or more of the following: QoS rule identifier; QoS flow identifier; radio bearer identifier; packet filter set; priority.

[0265] In some embodiments, the number of QoS rules that the first data packet conforms to is greater than the number of QoS rules that the second data packet conforms to, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

[0266] In some embodiments, the above list of QoS rules or QoS rules corresponds to any of the following: terminal; radio bearer; protocol.

[0267] In some embodiments, the first QoS rule corresponds to a radio bearer and is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

[0268] In some embodiments, the identification information of the first QoS rule corresponding to different terminals is different, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

[0269] In some embodiments, the packet filter described above includes one or more of the following: protocol type; data type; service type; QoS requirements.

[0270] In some embodiments, the QoS rule list above includes a second QoS rule, which either does not contain a packet filter or contains a general packet filter.

[0271] In some embodiments, the processing module is configured to add the identification information corresponding to the downlink QoS flow to the SDAP data packet or PDCP data packet corresponding to the downlink QoS flow, wherein the identification information includes one or more of the following: QoS flow identifier, QoS rule identifier.

[0272] 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.

[0273] 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.

[0274] 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.

[0275] 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.

[0276] 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.

[0277] 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 transceiver 5103 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2101), and the processor 5101 performs other steps (e.g., at least one of S2102, S2103, S2104, etc.).

[0278] 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.

[0279] 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.

[0280] 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.

[0281] 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.

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

[0283] 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.

[0284] 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.

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

[0286] 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.

[0287] 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.

[0288] 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.

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

[0290] 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)).

[0291] 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.

[0292] 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.

[0293] 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 by comprising: include: Receive configuration information, wherein the configuration information is 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 data packets and radio bearers.

2. The method of claim 1, wherein, The QoS rules include one or more of the following: QoS rule identifier; QoS flow identifier; Wireless bearer identifier; Packet filter set; Priority.

3. The method of claim 2, wherein, The number of QoS rules that the first data packet conforms to is greater than the number of QoS rules that the second data packet conforms to, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

4. The method according to any one of claims 1 to 3, characterized in that, The QoS rule list or the QoS rule corresponds to any of the following: terminal; wireless bearer; protocol.

5. The method of claim 4, wherein, The first QoS rule corresponds to the first radio bearer. The first QoS rule is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

6. The method of claim 5, wherein, The identification information of the first QoS rule is different for different terminals, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

7. The method as described in claim 2, characterized in that, The packet filter includes one or more of the following: Protocol type; data type; service type; QoS requirements.

8. The method according to any one of claims 1-7, characterized in that, The QoS rule list contains a second QoS rule, which either does not contain a packet filter or contains a general packet filter.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: Based on the order of each QoS rule in the QoS rule list, determine the QoS flow identifier and / or QoS rule identifier corresponding to each QoS rule.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: The identification information corresponding to the uplink QoS flow is added to the SDAP data packet or PDCP data packet corresponding to the uplink QoS flow. The identification information includes one or more of the following: QoS flow identifier and QoS rule identifier.

11. A communication method, characterized in that, include: Send configuration information, wherein the configuration information is 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 data packets and radio bearers.

12. The method as described in claim 11, characterized in that, The QoS rules include one or more of the following: QoS rule identifier; QoS flow identifier; radio bearer identifier; packet filter set; priority.

13. The method as described in claim 12, characterized in that, The number of QoS rules that the first data packet conforms to is greater than the number of QoS rules that the second data packet conforms to, and the priority of the QoS rule corresponding to the first data packet is higher than the priority of the QoS rule corresponding to the second data packet.

14. The method according to any one of claims 11-13, characterized in that, The QoS rule list or the QoS rule corresponds to any of the following: terminal; wireless bearer; protocol.

15. The method as described in claim 14, characterized in that, The first QoS rule corresponds to the radio bearer. The first QoS rule is included in the Service Data Adaptation Protocol (SDAP) configuration of the first radio bearer, or the first QoS rule is included in the Packet Data Convergence Protocol (PDCP) configuration of the first radio bearer.

16. The method as described in claim 15, characterized in that, The identification information of the first QoS rule is different for different terminals, wherein the identification information includes one or more of the following: QoS rule identifier, QoS flow identifier.

17. The method as described in claim 12, characterized in that, The packet filter includes one or more of the following: Protocol type; data type; service type; QoS requirements.

18. The method as described in any one of claims 11-17, characterized in that, The QoS rule list contains a second QoS rule, which either does not contain a packet filter or contains a general packet filter.

19. The method as described in any one of claims 11-18, characterized in that, The method further includes: The identification information corresponding to the downlink QoS flow is added to the SDAP data packet or PDCP data packet corresponding to the downlink QoS flow. The identification information includes one or more of the following: QoS flow identifier and QoS rule identifier.

20. A terminal, characterized in that, The terminal includes: The transceiver module is used to receive configuration information, wherein the configuration information is used to configure a list of access layer quality of service (QoS) rules, and the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

21. A network device, characterized in that, The network device includes: The transceiver module is used to send configuration information, wherein the configuration information is used to configure a list of access layer quality of service (QoS) rules, and the QoS rules are used to indicate the mapping relationship between access layer protocol data packets and radio bearers.

22. 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-10 and 11-19.

23. 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-10, and the network device is configured to implement the communication method according to any one of claims 11-19.

24. 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-10 and 11-19.

25. 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-10 and 11-19.

Images