Communication method and communication device

Abstract

Provided are a communication method and a communication device. The method comprises: for a first QoS flow or a first data packet, a first terminal device determines to execute or not execute a first RQI-related operation.

Description

Communication methods and communication equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0002] In related technologies, once reflective quality of service indication (RQI) is enabled, the terminal device needs to derive quality of service (QoS) rules for each packet, which will bring unnecessary implementation complexity to the terminal device. Summary of the Invention

[0003] This application provides a communication method and a communication device. The various aspects covered by this application are described below.

[0004] In a first aspect, a communication method is provided, comprising: for a first QoS stream or a first data packet, a first terminal device determining whether to perform or not perform a first RQI-related operation.

[0005] In a second aspect, a communication method is provided, comprising: an access network device sending first information to a first terminal device; wherein the first information is used to configure a first rule, instruct the first terminal device to enable the first rule, and instruct the configuration of the first rule or a first RQI-related operation; wherein the first rule is used by the first terminal device to determine whether to perform or not perform the first RQI-related operation for a first data packet or a first data stream.

[0006] Thirdly, a communication method is provided, comprising: a core network device sending first information to a first terminal device; wherein the first information is used to configure a first rule, instructing the first terminal device to enable the first rule, and instructing the configuration of the first rule or a first RQI-related operation; wherein the first rule is used by the first terminal device to determine whether to perform or not perform the first RQI-related operation for a first data packet or a first data stream.

[0007] Fourthly, a communication device is provided, the communication device being a first terminal device, the communication device comprising: a determining unit, configured to determine, for a first Quality of Service (QoS) stream or a first data packet, whether to perform or not perform a first Reflection Mapping Quality of Service Indication (RQI) related operation.

[0008] Fifthly, a communication device is provided, the communication device being an access network device, the communication device comprising: a communication unit, configured to send first information to a first terminal device; wherein the first information is configured to configure a first rule, instructing the first terminal device to enable the first rule, and instructing the configuration of the first rule or a first RQI-related operation; wherein the first rule is used by the first terminal device to determine whether to execute or not execute the first RQI-related operation for a first data packet or a first data stream.

[0009] In a sixth aspect, a communication device is provided, the communication device being a core network device, the communication device comprising: a communication unit, configured to send first information to a first terminal device; wherein the first information is configured to configure a first rule, instructing the first terminal device to enable the first rule, and instructing the configuration of the first rule or a first RQI-related operation; wherein the first rule is used by the first terminal device to determine whether to execute or not execute the first RQI-related operation for a first data packet or a first data stream.

[0010] A seventh aspect provides a communication device including a transceiver, a memory, and a processor, wherein the memory is used to store a program, the processor is used to invoke the program in the memory, and to control the transceiver to receive or transmit signals so that the communication device performs the method as described in the first aspect, the second aspect, or the third aspect.

[0011] Eighth aspect, an apparatus is provided, including a processor for calling a program from a memory to cause the apparatus to perform the method as described in the first, second, or third aspect.

[0012] A ninth aspect provides a chip including a processor for calling a program from memory, causing a device having the chip mounted to perform the method as described in the first, second, or third aspect.

[0013] A tenth aspect provides a computer-readable storage medium having a program stored thereon that causes a computer to perform the methods described in the first, second, or third aspects.

[0014] Eleventhly, a computer program product is provided, including a program that causes a computer to perform the methods described in the first, second, or third aspects.

[0015] In a twelfth aspect, a computer program is provided that causes a computer to perform the methods described in the first, second, or third aspects.

[0016] This application introduces a packet-level or QoS flow-level RQI control mechanism that can determine whether RQI-related operations need to be performed for packets or QoS flows, which helps to reduce the implementation complexity of terminal devices. Attached Figure Description

[0017] Figure 1 is an example architecture diagram of a wireless communication system to which embodiments of this application can be applied.

[0018] Figure 2 is an example diagram of the format of a data packet containing the RQI field.

[0019] Figure 3 is a schematic flowchart of a communication method provided in one embodiment of this application.

[0020] Figure 4 is an example diagram of the data packet format provided in the embodiments of this application.

[0021] Figure 5 is another example diagram of the data packet format provided in the embodiments of this application.

[0022] Figure 6 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0023] Figure 7 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0024] Figure 8 is a schematic diagram of the structure of a communication device provided in one embodiment of this application.

[0025] Figure 9 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0026] Figure 10 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0027] Figure 11 is a schematic diagram of an apparatus applicable to embodiments of this application. Detailed Implementation

[0028] The technical solutions in this application will now be described in conjunction with the accompanying drawings.

[0029] The technical solutions of this application embodiment can be applied to various communication systems. For example, the embodiments of this application can be applied to Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A), New Radio (NR), evolution systems of NR, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), and 5th-generation (5G) systems. The embodiments of this application can also be applied to other communication systems, such as 6th-generation (6G) mobile communication systems, or future communication systems such as satellite communication systems.

[0030] Traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, communication systems can support not only traditional cellular communication but also one or more other types of communication. For example, a communication system can support one or more of the following communication methods: device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), enhanced machine-type communication (eMTC), vehicle-to-vehicle (V2V) communication, and vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to communication systems that support the above-mentioned communication methods.

[0031] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0032] The communication system in this application embodiment can be applied to unlicensed spectrum. This unlicensed spectrum can also be considered a shared spectrum. Alternatively, the communication system in this application embodiment can also be applied to licensed spectrum. This licensed spectrum can also be considered a dedicated spectrum.

[0033] The technical solutions of this application embodiment can be applied to various Internet of Things (IoT) communication systems. For example, this technical solution can be applied to narrowband Internet of Things (NB-IoT) communication systems. As another example, this technical solution can be applied to ambient IoT (AIoT) communication systems.

[0034] Figure 1 illustrates an example system architecture of a communication system 100 applicable to embodiments of this application. The communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 can provide network coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The terminal device 120 can access a network (such as a wireless network) through the network device 110. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity; this embodiment of the application does not limit this.

[0035] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes, etc. Optionally, the terminal device can act as a base station. For example, the terminal device can act as a scheduling entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) systems. For instance, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0036] In some embodiments, the terminal device may also be a device in AIoT (such as a reader) to meet the needs of certain scenarios.

[0037] The network device in this application embodiment can also be an access network device or a radio access network device, such as a base station. The network device in this application embodiment can refer to a radio access network (RAN) node or device that connects a terminal device to a wireless network. A base station can broadly encompass, or be interchangeable with, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in device-to-device (D2D), V2X, and M2M communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0038] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0039] In some deployments, the network device in this application embodiment may refer to a CU or a DU; or, the network device may include both a CU and a DU. The gNB may also include an AAU.

[0040] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0041] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform such as a cloud platform.

[0042] Figure 1 illustrates an exemplary network device 110 and two terminal devices 120. Optionally, the communication system 100 may include multiple network devices 110, and the communication system 100 may also include other numbers of terminal devices 120.

[0043] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system 100 shown in FIG1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 can be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities. This application embodiment does not limit this.

[0044] Reflective Quality of Service (QoS)

[0045] In NR systems, the reverse mapping QoS mechanism can be used for Internet Protocol (IP) or Ethernet Protocol Data Unit (PDU) sessions. Based on reverse mapping QoS, uplink user plane data can be mapped to QoS flows on the terminal device side without requiring a session management function (SMF) to provide QoS rules. In the reverse mapping QoS mechanism, the terminal device generates QoS rules automatically based on the received downlink data packets, and the reverse mapping QoS mechanism operates at the service data flow level.

[0046] If the terminal device supports reverse mapping QoS, it needs to indicate this support to the network device during the PDU session. Generally, this indication of support for reverse mapping QoS remains unchanged throughout the PDU session's lifecycle. However, in certain special cases, the terminal device may retract its previously sent indication of support for reverse mapping QoS to the network device. In this situation, the terminal device needs to delete all QoS rules it generated in the PDU session, and the network device can provide new QoS rules to the terminal device via signaling for the service data flows previously controlled by reverse mapping QoS. Because this scenario is special, the terminal device is generally not allowed to indicate support for reverse mapping QoS to the network device again during the PDU session's lifecycle.

[0047] When a network device determines that a service data flow should use the reverse mapping QoS mechanism, the SMF will instruct the user plane function (UPF) to enable the reverse mapping QoS mechanism for this service data flow via signaling on the N4 interface. Upon receiving the instruction, the UPF adds a Quality of Service Flow Identifier (QFI) to the header of each downlink data packet for this service data flow, and also adds an RQI. Data packets with the QFI and RQI added to the header can be sent to the terminal device through the access network device.

[0048] A reverse mapping timer is configured on the terminal device. This reverse mapping timer can use a default value, or the network device can configure a value for each PDU session. After receiving a downlink data packet carrying RQI, the terminal device generates a QoS rule. Once the reverse mapping timer corresponding to a QoS rule generated by the terminal device expires, the terminal device deletes that QoS rule.

[0049] When a network device decides to no longer use the reverse mapping QoS mechanism for a service data flow, the SMF will delete the reverse mapping QoS indication sent to the UPF for that service data flow via signaling on the N4 interface. After receiving the deletion indication, the UPF will no longer add RQI to the downlink packets of that service data flow.

[0050] Based on the SMF indication, the access network device enables a reverse QoS mapping mechanism for this QoS flow on its side. In related technologies, the format of the Service Data Adaptation Protocol (SDAP) header is shown in Figure 2. Referring to Figure 2, the SDAP header includes a reflective QoS flow to DRB mapping indication (RDI), an RQI, and a QFI. The RQI indicates whether to notify the non-access stratum (NAS) of the SDF-to-QoS flow mapping rule update.

[0051] Table 1 shows the meaning of the different values ​​of the RQI field.

[0052] In related technologies, once RQI is enabled, the protocol design requires the AS to deliver each packet to the NAS, thereby deriving QoS rules for each packet. However, for some services, the mapping rules from SDF to QoS flow can be immutable or semi-static (i.e., remain unchanged for a period of time). The RQI mechanisms provided by related technologies introduce unnecessary implementation complexity for terminal devices when supporting such services. Therefore, this application introduces a new reverse mapping QoS mechanism. Examples of this application are provided below.

[0053] Figure 3 is a schematic flowchart of a communication method provided in an embodiment of this application. The method shown in Figure 3 can be executed by a first terminal device. The first terminal device can be any type of terminal device mentioned above.

[0054] Referring to Figure 3, in step S310, for the first QoS flow or the first data packet, the first terminal device performs or does not perform the first RQI-related operation (the first terminal device may, for example, perform some of the operations in the first RQI-related operation, and / or not perform some of the operations in the first RQI-related operation), or the first terminal device determines whether to perform or not perform the first RQI-related operation (the first terminal device may, for example, determine to perform some of the operations in the first RQI-related operation, and / or determine not to perform some of the operations in the first RQI-related operation).

[0055] This application does not specifically limit the content of the first RQI-related operation in the embodiments. For example, the first RQI-related operation includes one or more of the following: obtaining RQI from the first data packet or the data packet of the first QoS stream; deriving QoS rules based on the RQI in the first data packet or the data packet of the first QoS stream; indicating the RQI in the first data packet or the data packet of the first QoS stream to the NAS of the first terminal device; indicating to the NAS of the first terminal device to update or derive the SDF to QoS stream mapping rules; ignoring or skipping the RQI field in the first data packet or the data packet of the first QoS stream; ignoring the derived SDF to QoS stream mapping rules; maintaining the current SDF to QoS stream mapping rules; updating or deriving the SDF to QoS stream mapping rules; starting or restarting the first timer (the first timer is used to control whether the first RQI-related operation is executed or not, as described in detail below); parsing the header of the first data packet or the data packet of the first QoS stream using a first header format (a header format excluding the RQI field) (the first header format mentioned here may be, for example, the header format of the SDAP header).

[0056] For example, the first RQI-related operation may include a first operation. The first operation includes one or more of the following: obtaining RQI from a first data packet or a data packet of a first QoS flow; deriving QoS rules based on the RQI in the first data packet or data packet of the first QoS flow; indicating the RQI in the first data packet or data packet of the first QoS flow to the NAS of the first terminal device; indicating to the NAS of the first terminal device to update or derive the SDF-to-QoS flow mapping rules; updating or deriving the SDF-to-QoS flow mapping rules. In this example, step S310 may include: for the first QoS flow or the first data packet, the first terminal device determines whether to perform the first operation or not.

[0057] For example, the first RQI-related operation may include a second operation. The second operation includes one or more of the following: ignoring or skipping the RQI field in the first data packet or the data packet of the first QoS flow; ignoring the SDF-to-QoS flow mapping rules; not instructing the NAS of the first terminal device to update or derive the SDF-to-QoS flow mapping rules; not updating or deriving the SDF-to-QoS flow mapping rules; and parsing the header of the first data packet or the data packet of the first QoS flow using a first header format (a header format excluding the RQI field). In this example, step S310 may include: for the first QoS flow or the first data packet, the first terminal device determining whether to perform or not perform the second operation.

[0058] For example, the first RQI-related operation may include a third operation. The third operation includes one or more of the following: obtaining the RQI from the first data packet or the data packet of the first QoS stream; indicating the RQI in the first data packet or the data packet of the first QoS stream to the NAS of the first terminal device; indicating to the NAS of the first terminal device to update or derive the SDF-to-QoS stream mapping rules; the NAS of the first terminal device not updating or deriving the SDF-to-QoS stream mapping rules, and the NAS of the first terminal device not deriving QoS rules based on the RQI in the first data packet or the data packet of the first QoS stream. In this example, step S310 may include: for the first QoS stream or the first data packet, the first terminal device determining whether to perform the third operation.

[0059] In some embodiments, the first terminal device may determine whether to perform or not perform a first RQI-related operation based on a first rule. The first rule mentioned herein may be associated with one or more of the following: a first duration for controlling the execution or non-execution of some or all of the operations in the first RQI-related operation (as an example, the first duration may be represented by a first timer, that is, the first timer is used to control the execution or non-execution of some or all of the operations in the first RQI-related operation); identification information of one or more QoS flows, wherein the one or more QoS flows are used to perform the first RQI-related operation, or the identification information is used to determine whether to perform or not perform the first RQI-related operation; and information in a first data packet, wherein the information in the first data packet is used to determine whether to perform or not perform the first RQI-related operation.

[0060] The following examples illustrate the specific content of the first rule.

[0061] In one implementation, the first rule is associated with a first duration. The first duration is used for RQI control, i.e., controlling whether or not a first RQI-related operation is performed. This first duration can be a timer for one or more QoS flows, or a timer for a terminal device. That is, the scope of the first duration can be a single QoS flow, multiple QoS flows, or a terminal device. The QoS flow targeted by the first duration can be a QoS flow that supports RQI, or a QoS flow with RQI enabled. The first rule may include: if the current time falls within the time range corresponding to the first duration, then for the first data packet or the first QoS flow, the first terminal device performs or determines to perform some or all of the operations in the first RQI-related operation; and / or, if the current time does not fall within the time range corresponding to the first duration, then the first terminal device does not perform or determines not to perform some or all of the operations in the first RQI-related operation.

[0062] In one implementation, the first rule is associated with a first timer. The first timer is used for RQI control, that is, to control whether or not a first RQI-related operation is performed. This first timer can be a timer for one or more QoS flows, or a timer for a terminal device. In other words, the scope of the first timer can be a single QoS flow, multiple QoS flows, or a terminal device. The QoS flow targeted by the first timer can be a QoS flow that supports RQI, or a QoS flow with RQI enabled.

[0063] The embodiments of this application do not specifically limit the maintenance method of the first timer.

[0064] For example, the first timer may be maintained jointly by the first terminal device and the access network device, or jointly by the first terminal device and the core network device, or maintained solely by the first terminal device.

[0065] For example, the first timer is maintained by the NAS or AS of the first terminal device.

[0066] For example, if the first RQI-related operation includes the third operation mentioned above, the first timer is maintained by the NAS of the first terminal device.

[0067] For example, if the first RQI-related operation includes the second operation mentioned above, the first timer is maintained by the AS of the first terminal device.

[0068] For example, if the first RQI-related operation includes the first operation mentioned above, the first timer is maintained by the AS and / or NAS of the first terminal device.

[0069] Based on the introduction of a first timer, the first rule may include: if the first timer is running, then for the first data packet or the first QoS flow, the first terminal device performs or determines to perform some or all of the operations in the first RQI-related operations; and / or, if the first timer is not started or times out, then the first terminal device does not perform or determines not to perform some or all of the operations in the first RQI-related operations.

[0070] For example, if the first timer is running, the first terminal device will not perform or will determine not to perform the first operation mentioned above for the first data packet or the first QoS stream. Furthermore, as an implementation, if the first timer is running and the first QoS stream is the QoS stream corresponding to the first timer, the first terminal device will not perform or will determine not to perform the first operation mentioned above for the data packets in the first QoS stream.

[0071] For example, if the first timer is running, the first terminal device performs or determines to perform the second operation mentioned above for the first data packet or the first QoS stream.

[0072] For example, if the first timer is running, the first terminal device performs or determines to perform the third operation mentioned above for the first data packet or the first QoS stream.

[0073] For example, if the first timer is a timer for a QoS stream, and the first data packet is a data packet in the QoS stream corresponding to the first timer, then the first terminal device will not execute or will determine not to execute the first operation mentioned above. Whether the first data packet belongs to the QoS stream corresponding to the first timer can be determined based on the information in the first data packet. For example, it can be determined whether the first data packet belongs to the QoS stream corresponding to the first timer based on the QFI field in the first data packet. If the QFI field of the first data packet matches the QFI of the QoS stream corresponding to the first timer, then it means that the first data packet belongs to the QoS stream corresponding to the first timer; otherwise, the first data packet does not belong to the QoS stream corresponding to the first timer.

[0074] For example, if the first timer is a timer for a QoS stream, and the first data packet is a data packet in the QoS stream corresponding to the first timer, then the first terminal device executes or determines to execute the second operation mentioned above.

[0075] For example, if the first timer is a timer for a QoS stream, and the first data packet is a data packet in the QoS stream corresponding to the first timer, then the first terminal device executes or determines to execute the third operation mentioned above.

[0076] For example, if the first timer does not start or times out, the first terminal device performs or determines to perform the first operation for the first data packet or the first QoS stream.

[0077] For example, if the first timer is a timer for a QoS stream, and the first data packet is a data packet in the QoS stream corresponding to the first timer, then the first terminal device executes or determines to execute the first operation mentioned above.

[0078] For example, if the first timer is a timer for the QoS stream, and the first data packet is a data packet in the QoS stream corresponding to the first timer, then the first terminal device will not execute or will determine not to execute the second operation mentioned above.

[0079] For example, if the first timer is a timer for the QoS stream, and the first data packet is a data packet in the QoS stream corresponding to the first timer, then the first terminal device will not execute or will determine not to execute the third operation mentioned above.

[0080] Below are some more specific examples (in the examples below, the data packets mentioned above are SDAP packets. Of course, they could also be other packet headers carrying flow information or packet information).

[0081] For example, for QoS flows that support RQI and / or QoS flows that enable RQI, when the RQI of the first data packet is set or RQI is 1, the first terminal device controls the first terminal device to parse, not parse, or parse the RQI field in the SDAP packet header based on the first timer.

[0082] For example, for QoS flows that support RQI and / or QoS flows that enable RQI, when the RQI of the first data packet is set or RQI is 1, the first terminal device controls the first terminal device to derive, not derive, or whether to derive QoS rules based on the first timer.

[0083] For example, for QoS flows that support RQI and / or QoS flows that enable RQI, when the RQI of the first data packet is set or RQI is 1, the first terminal device controls the AS of the first terminal device to indicate RQI to or not to or whether to indicate RQI to the NAS of the first terminal device based on the first timer.

[0084] For example, for QoS flows that support RQI and / or QoS flows with RQI enabled, when the RQI of the first data packet is set or RQI is 1, the first terminal device controls whether the NAS of the first terminal device derives or updates the mapping / mapping rules from SDF to QoS flow based on the first timer.

[0085] For example, before the first timer expires, the first terminal device continues to use the QoS rules previously derived or stored by the first terminal device (which can also be understood as the QoS rules derived before the first timer starts or restarts). In other words, before the first timer expires, the first terminal device does not generate new QoS rules or derive QoS rules.

[0086] In one implementation, the first rule is associated with identification information of one or more QoS flows. These one or more QoS flows may be QoS flows configured or indicated by a network device (access network device and / or core network device). The network device may configure or indicate QoS flows used to perform a first RQI-related operation, or it may configure or indicate QoS flows not used to perform the first RQI-related operation, or it may simultaneously configure QoS flows that perform and do not perform the first RQI-related operation. The identification information of the one or more QoS flows may be any type of information capable of identifying the QoS flows. For example, the network device may indicate the QFI of the one or more QoS flows to a first terminal device. As another example, the network device may indicate a PDU session (such as the identifier of the PDU session) to the first terminal device, thereby indirectly indicating one or more QoS flows associated with the PDU session. The first rule may include: if the first QoS flow belongs to the one or more QoS flows, then the first terminal device performs or determines to perform some or all of the operations in the first RQI-related operation; and / or, if the first QoS flow does not belong to the one or more QoS flows, then the first terminal device does not perform or determines not to perform some or all of the operations in the first RQI-related operation.

[0087] For example, if the first QoS flow belongs to one or more QoS flows, the first terminal device does not perform or determines not to perform the first operation mentioned above. Whether the first QoS flow belongs to one or more QoS flows can be determined based on information in the packets in the first QoS flow. For example, if the QFI in the QFI field of the packets in the first QoS flow matches the QFI of one or more QoS flows, it indicates that the first QoS flow belongs to one or more QoS flows. From this perspective, the scheme proposed in this example can provide QFI-level QoS control. Exemplarily, if the first QoS flow belongs to one or more QoS flows, the first terminal device performs one or more of the following actions: does not parse the RQI field in the SDAP header of the first QoS flow, does not derive QoS rules, the AS of the first terminal device does not indicate the RQI to the NAS, and updates the QoS rules based on the QoS rules sent by the SMF. Alternatively, if the first QoS flow belongs to one or more QoS flows, and the RQI field of the data packet of the first QoS flow takes the first value (e.g., 1), the first terminal device performs one or more of the following actions: does not parse the RQI field in the SDAP header of the first QoS flow, does not derive QoS rules, the AS of the first terminal device does not indicate the RQI to the NAS, and updates the QoS rules based on the QoS rules sent by the SMF.

[0088] For example, if the first QoS flow belongs to one or more QoS flows, the first terminal device performs or determines to perform the second operation mentioned above. Exemplarily, if the first QoS flow belongs to one or more QoS flows, the first terminal device can parse the data packets in the first QoS flow using a first header format. This first header format can be a header format that does not include the RQI field; for example, Figure 4 or Figure 5 shows two possible implementations of the first header format.

[0089] For example, if the first QoS flow belongs to one or more QoS flows, the first terminal device performs or determines to perform the third operation mentioned above. Exemplarily, if the first QoS flow belongs to one or more QoS flows, the first terminal device's NAS does not derive QoS rules based on the RQI in the first data packet or the data packet of the first QoS flow.

[0090] For example, if the first QoS flow belongs to one or more QoS flows, then the SDAP header may not need to be configured for the packets in the first QoS flow.

[0091] For example, if the first QoS flow does not belong to the one or more QoS flows, the first terminal device does not perform or is determined not to perform the first operation mentioned above.

[0092] For example, if the first QoS flow does not belong to the one or more QoS flows, the first terminal device determines or decides to perform the second operation mentioned above.

[0093] For example, if the first QoS flow does not belong to the one or more QoS flows, the first terminal device performs or determines to perform the third operation mentioned above.

[0094] For example, if the first QoS flow belongs to one or more QoS flows, then the data packets in the first QoS flow use the first header format described above.

[0095] For example, if the first QoS flow does not belong to one or more QoS flows, then the data packets in the first QoS flow do not use the first header format described above.

[0096] For example, if the first QoS flow belongs to one or more QoS flows, then an SDAP header can be configured for the packets in the first QoS flow; otherwise, an SDAP header can be left unconfigured for the packets in the first QoS flow.

[0097] The content of the first rule has been illustrated in detail above. During communication, the first terminal device can always communicate based on the first rule. Alternatively, in some embodiments, the first terminal device can communicate based on the first rule when certain conditions (hereinafter referred to as the first condition for ease of description) are met.

[0098] The specific content of the first condition can be set according to actual needs, and this application embodiment does not impose specific limitations on it. For example, the first condition can be related to one or more of the following: a first capability and receiving first information sent by a network device.

[0099] The first capability mentioned above can be used to indicate whether the first terminal device supports, does not support, or does not support the first rule. Alternatively, the first capability mentioned above can be used to indicate whether the first terminal device supports, does not support, or does not support the first RQI-related operation. For example, the first capability can be used to indicate that the first terminal device supports not performing the first operation mentioned above. As another example, the first capability can be used to indicate that the first terminal device supports performing the second operation mentioned above. As yet another example, the first capability can be used to indicate that the first terminal device supports performing the third operation mentioned above.

[0100] The first information mentioned above (the first information mentioned in the embodiments of this application may be, for example, control information sent by a network device) can be used to configure a first rule. For example, the first information can be used to configure a first duration or instruct a first terminal device to use a first duration. The first information can be used to configure a first timer. As another example, the first information can be used to configure the identification information of one or more data streams associated with the first rule mentioned above. Alternatively, the first information can be used to instruct the first terminal device to enable, activate, or not execute a first RQI-related operation. Alternatively, the first information mentioned above can be used to instruct the first terminal device to enable, activate, or activate a first rule. Alternatively, the first information can be used to instruct the relevant configuration of the first rule or the first RQI-related operation, such as the PDCP entity, SDAP entity, first protocol layer, QoS stream, radio bearer, media access control (MAC) entity, or terminal device corresponding to the first rule or the first RQI-related operation.

[0101] It should be noted that the first information can be information specific to the first terminal device, information specific to a QoS flow, information specific to a MAC entity, or information specific to a radio bearer. If the first information is information specific to the first terminal device, then all data packets received by the first terminal device can be used to determine whether or not to perform the first RQI-related operation according to the first rule. If the first information is information specific to a QoS flow, then the first terminal device can use the first rule to determine whether or not to perform the first RQI-related operation for data packets in that QoS flow. If the first information is information specific to a MAC entity, then the first terminal device can use the first rule to determine whether or not to perform the first RQI-related operation for data packets associated with that MAC entity. If the first information is information specific to a radio bearer, then the first terminal device can use the first rule to determine whether or not to perform the first RQI-related operation for data packets associated with that radio bearer.

[0102] This application does not specifically limit the type of network device sending the first information in its embodiments. For example, as shown in FIG6, the first information can be sent by an access network device (see step S610 in FIG6). As shown in FIG7, the first information can be sent by a core network device (see step S710 in FIG7). The first information can be carried in NAS signaling, radio resource control (RRC) signaling, SDAP control PDU, MAC control element (CE), downlink control information (DCI), or control signaling of the first protocol layer. For example, if the first information is sent by an access network device, it can be carried in RRC signaling, SDAP control PDU, MAC CE, DCI, or control signaling of the first protocol layer. Similarly, if the first information is sent by a core network device, it can be carried in NAS signaling or control signaling of the first protocol layer. It should be understood that the first protocol layer mentioned above can be the SDAP layer or the PDCP layer. Alternatively, the first protocol layer can also be a newly added protocol layer (i.e., a new protocol layer introduced in future protocols). Alternatively, the first protocol layer can be a protocol layer composed of multiple protocol layers. For example, the first protocol layer can be a protocol layer composed of the PDCP layer and the radio link control (RLC) layer, or a protocol layer composed of the RLC layer and the MAC layer. Furthermore, the embodiments of this application do not specifically limit the type of control signaling mentioned above; for example, it can be a control PDU or a control CE.

[0103] Below are some possible examples of the functions performed by the first message. It should be understood that the first message can satisfy one or more of the functions mentioned below. If the first message performs multiple functions, it can contain multiple messages, which can be sent simultaneously or separately.

[0104] For example, the first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first duration / related operation.

[0105] For example, the first information is used to explicitly or implicitly indicate the first terminal device to maintain the first duration.

[0106] For example, the first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer.

[0107] For example, the first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer.

[0108] For example, the first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of one or more QoS flows.

[0109] For example, the first information is used to configure the first terminal device to perform or not perform the first RQI-related operation.

[0110] For example, the first information is used to configure the first terminal device to perform or not perform the first operation.

[0111] For example, the first information is used to configure the first terminal device to perform or not perform the second operation.

[0112] For example, the first information is used to configure the first terminal device to perform or not perform the third operation.

[0113] For example, the first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule.

[0114] For example, the first information is used to configure the first terminal device to perform the first operation based on or not based on the first rule.

[0115] For example, the first information is used to configure the first terminal device to perform the second operation based on or not based on the first rule.

[0116] For example, the first information is used to configure the first terminal device to perform a third operation based on or not based on the first rule.

[0117] For example, the first information is used to configure or instruct the PDCP entity, SDAP entity, first protocol layer, QoS stream, radio bearer, MAC entity, or terminal device to perform the first RQI-related operation.

[0118] For example, the first information is used to configure or instruct a PDCP entity, SDAP entity, first protocol layer, QoS stream, radio bearer, MAC entity, or terminal device to perform a first RQI-related operation based on a first rule.

[0119] For example, the first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the first rule.

[0120] For example, the first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule.

[0121] For example, the first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule.

[0122] For example, the first information is used to configure the first duration.

[0123] For example, the first information is used to configure the first timer.

[0124] For example, the first information is used to configure one or more QoS flows.

[0125] For example, the first information is used to configure the QoS flow corresponding to the first timer.

[0126] For example, the first information is used to activate or parse the header of a data packet using a first header format, which does not include the RQI field.

[0127] For example, the first information is used to activate or configure the first header format, which does not include the RQI field.

[0128] As mentioned earlier, if the first condition is met, the first terminal device determines whether to perform or not perform the first RQI-related operation according to the first rule. Several examples are given below.

[0129] For example, if the first terminal device supports the first rule and / or the first terminal device receives the first information sent by the network device, then the first terminal device does not perform or determines not to perform the first operation mentioned above.

[0130] For example, if the first terminal device supports the first rule and / or the first terminal device receives the first information sent by the network device, then the first terminal device performs or determines to perform the second operation mentioned above.

[0131] For example, if the first terminal device supports the first rule and / or the first terminal device receives the first information sent by the network device, then the first terminal device performs or determines to perform the third operation mentioned above.

[0132] For example, if the first terminal device does not support the first rule and / or the first terminal device does not receive the first information sent by the network device, then the first terminal device performs or determines to perform the first operation mentioned above.

[0133] For example, if the first terminal device does not support the first rule and / or the first terminal device does not receive the first information sent by the network device, then the first terminal device will not perform or will determine not to perform the second operation mentioned above.

[0134] For example, if the first terminal device does not support the first rule and / or the first terminal device does not receive the first information sent by the network device, then the first terminal device will not perform or will determine not to perform the third operation mentioned above.

[0135] The embodiments of this application do not specifically limit the objects targeted by the first RQI-related operations mentioned above.

[0136] For example, the first RQI-related operation is an operation for a first QoS stream or an operation for data packets in the first QoS stream. For other QoS streams or data in other QoS streams, the first terminal device may not perform RQI-related operations or may perform RQI-related operations based on relevant technologies.

[0137] For example, the first RQI-related operation is an operation on the QoS stream corresponding to the first timer or an operation on the data packets of the QoS stream corresponding to the first timer. For other QoS streams or data in other QoS streams, the first terminal device may not perform RQI-related operations or may perform RQI-related operations based on relevant technologies.

[0138] For example, the first RQI-related operation is an operation on a QoS flow determined based on first information sent by the network device (a detailed description of the first information can be found above and will not be elaborated here), or an operation on data packets in a QoS flow determined based on the first information sent by the network device. For other QoS flows or data in other QoS flows, the first terminal device may not perform RQI-related operations or may perform RQI-related operations based on relevant technologies.

[0139] For example, the first RQI-related operation is an operation on any QoS flow of the first terminal device, or an operation on the data packets of any QoS flow of the first terminal device.

[0140] The first timer mentioned above can be configured by the access network device. For example, the access network device can configure the first timer based on the first information mentioned above.

[0141] Alternatively, the first timer can also be configured by the core network device. For example, the core network device can configure the first timer based on the first information mentioned above. For example, the core network device can configure the first timer through NAS signaling. Exemplarily, the core network device will carry NAS signaling during the PDU session establishment process, and carry the first information based on the NAS signaling to configure the first timer. Alternatively, the core network can also carry the first information through the first protocol layer packet header to configure the first timer. Optionally, if the NAS signaling does not carry the first information, the first terminal device can determine that the first timer has not been configured. In this case, the first terminal device can choose not to use the first timer for RQI control (i.e., perform the operation mentioned above of determining whether to perform the first RQI-related operation according to the first rule). Alternatively, the first terminal device can still perform RQI control based on the first timer, in which case the timing duration of the first timer can be a default value.

[0142] In some embodiments, the first timer may be activated by an access network device. For example, the access network device may activate the first timer based on the first information mentioned above. Optionally, the access network device may maintain the first timer.

[0143] In some embodiments, the first timer can be activated by a core network device. For example, the core network device can activate the first timer based on the first information mentioned above. Optionally, the core network device can maintain the first timer.

[0144] In some embodiments, the first timer may be maintained by the access network device, the first terminal device, and / or the core network device.

[0145] When the first terminal device maintains the first timer, it can do so either in the AS (Application Server) or the NAS (Application Network Server). For example, if the first timer is maintained in the AS, before the first timer expires, the first terminal device may not parse the RQI field of the data packets in the QoS stream corresponding to the first timer, and / or may not indicate RQI or RQI enable information to the NAS for the data packets in the QoS stream corresponding to the first timer. Similarly, if the first timer is maintained in the NAS, before the first timer expires, the first terminal device may not derive QoS rules for the data packets in the QoS stream corresponding to the first timer.

[0146] For example, assuming the QoS flow corresponding to the first timer is QFI x, if the first terminal device receives a new data packet during the operation of the first timer, and the QoS flow or QoS flow identifier corresponding to the data packet is QFI x, then the first terminal device does not deduce the QoS rules or parse the RQI field of the SDAP packet header.

[0147] For example, assuming the QoS flow corresponding to the first timer is QFI x, if the first terminal device receives a new data packet during the operation of the first timer, and the data packet has an SDAP header or an RQI field in the SDAP header, and the QFI field in the SDAP header matches QFI x, then the first terminal device does not deduce QoS rules or parse the RQI field in the SDAP header.

[0148] For example, assuming the QoS flow corresponding to the first timer is QFI x, if the first terminal device receives a new data packet during the operation of the first timer, and the QoS flow or QoS flow identifier corresponding to the data packet is QFI x, then the first terminal device indicates RQI to the higher layer, or does not indicate the update of SDF to QoS flow to the higher layer.

[0149] For example, assuming the QoS flow corresponding to the first timer is QFI x, if the first terminal device receives a new data packet during the operation of the first timer, and the data packet has an SDAP header or the SDAP header has an RQI field and the QFI field of the SDAP header matches QFI x, then the first terminal device indicates the RQI to the higher layer, or does not indicate the update of the SDF to QoS flow to the higher layer.

[0150] When the access network device maintains a first timer, optionally, the access network device can determine whether or not an RQI is generated or indicated in a data packet (such as the downstream SDAP header) based on the first timer. For example, for a data packet of a first QoS flow, if the first timer is not running, the access network device sets the RQI of the data packet to 1. As another example, for a QoS flow with RQI enabled, if the first timer is running, the access network device sets the RQI of the data packet to 0.

[0151] In some embodiments, the duration of the first timer is a default, predefined, or configured by the access network device or the core network device.

[0152] In some embodiments, the use, non-use, or whether to use a first duration can be configured or indicated by the access network device.

[0153] In some embodiments, the use, non-use, or whether to use a first duration can be configured or indicated by the core network equipment.

[0154] In some embodiments, enabling, disabling, or not enabling the first timer can be configured or indicated by the access network device.

[0155] In some embodiments, enabling, disabling, or not enabling the first timer can be configured or indicated by the core network device.

[0156] In some embodiments, one or more QoS flows associated with the first rule mentioned above may be configured or indicated by the access network device.

[0157] In some embodiments, one or more QoS flows associated with the first rule mentioned above may be configured or indicated by the core network device.

[0158] In some embodiments, the first rule mentioned above can be configured by the access network device.

[0159] In some embodiments, the first rule mentioned above can be configured by the core network equipment.

[0160] In some embodiments, enabling, disabling, or not enabling the first rule can be configured or indicated by the access network device.

[0161] In some embodiments, enabling, disabling, or not enabling the first rule can be configured or indicated by the core network equipment.

[0162] In some embodiments, the PDCP entity, SDAP entity, first protocol layer, QoS stream, radio bearer, MAC entity, and terminal device that perform the first RQI-related operations (such as the first operation and / or the second operation and / or the third operation mentioned above) are configured or indicated by the access network device.

[0163] In some embodiments, the PDCP entity, SDAP entity, first protocol layer, QoS stream, radio bearer, MAC entity, and terminal device that perform the first RQI-related operation (such as the first operation and / or the second operation and / or the third operation mentioned above) are configured or indicated by the core network device.

[0164] In some embodiments, the PDCP entity, SDAP entity, first protocol layer, QoS flow, radio bearer, MAC entity, and terminal device that execute the first rule are configured or indicated by the access network device.

[0165] In some embodiments, the PDCP entity, SDAP entity, first protocol layer, QoS flow, radio bearer, MAC entity, and terminal device that execute the first rule are configured or indicated by the core network device.

[0166] The preceding text mentioned various types of QoS flows. For ease of description, the following text introduces a second QoS flow. The second QoS flow may include one or more of the following: the first QoS flow mentioned above, one or more QoS flows related to the first rule, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

[0167] The data packets of the second QoS flow can satisfy one of the following: carrying a QoS flow identifier; carrying QFI and RQI; carrying QFI but not RQI; or not carrying QFI and not RQI. Alternatively, the data packets of the first QoS flow can satisfy one of the following: including a first header (the first header mentioned in this embodiment can be, for example, an SDAP header), and the first header carries QFI but not RQI (see Figure 4 or Figure 5); including a first header, and the first header carries both QFI and RQI; or not including a first header. The first header mentioned here can be, for example, an SDAP header.

[0168] The data packets or QoS streams mentioned above can refer to the data packets or QoS streams received by the first terminal device. In addition to the data packets or QoS streams mentioned above, the first terminal device can also receive other types of data packets or QoS streams (such as data packets or QoS streams that do not need to determine whether to perform, not perform, or perform the first RQI-related operation based on the first rule).

[0169] In summary, the first terminal device can receive one or more of the following:

[0170] The first type of QoS flow is a QoS flow associated with the first rule or the first information. The first type of data flow may include, for example, the first QoS flow mentioned above, one or more QoS flows, the QoS flow where the first data packet is located, and one or more of the QoS flows corresponding to the first timer.

[0171] The second type of QoS flow is a QoS flow that is not associated with the first rule or the first information. This second type of QoS flow may be, for example, a QoS flow that performs RQI operation based on relevant technologies, or a QoS flow that does not perform any RQI operation.

[0172] The first type of QoS flow is the QoS flow that performs the first RQI-related operation;

[0173] The second type of QoS flow is a QoS flow that does not perform the first RQI related operation. This second type of data packet may be, for example, a data packet that performs RQI operation based on related technology, or a data packet that does not perform any RQI operation.

[0174] The first type of data packet is a data packet that performs the first RQI-related operation in a specific QoS flow;

[0175] The second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation;

[0176] The first type of data packet is a data packet associated with the first rule or the first information in a specific QoS flow;

[0177] The second type of data packet is a data packet in a specific QoS flow that is not associated with the first rule or the first information.

[0178] Different types of QoS streams or packets can be transmitted using the same radio bearer or different radio bearers. For example, Type I QoS streams and Type II QoS streams can be mapped to the same data radio bearer. Alternatively, Type I QoS streams and Type II QoS streams can be mapped to different data radio bearers. Similarly, Type I packets and Type II packets can be transmitted using the same data radio bearer. Or, Type I packets and Type II packets can be transmitted using different data radio bearers.

[0179] Mapping different types of QoS flows or different types of data packets to different data radio bearers can be implemented based on network device configuration. For example, the mapping relationship between QoS flow or data packet types and data radio bearers can be configured based on the RRC signaling sent by the network device.

[0180] If different types of QoS streams can be mapped to the same data radio bearer, the first terminal device can determine the behavior it needs to perform based on the QFI of the different QoS streams.

[0181] As mentioned earlier, the first timer may be in a running state or a non-started state. This application embodiment does not specifically limit the starting conditions of the first timer. For example, if the RQI value in the first data packet or the data packet of the first QoS stream is a first value (e.g., 1), the first terminal device starts the first timer. Alternatively, if the first timer corresponds to a data stream, then if the RQI value of the data packet in the data stream corresponding to the first timer is a first value (e.g., 1), the first terminal device starts the first timer, even if the first timer is not started. Or, if the first timer corresponds to a data stream (e.g., a service data stream), then if the first terminal device receives a data packet from the QoS stream corresponding to that data stream, or receives a data packet from that data stream, even if the first timer is not started. Of course, the first timer can also be started based on other conditions, such as the first terminal device starting the first timer after receiving the configuration information of the first timer (the first information mentioned earlier may include the configuration information of the first timer). For example, assuming the QoS flow corresponding to the first timer is QFI x, if the first terminal device receives an SDAP packet for the first time when the first timer is not started, and the packet has an SDAP header or an RQI field in the header, and the QFI field of the SDAP packet indicates a QFI that matches QFI x, then the first terminal device performs one or more of the following operations: derives QoS rules or parses the RQI field of the SDAP packet, and starts the first timer. For example, assuming the data flow corresponding to the first timer, if the first terminal device receives a data packet from this data flow for the first time when the first timer is not started, then the first terminal device performs one or more of the following operations: derives QoS rules or parses the RQI field of the SDAP packet, and starts the first timer. For example, assuming the QoS flow corresponding to the first timer, if the first terminal device receives a data packet from this QoS flow for the first time when the first timer is not started, then the first terminal device performs one or more of the following operations: derives QoS rules or parses the RQI field of the SDAP packet, and starts the first timer.

[0182] In some embodiments, the data packets mentioned in the preceding embodiments may refer to downlink data packets received by the terminal device. These downlink data packets may, for example, be first protocol layer data packets. Correspondingly, the first packet format mentioned in the preceding embodiments may refer to the packet format of first protocol layer data. The first protocol layer may be the SDAP layer or the PDCP layer. Alternatively, the first protocol layer may be a newly added protocol layer (i.e., a new protocol layer introduced in a future protocol). Alternatively, the first protocol layer may be a protocol layer composed of multiple protocol layers. For example, the first protocol layer may be a protocol layer composed of the PDCP layer and the radio link control (RLC) layer, or a protocol layer composed of the RLC layer and the MAC layer.

[0183] In some embodiments, the data packets mentioned in the preceding examples may refer to downlink data packets received by the terminal device. These downlink data packets may, for example, be SDAP packets. Accordingly, the first packet format mentioned in the preceding examples may refer to the packet format of an SDAP packet.

[0184] In some embodiments, the radio bearers mentioned in the foregoing embodiments may include radio data bearers and / or radio signaling bearers.

[0185] In some embodiments, the QoS flow mentioned in the preceding embodiments may also refer to a sub-QoS flow. Alternatively, the QoS flow mentioned in the preceding embodiments may be replaced with an SDF. Alternatively, the QoS flow mentioned in the preceding embodiments may also be an SDF or data packet with a first feature or tag, and the SDF or data packet belongs to a QoS flow.

[0186] It should be understood that the first timer mentioned in each embodiment of this application is replaced with the first duration.

[0187] The embodiments of this application are described in more detail below with specific examples. It should be understood that the UE mentioned below corresponds to the first terminal device mentioned above, the timer mentioned below corresponds to the first timer mentioned above, the QFI mentioned in Embodiment 2 below corresponds to one or more QoS flows related to the first rule mentioned above, and the data packets mentioned below are all downlink SDAP packets. It should be noted that the examples below are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific values ​​or scenarios illustrated. Those skilled in the art can obviously perform various equivalent modifications or changes based on the given examples, and such modifications or changes also fall within the scope of the embodiments of this application.

[0188] Example 1

[0189] Example 1 introduces a packet-level QoS mechanism that controls UE behavior based on a timer. For example, for QoS flows that support RQI, and / or QoS flows with RQI enabled, when RQI is set or RQI is 1, the UE controls whether to parse the RQI field in the SDAP header, or whether to derive QoS rules, or whether the UE AS indicates RQI to the UE NAS, based on the timer.

[0190] The QoS rules derived by the UE are used until the timer expires.

[0191] No new QoS rules are generated or QoS flows are deduced before the timer expires.

[0192] When the UE receives a DL packet indicating that RQI is set or RQI=1, the UE starts the timer.

[0193] This timer is configured by the core network equipment or the access network equipment;

[0194] This timer is used in UE and / or access network equipment maintenance.

[0195] The following provides a more detailed example of Example 1.

[0196] RQI control is performed based on a timer. Timer-based RQI control can include one or more of the aspects described below.

[0197] The activation or enablement of a timer-based RQI control mechanism is controlled by core network equipment or access network equipment, and / or the control information used to activate or enable this control mechanism is carried via NAS signaling, RRC signaling, SDAP control PDU, MAC CE, or DCI. Optionally, the control information used to activate or enable this control mechanism is for the UE, or for a QoS flow (correspondingly, carrying a PDU session and / or QFI to indicate the corresponding QoS flow or QoS flow list).

[0198] The UE receives downlink SDAP packets, the packet header of which carries the QFI field and the RQI field.

[0199] If a downlink data packet with RQI set or RQI=1 is received, the UE starts a timer.

[0200] The timer is used to control the UE to derive QoS or resolve the RQI field.

[0201] The timer is configured by the core network device or the access network device (if configured by the core network device, it can be configured via NAS signaling, such as by carrying the NAS signaling during the PDU session establishment process. Optionally, if the NAS signaling is not carried, it can be assumed that no timer is configured, and thus no timer is used for RQI control; alternatively, a timer-based RQI control mechanism can still be used with the timer's duration set to the default value).

[0202] The UE maintains a timer. Optionally, the UE will no longer derive QoS or resolve the RQI field before the timer expires.

[0203] Furthermore, if the timer is maintained by the UE AS, the UE will no longer parse the RQI field of the same QFI, and / or will not indicate RQI or RQI enable information to the UE NAS for that QFI.

[0204] Furthermore, if the timer is maintained in the UE NAS, the UE will no longer derive QoS rules for that QFI.

[0205] For example, during the execution of a timer for QFI x, if the UE receives a new DL SDAP packet with an SDAP header or an RQI field in the header, and the QFI in the header matches QFI x, the UE does not infer QoS rules or parse the RQI field.

[0206] For example, if the timer for QFI x is not enabled, or if the UE receives a DL SDAP packet for the first time, and the packet has an SDAP header or an RQI header, and the QFI of the packet matches QFI x, then the UE infers the QoS rules or parses the RQI field, and / or the UE enables the timer.

[0207] If the timer times out or is not running, the UE derives QoS rules or parses the RQI domain.

[0208] Furthermore, if the timer is maintained by the UE AS, the UE resolves the RQI field of the same QFI, and / or indicates RQI or RQI enable information to the UE NAS for that QFI.

[0209] Furthermore, if the timer is maintained in the UE NAS, the UE infers QoS rules for that QFI.

[0210] For example, if the timer for QFI x is not running, and the UE receives a new DL SDAP packet with an SDAP header or an RQI field, and the QFI of the packet matches QFI x, the UE infers the QoS or resolves the RQI field, and / or the UE starts the timer corresponding to that QFI.

[0211] Optionally, the network device maintains a corresponding timer. If the UE AS maintains a timer, the access network device can maintain a corresponding timer and / or generate or indicate the corresponding RQI in the DL SDAP packet header.

[0212] For example, for a QoS flow with RQI enabled, if the timer is not running, the access network device will set RQI to 1. Conversely, for a QoS flow with RQI enabled, if the timer is running, the access network device will set RQI to 0.

[0213] The DL SDAP packet mentioned above can be formatted as shown in Figure 2, for example.

[0214] If two types of QoS flows exist simultaneously within the UE, one is a QoS flow with timer-based RQI mechanism enabled, and the other is a QoS flow with timer-based RQI mechanism disabled (such as a QoS flow that supports the RQI mechanism provided by relevant technologies (case 1), or a QoS flow that does not support the RQI mechanism (case 2)), then the following two options can exist for different types of QoS flows.

[0215] Option 1: Map different types of QoS flows to different DRBs (for case 1 and case 2).

[0216] Optionally, option 1 can be implemented based on network device configuration, such as RRC configuration.

[0217] Option 2: Different types of QoS flows can be mapped to a DRB, and the UE determines the behavior to be performed based on QFI (for case 2).

[0218] Optionally, the distinction of QFI behavior is implemented based on the configuration or instructions of the network device.

[0219] Example 2

[0220] Example 2 introduces a QFI-level QoS mechanism. For example, Example 2 may include the following two options.

[0221] Option 1: For a specific QFI, use a new DL SDAP header that does not carry the RQI field; or, for a specific QFI, although using the DL SDAP header provided by the relevant technology, the UE performs a first action (e.g., the UE does not parse the RQI field in the SDAP header, or the UE does not autonomously derive QoS rules, or the UE AS does not indicate the RQI to the UE NAS).

[0222] Option 2: For a specific QFI, disable RQI, or configure the SDAP header not to appear in the data packets corresponding to that QFI.

[0223] The following provides a more detailed example of Example 2.

[0224] The UE executes a QFI-level QoS mechanism. For example, this mechanism may include one or more of the following aspects.

[0225] The activation or enablement of this mechanism is controlled by the core network equipment or access network equipment, and / or the control information for activating or enabling the mechanism is carried via NAS signaling, or RRC signaling, or SDAP control PDU, or MAC CE or DCI. Optionally, the control information for activating or enabling the mechanism is for the UE, or is for a QoS flow (correspondingly, carrying a PDU session and / or QFI to indicate the corresponding QoS flow or QoS flow list).

[0226] The specific QFIs are notified to the UE by the core network equipment or access network equipment.

[0227] For specific QFIs, a new DL SDAP header is used, which does not carry the RQI field.

[0228] For this QFI, the UE updates the QoS rules for the corresponding QFI based on the QoS rules provided by the SMF.

[0229] For example, the format of a DL SDAP packet can be as shown in Figure 4 or Figure 5.

[0230] Alternatively, for a specific QFI, although the DL SDAP header provided by the relevant technology can continue to be used, the UE performs the first action (such as the UE not parsing the RQI field in the SDAP header, or the UE not independently deriving QoS rules, or the UE AS not indicating the RQI to the UE NAS).

[0231] The UE receives SDAP DL data packets, the header of which carries at least the QFI field.

[0232] If the QFI is a specific QFI, the UE performs the first action (including at least one of the following: the UE does not parse the RQI field in the SDAP packet header, the UE does not deduce the QoS rules independently, the UE AS does not indicate the RQI to the UE NAS, and the UE updates the QoS rules for the corresponding QFI based on the QoS rules provided by the SMF).

[0233] For example, the UE AS does not parse the RQI field in the SDAP header, and / or the UE AS does not indicate the RQI to the UE NAS (furthermore, the UE AS also does not indicate the RQI to the UE NAS when RQI=1).

[0234] For example, UE NAS does not autonomously derive QoS rules.

[0235] If the QFI is not a specific QFI, the UE can perform relevant actions according to relevant technologies (the UE parses the RQI field in the SDAP packet header, or the UE autonomously derives QoS rules, or if RQI=1, the UE AS indicates the RQI to the UE NAS). For example, the format of the SDAP DL packet can be as shown in Figure 2.

[0236] If there is a coexistence situation, such as two types of QoS flows existing within the UE at the same time, one is a QoS flow with QFI-level QoS enabled, and the other is a QoS flow with QFI-level QoS not enabled (such as a QoS flow that supports the RQI mechanism provided by relevant technologies (case 1), or a QoS flow that does not support the RQI mechanism (case 2)), then the following two options can exist for different types of QoS flows.

[0237] Option 1: Map different types of QoS flows to different DRBs (for case 1 and case 2). Optionally, implement alt1 based on network configuration, such as RRC configuration.

[0238] Option 2: Different types of QoS flows can be mapped to a DRB, and the UE determines the behavior to be performed based on QFI (for case 2). Optionally, the distinction of QFI behavior is based on network configuration or indication.

[0239] The method embodiments of this application have been described in detail above with reference to Figures 1 to 7. The apparatus embodiments of this application will be described in detail below with reference to Figures 8 to 11. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments. Therefore, any parts not described in detail can be referred to the foregoing method embodiments.

[0240] Figure 8 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 800 shown in Figure 8 can be the first terminal device mentioned above. The communication device 800 may include a determining unit 810. The determining unit 810 is used to determine whether to perform or not to perform a first reflection mapping quality of service indication (RQI) related operation for a first quality of service (QoS) flow or a first data packet.

[0241] In some embodiments, the first RQI-related operation includes one or more of the following: obtaining RQI from the first data packet or the data packet of the first QoS stream; deriving QoS rules based on the RQI in the first data packet or the data packet of the first QoS stream; indicating the RQI in the first data packet or the data packet of the first QoS stream to the Non-Access Stratum (NAS) of the first terminal device; indicating to the NAS of the first terminal device to update or derive the mapping rules from Service Data Flow SDF to QoS stream; ignoring or skipping the RQI field in the first data packet or the data packet of the first QoS stream; ignoring the derived mapping rules from SDF to QoS stream; maintaining the current mapping rules from SDF to QoS stream; updating or deriving the mapping rules from SDF to QoS stream; starting or restarting a first timer, the first timer being used to control whether the first RQI-related operation is performed; and parsing the header of the first data packet or the data packet of the first QoS stream using a first header format, the first header format not including the RQI field.

[0242] In some embodiments, the determining unit 810 is configured to: determine whether to perform or not perform the first RQI-related operation according to a first rule; wherein the first rule is associated with one or more of the following: a first timer, the first timer being used to control whether to perform or not perform the first RQI-related operation; identification information of one or more QoS flows, the one or more QoS flows being used to perform the first RQI-related operation, or the identification information being used to determine whether to perform or not perform the first RQI-related operation; information in the first data packet, the information in the first data packet being used to determine whether to perform or not perform the first RQI-related operation.

[0243] In some embodiments, the determining unit 810 is configured to: determine whether to perform or not perform the first RQI-related operation according to the first rule when a first condition is met; wherein the first condition is related to one or more of the following: a first capability, the first capability being used to indicate whether the first terminal device supports or does not support the first rule; receiving first information sent by a network device, the first information being used to configure the first rule, instructing the first terminal device to enable the first rule, or instructing the configuration of the first rule or the first RQI-related operation.

[0244] In some embodiments, the first information satisfies one or more of the following: the first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer; the first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer; the first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of the one or more QoS flows; the first information is used to configure the first terminal device to perform or not perform the first RQI-related operation; the first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule; the first information is used to configure or instruct the QoS flow, radio bearer, media access control MAC entity, or terminal device that performs the first RQI-related operation; the first information is used to configure or instruct the QoS flow, radio bearer, media access control MAC entity, or terminal device that performs the first RQI-related operation; the first information is used to configure or instruct the QoS flow, radio bearer, media access control MAC entity, or terminal device that performs the first RQI-related operation based on the first rule. The first information is used to explicitly or implicitly instruct the first terminal device to perform or not perform the first RQI-related operation based on the first rule; the first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule; the first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule; the first information is used to configure the first timer; the first information is used to configure the one or more QoS flows; the first information is used to configure the QoS flow corresponding to the first timer; the first information is used to activate or use a first header format to parse the header of a data packet; the first information is used to activate or configure a first header format; wherein, the first header format does not include the RQI field.

[0245] In some embodiments, the first information is information for the first terminal device; or, the first information is information for a QoS flow; or, the first information is information for a MAC entity; or, the first information is information for a radio bearer.

[0246] In some embodiments, the first information is information sent by an access network device or a core network device.

[0247] In some embodiments, the first information is carried in NAS signaling, RRC signaling, SDAP control PDU, MAC CE, DCI, or control signaling of a first protocol layer.

[0248] In some embodiments, the first rule includes one or more of the following: if the first timer is running, the first terminal device performs some or all of the operations in the first RQI-related operation; if the first timer is not started or times out, the first terminal device does not perform some or all of the operations in the first RQI-related operation; if the first QoS flow belongs to one or more QoS flows, the first terminal device performs some or all of the operations in the first RQI-related operation; if the first QoS flow does not belong to one or more QoS flows, the first terminal device does not perform some or all of the operations in the first RQI-related operation.

[0249] In some embodiments, the communication device 800 further includes: a startup unit, configured to start the first timer if the RQI value in the first data packet or the data packet of the first QoS stream is a first value when the first timer is not started.

[0250] In some embodiments, the first RQI-related operation is an operation on the first QoS flow or an operation on data packets of the first QoS flow; or, the first RQI-related operation is an operation on the QoS flow corresponding to the first timer or an operation on data packets of the QoS flow corresponding to the first timer; or, the first RQI-related operation is an operation on the QoS flow determined based on first information sent by the network device, or an operation on data packets in the QoS flow determined based on the first information sent by the network device, wherein the first information is used to configure the first rule, instruct the first terminal device to enable the first rule, or instruct the relevant configuration of the first rule or the first RQI-related operation; or, the first RQI-related operation is an operation on any QoS flow currently being performed by the first terminal device, or an operation on data packets of any QoS flow currently being performed by the first terminal device.

[0251] In some embodiments, one or more of the following are satisfied: the first timer is configured by the access network device or the core network device; the first timer is activated by the access network device or the core network device; the first timer is maintained by the access network device and / or the first terminal device; the timing duration of the first timer is default, predefined, or configured by the access network device or the core network device; enabling or disabling the first timer is configured or indicated by the access network device or the core network device; the one or more QoS flows are configured by the access network device or the core network device; the first rule is configured by the access network device or the core network device; enabling or disabling the first rule is indicated by the access network device or the core network device; the QoS flows, radio bearers, MAC entities, and terminal devices performing the first RQI-related operations are configured or indicated by the access network device or the core network device; the QoS flows, radio bearers, MAC entities, and terminal devices performing the first rule are configured or indicated by the access network device or the core network device.

[0252] In some embodiments, the second QoS flow is a specific QoS flow; or, the second QoS flow is a QoS flow determined based on first information sent by the network device, the first information being used to configure the first rule, instructing the first terminal device to enable the first rule, or instructing the relevant configuration of the first rule or the first RQI-related operation; or, the second QoS flow is any QoS flow currently being used by the first terminal device; wherein, the second QoS flow includes one or more of the following: the first QoS flow; the one or more QoS flows; the QoS flow containing the first data packet; the QoS flow corresponding to the first timer.

[0253] In some embodiments, the data packets of the second QoS flow satisfy one of the following: carrying QFI and carrying RQI; carrying QFI but not carrying RQI; not carrying QFI and not carrying RQI; wherein the second QoS flow includes one or more of the following: the first QoS flow; the one or more QoS flows.

[0254] In some embodiments, the data packets of the second QoS flow satisfy one of the following: including a first header, wherein the first header carries QFI but not RQI; including a first header, wherein the first header carries both QFI and RQI; excluding the first header; wherein the second QoS flow includes one or more of the following: the first QoS flow; the one or more QoS flows.

[0255] In some embodiments, the first terminal device is configured to receive one or more of the following: a first type of QoS flow, wherein the first type of QoS flow is a QoS flow associated with the first rule or first information; a second type of QoS flow, wherein the second type of QoS flow is a QoS flow not associated with the first rule or first information; a first type of QoS flow, wherein the first type of QoS flow performs the first RQI-related operation; a second type of QoS flow, wherein the second type of QoS flow does not perform the first RQI-related operation; a first type of data packet, wherein the first type of data packet is a data packet in a specific QoS flow that performs the first RQI-related operation; a second type of data packet, wherein the second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation; a first type of data packet, wherein the first type of data packet is a data packet in a specific QoS flow associated with the first rule or first information; a second type of data packet, wherein the second type of data packet is a data packet in a specific QoS flow not associated with the first rule or first information; wherein the first information is used to configure the first rule, instructing the first terminal device to enable the first rule, or instructing the relevant configuration of the first rule or the first RQI-related operation.

[0256] In some embodiments, the first type of QoS stream and the second type of QoS stream are mapped to the same data radio bearer; or, the first type of QoS stream and the second type of QoS stream are mapped to different data radio bearers; or, the first type of data packet and the second type of data packet are transmitted through the same data radio bearer; or, the first type of data packet and the second type of data packet are transmitted through different data radio bearers.

[0257] In some embodiments, the first type of QoS flow includes one or more of the following: the first QoS flow, the one or more QoS flows, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

[0258] Figure 9 is a schematic diagram of the structure of a communication device provided in another embodiment of this application. The communication device 900 shown in Figure 9 can be the access network device mentioned above. The communication device 900 includes a communication unit 910. The communication unit 910 is used to send first information to a first terminal device; wherein, the first information is used to configure a first rule, instructing the first terminal device to enable the first rule, and instructing the relevant configuration of the first rule or the first reflection mapping service quality indication RQI related operation; wherein, the first rule is used by the first terminal device to determine whether to perform or not perform the first RQI related operation for a first data packet or a first data stream.

[0259] In some embodiments, the first RQI-related operation includes one or more of the following: obtaining RQI from the first data packet or the data packet of the first Quality of Service (QoS) stream; deriving QoS rules based on the RQI in the first data packet or the data packet of the first QoS stream; indicating the RQI in the first data packet or the data packet of the first QoS stream to the Non-Access Stratum (NAS) of the first terminal device; indicating to the NAS of the first terminal device to update or derive the mapping rules from Service Data Flow (SDF) to QoS stream; ignoring or skipping the RQI field in the first data packet or the data packet of the first QoS stream; ignoring the derived SDF to QoS stream mapping rules; maintaining the current SDF to QoS stream mapping rules; updating or deriving the SDF to QoS stream mapping rules; starting or restarting a first timer, the first timer being used to control whether the first RQI-related operation is performed; and parsing the header of the first data packet or the data packet of the first QoS stream using a first header format, the first header format not including the RQI field.

[0260] In some embodiments, the first rule is associated with one or more of the following: a first timer, the first timer being used to control whether or not the first RQI-related operation is performed; identification information of one or more QoS flows, the one or more QoS flows being used to perform the first RQI-related operation, or the identification information being used to determine whether or not the first RQI-related operation is performed; and information in the first data packet, the information in the first data packet being used to determine whether or not the first RQI-related operation is performed.

[0261] In some embodiments, the first rule is enabled when a first condition is met, the first condition being related to one or more of the following: a first capability, the first capability being used to indicate whether the first terminal device supports or does not support the first rule; and the access network device sending the first information to the first terminal device.

[0262] In some embodiments, the first information satisfies one or more of the following: the first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer; the first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer; the first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of the one or more QoS flows; the first information is used to configure the first terminal device to perform or not perform the first RQI-related operation; the first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule; the first information is used to configure or instruct the QoS flow, radio bearer, media access control MAC entity, or terminal device that performs the first RQI-related operation; the first information is used to configure or instruct the QoS flow, radio bearer, media access control MAC entity, or terminal device that performs the first RQI-related operation; the first information is used to configure or instruct the QoS flow, radio bearer, media access control MAC entity, or terminal device that performs the first RQI-related operation based on the first rule. The first information is used to explicitly or implicitly instruct the first terminal device to perform or not perform the first RQI-related operation based on the first rule; the first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule; the first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule; the first information is used to configure the first timer; the first information is used to configure the one or more QoS flows; the first information is used to configure the QoS flow corresponding to the first timer; the first information is used to activate or use a first header format to parse the header of a data packet; the first information is used to activate or configure a first header format; wherein, the first header format does not include the RQI field.

[0263] In some embodiments, the first information is information for the first terminal device; or, the first information is information for a QoS flow; or, the first information is information for a MAC entity; or, the first information is information for a radio bearer.

[0264] In some embodiments, the first rule includes one or more of the following: if the first timer is running, the first terminal device performs some or all of the operations in the first RQI-related operation; if the first timer is not started or times out, the first terminal device does not perform some or all of the operations in the first RQI-related operation; if the first QoS flow belongs to one or more QoS flows, the first terminal device performs some or all of the operations in the first RQI-related operation; if the first QoS flow does not belong to one or more QoS flows, the first terminal device does not perform some or all of the operations in the first RQI-related operation.

[0265] In some embodiments, if the RQI value in the first data packet or the data packet of the first QoS stream is a first value when the first timer is not started, then the first timer is started.

[0266] In some embodiments, the first RQI-related operation is an operation on the first QoS stream or an operation on the data packets of the first QoS stream; or, the first RQI-related operation is an operation on the QoS stream corresponding to the first timer or an operation on the data packets of the QoS stream corresponding to the first timer; or, the first RQI-related operation is an operation on the QoS stream determined based on the first information, or an operation on the data packets in the QoS stream determined based on the first information; or, the first RQI-related operation is an operation on any QoS stream currently being run by the first terminal device, or an operation on the data packets of any QoS stream currently being run by the first terminal device.

[0267] In some embodiments, one or more of the following are satisfied: the first timer is configured by the access network device; the first timer is activated by the access network device; the first timer is maintained by the access network device and / or the first terminal device; the timing duration of the first timer is default, predefined, or configured by the access network device; enabling or disabling the first timer is configured or indicated by the access network device; the one or more QoS flows are configured by the access network device; the QoS flows, radio bearers, MAC entities, and terminal devices performing the first RQI-related operations are configured or indicated by the access network device; the QoS flows, radio bearers, MAC entities, and terminal devices performing the first rule are configured or indicated by the access network device.

[0268] In some embodiments, the second QoS flow is a specific QoS flow; or, the second QoS flow is a QoS flow determined based on the first information; or, the second QoS flow is any QoS flow currently being used by the first terminal device; wherein, the second QoS flow includes one or more of the following: the first QoS flow; the one or more QoS flows; the QoS flow containing the first data packet; the QoS flow corresponding to the first timer.

[0269] In some embodiments, the data packets of the second QoS flow satisfy one of the following: carrying QFI and carrying RQI; carrying QFI but not carrying RQI; not carrying QFI and not carrying RQI; wherein the second QoS flow includes one or more of the following: the first QoS flow; the one or more QoS flows.

[0270] In some embodiments, the data packets of the second QoS flow satisfy one of the following: including a first header, wherein the first header carries QFI but not RQI; including a first header, wherein the first header carries both QFI and RQI; excluding the first header; wherein the second QoS flow includes one or more of the following: the first QoS flow; the one or more QoS flows.

[0271] In some embodiments, the first terminal device is configured to receive one or more of the following: a first type of QoS flow, wherein the first type of QoS flow is a QoS flow associated with the first rule or the first information; a second type of QoS flow, wherein the second type of QoS flow is a QoS flow not associated with the first rule or the first information; a first type of QoS flow, wherein the first type of QoS flow performs the first RQI-related operation; a second type of QoS flow, wherein the second type of QoS flow does not perform the first RQI-related operation; a first type of data packet, wherein the first type of data packet is a data packet in a specific QoS flow that performs the first RQI-related operation; a second type of data packet, wherein the second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation; a first type of data packet, wherein the first type of data packet is a data packet in a specific QoS flow associated with the first rule or the first information; and a second type of data packet, wherein the second type of data packet is a data packet in a specific QoS flow not associated with the first rule or the first information.

[0272] In some embodiments, the first type of QoS stream and the second type of QoS stream are mapped to the same data radio bearer; or, the first type of QoS stream and the second type of QoS stream are mapped to different data radio bearers; or, the first type of data packet and the second type of data packet are transmitted through the same data radio bearer; or, the first type of data packet and the second type of data packet are transmitted through different data radio bearers.

[0273] In some embodiments, the first type of QoS flow includes one or more of the following: the first QoS flow, the one or more QoS flows, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

[0274] In some embodiments, the first information is information sent by the access network device.

[0275] In some embodiments, the first information is carried in RRC signaling, SDAP control PDU, MAC CE, DCI, or control signaling of the first protocol layer.

[0276] Figure 10 is a schematic diagram of the structure of a communication device provided in another embodiment of this application. The communication device 1000 shown in Figure 10 can be the core network device mentioned above. The communication device 1000 includes a communication unit 1010. The communication unit 1010 is used to send first information to a first terminal device; wherein, the first information is used to configure a first rule, instructing the first terminal device to enable the first rule, and instructing the configuration of the first rule or the first RQI related operation; wherein, the first rule is used by the first terminal device to determine whether to execute or not execute the first RQI related operation for a first data packet or a first data stream.

[0277] In some embodiments, the first RQI-related operation includes one or more of the following: obtaining RQI from the first data packet or the data packet of the first Quality of Service (QoS) stream; deriving QoS rules based on the RQI in the first data packet or the data packet of the first QoS stream; indicating the RQI in the first data packet or the data packet of the first QoS stream to the Non-Access Stratum (NAS) of the first terminal device; indicating to the NAS of the first terminal device to update or derive the mapping rules from Service Data Flow (SDF) to QoS stream; ignoring or skipping the RQI field in the first data packet or the data packet of the first QoS stream; ignoring the derived SDF to QoS stream mapping rules; maintaining the current SDF to QoS stream mapping rules; updating or deriving the SDF to QoS stream mapping rules; starting or restarting a first timer, the first timer being used to control whether the first RQI-related operation is performed; and parsing the header of the first data packet or the data packet of the first QoS stream using a first header format, the first header format not including the RQI field.

[0278] In some embodiments, the first rule is associated with one or more of the following: a first timer, the first timer being used to control whether or not the first RQI-related operation is performed; identification information of one or more QoS flows, the one or more QoS flows being used to perform the first RQI-related operation, or the identification information being used to determine whether or not the first RQI-related operation is performed; and information in the first data packet, the information in the first data packet being used to determine whether or not the first RQI-related operation is performed.

[0279] In some embodiments, the first rule is enabled when a first condition is met, the first condition being related to one or more of the following: a first capability, the first capability being used to indicate whether the first terminal device supports or does not support the first rule; the core network device sending the first information to the first terminal device.

[0280] In some embodiments, the first information satisfies one or more of the following: the first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer; the first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer; the first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of the one or more QoS flows; the first information is used to configure the first terminal device to perform or not perform the first RQI-related operation; the first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule; the first information is used to configure or instruct the QoS flow, radio bearer, media access control MAC entity, or terminal device that performs the first RQI-related operation; the first information is used to configure or instruct the QoS flow, radio bearer, media access control MAC entity, or terminal device that performs the first RQI-related operation; the first information is used to configure or instruct the QoS flow, radio bearer, media access control MAC entity, or terminal device that performs the first RQI-related operation based on the first rule. The first information is used to explicitly or implicitly instruct the first terminal device to perform or not perform the first RQI-related operation based on the first rule; the first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule; the first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule; the first information is used to configure the first timer; the first information is used to configure the one or more QoS flows; the first information is used to configure the QoS flow corresponding to the first timer; the first information is used to activate or use a first header format to parse the header of a data packet; the first information is used to activate or configure a first header format; wherein, the first header format does not include the RQI field.

[0281] In some embodiments, the first information is information for the first terminal device; or, the first information is information for a QoS flow; or, the first information is information for a MAC entity; or, the first information is information for a radio bearer.

[0282] In some embodiments, the first rule includes one or more of the following: if the first timer is running, the first terminal device performs some or all of the operations in the first RQI-related operation; if the first timer is not started or times out, the first terminal device does not perform some or all of the operations in the first RQI-related operation; if the first QoS flow belongs to one or more QoS flows, the first terminal device performs some or all of the operations in the first RQI-related operation; if the first QoS flow does not belong to one or more QoS flows, the first terminal device does not perform some or all of the operations in the first RQI-related operation.

[0283] In some embodiments, if the RQI value in the first data packet or the data packet of the first QoS stream is a first value when the first timer is not started, then the first timer is started.

[0284] In some embodiments, the first RQI-related operation is an operation on the first QoS stream or an operation on the data packets of the first QoS stream; or, the first RQI-related operation is an operation on the QoS stream corresponding to the first timer or an operation on the data packets of the QoS stream corresponding to the first timer; or, the first RQI-related operation is an operation on the QoS stream determined based on the first information, or an operation on the data packets in the QoS stream determined based on the first information; or, the first RQI-related operation is an operation on any QoS stream currently being run by the first terminal device, or an operation on the data packets of any QoS stream currently being run by the first terminal device.

[0285] In some embodiments, one or more of the following are satisfied: the first timer is configured by the core network device; the first timer is activated by the core network device; the first timer is maintained in the core network; the timing duration of the first timer is default, predefined, or configured by the core network device; enabling or disabling the first timer is configured or indicated by the core network device; the one or more QoS flows are configured by the core network device; the QoS flows, radio bearers, MAC entities, and terminal devices performing the first RQI-related operations are configured or indicated by the core network device; the QoS flows, radio bearers, MAC entities, and terminal devices performing the first rule are configured or indicated by the core network device.

[0286] In some embodiments, the second QoS flow is a specific QoS flow; or, the second QoS flow is a QoS flow determined based on the first information; or, the second QoS flow is any QoS flow currently being used by the first terminal device; wherein, the second QoS flow includes one or more of the following: the first QoS flow; the one or more QoS flows; the QoS flow containing the first data packet; the QoS flow corresponding to the first timer.

[0287] In some embodiments, the data packets of the second QoS flow satisfy one of the following: carrying QFI and carrying RQI; carrying QFI but not carrying RQI; not carrying QFI and not carrying RQI; wherein the second QoS flow includes one or more of the following: the first QoS flow; the one or more QoS flows.

[0288] In some embodiments, the data packets of the second QoS flow satisfy one of the following: including a first header, wherein the first header carries QFI but not RQI; including a first header, wherein the first header carries both QFI and RQI; excluding the first header; wherein the second QoS flow includes one or more of the following: the first QoS flow; the one or more QoS flows.

[0289] In some embodiments, the first terminal device is configured to receive one or more of the following: a first type of QoS flow, wherein the first type of QoS flow is a QoS flow associated with the first rule or the first information; a second type of QoS flow, wherein the second type of QoS flow is a QoS flow not associated with the first rule or the first information; a first type of QoS flow, wherein the first type of QoS flow performs the first RQI-related operation; a second type of QoS flow, wherein the second type of QoS flow does not perform the first RQI-related operation; a first type of data packet, wherein the first type of data packet is a data packet in a specific QoS flow that performs the first RQI-related operation; a second type of data packet, wherein the second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation; a first type of data packet, wherein the first type of data packet is a data packet in a specific QoS flow associated with the first rule or the first information; and a second type of data packet, wherein the second type of data packet is a data packet in a specific QoS flow not associated with the first rule or the first information.

[0290] In some embodiments, the first type of QoS stream and the second type of QoS stream are mapped to the same data radio bearer; or, the first type of QoS stream and the second type of QoS stream are mapped to different data radio bearers; or, the first type of data packet and the second type of data packet are transmitted through the same data radio bearer; or, the first type of data packet and the second type of data packet are transmitted through different data radio bearers.

[0291] In some embodiments, the first type of QoS flow includes one or more of the following: the first QoS flow, the one or more QoS flows, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

[0292] In some embodiments, the first information is information sent by the core network device.

[0293] In some embodiments, the first information is carried in NAS signaling.

[0294] Figure 11 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 11 indicate that the unit or module is optional. This device 1100 can be used to implement the methods described in the above method embodiments. Device 1100 can be a chip, a terminal device, or a network device.

[0295] Apparatus 1100 may include one or more processors 1110. The processor 1110 may support apparatus 1100 in implementing the methods described in the preceding method embodiments. The processor 1110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0296] The apparatus 1100 may further include one or more memories 1120. The memories 1120 store a program that can be executed by the processor 1110, causing the processor 1110 to perform the methods described in the preceding method embodiments. The memories 1120 may be independent of the processor 1110 or integrated within the processor 1110.

[0297] The device 1100 may also include a transceiver 1130. The processor 1110 can communicate with other devices or chips via the transceiver 1130. For example, the processor 1110 can send and receive data with other devices or chips via the transceiver 1130.

[0298] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0299] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0300] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.

[0301] It should be understood that the terminology used in this application is only for interpreting specific embodiments of the application and is not intended to limit the application. The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a particular order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0302] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0303] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0304] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0305] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0306] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0307] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0308] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0309] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0310] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0311] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0312] 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 instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted 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 that a computer can read 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., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0313] The above description is merely a specific embodiment of this application, but the scope of protection of this application 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 application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: For a first Quality of Service (QoS) stream or a first data packet, the first terminal device determines whether to perform or not to perform the first Reflection Mapping Quality of Service Indication (RQI) related operation.

2. The method according to claim 1, characterized in that, The first RQI-related operation includes one or more of the following: Obtain the RQI from the first data packet or the data packet of the first QoS stream; Deduce QoS rules based on RQI in the first data packet or the data packet of the first QoS stream; Indicate the RQI in the first data packet or the data packet of the first QoS stream to the non-access stratum NAS of the first terminal device; Instruct the NAS of the first terminal device to update or derive the mapping rules from service data stream SDF to QoS stream; Ignore or skip the RQI field in the first data packet or the data packet of the first QoS stream; Ignore the rules for deriving the SDF to QoS flow mapping; Maintain the current SDF to QoS flow mapping rules; Update or derive the SDF to QoS flow mapping rules; Start or restart the first timer, which is used to control whether or not the first RQI-related operation is executed; The header of the first data packet or the data packet of the first QoS flow is parsed using a first header format, wherein the first header format does not include the RQI field.

3. The method according to claim 1 or 2, characterized in that, The first terminal device determines whether to perform or not perform the first RQI-related operation, including: The first terminal device determines whether to perform or not to perform the first RQI-related operation according to the first rule; The first rule is related to one or more of the following: A first timer is used to control whether or not the first RQI-related operation is executed; The identification information of one or more QoS flows, wherein the one or more QoS flows are used to perform the first RQI-related operation, or the identification information is used to determine whether to perform or not perform the first RQI-related operation; The information in the first data packet is used to determine whether or not to perform the first RQI-related operation.

4. The method according to claim 3, characterized in that, The first terminal device determines whether to perform or not perform the first RQI-related operation according to the first rule, including: If the first condition is met, the first terminal device determines whether to perform or not to perform the first RQI-related operation according to the first rule; The first condition is related to one or more of the following: A first capability, wherein the first capability is used to indicate whether the first terminal device supports or does not support the first rule; The system receives first information sent by a network device. The first information is used to configure the first rule, instructing the first terminal device to enable the first rule, or instructing the configuration of the first rule or the first RQI-related operation.

5. The method according to claim 4, characterized in that, The first information satisfies one or more of the following: The first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of the one or more QoS flows; The first information is used to configure the first terminal device to perform or not perform the first RQI-related operation; The first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule; The first information is used to configure or instruct the QoS stream, radio bearer, media access control MAC entity or terminal device that performs the first RQI-related operation; The first information is used to configure or indicate the QoS flow, radio bearer, MAC entity, or terminal device that performs the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule; The first information is used to configure the first timer; The first information is used to configure the one or more QoS flows; The first information is used to configure the QoS flow corresponding to the first timer; The first information is used to activate or instruct the parsing of the packet header using the first header format; The first information is used to activate or configure the first packet header format; The first header format does not include the RQI field.

6. The method according to claim 4 or 5, characterized in that: The first information is information specific to the first terminal device; or... The first information is information specific to QoS flows; or, The first information pertains to MAC entities; or, The first piece of information pertains to the wireless bearer.

7. The method according to any one of claims 4 to 6, characterized in that, The first information is information sent by the access network device or the core network device.

8. The method according to claim 7, characterized in that, The first information is carried in NAS signaling, Radio Resource Control (RRC) signaling, Service Data Adaptation Protocol (SDAP) Control Protocol Data Unit (PDU), Media Access Control (MAC) Control Element (CE), Downlink Control Information (DCI), or control signaling of the first protocol layer.

9. The method according to any one of claims 3 to 8, characterized in that, The first rule includes one or more of the following: If the first timer is running, the first terminal device executes some or all of the operations in the first RQI-related operation; If the first timer is not started or times out, the first terminal device will not perform some or all of the operations in the first RQI related operation; If the first QoS flow belongs to one or more QoS flows, the first terminal device performs some or all of the operations in the first RQI-related operation; If the first QoS flow does not belong to the one or more QoS flows, the first terminal device does not perform some or all of the operations in the first RQI related operation.

10. The method according to any one of claims 3 to 9, characterized in that, The method further includes: If the RQI value in the first data packet or the data packet of the first QoS stream is a first value when the first timer is not started, the first terminal device starts the first timer.

11. The method according to any one of claims 3 to 10, characterized in that: The first RQI-related operation is an operation on the first QoS stream or an operation on the data packets of the first QoS stream; or, The first RQI-related operation is an operation on the QoS stream corresponding to the first timer or an operation on the data packets of the QoS stream corresponding to the first timer; or, The first RQI-related operation is an operation for a QoS flow determined based on the first information sent by the network device, or an operation for data packets in a QoS flow determined based on the first information sent by the network device. The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, or instruct the configuration of the first rule or the first RQI-related operation. or, The first RQI-related operation is an operation on any QoS flow of the first terminal device at present, or an operation on data packets of any QoS flow of the first terminal device at present.

12. The method according to any one of claims 3 to 11, characterized in that, One or more of the following are satisfied: The first timer is configured by the access network device or the core network device; The first timer is activated by the access network device or the core network device; The first timer is maintained by the access network device and / or the first terminal device; The timing duration of the first timer is either default, predefined, or configured by the access network device or the core network device. Whether the first timer is enabled or disabled is configured or indicated by the access network device or the core network device; The one or more QoS flows are configured by access network equipment or core network equipment; The first rule is configured by the access network device or the core network device; Whether the first rule is enabled or disabled is indicated by the access network device or the core network device. The QoS flow, radio bearer, MAC entity, and terminal device that perform the first RQI-related operation are configured or indicated by the access network device or core network device. The QoS flow, radio bearer, MAC entity, and terminal device that execute the first rule are configured or indicated by the access network device or core network device.

13. The method according to any one of claims 3 to 12, characterized in that: The second QoS flow is a specific QoS flow; or, The second QoS flow is a QoS flow determined based on the first information sent by the network device. The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, or instruct the relevant configuration of the first rule or the first RQI related operation. or, The second QoS stream is any QoS stream currently being used by the first terminal device; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows; The QoS stream in which the first data packet is located; The QoS stream corresponding to the first timer.

14. The method according to any one of claims 3 to 13, characterized in that, The packets of the second QoS stream satisfy one of the following: It carries the Quality of Service Flow Identifier (QFI) and the RQI. It carries QFI, but not RQI; It does not carry QFI, nor does it carry RQI; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

15. The method according to any one of claims 3 to 14, characterized in that, The packets of the second QoS stream satisfy one of the following: Includes a first packet header, and the first packet header carries QFI but not RQI; Includes a first header, and the first header carries QFI and RQI; Excluding the first pack head; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

16. The method according to any one of claims 3 to 15, characterized in that, The first terminal device is configured to receive one or more of the following: The first type of QoS flow is a QoS flow associated with the first rule or the first information; The second type of QoS flow is a QoS flow that is not associated with the first rule or the first information; The first type of QoS flow is the QoS flow that performs the first RQI-related operation; The second type of QoS flow is a QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet that performs the first RQI-related operation in a specific QoS flow; The second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet associated with the first rule or the first information in a specific QoS flow; The second type of data packet is a data packet in a specific QoS flow that is not associated with the first rule or the first information; The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, or instruct the configuration of the first rule or the first RQI-related operation.

17. The method according to claim 16, characterized in that: The first type of QoS stream and the second type of QoS stream are mapped to the same data radio bearer; or, The first type of QoS stream and the second type of QoS stream are mapped to different data radio bearers; or, The first type of data packet and the second type of data packet are transmitted via the same data wireless bearer; or, The first type of data packet and the second type of data packet are transmitted through different data wireless bearers.

18. The method according to claim 16 or 17, characterized in that, The first type of QoS flow includes one or more of the following: the first QoS flow, the one or more QoS flows, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

19. A communication method, characterized in that, include: The access network device sends the first information to the first terminal device; The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, and instruct the configuration of the first rule or the first reflection mapping service quality indicator (RQI) related operations. The first rule is used by the first terminal device to determine whether to perform or not perform the first RQI-related operation for the first data packet or the first data stream.

20. The method according to claim 19, characterized in that, The first RQI-related operation includes one or more of the following: Obtain the RQI from the first data packet or the data packet of the first Quality of Service (QoS) stream; Deduce QoS rules based on RQI in the first data packet or the data packet of the first QoS stream; Indicate the RQI in the first data packet or the data packet of the first QoS stream to the non-access stratum NAS of the first terminal device; Instruct the NAS of the first terminal device to update or derive the mapping rules from service data stream SDF to QoS stream; Ignore or skip the RQI field in the first data packet or the data packet of the first QoS stream; Ignore the rules for deriving the SDF to QoS flow mapping; Maintain the current SDF to QoS flow mapping rules; Update or derive the SDF to QoS flow mapping rules; Start or restart the first timer, which is used to control whether or not the first RQI-related operation is executed; The header of the first data packet or the data packet of the first QoS flow is parsed using a first header format, wherein the first header format does not include the RQI field.

21. The method according to claim 19 or 20, characterized in that, The first rule is related to one or more of the following: A first timer is used to control whether or not the first RQI-related operation is executed; The identification information of one or more QoS flows, wherein the one or more QoS flows are used to perform the first RQI-related operation, or the identification information is used to determine whether to perform or not perform the first RQI-related operation; The information in the first data packet is used to determine whether or not to perform the first RQI-related operation.

22. The method according to claim 21, characterized in that, The first rule is activated when a first condition is met, which is related to one or more of the following: A first capability, wherein the first capability is used to indicate whether the first terminal device supports or does not support the first rule; The access network device sent the first information to the first terminal device.

23. The method according to claim 21 or 22, characterized in that, The first information satisfies one or more of the following: The first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of the one or more QoS flows; The first information is used to configure the first terminal device to perform or not perform the first RQI-related operation; The first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule; The first information is used to configure or instruct the QoS stream, radio bearer, media access control MAC entity or terminal device that performs the first RQI-related operation; The first information is used to configure or indicate the QoS flow, radio bearer, MAC entity, or terminal device that performs the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule; The first information is used to configure the first timer; The first information is used to configure the one or more QoS flows; The first information is used to configure the QoS flow corresponding to the first timer; The first information is used to activate or parse the header of the data packet using the first header format; The first information is used to activate or configure the first packet header format; The first header format does not include the RQI field.

24. The method according to claim 22 or 23, characterized in that: The first information is information specific to the first terminal device; or... The first information is information specific to QoS flows; or, The first information pertains to MAC entities; or, The first piece of information pertains to the wireless bearer.

25. The method according to any one of claims 21 to 24, characterized in that, The first rule includes one or more of the following: If the first timer is running, the first terminal device executes some or all of the operations in the first RQI-related operation; If the first timer is not started or times out, the first terminal device will not perform some or all of the operations in the first RQI related operation; If the first QoS flow belongs to one or more QoS flows, the first terminal device performs some or all of the operations in the first RQI-related operation; If the first QoS flow does not belong to the one or more QoS flows, the first terminal device does not perform some or all of the operations in the first RQI related operation.

26. The method according to any one of claims 21 to 25, characterized in that, If the RQI value in the first data packet or the data packet of the first QoS stream is the first value when the first timer is not started, then the first timer is started.

27. The method according to any one of claims 21 to 26, characterized in that: The first RQI-related operation is an operation on the first QoS stream or an operation on the data packets of the first QoS stream; or, The first RQI-related operation is an operation on the QoS stream corresponding to the first timer or an operation on the data packets of the QoS stream corresponding to the first timer; or, The first RQI-related operation is an operation on the QoS flow determined based on the first information, or an operation on data packets in the QoS flow determined based on the first information; or, The first RQI-related operation is an operation on any QoS flow of the first terminal device at present, or an operation on data packets of any QoS flow of the first terminal device at present.

28. The method according to any one of claims 21 to 27, characterized in that, One or more of the following are satisfied: The first timer is configured by the access network device; The first timer is activated by the access network device; The first timer is maintained by the access network device and / or the first terminal device; The timing duration of the first timer is either default, predefined, or configured by the access network device; The first timer may be enabled or disabled by the access network device; The one or more QoS flows are configured by the access network device; The QoS stream, radio bearer, MAC entity, and terminal device that perform the first RQI-related operation are configured or indicated by the access network device. The QoS flow, radio bearer, MAC entity, and terminal device that execute the first rule are configured or indicated by the access network device.

29. The method according to any one of claims 21 to 28, characterized in that: The second QoS flow is a specific QoS flow; or, The second QoS flow is the QoS flow determined based on the first information; or, The second QoS stream is any QoS stream currently being used by the first terminal device; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows; The QoS stream in which the first data packet is located; The QoS stream corresponding to the first timer.

30. The method according to any one of claims 21 to 29, characterized in that, The packets of the second QoS stream satisfy one of the following: It carries the Quality of Service Flow Identifier (QFI) and the RQI. It carries QFI, but not RQI; It does not carry QFI, nor does it carry RQI; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

31. The method according to any one of claims 21 to 30, characterized in that, The packets of the second QoS stream satisfy one of the following: Includes a first packet header, and the first packet header carries QFI but not RQI; Includes a first header, and the first header carries QFI and RQI; Excluding the first pack head; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

32. The method according to any one of claims 19 to 31, characterized in that, The first terminal device is configured to receive one or more of the following: The first type of QoS flow is a QoS flow associated with the first rule or the first information; The second type of QoS flow is a QoS flow that is not associated with the first rule or the first information; The first type of QoS flow is the QoS flow that performs the first RQI-related operation; The second type of QoS flow is a QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet that performs the first RQI-related operation in a specific QoS flow; The second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet in a specific QoS flow that is associated with the first rule or the first information; The second type of data packet is a data packet in a specific QoS flow that is not associated with the first rule or the first information.

33. The method according to claim 32, characterized in that: The first type of QoS stream and the second type of QoS stream are mapped to the same data radio bearer; or, The first type of QoS stream and the second type of QoS stream are mapped to different data radio bearers; or, The first type of data packet and the second type of data packet are transmitted via the same data wireless bearer; or, The first type of data packet and the second type of data packet are transmitted through different data wireless bearers.

34. The method according to claim 32 or 33, characterized in that, The first type of QoS flow includes one or more of the following: the first QoS flow, the one or more QoS flows, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

35. The method according to any one of claims 19 to 34, characterized in that, The first information is information sent by the access network device.

36. The method according to claim 35, characterized in that, The first information is carried in Radio Resource Control (RRC) signaling, Service Data Adaptation Protocol (SDAP) control PDU, Media Access Control (MAC) control element (CE), Downlink Control Information (DCI), or control signaling of the first protocol layer.

37. A communication method, characterized in that, include: The core network equipment sends the first information to the first terminal equipment; The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, and instruct the configuration of the first rule or the first reflection mapping service quality indicator (RQI) related operations. The first rule is used by the first terminal device to determine whether to perform or not perform the first RQI-related operation for the first data packet or the first data stream.

38. The method according to claim 37, characterized in that, The first RQI-related operation includes one or more of the following: Obtain the RQI from the first data packet or the data packet of the first Quality of Service (QoS) stream; Deduce QoS rules based on RQI in the first data packet or the data packet of the first QoS stream; Indicate the RQI in the first data packet or the data packet of the first QoS stream to the non-access stratum NAS of the first terminal device; Instruct the NAS of the first terminal device to update or derive the mapping rules from service data stream SDF to QoS stream; Ignore or skip the RQI field in the first data packet or the data packet of the first QoS stream; Ignore the rules for deriving the SDF to QoS flow mapping; Maintain the current SDF to QoS flow mapping rules; Update or derive the SDF to QoS flow mapping rules; Start or restart the first timer, which is used to control whether or not the first RQI-related operation is executed; The header of the first data packet or the data packet of the first QoS flow is parsed using a first header format, wherein the first header format does not include the RQI field.

39. The method according to claim 37 or 38, characterized in that, The first rule is related to one or more of the following: A first timer is used to control whether or not the first RQI-related operation is executed; The identification information of one or more QoS flows, wherein the one or more QoS flows are used to perform the first RQI-related operation, or the identification information is used to determine whether to perform or not perform the first RQI-related operation; The information in the first data packet is used to determine whether or not to perform the first RQI-related operation.

40. The method according to claim 39, characterized in that, The first rule is activated when a first condition is met, which is related to one or more of the following: A first capability, wherein the first capability is used to indicate whether the first terminal device supports or does not support the first rule; The core network device sent the first information to the first terminal device.

41. The method according to claim 39 or 40, characterized in that, The first information satisfies one or more of the following: The first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of the one or more QoS flows; The first information is used to configure the first terminal device to perform or not perform the first RQI-related operation; The first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule; The first information is used to configure or instruct the QoS stream, radio bearer, media access control MAC entity or terminal device that performs the first RQI-related operation; The first information is used to configure or indicate the QoS flow, radio bearer, MAC entity, or terminal device that performs the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule; The first information is used to configure the first timer; The first information is used to configure the one or more QoS flows; The first information is used to configure the QoS flow corresponding to the first timer; The first information is used to activate or parse the header of the data packet using the first header format; The first information is used to activate or configure the first packet header format; The first header format does not include the RQI field.

42. The method according to claim 40 or 41, characterized in that: The first information is information specific to the first terminal device; or... The first information is information specific to QoS flows; or, The first information pertains to MAC entities; or, The first piece of information pertains to the wireless bearer.

43. The method according to any one of claims 39 to 42, characterized in that, The first rule includes one or more of the following: If the first timer is running, the first terminal device executes some or all of the operations in the first RQI-related operation; If the first timer is not started or times out, the first terminal device will not perform some or all of the operations in the first RQI related operation; If the first QoS flow belongs to one or more QoS flows, the first terminal device performs some or all of the operations in the first RQI-related operation; If the first QoS flow does not belong to the one or more QoS flows, the first terminal device does not perform some or all of the operations in the first RQI related operation.

44. The method according to any one of claims 39 to 43, characterized in that, If the RQI value in the first data packet or the data packet of the first QoS stream is the first value when the first timer is not started, then the first timer is started.

45. The method according to any one of claims 39 to 44, characterized in that: The first RQI-related operation is an operation on the first QoS stream or an operation on the data packets of the first QoS stream; or, The first RQI-related operation is an operation on the QoS stream corresponding to the first timer or an operation on the data packets of the QoS stream corresponding to the first timer; or, The first RQI-related operation is an operation on the QoS flow determined based on the first information, or an operation on data packets in the QoS flow determined based on the first information; or, The first RQI-related operation is an operation on any QoS flow of the first terminal device at present, or an operation on data packets of any QoS flow of the first terminal device at present.

46. ​​The method according to any one of claims 39 to 45, characterized in that, One or more of the following are satisfied: The first timer is configured by the core network device; The first timer is activated by the core network device; The first timer is maintained in the core network; The timing duration of the first timer is either default, predefined, or configured by the core network device; The enabling or disabling of the first timer is configured or indicated by the core network device; The one or more QoS flows are configured by the core network equipment; The QoS stream, radio bearer, MAC entity, and terminal device that perform the first RQI-related operation are configured or indicated by the core network device. The QoS flow, radio bearer, MAC entity, and terminal device that execute the first rule are configured or indicated by the core network device.

47. The method according to any one of claims 39 to 46, characterized in that: The second QoS flow is a specific QoS flow; or, The second QoS flow is the QoS flow determined based on the first information; or, The second QoS stream is any QoS stream currently being used by the first terminal device; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows; The QoS stream in which the first data packet is located; The QoS stream corresponding to the first timer.

48. The method according to any one of claims 39 to 47, characterized in that, The packets of the second QoS stream satisfy one of the following: It carries the Quality of Service (QFI) identifier and the Reliability Quality (RQI). It carries QFI, but not RQI; It does not carry QFI, nor does it carry RQI; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

49. The method according to any one of claims 39 to 48, characterized in that, The packets of the second QoS stream satisfy one of the following: Includes a first packet header, and the first packet header carries QFI but not RQI; Includes a first header, and the first header carries QFI and RQI; Excluding the first pack head; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

50. The method according to any one of claims 37 to 49, characterized in that, The first terminal device is configured to receive one or more of the following: The first type of QoS flow is a QoS flow associated with the first rule or the first information; The second type of QoS flow is a QoS flow that is not associated with the first rule or the first information; The first type of QoS flow is the QoS flow that performs the first RQI-related operation; The second type of QoS flow is a QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet that performs the first RQI-related operation in a specific QoS flow; The second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet in a specific QoS flow that is associated with the first rule or the first information; The second type of data packet is a data packet in a specific QoS flow that is not associated with the first rule or the first information.

51. The method according to claim 50, characterized in that: The first type of QoS stream and the second type of QoS stream are mapped to the same data radio bearer; or, The first type of QoS stream and the second type of QoS stream are mapped to different data radio bearers; or, The first type of data packet and the second type of data packet are transmitted via the same data wireless bearer; or, The first type of data packet and the second type of data packet are transmitted through different data wireless bearers.

52. The method according to claim 50 or 51, characterized in that, The first type of QoS flow includes one or more of the following: the first QoS flow, the one or more QoS flows, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

53. The method according to any one of claims 37 to 52, characterized in that, The first information is information sent by the core network device.

54. The method according to claim 53, characterized in that, The first information is carried in the NAS signaling.

55. A communication device, characterized in that, The communication device is a first terminal device, and the communication device includes: The determining unit is configured to determine, for a first Quality of Service (QoS) flow or a first data packet, whether to perform or not to perform a first Reflection Mapping Quality of Service Indication (RQI) related operation.

56. The communication device according to claim 55, characterized in that, The first RQI-related operation includes one or more of the following: Obtain the RQI from the first data packet or the data packet of the first QoS stream; Deduce QoS rules based on RQI in the first data packet or the data packet of the first QoS stream; Indicate the RQI in the first data packet or the data packet of the first QoS stream to the non-access stratum NAS of the first terminal device; Instruct the NAS of the first terminal device to update or derive the mapping rules from service data stream SDF to QoS stream; Ignore or skip the RQI field in the first data packet or the data packet of the first QoS stream; Ignore the rules for deriving the SDF to QoS flow mapping; Maintain the current SDF to QoS flow mapping rules; Update or derive the SDF to QoS flow mapping rules; Start or restart the first timer, which is used to control whether or not the first RQI-related operation is executed; The header of the first data packet or the data packet of the first QoS flow is parsed using a first header format, wherein the first header format does not include the RQI field.

57. The communication device according to claim 55 or 56, characterized in that, The determining unit is used for: The first rule determines whether to execute or not to execute the first RQI-related operation; The first rule is related to one or more of the following: A first timer is used to control whether or not the first RQI-related operation is executed; The identification information of one or more QoS flows, wherein the one or more QoS flows are used to perform the first RQI-related operation, or the identification information is used to determine whether to perform or not perform the first RQI-related operation; The information in the first data packet is used to determine whether or not to perform the first RQI-related operation.

58. The communication device according to claim 57, characterized in that, The determining unit is used for: If the first condition is met, determine whether to execute or not execute the first RQI-related operation according to the first rule; The first condition is related to one or more of the following: A first capability, wherein the first capability is used to indicate whether the first terminal device supports or does not support the first rule; The system receives first information sent by a network device. The first information is used to configure the first rule, instructing the first terminal device to enable the first rule, or instructing the configuration of the first rule or the first RQI-related operation.

59. The communication device according to claim 58, characterized in that, The first information satisfies one or more of the following: The first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of the one or more QoS flows; The first information is used to configure the first terminal device to perform or not perform the first RQI-related operation; The first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule; The first information is used to configure or instruct the QoS stream, radio bearer, media access control MAC entity or terminal device that performs the first RQI-related operation; The first information is used to configure or indicate the QoS flow, radio bearer, MAC entity, or terminal device that performs the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule; The first information is used to configure the first timer; The first information is used to configure the one or more QoS flows; The first information is used to configure the QoS flow corresponding to the first timer; The first information is used to activate or parse the header of the data packet using the first header format; The first information is used to activate or configure the first packet header format; The first header format does not include the RQI field.

60. The communication device according to claim 58 or 59, characterized in that: The first information is information specific to the first terminal device; or... The first information is information specific to QoS flows; or, The first information pertains to MAC entities; or, The first piece of information pertains to the wireless bearer.

61. The communication device according to any one of claims 58 to 60, characterized in that, The first information is information sent by the access network device or the core network device.

62. The communication device according to claim 61, characterized in that, The first information is carried in NAS signaling, Radio Resource Control (RRC) signaling, Service Data Adaptation Protocol (SDAP) control PDU, Media Access Control (MAC) control element (CE), Downlink Control Information (DCI), or control signaling of the first protocol layer.

63. The communication device according to any one of claims 57 to 62, characterized in that, The first rule includes one or more of the following: If the first timer is running, the first terminal device executes some or all of the operations in the first RQI-related operation; If the first timer is not started or times out, the first terminal device will not perform some or all of the operations in the first RQI related operation; If the first QoS flow belongs to one or more QoS flows, the first terminal device performs some or all of the operations in the first RQI-related operation; If the first QoS flow does not belong to the one or more QoS flows, the first terminal device does not perform some or all of the operations in the first RQI related operation.

64. The communication device according to any one of claims 57 to 63, characterized in that, The communication device also includes: The startup unit is configured to start the first timer if the RQI value in the first data packet or the data packet of the first QoS stream is a first value when the first timer is not started.

65. The communication device according to any one of claims 57 to 64, characterized in that: The first RQI-related operation is an operation on the first QoS stream or an operation on the data packets of the first QoS stream; or, The first RQI-related operation is an operation on the QoS stream corresponding to the first timer or an operation on the data packets of the QoS stream corresponding to the first timer; or, The first RQI-related operation is an operation for a QoS flow determined based on the first information sent by the network device, or an operation for data packets in a QoS flow determined based on the first information sent by the network device. The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, or instruct the configuration of the first rule or the first RQI-related operation. or, The first RQI-related operation is an operation on any QoS flow of the first terminal device at present, or an operation on data packets of any QoS flow of the first terminal device at present.

66. The communication device according to any one of claims 57 to 65, characterized in that, One or more of the following are satisfied: The first timer is configured by the access network device or the core network device; The first timer is activated by the access network device or the core network device; The first timer is maintained by the access network device and / or the first terminal device; The timing duration of the first timer is either default, predefined, or configured by the access network device or the core network device. Whether the first timer is enabled or disabled is configured or indicated by the access network device or the core network device; The one or more QoS flows are configured by access network equipment or core network equipment; The first rule is configured by the access network device or the core network device; Whether the first rule is enabled or disabled is indicated by the access network device or the core network device. The QoS flow, radio bearer, MAC entity, and terminal device that perform the first RQI-related operation are configured or indicated by the access network device or core network device. The QoS flow, radio bearer, MAC entity, and terminal device that execute the first rule are configured or indicated by the access network device or core network device.

67. The communication device according to any one of claims 57 to 66, characterized in that: The second QoS flow is a specific QoS flow; or, The second QoS flow is a QoS flow determined based on the first information sent by the network device. The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, or instruct the relevant configuration of the first rule or the first RQI related operation. or, The second QoS stream is any QoS stream currently being used by the first terminal device; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows; The QoS stream in which the first data packet is located; The QoS stream corresponding to the first timer.

68. The communication device according to any one of claims 57 to 67, characterized in that, The packets of the second QoS stream satisfy one of the following: It carries the Quality of Service Flow Identifier (QFI) and the RQI. It carries QFI, but not RQI; It does not carry QFI, nor does it carry RQI; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

69. The communication device according to any one of claims 57 to 68, characterized in that, The packets of the second QoS stream satisfy one of the following: Includes a first packet header, and the first packet header carries QFI but not RQI; Includes a first header, and the first header carries QFI and RQI; Excluding the first pack head; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

70. The communication device according to any one of claims 57 to 69, characterized in that, The first terminal device is configured to receive one or more of the following: The first type of QoS flow is a QoS flow associated with the first rule or the first information; The second type of QoS flow is a QoS flow that is not associated with the first rule or the first information; The first type of QoS flow is the QoS flow that performs the first RQI-related operation; The second type of QoS flow is a QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet that performs the first RQI-related operation in a specific QoS flow; The second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet associated with the first rule or the first information in a specific QoS flow; The second type of data packet is a data packet in a specific QoS flow that is not associated with the first rule or the first information; The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, or instruct the configuration of the first rule or the first RQI-related operation.

71. The communication device according to claim 70, characterized in that: The first type of QoS stream and the second type of QoS stream are mapped to the same data radio bearer; or, The first type of QoS stream and the second type of QoS stream are mapped to different data radio bearers; or, The first type of data packet and the second type of data packet are transmitted via the same data wireless bearer; or, The first type of data packet and the second type of data packet are transmitted through different data wireless bearers.

72. The communication device according to claim 70 or 71, characterized in that, The first type of QoS flow includes one or more of the following: the first QoS flow, the one or more QoS flows, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

73. A communication device, characterized in that, The communication device is an access network device, and the communication device includes: A communication unit is used to send first information to a first terminal device; The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, and instruct the configuration of the first rule or the first reflection mapping service quality indicator (RQI) related operations. The first rule is used by the first terminal device to determine whether to perform or not perform the first RQI-related operation for the first data packet or the first data stream.

74. The communication device according to claim 73, characterized in that, The first RQI-related operation includes one or more of the following: Obtain the RQI from the first data packet or the data packet of the first Quality of Service (QoS) stream; Deduce QoS rules based on RQI in the first data packet or the data packet of the first QoS stream; Indicate the RQI in the first data packet or the data packet of the first QoS stream to the non-access stratum NAS of the first terminal device; Instruct the NAS of the first terminal device to update or derive the mapping rules from service data stream SDF to QoS stream; Ignore or skip the RQI field in the first data packet or the data packet of the first QoS stream; Ignore the rules for deriving the SDF to QoS flow mapping; Maintain the current SDF to QoS flow mapping rules; Update or derive the SDF to QoS flow mapping rules; Start or restart the first timer, which is used to control whether or not the first RQI-related operation is executed; The header of the first data packet or the data packet of the first QoS flow is parsed using a first header format, wherein the first header format does not include the RQI field.

75. The communication device according to claim 73 or 74, characterized in that, The first rule is related to one or more of the following: A first timer is used to control whether or not the first RQI-related operation is executed; The identification information of one or more QoS flows, wherein the one or more QoS flows are used to perform the first RQI-related operation, or the identification information is used to determine whether to perform or not perform the first RQI-related operation; The information in the first data packet is used to determine whether or not to perform the first RQI-related operation.

76. The communication device according to claim 75, characterized in that, The first rule is activated when a first condition is met, which is related to one or more of the following: A first capability, wherein the first capability is used to indicate whether the first terminal device supports or does not support the first rule; The access network device sent the first information to the first terminal device.

77. The communication device according to claim 75 or 76, characterized in that, The first information satisfies one or more of the following: The first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of the one or more QoS flows; The first information is used to configure the first terminal device to perform or not perform the first RQI-related operation; The first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule; The first information is used to configure or instruct the QoS stream, radio bearer, media access control MAC entity or terminal device that performs the first RQI-related operation; The first information is used to configure or indicate the QoS flow, radio bearer, MAC entity, or terminal device that performs the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule; The first information is used to configure the first timer; The first information is used to configure the one or more QoS flows; The first information is used to configure the QoS flow corresponding to the first timer; The first information is used to activate or parse the header of the data packet using the first header format; The first information is used to activate or configure the first packet header format; The first header format does not include the RQI field.

78. The communication device according to claim 76 or 77, characterized in that: The first information is information specific to the first terminal device; or... The first information is information specific to QoS flows; or, The first information pertains to MAC entities; or, The first piece of information pertains to the wireless bearer.

79. The communication device according to any one of claims 75 to 78, characterized in that, The first rule includes one or more of the following: If the first timer is running, the first terminal device executes some or all of the operations in the first RQI-related operation; If the first timer is not started or times out, the first terminal device will not perform some or all of the operations in the first RQI related operation; If the first QoS flow belongs to one or more QoS flows, the first terminal device performs some or all of the operations in the first RQI-related operation; If the first QoS flow does not belong to the one or more QoS flows, the first terminal device does not perform some or all of the operations in the first RQI related operation.

80. The communication device according to any one of claims 75 to 79, characterized in that, If the RQI value in the first data packet or the data packet of the first QoS stream is the first value when the first timer is not started, then the first timer is started.

81. The communication device according to any one of claims 75 to 80, characterized in that: The first RQI-related operation is an operation on the first QoS stream or an operation on the data packets of the first QoS stream; or, The first RQI-related operation is an operation on the QoS stream corresponding to the first timer or an operation on the data packets of the QoS stream corresponding to the first timer; or, The first RQI-related operation is an operation on the QoS flow determined based on the first information, or an operation on data packets in the QoS flow determined based on the first information; or, The first RQI-related operation is an operation on any QoS flow of the first terminal device at present, or an operation on data packets of any QoS flow of the first terminal device at present.

82. The communication device according to any one of claims 75 to 81, characterized in that, One or more of the following are satisfied: The first timer is configured by the access network device; The first timer is activated by the access network device; The first timer is maintained by the access network device and / or the first terminal device; The timing duration of the first timer is either default, predefined, or configured by the access network device; The first timer may be enabled or disabled by the access network device; The one or more QoS flows are configured by the access network device; The QoS stream, radio bearer, MAC entity, and terminal device that perform the first RQI-related operation are configured or indicated by the access network device. The QoS flow, radio bearer, MAC entity, and terminal device that execute the first rule are configured or indicated by the access network device.

83. The communication device according to any one of claims 75 to 82, characterized in that: The second QoS flow is a specific QoS flow; or, The second QoS flow is the QoS flow determined based on the first information; or, The second QoS stream is any QoS stream currently being used by the first terminal device; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows; The QoS stream in which the first data packet is located; The QoS stream corresponding to the first timer.

84. The communication device according to any one of claims 75 to 83, characterized in that, The packets of the second QoS stream satisfy one of the following: It carries the Quality of Service Flow Identifier (QFI) and the RQI. It carries QFI, but not RQI; It does not carry QFI, nor does it carry RQI; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

85. The communication device according to any one of claims 85 to 84, characterized in that, The packets of the second QoS stream satisfy one of the following: Includes a first packet header, and the first packet header carries QFI but not RQI; Includes a first header, and the first header carries QFI and RQI; Excluding the first pack head; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

86. The communication device according to any one of claims 73 to 85, characterized in that, The first terminal device is configured to receive one or more of the following: The first type of QoS flow is a QoS flow associated with the first rule or the first information; The second type of QoS flow is a QoS flow that is not associated with the first rule or the first information; The first type of QoS flow is the QoS flow that performs the first RQI-related operation; The second type of QoS flow is a QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet that performs the first RQI-related operation in a specific QoS flow; The second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet in a specific QoS flow that is associated with the first rule or the first information; The second type of data packet is a data packet in a specific QoS flow that is not associated with the first rule or the first information.

87. The communication device according to claim 86, characterized in that: The first type of QoS stream and the second type of QoS stream are mapped to the same data radio bearer; or, The first type of QoS stream and the second type of QoS stream are mapped to different data radio bearers; or, The first type of data packet and the second type of data packet are transmitted via the same data wireless bearer; or, The first type of data packet and the second type of data packet are transmitted through different data wireless bearers.

88. The communication device according to claim 86 or 87, characterized in that, The first type of QoS flow includes one or more of the following: the first QoS flow, the one or more QoS flows, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

89. The communication device according to any one of claims 73 to 88, characterized in that, The first information is information sent by the access network device.

90. The communication device according to claim 89, characterized in that, The first information is carried in Radio Resource Control (RRC) signaling, Service Data Adaptation Protocol (SDAP) control PDU, Media Access Control (MAC) control element (CE), Downlink Control Information (DCI), or control signaling of the first protocol layer.

91. A communication device, characterized in that, The communication equipment is a core network device, and the communication equipment includes: A communication unit is used to send first information to a first terminal device; The first information is used to configure the first rule, instruct the first terminal device to enable the first rule, and instruct the configuration of the first rule or the first reflection mapping service quality indicator (RQI) related operations. The first rule is used by the first terminal device to determine whether to perform or not perform the first RQI-related operation for the first data packet or the first data stream.

92. The communication device according to claim 91, characterized in that, The first RQI-related operation includes one or more of the following: Obtain the RQI from the first data packet or the data packet of the first Quality of Service (QoS) stream; Deduce QoS rules based on RQI in the first data packet or the data packet of the first QoS stream; Indicate the RQI in the first data packet or the data packet of the first QoS stream to the non-access stratum NAS of the first terminal device; Instruct the NAS of the first terminal device to update or derive the mapping rules from service data stream SDF to QoS stream; Ignore or skip the RQI field in the first data packet or the data packet of the first QoS stream; Ignore the rules for deriving the SDF to QoS flow mapping; Maintain the current SDF to QoS flow mapping rules; Update or derive the SDF to QoS flow mapping rules; Start or restart the first timer, which is used to control whether or not the first RQI-related operation is executed; The header of the first data packet or the data packet of the first QoS flow is parsed using a first header format, wherein the first header format does not include the RQI field.

93. The communication device according to claim 91 or 92, characterized in that, The first rule is related to one or more of the following: A first timer is used to control whether or not the first RQI-related operation is executed; The identification information of one or more QoS flows, wherein the one or more QoS flows are used to perform the first RQI-related operation, or the identification information is used to determine whether to perform or not perform the first RQI-related operation; The information in the first data packet is used to determine whether or not to perform the first RQI-related operation.

94. The communication device according to claim 93, characterized in that, The first rule is activated when a first condition is met, which is related to one or more of the following: A first capability, wherein the first capability is used to indicate whether the first terminal device supports or does not support the first rule; The core network device sent the first information to the first terminal device.

95. The communication device according to claim 93 or 94, characterized in that, The first information satisfies one or more of the following: The first information is used to explicitly or implicitly instruct the first terminal device to enable or activate the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to maintain the first timer; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the identification information of the one or more QoS flows; The first information is used to configure the first terminal device to perform or not perform the first RQI-related operation; The first information is used to configure the first terminal device to perform the first RQI-related operation based on or not based on the first rule; The first information is used to configure or instruct the QoS stream, radio bearer, media access control MAC entity or terminal device that performs the first RQI-related operation; The first information is used to configure or indicate the QoS flow, radio bearer, MAC entity, or terminal device that performs the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to determine whether to perform or not perform the first RQI-related operation based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different data packets based on the first rule; The first information is used to explicitly or implicitly instruct the first terminal device to perform different operations on different QoS flows based on the first rule; The first information is used to configure the first timer; The first information is used to configure the one or more QoS flows; The first information is used to configure the QoS flow corresponding to the first timer; The first information is used to activate or parse the header of the data packet using the first header format; The first information is used to activate or configure the first packet header format; The first header format does not include the RQI field.

96. The communication device according to claim 94 or 95, characterized in that: The first information is information specific to the first terminal device; or... The first information is information specific to QoS flows; or, The first information pertains to MAC entities; or, The first piece of information pertains to the wireless bearer.

97. The communication device according to any one of claims 93 to 96, characterized in that, The first rule includes one or more of the following: If the first timer is running, the first terminal device executes some or all of the operations in the first RQI-related operation; If the first timer is not started or times out, the first terminal device will not perform some or all of the operations in the first RQI related operation; If the first QoS flow belongs to one or more QoS flows, the first terminal device performs some or all of the operations in the first RQI-related operation; If the first QoS flow does not belong to the one or more QoS flows, the first terminal device does not perform some or all of the operations in the first RQI related operation.

98. The communication device according to any one of claims 93 to 97, characterized in that, If the RQI value in the first data packet or the data packet of the first QoS stream is the first value when the first timer is not started, then the first timer is started.

99. The communication device according to any one of claims 93 to 98, characterized in that: The first RQI-related operation is an operation on the first QoS stream or an operation on the data packets of the first QoS stream; or, The first RQI-related operation is an operation on the QoS stream corresponding to the first timer or an operation on the data packets of the QoS stream corresponding to the first timer; or, The first RQI-related operation is an operation on the QoS flow determined based on the first information, or an operation on data packets in the QoS flow determined based on the first information; or, The first RQI-related operation is an operation on any QoS flow of the first terminal device at present, or an operation on data packets of any QoS flow of the first terminal device at present.

100. The communication device according to any one of claims 93 to 99, characterized in that, One or more of the following are satisfied: The first timer is configured by the core network device; The first timer is activated by the core network device; The first timer is maintained in the core network; The timing duration of the first timer is either default, predefined, or configured by the core network device; The enabling or disabling of the first timer is configured or indicated by the core network device; The one or more QoS flows are configured by the core network equipment; The QoS stream, radio bearer, MAC entity, and terminal device that perform the first RQI-related operation are configured or indicated by the core network device. The QoS flow, radio bearer, MAC entity, and terminal device that execute the first rule are configured or indicated by the core network device.

101. The communication device according to any one of claims 93 to 100, characterized in that: The second QoS flow is a specific QoS flow; or, The second QoS flow is the QoS flow determined based on the first information; or, The second QoS stream is any QoS stream currently being used by the first terminal device; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows; The QoS stream in which the first data packet is located; The QoS stream corresponding to the first timer.

102. The communication device according to any one of claims 93 to 101, characterized in that, The packets of the second QoS stream satisfy one of the following: It carries the Quality of Service (QFI) identifier and the Reliability Quality (RQI). It carries QFI, but not RQI; It does not carry QFI, nor does it carry RQI; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

103. The communication device according to any one of claims 93 to 102, characterized in that, The packets of the second QoS stream satisfy one of the following: Includes a first packet header, and the first packet header carries QFI but not RQI; Includes a first header, and the first header carries QFI and RQI; Excluding the first pack head; The second QoS flow includes one or more of the following: The first QoS stream; The one or more QoS flows.

104. The communication device according to any one of claims 91 to 103, characterized in that, The first terminal device is configured to receive one or more of the following: The first type of QoS flow is a QoS flow associated with the first rule or the first information; The second type of QoS flow is a QoS flow that is not associated with the first rule or the first information; The first type of QoS flow is the QoS flow that performs the first RQI-related operation; The second type of QoS flow is a QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet that performs the first RQI-related operation in a specific QoS flow; The second type of data packet is a data packet in a specific QoS flow that does not perform the first RQI-related operation; The first type of data packet is a data packet in a specific QoS flow that is associated with the first rule or the first information; The second type of data packet is a data packet in a specific QoS flow that is not associated with the first rule or the first information.

105. The communication device according to claim 104, characterized in that: The first type of QoS stream and the second type of QoS stream are mapped to the same data radio bearer; or, The first type of QoS stream and the second type of QoS stream are mapped to different data radio bearers; or, The first type of data packet and the second type of data packet are transmitted via the same data wireless bearer; or, The first type of data packet and the second type of data packet are transmitted through different data wireless bearers.

106. The communication device according to claim 104 or 105, characterized in that, The first type of QoS flow includes one or more of the following: the first QoS flow, the one or more QoS flows, the QoS flow containing the first data packet, and the QoS flow corresponding to the first timer.

107. The communication device according to any one of claims 91 to 106, characterized in that, The first information is information sent by the core network device.

108. The communication device according to claim 107, characterized in that, The first information is carried in the NAS signaling.

109. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs the method as described in any one of claims 1 to 18, 19 to 36, or 37 to 54.

110. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method as described in any one of claims 1 to 18, 19 to 36, or 37 to 54.

111. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 18, 19 to 36, or 37 to 54.

112. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1 to 18, 19 to 36, or 37 to 54.

113. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1 to 18, 19 to 36, or 37 to 54.

114. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 18, 19 to 36, or 37 to 54.

Images