Communication method and device

Abstract

The present application relates to a communication method and device. The method comprises: an access network device sends downlink signaling to a terminal, wherein the downlink signaling is used by the terminal to perform a first behavior, and the first behavior includes at least one of the following: determining or adjusting an uplink rate, determining or adjusting a Quality of Service (QoS) parameter, and determining or adjusting a QoS requirement.

Description

Communication methods and devices Technical Field

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

[0002] In related technologies, network-side QoS (Quality of Service) control is executed at the granularity of QoS flows. The configuration of QoS parameters for these flows is done by the core network for the access network devices, which then schedule radio resources based on these parameters. Current QoS control mechanisms allow access network devices to change or adjust QoS requirements according to actual needs. However, ensuring the efficiency of adjustments to at least one of the following—uplink rate, QoS parameters, or QoS requirements—on the terminal side becomes a problem that needs to be solved. Summary of the Invention

[0003] This application provides a communication method and device.

[0004] This application provides a communication method, including:

[0005] The access network device sends downlink signaling to the terminal, wherein the downlink signaling is used for the terminal to perform a first action, the first action including at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

[0006] This application provides a communication method, including:

[0007] The access network device receives first information reported by the terminal, wherein the first information is used to assist the access network device in selecting QoS requirements.

[0008] This application provides a communication method, including:

[0009] The terminal receives downlink signaling sent by the access network equipment;

[0010] The terminal performs a first action based on the downlink signaling, wherein the first action includes at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

[0011] This application provides a communication method, including:

[0012] The terminal reports first information to the access network device, wherein the first information is used to assist the access network device in selecting QoS requirements.

[0013] This application provides an access network device, including:

[0014] The first communication unit is configured to send downlink signaling to the terminal, wherein the downlink signaling is used by the terminal to perform a first action, the first action including at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

[0015] This application provides an access network device, including:

[0016] The first communication unit is used to receive first information reported by the terminal, wherein the first information is used to assist the access network device in selecting QoS requirements.

[0017] This application provides a terminal, including:

[0018] The second communication unit is used to receive downlink signaling sent by the access network equipment;

[0019] The second processing unit is configured to perform a first action based on the downlink signaling, wherein the first action includes at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

[0020] This application provides a terminal, including:

[0021] The second communication unit is used to report first information to the access network device, wherein the first information is used to assist the access network device in selecting QoS requirements.

[0022] This application provides an access network device, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to cause the access network device to perform the methods described above.

[0023] This application provides a terminal, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the terminal to perform the methods described above.

[0024] This application provides a chip for implementing the above method.

[0025] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the methods described above.

[0026] This application provides a computer-readable storage medium for storing a computer program, which, when run by a device, causes the device to perform the above-described method.

[0027] This application provides a computer program product, including computer program instructions that cause a computer to perform the above-described method.

[0028] By adopting the above scheme, the access network device sends downlink signaling to the terminal, enabling the terminal to perform at least one of the following actions based on this downlink signaling: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements. This allows the terminal to quickly receive downlink signaling from the access network device to determine or adjust at least one of the QoS parameters, uplink rate, or QoS requirements, improving the adjustment efficiency on the terminal side. This avoids the problems of low indication efficiency and impact on terminal adjustment efficiency caused by the previous method in related technologies where the access network first notifies the core network, and then the core network notifies the terminal, when the access network needs to change QoS parameters or QoS requirements. Attached Figure Description

[0029] Figure 1 is a schematic diagram of an application scenario according to an embodiment of this application.

[0030] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application.

[0031] Figure 3 is a schematic flowchart of a communication method according to another embodiment of this application.

[0032] Figure 4 is a schematic flowchart of a communication method according to another embodiment of this application.

[0033] Figure 5 is a schematic flowchart of a communication method according to another embodiment of this application.

[0034] Figure 6 is a schematic flowchart of a communication method according to another embodiment of this application.

[0035] Figure 7 is a schematic flowchart of a communication method according to another embodiment of this application.

[0036] Figure 8 is a schematic block diagram of an access network device according to an embodiment of the present application.

[0037] Figure 9 is a schematic block diagram of a terminal according to an embodiment of this application.

[0038] Figure 10 is a schematic block diagram of a communication device according to an embodiment of this application.

[0039] Figure 11 is a schematic block diagram of a chip according to an embodiment of this application.

[0040] Figure 12 is a schematic block diagram of a communication system according to an embodiment of this application. Detailed Implementation

[0041] The technical solutions of this application embodiment can be applied to various communication systems, such as: LTE (Long Term Evolution), LTE-A (Long Term Evolution-Advanced), NR (New Radio), evolution of NR, WLAN (Wireless Local Area Network), WiFi (Wireless Fidelity), or other communication systems.

[0042] This application describes various embodiments in conjunction with network devices and terminals. The terminal can be mobile or fixed, and may also be referred to as a mobile station, user unit, etc. The terminal can be a station in a WLAN, or a smart terminal, wireless modem, laptop, tablet, etc. In this application embodiment, the terminal can be a VR (Virtual Reality) terminal / AR (Augmented Reality) terminal, industrial control terminal, autonomous driving terminal, telemedicine terminal, smart grid terminal, transportation safety terminal, smart city terminal, or smart home wireless terminal, etc. By way of example and not limitation, in this application embodiment, the terminal can also be a wearable device.

[0043] In this embodiment, the network device can be a device for communicating with a terminal. The network device can be an access point in a WLAN, an evolved base station in LTE, a relay station, a vehicle-mounted device, a wearable device, a network device in an NR network (gNB, the next generation Node B), a network device in a future PLMN network, or a network device in a non-terrestrial network, etc. By way of example and not limitation, in this embodiment, the network device can have mobility characteristics; for example, the network device can be a mobile device.

[0044] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0045] Figure 1 exemplarily illustrates a communication system 100. The communication system includes network devices 110 and terminals 120. In one possible implementation, the communication system 100 may include multiple network devices 110, and the coverage area of ​​each network device 110 may include one or more terminals 120; this embodiment does not limit this. In another possible implementation, the communication system 100 may also include other network entities such as mobility management entities and access and mobility management functions; this embodiment does not limit this. The network devices may further include access network devices and first core network elements. That is, the communication system may also include multiple core networks for communicating with the access network devices. The access network devices may be base stations of LTE, LTE-A, or NR systems. Taking the communication system shown in Figure 1 as an example, the communication devices may include network devices and terminals with communication functions. The communication devices may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities; this embodiment does not limit this.

[0046] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0047] S210. The access network device sends downlink signaling to the terminal, wherein the downlink signaling is used by the terminal to perform a first action, the first action including at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

[0048] Figure 3 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0049] S310, The terminal receives downlink signaling sent by the access network equipment;

[0050] S320. The terminal performs a first action based on the downlink signaling, wherein the first action includes at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS (Quality of Service) parameters, or determining or adjusting QoS requirements.

[0051] The downlink signaling is carried by one of the following: DCI (Downlink Control Information), downlink RRC (Radio Resource Control) message, or downlink MAC (Medium Access Control) CE (Control Element).

[0052] In some possible implementations, the processing of the access network device may further include: the access network device receiving multiple sets of QoS requirements.

[0053] In one embodiment, the core network element configures multiple sets of QoS requirements for the access network device.

[0054] Specifically, the processing by core network elements includes: core network elements sending multiple sets of QoS requirements to access network devices. Access network devices receiving multiple sets of QoS requirements includes: access network devices receiving multiple sets of QoS requirements sent by core network elements.

[0055] The core network element can be a control plane network element on the core network side, such as an SMF (Session Management Function), etc., without any limitation.

[0056] The core network element sending multiple QoS requests to the access network device can be either the core network element sending multiple QoS requests to the access network device for the first time, or the core network element sending multiple updated QoS requests to the access network device. Here, there are no restrictions on the timing, reason, or update reason for the core network element sending multiple QoS requests.

[0057] In this embodiment, the granularity at which the core network element configures multiple QoS requirements for the access network device can be any one of QoS flow, PDU (Packet Data Unit) session, DRB (Data Radio Bearer), MAC entity, or terminal.

[0058] In one example, core network elements configure multiple sets of QoS requirements for access network devices at the QoS flow granularity. The access network devices receive these multiple sets of QoS requirements for the terminal's QoS flow from the core network elements. The information sent by the core network elements to the access network devices can be QoS data flow information (carrying multiple sets of QoS requirements for the terminal's QoS flow), which will not be repeated below.

[0059] The terminal may have one or more QoS streams. Multiple QoS requirements for a terminal's QoS streams may include multiple QoS requirements for each QoS stream in at least one of the terminal's QoS streams; alternatively, multiple QoS requirements for a terminal's QoS streams may also be multiple QoS requirements corresponding to multiple QoS streams.

[0060] The specific content of multiple QoS requirements for any QoS flow may include at least one of the following: the identification information of the QoS flow, the identification information of each QoS requirement in the multiple QoS requirements, and the specific parameters and values ​​of each QoS requirement.

[0061] Optionally, the QoS flow identification information may include at least one of the following: the QoS flow QFI (QoS flow ID), the QoS flow name, and the QoS flow index. Alternatively, the QoS flow identification information may also include a list of QoS flow identifiers. The list of QoS flow identifiers is a list that includes at least one of the following: a QoS flow QFI, a QoS flow name, and a QoS flow index.

[0062] The identification information for QoS requirements may include the ID of the QoS requirement, etc.

[0063] Specific parameters for QoS requirements may include at least one of the following: 5QI (5G QoS Indicator) and GBR (Guaranteed Bit Rate). This is for illustrative purposes only. In actual processing, QoS requirements may include at least one of the following in addition to 5QI and / or GBR: MBR (Maximum Bit Rate), ARP (Allocation and Retention Priority), latency, jitter, packet loss rate, etc. This document does not limit or exhaustively list all possible parameters for QoS requirements.

[0064] In a QoS flow, the QoS requirements of different groups may have different values ​​for at least some parameters, which will not be elaborated here.

[0065] The descriptions of each QoS requirement for each group of each QoS flow are similar to those above, so they will not be repeated here.

[0066] In one example, the core network element configures multiple sets of QoS requirements for the access network device at the PDU session granularity. The access network device receives the multiple sets of QoS requirements for the terminal's PDU session from the core network element.

[0067] The terminal may have one or more PDU sessions, and the multiple QoS requirements of the terminal's PDU sessions may include multiple QoS requirements for each PDU session in at least one of the terminal's total PDU sessions.

[0068] In this example, different QoS flows within a PDU session (or the various QoS flows corresponding to a PDU session) can correspond to different sets of QoS requirements. Alternatively, different QoS flows within a PDU session (or the various QoS flows corresponding to a PDU session) can correspond to the same sets of QoS requirements. Or, some of the different QoS flows within a PDU session (or the various QoS flows corresponding to a PDU session) can correspond to the same sets of QoS requirements.

[0069] Taking any given PDU session as an example, the specific content of the multiple QoS requirements for that PDU session may include at least one of the following: the PDU session's identification information, the QoS flow's identification information, the identification information of each QoS requirement within the multiple QoS requirements, and the specific parameters and values ​​of each QoS requirement. The PDU session's identification information may include the PDU session's ID and / or index. The explanations regarding the identification information of each QoS requirement, the QoS flow's identification information, the specific parameters, and their values ​​are the same as in the previous example and will not be repeated. Since the explanations regarding the multiple QoS requirements for each PDU session are the same, they will not be elaborated further.

[0070] In one example, core network elements configure multiple sets of QoS requirements for access network devices at the MAC entity level. The access network devices receive these multiple sets of QoS requirements from the core network elements, representing the terminal's MAC entity.

[0071] In this example, different QoS flows under a single MAC entity can correspond to the same multiple sets of QoS requirements. Alternatively, different QoS flows within different QoS flows under a single MAC entity can correspond to different multiple sets of QoS requirements. Alternatively, some parts of different QoS flows under a single MAC entity can correspond to the same multiple sets of QoS requirements. Alternatively, different PDU sessions under a single MAC entity can correspond to the same multiple sets of QoS requirements. Alternatively, some parts of different PDU sessions under a single MAC entity can correspond to the same multiple sets of QoS requirements. Alternatively, different PDU sessions within different PDU sessions under a single MAC entity can correspond to different multiple sets of QoS requirements, wherein different QoS flows within any single PDU session (or the QoS flows corresponding to a PDU session) can correspond to different or the same multiple sets of QoS requirements.

[0072] The specific content of multiple QoS requirements for a MAC entity may include at least one of the following: the identification information of the MAC entity, the identification information of the PDU session, the identification information of the QoS flow, the identification information of each QoS requirement in the multiple QoS requirements, and the specific parameters and values ​​of each QoS requirement. The explanations regarding the identification information, specific parameters, and values ​​of each QoS requirement are the same as in the previous example and will not be repeated.

[0073] In one example, core network elements configure multiple QoS requirements for access network devices at the DRB granularity. The access network devices receive these multiple QoS requirements from the core network elements, representing the terminal's DRB.

[0074] Among them, the DRB of the terminal can be referred to as the DRB corresponding to the terminal. The number of DRBs corresponding to the terminal can be one or more. The multiple sets of QoS requirements of the DRB corresponding to the terminal can include multiple sets of QoS requirements of each DRB in at least one of the DRBs of the terminal.

[0075] In this example, the various QoS flows corresponding to a DRB can correspond to the same multiple sets of QoS requirements. Alternatively, different QoS flows within the various QoS flows corresponding to a DRB can correspond to different multiple sets of QoS requirements. Or, some of the various QoS flows corresponding to a DRB can correspond to the same multiple sets of QoS requirements.

[0076] The specific content of multiple QoS requirements for any DRB may include at least one of the following: DRB identification information, QoS flow identification information, identification information of each QoS requirement in the multiple QoS requirements, and specific parameters and values ​​of each QoS requirement. The explanations regarding the identification information, specific parameters, and values ​​of each QoS requirement are the same as in the previous example and will not be repeated. Since the explanations regarding multiple QoS requirements for each DRB are the same, they will not be elaborated further.

[0077] In one example, core network elements configure multiple QoS requirements for access network devices at the terminal level. The access network devices receive these multiple QoS requirements from the core network elements.

[0078] In this example, multiple QoS requirements of the terminal can correspond to at least one of at least a MAC entity, at least one PDU session, at least one DRB, and at least one QoS flow. For example, multiple QoS requirements of the terminal may correspond to at least one PDU session, where at least one PDU session may use the same multiple QoS requirements, or different PDU sessions within at least one PDU session may use different multiple QoS requirements, or parts of at least one PDU session may use the same multiple QoS requirements. The explanation regarding multiple QoS requirements of the terminal corresponding to at least one MAC entity, at least one DRB, and at least one QoS flow is similar to the example above and will not be repeated.

[0079] The specific content of multiple QoS requirements for a terminal may include at least one of the following: terminal identification information, PDU session identification information, MAC entity identification information, DRB identification information, QoS flow identification information, identification information of each QoS requirement in the multiple QoS requirements, and specific parameters and values ​​of each QoS requirement. The explanations regarding the identification information, specific parameters, and values ​​of each QoS requirement are the same as in the previous example and will not be repeated.

[0080] Optionally, after receiving multiple QoS requirements from core network elements, the access network device can send these requirements to the terminal, or determine whether to configure multiple QoS requirements for the terminal based on actual conditions, protocols, or policies. If the access network device determines to configure multiple QoS requirements for the terminal based on actual conditions, protocols, or policies, it can further configure these requirements. The processing by the access network device also includes: the access network device sending multiple QoS requirements to the terminal; and the terminal receiving the multiple QoS requirements sent by the access network device. The granularity and specific content of the QoS requirements configured by the access network device for the terminal are the same as the granularity and specific content of the multiple QoS requirements received by the access network device, and will not be repeated here.

[0081] Optionally, core network elements may configure multiple QoS requirements for terminals based on actual conditions, protocols, or policies; or, core network elements may negotiate or interact with terminals based on actual conditions, protocols, or policies to configure multiple QoS requirements.

[0082] The processing by core network elements includes one of the following: the core network element sends multiple sets of QoS requirements to the terminal; or the core network element and the terminal interact and negotiate to configure multiple sets of QoS requirements. Correspondingly, the terminal receives multiple sets of QoS requirements sent by the core network element; or interacts and negotiates with the core network element to determine multiple sets of QoS requirements. The granularity and specific content of the multiple sets of QoS requirements configured or sent by the core network element to the terminal are the same as those in the previous embodiment for configuring multiple sets of QoS requirements for the access network device, and will not be repeated.

[0083] In one embodiment, the terminal reports multiple sets of QoS requirements to the access network device.

[0084] In this embodiment, the terminal's processing further includes: the terminal receiving or determining multiple sets of QoS requirements.

[0085] Optionally, the core network element configures multiple QoS requirements for the terminal. That is, the core network element sends multiple QoS requirements to the terminal; the terminal receives the multiple QoS requirements sent by the core network element.

[0086] Optionally, multiple sets of QoS requirements can be configured through negotiation between the core network elements and the terminal. That is, the core network elements and the terminal negotiate with each other, and ultimately the terminal and the core network elements determine multiple sets of QoS requirements.

[0087] The granularity and specific content of the multiple QoS requirements obtained by the terminal are the same as the relevant descriptions of the granularity and specific content of the multiple QoS requirements configured by the core network element for the access network device in the aforementioned embodiments, and will not be repeated.

[0088] Optionally, after receiving or determining multiple sets of QoS requirements, the terminal may report these multiple sets of QoS requirements to the access network device; correspondingly, the access network device receives the multiple sets of QoS requirements sent by the terminal. The multiple sets of QoS requirements reported by the terminal to the access network device are the same as the multiple sets of QoS requirements received by the terminal, and will not be described in detail here.

[0089] In some possible implementations, the access network device sends downlink signaling, including one of the following: the access network device sends the downlink signaling when it determines or determines an adjusted QoS requirement from multiple sets of QoS requirements; the access network device sends the downlink signaling when it determines or determines an adjusted QoS parameter and / or the value of the QoS parameter; the access network device sends the downlink signaling when it determines or determines an adjusted rate.

[0090] The access network device may send downlink signaling if it receives multiple QoS requests at any given time. Alternatively, the access network device may send downlink signaling if it has determined or adjusted the rate. Or, the access network device may send downlink signaling if it has determined or adjusted QoS parameters and / or the values ​​of those QoS parameters.

[0091] In some possible embodiments, the access network device sends the downlink signaling when it determines or adjusts the QoS requirements from multiple sets of QoS requirements.

[0092] This embodiment can be executed by the access network device when it receives multiple sets of QoS requirements at any given time.

[0093] The phrase "the access network device determines or adjusts the QoS requirements from multiple sets of QoS requirements" can refer to the access network device determining the QoS requirements of the first object currently in use from multiple sets of QoS requirements; or, the access network device determining the adjusted QoS requirements of the first object from multiple sets of QoS requirements.

[0094] The process of the access network device determining the QoS requirement of the first object to be used from multiple sets of QoS requirements can be achieved by the access network device determining or selecting the QoS requirement of the first object to be used from the multiple sets of QoS requirements of the first object for the first time after receiving multiple sets of QoS requirements.

[0095] The access network device determines the adjusted QoS requirement of the first object from multiple sets of QoS requirements. This can be done when the access network device is currently using the QoS requirement of the first object determined or selected in the last time to transmit radio resources, and then determines that the original QoS requirement of the first object needs to be changed. The device then determines the adjusted QoS requirement of the first object to be used from multiple sets of QoS requirements of the first object.

[0096] The first object includes one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB. This embodiment does not limit the specific method by which the access network device determines the first object. For example, determining which QoS flows(s) among all the terminal's QoS flows as the first object is not limited in this embodiment; similarly, determining which PDU sessions(s) among all the terminal's PDU sessions as the first object is also not limited in this embodiment, and will not be exhaustively listed here.

[0097] In one embodiment, the specific reason why the access network device needs to change the QoS requirements of the first object is not limited in this embodiment. For example, the access network device may determine the need to change the QoS requirements of the first object based on at least one of the following: local configuration, protocol provisions, its own policies, its own rules, communication status, terminal requests, etc.

[0098] As illustrated in the foregoing embodiments, the multiple QoS requirements configured on the access network device side can be granular at any one of the following: terminal, QoS flow, PDU session, DRB, and MAC entity.

[0099] The following examples illustrate the contents of the multiple QoS requirements for the first object and the QoS requirements of the first object determined or adjusted by the access network device, using various examples at different granularities.

[0100] In one example, the first object is a terminal.

[0101] Optionally, the access network device is configured with multiple QoS requirements at the terminal level. The multiple QoS requirements of the first object are the same as the multiple QoS requirements of the terminal. The QoS requirements of the first object determined or adjusted by the access network device are one of the multiple QoS requirements of the terminal.

[0102] Optionally, the access network device is configured with multiple sets of QoS requirements at the QoS flow granularity. The multiple sets of QoS requirements for the first object include multiple sets of QoS requirements for each QoS flow of the terminal. The QoS requirements for the first object determined or adjusted by the access network device include a set of QoS requirements for each QoS flow of the terminal.

[0103] Optionally, the access network device is configured with multiple sets of QoS requirements at the PDU session granularity. The multiple sets of QoS requirements for the first object include multiple sets of QoS requirements for each PDU session of the terminal. The QoS requirements for the first object determined or adjusted by the access network device include a set of QoS requirements for each PDU session of the terminal.

[0104] Optionally, the access network device is configured with multiple sets of QoS requirements at the DRB granularity. The multiple sets of QoS requirements for the first object include multiple sets of QoS requirements for each DRB of the terminal. The QoS requirements for the first object determined or adjusted by the access network device include a set of QoS requirements for each DRB of the terminal.

[0105] Optionally, the access network device is configured with multiple sets of QoS requirements at the MAC entity level. The multiple sets of QoS requirements for the first object include multiple sets of QoS requirements for each MAC entity of the terminal. The QoS requirements for the first object determined or adjusted by the access network device include one set of QoS requirements for each MAC entity of the terminal.

[0106] In one example, the first object includes one or more QoS flows.

[0107] Optionally, the access network device is configured with multiple sets of QoS requirements at the terminal level. In this case, each QoS flow included in the first object uses the same multiple sets of QoS requirements from the same terminal. The QoS requirements for the first object determined or adjusted by the access network device include a set of QoS requirements from the terminal.

[0108] Optionally, the access network device is configured with multiple sets of QoS requirements at the QoS flow granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for each QoS flow within one or more QoS flows contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for each QoS flow contained in the first object.

[0109] Optionally, the access network device is configured with multiple sets of QoS requirements at the PDU session granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for the PDU session corresponding to each QoS flow in one or more QoS flows contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for the PDU session corresponding to each QoS flow contained in the first object, wherein one or more QoS flows of the first object may correspond to the same PDU session; in this case, these QoS flows correspond to the same set of QoS requirements for the PDU session.

[0110] Optionally, the access network device is configured with multiple sets of QoS requirements at the DRB granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for the DRB corresponding to each QoS flow in one or more QoS flows contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for the DRB corresponding to each QoS flow contained in the first object, wherein one or more QoS flows of the first object may correspond to the same DRB; in this case, these QoS flows correspond to the same set of QoS requirements for the DRB.

[0111] Optionally, the access network device is configured with multiple sets of QoS requirements at the MAC entity level. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for the MAC entity corresponding to each QoS flow in one or more QoS flows contained in the first object, wherein the MAC entities corresponding to one or more QoS flows of the first object may be the same. In this case, these QoS flows correspond to the same set of QoS requirements for the MAC entity.

[0112] In one example, the first object includes one or more PDU sessions.

[0113] Optionally, the access network device is configured with multiple sets of QoS requirements at the terminal level. In this case, each PDU session included in the first object uses the same multiple sets of QoS requirements for the terminal. The QoS requirements for the first object determined or adjusted by the access network device include a set of QoS requirements for the terminal.

[0114] Optionally, the access network device is configured with multiple sets of QoS requirements at the QoS flow granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for each QoS flow contained in each of the one or more PDU sessions included in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for each QoS flow contained in each PDU session included in the first object.

[0115] Optionally, the access network device is configured with multiple sets of QoS requirements at the PDU session granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for each PDU session contained within the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for each PDU session contained within the first object.

[0116] Optionally, the access network device is configured with multiple sets of QoS requirements at the DRB granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements of the DRBs corresponding to one or more PDU sessions contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements of each DRB corresponding to each PDU session contained in the first object.

[0117] Optionally, the access network device is configured with multiple sets of QoS requirements at the MAC entity level. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for the MAC entities corresponding to one or more PDU sessions contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for the MAC entities corresponding to each PDU session contained in the first object.

[0118] In one example, the first object includes one or more DRBs.

[0119] Optionally, the access network device is configured with multiple sets of QoS requirements at the terminal level. In this case, each DRB included in the first object uses the same multiple sets of QoS requirements for the terminal. The QoS requirements for the first object determined or adjusted by the access network device include a set of QoS requirements for the terminal.

[0120] Optionally, the access network device is configured with multiple sets of QoS requirements at the QoS flow granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for each QoS flow corresponding to each DRB in one or more DRBs contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for each QoS flow corresponding to each DRB contained in the first object.

[0121] Optionally, the access network device is configured with multiple sets of QoS requirements at the PDU session granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for the PDU sessions corresponding to each DRB contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for the PDU sessions corresponding to each DRB contained in the first object.

[0122] Optionally, the access network device is configured with multiple sets of QoS requirements at the DRB granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements from one or more DRBs contained within the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements from each DRB contained within the first object.

[0123] Optionally, the access network device is configured with multiple sets of QoS requirements at the MAC entity level. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for the MAC entities corresponding to one or more DRBs contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for the MAC entities corresponding to each DRB contained in the first object.

[0124] In one example, the first object includes one or more MAC entities.

[0125] Optionally, the access network device is configured with multiple sets of QoS requirements at the terminal level. In this case, each MAC entity included in the first object uses the same multiple sets of QoS requirements for the terminal. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for the terminal.

[0126] Optionally, the access network device is configured with multiple sets of QoS requirements at the QoS flow granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for each QoS flow corresponding to each MAC entity among one or more MAC entities contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for each QoS flow corresponding to the MAC entities contained in the first object.

[0127] Optionally, the access network device is configured with multiple sets of QoS requirements at the PDU session granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for the PDU sessions corresponding to each MAC entity contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for the PDU sessions corresponding to each MAC entity contained in the first object.

[0128] Optionally, the access network device is configured with multiple sets of QoS requirements at the DRB granularity. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for the DRBs corresponding to one or more MAC entities contained in the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for the DRBs corresponding to each MAC entity contained in the first object.

[0129] Optionally, the access network device is configured with multiple sets of QoS requirements at the MAC entity level. The multiple sets of QoS requirements for the first object include: multiple sets of QoS requirements for each MAC entity contained within the first object. The QoS requirements for the first object determined or adjusted by the access network device include: a set of QoS requirements for each MAC entity contained within the first object.

[0130] In this embodiment, the downlink signaling includes or carries at least one of the following: the identification information of the QoS requirement, the rate, the QoS parameter, the value of the QoS parameter, the identification information of the QoS flow, the identification information of the PDU session, the identification information of the MAC entity, the identification information of the DRB, the uplink direction information, and the downlink direction information.

[0131] The QoS requirement can be the QoS requirement corresponding to the first object that the access network device currently needs to use, or the QoS requirement of the first object that the access network device needs to use after adjustment. The relevant description of the QoS requirement corresponding to the first object is the same as that in the previous embodiment and will not be repeated.

[0132] The rate can be determined or changed by the application; alternatively, the rate can be determined or changed by the access network device based on the current state; or the rate can be related to QoS parameters and their values ​​and / or QoS requirements. For example, the rate can be determined by the access network device based on a set of QoS requirements corresponding to the first object currently needed, or by the access network device based on a set of QoS requirements for the first object to be used after a change.

[0133] Rate can be one of the following: air interface transmission rate, physical layer rate, application encoding / decoding rate, source rate, or channel rate. Rate can include at least one of the following: data rate or bit rate.

[0134] QoS parameters and their values ​​can be determined by the access network device based on a set of QoS requirements corresponding to the first object currently needed; or determined by the access network device based on a set of QoS requirements for the first object to be used after the change; or related to a set of QoS requirements corresponding to the first object currently needed; or related to a set of QoS requirements for the first object to be used after the change.

[0135] QoS parameters may include at least one of the following: 5QI, GBR, MBR, ARP, latency, jitter, packet loss rate, etc. The types of QoS parameters that may be included are not limited or exhaustively listed here.

[0136] The conditions under which downlink signaling may include QoS requirement identification information, rate, QoS parameters, and which of the QoS parameter values ​​are included are related to the configuration of multiple QoS requirements and whether multiple QoS requirements are configured on the terminal side.

[0137] Specifically, if multiple QoS requirements on the access network device side are configured by core network elements, the access network device can determine whether multiple QoS requirements are configured on the terminal side or not based on default rules, policies, or protocol provisions; if multiple QoS requirements on the access network device are reported by the terminal, the access network device can directly determine that multiple QoS requirements are configured on the terminal side.

[0138] If multiple QoS requirements are configured on the terminal side, the downlink signaling may include at least one of the following: QoS requirement identification information, rate, QoS parameter, and the value of the QoS parameter. For example, the downlink signaling may include QoS requirement identification information; or it may include rate, QoS parameter and its value, but not QoS requirement identification information; or it may include QoS requirement identification information, rate, QoS parameter, and at least one of the QoS parameter values, etc., without limitation or exhaustive list.

[0139] If the terminal is not configured with multiple QoS requirements, the downlink signaling does not include the identification information of the QoS requirements, but includes the rate, the QoS parameter, and at least one of the values ​​of the QoS parameter.

[0140] Uplink and / or downlink information can be used to indicate that the first action that the terminal needs to perform is the transmission direction targeted at the uplink and / or downlink.

[0141] If the first action required by the terminal is directed towards both the uplink and downlink directions, the downlink signaling may or may not include direction information.

[0142] If the first action that the terminal needs to execute is only for the uplink or downlink direction, then the downlink signaling can include uplink or downlink information.

[0143] If the downlink signaling does not include direction information, the terminal may determine the first action to be performed for the uplink and / or downlink directions based on default rules, policies, or protocol provisions.

[0144] Furthermore, the downlink signaling is also used for the terminal to determine a first object, wherein the first object corresponds to the first action, and the first object includes at least one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB. The QoS requirement is included in multiple sets of QoS requirements.

[0145] The specific content carried by the downlink signaling can be related to the first object, and examples are given below.

[0146] In one example, the first object is a terminal.

[0147] The downlink signaling may not carry QoS flow identification information, PDU session identification information, MAC entity identification information, or DRB identification information. Alternatively, if the first object is a terminal, the downlink signaling may carry at least one of the following: QoS flow identification information, PDU session identification information, DRB identification information, or MAC entity identification information.

[0148] Furthermore, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, QoS parameter, QoS parameter value, uplink direction information, and downlink direction information.

[0149] For example, if the first action required by the terminal is for the uplink direction, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling may or may not carry at least one of the following: QoS flow identification information, PDU session identification information, DRB identification information, and MAC entity identification information. The downlink signaling may carry uplink direction information, or it may not carry uplink direction information, meaning it defaults to the uplink direction. For instance, the downlink signaling may carry QoS requirement identification information and uplink direction information; or, the downlink signaling may carry the rate, the QoS parameter, the QoS parameter value, and uplink direction information.

[0150] For example, if the first action required by the terminal is for the downlink direction, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling may or may not carry at least one of the following: QoS flow identification information, PDU session identification information, DRB identification information, and MAC entity identification information. The downlink signaling may also carry downlink direction information. For instance, the downlink signaling may carry QoS requirement identification information and downlink direction information; or, the downlink signaling may carry the rate, the QoS parameter, the QoS parameter value, and downlink direction information.

[0151] For example, if the first action required by the terminal is for both downlink and uplink directions, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling may or may not carry at least one of the following: QoS flow identification information, PDU session identification information, DRB identification information, and MAC entity identification information. The downlink signaling may carry both uplink and downlink direction information, or it may not carry direction information, meaning it defaults to both uplink and downlink directions. For instance, the downlink signaling may carry QoS requirement identification information; or, the downlink signaling may carry rate, the QoS parameter, and the QoS parameter value; or, the downlink signaling may carry QoS requirement identification information, downlink direction information, and uplink direction information; or, the downlink signaling may carry rate, the QoS parameter, the QoS parameter value, downlink direction information, and uplink direction information.

[0152] This section does not limit or exhaustively list the possible contents carried by downlink signaling when the first object is a terminal.

[0153] In one example, the first object includes one or more QoS flows. Downlink signaling needs to carry identification information for the QoS flows.

[0154] In one scenario, the identification information for a QoS flow is the QoS flow's QFI and / or name and / or index.

[0155] In one scenario, the identification information of a QoS flow can be represented using a first bitmap.

[0156] The first bitmap includes the same number of bits as the number of QoS flows of the terminal, or the same number of specific QoS flows of the terminal. The specific QoS flow can be a QoS flow that is configured, indicated, or supports the first behavior. One QoS flow of the terminal corresponds to one bit in the first bitmap, and different QoS flows correspond to different bits in the first bitmap; for example, the first bit represents QoS flow 1 of the terminal, the second bit represents QoS flow 2 of the terminal, and so on.

[0157] When the corresponding bit of any QoS flow in the first bitmap is of the first value, it indicates that the QoS flow is included in the first object of the QoS flow; when the corresponding bit of any QoS flow in the first bitmap is of the second value, it indicates that the QoS flow is not included in the first object of the QoS flow. The first value and the second value are different; for example, the first value can be 1 and the second value can be 0, or vice versa, which is not limited here.

[0158] In this example, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, QoS parameter, QoS parameter value, QoS flow identification information, uplink direction information, and downlink direction information.

[0159] For example, if the first action required by the terminal is in the uplink direction, the downlink signaling can carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling carries the QoS flow identification information and can carry uplink direction information or not (i.e., the default uplink direction). For instance, the downlink signaling can carry the QoS requirement identification information, uplink direction information, and QoS flow identification information; or, the downlink signaling can carry the rate, the QoS parameter, the QoS parameter value, the QoS flow identification information, and uplink direction information; or, the downlink signaling can carry the rate, the QoS parameter, the QoS parameter value, and the QoS flow identification information, without carrying direction information, i.e., the default uplink direction.

[0160] For example, if the first action required by the terminal is in the downlink direction, the downlink signaling can carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling can also carry QoS flow identification information and downlink direction information. For instance, the downlink signaling can carry QoS requirement identification information, QoS flow identification information, and downlink direction information; or, the downlink signaling can carry rate, the QoS parameter, the QoS parameter value, QoS flow identification information, and downlink direction information.

[0161] For example, if the first action required by the terminal is directed towards both downlink and uplink directions, the downlink signaling can carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling also carries the QoS flow identification information. This downlink signaling may not carry direction information, meaning it can default to both uplink and downlink directions, or it may carry both uplink and downlink direction information. For instance, the downlink signaling can carry the QoS requirement identification information and the QoS flow identification information; or, the downlink signaling can carry the rate, the QoS parameter, the QoS parameter value, and the QoS flow identification information.

[0162] This section does not limit or exhaustively list the content that downlink signaling may carry when the first object is a QoS flow.

[0163] In one example, the first object includes one or more PDU sessions. The downlink signaling includes identification information of the PDU sessions. Optionally, the downlink signaling also includes identification information of the QoS flow corresponding to the PDU sessions.

[0164] In one scenario, the identification information for a PDU session can be the PDU session's ID and / or index.

[0165] In one scenario, the identification information of a PDU session can be represented using a second bitmap.

[0166] The second bitmap includes the same number of bits as the number of PDU sessions in the terminal, or the same number as the number of specific PDU sessions in the terminal. The specific PDU session can be a configured, indicated, or supportive PDU session. One PDU session in the terminal corresponds to one bit in the second bitmap, and different PDU sessions correspond to different bits in the second bitmap; for example, the first bit represents PDU session 1, the second bit represents PDU session 2, and so on.

[0167] When the bit corresponding to any PDU session in the second bit diagram takes the first value, it is used to indicate that the PDU session is included in the first object; when the bit corresponding to any PDU session in the second bit diagram takes the second value, it is used to indicate that the PDU session is not included in the first object.

[0168] In this example, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, QoS parameter, QoS parameter value, PDU session identification information, uplink direction information, and downlink direction information.

[0169] For example, if the first action required by the terminal is in the uplink direction, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling may also carry the PDU session identification information. Optionally, the downlink signaling may carry the QoS flow identification information, and may carry uplink direction information, or it may not carry uplink direction information, thus defaulting to the uplink direction. For instance, the downlink signaling may carry the QoS requirement identification information, uplink direction information, and PDU session identification information; or, the downlink signaling may carry the rate, the QoS parameter, the QoS parameter value, the PDU session identification information, and uplink direction information; or, the downlink signaling may carry the rate, the QoS parameter, the QoS parameter value, and the PDU session identification information (e.g., defaulting to the uplink direction).

[0170] For example, if the first action required by the terminal is in the downlink direction, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling may also carry the PDU session identification information. Optionally, the downlink signaling may carry the QoS flow identification information and downlink direction information. For instance, the downlink signaling may carry the QoS requirement identification information, the PDU session identification information, and downlink direction information; or, the downlink signaling may carry the rate, the QoS parameter, the QoS parameter value, the PDU session identification information, and downlink direction information.

[0171] For example, if the first action required by the terminal is for both downlink and uplink directions, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling may also carry the PDU session identification information. Optionally, the downlink signaling may carry the QoS flow identification information, uplink direction information, and downlink direction information, or it may not carry direction information, defaulting to uplink and downlink directions. For instance, the downlink signaling may carry the QoS requirement identification information and the PDU session identification information; or, the downlink signaling may carry the rate, the QoS parameter, the QoS parameter value, and the PDU session identification information.

[0172] This section does not limit or exhaustively list the possible contents carried by downlink signaling when the first object is a PDU session.

[0173] In one example, the first object includes one or more DRBs. Downlink signaling needs to carry identification information of the DRB. Optionally, the downlink signaling also includes identification information of the QoS flow corresponding to the DRB.

[0174] For example, the identification information of a DRB is its ID.

[0175] For example, the identification information of DRB can be represented using a third bitmap.

[0176] The third bitmap includes the same number of bits as the terminal's DRBs, or the same number as a specific DRB of the terminal. The specific DRB may be a configured, indicated, or DRB that supports the first action. One DRB of the terminal corresponds to one bit in the third bitmap, and different DRBs correspond to different bits in the third bitmap; for example, the first bit represents the terminal's DRB1, the second bit represents the terminal's DRB2, and so on.

[0177] When the bit corresponding to any DRB in the third bit diagram is of the first value, it is used to indicate that the DRB is a DRB included in the first object; when the bit corresponding to any DRB in the third bit diagram is of the second value, it is used to indicate that the DRB is not a DRB included in the first object.

[0178] In this example, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, QoS parameter, QoS parameter value, DRB identification information, QoS flow identification information, uplink direction information, and downlink direction information.

[0179] For example, if the first action required by the terminal is in the uplink direction, the downlink signaling can carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling can also carry DRB identification information, optionally carrying QoS flow identification information. The downlink signaling can carry uplink direction information or not (i.e., defaults to uplink direction). For instance, the downlink signaling can carry QoS requirement identification information, uplink direction information, and DRB identification information; or, the downlink signaling can carry rate, the QoS parameter, the QoS parameter value, DRB identification information, and uplink direction information; or, the downlink signaling can carry QoS requirement identification information, DRB identification information, and QoS flow identification information (defaults to uplink direction).

[0180] For example, if the first action to be performed by the terminal is in the downlink direction, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling may also carry DRB identification information, optionally carrying QoS flow identification information, and downlink direction information. For instance, the downlink signaling may carry QoS requirement identification information, DRB identification information, and downlink direction information; or, the downlink signaling may carry rate, the QoS parameter, the QoS parameter value, DRB identification information, and downlink direction information; or, the downlink signaling may carry rate, the QoS parameter, the QoS parameter value, DRB identification information, QoS flow identification information, and downlink direction information.

[0181] For example, if the first action required by the terminal is for both downlink and uplink directions, the downlink signaling can carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling can also carry DRB identification information. Optionally, the downlink signaling can carry QoS flow identification information, uplink direction information, and downlink direction information, or it can omit direction information, defaulting to uplink and downlink directions. For instance, the downlink signaling can carry QoS requirement identification information and DRB identification information; or, the downlink signaling can carry rate, the QoS parameter, the QoS parameter value, and DRB identification information; or, the downlink signaling can carry QoS requirement identification information, DRB identification information, QoS flow identification information, downlink direction information, and uplink direction information.

[0182] This section does not limit or exhaustively list the possible contents of downlink signaling when the first object is a DRB.

[0183] In one example, when the first object includes a MAC entity, the downlink signaling may or may not carry the identification information of the MAC entity. Optionally, the downlink signaling may also include the identification information of the PDU session corresponding to the MAC entity, and / or the identification information of the QoS flow corresponding to the MAC entity.

[0184] Downlink signaling may carry at least one of the following: QoS requirement identification information, rate, QoS parameters, QoS parameter values, MAC entity identification information, PDU session identification information, QoS flow identification information, uplink direction information, and downlink direction information.

[0185] For example, if the first action required by the terminal is in the uplink direction, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling may or may not carry the MAC entity identification information. Optionally, the downlink signaling may or may not carry the PDU session identification information and the QoS flow identification information. The downlink signaling may or may not carry uplink direction information (i.e., defaults to uplink direction). For instance, the downlink signaling may carry the QoS requirement identification information, uplink direction information, and MAC entity identification information; or, the downlink signaling may carry the rate, the QoS parameter, the QoS parameter value, the MAC entity identification information, and uplink direction information; or, the downlink signaling may carry the QoS requirement identification information and uplink direction information; or, the downlink signaling may carry the rate, the QoS parameter, the QoS parameter value, and uplink direction information; or, the downlink signaling may carry the rate, the QoS parameter, and the QoS parameter value (defaults to uplink direction).

[0186] For example, if the first action to be performed by the terminal is in the downlink direction, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, QoS parameter, and the value of the QoS parameter. The downlink signaling may or may not carry the identification information of the MAC entity. Optionally, the downlink signaling may or may not carry the identification information of the PDU session and the identification information of the QoS flow. The downlink signaling may carry downlink direction information. For example, the downlink signaling may carry the identification information of the QoS requirement, the identification information of the MAC entity, the identification information of the PDU session, the identification information of the QoS flow, and downlink direction information; or, the downlink signaling may carry the rate, the QoS parameter, the value of the QoS parameter, and downlink direction information.

[0187] For example, if the first action required by the terminal is directed towards both downlink and uplink directions, the downlink signaling may carry at least one of the following: QoS requirement identification information, rate, the QoS parameter, and the QoS parameter value. The downlink signaling may or may not carry MAC entity identification information. Optionally, the downlink signaling may or may not carry PDU session identification information and QoS flow identification information. The downlink signaling may carry uplink and downlink direction information, or may not carry direction information (i.e., defaults to uplink and downlink directions). For instance, the downlink signaling may carry QoS requirement identification information, MAC entity identification information, PDU session identification information, and QoS flow identification information; or, the downlink signaling may carry rate, the QoS parameter, and the QoS parameter value.

[0188] This section does not limit or exhaustively list the contents that the downlink signaling may carry when the first object is a MAC entity.

[0189] In one embodiment, before the access network device sends downlink signaling to the terminal, the method further includes: the access network device receiving first information reported by the terminal, wherein the first information is used to assist the access network device in selecting the QoS requirement. Correspondingly, before the terminal receives downlink signaling from the access network device, the method further includes: the terminal reporting first information to the access network device, wherein the first information is used to assist the access network device in selecting the QoS requirement.

[0190] The specific reason why the access network device needs to change the QoS requirements of the first object can be that the access network device receives the first information reported by the terminal, thereby enabling the access network device to select the QoS requirements of the first object that need to be changed this time based on the first information.

[0191] The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

[0192] The first information is carried by one of the following: uplink RRC message, uplink MAC CE, PUCCH (Physical Uplink Control Channel), or UCI (Uplink Control Information).

[0193] It should be noted that the above is only an exemplary description of the method of carrying the first information. In actual processing, the first information can also be carried by other messages or information. For example, the first information can be carried by new signaling; or the first information can be carried by existing signaling, such as UAI (User Association Identifier), BSR (Buffer Status Report) MAC CE, DSR (Data Status Report) MAC CE, data rate MAC CE, etc., without limitation or exhaustive list.

[0194] Optionally, the terminal and access network equipment may receive the first correspondence and / or the second correspondence in advance.

[0195] The first correspondence includes the correspondence between each group of QoS requirements and the first index in the multiple groups of QoS requirements.

[0196] The first index corresponding to different groups of QoS requirements is different. The first index corresponding to each group of QoS requirements may correspond to the priority of that group of QoS requirements, or be associated with the identification information of that group of QoS requirements, or be associated with that group of QoS requirements. It is referred to here as the first index corresponding to each group of QoS requirements, mainly to distinguish it from the identification information corresponding to each group of QoS requirements in the aforementioned embodiments. It should be emphasized that each group of QoS requirements can correspond to its own first index, and different groups of QoS requirements correspond to different first indices, which does not mean that each group of QoS requirements corresponds to the same index.

[0197] The second correspondence includes the correspondence between each group of QoS requirements and / or the first index corresponding to each group of QoS requirements and at least one of the following: service feature information, service experience score, service type, service identifier, and QoE indicator.

[0198] This second correspondence can be used by the terminal and / or access network equipment to determine the relationship between each set of QoS requirements and at least one of the following: service characteristic information, service experience score, service type, service identifier, and QoE indicator. For example, the terminal and / or access network equipment can determine at least one of the following: service characteristic information, service experience score, service type, service identifier, and QoE indicator corresponding to or associated with the terminal side (or the second object on the terminal side) based on the QoS requirements and / or the first index of the QoS requirements and the second correspondence; or, the terminal and / or access network equipment can determine the QoS requirements based on at least one of the following: service characteristic information, service experience score, service type, service identifier, and QoE indicator corresponding to or associated with the terminal side (or the second object on the terminal side), combined with the second correspondence.

[0199] This is merely an illustrative example of the second correspondence. In actual processing, the second correspondence may also include or be replaced by a correspondence between the identification information of each group of QoS requirements and at least one of the following: service characteristic information, service experience score, service type, service identifier, and QoE metric.

[0200] It should be noted that the QoS requirements of different groups and / or the first index of different groups of QoS requirements (and / or the identification information of different groups of QoS requirements) must differ in at least one of the following: service characteristic information, service experience score, service type, service identifier, and QoE indicator. In other words, the QoS requirements and / or indexes of different groups may correspond to at least one of the following: service characteristic information, service experience score, service type, service identifier, and QoE indicator for different states, different priorities, or different service states.

[0201] For example, the terminal's processing further includes: the terminal receiving a first correspondence and / or a second correspondence.

[0202] The terminal receiving the first correspondence and / or the second correspondence includes one of the following: the terminal receiving the first correspondence and / or the second correspondence from the access network device; the terminal receiving the first correspondence and / or the second correspondence from the core network element; the terminal receiving the first correspondence and / or the second correspondence from the AF (Application Function).

[0203] Optionally, if the terminal receives a first correspondence and / or a second correspondence from a core network element or an AF, the terminal may also send the first correspondence and / or the second correspondence to the access network device.

[0204] For example, the processing of the access network device further includes: the access network device receiving a first correspondence and / or a second correspondence.

[0205] The access network device receiving the first correspondence and / or the second correspondence includes one of the following: the access network device receiving the first correspondence and / or the second correspondence from the core network element; or the access network device receiving the first correspondence and / or the second correspondence from the AF.

[0206] Optionally, the core network element can be one of PCF, SMF, UPF, or AMF.

[0207] Optionally, after receiving the first and / or second correspondence, the access network device may send the first and / or second correspondence to the terminal. Correspondingly, the terminal receives the first and / or second correspondence from the access network device.

[0208] The specific reason or method by which the terminal determines the reporting of the first information to the access network device is not limited in this embodiment. The terminal may trigger or determine the reporting of the first information to the access network device based on rules, policies, protocols, or periodically. The content that such rules or policies may include is also not limited here, and the length of the period can be configured according to the actual situation and is not limited here.

[0209] For example, the terminal may perform the process of reporting the first information after receiving multiple sets of QoS requirements and / or receiving the first correspondence and / or the second correspondence.

[0210] For example, a terminal may not receive multiple sets of QoS requirements, first correspondence, and / or second correspondence. In this case, the terminal may determine the timing of execution of the first information based on actual needs, rules, policies, protocol provisions, or periodicity, without any restrictions here.

[0211] For example, a terminal can also report initial information upon receiving an instruction or request from the access network. For instance, the access network device can send a reporting instruction or request to the terminal, and after receiving the instruction or request, the terminal reports the initial information.

[0212] For example, a terminal can also report the first information if the conditions configured by the access network are met. For example, the conditions configured by the access network device for the terminal can be at least one of the following: configuration (reporting the first information based on the configuration), configuration but no reporting (configuration to report the first information but the terminal has not reported the first information), reaching the reporting period, prohibiting reporting timeout, etc.

[0213] The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than a threshold, energy-saving indication, energy-saving indication, overheating indication, no-overheating indication, number of MIMO (Multiple-Input Multiple-Output) layers, service characteristic information, service experience score, service type, service identifier, QoE (Quality of Experience) index, uplink information, and downlink information. The recommended or requested QoS requirements are included in multiple sets of QoS requirements.

[0214] The first information is also used by the access network device to determine a first object. The relevant description of the first object is the same as in the previous embodiments and will not be repeated. This embodiment also does not limit the specific method by which the terminal determines the first object.

[0215] The recommended or requested rate may include the rate of the first object recommended or requested by the terminal. This rate may include the data rate and / or bitrate. This rate may correspond to the uplink and / or downlink directions. The specific method by which the terminal determines the recommended or requested rate is not limited.

[0216] Recommended or requested QoS requirements may refer to the QoS requirements of a first object recommended or requested by the terminal, which are included in multiple sets of QoS requirements of the first object.

[0217] As described in the foregoing embodiments, the multiple QoS requirements configured on the terminal side can be granularized at any one of the following: terminal, QoS flow, PDU session, DRB, and MAC entity. In the case of multiple QoS requirements at different granularities, the content included in the multiple QoS requirements of the first object, and the QoS requirements of the first object recommended or requested by the terminal, are similar to the exemplary descriptions in the foregoing embodiments regarding the content included in the multiple QoS requirements of the first object, and the QoS requirements of the first object determined or adjusted by the access network device in the case of multiple QoS requirements at different granularities. Therefore, they will not be repeated.

[0218] The identification information of the recommended or requested QoS requirements can be included in multiple sets of QoS requirements received by the terminal, which will not be repeated here.

[0219] The first index corresponding to the recommended or requested QoS requirement can be determined by the terminal based on a pre-configured first correspondence.

[0220] The first correspondence relationship includes the correspondence between each group of QoS requirements and a first index in the multiple groups of QoS requirements. That is, different groups of QoS requirements received by the terminal correspond to different first indices. In this embodiment, after determining the recommended or requested QoS requirements, the terminal can determine the first index corresponding to the recommended or requested QoS requirements based on the first correspondence relationship.

[0221] Recommended or requested QoS parameters can be determined by the terminal based on recommended or requested QoS requirements and / or local policies, rules, or protocols, etc. The specific method by which the terminal determines recommended or requested QoS parameters is not limited here. The types of QoS parameters that may be included are the same as in the aforementioned embodiments and will not be elaborated upon further.

[0222] The descriptions of the QoS flow identification information, PDU session identification information, MAC entity identification information, and DRB identification information are the same as those in the previous embodiments and will not be repeated.

[0223] Latency can refer to at least one of the following: the current latency of the first object on the terminal side, the statistical average latency, the latency of the next data packet, the maximum tolerable latency, the remaining latency, etc.

[0224] The data volume may include at least one of the following: the average data volume of the first object on the terminal side, the data volume of each data packet, the data volume of the current data packet, the data volume of the next data packet, the statistical average data volume, the statistical or expected data volume over a period of time, and the data volume corresponding to the above-mentioned delay information.

[0225] The amount of data to be transmitted can refer to at least one of the following: the amount of data to be transmitted in the next data packet, the amount of data to be transmitted in all remaining data packets, the amount of statistical or estimated data over a period of time, or the amount of data corresponding to the aforementioned delay information.

[0226] Service characteristic information may include at least one of the following: TTNB (time to next burst) of the first object on the terminal side, jitter, service pattern, packet size, period, packet arrival time, etc.

[0227] Overheating indication, no-overheating indication, energy-saving indication, and no-energy-saving indication can be applied to the terminal.

[0228] Service experience scores can include MOS (Mean Opinion Score) as defined by relevant protocols of the International Telecommunication Union Telecommunication Standardization Sector (ITU-T), or Video MOS, or service experience scores can be customized MOS for any type of service unrelated to video or voice.

[0229] The business type can be one of the following: voice business, video business, other types of business, etc. We will not limit or exhaust all possible business types here.

[0230] The QoE metric can be the QoE metric corresponding to the first object. For example, the QoE metric includes at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

[0231] The explanations regarding the upward and downward direction information are the same as those in the aforementioned implementation method and will not be repeated.

[0232] For example, if the terminal receives multiple sets of QoS requirements, the first information may carry identification information of the recommended or requested QoS requirements.

[0233] For example, if the terminal receives the first correspondence and the second correspondence, the first information may carry the first index corresponding to the recommended or requested QoS requirements.

[0234] For example, if the terminal does not receive multiple sets of QoS requirements, does not receive the first correspondence and the second correspondence, and the terminal calculates the recommended or requested QoS parameter values ​​and / or rates, then the first information may carry at least one of the recommended or requested QoS parameters, the recommended or requested QoS parameter values, and the recommended or requested rates.

[0235] For example, if the terminal does not receive multiple sets of QoS requirements, does not receive the first correspondence and the second correspondence, and does not calculate the recommended or requested QoS parameter values, the first information may carry at least one of the following: latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, MIMO layer number, service characteristic information, service experience score, service type, service identifier, and QoE indicator.

[0236] For example, if the first object is a terminal, the first information may or may not carry the identification information of QoS flow, PDU session, MAC entity, and DRB.

[0237] For example, the first object includes one or more QoS flows. The first information needs to carry identification information of the QoS flows.

[0238] For example, the first object includes one or more PDU sessions. The first information includes identification information of the PDU sessions; optionally, the first information may include identification information of QoS flows.

[0239] For example, the first object includes one or more DRBs. The first information needs to carry the identification information of the DRB; optionally, the first information may include the identification information of the QoS flow.

[0240] For example, the first object includes a MAC entity, and the first information may or may not carry the identification information of the MAC entity; optionally, the first information may include the identification information of the QoS flow and / or the identification information of the PDU session.

[0241] For example, if the first information is directed to the upward direction, the first information may carry upward direction information or may not carry upward direction information (the upward direction can be the default); if the first information is directed to the downward direction, the first information may carry downward direction information; if the first information is directed to both the upward and downward directions, the first information may not carry direction information (the upward and downward directions are the default), or it may carry both upward and downward direction information.

[0242] It should be noted that the above is merely an exemplary description of the content that the first information may or may not carry under certain possible circumstances. In actual processing, as long as the first information includes at least one of the above contents, it is within the protection scope of this embodiment. Here, not all possible situations are limited or exhaustively listed.

[0243] The processing after the access network device receives the first information also includes: the access network device determining or determining the adjusted QoS requirements from multiple sets of QoS requirements based on the first information.

[0244] In this embodiment, the processing after the access network device receives the first information further includes: the access network device determining a first object based on the first information. Specifically, the access network device determining the first object may include: if the first information does not carry QoS flow identification information, PDU session identification information, MAC entity identification information, or DRB identification information, determining the first object as a terminal; if the first information carries QoS flow identification information, determining the QoS flow included in the first object based on the QoS flow identification; if the first information carries PDU session identification information, determining the PDU session included in the first object based on the PDU session identification information; if the first information carries DRB identification information, determining the DRB included in the first object based on the DRB identification information; if the first information carries MAC entity identification information, determining the MAC entity included in the first object based on the MAC entity identification information; if the first information does not carry MAC entity identification information, determining the MAC entity included in the first object based on the source of receiving the first information; if the first information does not carry QoS flow identification information, PDU session identification information, MAC entity identification information, or DRB identification information, determining the MAC entity included in the first object based on the source of receiving the first information.

[0245] The source of the first information may include which MCG or SCG it corresponds to. For example, based on the source of the first information, determining the MAC entity included in the first object can be: if the source of the first information is an MCG, then the first object includes the MAC entity corresponding to that MCG; if the source of the first information is an SCG, then the first object includes the MAC entity corresponding to that SCG.

[0246] The access network device determines or determines the adjusted QoS requirements from multiple sets of QoS requirements based on the first information. This may include: the access network device determining the QoS requirements recommended or requested by the terminal based on the first information; the access network device determining whether the QoS requirements used by the first object need to be changed based on the QoS requirements recommended or requested by the terminal and the QoS requirements currently used by the first object; and if a change is determined, determining or determining the adjusted QoS requirements of the first object from multiple sets of QoS requirements.

[0247] Here, the QoS requirements of the first object ultimately determined or adjusted by the access network device are included in multiple sets of QoS requirements; and the QoS requirements of the first object determined or adjusted can be the same as the QoS requirements recommended or requested by the terminal; or they can be further processed based on the QoS requirements recommended or requested by the terminal to determine the final QoS requirements used for the first object. No specific limitations are made here regarding the access network device's method of determining whether to change the QoS requirements used for the first object, or the method of ultimately determining or adjusting the QoS requirements of the first object.

[0248] The way the access network device determines the QoS requirements recommended or requested by the terminal based on the first information can be related to the actual content carried by the first information.

[0249] For example, the first piece of information carries identification information of the recommended or requested QoS requirements. Based on this identification information, the access network device can determine the QoS requirements recommended or requested by the terminal from multiple sets of QoS requirements.

[0250] For example, the first information carries a first index corresponding to the recommended or requested QoS requirements. The access network device can determine the QoS requirements recommended or requested by the terminal from multiple sets of QoS requirements based on the first index corresponding to the recommended or requested QoS requirements and the first correspondence.

[0251] For example, the first information carries at least one of the following: recommended or requested QoS parameters, recommended or requested QoS parameter values, and recommended or requested rates. The access network device determines the QoS requirements recommended or requested by the terminal based on at least one of the recommended or requested QoS parameters, recommended or requested QoS parameter values, and recommended or requested rates.

[0252] For example, the first information carries at least one of the following: latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy-saving indicator, non-energy-saving indicator, overheating indicator, non-overheating indicator, MIMO layer number, service characteristic information, service experience score, service type, service identifier, and QoE indicator. The access network device can determine the QoS requirements recommended or requested by the terminal from multiple sets of QoS requirements based on the second correspondence and at least one of the following carried in the first information: latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy-saving indicator, non-energy-saving indicator, overheating indicator, non-overheating indicator, MIMO layer number, service characteristic information, service experience score, service type, service identifier, and QoE indicator.

[0253] Here, we do not limit or exhaust all the possible contents that the first information may carry, or all the possibilities that the access network device may specifically determine the QoS requirements recommended or requested by the terminal.

[0254] Furthermore, the access network device sends the downlink signaling to the terminal when it determines or adjusts the QoS requirements from multiple sets of QoS requirements. The content that the downlink signaling may carry under different first objects and different directions is similar to that in the previous embodiments, and therefore will not be described again.

[0255] In some embodiments, the access network device sends the downlink signaling after determining or determining the adjusted QoS parameters and / or the values ​​of the QoS parameters.

[0256] The access network device determining or determining the adjusted QoS parameters and / or the QoS parameter values ​​can refer to the access network device determining the QoS parameters and / or QoS parameter values ​​of the currently used first object based on local configuration and / or the QoS requirements of the currently used first object; or, the access network device determining the adjusted QoS parameters and / or the adjusted QoS parameter values ​​of the first object based on local configuration and / or the adjusted QoS requirements of the first object; or, the access network device determining or determining the adjusted QoS parameters and / or QoS parameter values ​​of the first object based on the current state.

[0257] The methods for determining the first object and the related descriptions of the QoS requirements of the first object are the same as those in the previous embodiments. The methods for determining the QoS requirements of the first object currently in use, or the methods for determining the QoS requirements of the first object after adjustment, are the same as those in the previous embodiments and will not be repeated here.

[0258] The local configuration of the access network device may include the specific processing method for determining the QoS parameters and / or QoS parameter values ​​of the first object currently in use, or the processing method for the adjusted QoS parameters and / or adjusted QoS parameter values ​​of the first object, etc., which are not limited here.

[0259] The current state can refer to at least one of the following: the current load state of the access network device, the communication state between the access network device and the terminal, the data transmission state between the access network device and the terminal, the communication state between the access network device and various network elements, the data transmission state between the access network device and various network elements, or the communication or data transmission state between the access network device and other terminals. This document does not limit the method by which the access network device determines or adjusts the QoS parameters and values ​​of the first object based on the current state. As long as the access network device can determine or adjust the QoS parameters and values ​​of the first object based on protocols, rules, policies, and the current state, it falls within the protection scope of this embodiment.

[0260] It should be noted that in this embodiment, if the access network device determines the QoS parameters and / or adjusted QoS parameter values ​​of the first object based on its local configuration and the QoS requirements of the currently used or adjusted first object, then the access network device needs to execute the above scheme after receiving multiple sets of QoS requirements at any given time. If the access network device determines or determines the adjusted QoS parameters and / or QoS parameter values ​​of the first object based only on its local configuration or current state, then the access network device does not need to execute the above scheme after receiving multiple sets of QoS requirements at any given time.

[0261] In this embodiment, the downlink signaling includes or carries at least one of the following: the QoS parameter, the QoS parameter value, the QoS flow identification information, the PDU session identification information, the MAC entity identification information, the DRB identification information, the uplink direction information, and the downlink direction information.

[0262] The QoS parameter and the QoS parameter value may refer to the QoS parameter or QoS parameter value currently used for the first object as determined by the access network device, or the adjusted QoS parameter or QoS parameter value for the first object as determined by the access network device.

[0263] In this embodiment, the downlink signaling can also be used to determine the first object as well as the terminal.

[0264] The content that downlink signaling may carry under different first objects and different directions is similar to that in the previous embodiments. The difference is that in this embodiment, downlink signaling may not carry QoS requirement identification information, so it will not be described again.

[0265] In some embodiments, the access network device sends the downlink signaling when it determines or determines an adjusted rate.

[0266] The access network device determining the adjusted rate can refer to the following: the access network device determines the rate for the first object based on the local configuration and / or the QoS requirements and / or the QoS parameters or QoS parameter values ​​of the first object currently in use; or the access network device determines the adjusted rate for the first object based on the local configuration and / or the adjusted QoS requirements and / or the adjusted QoS parameters or adjusted QoS parameter values ​​of the first object; or the access network device determines or adjusts the rate based on the current state.

[0267] This rate can include data rate and / or bit rate. And this rate can correspond to the uplink and / or downlink directions.

[0268] The method for determining the QoS requirements of the first object, whether currently used or after modification, is the same as in the aforementioned embodiments and will not be described again. Similarly, the method for determining the QoS parameters or QoS parameter values ​​for the first object, whether currently used or after adjustment, is the same as in the aforementioned embodiments and will not be described again.

[0269] The local configuration of the access network device may include determining the specific processing method for the rate of the first object, or determining the processing method for the adjusted rate of the first object, etc., which is not limited here.

[0270] The description of the current state is the same as in the previous embodiments. The method by which the access network device determines or adjusts the rate based on the current state is not limited, as long as the access network device can determine or adjust the rate of the first object based on protocols, rules, policies, and the current state, it falls within the protection scope of this embodiment.

[0271] It should be noted that in this embodiment, if the access network device determines the QoS parameters and / or adjusted QoS parameter values ​​of the first object based on its local configuration and the QoS requirements of the first object currently used or adjusted, and then determines or adjusts the rate based on the QoS requirements and / or the QoS parameters or QoS parameter values ​​of the first object currently used, then the access network device needs to execute the above scheme after receiving multiple sets of QoS requirements at any given time. If the access network device determines or adjusts the rate only based on its local configuration or current state, then the access network device does not need to execute the above scheme after receiving multiple sets of QoS requirements at any given time.

[0272] In this embodiment, the downlink signaling includes or carries at least one of the following: rate, PDU session identification information, MAC entity identification information, DRB identification information, uplink direction information, and downlink direction information.

[0273] The rate is the rate determined by the aforementioned access network device for the first object, or the adjusted rate for the first object.

[0274] In this embodiment, the downlink signaling can also be used to determine the first object as well as the terminal.

[0275] The content that downlink signaling may carry under different first objects and different directions is similar to that in the previous embodiments. The difference is that in this embodiment, the downlink signaling may not carry QoS requirement identification information, QoS parameters, or QoS parameter values, so it will not be described again.

[0276] In one embodiment, when the access network device sends downlink signaling, it may also perform at least one of the following processes: the access network device performs radio resource scheduling based on the QoS requirements or the QoS parameter values; the access network device reports the QoS requirements or the QoS parameter values; the access network device configures or schedules transmission resources based on the rate.

[0277] The QoS requirement is the QoS requirement determined by the access network device in the aforementioned embodiments or the QoS requirement after adjustment, and will not be repeated here.

[0278] The QoS parameter values ​​are those determined or adjusted by the access network device in the aforementioned embodiments, and will not be elaborated here.

[0279] The QoS requirement reported by the access network device may include: the access network device reporting at least one of the following to the core network element: the identification information of the currently used QoS requirement, the identification information of the adjusted QoS requirement, the identification information of the QoS requirement used before the adjustment, the specific content of the currently used QoS requirement, the specific content of the adjusted QoS requirement, the specific content of the QoS requirement used before the adjustment, and the identification information of the first object.

[0280] The identification information of the first object may include one of the following: the terminal identifier, the QoS flow identification information, the MAC entity identification information, the DRB identification information, or the PDU session identification information. The specific identification information reported that is related to the first object will not be elaborated here.

[0281] Optionally, when selecting or determining QoS requirements for the first time, the access network device reports the identification information of the currently used QoS requirements and / or the specific content of the currently used QoS requirements to the core network element. In this case, the access network device may also report the identification information of the first object to the core network element.

[0282] Optionally, if the access network device has already determined the QoS requirements but needs to change them, the access network device may report at least one of the following to the core network element: the identification information of the adjusted QoS requirements, the identification information of the QoS requirements used before the adjustment, the specific content of the adjusted QoS requirements, the specific content of the QoS requirements used before the adjustment, and the identification information of the first object.

[0283] The QoS parameter value reported by the access network device may include: the access network device reporting at least one of the following to the core network element: the currently used QoS parameter value, the adjusted QoS parameter value, the QoS parameter value used before adjustment, the identification information of the first object, etc.

[0284] Optionally, when the access network device selects or determines the QoS parameters and their values ​​for the first time, it reports the currently used QoS parameters and their values ​​to the core network element. In this case, the access network device may also report the identification information of the first object to the core network element.

[0285] Optionally, if the access network device has already determined the QoS parameter value, but now needs to change the QoS parameter value, in this case, the access network device may report at least one of the following to the core network element: the adjusted QoS parameter value, the QoS parameter value used before the adjustment, and the identification information of the first object.

[0286] The access network device performs radio resource scheduling based on the QoS requirements or the QoS parameter values, and / or the access network device configures or schedules transmission resources based on the rate. This can be implemented by the access network device based on local rules, policies, or protocols, and is not limited here.

[0287] In some possible implementations, after receiving downlink signaling, the terminal can perform the first action based on the downlink signaling.

[0288] In this embodiment, after the terminal receives downlink signaling, the method further includes: the terminal determining a first object based on the downlink signaling, wherein the first object corresponds to the first action, and the first object includes one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB.

[0289] Based on downlink signaling, the terminal can determine the first object by including one of the following:

[0290] If the downlink signaling does not carry the identification information of QoS flow, PDU session, MAC entity, or DRB, the first object is identified as the terminal.

[0291] When the downlink signaling carries the identification information of the QoS flow, the QoS flow included in the first object is determined based on the identification of the QoS flow;

[0292] When the downlink signaling carries the identification information of the PDU session, the PDU session included in the first object is determined based on the identification information of the PDU session;

[0293] When the downlink signaling carries the identification information of the DRB, the DRB included in the first object is determined based on the identification information of the DRB;

[0294] When the downlink signaling carries the identification information of the MAC entity, the MAC entity included in the first object is determined based on the identification information of the MAC entity;

[0295] In the absence of identification information of MAC entities carried in the downlink signaling, the MAC entities included in the first object are determined based on the receiving source of the downlink signaling.

[0296] When the downlink signaling does not carry the identification information of QoS flow, PDU session, MAC entity, or DRB, the MAC entity included in the first object is determined based on the receiving source of the downlink signaling.

[0297] The source of downlink signaling reception can include MCG (Master Cell Group) or SCG (Secondary Cell Group). For example, based on the source of downlink signaling reception, the MAC entity included in the first object can be determined as follows: if the source of downlink signaling reception is MCG, the first object includes the MAC entity corresponding to that MCG; if the source of downlink signaling reception is SCG, the first object includes the MAC entity corresponding to that SCG.

[0298] In this embodiment, the first action performed by the terminal can be an action performed on a first object. Specifically, the first action includes at least one of the following: determining or adjusting the uplink rate of the first object, determining or adjusting the QoS parameters of the first object, or determining or adjusting the QoS requirements of the first object. The uplink rate may include the uplink bit rate and / or the uplink data rate.

[0299] It should be noted that if the terminal sends the first information to the access network device in advance, the terminal may or may not perform the process of determining the first object based on downlink signaling. This is because if the terminal sends the first information to the access network device in advance, the first information enables the access network device to determine the first object, and the downlink signaling issued thereafter is also for the first object. Therefore, the terminal may no longer determine the first object based on downlink signaling, or the terminal may perform the process of determining the first object based on downlink signaling again. Both are within the scope of protection of this embodiment and are not limited here.

[0300] In one embodiment, the terminal performing a first action based on downlink signaling may include: the terminal's AS submitting the downlink signaling to the terminal's higher layer; and the terminal's higher layer performing the first action based on the downlink signaling.

[0301] The AS (Access Stratum) of the terminal may submit the downlink signaling to the higher layer of the terminal in the following ways: the AS of the terminal extracts the specific content included in the downlink signaling and submits the specific content included in the downlink signaling to the higher layer of the terminal; or, the AS of the terminal directly forwards the received downlink signaling to the higher layer of the terminal; or, the AS of the terminal generates second information based on the downlink signaling and sends the second information to the higher layer of the terminal.

[0302] The second information may include at least the content of downlink signaling. The specific method by which the terminal's AS generates the second information can be configured according to actual circumstances or needs. For example, the terminal can add content from the downlink signaling to the second information and add specified content within the second information; this specified content can also be configured according to actual circumstances, and neither is limited here. Alternatively, the terminal's AS can add content from the downlink signaling to a preset format template to generate the second information. This preset format template may be pre-configured according to protocols or default rules, etc. It should be noted that this is merely an illustrative example, and the specific methods by which the terminal's AS generates the second information are not limited or exhaustively described here.

[0303] The higher layers of the terminal executing the first action based on the downlink signaling can refer to the higher layers of the terminal executing the first action based on the downlink signaling, the second information, or the specific content included in the downlink signaling. Since regardless of which specific information the higher layers of the terminal are based on for executing the first action, in essence, the higher layers of the terminal must at least execute the first action based on downlink signaling, the following description uses the term "the higher layers of the terminal executing the first action based on downlink signaling" for specific explanation, and will no longer describe the execution of the first action by the higher layers of the terminal based on downlink signaling, the second information, or the downlink signaling separately.

[0304] The higher layers of the terminal may include the terminal's NAS (None Access Stratum) and the terminal's application layer.

[0305] The higher layers of the terminal perform the first action based on the downlink signaling, including at least one of the following: the NAS of the terminal determines or adjusts QoS requirements based on the downlink signaling; the NAS of the terminal determines or adjusts QoS parameters based on the downlink signaling; the NAS of the terminal determines or adjusts the uplink rate based on the downlink signaling; the NAS of the terminal determines or adjusts the uplink rate based on the QoS requirements or the QoS parameters; the application layer of the terminal determines or adjusts QoS requirements based on the downlink signaling; the application layer of the terminal determines or adjusts QoS parameters based on the downlink signaling; the application layer of the terminal determines or adjusts the uplink rate based on the downlink signaling; the application layer of the terminal determines or adjusts the uplink rate based on the QoS requirements or the QoS parameters.

[0306] In one example, the NAS of the terminal performs a first action, which may specifically include at least one of the following: the NAS of the terminal determines or adjusts QoS requirements based on the downlink signaling; the NAS of the terminal determines or adjusts QoS parameters based on the downlink signaling; the NAS of the terminal determines or adjusts the uplink rate based on the downlink signaling; the NAS of the terminal determines or adjusts the uplink rate based on the QoS requirements or the QoS parameters.

[0307] In this example, the terminal's NAS can determine a first object based on downlink signaling and then perform at least one of the following: the terminal's NAS determines or adjusts QoS requirements based on the downlink signaling; the terminal's NAS determines or adjusts QoS parameters based on the downlink signaling; the terminal's NAS determines or adjusts the uplink rate based on the downlink signaling; or the terminal's NAS determines or adjusts the uplink rate based on the QoS requirements or the QoS parameters.

[0308] The method by which the NAS of this terminal determines the first object is the same as the method by which the terminal determines the first object in the aforementioned embodiments, and will not be described in detail here.

[0309] Optionally, the NAS of the terminal, based on the downlink signaling, determines or adjusts the QoS requirements, including: the NAS of the terminal, based on the identification information of the QoS requirements in the downlink signaling, determines or determines the adjusted QoS requirements from multiple sets of QoS requirements for the first object. Here, determining the QoS requirements may refer to (initial) determining the current QoS requirements of the first object; determining the adjusted QoS requirements refers to determining to change the QoS requirements used by the first object to the adjusted QoS requirements.

[0310] Optionally, the NAS of the terminal, based on the downlink signaling, determines or adjusts the QoS requirements, including: the NAS of the terminal determining or adjusting the QoS requirements from multiple sets of QoS requirements for the first object based on the identification information of the QoS requirements in the downlink signaling; and the NAS of the terminal determining the transmission direction corresponding to the QoS requirements based on the uplink direction information and / or downlink direction information in the downlink signaling. Determining the transmission direction corresponding to the QoS requirements may refer to determining whether to use the QoS requirements in the uplink and / or downlink transmissions of the first object.

[0311] Optionally, the NAS of the terminal, based on the downlink signaling, determines or adjusts the QoS parameters, including: the NAS of the terminal, based on the QoS parameters and QoS parameter values ​​in the downlink signaling, determines or determines the adjusted QoS parameters and QoS parameter values. Specifically, determining the QoS parameters and QoS parameter values ​​may refer to determining the QoS parameters and QoS parameter values ​​of the current first object; determining the adjusted QoS parameters and QoS parameter values ​​refers to determining to change the QoS parameters and QoS parameter values ​​of the currently used first object to the adjusted QoS parameters and QoS parameter values.

[0312] Optionally, the NAS of the terminal determines or adjusts the QoS parameters based on the downlink signaling, including: the NAS of the terminal determines or determines the adjusted QoS requirements based on the identification information of the QoS requirements in the downlink signaling; then the terminal determines or determines the adjusted QoS parameters and the values ​​of the QoS parameters based on the QoS requirements. The specific method by which the terminal determines or determines the adjusted QoS parameters and the values ​​of the QoS parameters based on the QoS requirements is not limited in this embodiment.

[0313] Optionally, the NAS of the terminal determines or adjusts the QoS parameters based on the downlink signaling, including: the NAS of the terminal determines or determines the adjusted QoS parameters and QoS parameter values ​​based on the QoS parameters and QoS parameter values ​​in the downlink signaling; the NAS of the terminal determines the QoS parameters and the transmission direction corresponding to the QoS parameter values ​​based on the uplink direction information and / or downlink direction information in the downlink signaling.

[0314] Optionally, the NAS of the terminal determines or adjusts the QoS parameters based on the downlink signaling, including: the NAS of the terminal determines or determines the adjusted QoS requirements based on the identification information of the QoS requirements in the downlink signaling; then the terminal determines or determines the adjusted QoS parameters and the values ​​of the QoS parameters based on the QoS requirements; the NAS of the terminal determines the QoS parameters and the transmission direction corresponding to the values ​​of the QoS parameters based on the uplink direction information and / or downlink direction information in the downlink signaling.

[0315] The NAS of the terminal determines or adjusts the uplink rate based on the downlink signaling, including: the NAS of the terminal determines or adjusts the uplink rate of the first object based on the rate in the downlink signaling. Determining the uplink rate of the first object can refer to determining the current uplink rate of the first object; adjusting the uplink rate of the first object refers to determining to change the rate currently used by the first object to the adjusted uplink rate of the first object.

[0316] It should be noted that the NAS of the terminal can also determine the downlink rate of the first object based on the rate included in the downlink signaling, and this is not limited here.

[0317] The NAS of the terminal determines or adjusts the uplink rate based on the QoS requirements or the QoS parameters, including: the NAS of the terminal determines or adjusts the uplink rate of the first object based on the QoS requirements or the QoS parameters of the first object. This embodiment does not limit how the NAS of the terminal specifically determines the uplink rate of the first object based on the QoS requirements or QoS parameters.

[0318] In this embodiment, the terminal's NAS can also notify the terminal's application layer of the QoS requirements and values ​​of the determined or adjusted first object, and / or the uplink rate of the determined or adjusted first object, so that the terminal's application layer can ultimately use the uplink rate of the first object for transmission.

[0319] In one example, the terminal's application layer may determine a first object based on downlink signaling and then perform at least one of the following: the terminal's application layer determines or adjusts QoS requirements based on the downlink signaling; the terminal's application layer determines or adjusts QoS parameters based on the downlink signaling; the terminal's application layer determines or adjusts uplink rates based on the downlink signaling; or the terminal's application layer determines or adjusts uplink rates based on the QoS requirements or the QoS parameters.

[0320] In this example, the terminal's application layer can determine a first object based on downlink signaling and then perform at least one of the following: the terminal's application layer determines or adjusts QoS requirements based on the downlink signaling; the terminal's application layer determines or adjusts QoS parameters based on the downlink signaling; the terminal's application layer determines or adjusts the uplink rate based on the downlink signaling; or the terminal's application layer determines or adjusts the uplink rate based on the QoS requirements or the QoS parameters.

[0321] Regarding the method by which the terminal's application layer determines the first object, the specific processing methods by which the terminal's application layer determines or adjusts QoS requirements, QoS parameters, and uplink rates are similar to those in the aforementioned embodiments and will not be repeated here.

[0322] In one example, the NAS layer of the terminal and the application layer of the terminal can interact to jointly perform the first action.

[0323] Optionally, the terminal's NAS can determine a first object based on downlink signaling, and then the terminal's NAS layer can perform at least one of the following: determine or adjust QoS requirements based on the downlink signaling; determine or adjust QoS parameters based on the downlink signaling. The terminal's NAS then submits the determined or adjusted QoS requirements and / or the determined or adjusted QoS parameters to the terminal's application layer, which determines or adjusts the uplink rate based on the QoS requirements or the QoS parameters.

[0324] Optionally, the terminal's NAS can determine a first object based on downlink signaling, and then the terminal's NAS layer can determine or adjust QoS requirements based on the downlink signaling. The terminal's NAS then delivers the determined or adjusted QoS requirements and / or downlink signaling to the terminal's application layer, which determines or adjusts the uplink rate based on the QoS requirements; alternatively, the terminal's application layer determines or adjusts QoS parameters based on downlink signaling, and then determines or adjusts the uplink rate based on the determined or adjusted QoS parameters; or alternatively, the terminal's application layer determines or adjusts the uplink rate based on downlink signaling.

[0325] Regarding the NAS and / or application layer of the terminal, the specific methods for determining the first object, determining or adjusting QoS requirements, determining or adjusting QoS parameters, and determining or adjusting uplink rates are similar to those in the aforementioned embodiments and will not be repeated here.

[0326] In one embodiment, the terminal performing a first action based on downlink signaling may include at least one of the following: the terminal's AS determines or adjusts QoS parameters based on the downlink signaling; the terminal's AS determines or adjusts QoS requirements based on the downlink signaling; the terminal's AS determines or adjusts the uplink rate based on the downlink signaling; the terminal's AS determines or adjusts the uplink rate based on the QoS parameters or QoS requirements; the terminal's application layer adjusts the uplink rate; or the terminal's AS or physical layer adjusts the uplink rate.

[0327] In this embodiment, the terminal's AS can determine the first object based on downlink signaling, and then perform the first action on the first object. The specific methods by which the terminal's AS determines the first object, and the processing methods for determining or adjusting QoS requirements, QoS parameters, and uplink rates, are similar to those in the previous embodiments and will not be repeated here.

[0328] Furthermore, the AS of the terminal may include at least one of the following protocol layers: MAC layer, PDCP (Packet Data Convergence Protocol) layer, SDAP (Service Data Adaptation Protocol) layer, and physical layer.

[0329] Taking the PDCP layer as an example, the AS of the terminal determines or adjusts QoS parameters based on the downlink signaling, which may include: the PDCP layer of the terminal determining or adjusting QoS parameters based on the downlink signaling; or, the PDCP layer of the terminal determining QoS parameters based on the downlink signaling and sending the QoS parameters to at least one of the MAC layer, SDAP layer, and physical layer of the terminal, and the QoS parameters being adjusted by at least one of the MAC layer, SDAP layer, and physical layer of the terminal; or, the PDCP of the terminal sending downlink signaling to at least one of the MAC layer, SDAP layer, and physical layer of the terminal, and the QoS parameters being determined or adjusted by at least one of the MAC layer, SDAP layer, and physical layer of the terminal based on the downlink signaling.

[0330] Taking the MAC layer as an example, the AS of the terminal determines or adjusts QoS parameters based on the downlink signaling, which may include: the MAC layer of the terminal determining or adjusting QoS parameters based on the downlink signaling; or, the MAC layer of the terminal determining QoS parameters based on the downlink signaling and sending the QoS parameters to at least one of the PDCP layer, SDAP layer, and physical layer of the terminal, and at least one of the PDCP layer, SDAP layer, and physical layer of the terminal adjusting the QoS parameters; or, the MAC layer of the terminal sending downlink signaling to at least one of the PDCP layer, SDAP layer, and physical layer of the terminal, and at least one of the PDCP layer, SDAP layer, and physical layer of the terminal determining or adjusting the QoS parameters based on the downlink signaling.

[0331] The above is merely an illustrative example. In the process of determining or adjusting QoS parameters based on downlink signaling, the processing that the various protocol layers included in the terminal's AS may perform is similar to the above example, and will not be elaborated here.

[0332] The examples of how the terminal's AS determines or adjusts QoS requirements based on downlink signaling, and how the terminal's AS determines or adjusts uplink rates based on downlink signaling, are similar to the examples of how the terminal's AS determines or adjusts QoS parameters based on downlink signaling mentioned above, and will not be repeated here.

[0333] Taking the PDCP layer as an example, the AS of the terminal determines or adjusts the uplink rate based on the QoS parameters or QoS requirements, which may include: the PDCP layer of the terminal determining or adjusting the uplink rate based on the QoS parameters or QoS requirements; or, the PDCP layer of the terminal determining the uplink rate of at least one of the MAC layer, SDAP layer, and physical layer based on the QoS parameters or QoS requirements, sending the uplink rate to at least one of the MAC layer, SDAP layer, and physical layer, and having at least one of the MAC layer, SDAP layer, and physical layer adjust the uplink rate; or, at least one of the MAC layer, SDAP layer, and physical layer of the terminal determining the uplink rate of the PDCP layer based on the QoS parameters or QoS requirements, and at least one of the MAC layer, SDAP layer, and physical layer of the terminal sending the uplink rate to the PDCP layer, and having the PDCP layer adjust the uplink rate.

[0334] Taking the MAC layer as an example, the AS of the terminal determines or adjusts the uplink rate based on the QoS parameters or QoS requirements, which may include: the MAC layer of the terminal determining or adjusting the uplink rate based on the QoS parameters or QoS requirements; or, the MAC layer of the terminal determining the uplink rate of at least one of the PDCP layer, SDAP layer, and physical layer based on the QoS parameters or QoS requirements, sending the uplink rate to at least one of the PDCP layer, SDAP layer, and physical layer, and having at least one of the PDCP layer, SDAP layer, and physical layer adjust the uplink rate; or, at least one of the PDCP layer, SDAP layer, and physical layer of the terminal determining the uplink rate of the MAC layer based on the QoS parameters or QoS requirements, and at least one of the PDCP layer, SDAP layer, and physical layer of the terminal sending the uplink rate to the MAC layer, and having the MAC layer adjust the uplink rate.

[0335] Taking the SPAP layer as an example, the AS of the terminal determines or adjusts the uplink rate based on the QoS parameters or QoS requirements, which may include: the SPAP layer of the terminal determining or adjusting the uplink rate based on the QoS parameters or QoS requirements; or, the SPAP layer of the terminal determining the uplink rate of at least one of the PDCP layer, MAC layer, and physical layer based on the QoS parameters or QoS requirements, and sending the uplink rate to at least one of the PDCP layer, MAC layer, and physical layer, and having at least one of the PDCP layer, MAC layer, and physical layer adjust the uplink rate; or, at least one of the PDCP layer, MAC layer, and physical layer of the terminal determining the uplink rate of the SDAP layer based on the QoS parameters or QoS requirements, and at least one of the MAC layer, PDCP layer, and physical layer of the terminal sending the uplink rate to the SDAP layer, and having the SDAP layer adjust the uplink rate.

[0336] The above is merely an illustrative example. In the process of determining or adjusting the uplink rate based on the QoS parameters or QoS requirements, the processes that the various protocol layers included in the terminal's AS may perform are similar to the above example, and will not be described in detail here.

[0337] The application layer of the terminal can adjust the uplink rate as follows: After the terminal's AS determines or obtains the adjusted uplink rate, it can send the uplink rate to the terminal's application layer, and then the application layer will perform the uplink rate adjustment process. The specific process of the terminal's AS determining the uplink rate is the same as in the previous example and will not be repeated here.

[0338] After the AS of the terminal determines or obtains the adjusted uplink rate, the AS or physical layer of the terminal can perform the process of adjusting the uplink rate.

[0339] For example, the physical layer of the terminal determines and adjusts the uplink rate based on downlink signaling; or, the physical layer of the terminal receives downlink signaling from at least one of the terminal's PDCP layer, MAC layer, and SDAP layer, and determines and adjusts the uplink rate based on the downlink signaling; or, the physical layer of the terminal receives the uplink rate sent from at least one of the terminal's MAC layer, SDAP layer, and PDCP layer, and performs the uplink rate adjustment process.

[0340] In this way, the terminal's AS does not need to submit the downlink signaling to higher layers such as NAS and / or application layer. The terminal's AS can directly execute the first line based on the downlink signaling, enabling the terminal to quickly obtain the downlink signaling from the access layer sent by the access network device. At least one of the QoS parameters, uplink rate, and QoS requirements can be determined or adjusted directly at the terminal's access layer. This reduces the interaction between the terminal's AS and higher layers and improves the adjustment efficiency on the terminal side.

[0341] The communication method provided in this embodiment will be described below with reference to the embodiments.

[0342] For each QoS data stream, the base station (access network equipment) receives multiple QoS profiles (QoS requirements) sent by the core network to the base station. When determining or changing the QoS profile to be used, the base station sends DL signaling to the UE (terminal).

[0343] The DL signaling is used to instruct the UE to determine or change QoS parameters, or to determine or change the data rate; or, the DL signaling is used by the UE to adjust QoS parameters or UL data rate.

[0344] The DL signaling can be DCI, RRC, or MAC CE.

[0345] The DL signaling can be for QoS flow, PDU session, MAC entity, or UE.

[0346] The DL signaling may carry one of the following information indicators: PDU session identifier (e.g., index, ID, or bitmap), QoS flow identifier (e.g., index, ID, or bitmap), direction information (UL / DL), bit rate, QoS profile identifier / index, QoS parameters (e.g., 5QI, ARP, bit rate, etc.), and the value of the QoS parameters.

[0347] Referring to Figure 4, the optional steps of the communication method provided in this embodiment will be described:

[0348] Step 401: The core network element sends QoS data stream information to the base station. The QoS data stream information is used to identify the QoS data stream, such as the QoS data stream identifier and name. Multiple sets of QoS requirements can be configured or indicated for a single QoS stream.

[0349] Step 402: The base station sends DL signaling to the UE. This includes at least one of the following:

[0350] 1) When determining or changing the QoS profile currently required, the base station behavior includes at least one of the following:

[0351] a) The base station sends DL signaling to the UE.

[0352] b) The base station performs radio resource scheduling based on the determined or changed QoS profile currently required.

[0353] c) The base station reports the QoS requirement information currently in use to the core network elements. This information may include some or all parameters from the QoS requirement information currently in use, or the identifier, index, name, etc. of the QoS requirement.

[0354] 2) The DL signaling is used to instruct the UE to determine or change QoS parameters, or to determine or change the data rate; or, the DL signaling is used by the UE to adjust QoS parameters or UL data rate.

[0355] 3) The DL signaling can be carried by DCI, RRC or MAC CE.

[0356] 4) The DL signaling can be for QoS flow, PDU session, MAC entity, or UE.

[0357] 5) The DL signaling may carry one of the following information indicators: PDU session identifier (e.g., index, ID, or bitmap), QoS flow identifier (e.g., index, ID, or bitmap), direction information (UL / DL), bit rate, QoS profile identifier / index, QoS parameters (e.g., 5QI, ARP, bit rate, etc.), and the value of the QoS parameters.

[0358] Step 403: Based on the received DL signaling, the UE determines the QoS parameters to be used, and / or adjusts / determines the UL rate (which may include the code rate). This includes at least one of the following:

[0359] 1) The UE AS interacts with the UE higher layer with information obtained from the DL signaling (direct information or derived information), or instructs the bit rate to be adjusted.

[0360] 2) The UE higher layer determines the QoS parameters to be used, and / or adjusts / determines the UL bit rate.

[0361] For example, the NAS layer determines QoS parameters, and / or the NAS layer notifies the APP of the QoS parameters;

[0362] For example, the APP receives lower-layer information (AS and / or NAS) to determine or adjust the UL bit rate.

[0363] By adopting the solution provided in this embodiment, the terminal can receive downlink signaling from the access network device. Based on this downlink signaling, it can perform at least one of determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements. This allows the terminal to quickly obtain downlink signaling from the access network device to determine or adjust at least one of the QoS parameters, uplink rate, or QoS requirements, improving the adjustment efficiency on the terminal side. This avoids the problems of low indication efficiency and impact on terminal communication quality caused by the method in related technologies where the access network needs to change QoS parameters or QoS requirements, requiring the access network to first notify the core network, and then the core network to notify the terminal for adjustment.

[0364] Figure 5 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0365] S510. The terminal reports first information to the access network device, wherein the first information is used to assist the access network device in selecting QoS requirements.

[0366] Figure 6 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0367] S610. The access network device receives first information reported by the terminal, wherein the first information is used to assist the access network device in selecting QoS requirements.

[0368] The method of carrying this first information is the same as in the aforementioned embodiments, and will not be described again.

[0369] In some possible implementations, the processing of the access network device may further include: the access network device receiving multiple sets of QoS requirements.

[0370] In one embodiment, a core network element configures multiple sets of QoS requirements for the access network device. This core network element can be a control plane element on the core network side, such as an SMF (Software-Defined Function), etc., and is not limited here.

[0371] In this embodiment, the core network element specifically refers to the access network device configuring multiple sets of QoS requirements, which is the same as in the aforementioned embodiment, and therefore will not be repeated.

[0372] Optionally, after receiving multiple QoS requirements from core network elements, the access network device can send these multiple QoS requirements to the terminal, or determine whether to configure multiple QoS requirements for the terminal based on actual conditions, protocols, or policies. The specific details are the same as in the aforementioned embodiments and will not be repeated here.

[0373] Optionally, core network elements can configure multiple QoS requirements for terminals based on actual conditions, protocols, or policies. The specific details are the same as in the aforementioned implementation methods and will not be repeated here.

[0374] In one embodiment, the terminal reports multiple sets of QoS requirements to the access network device.

[0375] In this embodiment, the terminal's processing further includes: the terminal receiving or determining multiple sets of QoS requirements.

[0376] Optionally, the core network elements configure multiple sets of QoS requirements for the terminal. The explanation regarding the core network elements configuring multiple sets of QoS requirements for the terminal is the same as in the aforementioned embodiments and will not be repeated here.

[0377] Optionally, multiple sets of QoS requirements can be configured through negotiation between the core network elements and the terminal. The explanation regarding the negotiation and configuration of multiple sets of QoS requirements between the core network elements and the terminal is the same as in the aforementioned embodiments and will not be repeated here.

[0378] Optionally, after receiving multiple sets of QoS requirements, the terminal can report multiple sets of QoS requirements to the access network device; correspondingly, the access network device receives the multiple sets of QoS requirements sent by the terminal.

[0379] In some possible implementations, the terminal and / or access network device may receive a first correspondence and / or a second correspondence in advance. The detailed description of the terminal and / or access network device receiving the first correspondence and / or the second correspondence, and the first and second correspondences themselves, is the same as in the foregoing embodiments and will not be repeated here.

[0380] In some possible implementations, the terminal reports the first information to the access network device.

[0381] The specific triggering reason or determination method for the terminal to report the first information to the access network device is the same as in the aforementioned embodiments, and will not be repeated here.

[0382] The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than a threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

[0383] The first information is also used by the access network device to determine a second object, the second object corresponding to the first information, and the second object includes one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB.

[0384] The second object can be an object that the terminal needs to adjust or report information to. This embodiment does not limit the specific way the terminal determines the second object.

[0385] The recommended or requested rate may include the rate of a second object recommended or requested by the terminal. This rate may include the data rate and / or bitrate. This rate may correspond to the uplink and / or downlink directions. The specific method by which the terminal determines the recommended or requested rate is not limited.

[0386] Recommended or requested QoS requirements may refer to the QoS requirements of a second object recommended or requested by the terminal, which are included in multiple sets of QoS requirements of the second object.

[0387] As described in the foregoing embodiments, the multiple QoS requirements configured on the terminal side can be granularized at any one of the following: terminal, QoS flow, PDU session, DRB, and MAC entity. In the case of multiple QoS requirements at different granularities, the content of the multiple QoS requirements of the second object, and the QoS requirements of the second object recommended or requested by the terminal, are similar to the exemplary descriptions in the foregoing embodiments regarding the content of the multiple QoS requirements of the first object, and the QoS requirements of the first object determined or adjusted by the access network device in the case of multiple QoS requirements at different granularities. Therefore, they will not be repeated.

[0388] The identification information of the recommended or requested QoS requirements can be included in multiple sets of QoS requirements received by the terminal, which will not be repeated here.

[0389] The first index corresponding to the recommended or requested QoS requirement can be determined by the terminal based on a pre-configured first correspondence.

[0390] The first correspondence relationship includes the correspondence between each group of QoS requirements and a first index in the multiple groups of QoS requirements. That is, different groups of QoS requirements received by the terminal correspond to different first indices. In this embodiment, after determining the recommended or requested QoS requirements, the terminal can determine the first index corresponding to the recommended or requested QoS requirements based on the first correspondence relationship.

[0391] Recommended or requested QoS parameters can be determined by the terminal based on recommended or requested QoS requirements and / or local policies, rules, or protocols, etc. The specific method by which the terminal determines recommended or requested QoS parameters is not limited here. The types of QoS parameters that may be included are the same as in the aforementioned embodiments and will not be elaborated upon further.

[0392] The descriptions of the QoS flow identification information, PDU session identification information, MAC entity identification information, and DRB identification information are the same as those in the previous embodiments and will not be repeated.

[0393] Latency can refer to at least one of the following: the current latency of the second object on the terminal side, the statistical average latency, the latency of the next data packet, the maximum tolerable latency, the remaining latency, etc.

[0394] The data volume may include at least one of the following: the average data volume of the second object on the terminal side, the data volume of each data packet, the data volume of the current data packet, the data volume of the next data packet, the statistical average data volume, the statistical or expected data volume over a period of time, and the data volume corresponding to the above-mentioned delay information.

[0395] The amount of data to be transmitted can refer to at least one of the following: the amount of data to be transmitted in the next data packet, the amount of data to be transmitted in all remaining data packets, the amount of statistical or estimated data over a period of time, or the amount of data corresponding to the aforementioned delay information.

[0396] Service characteristic information may include at least one of the following: TTNB (time to next burst) of the second object on the terminal side, jitter, service pattern, packet size, period, packet arrival time, etc.

[0397] Overheating indication, no-overheating indication, energy-saving indication, and no-energy-saving indication can be applied to the terminal.

[0398] Service experience scores can include MOS (Mean Opinion Score) as defined by relevant protocols of the International Telecommunication Union Telecommunication Standardization Sector (ITU-T), or Video MOS, or service experience scores can be customized MOS for any type of service unrelated to video or voice.

[0399] The business type can be one of the following: voice business, video business, other types of business, etc. We will not limit or exhaust all possible business types here.

[0400] The QoE metric can be the QoE metric corresponding to the second object. For example, the QoE metric includes at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

[0401] The explanations regarding the upward and downward direction information are the same as those in the aforementioned implementation method and will not be repeated.

[0402] For example, if the terminal receives multiple sets of QoS requirements, the first information may carry identification information of the recommended or requested QoS requirements.

[0403] For example, if the terminal receives the first correspondence and the second correspondence, the first information may carry the first index corresponding to the recommended or requested QoS requirements.

[0404] For example, if the terminal does not receive multiple sets of QoS requirements, does not receive the first correspondence and the second correspondence, and the terminal calculates the recommended or requested QoS parameter values ​​and / or rates, then the first information may carry at least one of the recommended or requested QoS parameters, the recommended or requested QoS parameter values, and the recommended or requested rates.

[0405] For example, if the terminal does not receive multiple sets of QoS requirements, does not receive the first correspondence and the second correspondence, and does not calculate the recommended or requested QoS parameter values, the first information may carry at least one of the following: latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, MIMO layer number, service characteristic information, service experience score, service type, service identifier, and QoE indicator.

[0406] For example, if the second object is a terminal, the first information may or may not carry the identification information of the QoS flow, the identification information of the PDU session, the identification information of the MAC entity, and the identification information of the DRB.

[0407] For example, the second object includes one or more QoS flows. The first information needs to carry identification information for the QoS flows.

[0408] For example, the second object includes one or more PDU sessions. The first information includes identification information of the PDU sessions; optionally, the first information may include identification information of QoS flows.

[0409] For example, the second object includes one or more DRBs. The first information needs to carry the identification information of the DRB; optionally, the first information may include the identification information of the QoS flow.

[0410] For example, the second object includes a MAC entity, and the first information may or may not carry the identification information of the MAC entity; optionally, the first information may include the identification information of the QoS flow and / or the identification information of the PDU session.

[0411] For example, if the first information is directed to the upward direction, the first information may carry upward direction information or may not carry upward direction information (the upward direction can be the default); if the first information is directed to the downward direction, the first information may carry downward direction information; if the first information is directed to both the upward and downward directions, the first information may not carry direction information (the upward and downward directions are the default), or it may carry both upward and downward direction information.

[0412] It should be noted that the above is merely an exemplary description of the content that the first information may or may not carry under certain possible circumstances. In actual processing, as long as the first information includes at least one of the above contents, it is within the protection scope of this embodiment. Here, not all possible situations are limited or exhaustively listed.

[0413] In some possible implementations, the processing after the access network device receives the first information further includes: the access network device determining, based on the first information, at least one of the following: changing the used QoS requirements, not changing the used QoS requirements, using QoS requirements, configuring or scheduling transmission resources, adjusting the transmission rate, or exchanging the transmission rate with the core network element or AF.

[0414] In this embodiment, the processing after the access network device receives the first information further includes: the access network device determining a second object based on the first information, wherein the second object includes one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB. The second object can be the object corresponding to the action performed by the access network device, and / or the object corresponding to the first information.

[0415] Specifically, the access network device may determine the second object as follows: if the first information does not carry QoS flow identification information, PDU session identification information, MAC entity identification information, or DRB identification information, determine the second object as a terminal; if the first information carries QoS flow identification information, determine the QoS flow included in the second object based on the QoS flow identification; if the first information carries PDU session identification information, determine the PDU session included in the second object based on the PDU session identification information; if the first information carries DRB identification information, determine the DRB included in the second object based on the DRB identification information; if the first information carries MAC entity identification information, determine the MAC entity included in the second object based on the MAC entity identification information; if the first information does not carry MAC entity identification information, determine at least the MAC entities included in the second object based on the receiving source of the first information; if the first information does not carry QoS flow identification information, PDU session identification information, MAC entity identification information, or DRB identification information, determine the MAC entities included in the second object based on the receiving source of the first information.

[0416] The source of the first information may include which MCG or SCG it corresponds to. For example, based on the source of the first information, determining the MAC entity included in the second object can be: if the source of the first information is an MCG, then the second object includes the MAC entity corresponding to that MCG; if the source of the first information is an SCG, then the second object includes the MAC entity corresponding to that SCG.

[0417] In this embodiment, the actions performed by the access network device can be performed on the second object. Specifically, based on the first information, the access network device determines at least one of the following: changing the QoS requirements used by the second object, not changing the QoS requirements used by the second object, applying QoS requirements to the second object, configuring or scheduling the transmission resources of the second object, adjusting the transmission rate of the second object, or exchanging the transmission rate of the second object with the core network or AF.

[0418] For example, the access network device determines the QoS requirements recommended or requested by the terminal based on the first information; the access network device determines whether the QoS requirements used by the second object need to be changed based on the QoS requirements recommended or requested by the terminal and the QoS requirements currently used by the second object; if it is determined that a change is needed, the QoS requirements are applied to the second object; if it is determined that a change is not needed, the QoS requirements used by the second object are not changed.

[0419] Here, the QoS requirements that the access network device ultimately uses for the second object can be the same as the QoS requirements recommended or requested by the terminal; or it can be further processed based on the QoS requirements recommended or requested by the terminal to determine the final QoS requirements used for the second object. No restrictions are placed here on the specific methods by which the access network device determines whether to change the QoS requirements used for the second object, or on the methods by which the final QoS requirements are determined.

[0420] The way the access network device determines the QoS requirements recommended or requested by the terminal based on the first information can be related to the actual content carried by the first information.

[0421] For example, the first piece of information carries identification information of the recommended or requested QoS requirements. Based on this identification information, the access network device can determine the QoS requirements recommended or requested by the terminal from multiple sets of QoS requirements.

[0422] For example, the first information carries a first index corresponding to the recommended or requested QoS requirements. The access network device can determine the QoS requirements recommended or requested by the terminal from multiple sets of QoS requirements based on the first index corresponding to the recommended or requested QoS requirements and the first correspondence.

[0423] For example, the first information carries at least one of the following: recommended or requested QoS parameters, recommended or requested QoS parameter values, and recommended or requested rates. The access network device determines the QoS requirements recommended or requested by the terminal based on at least one of the recommended or requested QoS parameters, recommended or requested QoS parameter values, and recommended or requested rates.

[0424] For example, the first information carries at least one of the following: latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy-saving indicator, non-energy-saving indicator, overheating indicator, non-overheating indicator, MIMO layer number, service characteristic information, service experience score, service type, service identifier, and QoE indicator. The access network device can determine the QoS requirements recommended or requested by the terminal from multiple sets of QoS requirements based on the second correspondence and at least one of the following carried in the first information: latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy-saving indicator, non-energy-saving indicator, overheating indicator, non-overheating indicator, MIMO layer number, service characteristic information, service experience score, service type, service identifier, and QoE indicator.

[0425] Here, we do not limit or exhaust all the possible contents that the first information may carry, or all the possibilities that the access network device may specifically determine the QoS requirements recommended or requested by the terminal.

[0426] Furthermore, when the access network device changes or uses QoS requirements, it may also include: the access network device performing radio resource scheduling based on the QoS requirements; and / or the access network device configuring or scheduling transmission resources (or transmission resources of a second object) based on the QoS requirements.

[0427] For example, the access network device determines the rate recommended or requested by the terminal based on the first information; the access network device determines whether it is necessary to change the transmission rate used by the second object based on the recommended or requested rate and the transmission rate currently used by the second object, and adjusts the transmission rate used by the second object if it is determined to change it.

[0428] Here, the access network device may ultimately use the same transmission rate for the second object as the rate recommended or requested by the terminal; or it may further process the data based on the recommended or requested rate to determine the final transmission rate used for the second object. No specific limitations are imposed here regarding the access network device's method for determining whether to change the transmission rate used for the second object, or the method for ultimately determining the transmission rate.

[0429] The way the access network device determines the rate recommended or requested by the terminal based on the first information can be related to the actual content carried by the first information.

[0430] For example, the first piece of information carries the recommended or requested rate. The access network device can directly extract this recommended or requested rate.

[0431] For example, the first information carries a first index corresponding to the recommended or requested QoS requirements. The access network device can determine the terminal's recommended or requested QoS requirements from multiple sets of QoS requirements based on the first index and the first correspondence, and determine the terminal's recommended or requested rate based on the QoS requirements.

[0432] For example, the first information carries at least one of the following: recommended or requested QoS parameters, recommended or requested QoS parameter values, and recommended or requested rates. The access network device determines the QoS requirements recommended or requested by the terminal based on at least one of the recommended or requested QoS parameters, recommended or requested QoS parameter values, and recommended or requested rates, and determines the rates recommended or requested by the terminal based on the QoS requirements.

[0433] For example, the first information carries at least one of the following: latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy-saving indicator, non-energy-saving indicator, overheating indicator, non-overheating indicator, MIMO layer number, service characteristic information, service experience score, service type, service identifier, and QoE indicator. The access network device can, based on the second correspondence and at least one of the following carried in the first information (latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy-saving indicator, non-energy-saving indicator, overheating indicator, non-overheating indicator, MIMO layer number, service characteristic information, service experience score, service type, service identifier, and QoE indicator), determine the QoS requirements recommended or requested by the terminal from multiple sets of QoS requirements, and determine the rate recommended or requested by the terminal based on the QoS requirements.

[0434] Here, we do not limit or exhaust all the possible contents that the first information may carry, or all the possibilities for the access network device to specifically determine the rate recommended or requested by the terminal.

[0435] Furthermore, when the access network device adjusts the transmission rate, it may also include: the access network device configuring or scheduling transmission resources (or the transmission resources of the second object) based on the transmission rate, and / or exchanging the transmission rate (or the transmission rate of the second object) with the core network element or AF.

[0436] Optionally, after the access network device changes or uses QoS requirements and / or adjusts the transmission rate, it can also send downlink signaling to the terminal. The function of the downlink signaling and the related processing of the terminal receiving the downlink signaling are the same as the processing of the embodiments involved in Figures 2 to 4 above, and will not be described again here.

[0437] The communication method provided in this embodiment will be described below with reference to the embodiments.

[0438] In this embodiment, the UE (terminal) reports first information to the base station (access network equipment), and the first information is used to assist the base station in changing or selecting a suitable QoS profile (i.e., QoS requirements).

[0439] The first information can be carried in UL RRC, UL MAC CE, or PUCCH. For example, new signaling, UAI, BSR MAC CE, DSR MAC CE, data rate MAC CE, service information (such as TTNB, jitter).

[0440] The first piece of information can be for QoS flow, PDU session, MAC entity, or UE.

[0441] The first information may carry one of the following information indicators: PDU session identifier (e.g., index, ID, or bitmap), QoS flow identifier (e.g., index, ID, or bitmap), direction information (UL / DL), recommended or requested bit rate, identifier / index of recommended or requested QoS profile, recommended or requested QoS parameters (e.g., 5QI, ARP, bit rate, etc.), value of recommended or requested QoS parameters, and first index (one index corresponds to one QoS profile).

[0442] Referring to Figure 7, the optional steps of the communication method provided in this embodiment will be described:

[0443] Step 701: The core network element sends QoS data stream information to the base station. The QoS data stream information is used to identify the QoS data stream, such as the QoS data stream identifier and name. Multiple sets of QoS requirements can be configured or indicated for a single QoS stream.

[0444] Step 702: The UE reports first information to the base station, which is used to assist the base station in changing or selecting a suitable QoS profile (i.e., QoS requirements).

[0445] 1) The first information can be carried in UL RRC, UL MAC CE, or PUCCH. For example, the first information can be carried in new signaling or existing signaling (such as UAI, BSR MAC CE, DSR MAC CE, data rate MAC CE, etc.).

[0446] 2) The first information can be for QoS flow, PDU session, MAC entity, UE, or DRB.

[0447] 3) The first information may carry at least one of the following: PDU session identifier (e.g., index, ID, or bitmap), QoS flow identifier (e.g., index, ID, or bitmap), direction information (UL / DL), recommended or requested bit rate, identifier / index of recommended or requested QoS profile, recommended or requested QoS parameters (e.g., 5QI, ARP, bit rate, etc.), value of recommended or requested QoS parameters, first index (one index corresponds to one QoS profile), service characteristic information (e.g., TTNB, jitter, service pattern, packet size, period), latency, data volume, whether energy saving, whether overheating, number of MIMO layers, service experience score, service type, and service identifier.

[0448] a) If the information carried is a first index or QoS profile, the UE determines or obtains the correspondence between the QoS profile and the index through NAS information or through the interaction between the UE APP and the AF, or the correspondence between the index / profile and the service experience score, service type, service identifier, service feature information, and QoE indicator.

[0449] b) If the information carried is the first index or QoS profile, the UE obtains multiple sets of QoS requirements for a QoS flow through the NAS information.

[0450] c) Service experience score: e.g. MOS or video MOS as specified in ITU-T P.1203.3

[0011] or a customized MOS for any kind of service including those not related to video or voice (MOS as specified in the relevant protocol of the International Telecommunication Union Telecommunication Standardization Sector (ITU-T), or Video MOS, or a customized MOS for any type of service unrelated to video or voice).

[0451] d) QoE metrics: such as throughput, average throughput, initial playback latency, cache status, cache level, list of user start / stop operations, and user wait time for media to start.

[0452] Step 703: Optionally, the base station receives the first information reported by the UE. Based on the first information, it determines whether to change the required QoS requirements, or determines the current QoS requirements to be used.

[0453] Step 704: Perform radio resource scheduling based on the determined QoS requirements.

[0454] By adopting the solution provided in this embodiment, the terminal can report first information to the access network device, which can be used by the access network device to determine QoS requirements. This allows the access network device to adjust or select QoS requirements based on the information reported by the terminal, ensuring that network resource scheduling on the network side matches the user experience on the terminal side. This avoids the inconsistency between network resource scheduling and user experience satisfaction caused by the network side sequentially trying available QoS requirements based on order (e.g., priority order) without considering the terminal's state, as seen in related technologies.

[0455] Figure 8 is a schematic diagram of the composition structure of an access network device according to an embodiment of this application, including:

[0456] The first communication unit 801 is configured to send downlink signaling to the terminal, wherein the downlink signaling is used by the terminal to perform a first action, the first action including at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

[0457] The downlink signaling includes or carries at least one of the following: the identification information of the QoS requirement, the rate, the QoS parameter, the value of the QoS parameter, the identification information of the QoS flow, the identification information of the PDU session, the identification information of the MAC entity, the identification information of the DRB, the uplink direction information, and the downlink direction information.

[0458] The downlink signaling is also used for the terminal to determine a first object, wherein the first object corresponds to the first action, and the first object includes at least one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB.

[0459] The first communication unit is configured to perform one of the following: sending the downlink signaling to the terminal when determining or adjusting the QoS requirements from multiple sets of QoS requirements; sending the downlink signaling to the terminal when determining or adjusting the QoS parameters and / or the values ​​of the QoS parameters; and sending the downlink signaling to the terminal when determining or adjusting the rate.

[0460] The first communication unit is configured to receive first information reported by the terminal, wherein the first information is used to assist the access network device in selecting the QoS requirements.

[0461] The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

[0462] As shown in Figure 8, the access network device also includes a first processing unit 802.

[0463] The first processing unit 802 is configured to perform at least one of the following: perform radio resource scheduling based on the QoS requirements or the QoS parameter values; configure or schedule transmission resources based on the rate.

[0464] And / or, the first communication unit is used to report the QoS requirement or the QoS parameter value.

[0465] The first communication unit is used to receive the multiple sets of QoS requirements.

[0466] The first communication unit is used to receive a first correspondence and / or a second correspondence.

[0467] The first correspondence includes the correspondence between each group of QoS requirements and the first index in the multiple groups of QoS requirements.

[0468] The second correspondence includes the correspondence between each group of QoS requirements and / or the first index corresponding to each group of QoS requirements and at least one of the following: service feature information, service experience score, service type, service identifier, and QoE indicator.

[0469] The downlink signaling is carried by one of the following: DCI, downlink RRC message, or downlink MAC CE.

[0470] In one embodiment, the access network device includes:

[0471] The first communication unit is used to receive first information reported by the terminal, wherein the first information is used to assist the access network device in selecting QoS requirements.

[0472] The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

[0473] The first processing unit is configured to determine, based on the first information, at least one of the following: change the QoS requirements used, do not change the QoS requirements used, use the QoS requirements, configure or schedule transmission resources, adjust the transmission rate, or interact with the transmission rate to the core network element or AF.

[0474] The first processing unit is configured to determine a second object based on the first information, wherein the second object includes one of the following: the terminal, the QoS stream, the PDU session, the MAC entity, and the DRB.

[0475] The first communication unit is used to receive the multiple sets of QoS requirements.

[0476] The first communication unit is used to receive a first correspondence and / or a second correspondence.

[0477] The first correspondence includes the correspondence between each group of QoS requirements and the first index in the multiple groups of QoS requirements.

[0478] The second correspondence includes the correspondence between each group of QoS requirements and / or the first index corresponding to each group of QoS requirements and at least one of the following: service feature information, service experience score, service type, service identifier, and QoE indicator.

[0479] The first communication unit is configured to perform one of the following: receive a first correspondence and / or a second correspondence from a core network element; or receive a first correspondence and / or a second correspondence from an AF.

[0480] The first information is carried by one of the following: uplink RRC message, uplink MAC CE, PUCCH, UCI.

[0481] Figure 9 is a schematic diagram of the composition structure of a terminal according to an embodiment of this application, including:

[0482] The second communication unit 901 is used to receive downlink signaling sent by the access network equipment;

[0483] The second processing unit 902 is configured to perform a first action based on the downlink signaling, wherein the first action includes at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

[0484] The downlink signaling includes or carries at least one of the following: the identification information of the QoS requirement, the rate, the QoS parameter, the value of the QoS parameter, the identification information of the QoS flow, the identification information of the PDU session, the identification information of the MAC entity, the identification information of the DRB, uplink direction information, and downlink direction information, wherein the QoS requirement is included in multiple sets of QoS requirements.

[0485] The second communication unit is used to report first information to the access network device, wherein the first information is used to assist the access network device in selecting the QoS requirements.

[0486] The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

[0487] The second communication unit is used to receive or determine the multiple sets of QoS requirements.

[0488] The second communication unit is used to receive the first correspondence and / or the second correspondence.

[0489] The first correspondence includes the correspondence between each group of QoS requirements and the first index in the multiple groups of QoS requirements.

[0490] The second correspondence includes the correspondence between each group of QoS requirements and / or the first index corresponding to each group of QoS requirements and at least one of the following: service feature information, service experience score, service type, service identifier, and QoE indicator.

[0491] The second processing unit is configured to determine a first object based on the downlink signaling, wherein the first object corresponds to the first action, and the first object includes one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB.

[0492] The second processing unit is used for the AS to submit the downlink signaling to the higher layer; and to execute the first action based on the downlink signaling.

[0493] The second processing unit is configured to perform at least one of the following: NAS determines or adjusts QoS requirements based on the downlink signaling; NAS determines or adjusts QoS parameters based on the downlink signaling; NAS determines or adjusts uplink rate based on the downlink signaling; NAS determines or adjusts uplink rate based on the QoS requirements or the QoS parameters; the application layer determines or adjusts QoS requirements based on the downlink signaling; the application layer determines or adjusts QoS parameters based on the downlink signaling; the application layer determines or adjusts uplink rate based on the downlink signaling; the application layer determines or adjusts uplink rate based on the QoS requirements or the QoS parameters.

[0494] The second processing unit is configured to perform at least one of the following: the AS determines or adjusts QoS parameters based on the downlink signaling; the AS determines or adjusts QoS requirements based on the downlink signaling; the AS determines or adjusts the uplink rate based on the downlink signaling; the AS determines or adjusts the uplink rate based on the QoS parameters or QoS requirements; the application layer adjusts the uplink rate; the AS or the physical layer adjusts the uplink rate.

[0495] The downlink signaling is carried by one of the following: DCI, downlink RRC message, or downlink MAC CE.

[0496] In one embodiment, the terminal includes:

[0497] The second communication unit is used to report first information to the access network device, wherein the first information is used to assist the access network device in selecting QoS requirements.

[0498] The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

[0499] The first information is also used by the access network device to determine a second object, the second object including one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB.

[0500] The second communication unit is used to receive or determine the multiple sets of QoS requirements.

[0501] The second communication unit is used to receive the first correspondence and / or the second correspondence.

[0502] The first correspondence includes the correspondence between each group of QoS requirements and the first index in the multiple groups of QoS requirements.

[0503] The second correspondence includes the correspondence between each group of QoS requirements and / or the first index corresponding to each group of QoS requirements and at least one of the following: service feature information, service experience score, service type, service identifier, and QoE indicator.

[0504] The second communication unit is configured to perform one of the following: receive a first correspondence and / or a second correspondence from an access network device; receive a first correspondence and / or a second correspondence from a core network element; or receive a first correspondence and / or a second correspondence from an AF.

[0505] The first information is carried by one of the following: uplink RRC message, uplink MAC CE, PUCCH, UCI.

[0506] The device in this application embodiment can realize the corresponding functions of the devices in the foregoing configuration method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in this device can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the device of this application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0507] Figure 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of this application. The communication device 1000 includes a processor 1010, which can call and run computer programs from a memory to enable the communication device 1000 to implement the methods in the embodiments of this application. In one possible implementation, the communication device 1000 may further include a memory 1020. The processor 1010 can call and run computer programs from the memory 1020 to enable the communication device 1000 to implement the methods in the embodiments of this application. The memory 1020 may be a separate device independent of the processor 1010, or it may be integrated into the processor 1010. In one possible implementation, the communication device 1000 may further include a transceiver 1030, which the processor 1010 can control to communicate with other devices. Specifically, it can send information or data to other devices, or receive information or data sent by other devices. The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include antennas, and the number of antennas may be one or more.

[0508] In one possible implementation, the communication device 1000 may be a terminal or an access network device in the embodiments of this application, and the communication device 1000 may implement the corresponding processes implemented by the terminal or the access network device in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0509] Figure 11 is a schematic structural diagram of a chip 1100 according to an embodiment of this application. The chip 1100 includes a processor 1110, which can call and run computer programs from memory to implement the methods in the embodiments of this application. In one possible implementation, the chip 1100 may further include a memory 1120. The processor 1110 can call and run computer programs from the memory 1120 to implement the methods executed by the first terminal, the first core network element, or the second core network element in the embodiments of this application. The memory 1120 may be a separate device independent of the processor 1110, or it may be integrated into the processor 1110. In one possible implementation, the chip 1100 may further include an input interface 1130. The processor 1110 can control the input interface 1130 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips. In one possible implementation, the chip 1100 may further include an output interface 1140. The processor 1110 can control the output interface 1140 to communicate with other devices or chips, specifically, it can output information or data to other devices or chips.

[0510] In one possible implementation, the chip can be applied to the terminal or access network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal or access network device in the various methods of the embodiments of this application. For simplicity, these will not be elaborated further here. It should be understood that the chip mentioned in the embodiments of this application can also be called a system-on-a-chip, system-on-a-chip, chip system, or system-on-chip, etc. The processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above can be a microprocessor or any conventional processor, etc. The memory mentioned above can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM). It should be understood that the above-described memory is exemplary but not limiting. For example, the memory in the embodiments of this application can also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. In other words, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0511] Figure 12 is a schematic block diagram of a communication system 1200 according to an embodiment of this application. The communication system 1200 includes a terminal 1210 and an access network device 1220. The terminal 1210 can be used to implement the corresponding functions implemented by the terminal in the above-described method. The access network device 1220 can be used to implement the corresponding functions implemented by the access network device in the above-described method.

[0512] 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. This computer program product includes one or more computer instructions. When these 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 accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0513] It should be understood that in the various embodiments of this application, the sequence number of each process 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. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. The above descriptions are merely specific embodiments 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 technical scope 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, comprising: The access network device sends downlink signaling to the terminal, wherein the downlink signaling is used for the terminal to perform a first action, the first action including at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

2. The method according to claim 1, wherein, The downlink signaling includes or carries at least one of the following: the identification information of the QoS requirement, the rate, the QoS parameter, the value of the QoS parameter, the identification information of the QoS flow, the identification information of the PDU session, the identification information of the MAC entity, the identification information of the DRB, the uplink direction information, and the downlink direction information.

3. The method according to claim 2, wherein, The downlink signaling is also used for the terminal to determine a first object, wherein the first object corresponds to the first action, and the first object includes at least one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB.

4. The method according to claim 2 or 3, wherein, The access network device sends downlink signaling to the terminal, including one of the following: When the access network device determines or determines the adjusted QoS requirements from multiple sets of QoS requirements, it sends the downlink signaling to the terminal. When the access network device determines or determines the adjusted QoS parameters and / or the values ​​of the QoS parameters, it sends the downlink signaling to the terminal. When the access network device determines or determines the adjusted rate, it sends the downlink signaling to the terminal.

5. The method according to claim 4, wherein, Before the access network device sends downlink signaling to the terminal, it also includes: The access network device receives first information reported by the terminal, wherein the first information is used to assist the access network device in selecting the QoS requirements.

6. The method according to claim 5, wherein, The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

7. The method according to any one of claims 4-6, further comprising at least one of the following: The access network device performs wireless resource scheduling based on the QoS requirements or the QoS parameter values. The access network device reports the QoS requirement or the QoS parameter value; The access network device configures or schedules transmission resources based on the rate.

8. The method according to any one of claims 4-7, further comprising: The access network device receives the multiple sets of QoS requirements.

9. The method according to claim 8, further comprising: The access network device receives the first correspondence and / or the second correspondence.

10. The method according to claim 9, wherein, The first correspondence includes the correspondence between each group of QoS requirements and the first index in the multiple groups of QoS requirements.

11. The method according to claim 9, wherein, The second correspondence includes the correspondence between each group of QoS requirements and / or the first index corresponding to each group of QoS requirements and at least one of the following: service feature information, service experience score, service type, service identifier, and QoE indicator.

12. The method according to any one of claims 1-11, wherein, The downlink signaling is carried by one of the following: DCI, downlink RRC message, or downlink MAC CE.

13. A communication method, comprising: The access network device receives first information reported by the terminal, wherein the first information is used to assist the access network device in selecting QoS requirements.

14. The method according to claim 13, wherein, The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

15. The method of claim 14, further comprising: Based on the first information, the access network device determines at least one of the following: changes the QoS requirements used, does not change the QoS requirements used, uses the QoS requirements, configures or schedules transmission resources, adjusts the transmission rate, or interacts with the core network element or AF to change the transmission rate.

16. The method according to claim 14 or 15, further comprising: The access network device determines a second object based on the first information, wherein the second object includes one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB.

17. The method according to any one of claims 14-16, further comprising: The access network device receives the multiple sets of QoS requirements.

18. The method of claim 17, further comprising: The access network device receives the first correspondence and / or the second correspondence.

19. The method of claim 18, wherein, The first correspondence includes the correspondence between each group of QoS requirements and the first index in the multiple groups of QoS requirements.

20. The method of claim 18, wherein, The second correspondence includes the correspondence between each group of QoS requirements and / or the first index corresponding to each group of QoS requirements and at least one of the following: service feature information, service experience score, service type, service identifier, and QoE indicator.

21. The method of any one of claims 18-20, wherein, The access network device receives a first correspondence and / or a second correspondence, including one of the following: The access network device receives a first correspondence and / or a second correspondence from the core network element; The access network device receives a first correspondence and / or a second correspondence from the AF.

22. The method according to any one of claims 13-21, wherein, The first information is carried by one of the following: uplink RRC message, uplink MAC CE, PUCCH, UCI.

23. A communication method, comprising: The terminal receives downlink signaling sent by the access network equipment; The terminal performs a first action based on the downlink signaling, wherein the first action includes at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

24. The method according to claim 23, wherein, The downlink signaling includes or carries at least one of the following: the identification information of the QoS requirement, the rate, the QoS parameter, the value of the QoS parameter, the identification information of the QoS flow, the identification information of the PDU session, the identification information of the MAC entity, the identification information of the DRB, uplink direction information, and downlink direction information, wherein the QoS requirement is included in multiple sets of QoS requirements.

25. The method according to claim 24, wherein, Before the terminal receives downlink signaling sent by the access network device, it also includes: The terminal reports first information to the access network device, wherein the first information is used to assist the access network device in selecting the QoS requirements.

26. The method according to claim 25, wherein, The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

27. The method according to any one of claims 24-26, further comprising: The terminal receives or determines the multiple sets of QoS requirements.

28. The method of claim 27, further comprising: The terminal receives the first correspondence and / or the second correspondence.

29. The method according to claim 28, wherein, The first correspondence includes the correspondence between each group of QoS requirements and the first index in the multiple groups of QoS requirements.

30. The method according to claim 28, wherein, The second correspondence includes the correspondence between each group of QoS requirements and / or the first index corresponding to each group of QoS requirements and at least one of the following: service feature information, service experience score, service type, service identifier, and QoE indicator.

31. The method of claim 24, further comprising: The terminal determines a first object based on the downlink signaling, wherein the first object corresponds to the first action, and the first object includes one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB.

32. The method according to any one of claims 23-31, wherein, Based on the downlink signaling, the terminal performs a first action, including: The AS of the terminal submits the downlink signaling to the higher layers of the terminal; The higher layers of the terminal execute the first action based on the downlink signaling.

33. The method according to claim 32, wherein, The higher layers of the terminal perform the first action based on the downlink signaling, including at least one of the following: The NAS of the terminal determines or adjusts QoS requirements based on the downlink signaling; The NAS of the terminal determines or adjusts QoS parameters based on the downlink signaling; The NAS of the terminal determines or adjusts the uplink rate based on the downlink signaling. The NAS of the terminal determines or adjusts the uplink rate based on the QoS requirements or the QoS parameters. The application layer of the terminal determines or adjusts QoS requirements based on the downlink signaling; The application layer of the terminal determines or adjusts QoS parameters based on the downlink signaling; The application layer of the terminal determines or adjusts the uplink rate based on the downlink signaling; The application layer of the terminal determines or adjusts the uplink rate based on the QoS requirements or the QoS parameters.

34. The method according to any one of claims 23-31, wherein, The terminal performs a first action based on the downlink signaling, including at least one of the following: The terminal's AS determines or adjusts QoS parameters based on the downlink signaling; The terminal's AS determines or adjusts QoS requirements based on the downlink signaling; The AS of the terminal determines or adjusts the uplink rate based on the downlink signaling; The AS of the terminal determines or adjusts the uplink rate based on the QoS parameters or QoS requirements; The application layer of the terminal adjusts the uplink rate; The AS or physical layer of the terminal adjusts the uplink rate.

35. The method according to any one of claims 23-34, wherein, The downlink signaling is carried by one of the following: DCI, downlink RRC message, or downlink MAC CE.

36. A communication method, comprising: The terminal reports first information to the access network device, wherein the first information is used to assist the access network device in selecting QoS requirements.

37. The method of claim 36, wherein, The first information includes or carries at least one of the following: recommended or requested rate, identification information of recommended or requested QoS requirements, a first index corresponding to the recommended or requested QoS requirements, recommended or requested QoS parameters, values ​​of recommended or requested QoS parameters, identification information of QoS flows, identification information of PDU sessions, identification information of MAC entities, identification information of DRBs, latency, remaining latency, data volume, data volume to be transmitted, data volume with latency less than the latency threshold, energy saving indication, energy saving indication, overheating indication, no overheating indication, number of MIMO layers, service characteristic information, service experience score, service type, service identifier, QoE index, uplink direction information, and downlink direction information, wherein the recommended or requested QoS requirements are included in multiple sets of QoS requirements.

38. The method according to claim 37, wherein, The first information is also used by the access network device to determine a second object, the second object including one of the following: the terminal, the QoS flow, the PDU session, the MAC entity, and the DRB.

39. The method according to claim 37 or 38, further comprising: The terminal receives or determines the multiple sets of QoS requirements.

40. The method of claim 39, further comprising: The terminal receives the first correspondence and / or the second correspondence.

41. The method according to claim 40, wherein, The first correspondence includes the correspondence between each group of QoS requirements and the first index in the multiple groups of QoS requirements.

42. The method according to claim 41, wherein, The second correspondence includes the correspondence between each group of QoS requirements and / or the first index corresponding to each group of QoS requirements and at least one of the following: service feature information, service experience score, service type, service identifier, and QoE indicator.

43. The method according to any one of claims 40-42, wherein, The terminal receives a first correspondence and / or a second correspondence, including one of the following: The terminal receives a first correspondence and / or a second correspondence from the access network device; The terminal receives a first correspondence and / or a second correspondence from the core network elements; The terminal receives a first correspondence and / or a second correspondence from the AF.

44. The method according to any one of claims 36-43, wherein, The first information is carried by one of the following: uplink RRC message, uplink MAC CE, PUCCH, UCI.

45. An access network device, comprising: The first communication unit is configured to send downlink signaling to the terminal, wherein the downlink signaling is used by the terminal to perform a first action, the first action including at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

46. ​​An access network device, comprising: The first communication unit is used to receive first information reported by the terminal, wherein the first information is used to assist the access network device in selecting QoS requirements.

47. A terminal, comprising: The second communication unit is used to receive downlink signaling sent by the access network equipment; The second processing unit is configured to perform a first action based on the downlink signaling, wherein the first action includes at least one of the following: determining or adjusting the uplink rate, determining or adjusting QoS parameters, or determining or adjusting QoS requirements.

48. A terminal, comprising: The second communication unit is used to report first information to the access network device, wherein the first information is used to assist the access network device in selecting QoS requirements.

49. An access network device comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for calling and running the computer program stored in the memory to cause the access network device to perform the method as claimed in any one of claims 1 to 12, or claims 13 to 22.

50. A terminal comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for calling and running the computer program stored in the memory to cause the terminal to perform the method as described in any one of claims 23 to 35 or 36 to 44.

51. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as described in any one of claims 1 to 12, or claims 13 to 22, or claims 23 to 35, or claims 36 to 44.

52. A computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the method as described in any one of claims 1 to 12, or claims 13 to 22, or claims 23 to 35, or claims 36 to 44.

53. A computer program product comprising computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 12, or claims 13 to 22, or claims 23 to 35, or claims 36 to 44.

54. A computer program that causes a computer to perform the method as described in any one of claims 1 to 12, or claims 13 to 22, or claims 23 to 35, or claims 36 to 44.

Images