Communication method and device

Abstract

The present application relates to a communication method and device. The method comprises: a terminal sending experience information for a first service, wherein the experience information for the first service is used by a network device to adjust a QoS (quality of service) parameter of the first service.

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 relevant QoS parameters for QoS flows is determined by the core network, and access network devices schedule radio resources based on these parameters. However, with the current QoS control mechanism, only the network side can unilaterally configure QoS parameters, which cannot guarantee that network-side QoS control aligns with service requirements. Summary of the Invention

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

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

[0005] The terminal sends experience information for the first service, which is used by the network device to adjust the QoS parameters of the first service.

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

[0007] The first core network element receives experience information of the first service, wherein the experience information of the first service is used by the first core network element to adjust the QoS parameters of the first service.

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

[0009] The access network device receives experience information of a first service, wherein the experience information of the first service is used by the access network device to adjust the QoS parameters of the first service.

[0010] This application provides a terminal, including:

[0011] The first communication unit is used to send experience information of the first service, wherein the experience information of the first service is used by the network device to adjust the QoS parameters of the first service.

[0012] This application provides a first core network element, including:

[0013] The second communication unit is used to receive experience information of the first service, wherein the experience information of the first service is used by the first core network element to adjust the QoS parameters of the first service.

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

[0015] The third communication unit is used to receive experience information of the first service, wherein the experience information of the first service is used by the access network device to adjust the QoS parameters of the first service.

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

[0017] This application provides a first core network element, 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 first core network element to perform the aforementioned method.

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

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

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

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

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

[0023] By adopting the above approach, terminals can report their experience information for a specific service, enabling network devices to adjust the QoS parameters for that service. This ensures that the network side can obtain subjective experiences or evaluations of a service, thereby allowing for reasonable adjustments to QoS parameters and better aligning network-side QoS control with service requirements. Attached Figure Description

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

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

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

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

[0028] Figures 5 to 7 are various schematic flowcharts of a communication method according to an embodiment of this application.

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

[0030] Figure 9 is a schematic block diagram of a first core network element according to an embodiment of the present application.

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

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

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

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

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

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

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

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

[0039] 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 control plane 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.

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

[0041] S210, The terminal sends experience information of the first service, wherein the experience information of the first service is used by the network device to adjust the QoS parameters of the first service.

[0042] The network equipment includes one of the following: a first core network element, or an access network device.

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

[0044] S310. The first core network element receives experience information of the first service, wherein the experience information of the first service is used by the first core network element to adjust the QoS parameters of the first service.

[0045] Figure 4 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.

[0046] S410. The access network device receives experience information of a first service, wherein the experience information of the first service is used by the access network device to adjust the QoS parameters of the first service.

[0047] In some possible examples, "business" can also be replaced by "application." In the following text, "business" and "application" have the same meaning and will not be explained again.

[0048] The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the QoE (Quality of Experience) metric of the first service.

[0049] The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

[0050] A filter may include at least one of the following: source IP (Internet Protocol) address, destination IP address, source port number, destination port number, source MAC (Media Access Control) address, and destination MAC address.

[0051] For example, when the data stream corresponding to the first service transmits IP type data, the data stream filter corresponding to the first service may include at least one of the following: the source IP address of the data stream corresponding to the first service, the destination IP address of the data stream corresponding to the first service, the source port number of the data stream corresponding to the first service, and the destination port number of the data stream corresponding to the first service.

[0052] For example, when the data stream corresponding to the first service transmits data of Ethernet type or Ethernet type, the data stream filter corresponding to the first service may include at least one of the following: the source MAC address of the data stream corresponding to the first service, and the destination MAC address of the data stream corresponding to the first service.

[0053] Data flow identifiers can be represented as SDF (Service Data Flow) IDs.

[0054] The first service type can be any one of multiple service types; multiple service types may include voice services, video services, other types of services, etc., and not all possible service types are limited or exhaustively listed here.

[0055] Experience scores can include Mean Opinion Score (MOS) or Video MOS as defined by relevant protocols of the International Telecommunication Union Telecommunication Standardization Sector (ITU-T), or they can be customized MOS for any type of service unrelated to video or voice. For example, the first service can be a voice or video service, and its experience score can be the MOS or Video MOS obtained according to the relevant ITU-T protocols; or, the first service can be any type of service unrelated to video or voice, and its experience score can be the MOS obtained according to a pre-configured or customized method.

[0056] The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

[0057] Throughput can include throughput per unit time and / or average throughput. Throughput per unit time refers to the amount of data that can be transmitted within a unit of time, reflecting the instantaneous data transmission rate. The unit of time can be bits per second (bps), kilobits per second (Kbps), megabits per second (Mbps), or gigabits per second (Gbps), etc. Average throughput is the average throughput over a first time period. This first time period can be configured according to actual conditions, such as a day, a month, or a longer or shorter period; it is not limited here.

[0058] Throughput can include throughput within a second duration and / or average throughput. Throughput within a second duration can be the total amount of data transmitted within that duration, which can be configured according to actual conditions, such as one hour, longer, or shorter. Average throughput refers to the average throughput over a specified period. Specifically, average throughput can be the average of the throughput over N second durations contained within the specified period, divided by the number of second durations (N). N can be an integer greater than or equal to 2. The specified period can be configured according to actual conditions, and its duration can be longer than the second duration.

[0059] Initial playback latency is the time interval from when the user triggers a playback operation (such as clicking the play button) to when the media content actually begins to play in a media playback scenario (such as video, audio, etc.).

[0060] Cache status refers to the current state of the cache used to store media data in the terminal. Cache is used to pre-store a portion of data to cope with network fluctuations or data transmission delays, ensuring smooth media playback. Cache status may include any of the following: whether the cache is full, the amount of data already stored in the cache, and the cache's update status.

[0061] Cache level is a quantitative description or classification of cache status. Different cache levels can indicate different amounts of data stored in the cache. For example, a low cache level may indicate that there is less data in the cache, while a high cache level may indicate that there is more data stored in the cache. This is not a limited or exhaustive list.

[0062] The start / stop operation list is a detailed list recording user actions to start and stop media content (such as video, audio, applications, etc.). The start / stop operation list may include at least one of the following: the timestamp of the operation (i.e., the specific time the user performed the operation), the type of operation (whether it was a start or a stop), and the object of the operation (which specific media content or application).

[0063] The startup wait time can be the waiting time for a user to start media playback. Specifically, it refers to the length of time a user is willing to wait for the media to start playing after triggering the media startup operation.

[0064] It should be noted that the above are only some of the indicators or parameters that the QoE metric may include. In actual processing, the QoE metric may include more possible parameters or indicators, such as packet loss rate, jitter (used to indicate the change in the time interval between data packet arrivals), stuttering rate, etc. There is no limit or exhaustive list of all the parameters or indicators that the QoE metric may include.

[0065] In some possible implementations, the network device is a first core network element, which may include a PCF (Policy Control Function). It should be understood that the first core network element may also include other network elements on the core network side, which are not limited or exhaustively listed here.

[0066] In some embodiments, before the first core network element receives the experience information of the first service, it may include: the first core network element receiving the QoS requirements corresponding to the first service sent by the AF (Application Function); the first core network element determining the PCC (Policy and Charging Control) rules of the first service based on the QoS requirements corresponding to the first service; and the first core network element sending the PCC rules of the first service to the second core network element.

[0067] The AF's processing may include: the AF sending the QoS requirement corresponding to the first service to the first core network element.

[0068] The processing of the second core network element may include: the second core network element receiving the PCC rules of the first service sent by the first core network element. The second core network element may include SMF (Session Management Function). It should be understood that the second core network element may also include other network elements on the core network side, which are not limited or exhaustively listed here.

[0069] When the AF sends the QoS requirement corresponding to the first service to the first core network element, it also sends the relevant identification information of the first service. In other words, the QoS requirement corresponding to the first service received by the first core network element from the AF specifically includes: the relevant identification information of the first service received by the first core network element from the AF, and the QoS requirement corresponding to the first service associated with the relevant identification information.

[0070] 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 QoS requirements.

[0071] The relevant identification information of the first business can also be called the relevant identification information of the first business data stream, or the relevant identification information of the data stream corresponding to the first business, or the business identification information of the first business data stream, etc., without limitation or exhaustive list.

[0072] In some preferred examples, the relevant identification information for the first service may include the IP 5-tuple of the data stream corresponding to the first service. The IP 5-tuple may include: source IP address, destination IP address, source port number, destination port number, and protocol number. In some possible examples, the relevant identification information for the first service may include the data stream identifier corresponding to the first service.

[0073] It should be noted that the above are all exemplary descriptions of relevant identification information. In actual processing, the relevant identification information of the first service may also be other content. For example, it may be any one of the four-tuple (such as source IP address, destination IP address, source port number, destination port number) or the seven-tuple (such as source IP address, destination IP address, protocol number, source port, destination port, service type, interface index) of the data stream corresponding to the first service. As long as the relevant identification information of the first service sent by AF to the first core network element can enable the first core network element to uniquely identify the first service, it is within the protection scope of this embodiment. Here, the specific composition or specific content of the relevant identification information is not limited or exhaustively listed.

[0074] It is important to understand that the content sent by the AF to the first core network element may include, but is not limited to, the relevant identification information of the first service and its associated QoS requirements. It may also include the relevant identification information of each of one or more other services and the corresponding QoS requirements. The descriptions of the relevant identification information and QoS requirements of each other service are the same as those of the first service, and therefore will not be elaborated upon. For example, the AF sends the following to the first core network element: relevant identification information (IP 5-tuple a) of service data flow a (or the data flow corresponding to service a (the first service)), with a QoS requirement of 5QI=1 and a code rate requirement of GBR=2Mbps; and relevant identification information (IP 5-tuple b) of service data flow b (or the data flow corresponding to service b (another service)), with a QoS requirement of 5QI=1 and a code rate requirement of GBR=3Mbps.

[0075] The PCC rules for the first service may include: relevant identification information of the first service and QoS parameters of the first service, wherein the QoS parameters may include at least one of 5QI, GBR, etc. The QoS parameters of the first service may also be referred to as the QoS parameters of the data stream corresponding to the first service, or the QoS parameters of the data stream of the first service, etc.

[0076] Optionally, the method by which the first core network element determines the PCC rules of the first service based on the QoS requirements corresponding to the first service may include: the first core network element directly determining the QoS parameters of the first service based on the information obtained from the AF (i.e., the relevant identification information of the first service and its associated QoS requirements); and generating PCC rules for the first service based on the QoS parameters of the first service and the relevant identification information of the first service.

[0077] For example, the first core network element can directly use the QoS requirements corresponding to the first service as the QoS parameters of the first service. Alternatively, the first core network element can calculate the QoS parameters of the first service based on the QoS requirements corresponding to the first service. The specific method by which the first core network element calculates the QoS parameters of the first service is not limited here.

[0078] Optionally, the method by which the first core network element determines the PCC rules of the first service based on the QoS requirements corresponding to the first service may include: the first core network element can determine the QoS parameters of the first service based on the information obtained from the AF (i.e., the relevant identification information of the first service and its associated QoS requirements) and the operator's policies; and generate the PCC rules of the first service based on the QoS parameters of the first service and the relevant identification information of the first service.

[0079] For example, the first core network element can calculate the QoS parameters of the first service based on the QoS requirements corresponding to the first service and the operator's policy. The specific content of the operator's policy is not limited in this embodiment; it may include at least one of the following: the specific method for calculating QoS parameters, whether QoS requirements are directly used as QoS parameters, or other indicators that need to be considered when calculating QoS parameters.

[0080] It should be understood that the content sent by the AF to the first core network element may include, but is not limited to, the relevant identification information of the first service and the QoS requirements corresponding to the first service. It may also include the relevant identification information of each of the other services and the QoS requirements corresponding to each of the other services. Accordingly, the first core network element can determine the PCC rules of the first service and the PCC rules of each other service. The specific determination method of the PCC rules of each other service is the same as that of the first service, so it will not be described in detail. Taking the following example, where the first core network element receives the relevant identification information (IP 5-tuple a), QoS requirement of 5QI=1, and code rate requirement of GBR=2Mbps for service data stream a from the AF, and the relevant identification information (IP 5-tuple b), QoS requirement of 5QI=1, and code rate requirement of GBR=3Mbps for service data stream b, the following example is provided: The first core network element can determine, based on the above information obtained from the AF and / or the operator's policy, that PCC rule a (or the PCC rule for service a) includes {IP 5-tuple a, 5QI=1, GBR=2Mbps}, and PCC rule b (or the PCC rule for service b) includes {IP 5-tuple b, 5QI=1, GBR=3Mbps}.

[0081] When the first core network element sends the PCC rule of the first service to the second core network element, it can also send the PCC rule of each of the other services in one or more other services; correspondingly, the second core network element can receive the PCC rule of the first service and the PCC rule of each of the other services.

[0082] After the second core network element receives the PCC rules for the first service sent by the first core network element, the processing of the second core network element may further include: the second core network element determining that the PCC rules for the first service correspond to the first QoS flow, and determining the QoS parameters of the first QoS flow; and sending the QoS parameters of the first QoS flow to the access network device. Correspondingly, the processing of the access network device may include: receiving the QoS parameters of the first QoS flow sent by the second core network element.

[0083] The second core network element determines the PCC rule of the first service corresponding to the first QoS flow and determines the QoS parameters of the first QoS flow. This may include: the second core network element binding or mapping the PCC rule of the first service to the first QoS flow, and determining the QoS parameters of the first QoS flow based on the PCC rule of the first service.

[0084] The second core network element can manage multiple QoS flows. The first QoS flow is any one of the multiple QoS flows, and the first QoS flow can correspond to or be bound to one or more services. The first service is any service associated with or bound to the first QoS flow. More specifically, the first QoS flow can be bound to or correspond to the data flow corresponding to one or more services and the PCC rules of one or more services. The data flow corresponding to the first service is one of the data flows corresponding to one or more services bound to or corresponding to the first QoS flow, and the PCC rules of the first service are one of the PCC rules of one or more services bound to or corresponding to the first QoS flow. This embodiment does not limit the method by which the second core network element determines the service (or the data flow corresponding to the service and the PCC rules of the service) bound to or corresponding to each QoS flow among the multiple QoS flows.

[0085] Taking the example that the first QoS flow can be bound to or correspond to multiple services, the second core network element binds or corresponds the PCC rules of the first service to the first QoS flow. Based on the PCC rules of the first service, the QoS parameters of the first QoS flow are determined. This may include: the second core network element jointly corresponds or binds the PCC rules of the first service and the PCC rules of one or more other services to the first QoS flow; and based on the PCC rules of the first service and the PCC rules of one or more other services, the QoS parameters of the first QoS flow are determined.

[0086] The second core network element mapping or binding the PCC rules of the first service and one or more other service PCC rules to the first QoS flow can mean that the second core network element binds the PCC rules of the first service and one or more other service PCC rules to the identifier of the first QoS flow. The identifier of the first QoS flow can be the QFI (QoS flow ID) of the first QoS flow.

[0087] The second core network element can determine the QoS parameters of the first QoS flow based on the PCC rules of the first service and the PCC rules of one or more other services in the same way as the relevant protocols, and there is no limitation here.

[0088] The second core network element sends the QoS parameters of the first QoS flow to the access network device. Specifically, the second core network element sends the identifier of the first QoS flow and its associated QoS parameters to the access network device.

[0089] For example, the second core network element receives the following PCC rules from the first core network element: PCC rule a (or the PCC rule for service a, i.e., the first service) includes {IP 5-tuple a, 5QI = 1, GBR = 2Mbps}, and PCC rule b (or the PCC rule for service b, i.e., other services) includes {IP 5-tuple b, 5QI = 1, GBR = 3Mbps}. The second core network element can determine that both PCC rule a and PCC rule b are bound to or correspond to QoS flow 1 (i.e., the first QoS flow), and the identifier of QoS flow 1 is QFI 1. The second core network element can determine the QoS parameters of QoS flow 1 based on PCC rule a and PCC rule b. For example, the second core network element determines the QoS parameters of QoS flow 1 as: 5QI = 1, GFBR (Guaranteed Flow Bit) = 1, 5QI ... Rate (guaranteed stream bit rate) = 2Mbps + 3Mbps = 5Mbps; the second core network element sends the identifier of QoS flow 1 and its associated QoS parameters to the access network device. For example, the second core network element sends QFI 1, 5QI = 1, GFBR = 5Mbps to the access network device.

[0090] After receiving the QoS parameters of the first QoS stream from the second core network element, the access network device may perform radio resource scheduling based on the QoS parameters of the first QoS stream to ensure the QoS of data transmission. Specifically, the access network device performs radio resource scheduling with the terminal based on the QoS parameters of the first QoS stream to ensure the QoS of data transmission between the terminal and the network side for the first QoS stream.

[0091] This can be understood as the network side and the terminal completing the radio resource scheduling related to the first QoS stream to ensure the QoS of data transmission of the first QoS stream between the terminal and the network side.

[0092] After the terminal side begins transmitting the data stream of the first service (or the data stream of the first service and one or more other services), it can generate or obtain experience information of the first service and send the experience information of the first service. The following explanation will continue using the first service as an example. It should be understood that since the related processing for each other service is the same as that for the first service, it will not be elaborated upon one by one, but this does not mean that the terminal and network side can only perform subsequent processing for the first service.

[0093] The terminal sending experience information of the first service includes one of the following: the terminal sending experience information of the first service to the AF; the terminal sending experience information of the first service to the network device. In this embodiment, the network device is specifically a first core network element.

[0094] The first core network element receiving experience information of the first service may include one of the following: the first core network element receiving experience information of the first service sent by the AF; or the first core network element receiving experience information of the first service sent by the terminal.

[0095] In some examples, the terminal sends the experience information of the first service to the AF; the first core network element receives the experience information of the first service sent by the AF.

[0096] The terminal can send the experience information of the first service to the AF in the following ways: the terminal sends the experience information of the first service to the AF through the application layer; correspondingly, the AF obtains the experience information of the first service from the terminal through application layer interaction. The terminal can initiate the interaction of the experience information of the first service with the AF through the application layer on demand, periodically, or according to the actual situation, or the AF can request and obtain it from the terminal side according to demand or periodically, which is not limited here.

[0097] The specific content of the experience information for this first service may include the same as in the aforementioned embodiments, and will not be repeated here.

[0098] Optionally, the first core network element receiving the experience information of the first service sent by the AF may include: the first core network element notifying the AF of a service experience information subscription, and the first core network element receiving the experience information of the first service sent by the AF based on the subscription. That is, the first core network element can subscribe to the AF of a service experience information subscription according to its own needs, and then the AF can send the experience information of the first service it has obtained to the first core network element based on the subscription of the first core network element.

[0099] Optionally, the first core network element receiving the experience information of the first service sent by the AF may include: the first core network element directly receiving the experience information of the first service sent by the AF. That is, the AF may proactively send the obtained experience information of the first service to the first core network element, regardless of whether the first core network element has subscribed to the AF for service experience information notification.

[0100] It should be noted that this is only an illustrative example using the experience information of the first service. In actual processing, the AF can send the experience information of each service to the first core network element, which will not be elaborated here.

[0101] In some examples, the first core network element receives experience information of the first service sent by the AF. Unlike the previous example, in this example, the terminal sends partial experience information of the first service to the AF.

[0102] Specifically, the terminal sends partial experience information of the first service to the AF through the application layer. The interaction between the terminal and the AF through the application layer regarding this partial experience information of the first service can be initiated by the terminal on demand, periodically, or according to actual conditions, or it can be requested and obtained by the AF from the terminal side according to demand or periodically; there are no restrictions here.

[0103] Application Filtering (AF) obtains partial experience information of the first service from the terminal through application layer interaction. Based on this partial experience information, AF derives the overall experience information of the first service. For example, the partial experience information of the first service reported by the terminal may include: the identification information of the first service and the QoE metric of the first service.

[0104] The AF (Automatic Feedback) obtains the experience information of the first service based on partial experience information of the first service. This includes: the AF calculating the experience score of the first service based on the QoE (Quality of Experience) index of the first service; and generating the experience information of the first service together based on the identification information of the first service sent by the terminal, the QoE index of the first service, and the experience score of the first service generated by the AF. This embodiment does not limit the specific method by which the AF calculates the experience score of the first service.

[0105] Alternatively, AF can obtain the experience information of the first service based on some experience information of the first service, including: AF can calculate the experience score of the first service based on the QoE index of the first service, and obtain the experience information of the first service based on the identification information of the first service and the experience score of the first service.

[0106] Alternatively, the AF can obtain the experience information of the first service based on some experience information of the first service, including: the AF directly using the identification information of the first service and the QoE index of the first service sent by the terminal as the experience information of the first service.

[0107] The description of the first core network element receiving the experience information of the first service sent by the AF is the same as the previous example and will not be repeated here. It should be noted that this is only an illustrative example using the experience information of the first service as an example. In actual processing, the AF can send experience information of various services to the first core network element, which will not be described in detail here.

[0108] In some examples, the terminal sends the experience information of the first service to the first core network element; the first core network element receives the experience information of the first service sent by the terminal.

[0109] The experience information of the first service can be carried by control plane messages, which can be NAS (Non-Access Stratum) messages, specifically uplink NAS messages.

[0110] Optionally, the terminal may proactively send the experience information of the first service to the first core network element. The terminal may proactively send the experience information of the first service on demand, periodically, or according to actual circumstances; no restrictions are imposed here.

[0111] For example, the terminal can proactively send the experience information of the first service to the first core network element in an uplink NAS message; the first core network element receives the uplink NAS message carrying the experience information of the first service sent by the terminal.

[0112] For example, the terminal can proactively include the experience information of the first service in an uplink NAS message and send the uplink NAS message to the first core network element through the second core network element. Correspondingly, the first core network element can receive the uplink NAS message carrying the experience information of the first service sent by the terminal through the second core network element.

[0113] It should be noted that this is only an illustrative example using the experience information of the first service. In actual processing, the terminal can send experience information of multiple services (the first service and one or more other services) to the first core network element, which will not be elaborated here.

[0114] Optionally, the terminal may receive an experience information reporting request from a first core network element, and then the terminal may send experience information of the first service to the first core network element. The first core network element may also send an experience information reporting request to the terminal, and then the first core network element may receive the experience information of the first service sent by the terminal.

[0115] The experience information reporting request can also be carried by control plane messages, such as downlink NAS messages. The downlink NAS message carrying the experience information reporting request is sent directly from the first core network element to the terminal, or the downlink NAS message carrying the experience information reporting request can be sent from the first core network element to the terminal through the second core network element.

[0116] The experience information of the first service can be carried by an uplink NAS message. The uplink NAS message carrying the experience information of the first service can be sent directly from the terminal to the first core network element, or it can be sent from the terminal to the first core network element through the second core network element.

[0117] The experience information reporting request may carry at least one of the following: an instruction for requesting the reporting of experience information, or identification information of the first service.

[0118] For example, the experience information reporting request can be used to request the reporting of experience information for a first service. The experience information reporting request can carry an instruction for requesting the reporting of experience information and identification information of the first service. Accordingly, the terminal can send the experience information of the first service to the first core network element in an uplink NAS message, or send it to the first core network element through the second core network element.

[0119] For example, this experience information reporting request can be used to request the terminal to report experience information for all services, and the experience information reporting request can only carry an instruction for requesting the reporting of experience information. Accordingly, the terminal can send the experience information of all its corresponding services to the first core network element in an uplink NAS message, or send it to the first core network element through the second core network element.

[0120] For example, the experience information reporting request can be used to request the terminal to report experience information for at least two services out of all services. In this case, the experience information reporting request can carry an instruction for requesting the reporting of experience information and identification information for each of the at least two services, including the first service and one or more other services. Accordingly, the terminal can send the experience information of each of the at least two services in an uplink NAS message to the first core network element, or send it to the first core network element through the second core network element.

[0121] After receiving the experience information of the first service, the first core network element further includes: adjusting the QoS parameters of the first service based on the experience information of the first service to obtain the adjusted QoS parameters of the first service.

[0122] In this embodiment, the adjusted QoS parameters of the first service are included in the updated PCC rules of the first service. That is, the first core network element specifically adjusts the QoS parameters in the PCC rules of the first service, and finally obtains the updated PCC rules of the first service that include the adjusted QoS parameters of the first service.

[0123] For example, the experience information of the first service may include the identification information of the first service and the experience score of the first service.

[0124] The first core network element adjusts the QoS parameters of the first service based on the experience information of the first service to obtain the adjusted QoS parameters of the first service. This may include: the first core network element searching for the PCC rules of the first service based on the identification information of the first service; and if the first core network element determines, based on the experience score of the first service, that the QoS parameters in the PCC rules of the first service need to be adjusted, the first core network element adjusts the QoS parameters of the first service to obtain the adjusted QoS parameters of the first service.

[0125] The method by which the first core network element determines whether to adjust the QoS parameters in the PCC rules of the first service based on the experience score of the first service may include at least one of the following: if the experience score of the first service is higher than the experience threshold, the first core network element determines that it is not necessary to adjust the QoS parameters in the PCC rules of the first service, and / or determines that the experience of the first service is normal; if the experience score of the first service is not higher than the experience threshold, the first core network element determines that it is necessary to adjust the QoS parameters in the PCC rules of the first service. The experience threshold can be configured according to actual conditions and is not limited here.

[0126] This embodiment does not limit the specific method by which the first core network element adjusts the QoS parameters of the first service. For example, the first core network element may increase the bitrate in the QoS parameters of the first service by a first specified value, and / or increase other parameters in the QoS parameters of the first service by a second specified value. Both the first and second specified values ​​can be configured according to actual conditions, and this embodiment does not limit them. Another example is that the first core network element determines one or more parameters to be adjusted in the QoS parameters of the first service, and determines the adjustment value corresponding to each of the one or more parameters to be adjusted. Based on the adjustment value corresponding to each parameter to be adjusted, each parameter to be adjusted is adjusted to obtain the adjusted QoS parameters of the first service. The method by which the first core network element determines each parameter to be adjusted and its corresponding adjustment value is not limited in this embodiment.

[0127] For example, the terminal also reports the experience information of the first service. The first core network element finds the PCC rule for the first service, namely PCC rule a, from its own stored PCC rules based on the identification information of the first service. PCC rule a includes {IP 5-tuple a, 5QI=1, GBR=2Mbps}. Based on the experience score of the first service, it is determined that the bit rate in PCC rule a needs to be increased. The QoS parameters in PCC rule a can be adjusted to "5QI=1, GBR=5Mbps". Finally, the updated PCC rule a for the first service is {IP 5-tuple a, 5QI=1, GBR=5Mbps}.

[0128] For another example, the first core network element can also obtain experience information of another service. Based on the identification information of other services, the first core network element looks up the PCC rules of other services, such as PCC rule b, from its own stored PCC rules. PCC rule b includes {IP 5-tuple b, 5QI=1, GBR=3Mbps}. If it is determined that no QoS parameters need to be adjusted based on the experience score of other services, or if it is determined that the user experience of other services is normal or the experience of other services is normal, then PCC rule b remains unchanged.

[0129] For example, the experience information of the first service may include the identification information of the first service, the experience score of the first service, and the QoE metric of the first service.

[0130] The first core network element adjusts the QoS parameters of the first service based on the experience information of the first service to obtain the adjusted QoS parameters of the first service. This may include: the first core network element searching for the PCC rules of the first service based on the identification information of the first service; and if the first core network element determines that the QoS parameters in the PCC rules of the first service need to be adjusted based on the experience score of the first service, the first core network element adjusts the QoS parameters of the first service based on the QoE index of the first service to obtain the adjusted QoS parameters of the first service.

[0131] The method by which the first core network element determines whether to adjust the QoS parameters in the PCC rules of the first service based on the experience score of the first service is the same as the previous example and will not be repeated here.

[0132] The specific method by which the first core network element adjusts the QoS parameters of the first service based on the QoE index of the first service to obtain the adjusted QoS parameters of the first service is not limited in this embodiment. For example, the first core network element determines one or more parameters to be adjusted among the QoS parameters of the first service based on the QoE index of the first service, and determines the adjustment value corresponding to each of the one or more parameters to be adjusted. Based on the adjustment value corresponding to each parameter to be adjusted, each parameter to be adjusted is adjusted to obtain the adjusted QoS parameters of the first service. The method by which the first core network element determines the adjustment value corresponding to the parameter to be adjusted is not limited in this embodiment.

[0133] For example, the experience information of the first service may include the identification information of the first service and the QoE metric of the first service.

[0134] The first core network element adjusts the QoS parameters of the first service based on the experience information of the first service to obtain the adjusted QoS parameters of the first service. This may include: the first core network element searching for the PCC rules of the first service based on the identification information of the first service; and if the first core network element determines that the QoS parameters in the PCC rules of the first service need to be adjusted based on the QoE index of the first service, the first core network element adjusts the QoS parameters of the first service based on the QoE index of the first service to obtain the adjusted QoS parameters of the first service.

[0135] The method by which the first core network element determines whether to adjust the QoS parameters in the PCC rules of the first service based on the QoE index of the first service may include at least one of the following: If all QoE indices of the first service are higher than their corresponding thresholds, the first core network element determines that no adjustment to the QoS parameters in the PCC rules of the first service is needed; if at least one QoE index of the first service is not higher than its corresponding threshold, the first core network element determines that the QoS parameters in the PCC rules of the first service need to be adjusted. The various QoE indices can each correspond to their respective thresholds, and the thresholds for each index can be configured according to actual conditions, without limitation here.

[0136] The explanation regarding how the first core network element adjusts the QoS parameters of the first service based on the QoE index of the first service to obtain the adjusted QoS parameters of the first service is the same as the previous example and will not be repeated here.

[0137] After obtaining the adjusted QoS parameters of the first service, the method further includes: the first core network element sending an updated PCC rule for the first service to the second core network element, wherein the updated PCC rule for the first service includes the identification information of the first service and the adjusted QoS parameters of the first service, and the updated PCC rule for the first service is used by the second core network element to adjust the QoS parameters of the first QoS flow, wherein the first QoS flow corresponds to the data flow of one or more services, and the one or more services include the first service.

[0138] After receiving the updated PCC rules of the first service on the second core network element side, the process may further include: the second core network element updating or adjusting the QoS parameters of the first QoS flow according to the updated PCC rules of the first service, to obtain the adjusted QoS parameters of the first QoS flow.

[0139] Specifically, after receiving the updated PCC rules of the first service, the second core network element can determine the first QoS flow bound to or corresponding to the first service based on the identification information of the first service included in the updated PCC rules of the first service; based on the adjusted QoS parameters of the first service included in the updated PCC rules of the first service, it can update or adjust the QoS parameters of the first QoS flow to obtain the adjusted QoS parameters of the first QoS flow.

[0140] The second core network element updates or adjusts the QoS parameters of the first QoS flow based on the updated PCC rules of the first service, including the adjusted QoS parameters of the first service, to obtain the adjusted QoS parameters of the first QoS flow. This can include: the second core network element updating or adjusting the QoS parameters of the first QoS flow based on the updated PCC rules of the first service, including the adjusted QoS parameters of the first service, and the QoS parameters of each other service in the PCC rules of one or more services corresponding to the first QoS flow, excluding the first service, to obtain the adjusted or updated QoS parameters of the first QoS flow.

[0141] For example, the content sent from the first core network element to the second core network element includes an updated PCC rule a for the first service, which is {IP 5-tuple a, 5QI = 1, GBR = 5Mbps}. Based on the identification information of the first service included in the updated PCC rule a, the second core network element determines that the first QoS flow bound to or corresponding to the first service is QoS flow 1. This QoS flow 1 corresponds to service a (the first service) and service b (other services). Then, the second core network element can adjust the QoS parameters of QoS flow 1 to 5QI = 1 and GFBR = 5Mbps + 3Mbps = 8Mbps, based on the adjusted QoS parameters in PCC rule a for service a and the unchanged QoS parameters in PCC rule b for service b (e.g., PCC rule b in the aforementioned example includes {IP 5-tuple b, 5QI = 1, GBR = 3Mbps}).

[0142] The processing after the second core network element receives the adjusted QoS parameters of the first QoS flow may further include: the second core network element sending the identifier of the first QoS flow and the adjusted or updated QoS parameters of the first QoS flow to the access network device. Correspondingly, the processing of the access network device may include: the access network device receiving the identifier of the first QoS flow and the adjusted or updated QoS parameters of the first QoS flow from the second core network element; and performing radio resource scheduling based on the adjusted or updated QoS parameters of the first QoS flow to ensure the QoS of data transmission.

[0143] The communication method provided in this embodiment will be described by way of example below with reference to Figure 5:

[0144] Step 501: The AF provides the PCF (first core network element) located in the core network with service identification information (or service data flow identification information) and its corresponding QoS requirements.

[0145] For example, the AF provides the PCF with the service identification information (i.e., the relevant identification information of the first service) of service data stream a as IP 5-tuple a, with a QoS requirement of 5QI=1 and a code rate requirement of GBR=2Mbps; the AF can also send the PCF the service identification information (i.e., the relevant identification information of another service) of service data stream b as IP 5-tuple b, with a QoS requirement of 5QI=1 and a code rate requirement of GBR=3Mbps.

[0146] Step 502: The PCF determines the PCC rule based on the information obtained from the AF (or based on the information obtained from the AF and the operator's policy), and sends the PCC rule to the SMF (second core network element). The PCC rule includes service identification information (or service data flow identification information) and corresponding QoS parameters.

[0147] For example, the PCC rules determined by the PCF may include: PCC rule a (i.e., the PCC rule for the first service) includes {IP 5-tuple a, 5QI=1, GBR=2Mbps}, and PCC rule b (i.e., the PCC rule for another service) includes {IP 5-tuple b, 5QI=1, GBR=3Mbps}.

[0148] Step 503: The SMF determines the first QoS flow corresponding to the PCC rule and determines the QoS parameters of the first QoS flow. The SMF sends the identifier of the first QoS flow and the QoS parameters of the first QoS flow to the access network device.

[0149] For example, SMF determines that PCC rule a and PCC rule b are both bound to QoS flow 1 (i.e., the first QoS flow). The identifier of QoS flow 1 is QFI 1, and the QoS parameters of QoS flow 1 are 5QI=1 and GFBR=2Mbps+3Mbps=5Mbps.

[0150] Step 504: The access network device performs radio resource scheduling based on the QoS parameters of the first QoS stream obtained from the SMF (as shown in Figure 5, the access network device and the UE perform radio resource scheduling) to ensure the QoS of data transmission.

[0151] Step 505: The PCF obtains the user's service experience from the AF or the UE (including at least the experience information of the first service in the foregoing embodiments, and optionally the experience information of other services). The user's service experience includes service identification information (such as the identification information of the first service) and service experience information (experience score and / or QoE index).

[0152] Step 505 may include either step 505a or step 505b, as follows:

[0153] Step 505a: The PCF obtains service identification information and service experience information from the AF. For example, the PCF can obtain experience information of a first service from the AF, which includes at least one of the following: identification information of the first service, experience score of the first service, and QoE metric of the first service; optionally, the PCF can obtain experience information of other services from the AF.

[0154] For example, in implementation method 1: AF obtains service experience information (at least the experience information of the first service) from UE through application layer interaction, such as experience score, QoE index, etc. AF actively sends the service experience information to PCF, or PCF signs up for service experience information with AF, and AF sends the service experience information to PCF according to PCF's signing up.

[0155] For example, in implementation method 2: The Application Controller (AF) obtains service experience information from the User Equipment (UE) through application layer interaction. The AF can further generate new service experience information, such as obtaining QoE metrics from the UE and calculating and generating a service experience score. The AF sends the service experience information generated by the AF and / or the service experience information obtained from the UE to the PCF. The AF can send the information to the PCF proactively or according to the PCF's subscription.

[0156] Step 505b: The PCF obtains service identification information and service experience information from the UE.

[0157] Implementation Method 3: PCF obtains service experience information (at least the experience information of the first service) directly from the UE through control plane messages (such as uplink NAS messages) between the core network and the UE. These information include service experience scores and / or QoE metrics. The control plane messages also include service identification information.

[0158] For example, the UE proactively sends service experience information to the core network via an uplink NAS message. The UE can include this service experience information in the uplink NAS message and send it to the SMF, which in turn forwards it to the PCF.

[0159] For example, the PCF requests service experience information from the UE through control plane messages between the core network and the UE, and the UE responds with service experience information based on the PCF's request message.

[0160] Step 506: PCF adjusts the QoS parameters of the service data stream (including at least the QoS parameters of the first service) based on the service experience information (at least the experience information of the first service).

[0161] For example, if the user experience of the service data stream a (i.e. the first service or the data stream corresponding to the first service) obtained by the PCF is poor, the PCC rule a can be adjusted to increase the bit rate, for example, by adjusting it to {IP quintuple a, 5QI=1, GBR=5Mbps}.

[0162] For example, if the PCF determines that the user's business experience in business data stream b (the data stream corresponding to business b) is normal based on the business experience information obtained for business b, then the PCC rule b remains unchanged.

[0163] Step 507: The PCF sends the updated PCC rules to the SMF. The updated PCC rules include service identification information and adjusted QoS parameters.

[0164] Step 508: The SMF updates the QoS parameters of the first QoS flow according to the updated PCC rules. The SMF sends the identifier of the first QoS flow and its updated QoS parameters (i.e., the adjusted or updated QoS parameters of the first QoS flow) to the access network device.

[0165] For example, the SMF determines that the QoS parameters of QoS flow 1 (first data flow) are adjusted to 5QI=1, GFBR=5Mbps+3Mbps=8Mbps; then the SMF sends QFI1, 5QI=1, GFBR=8Mbps to the access network device.

[0166] Step 509: The access network device performs radio resource scheduling based on the updated QoS parameters of the first QoS stream obtained from the SMF to ensure the QoS of data transmission.

[0167] It should be noted that steps 505 to 509 can be executed once or multiple times, and the specific number of times steps 505 to 509 may be executed repeatedly is not limited in this embodiment. Furthermore, when steps 505 to 509 are executed at different times, the specific services adjusted on the PCF side and the content of the specific PCC rules adjusted may be the same or different, but the method of adjusting the PCC rules each time is the same as in the above example. Similarly, the specific content of the QoS parameters of the QoS flow adjusted on the SMF side may also be different, but the specific method of adjusting the QoS parameters of the QoS flow each time is also the same as in the above example, therefore, it will not be described again.

[0168] By adopting the solution provided in this embodiment, the network (such as the first core network element) can obtain the user's service experience, thereby updating the corresponding QoS parameters to better meet the user's service experience.

[0169] In some embodiments, before the first core network element receives the experience information of the first service, it may include: the first core network element receiving the QoS requirements corresponding to the first service sent by the AF; and the first core network element determining the QoS parameters of the first service based on the QoS requirements corresponding to the first service.

[0170] The AF's processing may include: the AF sending the QoS requirement corresponding to the first service to the first core network element.

[0171] The AF sends the QoS requirements related to the first service to the first core network element, which is the same as in the previous embodiment and will not be repeated here. Furthermore, the content sent by the AF to the first core network element may include, but is not limited to, the relevant identification information of the first service and its associated QoS requirements, and may also include the relevant identification information of each of one or more other services and the QoS requirements corresponding to each other service. The relevant descriptions of the identification information and the QoS requirements corresponding to each other service are the same as those for the first service, and therefore will not be repeated here.

[0172] QoS parameters may include at least one of the following: 5QI, GBR, etc.

[0173] Optionally, the first core network element determines the QoS parameters of the first service based on the QoS requirements corresponding to the first service. This can include: the first core network element can directly determine the QoS parameters of the first service based on information obtained from the AF (i.e., the relevant identification information of the first service and its associated QoS requirements). For example, the first core network element can directly use the QoS requirements corresponding to the first service as the QoS parameters of the first service.

[0174] Optionally, the first core network element determines the QoS parameters of the first service based on the QoS requirements corresponding to the first service. This may include: the first core network element determining the QoS parameters of the first service based on information obtained from the AF (i.e., the relevant identification information of the first service and its associated QoS requirements) and operator policies. The relevant explanations regarding the determination of the QoS parameters of the first service in this method are the same as in the aforementioned embodiments and will not be repeated here.

[0175] It should be understood that the content sent by the AF to the first core network element may include, but is not limited to, the relevant identification information of the first service and the QoS requirements corresponding to the first service. It may also include the relevant identification information of each of the other services and the QoS requirements corresponding to each of the other services. Accordingly, the first core network element can determine the QoS parameters of the first service and the QoS parameters of each other service. The specific determination method of the QoS parameters of each other service is the same as that of the first service, so it will not be described in detail.

[0176] In one scenario, after determining the QoS parameters of the first service based on the QoS requirements corresponding to the first service, the first core network element may send the QoS parameters of the first service to the access network device. The access network device's processing may include receiving the QoS parameters of the first service sent by the first core network element.

[0177] Sending QoS parameters of a first service from the first core network element to the access network device may include: the first core network element sending second information to the access network device, wherein the second information includes the QoS parameters of the first service. Correspondingly, the access network device receives the second information sent by the first core network element.

[0178] Sending second information from a first core network element to an access network device may include: the first core network element sending the second information directly to the access network device; or the first core network element forwarding the second information to the access network device through other core network elements. Correspondingly, the access network device receives the second information sent by the first core network element; or the access network device receives the second information sent by the first core network element through other core network elements. These other core network elements may include a second core network element; or, these other core network elements may be other core network elements besides the first and second core network elements. The possible entities of these other core network elements are not limited or exhaustively listed here.

[0179] Optionally, the second information may also include the data stream identifier corresponding to the first service.

[0180] The data flow identifier corresponding to the first service is assigned by the AF or by the first core network element.

[0181] For example, when the AF sends the QoS requirement of the first service to the first core network element, it can send the relevant identification information of the first service and its associated or corresponding QoS requirements. Specifically, the relevant identification information of the first service can be the data stream identifier corresponding to the first service allocated by the AF.

[0182] For example, when the AF sends the QoS requirement of the first service to the first core network element, it can send the relevant identification information of the first service and its associated or corresponding QoS requirements. Specifically, the relevant identification information of the first service is the IP 5-tuple of the data flow corresponding to the first service. In this case, the first core network element can assign a data flow identifier corresponding to the first service and save the correspondence between the data flow identifier corresponding to the first service and its IP 5-tuple (or data flow filter).

[0183] It should be noted that the second information sent by the first core network element includes, but is not limited to, the data flow identifier corresponding to the first service and its associated QoS parameters, and may also include the data flow identifier corresponding to each of one or more other services and its associated QoS parameters. For example, the first core network element sends {SDF IDda (data flow identifier corresponding to the first service), 5QI=1, GBR=2Mbps} and {SDF IDb (data flow identifier corresponding to a certain other service), 5QI=1, GBR=3Mbps} to the access network device, where each SDF ID can be obtained directly from the AF by the first core network element or assigned by the first core network element.

[0184] Optionally, the second information may also include the IP quintuple of the data stream corresponding to the first service.

[0185] It should be noted that the second information sent by the first core network element includes, but is not limited to, the IP 5-tuple of the data stream corresponding to the first service and its associated QoS parameters, and may also include the IP 5-tuple of the data stream corresponding to each of one or more other services and its associated QoS parameters. For example, the first core network element sends to the access network device {IP 5-tuple a (IP 5-tuple of the data stream corresponding to the first service), 5QI=1, GBR=2Mbps}, {IP 5-tuple b (IP 5-tuple of the data stream corresponding to a certain other service), 5QI=1, GBR=3Mbps}.

[0186] In another scenario, after determining the QoS parameters of the first service based on its QoS requirements, the first core network element may send the QoS parameters of the first service to the second core network element. The second core network element's processing may include: receiving the QoS parameters of the first service sent by the first core network element, and then sending the QoS parameters of the first service to the access network device. The access network device's processing includes: receiving the QoS parameters of the first service sent by the second core network element.

[0187] Specifically, the first core network element sending the QoS parameters of the first service to the second core network element may include: the first core network element sending third information to the second core network element, wherein the third information includes the IP 5-tuple of the data stream corresponding to the first service and the QoS parameters of the first service.

[0188] The process of the second core network element receiving the QoS parameters of the first service sent by the first core network element and the second core network element sending the QoS parameters of the first service to the access network device may include: the second core network element receiving the third information sent by the first core network element and the second core network element sending the second information to the access network device, wherein the second information includes the data flow identifier corresponding to the first service and the QoS parameters of the first service.

[0189] The processing of QoS parameters of the first service sent by the access network device to the second core network element includes: receiving second information sent by the second core network element, the second information including the data flow identifier corresponding to the first service and the QoS parameters of the first service.

[0190] In this scenario, the data flow identifier corresponding to the first service is assigned by the second core network element. For example, when the AF sends the QoS requirement for the first service to the first core network element, it can send the relevant identification information of the first service and its associated or corresponding QoS requirements. Specifically, the relevant identification information of the first service is the IP 5-tuple of the data flow corresponding to the first service. The first core network element can send the IP 5-tuple of the data flow corresponding to the first service and its associated QoS parameters to the second core network element; the second core network element then assigns the data flow identifier corresponding to the first service and stores the correspondence between the data flow identifier corresponding to the first service and its IP 5-tuple (or data flow filter).

[0191] It should also be noted that the third information sent by the first core network element includes, but is not limited to, the IP 5-tuple of the data flow corresponding to the first service and its associated QoS parameters, and may also include the IP 5-tuple of the data flow corresponding to each of one or more other services and its associated QoS parameters. The second information sent by the second core network element includes, but is not limited to, the data flow identifier corresponding to the first service and its associated QoS parameters, and may also include the data flow identifier corresponding to each of one or more other services and its associated QoS parameters.

[0192] The processing by the access network device after receiving the QoS parameters of the first service may include: performing radio resource scheduling based on the QoS parameters of the first service to ensure the QoS of data transmission. Specifically, the access network device performs radio resource scheduling with the terminal based on the QoS parameters of the first service to ensure the QoS of data transmission between the terminal and the network side for the first service.

[0193] Optionally, the access network device may also receive QoS parameters for one or more other services. Similarly, the access network device performs radio resource scheduling with the terminal based on the QoS parameters of each other service to ensure QoS when the terminal and the network side transmit data for each other service.

[0194] In this embodiment, the terminal sends the experience information of the first service, and the first core network element receives the experience information of the first service and performs the same related processing as in the previous embodiment, so it will not be described again.

[0195] After receiving the experience information of the first service, the first core network element further includes: adjusting the QoS parameters of the first service based on the experience information of the first service to obtain the adjusted QoS parameters of the first service.

[0196] For example, the experience information of the first service may include the identification information of the first service and the experience score of the first service.

[0197] The first core network element adjusts the QoS parameters of the first service based on the experience information of the first service to obtain the adjusted QoS parameters of the first service. This may include: the first core network element searching for the QoS parameters of the first service based on the identification information of the first service; and, if the first core network element determines that the QoS parameters of the first service need to be adjusted based on the experience score of the first service, the first core network element adjusts the QoS parameters of the first service to obtain the adjusted QoS parameters of the first service.

[0198] The method by which the first core network element determines whether to adjust the QoS parameters of the first service based on the experience score of the first service may include at least one of the following: if the experience score of the first service is higher than the experience threshold, the first core network element determines that the QoS parameters of the first service do not need to be adjusted, and / or determines that the experience of the first service is normal; if the experience score of the first service is not higher than the experience threshold, the first core network element determines that the QoS parameters of the first service need to be adjusted.

[0199] This embodiment does not limit the specific method by which the first core network element adjusts the QoS parameters of the first service.

[0200] For example, the experience information of the first service may include the identification information of the first service, the experience score of the first service, and the QoE metric of the first service.

[0201] The first core network element adjusts the QoS parameters of the first service based on the experience information of the first service to obtain the adjusted QoS parameters of the first service. This may include: the first core network element searching for the QoS parameters of the first service based on the identification information of the first service; and if the first core network element determines that the QoS parameters of the first service need to be adjusted based on the experience score of the first service, the first core network element adjusts the QoS parameters of the first service based on the QoE index of the first service to obtain the adjusted QoS parameters of the first service.

[0202] The method by which the first core network element determines whether to adjust the QoS parameters of the first service based on the experience score of the first service is the same as the previous example and will not be repeated here.

[0203] The explanation of how the first core network element adjusts the QoS parameters of the first service based on the QoE index of the first service to obtain the adjusted QoS parameters of the first service is the same as that in the previous embodiment and will not be repeated.

[0204] For example, the experience information of the first service may include the identification information of the first service and the QoE metric of the first service.

[0205] The first core network element adjusts the QoS parameters of the first service based on the experience information of the first service to obtain the adjusted QoS parameters of the first service. This may include: the first core network element searching for the QoS parameters of the first service based on the identification information of the first service; and, if the first core network element determines that the QoS parameters of the first service need to be adjusted based on the QoE index of the first service, the first core network element adjusts the QoS parameters of the first service based on the QoE index of the first service to obtain the adjusted QoS parameters of the first service.

[0206] The method by which the first core network element determines whether to adjust the QoS parameters of the first service based on the QoE index of the first service may include at least one of the following: if all the QoE indices of the first service are higher than the thresholds corresponding to each index, the first core network element determines that the QoS parameters of the first service do not need to be adjusted; if at least one of the QoE indices of the first service is not higher than its corresponding threshold, the first core network element determines that the QoS parameters of the first service need to be adjusted.

[0207] The explanation regarding how the first core network element adjusts the QoS parameters of the first service based on the QoE index of the first service to obtain the adjusted QoS parameters of the first service is the same as the previous example and will not be repeated here.

[0208] It should be noted that the first core network element may also receive experience information of other services from the AF or the terminal. The way the first core network element adjusts the QoS parameters of other services is the same as that of the first service, so it will not be described in detail.

[0209] In one scenario, after obtaining the adjusted QoS parameters of the first service, the method further includes: the first core network element sending first information to the access network device, wherein the first information includes the data flow identifier corresponding to the first service and the adjusted QoS parameters of the first service, and the data flow identifier corresponding to the first service is allocated by the AF or by the first core network element.

[0210] Correspondingly, the processing of the access network equipment may include: the access network equipment receiving the first information sent by the first core network element.

[0211] Sending first information from a first core network element to an access network device may include: the first core network element sending the first information directly to the access network device; or the first core network element forwarding the first information to the access network device through other core network elements. Correspondingly, the access network device receives the first information sent by the first core network element; or the access network device receives the first information sent by the first core network element through other core network elements. The relevant descriptions of these other core network elements are the same as in the aforementioned embodiments and will not be repeated.

[0212] This applies to scenarios where the data flow identifier corresponding to the first service is assigned by the AF or the first core network element. If the data flow identifier corresponding to the first service is assigned by the first core network element, the first core network element stores the correspondence between the data flow identifier corresponding to the first service and the IP 5-tuple (or data flow filter) of its data flow.

[0213] In another scenario, after obtaining the adjusted QoS parameters of the first service, the method further includes: the first core network element sending fourth information to the second core network element, wherein the fourth information includes the data flow filter corresponding to the first service and the adjusted QoS parameters of the first service.

[0214] The processing of the second core network element may include: the second core network element receiving the fourth information sent by the first core network element, and the second core network element sending the first information to the access network device, wherein the first information includes the data flow identifier corresponding to the first service and the adjusted QoS parameters of the first service.

[0215] Accordingly, the processing of the access network equipment may include: the access network equipment receiving the first information sent by the second core network element.

[0216] This applies to scenarios where the data flow identifier corresponding to the first service is assigned by the second core network element. The second core network element stores the correspondence between the data flow identifier corresponding to the first service and the IP 5-tuple (or data flow filter) of its data flow.

[0217] The processing performed by the access network device after receiving the first information may include: performing radio resource scheduling based on the adjusted QoS parameters of the first service to ensure the QoS of data transmission.

[0218] It should be noted that the first core network element may also adjust the QoS parameters of other services. In this case, the first information may also include the data flow identifiers corresponding to other services and their associated adjusted QoS parameters. The related processing of the access network device after receiving the adjusted QoS parameters of other services is the same as that of the first service, so it will not be described in detail.

[0219] The communication method provided in this embodiment will be described below with reference to Figure 6. Compared with the example provided in Figure 5, the example provided in Figure 6 involves the access network device directly performing QoS control at the service data stream level, without involving the mapping of service data streams to QoS streams. Specifically, it includes the following steps:

[0220] Step 601: The AF provides the service identification information and its corresponding QoS requirements to the PCF (first core network element) located in the core network.

[0221] For example, the AF provides the PCF with the service identification information of service data flow a as IP 5-tuple a, or the service identification information of service data flow a as SDF IDa (i.e., the relevant identification information of the first service is IP 5-tuple or data flow identifier), with a QoS requirement of 5QI=1 and a bit rate requirement of GBR=2Mbps; the AF can also provide the PCF with the service identification information of service data flow b as IP 5-tuple b, or the service identification information of service data flow b as SDF IDb (i.e., the relevant identification information of another service is IP 5-tuple or data flow identifier), with a QoS requirement of 5QI=1 and a bit rate requirement of GBR=3Mbps.

[0222] Step 602: The PCF determines the QoS parameters of the service data stream (including at least the QoS parameters of the first service in the aforementioned embodiments) based on the information obtained from the AF (or based on the information obtained from the AF and the operator's policy). The PCF then sends the service data stream identification information and QoS parameters to the access network device.

[0223] Optionally, the service data flow identification information sent by the PCF to the access network device can directly use the service identification information obtained in step 601, namely the IP 5-tuple or data flow identifier.

[0224] Optionally, the service data flow identification information sent by the PCF to the access network device can be used to assign a new service data flow identifier to the service data flow. For example, if the service identification information received in step 601 is IP 5-tuple 'a', the PCF assigns a service data flow identifier SDF Ida (i.e., the data flow identifier corresponding to the first service) to the service data flow. In this case, the PCF itself stores the correspondence between the service identification information obtained from the AF and the service data flow identifier assigned by the PCF.

[0225] For example, the PCF sends {IP 5-tuple a, 5QI=1, GBR=2Mbps} and {IP 5-tuple b, 5QI=1, GBR=3Mbps} to the access network device. Another example is the PCF sending {SDF IDa, 5QI=1, GBR=2Mbps} and {SDF IDb, 5QI=1, GBR=3Mbps} to the access network device, where the SDF ID can be obtained directly from the AF or assigned by the PCF.

[0226] Specifically, the PCF sends service data flow identification information and QoS parameters to the access network device. This can be done directly by the PCF or via other network elements such as the SMF. If the PCF sends the information to the access network device via the SMF, the SDF ID can also be assigned by the SMF.

[0227] Step 603: The access network device performs radio resource scheduling based on the QoS parameters of the service data stream obtained from the PCF to ensure the QoS of data transmission.

[0228] Step 604 is the same as step 505 in Figure 5, and will not be described in detail.

[0229] Step 605: PCF adjusts the QoS parameters of the service data stream (including at least the QoS parameters of the first service) based on the user's service experience (at least the experience information of the first service).

[0230] For example, if the PCF detects that users of service data stream a (i.e., the first service or the data stream corresponding to the first service) have a poor service experience, the bitrate GBR = 5Mbps can be increased for service data stream a. Conversely, if users of service data stream b (i.e., the data stream corresponding to another service) have a normal service experience, the QoS parameters for service data stream b remain unchanged.

[0231] Step 606: The PCF sends the service identification information and the updated QoS parameters (or adjusted QoS parameters) (including at least the adjusted QoS parameters of the first service in the foregoing embodiments) to the access network device.

[0232] Step 607: The access network device performs radio resource scheduling based on the updated or adjusted QoS parameters of the service data stream obtained from the PCF to ensure the QoS of data transmission.

[0233] It should be noted that steps 604 to 607 can be executed once or multiple times. The specific number of times steps 604 to 607 may be executed repeatedly is not limited in this embodiment. In addition, when steps 604 to 607 are executed in different times, the specific services adjusted on the PCF side, the content of the QoS parameters adjusted, or the adjustment values ​​may be the same or different, but the method of adjusting the QoS parameters each time is the same as the example above, so it will not be described again.

[0234] By adopting the solution provided in this embodiment, the network (such as the first core network element) can obtain the user's service experience, thereby updating the corresponding QoS parameters to better meet the user's service experience. Furthermore, since the access network device directly performs QoS control at the service (service data stream) level, the network side does not involve or perform the mapping between services or service data streams and QoS streams, thereby improving processing efficiency.

[0235] In the above embodiments, the first service can be the first service corresponding to the terminal, or it can be the first service corresponding to any other network element. If the first service is the service corresponding to any other network element, the first core network element may obtain the experience information of the first service from the AF or the network element. The subsequent processing of the first core network element adjusting the QoS parameters based on the experience information of the first service is the same as in the various embodiments of this embodiment, and will not be described again.

[0236] In some possible implementations, the network device is an access network device.

[0237] Before the access network device receives the experience information of the first service, the method further includes: the access network device receiving multiple sets of QoS parameters related to the first service sent by the first core network element, wherein the multiple sets of QoS parameters related to the first service are generated by the first core network element based on one or more sets of QoS requirements related to the first service configured by AF.

[0238] The processing of the first core network element may include: the first core network element receiving one or more sets of QoS requirements related to the first service configured by the AF; the first core network element generating multiple sets of QoS parameters related to the first service based on one or more sets of QoS requirements related to the first service configured by the AF; and sending the multiple sets of QoS parameters related to the first service to the access network device.

[0239] The AF's processing may include: the AF configuring one or more sets of QoS requirements related to the first service to the first core network element.

[0240] When the AF configures one or more sets of QoS requirements related to the first service for the first core network element, these one or more sets of requirements are associated with the relevant identification information of the first service. That is, the one or more sets of QoS requirements related to the first service received by the first core network element from the AF specifically include: the relevant identification information of the first service received by the first core network element from the AF, and the one or more sets of QoS requirements related to the first service.

[0241] The relevant descriptions of the identification information are the same as those in the previous embodiments and will not be repeated here. The contents that any set of QoS requirements may include are also the same as those in the previous embodiments. The difference is that the AF can send or configure a set of QoS requirements or multiple sets of QoS requirements corresponding to the first service to the first core network element, and the values ​​of the specific parameters included in different sets of QoS requirements are at least partially different. This is not limited or exhaustive.

[0242] The number of QoS parameter groups for the first service can be configured according to the actual situation or determined by the first core network element according to the actual situation; no limit is imposed here.

[0243] Each set of QoS parameters for the first service may include: the experience score level corresponding to that set of QoS parameters, and each set of QoS parameters for the first service may include at least one of the specific parameters such as 5QI and GBR. It should be noted that the values ​​of the specific parameters included in different sets of QoS parameters for the first service are at least partially different.

[0244] The experience score level corresponding to any set of QoS parameters for the first service can be one of all selectable score levels, and different sets of QoS parameters for the first service correspond to different experience score levels. This experience score level can also be interchangeably referred to as score level, user service experience level, service experience level, or user service experience score level, etc., without limitation or exhaustive list here.

[0245] All selectable scoring levels can be pre-configured in both the access network equipment and the first core network elements. For example, all selectable scoring levels could include two levels: high and low experience scores; or, for instance, all selectable scoring levels could include three levels: high, medium, and low experience scores. These are merely illustrative examples; in actual processing, all selectable scoring levels include, but are not limited to, the possibilities described above.

[0246] Each of the available scoring levels corresponds to a specific score or threshold for the experience score. The correspondence between each available scoring level and the specific score or threshold for the experience score can be pre-configured in the access network equipment (or the access network equipment and the first core network element).

[0247] For example, the access network equipment and the first core network element are pre-configured with the correspondence between each experience score and the optional score level. Different optional score levels correspond to different experience scores, and each optional score level can correspond to one or more experience scores.

[0248] For example, the correspondence between each optional scoring level and scoring threshold is pre-configured in the access network equipment and the first core network element, and the scoring thresholds corresponding to different optional scoring levels are different.

[0249] For example, if a lower experience score indicates a lower or worse user experience, and a higher experience score indicates a higher or better user experience, then the first core network element and the access network device can be pre-configured with a threshold value greater than a first value for a high experience score, a threshold value less than or equal to the first value and greater than a second value for a medium experience score, and a threshold value less than or equal to the second value for a low experience score. The first value is greater than the second value, and the specific values ​​of the first and second values ​​can be configured according to actual conditions. This embodiment does not limit this.

[0250] For example, if a lower experience score indicates a higher or better user experience, and a higher experience score indicates a lower or worse user experience, then the first core network element and the access network device can be pre-configured with a threshold for the experience score corresponding to a high experience score being less than the third value, a threshold for the experience score corresponding to a medium experience score being greater than or equal to the third value and less than the fourth value, and an experience score corresponding to a low experience score being greater than or equal to the fourth value, wherein the fourth value is greater than the third value. The specific values ​​of the third and fourth values ​​can be configured according to the actual situation, and this embodiment does not limit them.

[0251] The processing of multiple sets of QoS parameters related to the first service generated by the first core network element can be related to the number of QoS requirements of the first service configured by the AF, which will be explained separately below.

[0252] For example, the AF configures a set of QoS requirements related to the first service. The first core network element generates multiple sets of QoS parameters related to the first service based on the set of QoS requirements configured by the AF.

[0253] The first core network element can use a set of QoS requirements related to the first service as the median value of multiple sets of QoS parameters related to the first service. Based on this median value, it generates at least two of the following sets of QoS parameters related to the first service: a set of QoS parameters greater than the median value, a set of QoS parameters equal to the median value, and a set of QoS parameters less than the median value. Furthermore, the first core network element determines or sets different experience scoring levels for different sets of QoS parameters related to the first service. Specifically, the higher the value of a QoS parameter in the multiple sets of QoS parameters related to the first service, the lower the corresponding experience scoring level.

[0254] For example, the AF configures a set of QoS requirements for the first service for the first core network element, specifically 5QI=1 and the code rate requirement is GBR=2Mbps. The first core network element can determine two sets of QoS parameters related to the first service: the first set of QoS parameters (5QI=1, GBR=2Mbps) corresponds to a medium experience score, i.e., a medium user service experience score; the other set of QoS parameters (5QI=1, GBR=3Mbps) corresponds to a low experience score, i.e., a low user service experience score.

[0255] It should be noted that when generating multiple sets of QoS parameters related to the first service, the first core network element may also combine operator policies. The specific content of the operator policies may include at least one of the following: the number of sets of QoS parameters generated, the relevant calculation methods when generating different sets of QoS parameters, etc., which are not limited or exhaustively listed here.

[0256] For example, the AF configures multiple sets of QoS requirements related to the first service. The first core network element generates multiple sets of QoS parameters related to the first service based on the multiple sets of QoS requirements configured by the AF.

[0257] For example, the first core network element can directly use multiple sets of QoS requirements related to the first service as multiple sets of QoS parameters related to the first service; the first core network element can determine or set different experience score levels for different sets of QoS parameters among the multiple sets of QoS parameters related to the first service.

[0258] For another example, the first core network element can use any one of the multiple sets of QoS requirements related to the first service as the median value of the multiple sets of QoS parameters related to the first service, and generate at least two of the following as the multiple sets of QoS parameters related to the first service based on the median value: a set or multiple sets of QoS parameters greater than the median value, a set of QoS parameters equal to the median value, and a set or multiple sets of QoS parameters less than the median value; the first core network element determines or sets different experience scoring levels for different sets of QoS parameters in the multiple sets of QoS parameters related to the first service.

[0259] It should be noted that when generating multiple sets of QoS parameters related to the first service, the first core network element may also combine the operator's strategy. The specific content of the operator's strategy may include at least one of the following: the number of sets of QoS parameters generated, the relevant calculation methods when generating different sets of QoS parameters, and whether to directly use the multiple sets of QoS requirements configured by AF as multiple sets of QoS parameters. This is not limited or exhaustive.

[0260] It should be noted that when the AF configures one or more sets of QoS requirements related to the first service for the first core network element, it may also configure one or more sets of QoS requirements related to each of the other services in one or more other services for the first core network element. Correspondingly, the first core network element can also determine multiple sets of QoS parameters related to each other service. Since the way the first core network element determines multiple sets of QoS parameters related to each other service is the same as the way it determines multiple sets of QoS parameters related to the first service, it will not be described in detail.

[0261] In one scenario, the first core network element sends multiple sets of QoS parameters related to the first service to the access network device. This may include: the first core network element sending multiple sets of QoS parameters related to the first service and the data flow identifier corresponding to the first service to the access network device. Correspondingly, the access network device receives the multiple sets of QoS parameters related to the first service and the data flow identifier corresponding to the first service sent by the first core network element.

[0262] Sending multiple sets of QoS parameters related to the first service and the corresponding data flow identifier to the access network device from the first core network element may include: the first core network element directly sending the multiple sets of QoS parameters related to the first service and the corresponding data flow identifier to the access network device; or the first core network element forwarding the multiple sets of QoS parameters related to the first service and the corresponding data flow identifier to the access network device through other core network elements. Correspondingly, the access network device receives the multiple sets of QoS parameters related to the first service and the corresponding data flow identifier sent by the first core network element; or the access network device receives the multiple sets of QoS parameters related to the first service and the corresponding data flow identifier sent by the first core network element through other core network elements. The relevant descriptions of these other core network elements are the same as in the aforementioned embodiments and will not be repeated.

[0263] The data flow identifier corresponding to the first service is allocated by the AF or by the first core network element. The explanations regarding the allocation of the data flow identifier corresponding to the first service by the AF or the first core network element are the same as in the aforementioned embodiments and will not be repeated here.

[0264] For example, the content sent by the first core network element to the access network device includes: {SDF IDa (i.e., the data stream identifier corresponding to the first service), (user service experience score is medium (or experience score is medium), 5QI=1, GBR=2Mbps); (user service experience score is low (or experience score is low), 5QI=1, GBR=3Mbps)}.

[0265] In another scenario, the first core network element sends multiple sets of QoS parameters related to the first service to the access network device. This may include: the first core network element sending multiple sets of QoS parameters related to the first service and the IP 5-tuple of the data stream corresponding to the first service to the access network device. Correspondingly, the access network device receives the multiple sets of QoS parameters related to the first service and the IP 5-tuple of the data stream corresponding to the first service sent by the first core network element.

[0266] In this scenario, the IP 5-tuple for the data stream corresponding to the first service is assigned by AF, which will not be elaborated upon further.

[0267] For example, the content sent by the first core network element to the access network device includes: {IP 5-tuple a (i.e., the IP 5-tuple of the data stream corresponding to the first service), (user service experience score is medium (or experience score is medium), 5QI=1, GBR=2Mbps); (user service experience score is low (or experience score is low), 5QI=1, GBR=3Mbps)}.

[0268] In another scenario, the first core network element sends the IP 5-tuple of the data stream corresponding to the first service and multiple sets of QoS parameters related to the first service to the second core network element.

[0269] The processing of the second core network element may include: the second core network element receiving the IP 5-tuple of the data stream corresponding to the first service and multiple sets of QoS parameters related to the first service sent by the first core network element; the second core network element sending the data stream identifier corresponding to the first service and multiple sets of QoS parameters related to the first service to the access network device.

[0270] The processing of the access network equipment includes: receiving the data flow identifier corresponding to the first service and multiple sets of QoS parameters related to the first service sent by the second core network element.

[0271] In this scenario, the data flow identifier corresponding to the first service is allocated by the second core network element, and the second core network element stores the correspondence between the data flow identifier corresponding to the first service and the IP 5-tuple (or data flow filter) of the data flow. The relevant explanation regarding the allocation of the data flow identifier corresponding to the first service by the second core network element is the same as in the aforementioned embodiment and will not be repeated here.

[0272] The processing by the access network device after receiving multiple sets of QoS parameters related to the first service may include: performing radio resource scheduling based on the multiple sets of QoS parameters related to the first service to ensure the QoS of data transmission. Specifically, the access network device may select one set of QoS parameters from the multiple sets of QoS parameters related to the first service and perform radio resource scheduling with the terminal to ensure the QoS of data transmission between the terminal and the network side for the first service.

[0273] The process of access network equipment selecting a set of QoS parameters for radio resource scheduling can be performed according to the protocol or by default. For example, access network equipment can select the first set of QoS parameters from multiple sets of QoS parameters related to the first service for radio resource scheduling by default.

[0274] Optionally, the access network device may also receive multiple sets of QoS parameters related to each of the other services. Similarly, the access network device selects a set of QoS parameters from the multiple sets of QoS parameters for each other service and performs radio resource scheduling with the terminal to ensure QoS when the terminal and the network side transmit data for each other service. The specific method by which the access network device selects a set of QoS parameters for other services is the same as that for the first service and will not be described in detail.

[0275] The terminal sending the experience information of the first service includes: the terminal sending the experience information of the first service to the access network device.

[0276] Alternatively, the terminal sending the experience information of the first service may include: the terminal sending the experience information of the first service to a third core network element. This experience information of the first service is used by the access network equipment to adjust the QoS parameters of the first service.

[0277] The access network device receives experience information of the first service, including one of the following: the access network device receives experience information of the first service sent by a third core network element; the access network device receives experience information of the first service sent by the terminal. The third core network element may include NWDAF (Network Data Analytics Function).

[0278] In some examples, the access network device receives experience information of the first service sent by a third core network element.

[0279] The third core network element can obtain the experience information of the primary service in the following ways:

[0280] In one approach, the processing by which the third core network element obtains the experience information of the first service may include: the third core network element collecting information from at least one of the terminal, network management system, and AF (Automatic Application Firewall), performing statistical analysis and prediction of user service experience, and obtaining the experience information of the first service. This embodiment does not limit the specific content of the information collected by the third core network element from various devices or network elements, the specific methods of statistical analysis and prediction, or the specific methods of obtaining the experience information of the first service. In this approach, the specific content sent by the terminal to the third core network element is not limited. For example, the terminal may send a portion of the experience information of the first service to the third core network element, which may include some QoE indicators, etc. This is only an illustrative example and is not intended to limit this approach.

[0281] In another approach, the terminal can send experience information about the first service to a third core network element. Correspondingly, the third core network element receives the experience information about the first service sent by the terminal.

[0282] Optionally, the access network device receiving the experience information of the first service sent by the third core network element may include: the access network device notifying the third core network element of a subscription for service experience information, and receiving the experience information of the first service sent by the third core network element based on the subscription. That is, the access network device can subscribe to the third core network element for a subscription for service experience information according to its own needs, and then the third core network element can send the experience information of the first service it has obtained to the first core network element based on the subscription of the access network device.

[0283] Optionally, the access network device receiving the experience information of the first service sent by the third core network element may include: the access network device directly receiving the experience information of the first service sent by the third core network element. That is, the third core network element may proactively send the obtained experience information of the first service to the access network device, regardless of whether the access network device has subscribed to the third core network element for service experience information notification.

[0284] It should be noted that this is only an illustrative example using the experience information of the first service. In actual processing, the third core network element can send experience information of various other services to the access network device, which will not be elaborated here.

[0285] In some examples, the terminal sends experience information of the first service to the access network device; the access network device receives the experience information of the first service sent by the terminal.

[0286] The experience information of the first service can be carried by control plane messages, which can be uplink RRC (Radio Resource Control) messages or other uplink AS (Access Layer) messages. There are no restrictions on them here.

[0287] Optionally, the terminal may proactively send the experience information of the first service to the access network device. The terminal may proactively send the experience information of the first service on demand, periodically, or according to actual circumstances; no restrictions are imposed here.

[0288] For example, the terminal can proactively send the experience information of the first service in an uplink RRC message to the access network device; the access network device receives the uplink RRC message carrying the experience information of the first service sent by the terminal.

[0289] It should be noted that this is only an illustrative example using the experience information of the first service. In actual processing, the terminal can send experience information of multiple services (including the first service and one or more other services) to the first core network element, which will not be elaborated here.

[0290] Optionally, the terminal can receive an experience information reporting request from the access network device, and then send the experience information of the first service to the access network device. The access network device can send an experience information reporting request to the terminal and receive the experience information of the first service from the terminal.

[0291] The experience information reporting request can also be carried by control plane messages, such as downlink RRC messages or other downlink AS messages.

[0292] The experience information reporting request may carry at least one of the following: an instruction for requesting the reporting of experience information, or identification information of the first service.

[0293] For example, this experience information reporting request can be used to request the reporting of experience information for the first service. The experience information reporting request can carry an instruction for requesting the reporting of experience information and the identification information of the first service. Accordingly, the terminal can send the experience information of the first service to the access network device in an uplink RRC message.

[0294] For example, this experience information reporting request can be used to request the terminal to report experience information for all services, or it can simply carry an instruction to request the reporting of experience information. Correspondingly, the terminal can send the experience information for all its corresponding services in an uplink RRC message to the access network device.

[0295] For example, the experience information reporting request can be used to request the terminal to report experience information for at least two services out of all services. In this case, the experience information reporting request can carry an instruction for requesting the reporting of experience information and identification information for each of the at least two services, which includes a first service and one or more other services. Accordingly, the terminal can send the experience information for each of the at least two services to the access network device in an uplink RRC message.

[0296] After receiving the experience information of the first service, the access network device further includes: based on the experience information of the first service, the access network device selects the adjusted QoS parameters of the first service from multiple sets of QoS parameters of the first service, wherein the adjusted QoS parameters of the first service are one of the multiple sets of QoS parameters related to the first service.

[0297] For example, the experience information of the first service may include the identification information of the first service and the experience score of the first service. In this example, the experience information of the first service may or may not include the QoE metric of the first service.

[0298] Based on the experience information of the first service, the access network device selects the adjusted QoS parameters of the first service from multiple sets of QoS parameters of the first service. This may include: the access network device searching for multiple sets of QoS parameters of the first service based on the identification information of the first service; and selecting the adjusted QoS parameters of the first service from multiple sets of QoS parameters of the first service based on the experience score of the first service.

[0299] Based on the experience score of the first service, the adjusted QoS parameters of the first service are selected from multiple sets of QoS parameters of the first service. This can be achieved by: determining the experience score level corresponding to the experience score of the first service based on the correspondence between each experience score and the optional score level and the experience score of the first service; and selecting the adjusted QoS parameters of the first service from multiple sets of parameters based on the experience score level; or, determining the experience score level corresponding to the experience score of the first service based on the correspondence between each optional score level and the score threshold and the experience score of the first service; and selecting the adjusted QoS parameters of the first service from multiple sets of parameters based on the experience score level.

[0300] For example, the experience information of the first service may include the identification information of the first service and the QoE metric of the first service.

[0301] The access network device selects adjusted QoS parameters for the first service from multiple sets of QoS parameters based on the experience information of the first service. This process may include: the access network device searching for multiple sets of QoS parameters for the first service based on the identification information of the first service; calculating the experience score of the first service based on the QoE index of the first service; and selecting adjusted QoS parameters for the first service from multiple sets of QoS parameters based on the experience score of the first service. The specific processing method for calculating the experience score of the first service based on the QoE index can be configured according to actual conditions and is not limited in this embodiment. The specific processing method for selecting adjusted QoS parameters for the first service from multiple sets of QoS parameters based on the experience score of the first service is the same as in the above example and will not be repeated.

[0302] After the access network device selects the adjusted QoS parameters for the first service, it may include: performing radio resource scheduling based on the adjusted QoS parameters for the first service to ensure the QoS of data transmission.

[0303] It should be noted that the access network device may also receive or obtain experience information from other services. In this case, the relevant processing of the access network device after receiving experience information from other services is the same as that of the first service, so it will not be described in detail.

[0304] In the above embodiments, the first service can be the first service corresponding to the terminal, or it can be the first service corresponding to any other network element. If the first service is the service corresponding to any other network element, the access network device may obtain the experience information of the first service from the NWDAF or the network element. The subsequent processing of the access network device to adjust or select QoS parameters based on the experience information of the first service is the same as in the previous embodiments, and will not be described again.

[0305] The communication method provided in this embodiment will be described by way of example below with reference to Figure 7:

[0306] Step 701: The AF provides the PCF (first core network element) located in the core network with service identification information and one or more sets of corresponding QoS requirements.

[0307] For example, the AF provides the service identification information of service data flow a to the PCF located in the core network as IP 5-tuple a, or the service identification information of service data flow a as SDF IDa (that is, the relevant identification information of the first service is IP 5-tuple or data flow identifier), the QoS requirement is 5QI=1, and the code rate requirement is GBR=2Mbps.

[0308] Step 702: The PCF determines multiple sets of QoS parameters for the service data stream based on the information obtained from the AF (or based on the information obtained from the AF and the operator's policy). These parameters include at least multiple sets of QoS parameters related to the first service in the aforementioned embodiment, and optionally multiple sets of QoS parameters related to other services. The PCF then sends the service data stream identification information and the multiple sets of QoS parameters to the access network device.

[0309] For example, one set of QoS parameters determined by PCF (5QI=1, GBR=2Mbps) corresponds to a medium user service experience score, while another set of QoS parameters (5QI=1, GBR=3Mbps) corresponds to a low user service experience score.

[0310] Optionally, the service data flow identification information sent by the PCF to the access network device can directly use the service identification information obtained in step 701, namely the IP 5-tuple or data flow identifier.

[0311] Optionally, the service data flow identification information sent by the PCF to the access network device can be used to assign a new service data flow identifier to the service data flow. For example, if the service identification information received in step 701 is IP 5-tuple 'a', the PCF assigns a service data flow identifier SDF Ida (i.e., the data flow identifier corresponding to the first service) to the service data flow. In this case, the PCF itself stores the correspondence between the service identification information obtained from the AF and the service data flow identifier assigned by the PCF.

[0312] For example, the PCF sends the access network device {IP 5-tuple a, (Medium user service experience score, 5QI=1, GBR=2Mbps); (Low user service experience score, 5QI=1, GBR=3Mbps)}. Another example is the PCF sending the access network device {SDF ID a, (Medium user service experience score, 5QI=1, GBR=2Mbps); (Low user service experience score, 5QI=1, GBR=3Mbps)}, where the SDF ID can be obtained directly from the AF or assigned by the PCF.

[0313] The PCF sends service data flow identification information and multiple sets of QoS parameters to the access network device. This can be done directly by the PCF or via other network elements such as the SMF. If the PCF sends the data to the access network device via the SMF, the SDF ID can also be assigned by the SMF.

[0314] Step 703: The access network device uses one set of QoS parameters by default for radio resource scheduling based on the multiple sets of QoS parameters of the service data stream obtained from the PCF, ensuring the QoS of data transmission. For example, the access network device can use the first set of QoS parameters from the multiple sets of QoS parameters by default for radio resource scheduling.

[0315] Step 704: The access network device obtains the user's service experience (at least including the experience information of the first service in the foregoing embodiments, and optionally including the experience information of other services) from the NWDAF or from the UE. The user's service experience includes service data flow identification information (identification information of the first service) and service experience information (experience score and / or QoE index).

[0316] Step 704 may include either step 704a or step 704b, as follows:

[0317] Step 704a: The access network device obtains service data flow identification information and service experience information from the NWDAF.

[0318] In Method 1, the access network device notifies the NWDAF of the service experience information. The NWDAF collects information from the UE, network management system, AF, etc., and performs statistics, analysis, and prediction of user service experience to obtain the analysis results of user service experience. The NWDAF sends the analysis results of user service experience (including at least service data flow identification information and service experience information) to the access network device.

[0319] Step 704b: The access network device obtains service data stream identification information and service experience information from the UE.

[0320] That is, implementation method 2: The access network device obtains service experience information directly from the UE through control plane messages between the access network device and the UE, such as uplink RRC messages, such as service experience scores, QoE indicators, or at least one of them, and the control plane messages also include service data flow identification information.

[0321] For example, the UE proactively sends service experience information to the access network device via an uplink RRC message. As another example, the access network device uses a downlink RRC message to request service experience information from the UE, and the UE responds with service experience information based on the access network device's request.

[0322] Step 705: Based on the service experience information, the access network device selects a corresponding set of QoS parameters from multiple sets of QoS parameters of the service data stream for radio resource scheduling to ensure the QoS of data transmission.

[0323] It should be noted that steps 704 to 705 can be executed once or multiple times, and the specific number of times steps 704 to 705 may be executed repeatedly is not limited in this embodiment. In addition, when steps 704 to 705 are executed in different times, the specific services adjusted by the access network device and the specific QoS parameters selected may be the same or different, but the method of selecting QoS parameters each time is the same as the example above, so it will not be described again.

[0324] By adopting the solution provided in this embodiment, the network (such as the first core network element) can obtain the user's service experience, thereby updating the corresponding QoS parameters to better meet the user's service experience. Furthermore, the PCF, i.e., the first core network element, does not need to obtain the user's service experience; instead, it generates or formulates multiple sets of QoS parameters for the service data stream, each set of QoS parameters corresponding to a user's service experience. The access network device obtains the user's service experience from the NWDAF of the core network or the terminal, and selects the corresponding set of QoS parameters for radio resource scheduling, thereby saving network-side process overhead and improving processing efficiency.

[0325] The above-described solution provided in this application allows the terminal to report experience information for a specific service, enabling the network device to adjust the QoS parameters for that service. This ensures that the network side can obtain subjective experiences or evaluations of a service, thereby allowing the network side to reasonably adjust QoS parameters and better align QoS control with service requirements.

[0326] Further, regarding the aforementioned embodiments, the first service can be a service corresponding to the terminal; correspondingly, the first core network element or access network device can adjust the QoS parameters of the first service corresponding to the terminal. In this case, by adopting the solutions provided in the above embodiments, it can be ensured that the network side can obtain the user's subjective experience or subjective evaluation under the first service, thereby ensuring that the network side can reasonably adjust the QoS parameters of the first service corresponding to the terminal, so that the QoS control of the network side better meets the needs of the terminal user under the first service, and ensures that the scheduled network resources can improve the satisfaction of the terminal user.

[0327] Further, regarding the aforementioned embodiments, the first service can be a service corresponding to any network element other than the terminal; correspondingly, the first core network element or access network device can adjust the QoS parameters of the first service corresponding to that network element. In this case, by adopting the solutions provided in the above embodiments, it is possible to ensure that the network side obtains the experience or evaluation of any network element under the first service, thereby ensuring that the network side can reasonably adjust the QoS parameters of the first service corresponding to any network element, so that QoS control can better match or fit the needs of any network element under the first service.

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

[0329] The first communication unit 801 is used to send experience information of the first service, wherein the experience information of the first service is used by the network device to adjust the QoS parameters of the first service.

[0330] The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the quality of experience (QoE) index of the first service.

[0331] The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

[0332] The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

[0333] The first communication unit is configured to perform one of the following: send experience information of the first service to the AF; or send experience information of the first service to the network device.

[0334] The network equipment includes one of the following: a first core network element, or an access network device.

[0335] The first core network element includes a policy control function (PCF).

[0336] Figure 9 is a schematic diagram of the composition structure of a first core network element according to an embodiment of this application, including:

[0337] The second communication unit 901 is used to receive experience information of the first service, wherein the experience information of the first service is used by the first core network element to adjust the QoS parameters of the first service.

[0338] The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the QoE metric of the first service.

[0339] The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

[0340] The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

[0341] The second communication unit is configured to perform one of the following: receive experience information of the first service sent by the AF; or receive experience information of the first service sent by the terminal.

[0342] As shown in Figure 9, it also includes:

[0343] The second processing unit 902 is used to adjust the QoS parameters of the first service based on the experience information of the first service, so as to obtain the adjusted QoS parameters of the first service.

[0344] The second communication unit is used to send updated PCC rules for the first service to the second core network element. The updated PCC rules for the first service include identification information of the first service and adjusted QoS parameters of the first service. The updated PCC rules for the first service are used by the second core network element to adjust the QoS parameters of the first QoS flow. The first QoS flow corresponds to the data flow of one or more services, and the one or more services include the first service.

[0345] The second core network element includes the Session Management Function (SMF).

[0346] The second communication unit is used to send first information to the access network device, wherein the first information includes a data flow identifier corresponding to the first service and adjusted QoS parameters of the first service, and the data flow identifier corresponding to the first service is allocated by the AF or by the first core network element.

[0347] The first core network element includes PCF.

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

[0349] The third communication unit 1001 is used to receive experience information of the first service, wherein the experience information of the first service is used by the access network device to adjust the QoS parameters of the first service.

[0350] The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the QoE metric of the first service.

[0351] The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

[0352] The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

[0353] The third communication unit is configured to perform one of the following: receive experience information of the first service sent by the third core network element; or receive experience information of the first service sent by the terminal.

[0354] The third core network element includes the network data analysis function NWDAF.

[0355] As shown in Figure 10, it also includes:

[0356] The third processing unit 1002 is configured to select an adjusted QoS parameter of the first service from multiple sets of QoS parameters of the first service based on the experience information of the first service, wherein the adjusted QoS parameter of the first service is one of the multiple sets of QoS parameters related to the first service.

[0357] The third communication unit is used to execute the access network device to receive multiple sets of QoS parameters related to the first service sent by the first core network element, wherein the multiple sets of QoS parameters related to the first service are generated by the first core network element based on one or more sets of QoS requirements related to the first service configured by AF.

[0358] The first core network element includes PCF.

[0359] The device in this application embodiment can realize the corresponding functions of the various devices in the foregoing communication 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.).

[0360] Figure 11 is a schematic structural diagram of a communication device 1100 according to an embodiment of this application. The communication device 1100 includes a processor 1110, which can call and run computer programs from a memory to enable the communication device 1100 to implement the methods in the embodiments of this application. In one possible implementation, the communication device 1100 may further include a memory 1120. The processor 1110 can call and run computer programs from the memory 1120 to enable the communication device 1100 to implement the methods 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 communication device 1100 may further include a transceiver 1130, which the processor 1110 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 1130 may include a transmitter and a receiver. The transceiver 1130 may further include antennas, and the number of antennas may be one or more.

[0361] In one possible implementation, the communication device 1100 may be a terminal, a first core network element, or an access network device in the embodiments of this application, and the communication device 1100 may implement the corresponding processes implemented by the terminal, the first core network element, or the access network device in the various methods of the embodiments of this application. For the sake of brevity, these will not be elaborated here.

[0362] Figure 12 is a schematic structural diagram of a chip 1200 according to an embodiment of this application. The chip 1200 includes a processor 1210, which can call and run computer programs from a memory to implement the methods in the embodiments of this application. In one possible implementation, the chip 1200 may further include a memory 1220. The processor 1210 can call and run computer programs from the memory 1220 to implement the methods executed by a terminal, access network device, or first core network element in the embodiments of this application. The memory 1220 may be a separate device independent of the processor 1210, or it may be integrated into the processor 1210. In one possible implementation, the chip 1200 may further include an input interface 1230. The processor 1210 can control the input interface 1230 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 1200 may further include an output interface 1240. The processor 1210 can control the output interface 1240 to communicate with other devices or chips, specifically, it can output information or data to other devices or chips.

[0363] In one possible implementation, the chip can be applied to the terminal, the first core network element, or the access network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal, the first core network element, or the 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 can 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.

[0364] Figure 13 is a schematic block diagram of a communication system 1300 according to an embodiment of this application. The communication system 1300 includes a terminal 1310, a first core network element 1320, and an access network device 1330. The terminal 1310 can be used to implement the corresponding functions implemented by the terminal in the above method. The first core network element 1320 can be used to implement the corresponding functions implemented by the first core network element in the above method. The access network device 1330 can be used to implement the corresponding functions implemented by the access network device in the above method. For simplicity, further details are omitted here.

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

[0366] 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 terminal sends experience information for the first service, which is used by the network device to adjust the Quality of Service (QoS) parameters of the first service.

2. The method according to claim 1, wherein, The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the quality of experience (QoE) index of the first service.

3. The method according to claim 2, wherein, The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

4. The method according to claim 2 or 3, wherein, The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

5. The method according to any one of claims 1-4, wherein, The terminal sends experience information for the first service, including one of the following: The terminal sends the experience information of the first service to the application function AF; The terminal sends the experience information of the first service to the network device.

6. The method according to any one of claims 1-5, wherein, The network equipment includes one of the following: a first core network element, or an access network device.

7. The method according to claim 6, wherein, The first core network element includes a policy control function (PCF).

8. A communication method, comprising: The first core network element receives experience information of the first service, wherein the experience information of the first service is used by the first core network element to adjust the QoS parameters of the first service.

9. The method according to claim 8, wherein, The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the QoE metric of the first service.

10. The method according to claim 9, wherein, The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

11. The method according to claim 9 or 10, wherein, The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

12. The method according to any one of claims 8-11, wherein, The first core network element receives experience information for the first service, including one of the following: The first core network element receives the experience information of the first service sent by the AF; The first core network element receives the experience information of the first service sent by the terminal.

13. The method according to any one of claims 8-12, wherein, After the first core network element receives the experience information of the first service, it also includes: The first core network element adjusts the QoS parameters of the first service based on the experience information of the first service, thereby obtaining the adjusted QoS parameters of the first service.

14. The method according to claim 13, wherein, After obtaining the adjusted QoS parameters of the first service, the process further includes: The first core network element sends an updated PCC rule for the first service to the second core network element. The updated PCC rule for the first service includes the identification information of the first service and the adjusted QoS parameters of the first service. The updated PCC rule for the first service is used by the second core network element to adjust the QoS parameters of the first QoS flow. The first QoS flow corresponds to the data flow of one or more services, and the one or more services include the first service.

15. The method according to claim 14, wherein, The second core network element includes the Session Management Function (SMF).

16. The method according to claim 13, wherein, After obtaining the adjusted QoS parameters of the first service, the process further includes: The first core network element sends first information to the access network device, wherein the first information includes the data flow identifier corresponding to the first service and the adjusted QoS parameters of the first service, and the data flow identifier corresponding to the first service is allocated by the AF or by the first core network element.

17. The method according to any one of claims 8-16, wherein, The first core network element includes PCF.

18. A communication method, comprising: The access network device receives experience information of a first service, wherein the experience information of the first service is used by the access network device to adjust the QoS parameters of the first service.

19. The method according to claim 18, wherein, The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the QoE metric of the first service.

20. The method according to claim 19, wherein, The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

21. The method according to claim 19 or 20, wherein, The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

22. The method according to any one of claims 18-21, wherein, The access network device receives experience information for the first service, including one of the following: The access network device receives the experience information of the first service sent by the third core network element; The access network device receives the experience information of the first service sent by the terminal.

23. The method according to claim 22, wherein, The third core network element includes the network data analysis function NWDAF.

24. The method according to any one of claims 18-23, wherein, After receiving the experience information of the first service, the access network device further includes: Based on the experience information of the first service, the access network device selects the adjusted QoS parameters of the first service from multiple sets of QoS parameters of the first service, wherein the adjusted QoS parameters of the first service are one of the multiple sets of QoS parameters related to the first service.

25. The method according to claim 24, wherein, Before the access network device receives the experience information of the first service, it also includes: The access network device receives multiple sets of QoS parameters related to the first service from the first core network element, wherein the multiple sets of QoS parameters related to the first service are generated by the first core network element based on one or more sets of QoS requirements related to the first service configured by AF.

26. The method according to claim 25, wherein, The first core network element includes PCF.

27. A terminal, comprising: The first communication unit is used to send experience information of the first service, wherein the experience information of the first service is used by the network device to adjust the quality of service (QoS) parameters of the first service.

28. The method according to claim 27, wherein, The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the quality of experience (QoE) index of the first service.

29. The method according to claim 28, wherein, The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

30. The method according to claim 28 or 29, wherein, The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

31. The method according to any one of claims 27-30, wherein, The first communication unit is configured to perform one of the following: send experience information of the first service to the application function AF; or send experience information of the first service to the network device.

32. The method according to any one of claims 27-31, wherein, The network equipment includes one of the following: a first core network element, or an access network device.

33. The method according to claim 32, wherein, The first core network element includes a policy control function (PCF).

34. A first core network element, comprising: The second communication unit is used to receive experience information of the first service, wherein the experience information of the first service is used by the first core network element to adjust the QoS parameters of the first service.

35. The method according to claim 34, wherein, The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the QoE metric of the first service.

36. The method according to claim 35, wherein, The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

37. The method according to claim 35 or 36, wherein, The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

38. The method according to any one of claims 34-37, wherein, The second communication unit is configured to perform one of the following: receive experience information of the first service sent by the AF; or receive experience information of the first service sent by the terminal.

39. The method according to any one of claims 34-38, further comprising: The second processing unit is used to adjust the QoS parameters of the first service based on the experience information of the first service, so as to obtain the adjusted QoS parameters of the first service.

40. The method according to claim 39, wherein, The second communication unit is used to send updated PCC rules for the first service to the second core network element. The updated PCC rules for the first service include identification information of the first service and adjusted QoS parameters of the first service. The updated PCC rules for the first service are used by the second core network element to adjust the QoS parameters of the first QoS flow. The first QoS flow corresponds to the data flow of one or more services, and the one or more services include the first service.

41. The method according to claim 40, wherein, The second core network element includes the Session Management Function (SMF).

42. The method according to claim 39, wherein, The second communication unit is used to send first information to the access network device, wherein the first information includes a data flow identifier corresponding to the first service and adjusted QoS parameters of the first service, and the data flow identifier corresponding to the first service is allocated by the AF or by the first core network element.

43. The method according to any one of claims 34-42, wherein, The first core network element includes PCF.

44. An access network device, comprising: The third communication unit is used to receive experience information of the first service, wherein the experience information of the first service is used by the access network device to adjust the QoS parameters of the first service.

45. The method according to claim 44, wherein, The experience information of the first service includes at least one of the following: the identification information of the first service, the experience score of the first service, and the QoE metric of the first service.

46. ​​The method according to claim 45, wherein, The identification information of the first service includes at least one of the following: the data stream filter corresponding to the first service, the data stream identifier corresponding to the first service, the identifier of the first service, and the type of the first service.

47. The method according to claim 45 or 46, wherein, The QoE metrics include at least one of the following: throughput, throughput, initial playback latency, cache status, cache level, list of start / stop operations, and start wait time.

48. The method according to any one of claims 44-47, wherein, The third communication unit is configured to perform one of the following: receive experience information of the first service sent by the third core network element; or receive experience information of the first service sent by the terminal.

49. The method according to claim 48, wherein, The third core network element includes the network data analysis function NWDAF.

50. The method according to any one of claims 44-49, further comprising: The third processing unit is configured to select an adjusted QoS parameter for the first service from multiple sets of QoS parameters for the first service based on the experience information of the first service, wherein the adjusted QoS parameter for the first service is one of multiple sets of QoS parameters related to the first service.

51. The method according to claim 50, wherein, The third communication unit is used to execute the access network device to receive multiple sets of QoS parameters related to the first service sent by the first core network element, wherein the multiple sets of QoS parameters related to the first service are generated by the first core network element based on one or more sets of QoS requirements related to the first service configured by AF.

52. The method according to claim 51, wherein, The first core network element includes PCF.

53. 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 1 to 7.

54. A first core network element, comprising: A transceiver, a processor, and a memory for storing computer programs, the transceiver for communicating with other devices, and the processor for calling and running the computer programs stored in the memory to cause the first core network element to perform the method as described in any one of claims 8 to 17.

55. 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 described in any one of claims 18 to 26.

56. 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 7, or claims 8 to 17, or claims 18 to 26.

57. A computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the method as claimed in any one of claims 1 to 7, or claims 8 to 17, or claims 18 to 26.

58. A computer program product comprising computer program instructions that cause a computer to perform the method as claimed in any one of claims 1 to 7, or claims 8 to 17, or claims 18 to 26.

59. A computer program that causes a computer to perform the method as claimed in any one of claims 1 to 7, or claims 8 to 17, or claims 18 to 26.

Images