Communication method, communication apparatus and communication system

Abstract

The present application provides a communication method, a communication apparatus and a communication system. The method monitors a QoS flow on the basis of the granularity of PDU sets, each PDU set comprising a plurality of data packets, thus improving the QoS flow monitoring efficiency; moreover, the method can further expose a monitoring result outward by means of a second network element, such that a network element receiving the monitoring result can control a service on the basis of the monitoring result, thus improving the accuracy of service control and avoiding blind control over services.

Description

Communication method, communication device and communication system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on November 29, 2023, with application number 202311633661.3 and invention name "Communication Method, Communication Device and Communication System", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of wireless communication technology, and in particular to a communication method, a communication device, and a communication system. Background Art

[0004] Existing quality of service (QoS) mechanisms guarantee service at the packet level. Packets within the same service flow are mapped to the same QoS flow for transmission. Packets from different service flows may be mapped to the same QoS flow or to different QoS flows. Different packets within the same QoS flow are individually processed and transmitted based on the same QoS parameters. In other words, all packets within the same QoS flow receive the same, undifferentiated treatment during transmission.

[0005] To obtain the transmission status of QoS flows, QoS flows can be monitored at the packet granularity. However, to support the transmission of real-time media services such as extended reality (XR) and cloud gaming, a QoS transmission guarantee mechanism at the packet aggregate granularity has been introduced. While QoS guarantee and transmission are performed at the packet aggregate granularity, how to monitor and report QoS transmission status at the packet aggregate granularity remains to be solved.

[0006] Summary of the Invention

[0007] The present application provides a communication method, a communication device, and a communication system to improve the efficiency of monitoring QoS flows.

[0008] In a first aspect, an embodiment of the present application provides a communication method, which can be performed by a first network element or a chip applied to the first network element. The method includes: receiving first information, the first information being used to monitor a protocol data unit (PDU) set of a QoS flow and reporting a monitoring result of the PDU set; monitoring the PDU set carried by the QoS flow based on the first information; and sending the monitoring result of the PDU set to a second network element.

[0009] The above scheme monitors and reports the QoS flow at the granularity of the PDU set. Each PDU set includes multiple data packets, which can monitor and report the transmission status of the PDU set granularity within the QoS flow. Compared with monitoring the QoS flow at the granularity of the data packet, the method of monitoring the QoS flow at the granularity of the PDU set can improve the efficiency of monitoring by increasing the granularity of monitoring, and is more suitable for business scenarios where data is encoded in the form of PDU sets, which can improve the efficiency of business transmission. In addition, the scheme can also open the monitoring results to the outside world through the second network element, so that the network element that receives the monitoring results can perceive the PDU set granularity transmission status of the QoS flow based on the monitoring results, and further control the business, such as adjusting the business bit rate or the forward error correction code (FEC) redundancy of the business according to the monitoring results, which helps to improve the accuracy of business control and avoid blind control of the business.

[0010] In one possible implementation method, the first information includes a PDU set loss rate (PDU Set Loss Rate) event, and the PDU set loss rate event indicates that the monitored object is the PDU set loss rate; monitoring the PDU set carried by the QoS flow according to the first information includes: monitoring the PDU set loss rate of the QoS flow according to the first information.

[0011] In the above scheme, the first network element can measure the PDU set loss rate of the QoS flow, and can open the PDU set loss rate to the outside through the second network element, so that the entity that receives the PDU set loss rate can control the service based on the PDU set loss rate, which helps to improve the accuracy of service control and avoids blind control of the service. For example, the application server obtains the PDU set loss rate and makes corresponding adjustments on the service side. For example, when the PDU set loss rate is relatively high, it means that the current network is not good. The application server can reduce the bit rate or increase the proportion of FEC redundancy, thereby improving the network situation while ensuring the service experience.

[0012] In one possible implementation method, the first network element is an access network device, and the PDU aggregate loss rate includes one or more of the following:

[0013] The proportion of PDU sets that the access network device fails to send to the terminal device, that is, the ratio of the number of PDU sets that fail to send to the terminal device in the QoS flow to the total number of PDU sets sent to the terminal device by the access network device;

[0014] The ratio of discarded PDUs due to packet loss, that is, the ratio of the number of PDUs that failed to be successfully sent to the terminal device due to packet loss in the QoS flow to the total number of PDUs sent by the access network device to the terminal device;

[0015] The ratio of PDU sets discarded due to transmission failures, that is, the ratio of the number of PDU sets in the QoS flow that failed to be successfully sent to the terminal device due to transmission failures to the total number of PDU sets sent from the access network device to the terminal device;

[0016] The ratio of data packets that failed to be transmitted, that is, the ratio of the number of data packets sent to the terminal device that failed to be transmitted in the QoS flow to the total number of data packets sent by the access network device to the terminal device;

[0017] The total number of data packets that failed to be transmitted, that is, the number of data packets sent to the terminal device within the QoS flow that failed to be transmitted; or

[0018] The ratio of discarded PDU sets due to packet loss based on PDU set importance, that is, the ratio of the number of PDU sets discarded due to different PDU set importance to the total number of PDU sets sent by the access network device to the terminal device.

[0019] In one possible implementation method, the first network element is a terminal device, and the PDU aggregate loss rate includes one or more of the following:

[0020] The proportion of PDU sets that the terminal device fails to send to the access network device, that is, the ratio of the number of PDU sets that fail to send to the access network device in the QoS flow to the total number of PDU sets sent by the terminal device to the access network device;

[0021] The ratio of discarded PDUs due to transmission failures, that is, the ratio of the number of PDUs in the QoS flow that were not successfully sent to the access network device due to packet transmission failures to the total number of PDUs sent from the terminal device to the access network device;

[0022] The ratio of data packets that failed to be transmitted, that is, the ratio of the number of data packets sent to the access network device that failed to be transmitted in the QoS flow to the total number of data packets sent by the terminal device to the access network device;

[0023] The total number of data packets that failed to be transmitted, that is, the number of data packets within the QoS flow that failed to be transmitted to the access network device; or

[0024] The ratio of discarded PDU sets due to packet loss based on PDU set importance, that is, the ratio of the number of PDU sets discarded due to different PDU set importance to the total number of PDU sets sent by the terminal device to the access network device.

[0025] In a possible implementation method, the monitoring result includes the PDU set loss rate corresponding to the importance of each PDU set.

[0026] In one possible implementation method, the first information includes a PDU set delay (PDU Set Delay) event, and the PDU set delay event indicates that the monitored object is the PDU set delay; monitoring the bearer PDU set of the QoS flow according to the first information includes: monitoring the PDU set delay of the QoS flow according to the first information.

[0027] In the above solution, the first network element can measure the PDU aggregate delay of the QoS flow, and can open the PDU aggregate delay to the outside through the second network element, so that the entity that receives the PDU aggregate delay can control the service based on the PDU aggregate delay, which helps to improve the accuracy of service control and avoids blind control of the service. For example, the application server obtains the PDU aggregate delay and makes corresponding adjustments on the service side. For example, when the PDU aggregate delay is relatively high, it means that the current network is not good. The application server can reduce the bit rate or increase the proportion of FEC redundancy, thereby improving the network situation while ensuring the service experience.

[0028] In one possible implementation method, the first network element is an access network device, and the PDU aggregate delay includes one or more of the following:

[0029] The time taken by the access network device to successfully transmit the PDU set to the terminal device;

[0030] The time taken by the access network device to successfully transmit the PDU set to the terminal device within the PDU set delay budget;

[0031] The proportion or number of PDU sets successfully transmitted by the access network device to the terminal device within the PDU set delay budget time;

[0032] The percentage or number of PDU sets successfully transmitted to the terminal device by the access network device beyond the PDU set delay budget time; or

[0033] The time taken by the access network device to successfully transmit the PDU set to the terminal device exceeds the PDU set delay budget time.

[0034] In one possible implementation method, the first network element is a terminal device, and the PDU aggregate delay includes one or more of the following:

[0035] The time taken by the terminal device to successfully transmit the PDU set to the access network device;

[0036] The time taken by the terminal device to successfully transmit the PDU set to the access network device within the PDU set delay budget;

[0037] The proportion or number of PDU sets successfully transmitted by the terminal device to the access network device within the PDU set delay budget time;

[0038] The percentage or number of PDU sets successfully transmitted to the access network device by the terminal device beyond the PDU set delay budget time; or

[0039] The time taken by the terminal device to successfully transmit the PDU set to the access network device exceeds the PDU set delay budget time.

[0040] In a possible implementation method, the monitoring result includes the PDU aggregate delay, or includes the sum of the PDU aggregate delay and the N3 segment core network packet delay budget (core network packet delay budget, CN PDB).

[0041] In a possible implementation method, the monitoring result includes the PDU set delay corresponding to the importance of each PDU set.

[0042] In one possible implementation method, the first network element is a user plane network element; the first information includes a PDU set spread delay (PDU Set Spread Delay) event, and the PDU set spread delay event indicates that the monitoring object is the PDU set spread delay; the monitoring of the PDU set carried by the QoS flow according to the first information includes: monitoring the PDU set spread delay of the QoS flow according to the first information.

[0043] In the above scheme, the first network element can measure the PDU set extended delay of the QoS flow, and can open the PDU set extended delay to the outside through the second network element, so that the entity that receives the PDU set extended delay can control the service based on the PDU set extended delay, which helps to improve the accuracy of service control and avoids blind control of the service. For example, after the application server or policy control network element obtains the PDU set extended delay, the application server adjusts the traffic characteristics of the service PDU set. For example, when the PDU set extended delay is relatively high, it means that the current network is not good. The application server can reduce the bit rate or increase the proportion of FEC redundancy, thereby improving the network situation while ensuring the service experience. The policy control network element can adjust the QoS parameters according to the PDU set extended delay.

[0044] In one possible implementation method, the PDU aggregate extended delay includes one or more of the following:

[0045] The time interval between the arrival of the first packet of the PDU set at the user plane network element and the arrival of the last packet at the user plane network element;

[0046] The time interval between the first packet of the PDU set arriving at the user plane network element and the last packet leaving the user plane network element;

[0047] The time interval between the first packet of a PDU set leaving the user plane network element and the last packet leaving the user plane network element; or

[0048] The proportion of the target PDU set, wherein the time interval between the first packet of the target PDU set arriving at the user plane network element and the last packet arriving at the user plane network element does not exceed a preset threshold.

[0049] In a possible implementation method, the monitoring result is a PDU set extended delay corresponding to the importance of each PDU set.

[0050] In one possible implementation method, the first network element is a session management network element; the first information includes an enabled status event of PDU set QoS processing, and the enabled status event of PDU set QoS processing indicates that the monitored object is the enabled status of PDU set QoS processing; monitoring the PDU set carried by the QoS flow based on the first information includes: monitoring the enabled status of the PDU set QoS processing of the QoS flow based on the first information.

[0051] In the above scheme, the first network element can measure the enabled status of the PDU set QoS processing of the QoS flow, that is, determine whether the PDU set QoS processing of the QoS flow is turned on, and can open the enabled status of the PDU set QoS processing to the outside through the second network element, so that the entity that receives the enabled status of the PDU set QoS processing can perceive the enabled status of the PDU set QoS processing, thereby achieving accurate control of the service and avoiding blind control of the service, such as the policy control network element obtains the enabled status of the PDU set QoS processing for different billing processing or the third-party application obtains the enabled status of the PDU set QoS processing.

[0052] In one possible implementation method, the monitoring of the enabled status of the PDU set QoS processing of the QoS flow includes: receiving a capability indication from an access network device, the capability indication being used to indicate that the access network device has the capability of PDU set QoS processing; and monitoring the enabled status of the PDU set QoS processing of the QoS flow based on the capability indication.

[0053] In one possible implementation method, the enabling status of the PDU set QoS processing of the QoS flow is monitored according to the capability indication, including: sending the QoS parameters of the PDU set to the access network device according to the capability indication, and then determining that the PDU set QoS processing of the QoS flow has been enabled.

[0054] In one possible implementation method, the monitoring of the enabled status of the PDU set QoS processing of the QoS flow includes: sending the QoS parameters of the PDU set to the access network device; receiving a capability indication from the access network device, and then determining that the PDU set QoS processing of the QoS flow has been enabled, wherein the capability indication is used to indicate that the access network device has the PDU set QoS processing capability.

[0055] In one possible implementation method, the first information includes a reporting indication, and the reporting indication is used to indicate that the monitoring results of the PDU set are reported to the second network element; sending the monitoring results of the PDU set to the second network element includes: sending the monitoring results to the second network element according to the reporting indication.

[0056] The above solution notifies the first network element to send monitoring results to the second network element through a reporting indication, so that the first network element can accurately know that it needs to report the monitoring results to the second network element based on the reporting indication, which helps to improve the reporting speed and accuracy of the reporting.

[0057] In a second aspect, an embodiment of the present application provides a communication method, which can be executed by an application function network element or a chip applied to an application function network element. The method includes: sending a subscription request for subscribing to monitoring results of a PDU set of a service flow; and receiving monitoring results of the PDU set of the service flow.

[0058] The above scheme monitors and reports the QoS flow at the granularity of the PDU set. Each PDU set includes multiple data packets, which can realize the monitoring and reporting of the transmission status of the PDU set granularity within the QoS flow. Compared with monitoring the QoS flow at the granularity of the data packet, the method of monitoring the QoS flow at the granularity of the PDU set can improve the efficiency of monitoring by increasing the granularity of monitoring, and is more suitable for business scenarios where data is encoded in the form of PDU sets, which can improve the efficiency of business transmission. In addition, the application function network element can receive the monitoring results, so that the business can be controlled based on the monitoring results, such as adjusting the bit rate of the business or the FEC redundancy of the business according to the monitoring results, which helps to improve the accuracy of business control and avoid blind control of the business.

[0059] In one possible implementation method, the subscription request includes a PDU set loss rate event, and the PDU set loss rate event indicates that the monitoring object is the PDU set loss rate; the monitoring result of the PDU set of the business flow is received, including: receiving the PDU set loss rate of the business flow.

[0060] In the above solution, the monitoring results obtained by the application function network element include the PDU set loss rate, so that the application function network element can control the service based on the PDU set loss rate. For example, when the PDU set loss rate is relatively high, it means that the current network is not good. The application server can reduce the bit rate or increase the proportion of FEC redundancy, thereby improving the network situation while ensuring the service experience, which helps to improve the accuracy of service control and avoid blind control of the service.

[0061] In one possible implementation method, the PDU aggregate loss rate is from an access network device, and the PDU aggregate loss rate includes one or more of the following:

[0062] The percentage of PDUs that the access network device fails to send to the terminal device;

[0063] The percentage of PDU sets discarded due to packet loss;

[0064] The percentage of PDU sets discarded due to transmission failures;

[0065] The percentage of data packets that failed to be transmitted;

[0066] The total number of packets that failed to be transmitted; or

[0067] The percentage of discarded PDU sets due to packet loss based on the importance of the PDU set.

[0068] In one possible implementation method, the PDU aggregate loss rate is from a terminal device, and the PDU aggregate loss rate includes one or more of the following:

[0069] The percentage of PDU sets that the terminal device failed to send to the access network device;

[0070] The percentage of PDU sets discarded due to transmission failures;

[0071] The percentage of data packets that failed to be transmitted;

[0072] The total number of packets that failed to be transmitted; or

[0073] The percentage of discarded PDU sets due to packet loss based on the importance of the PDU set.

[0074] In a possible implementation method, the monitoring result includes the PDU set loss rate corresponding to the importance of each PDU set.

[0075] In one possible implementation method, the subscription request includes a PDU aggregate delay event, and the PDU aggregate delay event indicates that the monitoring object is the PDU aggregate delay; the monitoring result of receiving the PDU aggregate of the service flow includes: the PDU aggregate delay of receiving the service flow, or the sum of the PDU aggregate delay and the N3 segment core network packet delay budget CN PDB.

[0076] In the above solution, the monitoring results obtained by the application function network element include the PDU aggregate delay, or the sum of the PDU aggregate delay and the N3 segment CN PDB, so that the application function network element can control the service based on the monitoring results. For example, when the PDU aggregate delay is relatively high, it means that the current network is not good. The application server can reduce the bit rate or increase the proportion of FEC redundancy, thereby improving the network situation while ensuring the service experience, which helps to improve the accuracy of service control and avoid blind control of the service.

[0077] In one possible implementation method, the monitoring result comes from an access network device, and the PDU aggregate delay includes one or more of the following:

[0078] The time taken by the access network device to successfully transmit the PDU set to the terminal device;

[0079] The time taken by the access network device to successfully transmit the PDU set to the terminal device within the PDU set delay budget; the proportion or number of PDU sets successfully transmitted by the access network device to the terminal device within the PDU set delay budget;

[0080] The percentage or number of PDU sets successfully transmitted to the terminal device by the access network device beyond the PDU set delay budget time; or

[0081] The time taken by the access network device to successfully transmit the PDU set to the terminal device exceeds the PDU set delay budget time.

[0082] In one possible implementation method, the monitoring result comes from a terminal device, and the PDU aggregate delay includes one or more of the following:

[0083] The time taken by the terminal device to successfully transmit the PDU set to the access network device;

[0084] The time taken by the terminal device to successfully transmit the PDU set to the access network device within the PDU set delay budget;

[0085] The proportion or number of PDU sets successfully transmitted by the terminal device to the access network device within the PDU set delay budget time;

[0086] The percentage or number of PDU sets successfully transmitted to the access network device by the terminal device beyond the PDU set delay budget time; or

[0087] The time taken by the terminal device to successfully transmit the PDU set to the access network device exceeds the PDU set delay budget time.

[0088] In one possible implementation method, the subscription request includes a PDU set extended delay event, and the PDU set extended delay event indicates that the monitoring object is the PDU set extended delay; the monitoring result of receiving the PDU set of the business flow includes: receiving the PDU set extended delay of the business flow.

[0089] In the above solution, the monitoring results obtained by the application function network element include the PDU set extended delay, so that the application function network element can control the service based on the PDU set extended delay. For example, when the PDU set extended delay is relatively high, it means that the current network is not good. The application server can reduce the bit rate or increase the proportion of FEC redundancy, thereby improving the network situation while ensuring the service experience, which helps to improve the accuracy of service control and avoid blind control of the service.

[0090] In one possible implementation method, the monitoring result comes from a user plane network element, and the PDU aggregate extended delay includes one or more of the following:

[0091] The time interval between the arrival of the first packet of the PDU set at the user plane network element and the arrival of the last packet at the user plane network element;

[0092] The time interval between the first packet of the PDU set arriving at the user plane network element and the last packet leaving the user plane network element;

[0093] The time interval between the first packet of a PDU set leaving the user plane network element and the last packet leaving the user plane network element; or

[0094] The proportion of the target PDU set, wherein the time interval between the first packet of the target PDU set arriving at the user plane network element and the last packet arriving at the user plane network element does not exceed a preset threshold.

[0095] In one possible implementation method, the subscription request includes an enabled status event of the PDU set QoS processing, and the enabled status event of the PDU set QoS processing indicates that the monitoring object is the enabled status of the PDU set QoS processing; the monitoring result of receiving the PDU set of the service flow includes: receiving the enabled status of the PDU set QoS processing of the service flow.

[0096] In the above solution, the monitoring results obtained by the application function network element include the enabled status of the PDU set QoS processing, so that the application function network element can control the service based on the enabled status of the PDU set QoS processing, which helps to improve the accuracy of service control and avoid blind control of the service.

[0097] In one possible implementation method, the subscription request includes a reporting indication, and the reporting indication is used to indicate reporting the monitoring results of the PDU set to the second network element; the receiving of the monitoring results of the PDU set of the service flow includes: receiving the monitoring results from the second network element.

[0098] In a third aspect, embodiments of the present application provide a communications device, which may be a first network element or a chip for the first network element. The device has the function of implementing any of the implementation methods of the first aspect described above. The function may be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0099] In a fourth aspect, embodiments of the present application provide a communications device, which may be an application function network element or a chip for an application function network element. The device has the function of implementing any of the implementation methods of the second aspect described above. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0100] In a fifth aspect, an embodiment of the present application provides a communication device, comprising a unit or means for executing each step of any implementation method in the above-mentioned first to second aspects.

[0101] In a sixth aspect, an embodiment of the present application provides a communication device, comprising a processor and an interface circuit, wherein the processor is configured to communicate with other devices via the interface circuit and execute any of the implementation methods in the first to second aspects above. The processor comprises one or more.

[0102] In a seventh aspect, an embodiment of the present application provides a communication device, comprising a processor, the processor being configured to call a program to execute any of the implementation methods in the first to second aspects above. The processor may be one or more.

[0103] Optionally, the communication device may further include a memory, which is coupled to the processor and may be located inside or outside the device.

[0104] In an eighth aspect, an embodiment of the present application provides a communication device, comprising a processor; when the device is running, the processor executes computer instructions to enable the device to execute any implementation method in the above-mentioned first to second aspects.

[0105] Optionally, the communication device may further include a memory for storing the computer instructions.

[0106] In the ninth aspect, an embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run by a communication device, any implementation method in the above-mentioned first to second aspects is executed.

[0107] In the tenth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when run on a communication device, enables any implementation method in the above-mentioned first to second aspects to be executed.

[0108] In the eleventh aspect, an embodiment of the present application further provides a chip system, comprising: a processor for executing any implementation method in the above-mentioned first to second aspects.

[0109] In the twelfth aspect, an embodiment of the present application also provides a communication system, including a first network element, used to receive first information, wherein the first information is used to monitor the PDU set carried by the QoS flow and report the monitoring results of the PDU set; based on the first information, the PDU set carried by the QoS flow is monitored; and the monitoring results of the PDU set are sent to a second network element; the second network element is used to receive the monitoring results.

[0110] In the thirteenth aspect, an embodiment of the present application also provides a communication system, including an application function network element, used to send a subscription request to a policy control network element, the subscription request being used to subscribe to the monitoring results of the PDU set of the service flow; and receiving the monitoring results of the PDU set of the service flow from the policy control network element; the policy control network element is used to receive the subscription request; and send the monitoring results to the application function network element. BRIEF DESCRIPTION OF THE DRAWINGS

[0111] Figure 1(a) is a schematic diagram of the 5G network architecture based on service-oriented architecture;

[0112] Figure 1(b) is a schematic diagram of the 5G network architecture based on point-to-point interfaces;

[0113] FIG2 is a flow chart of a communication method provided in an embodiment of the present application;

[0114] FIG3 is a flow chart of another communication method provided in an embodiment of the present application;

[0115] FIG4 is a flow chart of another communication method provided in an embodiment of the present application;

[0116] FIG5 is a flow chart of another communication method provided in an embodiment of the present application;

[0117] FIG6 is a flow chart of another communication method provided in an embodiment of the present application;

[0118] FIG7 is a flow chart of another communication method provided in an embodiment of the present application;

[0119] FIG8 is a flow chart of another communication method provided in an embodiment of the present application;

[0120] FIG9 is a flow chart of another communication method provided in an embodiment of the present application;

[0121] FIG10 is a flow chart of another communication method provided in an embodiment of the present application;

[0122] FIG11 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0123] FIG12 is a schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0124] To meet the challenges of wireless broadband technology and maintain the leading edge of the 3rd Generation Partnership Project (3GPP) network, the 3GPP standards group has developed a next-generation mobile communications network system architecture, known as the fifth-generation (5G) network architecture. This architecture not only supports access to the 5G core network (CN) using 3GPP-defined radio access technologies (such as Long Term Evolution (LTE) and 5G Radio Access Network (RAN)), but also supports access to the core network using non-3GPP access technologies via the non-3GPP interworking function (N3IWF) or the next-generation packet data gateway (ngPDG).

[0125] Figure 1(a) shows a schematic diagram of a 5G network architecture based on a service-oriented architecture. The 5G network architecture shown in Figure 1(a) may include access network equipment and core network equipment. Terminal devices access the data network (DN) through the access network equipment and core network equipment. Among them, the core network equipment includes but is not limited to some or all of the following network elements: authentication server function (AUSF) network element (not shown in the figure), unified data management (UDM) network element, unified data repository (UDR) network element, network storage function (NRF) network element (not shown in the figure), network exposure function (NEF) network element (not shown in the figure), application function (AF) network element, policy control function (PCF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, binding support function (BSF) network element (not shown in the figure).

[0126] The terminal device can be user equipment (UE), a mobile station, a mobile terminal device, etc. The terminal device can be widely used in various scenarios, for example, device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, an urban air vehicle (such as an unmanned aerial vehicle, a helicopter, etc.), a ship, a robot, a robotic arm, a smart home device, etc. For the sake of convenience, this application uses UE as an example of a terminal device for illustration, and any UE appearing in any subsequent position can be replaced by a terminal device.

[0127] Access network equipment can be radio access network equipment (RAN equipment) or wired access network equipment. Radio access network equipment includes 3GPP access network equipment, untrusted non-3GPP access network equipment, and trusted non-3GPP access network equipment. 3GPP access network equipment includes, but is not limited to, evolved NodeBs (eNodeBs) in LTE, next-generation NodeBs (gNBs) in 5G mobile communication systems, base stations in future mobile communication systems, or modules or units that perform some of the functions of base stations, such as centralized units (CUs) and distributed units (DUs). Untrusted non-3GPP access network equipment includes, but is not limited to, untrusted non-3GPP access gateways or N3IWFs, untrusted wireless local area network (WLAN) access points (APs), switches, and routers. Trusted non-3GPP access network equipment includes, but is not limited to, trusted non-3GPP access gateways, trusted WLAN APs, switches, and routers. Wired access network equipment includes, but is not limited to, wireline access gateways, fixed-line network equipment, switches, and routers. For ease of explanation, this application uses a base station as an example of an access network device, and any base station appearing at any subsequent location can be replaced by an access network device.

[0128] Base stations and UEs can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and UEs.

[0129] The AMF network element performs functions such as mobility management and access authentication / authorization. It is also responsible for transferring user policies between the UE and the PCF.

[0130] The SMF network element includes functions such as performing session management, executing control policies issued by the PCF network element, selecting the UPF network element, or allocating the UE's Internet Protocol (IP) address.

[0131] The UPF network element includes functions such as user plane data forwarding, session / flow-level billing statistics, or bandwidth limitation.

[0132] UDM network elements include functions such as executing and managing contract data or user access authorization.

[0133] UDR includes functions for accessing data such as contract data, policy data, or application data.

[0134] NEF network element is used to support the opening of capabilities and events.

[0135] The AF network element communicates application-side requirements to the network, such as Quality of Service (QoS) requirements or user status event subscriptions. The AF can be a third-party functional entity or an application service deployed by an operator, such as the IP Multimedia Subsystem (IMS) voice call service. AF network elements include those within the core network (i.e., the operator's AF network element) and third-party AF network elements (such as an enterprise's application server).

[0136] The PCF network element includes policy control functions such as billing for sessions and service flow levels, QoS bandwidth guarantee and mobility management, or UE policy decision-making. PCF network elements include access and mobility management policy control function (AM PCF) network element and session management policy control function (SM PCF) network element. Among them, the AM PCF network element is used to formulate AM policy and user policy for UE. The AM PCF network element can also be called a policy control network element that provides services for UE (PCF for a UE). The SM PCF network element is used to formulate session management policy (SMpolicy) for the session. The SM PCF network element can also be called a policy control network element that provides services for protocol data unit (PDU) sessions ((PCF for a PDU session))).

[0137] NRF network elements can be used to provide network element discovery functions, providing network element information corresponding to the network element type based on requests from other network elements. NRF network elements also provide network element management services, such as network element registration, update, deregistration, or network element status subscription and push.

[0138] BSF network element can provide BSF service registration / deregistration / update, connection detection with NRF network element, session binding information creation, UE information acquisition, session binding information query for duplicate IP addresses, etc.

[0139] The AUSF network element is responsible for authenticating users to determine whether users or devices are allowed to access the network.

[0140] A DN is a network located outside of a carrier network. A carrier network can connect to multiple DNs, and a variety of services can be deployed on the DN, providing UEs with data and / or voice services. For example, a DN is the private network of a smart factory. Sensors installed in the workshop can be UEs. The DN houses a control server for these sensors, which can provide services to the sensors. The sensors can communicate with the control server, receive instructions from the control server, and transmit collected sensor data to the control server based on the instructions. Another example is a DN that is a company's internal office network. An employee's mobile phone or computer can be a UE, allowing them to access information and data resources on the company's internal office network.

[0141] In Figure 1(a), Npcf, Nudr, Nudm, Naf, Namf, and Nsmf are the service-oriented interfaces provided by the PCF, UDR, UDM, AF, AMF, and SMF, respectively, for invoking corresponding service-oriented operations. N1, N2, N3, N4, and N6 are interface serial numbers, and their meanings are as follows:

[0142] 1) N1: The interface between the AMF network element and the UE, which can be used to deliver non-access stratum (NAS) signaling (such as QoS rules from the AMF network element) to the UE.

[0143] 2) N2: The interface between the AMF network element and the base station, which can be used to transmit radio bearer control information from the core network side to the base station.

[0144] 3) N3: The interface between the base station and the UPF network element, mainly used to transmit uplink and downlink user plane data between the base station and the UPF network element.

[0145] 4) N4: The interface between the SMF network element and the UPF network element, which can be used to transmit information between the control plane and the user plane, including controlling the issuance of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane and reporting information on the user plane.

[0146] 5) N6: The interface between UPF network element and DN, used to transmit uplink and downlink user data flows between UPF network element and DN.

[0147] Figure 1(b) is a schematic diagram of a 5G network architecture based on point-to-point interfaces. The functions of the network elements in Figure 1(a) can be referred to for the functions of the corresponding network elements, and will not be repeated here. The main difference between Figure 1(b) and Figure 1(a) is that the interfaces between the control plane network elements in Figure 1(a) are service-oriented interfaces, while the interfaces between the control plane network elements in Figure 1(b) are point-to-point interfaces.

[0148] In the architecture shown in Figure 1(b), the interface names and functions between the various network elements are as follows:

[0149] 1) For the meanings of the N1, N2, N3, N4 and N6 interfaces, please refer to the above description.

[0150] 2) N5: The interface between the AF network element and the PCF network element, which can be used to issue application service requests and report network events.

[0151] 3) N7: The interface between PCF network element and SMF network element, which can be used to issue PDU session granularity and service data flow granularity control strategy.

[0152] 4) N8: The interface between the AMF network element and the UDM network element, which can be used by the AMF network element to obtain access and mobility management related contract data and authentication data from the UDM network element, and for the AMF to register UE mobility management related information with the UDM.

[0153] 5) N9: User plane interface between UPF network elements, used to transmit uplink and downlink user data flows between UPF network elements.

[0154] 6) N10: The interface between the SMF network element and the UDM network element, which can be used by the SMF network element to obtain session management related contract data from the UDM network element, and the SMF network element to register UE session related information with the UDM.

[0155] 7) N11: The interface between the SMF network element and the AMF network element, which can be used to transmit PDU session tunnel information between the base station and the UPF network element, transmit control messages sent to the UE, transmit radio resource control information sent to the base station, etc.

[0156] 8) N15: The interface between the PCF network element and the AMF network element, which can be used to deliver UE policies and access control related policies.

[0157] 9) N35: The interface between the UDM network element and the UDR network element, which can be used by the UDM network element to obtain user contract data information from the UDR network element.

[0158] 10) N36: Interface between PCF network element and UDR network element, which can be used by PCF network element to obtain policy-related contract data and application data-related information from UDR network element.

[0159] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or function can be implemented by a single device, or by multiple devices, or can be a functional module within a single device, and this is not specifically limited in the embodiments of the present application.

[0160] The session management network element, user plane network element, and application function network element in this application can be the SMF network element, UPF network element, and AF network element in the architecture of Figure 1(a) or Figure 1(b), respectively, or can be a network element having the functions of the above-mentioned SMF network element, UPF network element, and AF network element in a future communication system such as a 6G communication system. This application is not limited to this. In the embodiments of this application, the SMF network element, UPF network element, and AF network element are used as an example for description, and the SMF network element, UPF network element, and AF network element are referred to as SMF, UPF, and AF, respectively. In addition, in the embodiments of this application, the PCF network element and NEF network element are also referred to as PCF and NEF, respectively.

[0161] Existing QoS mechanisms guarantee services at the packet level. Packets within the same service flow are mapped to the same QoS flow for transmission. Packets from different service flows may be mapped to the same QoS flow or to different QoS flows. Different packets within the same QoS flow are individually processed and transmitted based on the same QoS parameters. In other words, all packets within the same QoS flow receive the same, undifferentiated treatment during transmission.

[0162] In the embodiments of the present application, for real-time media services, such as the currently emerging augmented reality (AR), virtual reality (VR), mixed reality (MR), and cloud gaming services, end-to-end latency has extremely stringent requirements, and the corresponding data processing granularity of the upper-layer media services during encoding and transmission may no longer be the granularity of the data packet. For example, when encoding at the media layer, media frames, fragments, etc. can be processed as basic granularities, that is, media frames, fragments, etc. can be independently encoded and processed as basic units at the application layer; at the same time, the receiving side will also perform decoding and display processing at the same granularity of media frames, fragments, etc. In addition, a basic data unit such as a media frame or fragment often contains multiple data packets (the size of each data packet is limited, for example, less than 1500 bytes). In order to represent the basic data unit of the above-mentioned media service layer, the embodiments of the present application are referred to as PDU sets (PDU Sets) or data packet sets. Therefore, a QoS flow will carry one or more PDU sets, each PDU set includes multiple data packets, which can also be called PDU data packets, such as IP data packets or Ethernet data packets. The PDU set is a basic unit that can be independently processed by the upper service layer. Once a data packet in the PDU set is lost or damaged, the entire PDU set may be difficult to decode and display correctly.

[0163] Furthermore, this application proposes a QoS handling mechanism at the PDU set granularity, that is, the loss rate and delay requirements at the PDU set granularity are given as the QoS parameters at the PDU set granularity. The 5G system identifies the relationship between different data packets and PDU sets, clarifies which data packets a PDU set contains, and based on the QoS parameters at the PDU set granularity, schedules, processes and transmits all data packets in the PDU set as a whole to ensure the user's service experience.

[0164] QoS processing at the PDU set granularity includes integrity transmission and differentiated transmission. Integrity transmission means that when the network side schedules transmission, it guarantees transmission at the granularity of the PDU set. If a PDU data packet is lost or damaged, the entire PDU set can be discarded. Differentiated transmission refers to the use of the reference relationship introduced by the encoding between media frames (or fragments) to determine the relative importance of PDU sets. When network congestion occurs, PDU sets with lower importance are discarded based on their importance.

[0165] However, after the introduction of the PDU aggregate granularity QoS processing mechanism, the processing status of the PDU aggregate cannot be perceived and exposed to the outside world, which will lead to incorrect judgment and estimation of network conditions at the application layer. Specifically,

[0166] First, QoS processing at the PDU aggregate granularity level may result in active packet loss due to complete or differentiated transmission. Traditional closed-loop network estimation and control between the application client and application server cannot guarantee that the application layer can perceive the most accurate transmission status.

[0167] Second, the QoS processing at the PDU set granularity is requested by the application side to be executed by the core network, aiming to improve network capacity while ensuring the user's service experience. However, the application side cannot perceive whether the network side has executed the QoS processing at the PDU set granularity and the specific circumstances of the execution, resulting in the application side being unable to decide whether it needs to make corresponding adjustments to the QoS request at the PDU set granularity.

[0168] Third, when the N6 latency between the application side and the UPF cannot be guaranteed, the latency of the PDU set cannot be guaranteed either. However, the application side cannot perceive whether the N6 latency guarantee can be met.

[0169] To solve the above problems, an embodiment of the present application proposes a method for monitoring and reporting PDU set granularity, which avoids blind control of the service layer by monitoring and reporting the PDU set processing status within the network.

[0170] Figure 2 is a flow chart of a communication method provided in an embodiment of the present application. The method is performed by a first network element or a chip for the first network element, and a second network element or a chip for the second network element. The following description uses the first network element and the second network element as an example to illustrate the method. The first network element can be a UE, a base station, a UPF, or an SMF.

[0171] The method comprises the following steps:

[0172] Step 201: A first network element receives first information, where the first information is used to monitor a PDU set carried by a QoS flow and report a monitoring result of the PDU set.

[0173] Among them, the first information is used to monitor the PDU set carried by the QoS flow and report the monitoring results of the PDU set. For example, it can be: the first information is used to trigger the monitoring of the PDU set carried by the QoS flow and report the monitoring results of the PDU set, or to enable the PDU set carried by the QoS flow to monitor and report the monitoring results of the PDU set, or to indicate the monitoring of the PDU set carried by the QoS flow and report the monitoring results of the PDU set.

[0174] Exemplarily, the first information includes a PDU set event, which is used to indicate a monitoring object, or the PDU set event can also be referred to as a monitoring object or a monitoring object corresponding to a PDU set. The monitoring object can be a PDU set loss rate, a PDU set delay, a PDU set extended delay, or the enabled state of a PDU set QoS processing. For example, when the PDU set event is a PDU set loss rate event, it indicates that the PDU set loss rate is monitored; when the PDU set event is a PDU set delay event, it indicates that the PDU set delay is monitored; when the PDU set event is a PDU set extended delay event, it indicates that the PDU set extended delay is monitored; when the PDU set event is an enabled state event of a PDU set QoS processing, it indicates that the enabled state of the PDU set QoS processing is monitored.

[0175] Exemplarily, the first information includes identification information of the QoS flow, and the identification information may be a QoS flow identity (QFI).

[0176] Exemplarily, the first information includes a reporting indication, which is used to indicate reporting the monitoring results of the PDU set to the second network element, or the reporting indication is used to trigger reporting the monitoring results of the PDU set to the second network element, or the reporting indication is used to enable reporting the monitoring results of the PDU set to the second network element.

[0177] Illustratively, the first information also includes a monitoring window, which indicates the monitoring time length, such as 1 hour, 2 hours, or the like, or indicates a monitoring time window, such as 2:00 p.m. to 4:00 p.m. The monitoring window may be from, that is, generated by, the SMF. Alternatively, in another implementation method, the monitoring window may be preconfigured on the first network element.

[0178] Exemplarily, the first information further includes a measurement frequency / reporting frequency, where the measurement frequency / reporting frequency is used to indicate a frequency or time interval for measuring / reporting a PDU set monitoring result.

[0179] It should be understood that monitoring and reporting on the PDU set carried by the QoS flow specifically refers to monitoring and reporting on the transmission status of the PDU set in the QoS flow. The transmission status of the PDU set can be a PDU set event. For example, the transmission status of the PDU set can specifically be the PDU set loss rate, PDU set delay, PDU set extended delay or the enabled status of PDU set QoS processing.

[0180] Step 202: The first network element monitors the PDU set carried by the QoS flow according to the first information.

[0181] Step 203: The first network element sends the monitoring result of the PDU set to the second network element. Correspondingly, the second network element receives the monitoring result of the PDU set.

[0182] Exemplarily, if the above-mentioned first information includes a reporting indication, then step 203 may be: the first network element sends the monitoring result of the PDU set to the second network element according to the reporting indication. Wherein, if the first network element is a UE, the second network element may be a UPF or an SMF, specifically, the UE may carry the monitoring result of the PDU set to the UPF through an uplink data packet or send the monitoring result of the PDU set to the SMF through uplink signaling information. If the first network element is a base station, the second network element may be a UPF or an SMF, specifically, the base station may carry the monitoring result of the PDU set to the UPF through an uplink data packet (such as the monitoring result of the PDU set carried in the GTP-U header of the uplink data packet) or send the monitoring result of the PDU set to the SMF through uplink signaling information. If the first network element is a UPF, the second network element may be an SMF or an NEF, that is, the UPF reports the monitoring result of the PDU set to the SMF, or the UPF opens the monitoring result of the PDU set to the outside world through the NEF. If the first network element is SMF, the second network element may be PCF or NEF, that is, SMF reports the monitoring result of the PDU set to SMF, or SMF opens the monitoring result of the PDU set to the outside world through NEF.

[0183] Exemplarily, if the above-mentioned first information includes a measurement frequency / reporting frequency, the first network element measures / reports the PDU set monitoring result according to the measurement frequency / reporting frequency.

[0184] Exemplarily, if the first information does not include a reporting instruction, step 203 may be: the first network element may send the monitoring result of the PDU set to the second network element according to local configuration.

[0185] As an implementation method, before step 201, the AF sends a subscription request to the PCF. The subscription request includes service flow description information. The service flow corresponding to the service flow description information is carried on the QoS flow. The subscription request is used to subscribe to the monitoring results of the PDU set of the service flow. The PCF then sends the first information to the first network element. Therefore, step 201 is specifically as follows: the first network element receives the first information from the PCF. Correspondingly, after step 203, the second network element also sends the monitoring results of the PDU set to the PCF, and the PCF then sends the monitoring results of the PDU set to the AF. After receiving the monitoring results of the PDU set, the AF can perform corresponding processing based on the monitoring results, such as adjusting the bit rate or forward error correction (FEC) redundancy. For example, if the loss rate of the PDU set is relatively high or the PDU set delay is relatively high, indicating that the current network is poor, the application server will correspondingly reduce the bit rate or increase the FEC redundancy ratio, thereby improving the network condition while ensuring the service experience.

[0186] The above solution monitors and reports QoS flows at the PDU aggregate granularity, enabling monitoring and reporting of the transmission status of PDU aggregate granularity within a QoS flow. Furthermore, this solution can expose the monitoring results to the public through a second network element, allowing the network element receiving the monitoring results to perceive the PDU aggregate granularity transmission status of the QoS flow based on the monitoring results and further control the service. This helps improve the accuracy of service control and avoids blind control of services.

[0187] In the implementation of this application, "exposing to the outside world" means sending certain information (such as the PDU aggregate loss rate, PDU aggregate delay, PDU aggregate extended delay, or the enabled status of PDU aggregate QoS processing) via a certain path (such as a user plane path or a control plane path) to a network element that needs to use the information, such as an application function network element (such as an application server) or a higher layer of the UE. The meaning of "exposing to the outside world" is explained here and will not be repeated later.

[0188] The following describes various specific implementation methods for monitoring the PDU set carried by the QoS flow in the above step 202.

[0189] Implementation method 1, the above step 202 is specifically as follows: the first information includes a PDU aggregate loss rate event, and the PDU aggregate loss rate event indicates that the monitoring object is the PDU aggregate loss rate; the first network element monitors the PDU aggregate loss rate of the QoS flow according to the first information.

[0190] It can be understood that the first information is used to monitor the PDU aggregate loss rate of the QoS flow, so the first network element monitors the PDU aggregate loss rate of the QoS flow according to the first information. The first information is used to monitor the PDU aggregate loss rate of the QoS flow, for example, the first information can be used to indicate that the PDU aggregate loss rate of the QoS flow is to be monitored, or the first information is used to trigger the monitoring of the PDU aggregate loss rate of the QoS flow, or the first information is used to enable the monitoring of the PDU aggregate loss rate of the QoS flow.

[0191] As an implementation method, the first network element is a base station, and the first information is used to monitor the PDU aggregate loss rate in the downlink direction of the QoS flow, wherein the PDU aggregate loss rate includes one or more of the following (1) to (6):

[0192] (1) The percentage of PDUs that the base station fails to send to the UE.

[0193] Exemplarily, the proportion of PDU sets that the base station fails to send to the UE is equal to the ratio of the number of PDU sets that the base station fails to send to the UE to the number of PDU sets that need to be sent to the UE in the QoS flow.

[0194] For example, the proportion of PDU sets that the base station fails to send to the UE is equal to the ratio of the number of PDU sets that the base station fails to send to the UE to the number of PDU sets that need to be sent to the UE in a QoS flow in a certain monitoring window.

[0195] (2) The percentage of PDU sets discarded due to packet loss.

[0196] The PDU set is discarded due to data packet loss, which means that when the base station receives the PDU set from the UPF, if at least one data packet is lost in the received PDU set, or when redundant coding transmission is used in the PDU set, the lost data packets exceed a certain threshold and the base station cannot restore the original data packets. In this case, the base station discards the PDU set, and the discarded PDU set will be included in the statistics.

[0197] Exemplarily, the proportion of PDU sets discarded due to packet loss is equal to the ratio of the number of PDU sets in the QoS flow that failed to be successfully sent to the UE due to packet loss to the total number of PDU sets sent by the base station to the UE.

[0198] For example, the proportion of PDU sets discarded due to packet loss is equal to the ratio of the number of PDU sets that failed to be successfully sent to the UE due to packet loss in a QoS flow over a certain monitoring window to the total number of PDU sets sent by the base station to the UE.

[0199] (3) The percentage of PDU sets discarded due to transmission failure.

[0200] The PDU set is discarded due to transmission failure, which means that the base station sends a PDU set to the UE. Due to the failure of transmission of at least one data packet in the PDU set, the PDU set is discarded, or when redundant coding transmission is used in the PDU set, the number of data packets that fail to be transmitted exceeds a certain threshold, resulting in the UE being unable to restore the original data packets, resulting in the PDU set being discarded. At this time, the discarded PDU set will be included in the statistics.

[0201] Exemplarily, the proportion of PDU sets discarded due to transmission failure is equal to the ratio of the number of PDU sets in the QoS flow that failed to be successfully sent to the UE due to transmission failure to the total number of PDU sets sent by the base station to the UE.

[0202] For example, the proportion of PDU sets discarded due to transmission failure is equal to the ratio of the number of PDU sets that failed to be successfully sent to the UE due to transmission failure in a QoS flow over a certain monitoring window to the total number of PDU sets sent by the base station to the UE.

[0203] (4) The proportion of data packets that failed to be transmitted.

[0204] Exemplarily, the proportion of data packets that fail to be transmitted is equal to the ratio of the number of data packets that fail to be transmitted sent to the UE in the QoS flow to the total number of data packets sent by the base station to the UE.

[0205] Illustratively, the proportion of data packets with transmission failure is equal to the ratio of the number of data packets with transmission failure sent to the UE in the QoS flow over a certain monitoring window to the total number of data packets sent by the base station to the UE.

[0206] (5) The total number of data packets that failed to be transmitted.

[0207] Exemplarily, the total number of data packets that fail to be transmitted is equal to the number of data packets that fail to be transmitted to the UE in the QoS flow.

[0208] Exemplarily, the total number of data packets that fail to be transmitted is equal to the number of data packets that fail to be transmitted to the UE in a QoS flow in a certain monitoring window.

[0209] (6) The proportion of PDU sets discarded due to packet loss based on the importance of the PDU set.

[0210] For example, in the case of network congestion, when the base station sends a PDU set to the UE, in order to reduce the network load or improve the success rate of sending the PDU set, the base station can discard a PDU set with relatively low importance. At this time, the discarded PDU set will be included in the statistics.

[0211] Exemplarily, the proportion of discarded PDU sets due to packet loss based on PDU set importance is equal to the ratio of the number of PDU sets discarded due to different PDU set importances to the total number of PDU sets sent by the base station to the UE.

[0212] Exemplarily, the proportion of PDU sets discarded due to packet loss based on PDU set importance is equal to the ratio of the number of PDU sets discarded due to different PDU set importances in a certain monitoring window to the total number of PDU sets sent by the base station to the UE.

[0213] It should be noted that the PDU set loss rate can be calculated for each PDU set importance by calculating one or more of the above (1) to (6), or it can be calculated for all PDU set importances by uniformly calculating one or more of the above (1) to (6).

[0214] As another implementation method, the first network element is a UE, and the first information is used to monitor the PDU set loss rate in the uplink direction of the QoS flow, wherein the PDU set loss rate includes one or more of the following (1) to (5):

[0215] (1) The percentage of PDUs that the UE fails to send to the base station.

[0216] Exemplarily, the proportion of PDU sets that the UE fails to send to the base station is equal to the ratio of the number of PDU sets that the UE fails to send to the base station to the number of PDU sets that need to be sent to the base station in the QoS flow.

[0217] For example, the proportion of PDU sets that the UE fails to send to the base station is equal to the ratio of the number of PDU sets that the UE fails to send to the base station to the number of PDU sets that need to be sent to the base station in a QoS flow in a certain monitoring window.

[0218] (2) The percentage of PDU sets discarded due to transmission failure.

[0219] The PDU set is discarded due to transmission failure, which means that the UE sends a PDU set to the base station. The PDU set is discarded due to the failure of transmission of at least one data packet in the PDU set, or when redundant coding transmission is used in the PDU set, the number of data packets that fail to be transmitted exceeds a certain threshold, resulting in the base station being unable to restore the original data packets, resulting in the PDU set being discarded. At this time, the discarded PDU set will be included in the statistics.

[0220] For example, the proportion of PDU sets discarded due to transmission failure is equal to the ratio of the number of PDU sets in the QoS flow that failed to be successfully sent to the base station due to transmission failure to the total number of PDU sets sent by the UE to the base station.

[0221] For example, the proportion of PDU sets discarded due to transmission failure is equal to the ratio of the number of PDU sets that failed to be successfully sent to the base station due to transmission failure in a QoS flow on a certain monitoring window to the total number of PDU sets sent by the UE to the base station.

[0222] (3) The proportion of data packets that failed to be transmitted.

[0223] Exemplarily, the proportion of data packets that fail to be transmitted is equal to the ratio of the number of data packets that fail to be transmitted sent to the base station in the QoS flow to the total number of data packets sent by the UE to the base station.

[0224] Illustratively, the proportion of data packets with failed transmission is equal to the ratio of the number of data packets with failed transmission sent to the base station in the QoS flow over a certain monitoring window to the total number of data packets sent from the UE to the base station.

[0225] (4) The total number of data packets that failed to be transmitted.

[0226] Exemplarily, the total number of data packets that fail to be transmitted is equal to the number of data packets that fail to be transmitted to the base station in the QoS flow.

[0227] Exemplarily, the total number of data packets that fail to be transmitted is equal to the number of data packets that fail to be transmitted to the base station in a QoS flow in a certain monitoring window.

[0228] (5) The proportion of PDU sets discarded due to packet loss based on the importance of the PDU set.

[0229] For example, in the case of network congestion, when the UE sends a PDU set to the base station, in order to reduce the network load or improve the success rate of sending the PDU set, the UE can discard a PDU set with relatively low importance. At this time, the discarded PDU set will be included in the statistics.

[0230] Exemplarily, the proportion of discarded PDU sets due to packet loss based on PDU set importance is equal to the ratio of the number of PDU sets discarded due to different PDU set importances to the total number of PDU sets sent by the UE to the base station.

[0231] Exemplarily, the proportion of PDU sets discarded due to packet loss based on PDU set importance is equal to the ratio of the number of PDU sets discarded due to different PDU set importances in a certain monitoring window to the total number of PDU sets sent by the UE to the base station.

[0232] It should be noted that the PDU set loss rate can be calculated for each PDU set importance by calculating one or more of the above (1) to (5), or it can be calculated for all PDU set importances by uniformly calculating one or more of the above (1) to (5).

[0233] Based on the first implementation method, the monitoring result reported in the above step 203 includes the PDU aggregate loss rate.

[0234] For specific examples of the first implementation method, please refer to the embodiments of Figures 3 and 4 below.

[0235] Implementation method 2, the above step 202 is specifically as follows: the first information includes a PDU aggregate delay event, and the PDU aggregate delay event indicates that the monitoring object is the PDU aggregate delay; the first network element monitors the PDU aggregate delay of the QoS flow according to the first information.

[0236] It can be understood that the first information is used to monitor the PDU aggregate delay of the QoS flow, so the first network element monitors the PDU aggregate delay of the QoS flow according to the first information. The first information is used to monitor the PDU aggregate delay of the QoS flow, for example, it can be: the first information is used to indicate the monitoring of the PDU aggregate delay of the QoS flow, or the first information is used to trigger the monitoring of the PDU aggregate delay of the QoS flow, or the first information is used to enable the monitoring of the PDU aggregate delay of the QoS flow.

[0237] As an implementation method, the first network element is a base station, and the first information is used to monitor the PDU aggregate delay in the downlink direction of the QoS flow, wherein the PDU aggregate delay includes one or more of the following (1) to (3):

[0238] (1) The time taken by the base station to successfully transmit the PDU set to the UE.

[0239] Exemplarily, the time taken by the base station to successfully transmit the PDU set to the UE specifically includes: the time taken by the base station to successfully transmit the PDU set to the UE, which may be the average, maximum, minimum or median of the time taken by each PDU set in at least two PDU sets to be transmitted to the UE; it may also be the average, maximum, minimum or median of the time taken by the base station to successfully transmit at least two PDU sets to the UE within the monitoring window, or include the time taken for each PDU set to be successfully transmitted to the UE.

[0240] It should be noted that the time taken by the base station to successfully transmit the PDU set to the UE may refer to the time taken by the base station to receive the first data packet of the PDU set and successfully transmit the last data packet of the PDU set to the UE, or it may refer to the time taken by the base station to receive the first data packet of the PDU set and successfully transmit all data packets in the PDU set to the UE.

[0241] (2) The time taken by the base station to successfully transmit the PDU set to the UE within the PDU set delay budget.

[0242] Exemplarily, the time taken by the base station to successfully transmit the PDU set to the UE within the PDU set delay budget time specifically includes: the average, maximum, minimum or median of the time taken by the base station to successfully transmit at least two PDU sets to the UE, or includes the time taken by each PDU set to be successfully transmitted to the UE. The time taken by each PDU set successfully transmitted to the UE is less than or equal to the PDU set delay budget time. For example, if the PDU set delay budget time is equal to 10 milliseconds (ms), the base station counts the average, minimum, maximum or median of the time taken by at least two PDU sets successfully transmitted to the UE within 10ms, or counts the time taken by the PDU set successfully transmitted to the UE within 10ms. It can be the average, maximum, minimum or median of the time taken by the base station to successfully transmit at least two PDU sets to the UE within a period of time (i.e., within the monitoring window), or includes the time taken by each PDU set to be successfully transmitted to the UE, and the time taken by each PDU set successfully transmitted to the UE here is less than or equal to the PDU set delay budget time.

[0243] (3) The time taken by the base station to successfully transmit the PDU aggregate to the UE beyond the PDU aggregate delay budget.

[0244] Exemplarily, the time taken by the base station to successfully transmit the PDU set to the UE beyond the PDU set delay budget time may be: the average, maximum, minimum or median of the time taken by the base station to successfully transmit at least two PDU sets to the UE; or the time taken by each PDU set to be successfully transmitted to the UE, where the time taken by each PDU set successfully transmitted to the UE is greater than the PDU set delay budget time. For example, if the PDU set delay budget time is equal to 10ms, then the base station counts the average, maximum, minimum or median of the time taken by at least two PDU sets to be successfully transmitted to the UE exceeding 10ms, or counts the time taken by the PDU set to be successfully transmitted to the UE exceeding 10ms. Optionally, it may be the average, maximum, minimum or median of the time taken by the base station to successfully transmit at least two PDU sets to the UE within a period of time (i.e., within the monitoring window), or includes the time taken by each PDU set to be successfully transmitted to the UE, and the time taken by each PDU set to be successfully transmitted to the UE is greater than the PDU set delay budget time.

[0245] Exemplarily, the PDU aggregate delay also includes the proportion or number of PDU aggregates successfully transmitted by the base station to the UE within the PDU aggregate delay budget time.

[0246] Exemplarily, the PDU aggregate delay also includes the proportion or number of PDU aggregates that the base station successfully transmits to the UE beyond the PDU aggregate delay budget time.

[0247] It should be noted that the PDU aggregate delay may be calculated for each PDU aggregate importance by calculating one or more of the above (1) to (3), or may be calculated for all PDU aggregate importances by uniformly calculating one or more of the above (1) to (3).

[0248] As another implementation method, the first network element is a UE, and the first information is used to monitor the PDU aggregate delay in the uplink direction of the QoS flow, wherein the PDU aggregate delay includes one or more of the following (1) to (3):

[0249] (1) The time it takes for the UE to successfully transmit the PDU set to the base station.

[0250] Exemplarily, the time taken by the UE to successfully transmit the PDU set to the base station specifically includes: the time taken by the UE to successfully transmit each PDU set to the base station, which can be the average, maximum, minimum or median of the time taken by each PDU set in at least two PDU sets to be transmitted to the UE; it can also be the average, maximum, minimum or median of the time taken by the UE to successfully transmit at least two PDU sets to the base station within the monitoring window, or include the time taken for each PDU set to be successfully transmitted to the base station.

[0251] It should be noted that the time taken by the UE to successfully transmit the PDU set to the base station may refer to the time taken by the UE's bottom layer (such as the modulation layer) to receive the first data packet of the PDU set from the UE's upper layer (such as the application layer) to successfully transmit the last data packet of the PDU set to the base station, or it may refer to the time taken by the UE's bottom layer (such as the modulation layer) to receive the first data packet of the PDU set from the UE's upper layer (such as the application layer) to successfully transmit all data packets in the PDU set to the base station.

[0252] (2) The time taken by the UE to successfully transmit the PDU set to the base station within the PDU set delay budget.

[0253] Exemplarily, the time taken by the UE to successfully transmit the PDU set to the base station within the PDU set delay budget time specifically includes: the average, maximum, minimum or median of the time taken by the UE to successfully transmit at least two PDU sets to the base station, or includes the time taken by each PDU set to be successfully transmitted to the base station, and the time taken by each PDU set successfully transmitted to the UE here is less than or equal to the PDU set delay budget time. For example, if the PDU set delay budget time is equal to 10ms, the UE counts the average, minimum, maximum or median of the time taken by at least two PDU sets to be successfully transmitted to the base station within 10ms, or counts the time taken by the PDU set to be successfully transmitted to the base station within 10ms. Specifically, it can be the average, maximum, minimum or median of the time taken by the UE to successfully transmit at least two PDU sets to the base station within a period of time (i.e., within the monitoring window), or includes the time taken by each PDU set to be successfully transmitted to the base station, and the time taken by each PDU set to be successfully transmitted to the base station here is less than or equal to the PDU set delay budget time.

[0254] (3) The time taken by the UE to successfully transmit the PDU aggregate to the base station beyond the PDU aggregate delay budget.

[0255] Exemplarily, the time taken by the UE to successfully transmit the PDU set to the base station beyond the PDU set delay budget time specifically includes: the average, maximum or minimum value of the time taken by the UE to successfully transmit at least two PDU sets to the base station, or includes the time taken by each PDU set to be successfully transmitted to the base station, and the time taken by each PDU set successfully transmitted to the base station here is greater than the PDU set delay budget time. For example, if the PDU set delay budget time is equal to 10ms, then the UE counts the average, minimum or maximum value of the time taken by at least two PDU sets to be successfully transmitted to the base station exceeding 10ms, or counts the time taken by the PDU set to be successfully transmitted to the base station exceeding 10ms. Optionally, it can be the average, maximum, minimum or median value of the time taken by the UE to successfully transmit at least two PDU sets to the base station within a period of time (i.e., within the monitoring window), or includes the time taken by each PDU set to be successfully transmitted to the base station, and the time taken by each PDU set to be successfully transmitted to the base station here is greater than the PDU set delay budget time.

[0256] Exemplarily, the PDU aggregate delay also includes the proportion or number of PDU aggregates successfully transmitted by the UE to the base station within the PDU aggregate delay budget time.

[0257] Exemplarily, the PDU aggregate delay also includes the proportion or number of PDU aggregates that the UE successfully transmits to the base station beyond the PDU aggregate delay budget time.

[0258] It should be noted that the PDU aggregate delay may be calculated for each PDU aggregate importance by calculating one or more of the above (1) to (3), or may be calculated for all PDU aggregate importances by uniformly calculating one or more of the above (1) to (3).

[0259] Based on this second implementation method, the monitoring results reported in step 203 above include the PDU aggregate delay, or the sum of the PDU aggregate delay and the N3-segment CN PDB, which additionally includes the N3-segment delay. The N3-segment CN-PDB is the delay required to transmit a data packet or PDU aggregate between the base station and the UPF. If the N3-segment delay is the N3-segment CN-PDB, it can be considered a static delay. Alternatively, the existing N3 delay measurement mechanism can be reused to obtain a dynamic N3-segment delay.

[0260] For specific examples of the second implementation method, please refer to the embodiments of Figures 6 and 7 below.

[0261] In implementation method three, step 202 is specifically as follows: the first information includes a PDU aggregate extended delay event, the PDU aggregate extended delay event indicating that the monitoring target is the PDU aggregate extended delay; and the first network element monitors the PDU aggregate extended delay of the QoS flow based on the first information. The first network element is a UPF.

[0262] It can be understood that the first information is used to monitor the PDU set extended delay of the QoS flow, so the first network element monitors the PDU set extended delay of the QoS flow according to the first information. The first information is used to monitor the PDU set extended delay of the QoS flow, for example, it can be: the first information is used to indicate the monitoring of the PDU set extended delay of the QoS flow, or the first information is used to trigger the monitoring of the PDU set extended delay of the QoS flow, or the first information is used to enable the monitoring of the PDU set extended delay of the QoS flow.

[0263] As an implementation method, the PDU aggregate extended delay includes one or more of the following (1) to (4):

[0264] (1) The time interval between the first packet of a PDU set arriving at the UPF and the last packet arriving at the UPF.

[0265] That is, for the downlink direction, the time interval between the UPF receiving the first packet of a PDU set and the last packet of the PDU set reflects the latency of the N6 link. For example, if the first packet of a PDU set arrives at the UPF at T1 and the last packet of the PDU set arrives at the UPF at T2, the PDU set extended latency can be T2-T1.

[0266] (2) The time interval between the first packet of the PDU set arriving at the user plane network element and the last packet leaving the user plane network element.

[0267] That is, for the downlink direction, the time interval between the UPF receiving the first packet of a PDU set and the last packet of the PDU set arriving at the UPF and leaving the UPF reflects the latency of the N6 link. For example, if the first packet of a PDU set arrives at the UPF at T1, and the last packet of the PDU set arrives at the UPF and is then sent from the UPF (for example, to the base station) at T2, the PDU set extended latency can include T2-T1.

[0268] (3) The time interval between the first packet of the PDU set leaving the user plane network element and the last packet leaving the user plane network element.

[0269] That is, for the downlink direction, the time interval between the first packet of a PDU set arriving at the UPF and leaving the UPF and the last packet of the PDU set arriving at the UPF and leaving the UPF reflects the latency of the N6 link. For example, if the first packet of a PDU set arrives at the UPF and is sent from the UPF (for example, to a base station) at time T1, and the last packet of the PDU set arrives at the UPF and is sent from the UPF (for example, to a base station) at time T2, then the PDU set extended latency may include T2-T1.

[0270] (4) The proportion of the target PDU set, where the time interval between the first packet of the target PDU set arriving at the UPF and the last packet arriving at the UPF does not exceed a preset threshold, which comes from the AF, PCF or SMF, or is locally configured by the UPF.

[0271] That is, if the time interval between when the UPF receives the first packet of a PDU set and when it receives the last packet of the PDU set is less than or equal to the preset threshold, then the PDU set is called the target PDU set, and the UPF counts the proportion of the target PDU set in all PDU sets.

[0272] In another implementation method, it can also be defined that the time interval between the first packet of the target PDU set arriving at the UPF and the last packet arriving at the UPF is greater than a preset threshold. That is, if the time interval between the UPF receiving the first packet of a PDU set and receiving the last packet of the PDU set is greater than the preset threshold, then the PDU set is called the target PDU set, and the UPF counts the proportion of the target PDU set in all PDU sets.

[0273] Alternatively, it is also possible to define that the time interval between the first packet of the target PDU set arriving at the UPF and the last packet leaving the UPF does not exceed a preset threshold, or it is also possible to define that the time interval between the first packet of the target PDU set arriving at the UPF and the last packet leaving the UPF is greater than a preset threshold, or it is also possible to define that the time interval between the first packet of the target PDU set leaving the user plane network element and the last packet leaving the user plane network element does not exceed a preset threshold, or it is also possible to define that the time interval between the first packet of the target PDU set leaving the user plane network element and the last packet leaving the user plane network element is greater than a preset threshold.

[0274] It should be noted that the PDU set extended delay can be calculated for each PDU set importance by calculating one or more of the above (1) to (4), or it can be calculated uniformly for all PDU set importances by calculating one or more of the above (1) to (4).

[0275] Based on the third implementation method, the monitoring result reported in the above step 203 includes the PDU aggregate extended delay.

[0276] For a specific example of the third implementation method, please refer to the embodiment of FIG9 below.

[0277] In the fourth implementation method, step 202 is specifically as follows: the first information includes an event indicating an enabled state of the PDU aggregate QoS processing, wherein the event indicates that the monitored object is the enabled state of the PDU aggregate QoS processing; and the first network element monitors the enabled state of the PDU aggregate QoS processing of the QoS flow based on the first information. The first network element is an SMF.

[0278] It can be understood that the first information is used to monitor the enabled state of the PDU set QoS processing of the QoS flow, so the first network element monitors the enabled state of the PDU set QoS processing of the QoS flow according to the first information. The first information is used to monitor the enabled state of the PDU set QoS processing of the QoS flow, for example, it can be: the first information is used to indicate the monitoring of the enabled state of the PDU set QoS processing of the QoS flow, or the first information is used to trigger the monitoring of the enabled state of the PDU set QoS processing of the QoS flow, or the first information is used to enable the monitoring of the enabled state of the PDU set QoS processing of the QoS flow.

[0279] As an implementation method, the SMF receives a capability indication from the base station, where the capability indication is used to indicate that the base station has the capability of PDU aggregate QoS processing. Then, the SMF determines the activation state of the PDU aggregate QoS processing of the QoS flow based on the capability indication. For example, the SMF sends the PDU aggregate QoS parameters to the base station based on the capability indication. After sending the PDU aggregate QoS parameters, it is determined that the PDU aggregate QoS processing of the QoS flow has been activated, that is, the activation state of the PDU aggregate QoS processing of the QoS flow is on.

[0280] As another implementation method, the SMF sends the QoS parameters of the PDU set to the base station. If the SMF then receives a capability indication from the base station, which is used to indicate that the base station has the PDU set QoS processing capability, the SMF determines that the PDU set QoS processing of the QoS flow has been enabled, that is, the enabling state of the PDU set QoS processing of the QoS flow is on.

[0281] As another implementation method, the SMF sends the QoS parameters of the PDU set to the base station. If the SMF then receives an indication message from the base station, which is used to indicate that the base station has received the QoS parameters of the PDU set, the SMF considers that the base station has the PDU set QoS processing capability and determines that the PDU set QoS processing of the QoS flow has been enabled, that is, the enabling state of the PDU set QoS processing of the QoS flow is on.

[0282] Based on the fourth implementation method, the monitoring result reported in the above step 203 includes the activation status of the PDU aggregate QoS processing.

[0283] For a specific example of the fourth implementation method, please refer to the embodiment of FIG10 below.

[0284] The embodiment of FIG. 2 will be described below in conjunction with the specific embodiments of FIG. 3 to FIG. 10 .

[0285] Figure 3 is a flow chart of a communication method provided in an embodiment of the present application. This embodiment is directed to monitoring and exposing the PDU aggregate loss rate in the downlink direction. Exemplarily, the base station monitors the PDU aggregate loss rate and exposes the monitoring results to the outside via the user plane or control plane. The embodiment of Figure 3 is a specific example of implementation method 1 in the embodiment of Figure 2 above, and the base station is a specific example of the first network element in the embodiment of Figure 2.

[0286] The method comprises the following steps:

[0287] Step 301: The AF sends a subscription request to the PCF. Correspondingly, the PCF receives the subscription request.

[0288] The subscription request includes service flow description information, a PDU Set Loss Rate Event, a monitoring trigger condition, and / or a reporting trigger condition. The subscription request is used to request the PCF to subscribe to the PDU Set Loss Rate.

[0289] The service flow description information is used to indicate the service flow to be monitored. The service flow description information may be information such as an IP triplet or a quintuple of the service flow.

[0290] The monitoring trigger condition is used to indicate the conditions for triggering the monitoring of the PDU set loss rate. Exemplarily, the monitoring trigger condition is used to indicate periodic triggering of monitoring, or to indicate event triggering of monitoring. When the monitoring trigger condition is used to indicate periodic triggering of monitoring, the monitoring trigger condition may include the monitoring period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event-triggered monitoring may be, for example, when the number of PDU set losses is greater than a preset threshold, or the number of PDU data packets lost is greater than a preset threshold, or the network congestion level exceeds a preset threshold, and so on.

[0291] The reporting trigger condition is used to indicate the conditions for triggering the reporting of the PDU set loss rate. Exemplarily, the reporting trigger condition is used to indicate periodic trigger reporting, or to indicate event trigger reporting. When the reporting trigger condition is used to indicate periodic trigger reporting, the reporting trigger condition may include the reporting period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event trigger monitoring may be, for example, when the number of PDU set losses is greater than a preset threshold, or the number of PDU data packets lost is greater than a preset threshold, or the network congestion level exceeds a preset threshold, or the PDU set loss rate is greater than a preset threshold, and so on.

[0292] It should be noted that the monitoring trigger condition and the reporting trigger condition may be the same or different. When they are the same, the monitoring trigger condition and the reporting trigger condition may be collectively referred to as trigger conditions.

[0293] Optionally, the subscription request further includes a monitoring window, which is used to indicate the length of monitoring time, such as 1 hour, 2 hours, etc.

[0294] Optionally, the subscription request also includes a reporting instruction, which is used to instruct the UPF to send the monitoring results, which can be understood as the reporting instruction for instructing the user to open the monitoring results to the outside. Alternatively, the reporting instruction is used to instruct the SMF to send the monitoring results, which can be understood as the reporting instruction for instructing the control surface to open the monitoring results to the outside.

[0295] As an implementation method, the AF can be a third-party application server or an application server within the 5G core network. If the AF is in a trusted domain, the AF can interact directly with the PCF, that is, by calling the PCF service interface, such as the Npcf_PolicyAuthorization service interface or the Npcf_EventExposure service interface, to send a subscription request to the PCF. If the AF is in a non-trusted domain, the AF needs to interact with the PCF through the NEF. The AF calls the NEF service interface, such as the Nnef_AFSessionWithQoS service interface or the Nnef_EventExposure service interface, to send a subscription request to the PCF. Then, the NEF calls the PCF service interface in response to send a subscription request to the PCF, so that the PCF receives the subscription request.

[0296] Among them, regarding the definition of the PDU aggregate loss rate, reference can be made to the description of the implementation method 1 in the embodiment of Figure 2 above, and no further details will be given.

[0297] Step 302: The PCF generates PCC rules.

[0298] Exemplarily, the PCF generates a PCC rule based on the subscription request and / or local policy. The PCC rule includes service flow description information, a PDU aggregate loss rate event, a monitoring trigger condition, and / or a reporting trigger condition. Optionally, the PCC rule also includes at least one of a monitoring window and a reporting indication.

[0299] Step 303: The PCF sends the PCC rules to the SMF. Correspondingly, the SMF receives the PCC rules.

[0300] In one implementation method, if the UE initiates the PDU session establishment or modification process, the SMF actively initiates the session management policy association establishment or modification process and obtains the PCC rule from the PCF.

[0301] In another implementation method, if the session management policy association modification process is initiated by the PCF, the PCF actively sends the PCC rule to the SMF.

[0302] Step 304: The SMF generates monitoring parameters.

[0303] Exemplarily, the SMF generates monitoring parameters according to PCC rules and / or local policies.

[0304] The monitoring parameters include QFI, PDU aggregate loss rate event, monitoring trigger condition and / or reporting trigger condition. Optionally, the monitoring parameters also include at least one of a monitoring window or a reporting indication.

[0305] The QFI is used to indicate the QoS flow corresponding to the service flow description information.

[0306] Step 305: The SMF sends monitoring parameters to the base station. Correspondingly, the base station receives the monitoring parameters.

[0307] After step 305, the remaining PDU session establishment or modification process will be completed. For details, please refer to Section 4.3.2.1 of TS23.502.

[0308] Among them, SMF sends monitoring parameters to the base station, specifically SMF sends monitoring parameters to the base station through AMF.

[0309] Step 306: The base station determines the PDU aggregate loss rate based on the monitoring parameters.

[0310] Exemplarily, the base station monitors the PDU aggregate loss rate of the downlink PDU aggregate according to the PDU aggregate loss rate event in the monitoring parameters and the monitoring trigger condition.

[0311] Step 307: The base station sends the PDU aggregate loss rate.

[0312] In one implementation method, if the reporting indication is used to indicate (or trigger, or enable) sending the monitoring results to the UPF, then step 307 is specifically: the base station adds the PDU aggregate loss rate to the general wireless packet service (GPRS) tunneling protocol user plane (GTP-U) layer of the uplink data packet and reports it to the UPF, and then the UPF sends the PDU aggregate loss rate to the AF, or the UPF sends the PDU aggregate loss rate to the AF through the NEF.

[0313] In another implementation method, if the reporting indication is used to indicate (or trigger, or enable) sending the monitoring results to the SMF, then step 307 is specifically: the base station sends the PDU aggregate loss rate to the SMF, and then the SMF sends the PDU aggregate loss rate to the PCF, the PCF sends the PDU aggregate loss rate to the AF, or the PCF sends the PDU aggregate loss rate to the AF through the NEF.

[0314] Optionally, after the AF receives the PDU aggregate loss rate, the application layer of the AF may perform corresponding processing according to the PDU aggregate loss rate, such as adjusting the bit rate or adjusting the FEC redundancy.

[0315] In the above solution, the AF requests the core network to obtain the PDU aggregate loss rate. The base station monitors the PDU aggregate loss rate of the downlink PDU aggregate and opens the PDU aggregate loss rate to the outside world, that is, to the AF. The AF can then perform corresponding processing based on the PDU aggregate loss rate, avoiding blind control at the service layer and improving the service experience.

[0316] Figure 4 is a flow chart of a communication method provided in an embodiment of the present application. This embodiment is directed to monitoring and exposing the uplink PDU aggregate loss rate. Exemplarily, the UE monitors the PDU aggregate loss rate and exposes the monitoring results to the outside world via the user plane or control plane. The embodiment of Figure 4 is a specific example of implementation method 1 in the embodiment of Figure 2 above, and the UE is a specific example of the first network element in the embodiment of Figure 2.

[0317] The method comprises the following steps:

[0318] Step 401: The AF sends a subscription request to the PCF. Correspondingly, the PCF receives the subscription request.

[0319] The subscription request includes service flow description information, PDU aggregate loss rate event, monitoring trigger condition and / or reporting trigger condition. The subscription request is used to request the PCF to subscribe to the PDU aggregate loss rate.

[0320] The service flow description information is used to indicate the service flow to be monitored. The service flow description information may be information such as an IP triplet or a quintuple of the service flow.

[0321] The monitoring trigger condition is used to indicate the conditions for triggering the monitoring of the PDU set loss rate. Exemplarily, the monitoring trigger condition is used to indicate periodic triggering of monitoring, or to indicate event triggering of monitoring. When the monitoring trigger condition is used to indicate periodic triggering of monitoring, the monitoring trigger condition may include the monitoring period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event-triggered monitoring may be, for example, when the number of PDU set losses is greater than a preset threshold, or the number of PDU data packets lost is greater than a preset threshold, or the network congestion level exceeds a preset threshold, and so on.

[0322] The reporting trigger condition is used to indicate the conditions for triggering the reporting of the PDU set loss rate. Exemplarily, the reporting trigger condition is used to indicate periodic trigger reporting, or to indicate event trigger reporting. When the reporting trigger condition is used to indicate periodic trigger reporting, the reporting trigger condition may include the reporting period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event trigger monitoring may be, for example, when the number of PDU set losses is greater than a preset threshold, or the number of PDU data packets lost is greater than a preset threshold, or the network congestion level exceeds a preset threshold, or the PDU set loss rate is greater than a preset threshold, and so on.

[0323] It should be noted that the monitoring trigger condition and the reporting trigger condition may be the same or different. When they are the same, the monitoring trigger condition and the reporting trigger condition may be collectively referred to as trigger conditions.

[0324] Optionally, the subscription request further includes a monitoring window, which is used to indicate the length of monitoring time, such as 1 hour, 2 hours, etc.

[0325] Optionally, the subscription request also includes a reporting indication, which is used to instruct (or trigger, or cause) the monitoring results to be sent to the UPF, which can be understood as the reporting indication being used to instruct (or trigger, or cause) the monitoring results to be exposed to the outside through the user surface. Alternatively, the reporting indication is used to instruct (or trigger, or cause) the monitoring results to be sent to the SMF, which can be understood as the reporting indication being used to instruct (or trigger, or cause) the monitoring results to be exposed to the outside through the control surface.

[0326] As an implementation method, the AF can be a third-party application server or an application server within the 5G core network. If the AF is in a trusted domain, the AF can interact directly with the PCF, that is, by calling the PCF service interface, such as the Npcf_PolicyAuthorization service interface or the Npcf_EventExposure service interface, to send a subscription request to the PCF. If the AF is in a non-trusted domain, the AF needs to interact with the PCF through the NEF. The AF calls the NEF service interface, such as the Nnef_AFSessionWithQoS service interface or the Nnef_EventExposure service interface, to send a subscription request to the PCF. Then, the NEF calls the PCF service interface in response to send a subscription request to the PCF, so that the PCF receives the subscription request.

[0327] Among them, regarding the definition of the PDU aggregate loss rate, reference can be made to the description of the implementation method 1 in the embodiment of Figure 2 above, and no further details will be given.

[0328] Step 402: The PCF generates PCC rules.

[0329] Exemplarily, the PCF generates a PCC rule based on the subscription request and / or local policy. The PCC rule includes service flow description information, a PDU aggregate loss rate event, a monitoring trigger condition, and / or a reporting trigger condition. Optionally, the PCC rule also includes at least one of a monitoring window and a reporting indication.

[0330] Step 403: The PCF sends the PCC rules to the SMF. Correspondingly, the SMF receives the PCC rules.

[0331] In one implementation method, if the UE initiates the PDU session establishment or modification process, the SMF actively initiates the session management policy association establishment or modification process and obtains the PCC rule from the PCF.

[0332] In another implementation method, if the session management policy association modification process is initiated by the PCF, the PCF actively sends the PCC rule to the SMF.

[0333] Step 404: The SMF generates monitoring parameters.

[0334] Exemplarily, the SMF generates monitoring parameters according to PCC rules and / or local policies from the PCF.

[0335] The monitoring parameters include QFI, PDU aggregate loss rate event, monitoring trigger condition and / or reporting trigger condition. Optionally, the monitoring parameters also include at least one of a monitoring window and a reporting indication.

[0336] The QFI is used to indicate the QoS flow corresponding to the service flow description information.

[0337] Step 405: The SMF sends monitoring parameters to the UE. Correspondingly, the UE receives the monitoring parameters.

[0338] After step 405, the remaining PDU session establishment or modification process will be completed. For details, please refer to Section 4.3.2.1 of TS23.502.

[0339] Among them, SMF sends monitoring parameters to UE, specifically SMF sends monitoring parameters to UE through AMF and base station.

[0340] Step 406: The UE determines the PDU aggregate loss rate based on the monitoring parameters.

[0341] The UE monitors the PDU aggregate loss rate of the uplink PDU aggregate according to the PDU aggregate loss rate event in the monitoring parameters and the monitoring trigger condition.

[0342] Step 407: The UE sends the PDU aggregate loss rate.

[0343] In one implementation method, if the reporting indication is used to indicate (or trigger, or enable) sending the monitoring results to the UPF, then step 407 is specifically: the UE adds the PDU aggregate loss rate to the PDCP layer header of the uplink data packet and sends it to the base station, and then the base station adds the PDU aggregate loss rate to the GTP-U layer of the uplink data packet and reports it to the UPF, and then the UPF sends the PDU aggregate loss rate to the AF, or the UPF sends the PDU aggregate loss rate to the AF through the NEF.

[0344] In another implementation method, if the reporting indication is used to indicate (or trigger, or enable) sending the monitoring results to the SMF, then step 407 is specifically: the UE sends the PDU aggregate loss rate to the SMF, and then the SMF sends the PDU aggregate loss rate to the PCF, the PCF sends the PDU aggregate loss rate to the AF, or the PCF sends the PDU aggregate loss rate to the AF through the NEF.

[0345] Optionally, after the AF receives the PDU aggregate loss rate, the application layer of the AF may perform corresponding processing according to the PDU aggregate loss rate, such as adjusting the bit rate or adjusting the FEC redundancy.

[0346] In the above solution, the AF requests the core network to obtain the PDU aggregate loss rate. The UE monitors the PDU aggregate loss rate of the uplink PDU aggregate and opens the PDU aggregate loss rate to the outside world, that is, to the AF. The application layer of the AF can perform corresponding processing based on the PDU aggregate loss rate, avoiding blind control of the service layer and improving the service experience.

[0347] Figure 5 is a flow chart of a communication method provided in an embodiment of the present application. This embodiment monitors and exposes the uplink PDU aggregate loss rate. For example, the UE's modulation layer (modem) monitors the PDU aggregate delay and exposes the monitoring results to the UE's application layer. The UE's modulation layer is primarily responsible for wireless reception and transmission and related functions.

[0348] The method comprises the following steps:

[0349] Step 501: The application layer of the UE sends a subscription request to the modulation layer of the UE. Correspondingly, the modulation layer of the UE receives the subscription request.

[0350] The subscription request includes service flow description information, PDU aggregate loss rate event, monitoring trigger condition and / or reporting trigger condition. The subscription request is used to request the PCF to subscribe to the PDU aggregate loss rate.

[0351] The service flow description information is used to indicate the service flow to be monitored. The service flow description information may be information such as an IP triplet or a quintuple of the service flow.

[0352] The monitoring trigger condition is used to indicate the conditions for triggering the monitoring of the PDU set loss rate. Exemplarily, the monitoring trigger condition is used to indicate periodic triggering of monitoring, or to indicate event triggering of monitoring. When the monitoring trigger condition is used to indicate periodic triggering of monitoring, the monitoring trigger condition may include the monitoring period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event-triggered monitoring may be, for example, when the number of PDU set losses is greater than a preset threshold, or the number of PDU data packets lost is greater than a preset threshold, or the network congestion level exceeds a preset threshold, and so on.

[0353] The reporting trigger condition is used to indicate the conditions for triggering the reporting of the PDU set loss rate. Exemplarily, the reporting trigger condition is used to indicate periodic trigger reporting, or to indicate event trigger reporting. When the reporting trigger condition is used to indicate periodic trigger reporting, the reporting trigger condition may include the reporting period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event trigger monitoring may be, for example, when the number of PDU set losses is greater than a preset threshold, or the number of PDU data packets lost is greater than a preset threshold, or the network congestion level exceeds a preset threshold, or the PDU set loss rate is greater than a preset threshold, and so on.

[0354] It should be noted that the monitoring trigger condition and the reporting trigger condition may be the same or different. When they are the same, the monitoring trigger condition and the reporting trigger condition may be collectively referred to as trigger conditions.

[0355] Optionally, the subscription request further includes a monitoring window, which is used to indicate the length of monitoring time, such as 1 hour, 2 hours, etc.

[0356] Optionally, the subscription request also includes a reporting indication, which is used to indicate (or trigger, or enable) reporting of monitoring results through the interactive interface between the UE's modulation layer and the UE's application layer, that is, the UE's modulation layer sends the monitoring results to the UE's application layer.

[0357] The specific meaning of the PDU aggregate loss rate is the same as that described in step 401 of the embodiment of FIG. 4 .

[0358] Step 502: The modulation layer of the UE determines the PDU aggregate loss rate.

[0359] The modulation layer of the UE monitors the PDU aggregate loss rate of the uplink PDU aggregate according to the PDU aggregate loss rate event in the subscription request and the monitoring trigger condition.

[0360] It should be noted that the modulation layer of the UE can determine the corresponding QFI according to the service flow description information in the subscription request, and then determine the PDU aggregate loss rate of the QoS flow indicated by the QFI.

[0361] Step 503: The modulation layer of the UE sends the PDU aggregate loss rate.

[0362] The step 503 is specifically as follows: the modulation layer of the UE sends the PDU aggregate loss rate to the application layer of the UE.

[0363] Optionally, after receiving the PDU aggregate loss rate, the UE application layer may perform corresponding processing according to the PDU aggregate loss rate, such as adjusting the bit rate or adjusting the FEC redundancy.

[0364] In the above solution, the UE's application layer requests to obtain the PDU aggregate loss rate, the UE's modulation layer monitors the PDU aggregate loss rate of the uplink PDU set, and opens the PDU aggregate loss rate to the outside, that is, to the UE's application layer, so that the UE's application layer can perform corresponding processing based on the PDU aggregate loss rate, avoiding blind control of the service layer and improving the service experience.

[0365] Figure 6 is a flow chart of a communication method provided in an embodiment of the present application. This embodiment is for monitoring and exposing the PDU aggregate delay in the downlink direction. For example, the base station monitors the PDU aggregate delay and exposes the monitoring results to the outside world via the user plane or control plane. The embodiment of Figure 6 is a specific example of implementation method 2 in the embodiment of Figure 2 above, and the base station is a specific example of the first network element in the embodiment of Figure 2.

[0366] The method comprises the following steps:

[0367] Step 601: The AF sends a subscription request to the PCF. Correspondingly, the PCF receives the subscription request.

[0368] The subscription request includes service flow description information, a PDU set delay event (PDU Set Delay Event), a monitoring trigger condition and / or a reporting trigger condition. The subscription request is used to request the PCF to subscribe to the PDU set delay.

[0369] The service flow description information is used to indicate the service flow to be monitored. The service flow description information may be information such as an IP triplet or a quintuple of the service flow.

[0370] The monitoring trigger condition is used to indicate the conditions for triggering the monitoring of the PDU set delay. Exemplarily, the monitoring trigger condition is used to indicate periodic triggering of monitoring, or to indicate event triggering of monitoring. When the monitoring trigger condition is used to indicate periodic triggering of monitoring, the monitoring trigger condition may include the monitoring period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event-triggered monitoring may, for example, be that the maximum delay (or average delay) of the PDU set is greater than a preset threshold, or that the network congestion level exceeds a preset threshold, and so on.

[0371] The reporting trigger condition is used to indicate the conditions for triggering the reporting of the PDU set delay. Exemplarily, the reporting trigger condition is used to indicate periodic trigger reporting, or to indicate event trigger reporting. When the reporting trigger condition is used to indicate periodic trigger reporting, the reporting trigger condition may include the reporting period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event trigger monitoring may be, for example, that the maximum delay (or average delay) of the PDU set is greater than a preset threshold, or that the network congestion level exceeds a preset threshold.

[0372] It should be noted that the monitoring trigger condition and the reporting trigger condition may be the same or different. When they are the same, the monitoring trigger condition and the reporting trigger condition may be collectively referred to as trigger conditions.

[0373] Optionally, the subscription request further includes a monitoring window, which is used to indicate the length of monitoring time, such as 1 hour, 2 hours, etc.

[0374] Optionally, the subscription request also includes a reporting indication, which is used to instruct (or trigger, or cause) the monitoring results to be sent to the UPF, which can be understood as the reporting indication being used to instruct (or trigger, or cause) the monitoring results to be exposed to the outside through the user surface. Alternatively, the reporting indication is used to instruct the monitoring results to be sent to the SMF, which can be understood as the reporting indication being used to instruct (or trigger, or cause) the monitoring results to be exposed to the outside through the control surface.

[0375] As an implementation method, the AF can be a third-party application server or an application server within the 5G core network. If the AF is in a trusted domain, the AF can interact directly with the PCF, that is, by calling the PCF service interface, such as the Npcf_PolicyAuthorization service interface or the Npcf_EventExposure service interface, to send a subscription request to the PCF. If the AF is in a non-trusted domain, the AF needs to interact with the PCF through the NEF. The AF calls the NEF service interface, such as the Nnef_AFSessionWithQoS service interface or the Nnef_EventExposure service interface, to send a subscription request to the PCF. Then, the NEF calls the PCF service interface in response to send a subscription request to the PCF, so that the PCF receives the subscription request.

[0376] Among them, regarding the definition of PDU aggregate delay, reference can be made to the description of the second implementation method in the embodiment of Figure 2 above, and no further details will be given.

[0377] Step 602: The PCF generates PCC rules.

[0378] Exemplarily, the PCF generates PCC rules based on the subscription request and / or local policy. The PCC rules include service flow description information, PDU aggregate delay events, monitoring trigger conditions, and / or reporting trigger conditions. Optionally, the PCC rules also include at least one of a monitoring window, a reporting indication, and a QoS monitoring policy.

[0379] Step 603: The PCF sends the PCC rules to the SMF. Correspondingly, the SMF receives the PCC rules.

[0380] In one implementation method, if the UE initiates the PDU session establishment or modification process, the SMF actively initiates the session management policy association establishment or modification process and obtains the PCC rule from the PCF.

[0381] In another implementation method, if the session management policy association modification process is initiated by the PCF, the PCF actively sends the PCC rule to the SMF.

[0382] Step 604: The SMF instructs the base station and the UPF to monitor the N3 segment QoS measurement delay between the base station and the UPF.

[0383] The N3 QoS measurement delay between the base station and the UPF refers to the delay required to transmit data packets or PDU sets between the base station and the UPF.

[0384] The QoS measurement delay of the N3 segment monitored by the base station and UPF can be considered as dynamic delay, that is, the QoS delay that needs to be obtained by dynamic measurement.

[0385] As an implementation method, the SMF sends indication information to the base station and UPF based on the QoS monitoring policy in the PCC rule, which is used to instruct the base station and UPF to monitor the N3 segment QoS measurement delay between the base station and the UPF.

[0386] Optionally, the UPF may also report the N3-segment QoS measurement delay between the base station and the UPF to the SMF, and the SMF may also report the N3-segment QoS measurement delay between the base station and the UPF to the PCF.

[0387] This step 604 is an optional step.

[0388] Step 605: The SMF generates monitoring parameters.

[0389] Exemplarily, the SMF generates monitoring parameters according to PCC rules and / or local policies from the PCF.

[0390] The monitoring parameters include QFI, PDU aggregate delay event, monitoring trigger condition and / or reporting trigger condition. Optionally, the monitoring parameters also include at least one of a monitoring window and a reporting indication.

[0391] The QFI is used to indicate the QoS flow corresponding to the service flow description information.

[0392] Step 606: The SMF sends the monitoring parameters to the base station. Correspondingly, the base station receives the monitoring parameters.

[0393] After step 606, the remaining PDU session establishment or modification process will be completed. For details, please refer to Section 4.3.2.1 of TS23.502.

[0394] Among them, SMF sends monitoring parameters to the base station, specifically SMF sends monitoring parameters to the base station through AMF.

[0395] Step 607: The base station determines the PDU aggregation delay according to the monitoring parameters.

[0396] Exemplarily, the base station monitors the PDU aggregate delay of the downlink PDU aggregate according to the PDU aggregate delay event in the monitoring parameters and the monitoring trigger condition.

[0397] Step 608: The base station sends the PDU aggregate delay.

[0398] In one implementation method, if the reporting indication is used to indicate (or trigger, or enable) the sending of monitoring results to the UPF, then step 608 is specifically as follows: the base station adds the monitoring results to the GTP-U layer of the uplink data packet and reports it to the UPF, and then the UPF sends the monitoring results to the AF, or the UPF sends the monitoring results to the AF through the NEF. The monitoring result is the PDU aggregate delay, or the sum of the PDU aggregate delay and the N3-segment CN-PDB. The N3-segment CN-PDB is the delay required to transmit a data packet or PDU aggregate between the base station and the UPF. The N3-segment CN-PDB can be considered as a static delay.

[0399] In another implementation method, if the reporting indication is used to indicate (or trigger, or cause) the transmission of the monitoring result to the UPF, then step 608 is specifically as follows: the base station adds the PDU aggregate delay to the GTP-U layer of the uplink data packet and reports it to the UPF. The UPF determines the monitoring result based on the PDU aggregate delay, and then the UPF sends the monitoring result to the AF, or the UPF sends the monitoring result to the AF through the NEF. The monitoring result is the sum of the PDU aggregate delay and the N3 segment CN-PDB, or the sum of the PDU aggregate delay and the N3 segment QoS measurement delay.

[0400] In another implementation method, if the reporting indication is used to instruct (or trigger, or cause) the monitoring result to be sent to the SMF, then step 608 specifically includes: the base station sends the monitoring result to the SMF, and then the SMF sends the monitoring result to the PCF, and the PCF sends the monitoring result to the AF, or the PCF sends the monitoring result to the AF through the NEF. The monitoring result is the PDU aggregate delay, or the sum of the PDU aggregate delay and the N3-segment CN-PDB.

[0401] In another implementation method, if the reporting indication is used to indicate (or trigger, or cause) the sending of monitoring results to the SMF, then step 608 is specifically as follows: the base station sends the PDU aggregate delay to the SMF, and then the SMF sends the PDU aggregate delay to the PCF. The PCF determines the monitoring result based on the PDU aggregate delay, and then the PCF sends the monitoring result to the AF, or the PCF sends the monitoring result to the AF through the NEF. The monitoring result is the sum of the PDU aggregate delay and the N3-segment CN-PDB, or the sum of the PDU aggregate delay and the N3-segment QoS measurement delay.

[0402] In another implementation method, if the reporting indication is used to indicate (or trigger, or cause) the sending of monitoring results to the SMF, then step 608 is specifically as follows: the base station sends the PDU aggregate delay to the SMF, and then the SMF determines the monitoring result based on the PDU aggregate delay and sends the monitoring result to the PCF, and then the PCF sends the monitoring result to the AF, or the PCF sends the monitoring result to the AF through the NEF. The monitoring result is the sum of the PDU aggregate delay and the N3-segment CN-PDB, or the sum of the PDU aggregate delay and the N3-segment QoS measurement delay.

[0403] Optionally, after the AF receives the monitoring result, the application layer of the AF may perform corresponding processing according to the monitoring result, such as adjusting the bit rate or adjusting the FEC redundancy.

[0404] In the above solution, the AF requests the core network to obtain the monitoring results. The base station monitors the PDU aggregate delay of the downlink PDU set and opens the PDU aggregate delay to the outside world, that is, to the AF. The AF can obtain the monitoring results and then perform corresponding processing based on the monitoring results, which can avoid blind control of the service layer and improve the service experience.

[0405] Figure 7 is a flow chart of a communication method provided in an embodiment of the present application. This embodiment is directed to monitoring and exposing the PDU aggregate delay in the uplink direction. For example, the UE monitors the PDU aggregate delay and exposes the monitoring results to the outside world via the user plane or control plane. The embodiment of Figure 7 is a specific example of implementation method 2 in the embodiment of Figure 2 above, and the UE is a specific example of the first network element in the embodiment of Figure 2.

[0406] The method comprises the following steps:

[0407] Step 701: The AF sends a subscription request to the PCF. Correspondingly, the PCF receives the subscription request.

[0408] The subscription request includes service flow description information, PDU aggregate delay event, monitoring trigger condition and / or reporting trigger condition. The subscription request is used to request the PCF to subscribe to the PDU aggregate delay.

[0409] The service flow description information is used to indicate the service flow to be monitored. The service flow description information may be information such as an IP triplet or a quintuple of the service flow.

[0410] The monitoring trigger condition is used to indicate the conditions for triggering the monitoring of the PDU set delay. Exemplarily, the monitoring trigger condition is used to indicate periodic triggering of monitoring, or to indicate event triggering of monitoring. When the monitoring trigger condition is used to indicate periodic triggering of monitoring, the monitoring trigger condition may include the monitoring period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event-triggered monitoring may, for example, be that the maximum delay (or average delay) of the PDU set is greater than a preset threshold, or that the network congestion level exceeds a preset threshold, and so on.

[0411] The reporting trigger condition is used to indicate the conditions for triggering the reporting of the PDU set delay. Exemplarily, the reporting trigger condition is used to indicate periodic trigger reporting, or to indicate event trigger reporting. When the reporting trigger condition is used to indicate periodic trigger reporting, the reporting trigger condition may include the reporting period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event trigger monitoring may be, for example, that the maximum delay (or average delay) of the PDU set is greater than a preset threshold, or that the network congestion level exceeds a preset threshold.

[0412] It should be noted that the monitoring trigger condition and the reporting trigger condition may be the same or different. When they are the same, the monitoring trigger condition and the reporting trigger condition may be collectively referred to as trigger conditions.

[0413] Optionally, the subscription request further includes a monitoring window, which is used to indicate the length of monitoring time, such as 1 hour, 2 hours, etc.

[0414] Optionally, the subscription request also includes a reporting indication, which is used to instruct (or trigger, or cause) the monitoring results to be sent to the UPF, which can be understood as the reporting indication being used to instruct (or trigger, or cause) the monitoring results to be exposed to the outside through the user surface. Alternatively, the reporting indication is used to instruct (or trigger, or cause) the monitoring results to be sent to the SMF, which can be understood as the reporting indication being used to instruct (or trigger, or cause) the monitoring results to be exposed to the outside through the control surface.

[0415] As an implementation method, the AF can be a third-party application server or an application server within the 5G core network. If the AF is in a trusted domain, the AF can interact directly with the PCF, that is, by calling the PCF service interface, such as the Npcf_PolicyAuthorization service interface or the Npcf_EventExposure service interface, to send a subscription request to the PCF. If the AF is in a non-trusted domain, the AF needs to interact with the PCF through the NEF. The AF calls the NEF service interface, such as the Nnef_AFSessionWithQoS service interface or the Nnef_EventExposure service interface, to send a subscription request to the PCF. Then, the NEF calls the PCF service interface in response to send a subscription request to the PCF, so that the PCF receives the subscription request.

[0416] Among them, regarding the definition of PDU aggregate delay, reference can be made to the description of the second implementation method in the embodiment of Figure 2 above, and no further details will be given.

[0417] Step 702: The PCF generates PCC rules.

[0418] Exemplarily, the PCF generates PCC rules based on the subscription request and / or local policy. The PCC rules include service flow description information, PDU aggregate delay events, monitoring trigger conditions, and / or reporting trigger conditions. Optionally, the PCC rules also include at least one of a monitoring window, a reporting indication, and a QoS monitoring policy.

[0419] Step 703: The PCF sends the PCC rules to the SMF. Correspondingly, the SMF receives the PCC rules.

[0420] In one implementation method, if the UE initiates the PDU session establishment or modification process, the SMF actively initiates the session management policy association establishment or modification process and obtains the PCC rule from the PCF.

[0421] In another implementation method, if the session management policy association modification process is initiated by the PCF, the PCF actively sends the PCC rule to the SMF.

[0422] Step 704: The SMF instructs the base station and the UPF to monitor the N3 segment QoS measurement delay between the base station and the UPF.

[0423] The N3 QoS measurement delay between the base station and the UPF refers to the delay required to transmit data packets or PDU sets between the base station and the UPF.

[0424] The QoS measurement delay of segment N3 monitored by the base station and UPF can be considered as dynamic delay.

[0425] As an implementation method, the SMF sends indication information to the base station and UPF based on the QoS monitoring policy in the PCC rule, which is used to instruct the base station and UPF to monitor the N3 segment QoS measurement delay between the base station and the UPF.

[0426] Optionally, the UPF may also report the N3 segment QoS measurement delay between the base station and the UPF to the SMF, and the SMF may also report the N3 segment QoS measurement delay between the base station and the UPF to the PCF.

[0427] This step 704 is an optional step.

[0428] Step 705: SMF generates monitoring parameters.

[0429] Exemplarily, the SMF generates monitoring parameters according to PCC rules and / or local policies from the PCF.

[0430] The monitoring parameters include QFI, PDU aggregate delay event, monitoring trigger condition and / or reporting trigger condition. Optionally, the monitoring parameters also include at least one of a monitoring window and a reporting indication.

[0431] The QFI is used to indicate the QoS flow corresponding to the service flow description information.

[0432] Step 706: The SMF sends the monitoring parameters to the UE. Correspondingly, the UE receives the monitoring parameters.

[0433] After step 706, the remaining PDU session establishment or modification process will be completed. For details, please refer to Section 4.3.2.1 of TS23.502.

[0434] Among them, SMF sends monitoring parameters to UE, specifically SMF sends monitoring parameters to UE through AMF.

[0435] Step 707: The UE determines the PDU aggregate delay based on the monitoring parameters.

[0436] The UE monitors the PDU aggregate delay of the downlink PDU aggregate according to the PDU aggregate delay event in the monitoring parameters and the monitoring trigger condition.

[0437] Step 708: UE sends PDU aggregate delay.

[0438] In one implementation method, if the reporting indication is used to indicate (or trigger, or enable) the sending of monitoring results to the UPF, then step 708 is specifically as follows: the UE adds the monitoring result to the PDCP layer header of the uplink data packet and sends it to the base station, and then the base station adds the monitoring result to the GTP-U layer of the uplink data packet and reports it to the UPF, and then the UPF sends the monitoring result to the AF, or the UPF sends the monitoring result to the AF through the NEF. The monitoring result is the PDU aggregate delay, or the sum of the PDU aggregate delay and the N3 segment CN-PDB. The N3 segment CN-PDB is the delay required for transmitting data packets or PDU aggregates between the base station and the UPF. The N3 segment CN-PDB can be considered as a static delay.

[0439] In another implementation method, if the reporting indication is used to indicate (or trigger, or enable) the sending of monitoring results to the UPF, then step 708 is specifically as follows: the UE adds the PDU aggregate delay to the PDCP layer header of the uplink data packet and sends it to the base station, and then the base station adds the PDU aggregate delay to the GTP-U layer of the uplink data packet and reports it to the UPF, the UPF determines the monitoring result based on the PDU aggregate delay, and then the UPF sends the monitoring result to the AF, or the UPF sends the monitoring result to the AF through the NEF. The monitoring result is the sum of the PDU aggregate delay and the N3 segment CN-PDB, or the sum of the PDU aggregate delay and the N3 segment QoS measurement delay.

[0440] In another implementation method, if the reporting indication is used to indicate (or trigger, or enable) the sending of monitoring results to the SMF, then step 708 is specifically: the UE sends the monitoring results to the SMF, and then the SMF sends the monitoring results to the PCF, the PCF sends the monitoring results to the AF, or the PCF sends the monitoring results to the AF through the NEF. The monitoring result is the PDU aggregate delay, or the sum of the PDU aggregate delay and the N3 segment CN-PDB. (or trigger, or enable)

[0441] In another implementation method, if the reporting indication is used to indicate (or trigger, or cause) the sending of the monitoring result to the SMF, then step 708 is specifically as follows: the UE sends the PDU aggregate delay to the SMF, and then the SMF sends the PDU aggregate delay to the PCF, the PCF determines the monitoring result based on the PDU aggregate delay, and then the PCF sends the monitoring result to the AF, or the PCF sends the monitoring result to the AF through the NEF. The monitoring result is the sum of the PDU aggregate delay and the N3-segment CN-PDB, or the sum of the PDU aggregate delay and the N3-segment QoS measurement delay.

[0442] In another implementation method, if the reporting indication is used to indicate (or trigger, or cause) the sending of monitoring results to the SMF, then step 708 is specifically as follows: the UE sends the PDU aggregate delay to the SMF, and then the SMF determines the monitoring result based on the PDU aggregate delay and sends the monitoring result to the PCF, and then the PCF sends the monitoring result to the AF, or the PCF sends the monitoring result to the AF through the NEF. The monitoring result is the sum of the PDU aggregate delay and the N3-segment CN-PDB, or the sum of the PDU aggregate delay and the N3-segment QoS measurement delay.

[0443] Optionally, after the AF receives the monitoring result, the application layer of the AF may perform corresponding processing according to the monitoring result, such as adjusting the bit rate or adjusting the FEC redundancy.

[0444] In the above solution, the AF requests the core network to obtain the monitoring results. The UE monitors the PDU aggregate delay of the uplink PDU set and opens the PDU aggregate delay to the outside world, that is, to the AF. The AF can obtain the monitoring results and then perform corresponding processing based on the monitoring results, which can avoid blind control of the service layer and improve the service experience.

[0445] FIG8 is a flow chart of a communication method provided in an embodiment of the present application. This embodiment is for monitoring and exposing the PDU aggregate delay in the uplink direction. For example, the UE's modulation layer monitors the PDU aggregate delay and exposes the monitoring results to the UE's application layer. The method includes the following steps:

[0446] Step 801: The application layer of the UE sends a subscription request to the modulation layer of the UE. Correspondingly, the modulation layer of the UE receives the subscription request.

[0447] The subscription request includes service flow description information, PDU aggregate delay event, monitoring trigger condition and / or reporting trigger condition. The subscription request is used to request the PCF to subscribe to the PDU aggregate delay.

[0448] The service flow description information is used to indicate the service flow to be monitored. The service flow description information may be information such as an IP triplet or a quintuple of the service flow.

[0449] The monitoring trigger condition is used to indicate the conditions for triggering the monitoring of the PDU set delay. Exemplarily, the monitoring trigger condition is used to indicate periodic triggering of monitoring, or to indicate event triggering of monitoring. When the monitoring trigger condition is used to indicate periodic triggering of monitoring, the monitoring trigger condition may include the monitoring period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event-triggered monitoring may, for example, be that the maximum delay (or average delay) of the PDU set is greater than a preset threshold, or that the network congestion level exceeds a preset threshold, and so on.

[0450] The reporting trigger condition is used to indicate the conditions for triggering the reporting of the PDU set delay. Exemplarily, the reporting trigger condition is used to indicate periodic trigger reporting, or to indicate event trigger reporting. When the reporting trigger condition is used to indicate periodic trigger reporting, the reporting trigger condition may include the reporting period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event trigger monitoring may be, for example, that the maximum delay (or average delay) of the PDU set is greater than a preset threshold, or that the network congestion level exceeds a preset threshold.

[0451] It should be noted that the monitoring trigger condition and the reporting trigger condition may be the same or different. When they are the same, the monitoring trigger condition and the reporting trigger condition may be collectively referred to as trigger conditions.

[0452] Optionally, the subscription request further includes a monitoring window, which is used to indicate the length of monitoring time, such as 1 hour, 2 hours, etc.

[0453] Optionally, the subscription request also includes a reporting indication, which is used to indicate (or trigger, or enable) reporting of monitoring results through the interactive interface between the UE's modulation layer and the UE's application layer, that is, the UE's modulation layer sends the monitoring results to the UE's application layer.

[0454] The specific meaning of the PDU aggregate delay is the same as described in step 707 of the embodiment of FIG. 7 .

[0455] Step 802: The modulation layer of the UE determines the PDU aggregate delay.

[0456] The modulation layer of the UE monitors the PDU aggregate delay of the uplink PDU aggregate according to the PDU aggregate delay event in the subscription request and the monitoring trigger condition.

[0457] It should be noted that the modulation layer of the UE can determine the corresponding QFI according to the service flow description information in the subscription request, and then determine the PDU aggregate delay of the QoS flow indicated by the QFI.

[0458] Step 803: The modulation layer of the UE sends the PDU aggregate delay.

[0459] The specific steps of step 803 are as follows: the modulation layer of the UE sends the monitoring result to the application layer of the UE. The monitoring result is the PDU aggregate delay, or the sum of the PDU aggregate delay and the N3-segment CN-PDB, or the sum of the PDU aggregate delay and the N3-segment QoS measurement delay. Among them, the N3-segment CN-PDB is the delay required for transmitting data packets or PDU aggregates between the base station and the UPF, and the N3-segment CN-PDB can be considered as a static delay. The N3-segment QoS measurement delay refers to the delay required for transmitting data packets or PDU aggregates between the base station monitored by the SMF or PCF and the UPF.

[0460] Optionally, after receiving the monitoring result, the UE application layer may perform corresponding processing according to the monitoring result, such as adjusting the bit rate or adjusting the FEC redundancy.

[0461] In the above solution, the UE's application layer requests to obtain the PDU aggregate delay, the UE's modulation layer monitors the PDU aggregate delay of the uplink PDU set, and opens the monitoring results to the outside world, that is, to the UE's application layer, so that the UE's application layer can perform corresponding processing based on the monitoring results, avoiding blind control of the service layer and improving the service experience.

[0462] Figure 9 is a flow chart of a communication method provided in an embodiment of the present application. This embodiment provides a monitoring and disclosure mechanism for PDU aggregate extended delay, where the PDU aggregate extended delay is monitored and disclosed externally by the UPF. The embodiment of Figure 9 is based on a specific example of implementation method three in the embodiment of Figure 2 above, and the UPF is a specific example of the first network element in the embodiment of Figure 2.

[0463] The method comprises the following steps:

[0464] Step 901: The AF sends a subscription request to the PCF. Correspondingly, the PCF receives the subscription request.

[0465] The subscription request includes service flow description information, a PDU Set Spread Delay Event, a monitoring trigger condition, and / or a reporting trigger condition. The subscription request is used to request the PCF to subscribe to the PDU Set Spread Delay Event.

[0466] The service flow description information is used to indicate the service flow to be monitored. The service flow description information may be information such as an IP triplet or a quintuple of the service flow.

[0467] The monitoring trigger condition is used to indicate the conditions for triggering the monitoring of the extended delay of the PDU set. Exemplarily, the monitoring trigger condition is used to indicate periodic triggering of monitoring, or to indicate event triggering of monitoring. When the monitoring trigger condition is used to indicate periodic triggering of monitoring, the monitoring trigger condition may include the monitoring period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event-triggered monitoring may be, for example, that the maximum extended delay (or average extended delay) of the PDU set is greater than a preset threshold, or that the network congestion level exceeds a preset threshold, and so on.

[0468] The reporting trigger condition is used to indicate the conditions for triggering the reporting of the extended delay of the PDU set. Exemplarily, the reporting trigger condition is used to indicate periodic triggered reporting, or to indicate event triggered reporting. When the reporting trigger condition is used to indicate periodic triggered reporting, the reporting trigger condition may include the reporting period size, or the period size may be pre-configured or predetermined by the protocol. Among them, event triggered monitoring may be, for example, that the maximum extended delay (or average extended delay) of the PDU set is greater than a preset threshold, or that the network congestion level exceeds a preset threshold.

[0469] It should be noted that the monitoring trigger condition and the reporting trigger condition may be the same or different. When they are the same, the monitoring trigger condition and the reporting trigger condition may be collectively referred to as trigger conditions.

[0470] Optionally, the subscription request further includes a monitoring window, which is used to indicate the length of monitoring time, such as 1 hour, 2 hours, etc.

[0471] Optionally, the subscription request further includes a reporting instruction, where the reporting instruction is used to instruct (or trigger, or cause) the monitoring result to be sent to the SMF. Alternatively, the reporting instruction is used to instruct (or trigger, or cause) the monitoring result to be sent to the NEF.

[0472] As an implementation method, the AF can be a third-party application server or an application server within the 5G core network. If the AF is in a trusted domain, the AF can interact directly with the PCF, that is, by calling the PCF service interface, such as the Npcf_PolicyAuthorization service interface or the Npcf_EventExposure service interface, to send a subscription request to the PCF. If the AF is in a non-trusted domain, the AF needs to interact with the PCF through the NEF. The AF calls the NEF service interface, such as the Nnef_AFSessionWithQoS service interface or the Nnef_EventExposure service interface, to send a subscription request to the PCF. Then, the NEF calls the PCF service interface in response to send a subscription request to the PCF, so that the PCF receives the subscription request.

[0473] Among them, regarding the definition of the PDU aggregate extended delay, reference can be made to the description of the implementation method three in the embodiment of Figure 2 above, and no further details will be given.

[0474] Step 902: The PCF generates PCC rules.

[0475] Exemplarily, the PCF generates a PCC rule based on the subscription request and / or local policy. The PCC rule includes service flow description information, a PDU aggregate extended delay event, a monitoring trigger condition, and / or a reporting trigger condition. Optionally, the PCC rule also includes at least one of a monitoring window, a reporting indication, or a QoS monitoring configuration.

[0476] Step 903: The PCF sends the PCC rules to the SMF. Correspondingly, the SMF receives the PCC rules.

[0477] In one implementation method, if the UE initiates the PDU session establishment or modification process, the SMF actively initiates the session management policy association establishment or modification process and obtains the PCC rule from the PCF.

[0478] In another implementation method, if the session management policy association modification process is initiated by the PCF, the PCF actively sends the PCC rule to the SMF.

[0479] Step 904: The SMF generates monitoring parameters.

[0480] Exemplarily, the SMF generates monitoring parameters according to PCC rules and / or local policies from the PCF.

[0481] The monitoring parameters include QFI, PDU aggregate extended delay event, monitoring trigger condition and / or reporting trigger condition. Optionally, the monitoring parameters also include at least one of a monitoring window or a reporting indication.

[0482] The QFI is used to indicate the QoS flow corresponding to the service flow description information.

[0483] Step 905: The SMF sends monitoring parameters to the UPF. Correspondingly, the UPF receives the monitoring parameters.

[0484] After step 905, the remaining PDU session establishment or modification process will be completed. For details, please refer to Section 4.3.2.1 of TS23.502.

[0485] Step 906: The UPF determines the PDU aggregate extended delay based on the monitoring parameters.

[0486] The UPF monitors the PDU aggregate extended delay of the downlink PDU aggregate according to the PDU aggregate extended delay event in the monitoring parameters and the monitoring trigger condition.

[0487] Step 907: UPF sends the PDU aggregate extended delay.

[0488] For example, if the reporting indication is used to indicate (or trigger, or enable) sending the monitoring results to the SMF, then step 907 is specifically: the UPF sends the PDU set extended delay to the SMF, the SMF sends the PDU set extended delay to the PCF, the PCF sends the PDU set extended delay to the AF, or the PCF sends the PDU set extended delay to the AF through the NEF.

[0489] Exemplarily, if the reporting indication is used to indicate (or trigger, or enable) sending the monitoring result to the NEF, then step 907 is specifically: the UPF sends the PDU aggregate extended delay to the NEF, and then the NEF sends the PDU aggregate extended delay to the AF.

[0490] Optionally, after the AF receives the PDU aggregate extended delay, the application layer of the AF may perform corresponding processing based on the PDU aggregate extended delay, such as adjusting the bit rate or adjusting the FEC redundancy.

[0491] In the above solution, AF requests the core network to obtain the PDU set extended delay, UPF monitors the PDU set extended delay of the downlink PDU set, and opens the PDU set extended delay to the outside world, that is, to AF. AF can obtain the PDU set extended delay, so that AF can perform corresponding processing according to the PDU set extended delay, which can avoid blind control of the service layer and improve the service experience.

[0492] Figure 10 is a flow chart of a communication method provided in an embodiment of the present application. In this embodiment, the SMF discloses the result of whether PDU aggregation processing is enabled to the AF, ensuring that the AF can perceive the activation status of PDU aggregation processing within the 5G network. The embodiment of Figure 10 is a specific example of implementation method 4 in the embodiment of Figure 2 above, and the SMF is a specific example of the first network element in the embodiment of Figure 2.

[0493] The method comprises the following steps:

[0494] Step 1001: The AF sends a subscription request to the PCF. Correspondingly, the PCF receives the subscription request.

[0495] The subscription request includes service flow description information, an activation state event of the PDU aggregate QoS processing and / or a reporting trigger condition. The subscription request is used to request the PCF to subscribe to the activation state of the PDU aggregate QoS processing.

[0496] The service flow description information is used to indicate the service flow to be monitored. The service flow description information may be information such as an IP triplet or a quintuple of the service flow.

[0497] The reporting trigger condition is used to indicate the conditions for triggering the reporting of the enabled state of the PDU aggregate QoS processing. Exemplarily, the reporting trigger condition is used to indicate periodic reporting triggering, or to indicate event-triggered reporting. When the reporting trigger condition is used to indicate periodic reporting triggering, the reporting trigger condition may include a reporting period size, or the period size may be preconfigured or predetermined by the protocol.

[0498] It should be noted that the monitoring trigger condition and the reporting trigger condition may be the same or different. When they are the same, the monitoring trigger condition and the reporting trigger condition may be collectively referred to as trigger conditions.

[0499] Optionally, the subscription request further includes a reporting instruction, where the reporting instruction is used to instruct (or trigger, or cause) the monitoring result to be sent to the PCF. Alternatively, the reporting instruction is used to instruct (or trigger, or cause) the monitoring result to be sent to the NEF.

[0500] As an implementation method, the AF can be a third-party application server or an application server within the 5G core network. If the AF is in a trusted domain, the AF can interact directly with the PCF, that is, by calling the PCF service interface, such as the Npcf_PolicyAuthorization service interface or the Npcf_EventExposure service interface, to send a subscription request to the PCF. If the AF is in a non-trusted domain, the AF needs to interact with the PCF through the NEF. The AF calls the NEF service interface, such as the Nnef_AFSessionWithQoS service interface or the Nnef_EventExposure service interface, to send a subscription request to the PCF. Then, the NEF calls the PCF service interface in response to send a subscription request to the PCF, so that the PCF receives the subscription request.

[0501] Step 1002: The PCF generates PCC rules.

[0502] The PCF generates a PCC rule based on the subscription request and / or local policy. The PCC rule includes service flow description information, an activation status event for PDU aggregate QoS processing, and / or a reporting trigger condition. Optionally, the PCC rule also includes a reporting indication.

[0503] Step 1003: The PCF sends the PCC rules to the SMF. Correspondingly, the SMF receives the PCC rules.

[0504] In one implementation method, if the UE initiates the PDU session establishment or modification process, the SMF actively initiates the session management policy association establishment or modification process and obtains the PCC rule from the PCF.

[0505] In another implementation method, if the session management policy association modification process is initiated by the PCF, the PCF actively sends the PCC rule to the SMF.

[0506] Step 1004: The SMF monitors the enabled status of the PDU aggregate QoS processing according to the PCC rules.

[0507] As an implementation method, the SMF receives a capability indication from the base station, where the capability indication is used to indicate that the base station has the capability of PDU aggregate QoS processing. Then, the SMF monitors the activation state of the PDU aggregate QoS processing of the QoS flow based on the capability indication. For example, the SMF sends the PDU aggregate QoS parameters to the base station based on the capability indication. After sending the PDU aggregate QoS parameters, it is determined that the PDU aggregate QoS processing of the QoS flow has been activated, that is, the activation state of the PDU aggregate QoS processing of the QoS flow is on.

[0508] As another implementation method, the SMF sends the QoS parameters of the PDU set to the base station. If the SMF then receives a capability indication from the base station, which is used to indicate that the base station has the PDU set QoS processing capability, the SMF determines that the PDU set QoS processing of the QoS flow has been enabled, that is, the enabling state of the PDU set QoS processing of the QoS flow is on.

[0509] Step 1005, the SMF sends the enabled status of the PDU aggregate QoS processing.

[0510] In one implementation method, if the reporting indication is used to indicate (or trigger, or enable) sending monitoring results to PCF, then step 1005 is specifically: SMF sends the enabled status of PDU set QoS processing to PCF, and then PCF directly sends the enabled status of PDU set QoS processing to AF, or sends the enabled status of PDU set QoS processing to AF through NEF.

[0511] In another implementation method, if the reporting indication is used to indicate (or trigger, or enable) sending monitoring results to NEF, then step 1005 is specifically: SMF sends the enabled status of PDU set QoS processing to NEF, and then NEF sends the enabled status of PDU set QoS processing to AF.

[0512] Optionally, after the AF receives the enabled state of the PDU aggregate QoS processing, the application layer of the AF may perform corresponding processing according to the enabled state of the PDU aggregate QoS processing, such as adjusting the bit rate or adjusting the FEC redundancy.

[0513] In the above solution, AF requests the core network to obtain the enabled status of PDU aggregate QoS processing, SMF determines the enabled status of PDU aggregate QoS processing, and opens the enabled status of PDU aggregate QoS processing to the outside world, that is, to AF. AF can obtain the enabled status of PDU aggregate QoS processing, so that AF can perform corresponding processing according to the enabled status of PDU aggregate QoS processing, which can avoid blind control of the service layer and improve the service experience.

[0514] It is understandable that, in order to implement the functions in the above embodiments, the first network element or the application function network element includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily appreciate that, in combination with the units and method steps of the various examples described in the embodiments disclosed in this application, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.

[0515] Figures 11 and 12 are schematic diagrams of the structures of the communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the first network element or the application function network element in the above method embodiments, thereby also achieving the beneficial effects of the above method embodiments. In the embodiments of the present application, the communication device can be the first network element or the application function network element, or it can be a module (such as a chip) applied to the first network element or the application function network element.

[0516] The communication device 1100 shown in Figure 11 includes a processing unit 1110 and a transceiver unit 1120. The communication device 1100 is used to implement the functions of the first network element or the application function network element in the above method embodiment.

[0517] When the communication device 1100 is used to implement the function of the first network element in the above method embodiment, the transceiver unit 1120 is used to receive first information, and the first information is used to monitor the PDU set carried by the QoS flow and report the monitoring results of the PDU set; the processing unit 1110 is used to monitor the PDU set carried by the QoS flow according to the first information; the transceiver unit 1120 is also used to send the monitoring results of the PDU set to the second network element.

[0518] In one possible implementation method, the first information includes a PDU set loss rate event, and the PDU set loss rate event indicates that the monitored object is the PDU set loss rate; the processing unit 1110 is used to monitor the PDU set carried by the QoS flow according to the first information, specifically including: monitoring the PDU set loss rate of the QoS flow according to the first information.

[0519] In one possible implementation method, the first network element is an access network device, and the PDU aggregate loss rate includes one or more of the following:

[0520] The percentage of PDUs that the access network device fails to send to the terminal device;

[0521] The percentage of PDU sets discarded due to packet loss;

[0522] The percentage of PDU sets discarded due to transmission failures;

[0523] The percentage of data packets that failed to be transmitted;

[0524] The total number of packets that failed to be transmitted; or

[0525] The percentage of discarded PDU sets due to packet loss based on the importance of the PDU set.

[0526] In one possible implementation method, the first network element is a terminal device, and the PDU aggregate loss rate includes one or more of the following:

[0527] The percentage of PDU sets that the terminal device failed to send to the access network device;

[0528] The percentage of PDU sets discarded due to transmission failures;

[0529] The percentage of data packets that failed to be transmitted;

[0530] The total number of packets that failed to be transmitted; or

[0531] The percentage of discarded PDU sets due to packet loss based on the importance of the PDU set.

[0532] In one possible implementation method, the first information includes a PDU set delay event, and the PDU set delay event indicates that the monitored object is the PDU set delay; the processing unit 1110 is used to monitor the PDU set carried by the QoS flow according to the first information, specifically including: monitoring the PDU set delay of the QoS flow according to the first information.

[0533] In one possible implementation method, the first network element is an access network device, and the PDU aggregate delay includes one or more of the following:

[0534] The time taken by the access network device to successfully transmit the PDU set to the terminal device;

[0535] The time taken by the access network device to successfully transmit the PDU aggregate to the terminal device within the PDU aggregate delay budget; or

[0536] The time taken by the access network device to successfully transmit the PDU set to the terminal device exceeds the PDU set delay budget time.

[0537] In one possible implementation method, the first network element is a terminal device, and the PDU aggregate delay includes one or more of the following:

[0538] The time taken by the terminal device to successfully transmit the PDU set to the access network device;

[0539] The time taken by the terminal device to successfully transmit the PDU set to the access network device within the PDU set delay budget; or

[0540] The time taken by the terminal device to successfully transmit the PDU set to the access network device exceeds the PDU set delay budget time.

[0541] In a possible implementation method, the monitoring result includes the PDU aggregate delay, or includes the sum of the PDU aggregate delay and the N3 segment CN PDB.

[0542] In one possible implementation method, the first information includes a PDU set extended delay event, and the PDU set extended delay event indicates that the monitored object is the PDU set extended delay; the first network element is a user plane network element; the processing unit 1110 is used to monitor the PDU set carried by the QoS flow according to the first information, specifically including: monitoring the PDU set extended delay of the QoS flow according to the first information.

[0543] In one possible implementation method, the PDU aggregate extended delay includes one or more of the following:

[0544] The time interval between the arrival of the first packet of the PDU set at the user plane network element and the arrival of the last packet at the user plane network element;

[0545] The time interval between the first packet of the PDU set arriving at the user plane network element and the last packet leaving the user plane network element;

[0546] The time interval between the first packet of a PDU set leaving the user plane network element and the last packet leaving the user plane network element; or

[0547] The proportion of the target PDU set, wherein the time interval between the first packet of the target PDU set arriving at the user plane network element and the last packet arriving at the user plane network element does not exceed a preset threshold.

[0548] In one possible implementation method, the first information includes an enabled status event of PDU set QoS processing, and the enabled status event of PDU set QoS processing indicates that the monitored object is the enabled status of PDU set QoS processing; the first network element is a session management network element; the processing unit 1110 is used to monitor the PDU set carried by the QoS flow according to the first information, specifically including: monitoring the enabled status of the PDU set QoS processing of the QoS flow according to the first information.

[0549] In one possible implementation method, the processing unit 1110 is used to monitor the enabled status of the PDU set QoS processing of the QoS flow, specifically including: receiving a capability indication from the access network device through the transceiver unit 1120, the capability indication being used to indicate that the access network device has the PDU set QoS processing capability; and monitoring the enabled status of the PDU set QoS processing of the QoS flow according to the capability indication.

[0550] In one possible implementation method, the processing unit 1110 is used to monitor the enabled status of the PDU set QoS processing of the QoS flow according to the capability indication, specifically including: sending the QoS parameters of the PDU set to the access network device through the transceiver unit 1120 according to the capability indication, and then determining that the PDU set QoS processing of the QoS flow has been enabled.

[0551] In one possible implementation method, the processing unit 1110 is used to monitor the enabled status of the PDU set QoS processing of the QoS flow, specifically including: sending the QoS parameters of the PDU set to the access network device through the transceiver unit 1120; and receiving a capability indication from the access network device, then determining that the PDU set QoS processing of the QoS flow has been enabled, wherein the capability indication is used to indicate that the access network device has the PDU set QoS processing capability.

[0552] In one possible implementation method, the first information includes a reporting indication, and the reporting indication is used to indicate that the monitoring results of the PDU set are reported to the second network element; the transceiver unit 1120 is used to send the monitoring results of the PDU set to the second network element, specifically including: sending the monitoring results to the second network element according to the reporting indication.

[0553] When the communication device 1100 is used to implement the function of the application function network element in the above method embodiment, the processing unit 1110 is used to control the transceiver unit 1120 to send a subscription request, and the subscription request is used to subscribe to the monitoring results of the PDU set of the service flow; and receive the monitoring results of the PDU set of the service flow.

[0554] In one possible implementation method, the subscription request includes a PDU aggregate loss rate event, and the PDU aggregate loss rate event indicates that the monitoring object is the PDU aggregate loss rate; the processing unit 1110 is configured to control the transceiver unit 1120 to receive the monitoring result of the PDU aggregate of the service flow, specifically including: controlling the transceiver unit 1120 to receive the PDU aggregate loss rate of the service flow. In one possible implementation method, the PDU aggregate loss rate comes from an access network device, and the PDU aggregate loss rate includes one or more of the following:

[0555] The percentage of PDUs that the access network device fails to send to the terminal device;

[0556] The percentage of PDU sets discarded due to packet loss;

[0557] The percentage of PDU sets discarded due to transmission failures;

[0558] The percentage of data packets that failed to be transmitted;

[0559] The total number of packets that failed to be transmitted; or

[0560] The percentage of discarded PDU sets due to packet loss based on the importance of the PDU set.

[0561] In one possible implementation method, the PDU aggregate loss rate is from a terminal device, and the PDU aggregate loss rate includes one or more of the following:

[0562] The percentage of PDU sets that the terminal device failed to send to the access network device;

[0563] The percentage of PDU sets discarded due to transmission failures;

[0564] The percentage of data packets that failed to be transmitted;

[0565] The total number of packets that failed to be transmitted; or

[0566] The percentage of discarded PDU sets due to packet loss based on the importance of the PDU set.

[0567] In one possible implementation method, the subscription request includes a PDU set delay event, and the PDU set delay event indicates that the monitoring object is the PDU set delay; the processing unit 1110 is used to control the transceiver unit 1120 to receive the monitoring result of the PDU set of the service flow, specifically including: controlling the transceiver unit 1120 to receive the PDU set delay of the service flow, or the sum of the PDU set delay and the N3 segment CN PDB.

[0568] In one possible implementation method, the monitoring result comes from an access network device, and the PDU aggregate delay includes one or more of the following:

[0569] The time taken by the access network device to successfully transmit the PDU set to the terminal device;

[0570] The time taken by the access network device to successfully transmit the PDU aggregate to the terminal device within the PDU aggregate delay budget; or

[0571] The time taken by the access network device to successfully transmit the PDU set to the terminal device exceeds the PDU set delay budget time.

[0572] In one possible implementation method, the monitoring result comes from a terminal device, and the PDU aggregate delay includes one or more of the following:

[0573] The time taken by the terminal device to successfully transmit the PDU set to the access network device;

[0574] The time taken by the terminal device to successfully transmit the PDU set to the access network device within the PDU set delay budget; or

[0575] The time taken by the terminal device to successfully transmit the PDU set to the access network device exceeds the PDU set delay budget time.

[0576] In one possible implementation method, the subscription request includes a PDU set extended delay event, and the PDU set extended delay event indicates that the monitoring object is the PDU set extended delay; the processing unit 1110 is used to control the transceiver unit 1120 to receive the monitoring results of the PDU set of the business flow, specifically including: controlling the transceiver unit 1120 to receive the PDU set extended delay of the business flow.

[0577] In one possible implementation method, the monitoring result comes from a user plane network element, and the PDU aggregate extended delay includes one or more of the following:

[0578] The time interval between the arrival of the first packet of the PDU set at the user plane network element and the arrival of the last packet at the user plane network element;

[0579] The time interval between the first packet of the PDU set arriving at the user plane network element and the last packet leaving the user plane network element;

[0580] The time interval between the first packet of a PDU set leaving the user plane network element and the last packet leaving the user plane network element; or

[0581] The proportion of the target PDU set, wherein the time interval between the first packet of the target PDU set arriving at the user plane network element and the last packet arriving at the user plane network element does not exceed a preset threshold.

[0582] In one possible implementation method, the subscription request includes an enabled status event of the PDU set QoS processing, and the enabled status event of the PDU set QoS processing indicates that the monitoring object is the enabled status of the PDU set QoS processing; the processing unit 1110 is used to control the transceiver unit 1120 to receive the monitoring results of the PDU set of the business flow, specifically including: controlling the transceiver unit 1120 to receive the enabled status of the PDU set QoS processing of the business flow.

[0583] In one possible implementation method, the subscription request includes a reporting indication, and the reporting indication is used to indicate that the monitoring results of the PDU set are reported to the second network element; the processing unit 1110 is used to control the transceiver unit 1120 to receive the monitoring results of the PDU set of the service flow, specifically including: controlling the transceiver unit 1120 to receive the monitoring results from the second network element.

[0584] A more detailed description of the processing unit 1110 and the transceiver unit 1120 can be directly obtained from the relevant description in the above method embodiment, and will not be repeated here.

[0585] The communication device 1200 shown in Figure 12 includes a processor 1210 and an interface circuit 1220. The processor 1210 and the interface circuit 1220 are coupled to each other. It is understood that the interface circuit 1220 can be a transceiver or an input / output interface. Optionally, the communication device 1200 may also include a memory 1230 for storing instructions executed by the processor 1210, or storing input data required by the processor 1210 to execute instructions, or storing data generated after the processor 1210 executes instructions.

[0586] When the communication device 1200 is used to implement the above method embodiment, the processor 1210 is used to implement the functions of the above processing unit 1110 , and the interface circuit 1220 is used to implement the functions of the above transceiver unit 1120 .

[0587] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0588] Those skilled in the art will understand that the various numerical numbers such as the first and second involved in this application are only for the convenience of description, and are not used to limit the scope of the embodiments of the present application, nor do they represent the order of precedence. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one" refers to one or more. At least two refers to two or more. "At least one" or similar expressions refer to any combination of these items, including any combination of single items (individuals) or plural items (individuals). For example, at least one item (individual, kind) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. "Multiple" refers to two or more, and other quantifiers are similar.

[0589] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean 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 the present application.

[0590] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0591] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. 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 computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0592] The various illustrative logic units and circuits described in the embodiments of the present application can be implemented or operated by a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or the design of any combination thereof. The general-purpose processor can be a microprocessor, alternatively, the general-purpose processor can also be any traditional processor, controller, microcontroller or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration to implement.

[0593] The steps of the method or algorithm described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two. The software unit can be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or other storage media in any form in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Alternatively, the storage medium can also be integrated into the processor. The processor and the storage medium can be arranged in an ASIC.

[0594] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0595] In one or more exemplary designs, the above-described functions described herein may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions may be stored on a computer-readable medium or transmitted in the form of one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one location to another. Storage media can be any available medium that can be accessed by a general-purpose or specialized computer. For example, such computer-readable media may include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store program code in the form of instructions or data structures and other forms that can be read by a general-purpose or specialized computer, or a general-purpose or specialized processor. In addition, any connection can be appropriately defined as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote resource via a coaxial cable, fiber optic cable, twisted pair cable, digital subscriber line (DSL), or wirelessly, such as infrared, wireless, and microwave, it is also included in the definition of computer-readable media. Disks and discs include compact disks, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while discs typically reproduce data optically using lasers. Combinations of these may also be included in computer-readable media.

[0596] Those skilled in the art will appreciate that, in one or more of the examples above, the functions described herein may be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0597] The specific implementation methods described above further explain the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above description is only the specific implementation method of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application. The above description of the specification of this application can enable any technical personnel in the field to utilize or implement the contents of this application. Any modification based on the disclosed contents should be considered obvious in the field. The basic principles described in this application can be applied to other variations without departing from the inventive essence and scope of the present application. Therefore, the contents disclosed in this application are not limited to the described embodiments and designs, but can also be extended to the maximum scope consistent with the principles of this application and the disclosed new features.

[0598] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the scope of the present application. Thus, the present application is intended to include such modifications and variations if they fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that: Applied to a first network element or a chip of the first network element, the method includes: Receive first information, where the first information is used to monitor a protocol data unit (PDU) set carried by a quality of service (QoS) flow and report a monitoring result of the PDU set; Monitoring a PDU set carried by the QoS flow according to the first information; The monitoring result of the PDU set is sent to the second network element.

2. The method according to claim 1, characterized in that The first information includes a PDU aggregate loss rate event, and the PDU aggregate loss rate event indicates that the monitoring object is a PDU aggregate loss rate; The monitoring, according to the first information, a PDU set carried by the QoS flow includes: The PDU set loss rate of the QoS flow is monitored according to the first information.

3. The method according to claim 2, characterized in that The first network element is an access network device, and the PDU set loss rate includes one or more of the following: The proportion of PDU sets that the access network device fails to send to the terminal device; The percentage of PDU sets discarded due to packet loss; The percentage of PDU sets discarded due to transmission failures; The percentage of data packets that failed to be transmitted; The total number of packets that failed to be transmitted; or The percentage of PDU sets discarded due to packet loss based on the importance of the PDU set.

4. The method according to claim 2, characterized in that The first network element is a terminal device, and the PDU set loss rate includes one or more of the following: The proportion of PDU sets that the terminal device fails to send to the access network device; The percentage of PDU sets discarded due to transmission failures; The percentage of data packets that failed to be transmitted; The total number of packets that failed to be transmitted; or The percentage of PDU sets discarded due to packet loss based on the importance of the PDU set.

5. The method according to claim 1, characterized in that The first information includes a PDU aggregate delay event, and the PDU aggregate delay event indicates that the monitoring object is the PDU aggregate delay; The monitoring, according to the first information, a PDU set carried by the QoS flow includes: Based on the first information, the PDU aggregate delay of the QoS flow is monitored.

6. The method according to claim 5, characterized in that The first network element is an access network device, and the PDU aggregate delay includes one or more of the following: The time taken by the access network device to successfully transmit the PDU set to the terminal device; The time taken by the access network device to successfully transmit the PDU set to the terminal device within the PDU set delay budget time; or The time taken by the access network device to successfully transmit the PDU set to the terminal device exceeds the PDU set delay budget time.

7. The method according to claim 5, characterized in that The first network element is a terminal device, and the PDU aggregate delay includes one or more of the following: The time taken by the terminal device to successfully transmit the PDU set to the access network device; The time taken by the terminal device to successfully transmit the PDU set to the access network device within the PDU set delay budget time; or The time taken by the terminal device to successfully transmit the PDU set to the access network device exceeds the PDU set delay budget time.

8. The method according to any one of claims 5 to 7, characterized in that The monitoring result includes the PDU aggregate delay, or includes the sum of the PDU aggregate delay and the N3 segment core network packet data delay budget CN PDB.

9. The method according to claim 1, characterized in that The first network element is a user plane network element; the first information includes a PDU aggregate extended delay event, and the PDU aggregate extended delay event indicates that the monitored object is a PDU aggregate extended delay; The monitoring, according to the first information, a PDU set carried by the QoS flow includes: Based on the first information, the PDU set extended delay of the QoS flow is monitored.

10. The method according to claim 9, characterized in that The PDU aggregate extended delay includes one or more of the following: The time interval between the first packet of the PDU set arriving at the user plane network element and the last packet arriving at the user plane network element; The time interval between the first packet of the PDU set arriving at the user plane network element and the last packet leaving the user plane network element; The time interval between the first packet of the PDU set leaving the user plane network element and the last packet leaving the user plane network element; or The proportion of the target PDU set, wherein the time interval between the first packet of the target PDU set arriving at the user plane network element and the last packet arriving at the user plane network element does not exceed a preset threshold.

11. The method according to claim 1, characterized in that The first network element is a session management network element; the first information includes an enabled state event of a PDU aggregate QoS processing, and the enabled state event of the PDU aggregate QoS processing indicates that the monitored object is an enabled state of the PDU aggregate QoS processing; The monitoring, according to the first information, a PDU set carried by the QoS flow includes: Based on the first information, the enabling status of the PDU set QoS processing of the QoS flow is monitored.

12. The method according to any one of claims 1 to 11, characterized in that The first information includes a reporting indication, where the reporting indication is used to indicate reporting a monitoring result of the PDU set to the second network element; The sending the monitoring result of the PDU set to the second network element includes: According to the reporting instruction, the monitoring result is sent to the second network element.

13. A communication method, characterized in that: include: Sending a subscription request, where the subscription request is used to subscribe to monitoring results of a PDU set of a service flow; Receive monitoring results of the PDU set of the service flow.

14. The method according to claim 13, characterized in that The subscription request includes a PDU aggregate loss rate event, and the PDU aggregate loss rate event indicates that the monitoring object is a PDU aggregate loss rate; The monitoring result of receiving the PDU set of the service flow includes: Receive a PDU aggregate loss rate of the service flow.

15. The method according to claim 14, characterized in that The PDU set loss rate is from an access network device, and the PDU set loss rate includes one or more of the following: The proportion of PDU sets that the access network device fails to send to the terminal device; The percentage of PDU sets discarded due to packet loss; The percentage of PDU sets discarded due to transmission failures; The percentage of data packets that failed to be transmitted; The total number of packets that failed to be transmitted; or The percentage of PDU sets discarded due to packet loss based on the importance of the PDU set.

16. The method according to claim 14, characterized in that The PDU aggregate loss rate is from a terminal device, and the PDU aggregate loss rate includes one or more of the following: The proportion of PDU sets that the terminal device fails to send to the access network device; The percentage of PDU sets discarded due to transmission failures; The percentage of data packets that failed to be transmitted; The total number of packets that failed to be transmitted; or The percentage of PDU sets discarded due to packet loss based on the importance of the PDU set.

17. The method according to claim 13, characterized in that The subscription request includes a PDU aggregate delay event, and the PDU aggregate delay event indicates that the monitoring object is the PDU aggregate delay; The monitoring result of receiving the PDU set of the service flow includes: The PDU aggregate delay of receiving the service flow, or the sum of the PDU aggregate delay and the N3 segment core network packet data packet delay budget CN PDB.

18. The method according to claim 17, characterized in that The monitoring result comes from the access network device, and the PDU aggregate delay includes one or more of the following: The time taken by the access network device to successfully transmit the PDU set to the terminal device; The time taken by the access network device to successfully transmit the PDU set to the terminal device within the PDU set delay budget time; or The time taken by the access network device to successfully transmit the PDU set to the terminal device exceeds the PDU set delay budget time.

19. The method according to claim 17, characterized in that The monitoring result comes from the terminal device, and the PDU aggregate delay includes one or more of the following: The time taken by the terminal device to successfully transmit the PDU set to the access network device; The time taken by the terminal device to successfully transmit the PDU set to the access network device within the PDU set delay budget time; or The time taken by the terminal device to successfully transmit the PDU set to the access network device exceeds the PDU set delay budget time.

20. The method of claim 13, wherein: The subscription request includes a PDU aggregate extended delay event, and the PDU aggregate extended delay event indicates that the monitoring object is a PDU aggregate extended delay; The monitoring result of receiving the PDU set of the service flow includes: The PDU set extension delay of receiving the service flow.

21. The method of claim 20, wherein: The monitoring result comes from the user plane network element, and the PDU set extended delay includes one or more of the following: The time interval between the first packet of the PDU set arriving at the user plane network element and the last packet arriving at the user plane network element; The time interval between the first packet of the PDU set arriving at the user plane network element and the last packet leaving the user plane network element; The time interval between the first packet of the PDU set leaving the user plane network element and the last packet leaving the user plane network element; or The proportion of the target PDU set, wherein the time interval between the first packet of the target PDU set arriving at the user plane network element and the last packet arriving at the user plane network element does not exceed a preset threshold.

22. The method of claim 13, wherein: The subscription request includes an enabled state event of the PDU aggregate QoS processing, and the enabled state event of the PDU aggregate QoS processing indicates that the monitoring object is the enabled state of the PDU aggregate QoS processing; The monitoring result of receiving the PDU set of the service flow includes: Receive the enabled state of PDU aggregate QoS processing for the service flow.

23. The method according to any one of claims 13 to 22, characterized in that The subscription request includes a reporting indication, where the reporting indication is used to indicate reporting the monitoring result of the PDU set to the second network element; The monitoring result of receiving the PDU set of the service flow includes: Receive the monitoring result from the second network element.

24. A communication device, characterized in that: The method comprises a module for executing the method described in any one of claims 1 to 12, or executing the method described in any one of claims 13 to 23.

25. A communication device, characterized in that: The invention comprises a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method described in any one of claims 1 to 12, or execute the method described in any one of claims 13 to 23.

26. A computer program product, characterized in that The computer program product comprises instructions, and when the instructions are executed on a communication device, the communication device is caused to execute the method according to any one of claims 1 to 12, or execute the method according to any one of claims 13 to 23.

27. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the method described in any one of claims 1 to 12 or the method described in any one of claims 13 to 23 is implemented.

28. A communication system, characterized in that: include: A first network element, configured to receive first information, wherein the first information is used to monitor a protocol data unit (PDU) set of a first quality of service (QoS) flow and report a monitoring result of the PDU set; Monitoring a PDU set carried by the QoS flow according to the first information; Sending the monitoring result of the PDU set to the second network element; The second network element is used to receive the monitoring result.

29. A communication system, characterized in that: include: The application function network element is used to send a subscription request to the policy control network element, where the subscription request is used to subscribe to the monitoring result of the PDU set of the service flow; and receiving a monitoring result of a PDU set of the service flow from the policy control network element; The policy control network element is used to receive the subscription request; And sending the monitoring result to the application function network element.

Images