RU2787009C2 - Communication method and related device - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: communication method contains sending by means of a network policy control element of the first information – a request to a network element for analytical data processing, while the first request information is intended for reception of quality of service information; and reception by means of the network policy control element of the first response information from the network element for analytical data processing, while the first response information contains quality of service information, which is requested by means of the use of the first request information; in this case, quality of service information is service experience information.

EFFECT: provision of a network policy control element with quality of service information.

23 cl, 13 dwg, 10 tbl

Description

[0001] This application claims priority on the basis of Chinese Patent Application No. 201811163075.6, filed with the China Patent Office on September 30, 2018, entitled "COMMUNICATION METHOD AND RELATED DEVICE", which is incorporated herein by reference in its entirety.

FIELD OF TECHNOLOGY

[0002] This application relates to the field of communication technologies and, in particular, to a communication method and an associated device.

BACKGROUND OF THE INVENTION

[0003] Due to the constant emergence of various communication services, various communication services have significant differences in network performance requirements. However, no effective solution has been proposed in the industry at present to obtain the working state of the service.

SUMMARY OF THE INVENTION

[0004] This application provides a communication method and an associated device to help obtain an operational state of a service.

[0005] According to a first aspect, an embodiment of this application provides a communication method. The method includes: sending, by means of the policy network element, first query information to the data analysis network element, the first query information being used to obtain quality of service information; and receiving, by the policy network element, the first response information sent by the data analysis network element, the first response information including said quality information that is related to a certain service and which is requested by using the first request information.

[0006] With reference to the first aspect, in an exemplary implementation of the first aspect, the quality of service information includes information that reflects the extent to which the quality of service parameter information for a service satisfies the service requirement.

[0007] With reference to the first aspect, in an exemplary implementation of the first aspect, the first request information includes time information, and the first request information is used to obtain quality of service information corresponding to this time information.

[0008] With reference to the first aspect, in an exemplary implementation of the first aspect, the first request information includes location information, and the first request information is used to obtain quality of service information corresponding to the location information.

[0009] With reference to the first aspect, in an exemplary implementation of the first aspect, the method further includes: adjusting the policy network element of the quality of service parameter information for the service based on the quality of service information; or applying by the network policy element the quality of service parameter information for the service to that service based on the quality of service information.

[0010] With reference to the first aspect, in an exemplary implementation of the first aspect, adjusting by the policy network element the quality of service parameter information for a service based on the quality of service information includes: determining by the policy network element that the quality of service information is below a predetermined condition; and adjusting the quality of service information policy information policy element for the service based on the fact that the quality of service information is below said predetermined condition.

[0011] With reference to the first aspect, in an exemplary implementation of the first aspect, the application by the policy network element of the quality of service parameter information for a service to that service based on the quality of service information includes: determining by the network policy element that the quality of service information is not lower than preset condition; and applying, by the network policy element, the quality of service parameter information for the service to the service based on that the quality of service information is not lower than said predetermined condition.

[0012] With reference to the first aspect, in an exemplary implementation of the first aspect, adjusting by the network policy element the information of quality of service parameters for a service based on the quality of service information includes: sending, by the network policy element, first request information to the network a data analysis element, wherein the first request information is used to request a recommended value of the quality of service parameter information for the service; receiving, by the policy network element, at least one group of recommended values that relates to quality of service parameter information for the service and that is sent by the analytical processing network element; and adjusting, by the policy network element, a quality of service parameter for the service based on at least one group of recommended values of the quality of service parameter information for the service.

[0013] With reference to the first aspect, in an exemplary implementation of the first aspect, the first request information further includes a service quality of service requirement and/or user category information, and the first request information is used to request a recommended value, which is parameter information quality of service for the service and which meets the requirement for quality of service and/or user category information; and each of the at least one group of recommended values of the quality of service parameter information for the service meets the requirement for quality of service and/or user category information.

[0014] With reference to the first aspect, in an exemplary implementation of the first aspect, the quality of service requirement includes a plurality of quality of service requirements.

[0015] With reference to the first aspect, in an exemplary implementation of the first aspect, the quality of service requirement includes a requirement for a range of average service score values.

[0016] With reference to the first aspect, in an exemplary implementation of the first aspect, the user category information includes a plurality of pieces of user category information.

[0017] With reference to the first aspect, in an exemplary implementation of the first aspect, before sending the first request information, the method further includes: determining by the policy network element that the service is in a testing phase.

[0018] With reference to the first aspect, in an exemplary implementation of the first aspect, the first request information further includes first indication information, and the first indication information is used to indicate that the service is in a testing phase.

[0019] With reference to the first aspect, in an exemplary implementation of the first aspect, the method further includes: receiving, by the policy network control element, a second request information sent by a service server, the second request information being used to request provision of a service for the first user; and determining by the policy network element, based on the user category information of said first user and/or the quality of service requirement of said first user with respect to the service, and at least one group of recommended values of the quality of service parameter information for the service, the target quality of service parameter information that relates to to said service and which corresponds to said first user.

[0020] According to a second aspect, an embodiment of this application provides a communication method. The method includes: receiving, by the data analysis network element, a first request information sent by the policy control network element, wherein the first request information is used to obtain quality of service information; and sending, by the data analysis network element, the first response information to the policy control network element, the first response information including the quality of service information that is requested by using the first request information.

[0021] With reference to the second aspect, in an exemplary implementation of the second aspect, the quality of service information includes information that reflects the extent to which the quality of service parameter information for a service satisfies the service requirement.

[0022] With reference to the second aspect, in an exemplary implementation of the second aspect, the method further includes: determining, by the data analytics network element, quality of service information based on the first request information.

[0023] With reference to the second aspect, in an exemplary implementation of the second aspect, the first response information includes time information, and the first response information includes quality of service information corresponding to this time information.

[0024] With reference to the second aspect, in an exemplary implementation of the second aspect, the first response information includes location information, and the first response information includes quality of service information corresponding to the location information.

[0025] With reference to the second aspect, in an exemplary implementation of the second aspect, the method further includes: receiving, by the data analysis network element, a first request information sent by the policy network control element, wherein the first request information is used to request a recommended value of the quality parameter information services for the service; and sending, by the data analysis network element, at least one group of recommended values of the quality of service parameter information for the service to the policy control network element.

[0026] With reference to the second aspect, in an exemplary implementation of the second aspect, the first request information further includes a service quality of service requirement and/or user category information, and the first request information is used to request a recommended value, which is parameter information quality of service for the service and which meets the requirement for quality of service and/or user category information; and each of the at least one group of recommended values of the quality of service parameter information for the service meets the requirement for quality of service and/or user category information.

[0027] With reference to the second aspect, in an exemplary implementation of the second aspect, the method further includes: determining by the data analytics network element at least one group of recommended QoS parameter information values for the service based on the first request information.

[0028] With reference to the second aspect, in an exemplary implementation of the second aspect, the quality of service requirement includes a plurality of quality of service requirements for a service.

[0029] With reference to the second aspect, in an exemplary implementation of the second aspect, the quality of service requirement includes a requirement for a range of average service score values.

[0030] With reference to the second aspect, in an exemplary implementation of the second aspect, the user category information includes a plurality of pieces of user category information.

[0031] With reference to the second aspect, in an exemplary implementation of the second aspect, the first request information further includes first indication information, and the first indication information is used to indicate that the service is in a testing phase.

[0032] According to a third aspect, an embodiment of this application provides a communication method. The method includes: sending, by the policy network element, a quality of service classification request message to the data analytic processing network element, the quality of service classification request message is used to request the quality of service classification information; and receiving, by the policy network element, a quality of service classification response message sent by the data analytics network element, wherein the quality of service classification response message includes quality of service classification information.

[0033] With reference to the third aspect, in an exemplary implementation of the third aspect, the QoS Classification Request message includes time information, and this QoS Classification Request message is used to request QoS classification information that corresponds to said time information.

[0034] With reference to a third aspect, in an exemplary implementation of the third aspect, the QoS Classification Request message includes location information, and the QoS Classification Request message is used to request QoS classification information that corresponds to said location information.

[0035] With reference to a third aspect, in an exemplary implementation of the third aspect, the quality of service classification request message includes a first classification value, and this first classification value is used to indicate to the analytics network element the classification value recommended or expected by the policy network control in regarding the quality of service of a particular service.

[0036] With reference to a third aspect, in an exemplary implementation of the third aspect, the method further includes: sending, by the policy network element, a first request information to a data analysis network element based on the quality of service classification information, the first request information being used to request quality of service parameter information for the service; and receiving, by the policy network element, at least one group of quality of service parameter information for the service that is sent by the analytics network element.

[0037] With reference to a third aspect, in an exemplary implementation of the third aspect, sending the policy network element information of the first request to the data analytic processing network element based on the quality of service classification information includes: generating, by the policy network element, a quality of service requirement based on the information service quality classifications; and sending, by the policy network element, a first request information to the analytics network element, wherein the first request information includes a quality of service requirement, and the first request information is used to request quality of service parameter information that is related to said service and that meets the requirement. on the quality of service.

[0038] With reference to the third aspect, in an possible implementation of the third aspect, the quality of service classification information includes a plurality of pieces of service classification information.

[0039] With reference to a third aspect, in an exemplary implementation of the third aspect, the quality of service classification information includes classifying a range of values of an average score of said service.

[0040] With reference to a third aspect, in an exemplary implementation of the third aspect, before sending the first request information, the method further includes: determining by the policy network element that the service is in a testing phase.

[0041] With reference to the third aspect, in an exemplary implementation of the third aspect, the first request information further includes first indication information, and the first indication information is used to indicate that the service is in a testing phase.

[0042] With reference to a third aspect, in an exemplary implementation of the third aspect, the method further includes: receiving, by the policy network element, second request information sent by the service server, the second request information being used to request provision of a service for the first user; and determining by the policy network element, based on the user category information of said first user and/or the quality of service requirement of said first user with respect to the service, and a recommended value from at least one group of quality of service parameter information for the service, quality of service target parameter information, which refers to said service and which corresponds to said first user.

[0043] According to a fourth aspect, an embodiment of this application provides a communication method. The method includes: receiving, by the analytics network element, a QoS classification request message sent by the policy control network element, using the QoS classification request message to request QoS classification information; and sending, by the data analytics network element, a quality of service classification response message to the policy network element, wherein the quality of service classification response message includes quality of service classification information.

[0044] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the data analytic processing network element determines quality of service classification information based on the quality of service classification request message.

[0045] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the QoS classification response message includes time information, and the QoS classification response message includes QoS-related classification information that corresponds to said time information.

[0046] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the QoS Classification Response message includes location information, and the QoS Classification Response message includes QoS-related classification information that corresponds to said location information.

[0047] With reference to a fourth aspect, in an exemplary implementation of the fourth aspect, the QoS Classification Request message includes a first classification value, and this first classification value is used to indicate to the analytics network element the classification value recommended or expected by the policy network control network element in regarding the quality of service of a particular service.

[0048] With reference to a fourth aspect, in an exemplary implementation of the fourth aspect, the method further includes: receiving, by the data analysis network element, a first request information sent by the policy control network element, the first request information being used to request quality of service parameter information for a service ; and sending, by the analytics network element, at least one group of quality of service parameter information for the service to the policy control network element.

[0049] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the method further includes: determining by the analytics network element at least one group of quality of service parameter information for the service based on the first request information.

[0050] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the first request information includes a quality of service requirement, wherein the quality of service requirement is generated by the policy network element based on the quality of service classification information, and the first request information is used to request the information quality of service parameters, which relates to the service and which meets the requirement for quality of service; and the analytics network element sends to the policy network element at least one group of QoS parameter information that is related to said service and that meets the QoS requirement.

[0051] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the quality of service requirement includes a plurality of quality of service requirements for a service.

[0052] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the quality of service requirement includes a requirement for a range of average service score values.

[0053] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the first request information further includes first indication information, and this first indication information is used to indicate that the service is in a testing phase.

[0054] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the quality of service classification information includes a plurality of pieces of service classification information.

[0055] With reference to the fourth aspect, in an exemplary implementation of the fourth aspect, the quality of service classification information includes classifying a range of values of an average score of said service.

[0056] According to a fifth aspect, an embodiment of this application provides a method for obtaining quality of service parameters. The method includes: sending, by the policy network element, a first request information to the data analysis network element, the first request information includes service identification information, and the first request information is used to request quality of service parameter information for the service; and receiving, by the policy network element, at least one group of quality of service parameter information for the service that is sent by the analytics network element.

[0057] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, the first request information further includes a service quality of service requirement and/or user category information, and the first request information is used to request quality of service parameter information related to service and which meets the requirement for quality of service and/or user category information; and each of the at least one group of quality of service parameter information for the service meets the requirement for quality of service and/or user category information.

[0058] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, before sending the first request information, the method further includes: determining by the policy network element that the service is in a testing phase.

[0059] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, the first request information further includes first indication information, and this first indication information is used to indicate that the service is in a testing phase.

[0060] With reference to a fifth aspect, in an exemplary implementation of the fifth aspect, the method further includes: sending, by the policy network control element, first cancellation information to the data analysis network element after completion of the testing phase, wherein the first cancellation information is used to instruct cancellation of receiving quality of service parameter information that is related to the service and that meets the quality of service requirement and/or user category information.

[0061] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, the quality of service requirement includes a plurality of quality of service requirements for a service.

[0062] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, the user category information includes a plurality of pieces of user category information.

[0063] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, the quality of service requirement includes a requirement for a range of average service score values.

[0064] With reference to a fifth aspect, in an exemplary implementation of the fifth aspect, the method further includes: receiving by the policy network element at least one part of the quality of service information that is sent by the data analysis network element, wherein said at least one part QoS information is in one-to-one correspondence with at least one group of QoS parameter information for a service, and each of said at least one piece of QoS information is used to indicate the extent to which the corresponding QoS parameter of the service satisfies the QoS requirement. .

[0065] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, the method further includes: receiving by the policy network element the second request information sent by the service server, the second request information being used to request provision of a service for the first user; and determining by the policy network element, based on the user category information of said first user and/or the quality of service requirement of said first user with respect to the service, and at least one group of quality of service parameter information for the service, the target quality of service parameter information that relates to said service and which corresponds to said first user.

[0066] With reference to a fifth aspect, in an exemplary implementation of the fifth aspect, determining quality of service target parameter information that is related to said service and that corresponds to said first user includes: determining, based on at least one piece of quality of service information, QoS target information that relates to said service and that corresponds to said first user.

[0067] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, the method further includes: sending, by the policy network element, to the analytics processing network element, QoS target information that is related to said service and that corresponds to said first user.

[0068] With reference to a fifth aspect, in an exemplary implementation of the fifth aspect, the method includes: sending, by the policy network element, to the analytics processing network element, quality of service information that corresponds to quality of service target parameter information that is related to said service and that corresponds to mentioned first user.

[0069] With reference to a fifth aspect, in an exemplary implementation of the fifth aspect, before the policy network element sends the first request information to the data analytics network element, the method further includes: receiving, by the policy network element, the third request information sent by the service server, wherein the third request information is used to request the provision of a service for the second user; and determining, by the policy network element, the quality of service requirement and/or the user category information based on the information of the third request, wherein the quality of service requirement is the quality of service requirement of the second user with respect to said service, and the user category information is the user category information of said own. second user.

[0070] With reference to a fifth aspect, in an exemplary implementation of the fifth aspect, the method further includes: determining, by the policy network element, based on at least one group of quality of service parameter information for said service, quality of service target parameter information that relates to said service and which corresponds to said second user.

[0071] With reference to a fifth aspect, in an exemplary implementation of the fifth aspect, determining quality of service target parameter information that is related to said service and that corresponds to said second user includes: determining, based on at least one piece of quality of service information, QoS target information that relates to said service and that corresponds to said second user.

[0072] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, the method further includes: sending, by the policy network element, to the analytics processing network element, quality of service target information that is related to said service and that corresponds to said second user.

[0073] With reference to the fifth aspect, in an exemplary implementation of the fifth aspect, the method further includes: sending, by the policy network element, to the analytics processing network element, quality of service information that corresponds to quality of service target parameter information that is related to said service and that is matches the mentioned second user.

[0074] According to a sixth aspect, an embodiment of this application provides a method for obtaining quality of service parameters. The method includes: determining, by the data analytics network element, at least one group of information of the quality of service parameters of the service, wherein each of the at least one group of information of the quality of service parameters for the service corresponds to the quality of service requirement for this service and/or information user categories; and sending, by the analytics network element, at least one group of quality of service parameter information for the service to the policy control network element.

[0075] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the method further includes: sending the data analysis network element at least one piece of quality of service information to the policy control network element, each said at least one piece of information quality of service is in one-to-one correspondence with each group of service quality of service parameters information in at least one group of service quality of service parameters information, and each piece of the quality of service information is used to indicate the extent to which the corresponding service quality of service parameter satisfies the requirement for service quality.

[0076] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the quality of service requirement includes a plurality of quality of service requirements for a service.

[0077] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the user category information includes a plurality of pieces of user category information.

[0078] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the quality of service requirement includes a requirement for a range of average service score values.

[0079] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the method further includes: receiving the quality of service requirement and/or user category information from the service server of said service itself by the data analytics network element.

[0080] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the method further includes: receiving, by the analytics network element, the first request information sent by the policy control network element, the first request information including service identification information, the information The first request further includes a quality of service requirement and/or user category information, and this first request information is used to request quality of service parameter information related to said service that corresponds to the quality of service requirement and/or user category information.

[0081] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the method further includes: the first request message includes first indication information, and this first indication information is used to indicate that the service is in a testing phase.

[0082] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, determining by the analytics network element of at least one group of service quality of service parameters information includes: determining by the analytics network element based on historical user level QoS data of said service and historical network data corresponding to the historical quality of service data at the user level of said service, at least one group of quality of service parameter information for the service.

[0083] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the method further includes: receiving, by the data analytics network element, quality of service target parameter information that is sent by the policy network element and which meets the quality of service requirement and/or category information user.

[0084] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the method further includes: receiving, by the analytics network element, quality information that is related to a service and corresponds to quality of service target parameter information that is sent by the policy control network element.

[0085] With reference to the sixth aspect, in an exemplary implementation of the sixth aspect, the method further includes: receiving, by the data analysis network element, the first cancellation information sent by the policy control network element, wherein the first cancellation information is used to cancel the receipt of the quality of service parameter information, which relates to a service and which meets the quality of service requirement of that service and/or user category information.

[0086] According to a seventh aspect, an embodiment of this application provides a method for obtaining quality of service parameters. The method includes: determining, by the data analytics network element, at least one group of QoS parameter information of a certain service, wherein each of the at least one group of QoS parameter information corresponds to a QoS requirement for a given service and/or user category information. .

[0087] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, a service quality requirement for a service includes a plurality of service quality requirements for a given service.

[0088] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, the quality of service requirement for a service includes a requirement for a range of mean score values.

[0089] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, the user category information includes a plurality of pieces of user category information.

[0090] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, the method further includes: receiving the quality of service requirement and/or user category information from the service server of said service itself by the data analytics network element.

[0091] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, determining by the analytics network element of at least one group of service quality of service parameters information includes: determining by the analytics network element based on historical user level quality of service data of said service and historical network data corresponding to the historical quality of service data at the user level of said service, at least one group of quality of service parameter information for the service.

[0092] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, the historical QoS data at the user level of said service includes historical QoS observation data at the user level of said service or historical QoS estimation data at the user level of said service.

[0093] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, the method further includes: obtaining, by the data analytics network element, historical data of a user level quality of service assessment of said service from the first device.

[0094] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, the first device includes an analytical processing network function, NWDAF.

[0095] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, the method further includes: receiving, by the analytics network element, a fourth request sent by a service server of said service itself, the fourth request being used to request provision of a service for a third user; determining, by the analytical processing network element, based on said at least one group of quality of service parameter information, target quality of service parameter information that is related to the service and that corresponds to the third user; and sending, by the data analysis network element, the quality of service target information to the core network element.

[0096] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, the determination by the network element of analytical data processing based on the at least one group of quality of service parameter information of the target quality of service parameter information that is related to the service and that corresponds to the third user includes: itself: receiving, by the data analysis network element, user-level QoS evaluation data that is related to a service and corresponds to a third user and that is sent by the first device; and determining, based on said at least one group of QoS parameter information and user-level QoS evaluation data that is related to the service and which corresponds to the third user, to the QoS target parameter information that is related to said service, and which corresponds to the third user.

[0097] With reference to the seventh aspect, in an exemplary implementation of the seventh aspect, the user level quality of service assessment data that is related to said service and which corresponds to the third user includes a range of user level quality of service values that is obtained by the assessment of the first device and which corresponds to the third user.

[0098] According to an eighth aspect, an embodiment of this application provides a method for obtaining quality of service parameters. The method includes: receiving, by the first network device, historical quality of service monitoring data at the level of a service user from a server of said service; obtaining by the first network device from the network historical network data corresponding to said historical quality of service monitoring data at the user level of said service; and obtaining, by the first network device, user-level quality of service assessment data based on the historical quality of service monitoring data and the historical network data.

[0099] With reference to the eighth aspect, in an exemplary implementation of the eighth aspect, the method further includes: sending, by the first network device, user level quality of service assessment data of said service to the PCF.

[00100] With reference to the eighth aspect, in an exemplary implementation of the eighth aspect, the method further includes: receiving, by the first network device, fifth request information sent by the PCF, wherein the fifth request information is used to request user level quality of service assessment data that relates to to the service and which correspond to the third user; and sending, by the first network device, to the PCF, user-level quality of service evaluation data that is related to said service and that corresponds to the third user.

[0100] With reference to the eighth aspect, in an exemplary implementation of the eighth aspect, the user level quality of service evaluation data that is related to said service and that corresponds to the third user includes a range of user level quality of service values that corresponds to the third user and that received by the evaluation of the first network device.

[0101] According to a ninth aspect, an embodiment of this application provides a network device, wherein the network device includes units configured to implement a method according to any of the first aspect or possible implementations of that first aspect.

[0102] According to a tenth aspect, an embodiment of this application provides a network device, wherein the network device includes units configured to implement a method according to any of the second aspect or possible implementations of this second aspect.

[0103] According to an eleventh aspect, an embodiment of this application provides a network device, the network device including units configured to implement a method according to any of the third aspect or possible implementations of that third aspect.

[0104] According to a twelfth aspect, an embodiment of this application provides a network device, the network device including units configured to implement a method according to any of the fourth aspect or possible implementations of that fourth aspect.

[0105] According to a thirteenth aspect, an embodiment of this application provides a network device, the network device including units configured to implement a method according to any of the fifth aspect or possible implementations of that fifth aspect.

[0106] According to a fourteenth aspect, an embodiment of this application provides a network device, and the network device includes units configured to implement the method according to any of the sixth aspect or possible implementations of this sixth aspect.

[0107] According to a fifteenth aspect, an embodiment of this application provides a network device, the network device including units configured to implement the method according to any of the seventh aspect or possible implementations of this seventh aspect.

[0108] According to a sixteenth aspect, an embodiment of this application provides a network device, the network device including units configured to implement the method according to any of the eighth aspect or possible implementations of this eighth aspect.

[0109] According to a seventeenth aspect, an embodiment of this application provides a storage medium, wherein the storage medium stores an instruction used to implement a method according to any of the first aspect or possible implementations of the first aspect.

[0110] According to an eighteenth aspect, an embodiment of this application provides a storage medium, wherein the storage medium stores an instruction used to implement a method according to any of the second aspect or possible implementations of the second aspect.

[0111] According to a nineteenth aspect, an embodiment of this application provides a storage medium, wherein the storage medium stores an instruction used to implement a method according to any of the third aspect or possible implementations of that third aspect.

[0112] According to a twentieth aspect, an embodiment of this application provides a storage medium, wherein the storage medium stores an instruction used to implement a method according to any of the fourth aspect or possible implementations of that fourth aspect.

[0113] According to a twenty-first aspect, an embodiment of this application provides a storage medium, wherein the storage medium stores an instruction used to implement a method according to any of the fifth aspect or possible implementations of the fifth aspect.

[0114] According to a twenty-second aspect, an embodiment of this application provides a storage medium, wherein the storage medium stores an instruction used to implement a method according to any of the sixth aspect or possible implementations of that sixth aspect.

[0115] According to a twenty-third aspect, an embodiment of this application provides a storage medium, wherein the storage medium stores an instruction used to implement a method according to any of the seventh aspect or possible implementations of the seventh aspect.

[0116] According to a twenty-fourth aspect, an embodiment of this application provides a storage medium, wherein the storage medium stores an instruction used to implement a method according to any of the eighth aspect or possible implementations of the eighth aspect.

[0117] According to a twenty-fifth aspect, this application provides a computer program product including an instruction. When this computer program product is run on a computer, that computer is enabled to execute the method according to any of the first aspect or possible implementations of this first aspect.

[0118] According to a twenty-sixth aspect, this application provides a computer program product including an instruction. When this computer program product is run on a computer, that computer is enabled to execute the method according to any of the second aspect or possible implementations of this second aspect.

[0119] According to a twenty-seventh aspect, this application provides a computer program product including an instruction. When this computer program product is run on a computer, that computer is enabled to execute the method according to any of the third aspect or possible implementations of this third aspect.

[0120] According to a twenty-eighth aspect, this application provides a computer program product including an instruction. When this computer program product is run on a computer, that computer is enabled to execute the method according to any of the fourth aspect or possible implementations of this fourth aspect.

[0121] According to a twenty-ninth aspect, this application provides a computer program product including an instruction. When this computer program product is run on a computer, that computer is enabled to execute the method according to any of the fifth aspect or possible implementations of this fifth aspect.

[0122] According to a thirtieth aspect, this application provides a computer program product including an instruction. When this computer program product is run on a computer, that computer is enabled to execute the method according to any of the sixth aspect or possible implementations of this sixth aspect.

[0123] According to a thirty-first aspect, this application provides a computer program product including an instruction. When this computer program product is run on a computer, that computer is enabled to execute the method according to any of the seventh aspect or possible implementations of this seventh aspect.

[0124] According to a thirty-second aspect, this application provides a computer program product including an instruction. When this computer program product is run on a computer, that computer is enabled to execute the method according to any of the eighth aspect or possible implementations of this eighth aspect.

[0125] According to a thirty-third aspect, this application provides a chip, and the chip is configured to perform a method according to any of the first aspect or possible implementations of this first aspect.

[0126] According to a thirty-fourth aspect, this application provides a chip, and the chip is configured to perform a method according to any of the second aspect or possible implementations of this second aspect.

[0127] According to a thirty-fifth aspect, this application provides a chip, and the chip is configured to perform a method according to any of the third aspect or possible implementations of this third aspect.

[0128] According to a thirty-sixth aspect, this application provides a chip, and the chip is configured to perform a method according to any of the fourth aspect or possible implementations of this fourth aspect.

[0129] According to a thirty-seventh aspect, this application provides a chip, and the chip is configured to perform a method according to any of the fifth aspect or possible implementations of this fifth aspect.

[0130] According to a thirty-eighth aspect, this application provides a chip, and the chip is configured to perform a method according to any of the sixth aspect or possible implementations of this sixth aspect.

[0131] According to a thirty-ninth aspect, this application provides a chip, and the chip is configured to perform a method according to any of the seventh aspect or possible implementations of this seventh aspect.

[0132] According to the fortieth aspect, this application provides a chip, and the chip is configured to perform a method according to any of the eighth aspect or possible implementations of this eighth aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

[0133] FIG. 1 is a schematic architectural representation of a communication system according to an embodiment of this application;

[0134] FIG. 2 is a schematic flow diagram of a method for obtaining quality of service parameters according to an embodiment of this application;

[0135] FIG. 3 is a schematic flow diagram of another method for obtaining quality of service parameters according to an embodiment of this application;

[0136] FIG. 4 is a schematic flow diagram of another method for obtaining quality of service parameters according to an embodiment of this application;

[0137] FIG. 5 is a schematic flow diagram of another method for obtaining quality of service parameters according to an embodiment of this application;

[0138] FIG. 6 is a schematic flow diagram of another method for obtaining quality of service parameters according to an embodiment of this application;

[0139] FIG. 7 is a schematic representation of a process flow for obtaining a quality of service classification according to an embodiment of this application;

[0140] FIG. 8 is a structural block representation of a network device according to an embodiment of this application;

[0141] FIG. 9 is a structural block representation of a network device according to an embodiment of this application;

[0142] FIG. 10 is a structural block representation of a network device according to an embodiment of this application;

[0143] FIG. 11 is a structural block representation of a network device according to an embodiment of this application;

[0144] FIG. 12 is a structural block representation of a server according to an embodiment of this application; and

[0145] FIG. 13 is a structural block representation of a server according to the embodiment of this application.

DESCRIPTION OF EMBODIMENTS

[0146] Technical solutions according to this application are described below with reference to the accompanying drawings.

[0147] In this application, "at least one" means one or more, "multiple" means two or more, and "and/or" means an associative relationship to describe related objects and represents that three relationships can exist. For example, A and/or B could represent the following three cases: Only A exists, both A and B exist, and only B exists. A and B can be singular or plural. The symbol "/" usually indicates the relationship "or" between related objects, and the expression "at least one of the following" or a similar expression means any combination of such elements, including any combination of individual elements (parts) or multiple elements (parts) . For example, at least one of a, b, or c may indicate: a, b, c, a-b, a-c, b-c, or a-b-c, with a, b, and c being singular or plural. In addition, in the embodiments of this application, words such as "first" and "second" do not limit the scope and sequence of execution.

[0148] It should be noted that in this application, words such as "example" or "for example" are used to represent an example, illustration, or description. Any embodiment or design scheme that is described as "example" or "for example" in this application should not be interpreted as more preferred (preferred) or having (having) more advantages than another embodiment or design scheme. The use of words such as "example" or "for example" is intended to represent a relative concept in a certain way.

[0149] The technical solutions in the embodiments of this application can be applied to a 5th generation system (5th generation, 5G), a new radio communication system (new radio, NR), a future communication network, or the like.

[0150] To facilitate understanding of the embodiments of this application, some technical terms in these embodiments of this application are first described.

[0151] The slice network described in the embodiments of this application may be one of a network slice, a network slice instance, and a network slice subnetwork instance.

[0152] Network slice (network slice, NS) can also be called a slice (segment) for short. Network slices are different logical networks individually configured on a physical or virtual network infrastructure depending on the service requirements of different tenants. A network slice may be a complete end-to-end network that includes a terminal device, an access network, a transmission network, a core network, and a service server, or may include only a core network and be assisted by a terminal device, an access network, a transmission network, and a server. services. The network slice can provide a complete communication service and has a network capability. A network slice may be a communication resource to ensure that a bearer service or some service can meet the requirement of a service level agreement, or may be considered a combination of a network function and a communication resource that is required to perform a communication service or some communication services. A network slice is identified by using single network slice selection assistance information (S-NSSAI). S-NSSAI includes a slice/service type (SST) and a slice differentiator (SD). SST and SD may be defined in the standard or defined by the operator. SD is additional information for padding SST to distinguish between multiple network slices having the same SST. For example, SD can be used to represent the home interconnection of a network slice.

[0153] A network slice instance (NSI) may also be referred to as a slice instance network, is a specific network instance created by an operator on an infrastructure based on a network slice template, and is formed by integrating various network function objects and physical resources. Different network slice instances are logically isolated from each other. One network slice can be instantiated into one or more NSIs, and each NSI is identified using a network slice instance identifier (NSI ID). In other words, one part of the S-NSSAI corresponds to one or more NSI IDs.

[0154] A network slice subnet instance (NSSI) may also be referred to as a slice subnet instance network and includes a set of network function network elements and resources organized and configured for these network function elements to form a local logical network. The network slice subnet instance is introduced primarily to facilitate administration of the network slice instance. For example, a network slice is divided into two instances of a network slice subnet based on a core network element and an access network element to respectively organize and configure a core network resource and an access network resource to facilitate administration.

[0155] A service level agreement (SLA) is an agreement between a service provider and a service provider's customer, and is used to record the application service provided by the service provider and determine the performance criteria that the service provider must meet. The SLA can set the customer's expectation of the service provider in terms of performance and quality. An SLA can include a number of qualitative or quantitative rules such as availability, performance baseline, reliability, and response time.

[0156] A tenant is a customer that leases a carrier's network and provides one or more services to a tenant user using that network. The tenant may be a vertical tenant, an OTT tenant, or another third-party tenant. In addition, the operator network leased by the tenant may be a network slice, a slice network instance in a slice network, a slice network subnet instance, or another type of network. In the embodiments of the present application, this is not particularly limited.

[0157] FIG. 1 is a schematic architectural representation of a communication system according to an embodiment of this application. The communication system includes an analytics network element, a policy control network element, an Application Function (AF) network element (also referred to as a service server), a core network element, an access network element (Radio Access Network, RAN or AN), a terminal device and a Network Exposure Function (NEF) network element. The analytics network element may be a Network Data Analytic Function (NWDAF) network element, the policy control network element may be a Policy Control Function (PCF) network element, and the core network element may include an SMF network element, an AMF network element, and a User plane Function (UPF) network element. The terminal device may be a User Equipment (UE).

[0158] The NWDAF network element can be deployed within the core network, in other words, the NWDAF is also a core network element. Alternatively, the NWDAF network element may not be deployed within the core network. In this embodiment of the present application, this is not particularly limited. In addition, the NWDAF may communicate directly through the service interface with the network element with which the NWDAF needs to communicate. For example, a network intelligence processor may communicate through a service interface with network elements such as PCF, SMF, AMF, UPF, NRF, and RAN, invoking various service interface services.

[0159] It can be understood that in the communication system shown in FIG. 1, the functions and interfaces of network elements are examples only. When network elements are used in the embodiments of this application, not all functions are necessary. In addition, in this application, network elements can communicate with each other based on a point-to-point interface. For example, the NWDAF connects to the PCF NE through the N23 interface. The PCF connects to the AF NE through the N5 interface, connects to the SMF NE through the N7 interface, and connects to the AMF NE through the N15 interface. The PCF can generate a dynamic QoS policy and distribute the appropriate policies to network elements such as SMFs and AMFs. The UPF connects to the SMF network element through the N4 interface and connects to the RAN network element through the N3 interface. The AN connects to the AMF NE through the N2 interface. The UE connects to the AMF network element through the N1 interface. FIG. 1 shows only some of the above interfaces.

[0160] The terminal device includes, but is not limited to: user equipment (user equipment, UE), subscriber unit, subscriber station, mobile station, remote station, remote terminal device, mobile terminal device, user terminal device, wireless communication device, user agent, user device, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), portable device with wireless communication function, computing device, processing device connected to a wireless modem, vehicle-mounted device, wearable device, IoT terminal device, household appliance, virtual reality device, future 5G network terminal device, etc. a terminal device in a future developed public land mobile network (PLMN) and the like.

[0161] An application function network element is a server side providing some type of service to a user, and therefore may also be referred to as an application server or a service server.

[0162] An access network element may be a network element that communicates with a terminal device. An access network element may provide coverage for communications in a particular geographic area and may communicate with a terminal device in a coverage area (cell). The access network element may communicate with any number of terminal devices. There may be multiple air interface connections between the access network element and the terminal device. For example, there are two air interface connections between the access network element and the terminal device, and these two air interface connections are used to transmit data stream A and data stream B, respectively. The access network element may support communication protocols of different standards, or may support different communication modes. For example, an access network element can be a 5G base station, a next generation node B (gNB), an evolved node B (evolved nodeB, eNodeB), a wireless access point (wireless fidelity access point, Wi-Fi AP), a base station using broadband access technology in the microwave range (worldwide interoperability for microwave access base station, WiMAX BS) or a radio controller in a cloud radio access network (CRAN). Alternatively, the network device may be an access network device in a future evolved PLMN or the like.

[0163] The PCF network element has a policy control decision function and provides policy to the network. The AMF network element is used for mobility management, lawful interception, access authorization, authentication, and the like. The SMF network element is configured to implement bearer and session administration, address allocation, and the like. The user plane function network element is used for functions such as routing and forwarding, threshold control, traffic monitoring, and user plane data verification. The network element of the network repository function is configured to provide a service discovery function or network element discovery, as well as a function of maintaining the operation of the network element and the service supported by this network element. The transmission network element has a network data transmission function. For example, the transmission network element may be a router.

[0164] The NWDAF has analytical and statistical data processing functions and can be configured to collect and analyze related data from a network element, a third-party service server, a terminal device, or a network management system, and provide a data analysis result to a network element, a third-party service server , terminal device or network administration system based on associated data. The result of the analysis can help the network in choosing the QoS parameter of the service, performing traffic routing, choosing the background traffic transfer policy, and so on. In embodiments of this application, the data analytics device may be further configured to provide a network analysis result (e.g., network slice or network slice instance) for the network to perform network deployment (e.g., network slice or network slice instance) or configure network resources. based on this analysis result.

[0165] The network element of the network capability discovery function, NEF, has the function of providing or exposing the operator's network function to an external server or external device, and serves as an intermediate medium for internal and external network communication. For example, when an untrusted third-party service server needs to communicate with the inside of the network, the network element of the network capability discovery function needs to perform processing and forwarding operations. Specifically, when an intra-network service server or a trusted third-party service server communicates with the inner network, the network element of the network capability discovery function may not be required.

[0166] In embodiments of this application, the access network device and all or some of the network elements in the core network may belong to a 3rd generation partnership project (3GPP) network or may belong to a non-3GPP network, for example, a corporate intranet. All or some of the network elements in the core network may be physical network elements or may be virtualized network elements. In this document, this is not a limitation.

[0167] An analytical processing network element in this application is a network element that can provide an analytical processing function. The data analysis function in this application may be deployed in a network data analysis function (NWDAF) network element or may be deployed in another network element. In other words, the analytic data processing network element in this application may include, but is not limited to, NWDAF. The analytic processing network element may be a network element which is located in the control plane of the core network and which has the data analytic processing function of this application, or may be a network element which is located in the network administration plane and which has the data analytic processing function of this application. .

[0168] The policy control network element of this application is a network element that can provide a policy control function. The policy control function in this application may be deployed in a Policy Control Function (PCF) network element or may be deployed in another network element. In other words, the network policy control element in this application may include, but is not limited to, PCF.

[0169] In addition, the function of analytical data processing and another function can be combined and deployed in the same network element. For example, a data analytics function and a policy management function may be deployed together. In this case, the data analytics network element and the policy control network element are physically the same entity.

[0170] In addition, the quality of service described in the embodiments of this application may also be referred to as service experience.

[0171] FIG. 2 is a schematic flow diagram of a method for obtaining quality of service parameters according to an embodiment of this application.

[0172] 201. The policy control network element sends first request information to the data analytic network element, the first request information includes service identification information, and this first request information is used to request quality of service parameter information for the service. Accordingly, the data analysis network element receives the first request information sent by the policy control network element.

[0173] In some embodiments, the first request information further includes a quality of service requirement for the service and/or user category information. In this case, the first request information is used to request quality of service parameter information that is related to a service and that meets the quality of service requirement and/or user category information. The service identification information is used to uniquely identify the service. The service identification information may specifically be an identifier corresponding to a service, a service type, or a service name. For example, in some embodiments, different services may correspond to different identifiers. For example, the voice service identifier may be identifier 1, the data service identifier may be identifier 2, and the video service identifier may be identifier 3. In this case, the service identification information may be a service identifier. In another example, in some embodiments, the service identification information may alternatively be a specific service type. For example, the service identification may be a voice service type, the service identification may be a data service type, or the service identification may be a video service type.

[0174] Unless otherwise indicated, the quality of service requirement in this embodiment of this application is a user-level quality of service requirement. The user-level quality of service requirement may be equivalent to the individual user's quality of service requirement, and more specifically, the individual user's experience requirement for the service. For example, a QoS requirement of 5>MOS>4.5 means that an individual user's MOS is greater than 4.5 and less than 5.

[0175] In some embodiments, the quality of service requirement may include a single quality of service requirement for a service. In some other embodiments, the QoS requirement may include a plurality of QoS requirements for a service.

[0176] In some embodiments, the user category information may include one piece of user category information. In other embodiments, the user category information may include a plurality of pieces of user category information. Typically, one piece of user category information corresponds to one quality of service requirement, and many different user categories correspond to many different quality of service requirements.

[0177] In some embodiments, the first request information includes service identification information and a quality of service requirement. In this case, the first request information is used to request quality of service parameter information that is related to the service and that meets the quality of service requirement.

[0178] Optionally, in some embodiments, the quality of service requirement includes a requirement for a range of average service scores.

[0179] For example, Table 1 shows an example of the first request information. It can be understood that although the first request information shown in Table 1 includes three quality of service requirements, the possibility that the first request information includes only one quality of service requirement is not excluded from this application.

Table 1

Service identification information Service quality requirement Voice service 5>MOS>4.5 4.5>MOS>4 4>MOS>3

[0180] The service indicated by the service identification information that is included in the first request information shown in Table 1 is a voice service. The first request information includes three quality of service requirements for the voice service. The three quality of service requirements shown in Table 1, respectively, are that the mean opinion score (MOS) be greater than 3 and less than 4, MOS greater than 4 and less than 4.5, and MOS greater than 4 ,5 and less than 5. It can be understood that the requirement for a specific value for MOS in this document is an example of an individual user's QoS requirement for a voice service. It can be understood that the quality of service requirement shown in Table 1 is a requirement for a range of average service scores.

[0181] In some other embodiments, the quality of service requirement may alternatively be another requirement, such as a call completion rate requirement, a successful payment rate requirement, a data packet loss rate requirement, or an average data packet transmission delay requirement.

[0182] In this application, the quality of service of an individual user is data for evaluating the service experience of an individual user. Accordingly, the requirement for the quality of service of an individual user is the requirement for data to evaluate the service experience of each user. The specific way in which each user's service experience is evaluated may be determined by the service provider. For example, the voice service server determines that the voice service quality for an individual user should be evaluated using MOS. The range of MOS values is [0, 5], and a higher MOS indicates a better user experience with the voice service. In this case, the quality of service requirement for the voice service may be the MOS value requirement. How each user's MOS is calculated is an internal calculation method and is outside the scope of this patent. For the video service, the video service server determines that each user's experience of the video service should be evaluated using a video mean opinion score (vMOS), and the calculation methods for MOS and vMOS are different. In this case, the quality of service requirement for the video service may be a vMOS value requirement. In this document, individual user quality of service assessment using MOS and vMOS is described with only two examples for voice service and video service. For another type of service, there are many other ways to evaluate the quality of service of an individual user. For example, for a data service, the QoS of an individual user in that data service can be comprehensively evaluated using parameters such as the data packet loss ratio and the average data packet transmission delay. In this case, the quality of service requirement for the data service may be a comprehensive multi-parameter requirement. It is not limited in this patent.

[0183] In some embodiments, the first request information includes service identification information and user category information. In this case, the first request information is used to request the quality of service parameter information that is related to the service and that corresponds to the user category information.

[0184] For example, Table 2 shows an example of the first request information. It can be understood that although the first request information shown in Table 2 includes a plurality of pieces of user category information, the possibility that the first request information includes only one piece of user category information is not excluded from this application.

table 2

Service identification information User category Voice service Gold user Silver user bronze user

[0185] The service indicated by the service identification information that is included in the first request information shown in Table 2 is a voice service. The first request information includes three pieces of user category information, which are gold user, silver user, and bronze user, respectively.

[0186] A gold user, a silver user, and a bronze user are examples for designating categories of users. Alternatively, the categories of users may be classified in other ways, such as classified into a high priority user, a medium priority user, and a low priority user. That is, the user category information may alternatively be user priority information. How the user category classification is performed is not limited in this embodiment of this application.

[0187] In some embodiments, the implementation of the information of the first request may further include the identifier of the network of slices in which the service is located. The slice network identifier can be single network slice selection assistance information (S-NSSAI), network slice instance identifier (NSI ID), network slice subnet instance identifier , NSSI ID) or the like.

[0188] In some embodiments, the quality of service requirement may be a quality of service requirement corresponding to one or more pieces of time information. More specifically, the first request information may be used to request quality of service parameter information that is for one or more pieces of time information and that is related to a service and meets a requirement for quality of service and/or user category information. In this scenario, the first request information may further include one or more pieces of time information. The specific form of the time information is not limited in this embodiment of this application, as long as the time information can reflect time. For example, time information may be divided by hour. For example, the first time information is from 8:00 to 10:00, and the second time information is from 10:00 to 12:00. In another example, the time information may alternatively be divided by day. For example, the first time information is from the first to the tenth day of each month, and the second time information is from the eleventh to the twentieth day of each month. In another example, the time information may alternatively be divided into time intervals after power-on by the user. For example, the first time information is from zero to the fourth hour after the power is turned on, and the second time information is from the fourth to the eighth hour after the power is turned on. Table 3 shows an example of the first request information.

Table 3

Service identification information Time Information Service quality requirement Voice service Time information 1 5>MOS>4.5 4.5>MOS>4 4>MOS>3 Time information 2 5>MOS>4 4>MOS>3.5 3.5>MOS>3

[0189] The service indicated by the service identification information that is included in the first request information shown in Table 3 is a voice service. The first request information includes three quality of service requirements for the voice service at different times. As shown in Table 3, when the time information is time information 1, the three quality of service requirements are respectively that the mean opinion score (MOS) of the service is greater than 3 and less than 4, the MOS is greater than 4 and less than 4 ,5, and MOS was greater than 4.5 and less than 5; when the time information is time information 2, the three quality of service requirements are respectively that MOS is greater than 3 and less than 3.5, MOS is greater than 3.5 and less than 4, and MOS is greater than 4 and less than 5. It can be understood that the requirement for a specific value for MOS in this document is an example of an individual user's QoS requirement for a voice service.

[0190] In some embodiments, the quality of service requirement may be a quality of service requirement for one or more pieces of site information. More specifically, the first request information may be used to request quality of service parameter information that is for one or more pieces of site information and that is related to a service and meets a requirement for quality of service and/or user category information. In this scenario, the first request information may further include one or more pieces of location information. The location information may be location information, such as serving cell A or registration area B, which is defined in the 3GPP communication network. Alternatively, the location information may be location information defined in a non-3GPP communication network. For example, the location information is a range of a specific geographic location (eg, latitude and longitude location information or GPS location information). Table 4 shows an example of the first request.

Table 4

Service identification information Location Information Service quality requirement Voice service Region 1 5>MOS>4.5 4.5>MOS>4 4>MOS>3 Region 2 5>MOS>4 4>MOS>3.5 3.5>MOS>3

[0191] The service indicated by the service identification information that is included in the first request information shown in Table 4 is a voice service. The first request information includes three quality of service requirements for the voice service at different locations. As shown in Table 4, when the location information is area 1, the three quality of service requirements are respectively that the mean opinion score (MOS) of the service is greater than 3 and less than 4, the MOS is greater than 4 and less than 4, 5, and MOS was greater than 4.5 and less than 5; when the location information is area 2, the three quality of service requirements are respectively that MOS is greater than 3 and less than 3.5, MOS is greater than 3.5 and less than 4, and MOS is greater than 4 and less than 5. It can be understood that the requirement for a specific value for MOS in this document is an example of an individual user's QoS requirement for a voice service.

[0192] In some embodiments, the user category information may be in one-to-one correspondence with the quality of service requirement. One piece of user category information corresponds to one quality of service requirement, and a plurality of user categories respectively correspond to a plurality of quality of service requirements.

[0193] In some embodiments, the first request information may include service identification information, quality of service requirement, and user category information. In this case, the first request information is used to request quality of service parameter information that is related to a service and that meets the quality of service requirement and user category information.

[0194] As described above, the quality of service requirement may include a plurality of quality of service requirements for a service, and the user category information may also include a plurality of pieces of user category information. A plurality of quality of service requirements may be in one-to-one correspondence with a plurality of pieces of user category information.

[0195] For example, Table 5 shows an example of the first request information. It can be understood that although the first request information shown in Table 5 includes a plurality of quality of service requirements and a plurality of pieces of user category information, the possibility that the first request information includes only one quality of service requirement and one piece of category information user, is not excluded from this application.

Table 5

Service identification information User category Service quality requirement Voice service Gold user 5>MOS>4.5 Silver user 4.5>MOS>4 bronze user 4>MOS>3

[0196] The service indicated by the service identification information that is included in the first request information shown in Table 5 is a voice service. The first request information further includes three categories of user, which are gold user, silver user, and bronze user, respectively. The first request information includes three quality of service requirements for the voice service. The three quality of service requirements shown in Table 5 are respectively MOS greater than 3 and less than 4, MOS greater than 4 and less than 4.5, and MOS greater than 4.5 and less than 5. The three categories of user in Table 5 are in one-to-one correspondence with the three quality of service requirements. In particular, the quality of service requirement corresponding to the gold user is that the MOS is greater than 4.5 and less than 5, the quality of service requirement corresponding to the silver user is that the MOS is greater than 4 and less than 4.5 , and the quality of service requirement corresponding to a bronze user is that the MOS be greater than 3 and less than 4.

[0197] In this application, quality of service parameter information that is related to a service and that meets the quality of service requirement means that the quality of service parameter information can satisfy the quality of service requirement. In particular, when a quality of service parameter is allocated to an individual user's service flow, the quality of service of that individual user can satisfy the quality of service requirement. For example, assuming that the quality of service parameter information of a voice service includes guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), and latency, the quality of service parameter information corresponding to MOS>3, maybe: GFBR>300Mbps, MFBR>500Mbps and latency<2ms.

[0198] For example, in some embodiments, different categories of users meet different quality of service requirements. The policy network element may store a correspondence between the quality of service requirement and the user category. Using Table 5 as an example, the correspondence that exists between the QoS requirement and the user category, which is stored by the Policy Network Element, can be the following: The QoS requirement corresponding to a golden user is that the MOS be greater than 4, 5 and less than 5, the silver user's quality of service requirement is that the MOS be greater than 4 and less than 4.5, and the bronze user's quality of service requirement is that the MOS be greater than 3 and less 4. In a procedure in which each user executes a certain service, the policy network element may first determine the user category of that user, and then determine the corresponding quality of service requirement based on the user category of that user. In another example, in some embodiments, the network policy control may not classify users into different user categories. In a procedure in which each user enforces a specific service, the policy network element can directly determine the specific quality of service requirement of that user.

[0199] In a procedure in which one user executes a particular service, the network policy control element requests that each network device allocate a network resource based on the quality of service parameter information that is related to that service and that meets the quality of service requirement of that user, so that the corresponding user quality of service can satisfy the user's quality of service requirement. The specific way that the network policy control element requests each network device to allocate a network resource based on the quality of service parameter may be as follows: the network policy control element directly or indirectly delivers the quality of service policy to each network device. The QoS policy includes a QoS setting. For example, the PCF may add parameters such as GFBR>300 Mbps, MFBR>500 Mbps, and latency<2 ms to a QoS profile and deliver this QoS profile to the base station using SMF, so that the base station allocates the appropriate air interface resource based on the mentioned parameters: GFBR>300 Mbps, MFBR>500 Mbps and delay<2 ms.

[0200] In some embodiments, the first request information may be real-time request information. More specifically, after the policy control network element sends the first request information to the data analysis network element, the data analysis network element immediately returns the content requested using the first request information.

[0201] In some other embodiments, the first request information may be subscription request information. Specifically, after the policy network element sends the first request information to the analytics network element, the analytics network element does not need to immediately send to the policy network element the content requested using the first request information, but it sends to the network to the policy control, the content requested using the first request information after waiting for the subscription event to occur or the subscription condition to be met.

[0202] Optionally, in some embodiments, prior to step 201, the network policy control element may further determine that the service is in a test state. In other words, the policy control network element receives the quality of service parameter information for a certain service from the data analysis network element only in the test phase of this service, and performs, in this phase, policy control and resource allocation for this service based on the quality of service parameter information recommended network element of analytical data processing. After the test is completed and the service enters the stable phase, the policy network element no longer needs to obtain the quality of service parameter information recommended by the data analytics network element. The network policy control element may learn from the slice network manager whether the service is in a test state, or it may learn whether the service is in a test state directly from the service tenant or the service server. The slice network manager may be a network slice selection function (NSSF) network element, a Network Slice Management Function (NSMF) network element, a network repository function (NRF) network element, or another network element that has the functions of managing and administering a network of slices.

[0203] Optionally, in some embodiments, the first request information may further include first indication information, and this first indication information is used to indicate that the service is in a testing phase.

[0204] Optionally, in some embodiments, the first indication information may alternatively be sent to the analytic processing network element as separate information. In other words, the policy control network element may separately send the first request information and the first indication information to the analytical processing network element.

[0205] Optionally, in some embodiments, the policy control network element sends the first cancellation information to the analytical processing network element after completion of the testing phase, wherein the first cancellation information is used to instruct the cancellation of obtaining the quality of service parameter information that is related to the service and that meets the requirement for quality of service and/or user category information. In other words, the policy control network element receives the quality of service parameter information for a certain service from the data analysis network element only in the test phase of this service, and performs, in this phase, policy control and resource allocation for this service based on the quality of service parameter information recommended network element of analytical data processing. After the test is completed and the service enters the stable phase, the policy network element no longer needs to obtain the quality of service parameter information recommended by the data analytics network element. The network policy control element may learn from the slice network manager whether the service has been tested, or it may know whether the service has been tested directly from the service tenant or service server. The slice network manager may be a network slice selection function (NSSF) network element, a Network Slice Management Function (NSMF) network element, a network repository function (NRF) network element, or another network element that has the functions of managing and administering a network of slices. In addition, the network policy control element can independently determine whether the service has been tested. For example, the network policy control element may determine whether a service has been tested depending on whether the quality information that is related to the service and that corresponds to the received quality of service parameter information exceeds a predetermined value. To know the specific meaning of the quality of service information, refer to step 203.

[0206] Optionally, in some embodiments, the first cancel information may further include second indication information, and this second indication information is used to indicate that the testing phase has already been completed.

[0207] Similarly, the second indication information may alternatively be sent to the analytic processing network element as separate information. In other words, the policy control network element may separately send the first cancellation information and the second indication information to the analytical processing network element.

[0208] Optionally, in some embodiments, upon receiving the first cancel information, the data analysis network element may determine that the testing phase has already been completed. In other words, the first cancellation information may also be used to indicate that the testing phase has already been completed.

[0209] Optionally, in some embodiments, upon receiving the first cancel information, the analytics network element has determined at least one group of QoS parameter information for the service based on the first request information, but does not send the at least one group of QoS parameter information for said service to the network policy control element. In this case, the analytics network element may not send the at least one group of QoS parameter information for a certain service to the policy control network element.

[0210] Optionally, in some embodiments, when receiving the first cancel information, the data analytics network element has not completed the process of determining at least one group of quality of service parameter information for a service. In this case, the analytics network element may stop determining at least one group of quality of service parameter information for that service.

[0211] Optionally, in some embodiments, before receiving the first cancellation information, the analytics network element sent at least one group of quality of service parameter information for the service to the policy control network element. If the network policy control element has determined upon receiving at least one group of service quality parameter information that the test phase is completed, the network policy control element may ignore the at least one group of service quality parameter information for the service. For example, the network policy control element may directly remove the received at least one group of quality of service parameter information for a service.

[0212] 202. The data analytics network element determines at least one group of quality of service parameter information for a service.

[0213] In some embodiments, an analytics network element may determine at least one group of QoS parameter information for a service based on the first request information.

[0214] In some embodiments, each of the at least one group of quality of service parameter information for a service corresponds to a requirement for quality of service and/or user category information.

[0215] The quality of service parameter information is various resource parameters or performance status parameters allocated by the network to an individual user in the process of one service. For example, the QoS parameters of the 5G quality of service (QoS) flow, which are defined in the existing standard, such as GFBR, MFBR, 5G QoS class identifier (5QI), allocation and retention priority (allocation and retention priority (ARP), average window size, and Maximum Packet Loss Rate (UL, DL, UL/DL MaxPLR) are quality of service parameters. However, the quality of service parameter in this application may alternatively be a new parameter that is not defined but affects the service experience, e.g. jitter buffer size, TCP congestion window size, TCP receive window size, media encoding type, encoding rate, buffer size base station or radio access type (RAT). In addition, the new parameter may be a normalized parameter, and this normalized parameter is obtained by mapping the physical value of the parameter into a space of fixed values.

[0216] For a particular service, the data analytics network element derives a user-level service experience model of that service by analyzing a large amount of collected user-level QoS data and flow-level network data. Service experience can reflect the quality of service. Therefore, the quality of service described in this embodiment of this application may also be referred to as service experience. For example, the service experience model may also be referred to as a service quality model, and the service quality data may also be referred to as service experience data. The user-level service experience model refers to the variant relationship between user-level QoS data of a particular service and associated flow-level network data. The user-level quality of service data is the quality of service data at the service flow level of an individual user, that is, the quality data generated by one user in the process of one service. The quality data generated by the various users in the service processes constitutes a set of user-level quality of service data collected by the data analytics network element. Flow-level network data is flow-level network data (5G network flow is a QoS flow) associated with user-level QoS data. For example, network data at the flow level are various resource parameters or status parameters (for example, 5G QoS flow QoS parameters that are defined in the existing standard, such as GFBR, MFBR, QCI and average window size, or a new parameter that is not defined, but affects the quality of service) allocated by the network to one user in the process of one service. The data analytics network element may collect a large number of resource parameters or status parameters allocated by the network to different users in service processes to generate network data at the flow level.

[0217] The data analytics network element can obtain a user-level service experience model by performing the following two steps.

[0218] A: The data analytics network element receives training data for a specific service, wherein the training data may include user-level historical QoS data for said service and flow-level historical network data corresponding to said service-level historical QoS data. user level.

[0219] For example, the data analytics network element first separately collects data from the service server (eg, AF), access network element (eg, RAN), user plane function network element (eg, UPF), terminal device (eg, UE) , a mobility management function network element (eg, AMF), a session management function network element (eg, SMF), a policy management function network element (eg, PCF), a network administration system, and the like, and then associates the data of these network elements using such information such as service identification information, service flow ID, terminal ID, session ID in which the service flow resides, user association ID existing in each network element, time and location, to obtain complete training data. The training data includes the following content:

[0220] (1). Specific Service User Level Historical Quality of Service: The User Level Historical Quality of Service comes from an AF or other network element that may provide quality of service data, and may be, for example, historical MOS data at the voice service user level.

[0221] In some embodiments, the implementation of the historical quality of service at the user level may be the historical quality of service in the area of a certain place. In other words, the historical quality of service may include the historical quality of service corresponding to the information of various places. The specific form of the place information in this embodiment of this application is not limited. The location information may be location information, such as serving cell A or registration area B, which is defined in the 3GPP communication network. Alternatively, the location information may be location information defined in a non-3GPP communication network. For example, the location information is a range of a particular geographic location (eg, latitude and longitude location information or GPS location information). For example, the historical quality of service may include the historical quality of service in region 1 and the historical quality of service in region 2. Thus, the resulting service experience model may be a service experience model that includes information from various locations.

[0222] In some embodiments, the historical quality of service may be a historical quality of service in the time domain. In other words, the historical quality of service may include the historical quality of service corresponding to different time information. The specific form of the time information is not limited in this embodiment of this application, as long as the time information can reflect time. For example, time information may be divided by hour. For example, the first time information is from 8:00 to 10:00, and the second time information is from 10:00 to 12:00. In another example, the time information may alternatively be divided by day. For example, the first time information is from the first to the tenth day of each month, and the second time information is from the eleventh to the twentieth day of each month. In another example, the time information may alternatively be divided into time intervals after power-on by the user. For example, the first time information is from zero to the fourth hour after the power is turned on, and the second time information is from the fourth to the eighth hour after the power is turned on. For example, the historical quality of service may include the historical quality of service for time information 1 and the historical quality of service for time information 2. Thus, the resulting service experience model may be a service experience model that includes different time information.

[0223] (2). Time-varying parameter data affecting the historical quality of service at the user level of a certain service, namely, the historical network data at the flow level corresponding to the historical quality of service data at the user level, namely, the historical quality of service parameter information for said service, is included in myself:

i. TCP congestion window data, TCP receive window data, jitter buffer data, coding rate and media coding type data, buffer data, and data of at least one type of data that come from the AF network element;

ii. flow bit rate data, packet loss rate data, delay data, radio link quality data, and data of at least one type of data that are received from the RAN element;

iii. flow bit rate data, packet loss rate data, delay data, and data of at least one type of data that are received from the UPF network element;

iv. stream bit rate data, packet loss rate data, delay data, TCP congestion window data, TCP receive window data, jitter buffer data, code rate and media encoding type data, buffer data, CPU usage, memory usage, and at least one type of data that comes from the terminal device; and

v. other data.

[0224] In some embodiments, the flow-level historical network data corresponding to the user-level historical QoS data may be flow-level historical network data in a specific location area. In other words, the historical network data at the flow level may include the historical network data at the flow level corresponding to the information of various places. For example, the historical network data at the flow level may include the historical network data at the flow level in region 1 and the historical network data at the flow level in region 2.

[0225] It should be noted that the place information in the historical quality of service data and the place information in the historical network data at the flow level, which are obtained by the data analysis network element, may be inconsistent. For example, the first is GPS location information and the second is cell identification information. In this case, the data analytics network element can establish a mapping relationship between two different types of location information by using user association identification information that is included in both the historical quality of service data and the historical network data at the flow level. Subsequently, the data analytics network element may train the service experience model based on one type of location information.

[0226] In some embodiments, the flow-level historical network data corresponding to the user-level historical QoS data may be flow-level historical network data in the time domain. In other words, the historical network data at the flow level may include the historical network data at the flow level corresponding to different time information. For example, the historical network data at the flow level may include the historical network data at the flow level for time information 1 and the historical network data at the flow level for time information 2.

[0227] B. For example, the data analytics network element can obtain a relational model between the historical quality of service at the service user level and the historical network data at the flow level, namely, the user experience service experience model based on the Linear Regression method. . The details are:

(формула 1.4)

(formula 1.4)

[0228] In formula (1.4), f(x) is the user level quality of service for some service, for example, the MOS value of an individual user for a voice service. X=(x ₁ , x ₂ , x ₃ , ..., x _g ) is an eigenvector. For example, x ₁ indicates delay, x ₂ indicates packet loss ratio, x ₃ indicates stream bitrate, ..., x _g indicates TCP congestion window, and x ₀ is constant 1. M=(m ₁ , m ₂ , m ₃ , ..., m _g ) is a parameter vector, also referred to as a weight vector, and m _i indicates the weight value of the i-th parameter affecting user-level QoS data.

[0229] The above linear regression is just an example of a data analysis algorithm, and the data analytics network element may obtain a user experience model based on a different algorithm. In the present application, this is not particularly limited.

[0230] It can be understood that when a value requirement is set on the function value f(x), that is, a user level quality of service requirement is set, a value of the vector X that satisfies this function value requirement can be obtained by using the above models of the function f(x). Of course, since f(x) is a function of many variables, the resulting X that satisfies the requirement may have multiple solutions, e.g. X1 (x ₁₁ , x ₁₂ , x ₁₃ , ..., x _1g ), X2 ( x ₂₁ , x ₂₂ , x ₂₃ , ..., x _2g ) and X3 (x ₃₁ , x ₃₂ , x ₃₃ , ..., x _3g ).

[0231] Thus, after receiving the quality of service requirement, the analytics network element can determine, based on the quality of service requirement and the user experience model, at least one group of quality of service parameter information that is related to the service and which meets the requirements for quality of service. It should be noted that the process of training the service experience model by the analytical processing network element may be independent of the operation of obtaining the quality of service requirement from the policy network element in step 201. In particular, the analytical processing network element may train the service experience model in advance and then obtain an appropriate decision based on the quality of service requirement received from the policy network element in step 201. Alternatively, the data analytics network element may first obtain the quality of service requirement in step 201, then train the service experience model, and finally obtain an appropriate decision based on the service quality requirement and the service experience model. In addition, the quality of service requirement may not come from the policy network element but from the service server, or be configured in the analytics network element.

[0232] For example, when f(x) means that MOS is greater than 3 and less than 4, the solution to X may be X1 (x ₁₁ , x ₁₂ , x ₁₃ , ..., x _1g ), X2 (x ₂₁ , x ₂₂ , x ₂₃ , ..., x _2g ), X3 (x ₃₁ , x ₃₂ , x ₃₃ , ..., x _3g ), X4 (x ₄₁ , x ₄₂ , x ₄₃ , ..., x _4g ) and X5 (x ₅₁ , x ₅₂ , x ₅₃ , ..., x _5g ). In another example, when f(x) means MOS is greater than 4.5 and less than 5, the solution to X could be X6 (x ₆₁ , x ₆₂ , x ₆₃ , ..., x _6g ) and X7 (x ₇₁ , x ₇₂ , x ₇₃ , ..., x _7g ).

[0233] It can be understood that when the quality of service parameter information that is related to the service and that corresponds to the quality of service requirement is determined by using the user-level service experience model, the quality of service requirement can be used as a requirement of some specific value with respect to the values of the function f(x).

[0234] As described above, in some embodiments, the first request information may include service identification information and a quality of service requirement. Thus, the analytics network element can directly determine, using the quality of service requirement in the first request information, at least one part of the quality of service parameter information that is related to the service and that meets the quality of service requirement.

[0235] In some embodiments, the first request information may include service identification information and user category information. In this case, the analytics network element may determine, based on the correspondence between the user category information and the quality of service requirement, the quality of service requirement corresponding to said user category information in the first request information, and then determine based on this quality of service requirement by at least one group of quality of service parameter information that is related to a service and that corresponds to said user category information. In some embodiments, the data analytics network element may obtain a correspondence between the user category information and the quality of service requirement from the policy network element. In some other embodiments, the analytics network element may obtain a correspondence between the user category information and the quality of service requirement from a service server of a particular service. In some other embodiments, the correspondence between the user category information and the quality of service requirement may alternatively be configured in the analytics network element.

[0236] In some embodiments, the first request information may include service identification information, quality of service requirement, and user category information. In this case, the analytics network element can directly determine at least one group of quality of service parameter information for a service by using the quality of service requirement in the first request information. Each of the at least one group of QoS parameter information for a service corresponds to a QoS requirement and user category information.

[0237] In some embodiments, step 201 may not be performed. Specifically, the analytics network element does not need to determine the quality of service parameter information for the service based on the first request information, but independently determines the quality of service parameter information for the service. Specifically, after the data analysis network element configures or obtains from the specific service service server a quality of service requirement and/or user category information similar to those described in step 201, the data analysis network element determines the quality of service parameter information for said service based on the model trained in step 202 and the requirement for quality of service and/or user category information.

[0238] 203. The data analytics network element sends at least one group of QoS parameter information for the service to the policy control network element. Accordingly, the policy control network element receives at least one group of QoS parameter information for a service that is sent by the data analysis network element.

[0239] In some embodiments, each group of quality of service parameter information may include at least one quality of service parameter type and a corresponding quality of service parameter value. For example, GFBR may be a quality of service parameter type; if GFBR=300, 300 is the value of the QoS parameter. Each quality of service parameter information group may further include a quality of service requirement and/or user category information corresponding to that quality of service parameter information group.

[0240] In some embodiments, the analytics network element may further send to the policy network element the identification information of a service corresponding to at least one group of service quality parameter information of that service. Alternatively, in some embodiments, each group of quality of service parameter information may include identification information of a corresponding service.

[0241] In some embodiments, the analytics network element may further send, to the policy network element, network identification information from slices corresponding to at least one group of quality of service parameter information for a service. Alternatively, in some embodiments, each group of quality of service parameter information may include identification information of a corresponding sliced network.

[0242] In some embodiments, each group of service quality of service parameters information may further include an applicable condition corresponding to that group of service quality of service parameters information. Thus, the policy network element can subsequently determine the applicable quality of service target parameter information for the individual user service procedure based on the applied condition.

[0243] The applied condition can be any one or more of a timing condition, a specific location condition, a network parameter condition (eg, network performance parameter configuration, KPI), a sliced network load condition, and the like.

[0244] The specific form of a specific location condition is not limited in this embodiment of this application as long as the location condition can reflect the location information. For example, the location information may be location information, such as serving cell A or registration area B, which is defined in the 3GPP communication network; or may be location information defined in a non-3GPP communication network. For example, the location information is a range of a specific geographic location. In some embodiments, when step 201 is performed and the first request information carries location information corresponding to the quality of service requirement and/or user category, the location condition may be consistent with the location information.

[0245] The specific form of the time condition is not limited in this embodiment of this application as long as the time condition can reflect time. For example, a time condition can be divided by hours. For example, the time condition could be - from 8:00 to 10:00. In another example, the time condition may alternatively be divided by day. For example, the time condition could be - from the first day to the tenth day of each month. In another example, the time condition may alternatively be divided into time intervals after power-on by the user. For example, the time condition could be from zero to four hours after power on. In some embodiments, when step 201 is performed and the first request information carries time information corresponding to the quality of service requirement and/or user category, the time condition may be consistent with the time information.

[0246] The specific form of the network parameter condition is not limited in this embodiment of this application as long as the network parameter condition can reflect network performance. The network performance may be one or more of user-level network performance, device-level network performance, interface-level network performance, and network-level network performance. For example, user-level network performance may be an individual user service QoS parameter, device-level network performance may be network device capacity, access-layer network performance may be network interface latency or throughput, and network-level network performance may be end-to-end delay. networks.

[0247] Optionally, in some embodiments, the analytics network element may further send at least one piece of QoS information to the policy control network element, wherein said at least one piece of QoS information is in one-to-one correspondence with at least at least one group of quality of service parameter information of a specific service.

[0248] In some embodiments, the quality of service information may be information that reflects the extent to which the quality of service parameter information satisfies the service requirement, in other words, information about the effect of using the quality of service parameter information. For example, the quality of service information may include three levels: "high", "medium", and "low", where "high" means a very high degree in which the quality of service parameter satisfies the service requirement, "medium" means a medium degree , in which the quality of service parameter satisfies the service requirement, and "low" means a very low degree to which the quality of service parameter satisfies the service requirement. Of course, the degree to which the quality of service parameter satisfies the service requirement could alternatively be expressed in another form. In this document, this is not a limitation. As an example, this power can be some particular value in the interval [0, 1]. How the degree to which the quality of service parameter information satisfies the service requirement is calculated belongs to the internal algorithm of the analytical data processing network element. In the present application, this is not a limitation.

[0249] In some embodiments, the quality of service information may be information that reflects the service experience. For example, quality of service data evaluated in the network may reflect the service experience. The quality of service evaluated in the network includes estimated average MOS information or information about user satisfaction with the service. The average MOS information is the average value of the MOS scores obtained by the evaluation of the analytical data processing network element for all service users in the entire network or some areas of the network. User satisfaction with a service is the percentage of users who meet the quality of service requirement of an individual user of said service. For example, the percentage of users whose voice service MOS exceeds three is 95%.

[0250] In some embodiments, the quality of service information may be validity information for a service, and the validity information is information that may reflect the degree of closeness between the network's estimated quality of service and the actual quality of service for said service. For example, the validity information may be a floating point value in [0, 1]. A larger value means higher reliability, namely a higher degree of closeness between the estimated quality of service in the network and the actual quality of service for said service. For example, compared with the case in which the value of the confidence information is 0.3, the case in which the value of the confidence information is 0.8 corresponds to a higher degree of closeness between the estimated quality of service in the network and the actual quality of service for said service. For example, the analytics network element may calculate confidence based on an absolute difference between the network's estimated quality of service and the actual quality of service for said service, with a smaller difference indicating higher confidence. For example, the estimated MOS of the quality of service is 3, the actual MOS is 4, the absolute difference between the estimated MOS and the actual MOS is 1, and the confidence value corresponding to 1 is 0.8. In another example, the estimated quality of service MOS is 3.8, the actual MOS is 4, the absolute difference between the estimated MOS and the actual MOS is 0.2, and the confidence value corresponding to 0.2 is 0.98. In this application, there may be another specific algorithm for calculating this confidence. In the present application, this is not a limitation.

[0251] In this application, the quality of service information may be one type or a combination of several types of quality of service information, which is described in the above three embodiments. Of course, the quality of service information may alternatively be expressed in another form, as long as the quality of service level can be reflected.

[0252] For example, the descriptions in Table 6 are presented using an example in which the quality of service information reflects the extent to which the quality of service parameter information satisfies the service requirement.

Table 6

Service quality requirement Quality of Service Parameter Information Service quality information 4>MOS>3 GFBR=300, MFBR=500 and delay=5 85% GFBR=300, MFBR=500 and delay=4 95% GFBR=300, MFBR=500 and delay=3 98% 4.5>MOS>4 GFBR=200, MFBR=500 and delay=3 98% GFBR=300, MFBR=800 and delay=2 92% 5>MOS>4.5 GFBR=500, MFBR=500 and delay=1. 90%

[0253] As shown in Table 6, the quality information that is related to the service and which corresponds to the information of the quality of service parameters GFBR=300, MFBR=500 and delay=5 is 85%, indicating that the degree to which the GFBR =300, MFBR=500 and delay=5 can satisfy the 4>MOS>3 service requirement is 85%.

[0254] Table 7 shows an example of at least one group of quality of service parameter information for a service.

Table 7

Service quality requirement Quality of Service Parameter Information 4>MOS>3 GFBR=300, MFBR=500 and delay=5 GFBR=300, MFBR=500 and delay=4 GFBR=300, MFBR=500 and delay=3 4.5>MOS>4 GFBR=200, MFBR=500 and delay=3 GFBR=300, MFBR=800 and delay=2 5>MOS>4.5 GFBR=500, MFBR=500 and delay=1.

[0255] As shown in Table 7, the quality of service requirement 4>MOS>3 corresponds to three groups of quality of service parameter information, the quality of service requirement 4.5>MOS>4 corresponds to two groups of quality of service parameter information, and the quality of service requirement 5>MOS>4.5 corresponds to one group of quality of service parameter information. The quality of service parameter information shown in Table 7 represents specific quality of service parameters. For example, one of the three groups of quality of service parameter information that meets the requirement for quality of service 4>MOS>3 includes: guaranteed flow bit rate (GFBR) equal to 300, maximum flow bit rate, MFBR) equal to 500 and a delay (latency) equal to five seconds.

[0256] As shown in Table 7, different quality of service requirements correspond to different quality of service parameter information, and different quality of service requirements also correspond to different numbers of quality of service parameter information groups. As shown in Table 7, the quality of service requirement 5>MOS>4.5 corresponds to one group of quality of service parameters, the quality of service requirement 4.5>MOS>4 corresponds to two groups of quality of service parameter information, and the quality of service requirement 4> MOS>3 corresponds to three groups of quality of service parameter information.

[0257] In some embodiments, different quality of service requirements may correspond to the same number of pieces of quality of service parameter information.

[0258] In some other embodiments, the quality of service parameter information may further include intermediate information. The network policy control element may infer the value of the quality of service parameter based on the intermediate information. For example, one group of quality of service parameter values may correspond to one index, and this index may be used to indicate the corresponding quality of service parameter values. In this case, the quality of service parameter information may be an index. In another example, the quality of service parameter information delivered by the analytics network element is not a quality of service parameter (e.g., a QoS parameter) that is ultimately delivered by the policy network element in the QoS policy to each network element to use, but represents some intermediate parameters. In this case, after receiving at least one group of QoS parameter information, the policy network element further needs to first calculate or map the received at least one QoS parameter information group into a QoS parameter included in the QoS policy, and then deliver the policy. quality of service to each connected network element.

[0259] As an example, Table 8 shows an example of at least one group of quality of service parameter information for a service.

Table 8

Service quality requirement Quality of Service Parameter Information 4>MOS>3 1 2 3 4.5>MOS>4 four five 5>MOS>4.5 6

[0260] Table 9 shows the correspondence between the values of the quality of service parameters and the index.

Table 9

Index QoS parameter value 1 GFBR=300, MFBR=500 and delay=5 2 GFBR=300, MFBR=500 and delay=4 3 GFBR=300, MFBR=500 and delay=3 four GFBR=200, MFBR=500 and delay=3 five GFBR=300, MFBR=800 and delay=2 6 GFBR=500, MFBR=500 and delay=1.5

[0261] The analytics network element may first determine at least one quality of service parameter value group, and then determine, based on the correspondence between the quality of service parameter values and the index, an index corresponding to the at least one quality of service parameter value group. The at least one QoS parameter information group for the service that is sent by the data analysis network element to the policy control network element may be an index corresponding to the at least one QoS parameter value group. Upon receiving at least one group of QoS parameter information for a service, the network policy control element may determine specific QoS parameter values based on a correspondence between the QoS parameter values and the index.

[0262] The correspondence between the quality of service parameter values and the index can be determined by the data analytics network element and then sent to the policy control network element.

[0263] In some embodiments, the implementation of the method shown in FIG. 2 may further include step 204 and step 205.

[0264] 204. The policy network element receives second request information sent by the service server, where the second request information is used to request service setup for the first user.

[0265] The second request information may be sent by the service server to the network policy control element in the process in which the first user sets up the service. The second request information may include identification information of the first user. Optionally, the second request information may further include the first user's user category information and/or the first user's quality of service requirement for the service.

[0266] Optionally, the second request message may further include service description information corresponding to the first user. The service description information is used to describe information about the application layer or media plane that is used by the first user to perform the service, and may specifically include one or more of the following information: identification information of the service to which the service flow belongs, IP- filtering, media bandwidth requirement, traffic routing information, jitter buffer requirement, media encoding type requirement, encoding rate requirement according to media encoding type requirement, TCP congestion window requirement, TCP receive window requirement, requirement to a buffer and a requirement for a value of at least one data type.

[0267] 205. The policy network element determines, based on the user category information of said first user and/or the quality of service requirement of said first user and at least one group of quality of service parameter information for a specific service, quality of service target parameter information that relates to to said service and which corresponds to said first user.

[0268] Optionally, in some embodiments, target quality of service parameter information that is related to the service and that corresponds to the first user may be included in at least one group of quality of service parameter information for the service. In other words, the policy network element may determine, based on the user category information of said first user and/or the quality of service requirement of said first user, one of at least one group of quality of service parameter information for a certain service as the target quality of service parameter information, which refers to said service and which corresponds to said first user.

[0269] Optionally, in some embodiments, the policy network element may generate, based on the user category information of said first user and/or the quality of service requirement of said first user, and at least one group of quality of service parameter information for a specific service, target parameter information quality of service that relates to said service and that corresponds to said first user. In other words, the target quality of service parameter information that is related to the service and that corresponds to the first user is not included in at least one group of quality of service parameter information for the service.

[0270] For example, the network policy control element may first determine, based on the user category information of the first user itself and/or the first user's quality of service requirements, one of at least one group of quality of service parameter information for the service as quality reference parameter information. service, which relates to the service and which corresponds to the first user; and then determining, based on the reference quality of service parameter information that is related to the service and that corresponds to the first user, the target quality of service parameter information that is related to the service and that corresponds to the first user.

[0271] In particular, the network policy control element can modify one or more parameters in the service quality reference parameter information that is related to the service and which corresponds to the first user, and this modified quality of service reference parameter information that is related to the service and which corresponds to the first to the user is quality of service target information that is related to the service and that corresponds to the first user. The network policy control element may modify, based on the current local policy and the current status of the network resources, one or more parameters in the reference quality of service parameter information that is related to the service and that corresponds to the first user.

[0272] In another example, the policy network element may generate a quality of service policy based on one of at least one group of quality of service parameter information for a service, and this quality of service policy is used as quality of service target parameter information that is related to the service. and which matches the first user. For example, the quality of service parameter information includes service coding information. The network policy control element generates a maximum packet loss rate for the data packet based on the coding information, and the maximum packet loss rate for the data packet is used as the target quality of service parameter information.

[0273] It can be understood that step 204 and step 205 can be performed after step 203; or step 204 may be performed before step 203, but step 205 must be performed after step 203.

[0274] If the network policy control element receives a plurality of quality of service parameter information groups for a service, the plurality of quality of service parameter information groups may include quality of service parameter information corresponding to different user category information and/or quality of service requirements.

[0275] For example, assuming that the network policy control element receives N quality of service parameter information groups for a service, where N is a positive integer greater than 1, the N quality of service parameter information groups may include N1 quality of service parameter information groups corresponding to A -th user category information and/or Ath quality of service requirement, N2 groups of information of the quality of service parameters corresponding to the Bth information of the user category and/or the Bth quality of service requirement, and N3 groups of information of the quality of service parameters corresponding to C-th user category information and/or C-th quality of service requirement, wherein N1, N2 and N3 are all positive integers greater than or equal to 1, and the sum of N1, N2 and N3 is N.

[0276] The policy network element may first determine, based on the first user's own user category information and/or the first user's quality of service requirements, quality of service parameter information that is related to said service and which corresponds to said first user's own user category information, and /or the quality of service requirement of the first user. If the plurality of groups of quality of service parameter information for a service include only one group of quality of service parameter information that is related to the service and that corresponds to the user category information of the first user proper and/or the first user's quality of service requirement, the target quality of service parameter information that refers to the service and which corresponds to the first user is a group of quality of service parameter information which refers to the service and which corresponds to the user category information of the first user itself and/or the first user's quality of service requirement. If the plurality of service quality parameter information groups for a service only includes a plurality of service quality parameter information groups that correspond to the user category information of the first user itself and/or the first user's quality of service requirement, the network policy control element may define one parameter information group quality of service parameter information of the plurality of service quality parameter information groups as the target quality of service parameter information corresponding to the first user. In some embodiments, the network policy control element may alternatively determine, based on one or more of a slice network identity, a service identity, and an applied condition that corresponds to each of a plurality of quality of service parameter information groups for a service, target quality parameter information. service which belongs to said service and which corresponds to said first user.

[0277] In particular, the network policy control element can determine, based on the network status and the matching applicable condition, quality of service target information that is related to the service and that corresponds to the first user. For example, assuming that the applicable condition corresponding to each quality of service parameter group is a temporary condition, the network policy control element selects from a plurality of groups of quality of service parameter information for a service that corresponds to the first user's user category information and/or the first user's quality of service requirement. , one group of quality of service parameters that corresponds to the time condition as target quality of service parameters based on the current time information. For example, assuming that the applicable condition corresponding to each QoS parameter group is the slice network load information in which the user performs the service, the network policy control element may alternatively determine, based on the current slice network load information, one parameter group of a plurality of groups of quality of service parameter information for a service that corresponds to the user category information of the first user itself and/or the first user's quality of service requirement, as the quality of service target parameter information that is related to the service and that corresponds to the first user. For example, when the network load information of the slices is level, the network policy control element selects one QoS parameter group from a plurality of service QoS parameter information groups that correspond to the user category information of the first user itself and/or the first user QoS requirement, in as quality of service target information that is related to the service and that corresponds to the first user; when the network load information of the slices is another layer, the network policy control element selects another QoS parameter group from the plurality of service QoS parameter information groups that correspond to the user category information of the first user itself and/or the first user QoS requirement, as quality of service target information that is related to the service and that corresponds to the first user.

[0278] In some embodiments, if the second request information carries the first user's own user category information and/or the first user's quality of service requirement for the service, the policy network element may directly determine based on the first user's user category information and/or or the first user's quality of service requirements for the service in the second request information, quality of service target information that is related to the service and that corresponds to the first user. The method of specifically determining, by the policy network element, the quality of service target information that is related to the service and that corresponds to the first user has been described above. The details are not repeated here.

[0279] In some other embodiments, the policy network control element may store or know in advance the correspondence between the first user and user category information. Therefore, if the second request information includes the identification information of the first user, but does not include the user category information of the first user itself, the policy network element may determine the user category of the first user based on this match. Then, the network policy control element may determine a group of target quality of service parameters information for the service for the first user in the quality of service parameter information that is related to the service and that corresponds to the category of the user. For example, the policy network element learns, based on the first user's subscription information that is obtained from the UDM, that the first user's user category information represents a golden user. In this case, the network policy control element obtains, from at least one group of QoS parameter information for the service that is received in step 203, one or more groups of QoS parameter information that correspond to the golden user, and ultimately selects one of one or more groups of QoS parameter information that correspond to the golden user as target QoS parameters for the service that correspond to the first user. For example, Table 10 shows an example of at least one group of QoS parameter information for a service.

Table 10

User category Quality of Service Parameter Information bronze user GFBR=300, MFBR=500 and delay=5 GFBR=300, MFBR=500 and delay=4 GFBR=300, MFBR=500 and delay=3 Silver user GFBR=200, MFBR=500 and delay=3 GFBR=300, MFBR=800 and delay=2 Gold user GFBR=500, MFBR=500 and delay=1.

[0280] It is assumed that at least one group of quality of service parameter information for a service that is received by the policy network element is shown in Table 10. If the user category information of the first user is a gold user, the policy network element may determine that the target parameters the QoS for the service that correspond to the first user are: GFBR=500, MFBR=500 and delay=1. If the user category information of the first user is a silver user, the network policy control element may determine that the target quality of service parameters for the service that correspond to the first user are one of (GFBR=200, MFBR=500 and delay=3) and (GFBR= 500, MFBR=500 and delay=1). The policy determined by the policy network element may be determined randomly or may be determined according to a predefined rule. For example, the QoS parameter group with the minimum value (eg, the minimum delay value) in the QoS parameters is defined as QoS target parameter information that is related to the service and that corresponds to the first user. The policy network element may alternatively determine, based on one or more of the slice network identity, the service identity, and the applied condition that corresponds to each group of the quality of service parameter information, the target quality of service parameter information that is related to said service, and which corresponds to the mentioned first user. The method of specifically determining, by the policy network element, the quality of service target information that is related to the service and that corresponds to the first user has been described above. The details are not repeated here.

[0281] In some other embodiments, the network policy control element may store or know in advance the correspondence between the first user and the quality of service requirement. Therefore, if the second request information includes the identification information of the first user, but does not include either the user category information of the first user itself or the quality of service requirement information, the network policy control element may determine the first user's quality of service requirement based on said correspondence. . Then, the network policy control element may determine, in the quality of service parameter information corresponding to the quality of service requirement, the target quality of service parameter information that is related to the service and that corresponds to the first user. For example, the network policy control element learns, based on the subscription information of the first user that is obtained from the UDM, that the quality of service parameter information that is related to the service and that corresponds to the first user is 5>MOS>4.5. In this case, the network policy control element obtains, from at least one group of quality of service parameter information for the service that is received in step 203, quality of service parameter information corresponding to 5>MOS>4.5, and selects one group from the quality of service parameter information as the QoS targets for the service that correspond to the first user.

[0282] It is assumed that at least one group of quality of service parameter information for a service that is received by the policy network element is the one shown in Table 7. If the first user's quality of service requirement for the service is 5>MOS>4 ,5, the network policy control element may determine that the target quality of service parameters for this service that correspond to the first user are: GFBR=500, MFBR=500, and delay=1. If the first user's quality of service requirement for a service is 4.5>MOS>4, the network policy control element may determine that the quality of service targets for that service that correspond to the first user are one of (GFBR=200, MFBR= 500 and delay=3) and (GFBR=500, MFBR=500 and delay=1). The policy determined by the policy network element may be determined randomly or may be determined according to a predefined rule. For example, a group of quality of service parameters with a minimum value (eg, minimum delay value) in the quality of service parameters is defined as the target quality of service parameters for the service that correspond to the first user. The policy network element may alternatively determine, based on one or more of the slice network identity, the service identity, and the applied condition that corresponds to each group of the quality of service parameter information, the target quality of service parameter information that is related to said service, and which corresponds to the mentioned first user. The method of specifically determining, by the policy network element, the quality of service target information that is related to the service and that corresponds to the first user has been described above. The details are not repeated here.

[0283] In some other embodiments, the policy network element may store or know in advance the correspondence between service description information and user category information and/or quality of service requirement. Therefore, if the second request information includes the service description information of the first user, but does not include either the user category information or the first user's quality of service requirement information, the network policy control element may determine the user category and/or the first user's quality of service requirement. user based on said match. Then, the policy network element may determine, based on the user category information and/or the first user's quality of service requirement, quality of service target information that is related to the service and that corresponds to the first user. The method of specifically determining, by the policy network element, the quality of service target information that is related to the service and that corresponds to the first user has been described above. The details are not repeated here. After determining the quality of service target information related to the service and corresponding to the first user, the policy network element can generate, based on the quality of service target information, a quality of service policy corresponding to the first user's service procedure, and send the quality of service policy to the associated the network element or terminal, so that the associated network element or terminal allocates a resource or sets a quality of service parameter for the first user service procedure based on said quality of service policy, thereby ensuring that the first user service procedure has an appropriate quality of service. The QoS policy may be QoS target information, or may not be QoS target information, but obtained after intermediate processing is performed on the QoS target information.

[0284] Optionally, in some embodiments, when the analytics network element further sends at least one piece of QoS information to the policy network element, the policy network element may further determine, based on the at least one piece of QoS information, information QoS targets that are related to the service and that correspond to the first user.

[0285] In some embodiments, when determining the target quality of service parameter information that is related to the service and that corresponds to the first user, the network policy control element may select the quality of service parameter information that is related to the service and that corresponds to the optimal quality of service information.

[0286] Specifically, as described above, the policy network element may first determine, based on the user category information of the first user itself and/or the first user's quality of service requirement, quality of service parameter information that is related to said service and that corresponds to said user category information of the first user itself and/or the first user's quality of service requirement. In some cases, there may be a plurality of groups of QoS parameter information for a service that correspond to the user category information of the first user and/or the QoS requirement of the first user. In this case, the network policy control element can determine, based on the plurality of pieces of the quality of service information that corresponds to the plurality of groups of quality of service parameter information for the service, the target quality of service parameter information corresponding to the first user. In particular, the network policy control element may determine optimal quality of service information from a plurality of pieces of quality of service information. The quality of service parameter information that is related to the service and which corresponds to the optimal quality of service information is the target quality of service parameter information corresponding to the first user. If there are a plurality of pieces of optimal quality of service information, quality of service parameter information that is related to a service and which corresponds to one of the plurality of pieces of optimal quality of service information can be randomly determined as target quality of service parameter information corresponding to the first user.

[0287] Table 6 is used as an example. It is assumed that the six groups of quality of service parameter information for a service, which are shown in Table 6, are all quality of service parameter information that is related to the service and that corresponds to the first user. Assuming that the first user's quality of service requirement is 4>MOS>3, it can be understood from Table 6 that when the corresponding quality of service requirement is 4>MOS>3, the quality information which is related to the service and which corresponds to GFBR=300 , MFBR=500 and delay=3, is the highest. Thus, the network policy control element may select GFBR=300, MFBR=500, and delay=3 as the quality of service target information that is related to the service and that corresponds to the first user.

[0288] Optionally, in some embodiments, the policy network element may further send quality of service target information that is related to the service and that corresponds to the first user to the analytic processing network element. Accordingly, the data analysis network element can receive quality of service target information that is related to the service and corresponds to the first user, and that is sent by the policy control network element. Thus, the data analytics network element can obtain quality of service targets for each service that correspond to all users in the entire network, and the data analytics network element can obtain a load model corresponding to the network by learning the quality of service targets based on this information. .

[0289] Optionally, in some embodiments, the policy control network element may further send target quality of service information to the analytics network element. The target quality of service information is quality of service information that is contained in at least one part of the quality of service information and that corresponds to the target quality of service parameter information that is related to the service and that corresponds to the first user. Accordingly, the data analytics network element can receive target quality of service information. Thus, the data analytics network element can know the quality information that is related to the service and that corresponds to the quality of service targets for each service that correspond to all users in the entire network. This helps to provide quality of service data to support the data analytics network element in the subsequent acquisition, through training, of a load model corresponding to the network.

[0290] As described above, the quality of service target information that is related to the service and which corresponds to the first user is included in at least one group of quality of service parameter information for said service, in other words, the quality of service target information is one of at least one group of quality of service parameter information for the service. In some other embodiments, the quality of service target information that is related to the service and that corresponds to the first user may alternatively be generated based on at least one group of quality of service parameter information for the service, in other words, the quality of service target information may not be one of said at least one group of quality of service parameter information for the service. For example, the network policy control element may modify one of the at least one group of quality of service parameter information for the service, and use the modified group of quality of service parameter information for the service as target quality of service parameter information that is related to said service and that corresponds to the first user. . Alternatively, the network policy control element may generate a quality of service policy based on one of at least one group of quality of service parameter information for a service, and this quality of service policy is used as the target quality of service parameter information that is related to said service and which matches the first user.

[0291] In some embodiments, the implementation of the method shown in FIG. 2 may further include step 206, step 207, and step 208. It can be understood that step 206 and step 207 may be performed before step 201, and step 208 is performed after step 203.

[0292] 206. The policy network element receives third request information sent by the service server, where the third request information is used to request service establishment for the second user.

[0293] The third request information may be sent by the service server to the network policy control element in the process in which the second user sets up the service. The third request information may include identification information of the second user. Optionally, the third request information may further include the second user's user category information and/or the second user's quality of service requirement for the service.

[0294] Optionally, the third request message may further include service description information corresponding to the second user. The service description information is used to describe information about the application layer or media plane that is used by the second user to perform the service, and may specifically include one or more of the following information: identification information of the service to which the service flow belongs, IP- filtering, media bandwidth requirement, traffic routing information, jitter buffer requirement, media encoding type requirement, encoding rate requirement according to media encoding type requirement, TCP congestion window requirement, TCP receive window requirement, requirement to a buffer and a requirement for a value of at least one data type.

[0295] 207. The policy network element determines the quality of service requirement and/or user category information based on the information of the third request, where the quality of service requirement is the quality of service requirement of the second user, and the user category information is the user category information of the second user itself. user.

[0296] That is, the quality of service parameter information that meets the quality of service requirement and/or the user category information and that is requested in the first request information is the quality of service parameter information that is related to the service and that meets the quality of service requirement of the second user, and /or user category information of the second user itself. Accordingly, each of the at least one group of QoS parameter information for the service corresponds to the QoS requirement of the second user and/or the user category of the second user itself. It should be noted that when step 206 and step 207 are included, the first request information may be real-time request information. Specifically, the policy control network element generates real-time first request information based on the third request information sent by the service server, and sends the first request message to the data analysis network element; the data analysis network element returns the content requested by using the first request information. In addition, when step 206 and step 207 are included, the first request information may include only one piece of user category information and/or one piece of quality of service requirement information. Specifically, the first request information includes user category information of the second user itself and/or the second user's quality of service requirement.

[0297] It can be understood that if step 206 and step 207 are not performed, the policy network control element can independently determine the quality of service requirement and/or user category information that are included in the first request information. For example, the network policy control element may determine, according to an internal configuration or an internal policy, the quality of service requirement and/or user category information that is included in the first request information. Note that when step 206 and step 207 are not executed, the first request information may be real-time request information or subscription request information. When the first request information is subscription request information, the analytics network element does not need to immediately send to the policy network element the content requested using the first request information, but it sends the content requested using the first request information to the policy network element after waiting. the occurrence of a subscription event or the fulfillment of a subscription condition. In addition, when steps 206 and step 207 are not performed, the first request information may include a plurality of user categories and/or a plurality of quality of service requirements.

[0298] 208. The policy network element determines, based on at least one group of QoS parameter information for a service, QoS target parameter information that is related to said service and that corresponds to the second user.

[0299] In some embodiments, quality of service target parameter information that is related to the service and that corresponds to the second user may be included in at least one group of quality of service parameter information for the service.

[0300] The specific way that the network policy control element determines the quality of service target information that is related to the service and that corresponds to the second user is similar to the specific way that the network policy control element determines the quality of service target information that is related to the service and that corresponds to the first user, at step 205. Details are not repeated here.

[0301] Similarly, the analytics network element may further send at least one piece of QoS information to the policy control network element, wherein at least one piece of QoS information is in a one-to-one correspondence with at least one group of information. quality of service parameters information for the service, and each of the at least one part of the quality of service information is used to indicate the degree of reliability of the corresponding quality of service parameter information for the service or indicate the degree to which the corresponding quality of service parameter information satisfies the quality of service requirement. Thus, the network policy control element can determine, based on at least one piece of the quality of service information, quality of service target information that is related to the service and that corresponds to the second user.

[0302] Optionally, in some embodiments, the policy network element may further send quality of service target information that is related to the service and that corresponds to the second user to the analytic processing network element. Accordingly, the data analysis network element can receive quality of service target information that is related to the service and corresponds to the second user and sent by the policy control network element. Thus, the data analytics network element can obtain quality of service targets for each service that correspond to all users in the entire network, and the data analytics network element can obtain a load model corresponding to the network by learning the quality of service targets based on this information. .

[0303] Optionally, in some embodiments, the policy control network element may further send target quality of service information to the analytics network element. The target quality of service information is the quality of service information which is in at least one part of the quality of service information and which corresponds to the target quality of service parameter information which is related to the service and which corresponds to the second user. Accordingly, the data analytics network element can receive target quality of service information. In this way, the data analytics network element can know the quality information that is related to the service and that corresponds to the quality of service targets for each service that correspond to all users in the entire network. This helps to provide quality of service data to support the data analytics network element in the subsequent acquisition, through training, of a load model corresponding to the network.

[0304] After determining the quality of service target information that is related to the service and that corresponds to the second user, the policy network element can generate, based on the quality of service target information, a quality of service policy corresponding to the service procedure of the second user, and send the quality policy service to the associated network element or terminal, so that the associated network element or terminal allocates a resource or sets a quality of service parameter for the second user's service procedure based on said quality of service policy, thereby ensuring that the second user's service procedure has an appropriate quality of service. The quality of service policy may be quality of service target information, or may not be quality of service target information, but obtained after performing intermediate processing on this quality of service target information. As described above, the quality of service target information that is related to the service and which corresponds to the second user is included in at least one group of quality of service parameter information for said service, in other words, the quality of service target information is one of at least one a group of QoS parameter information for the service. In some other embodiments, quality of service target information that is related to the service and that corresponds to the second user may alternatively be generated based on at least one group of quality of service parameter information for said service, in other words, quality of service target information may not be one of at least one group of quality of service parameter information for the service. For example, the network policy control element may modify one of the at least one group of service quality parameter information for a service, and use the modified group of service quality parameter information for the service as target quality of service parameter information that is related to said service and that corresponds to the second user. . Alternatively, the policy network element may generate a quality of service policy based on one of at least one group of quality of service parameter information for a service, and this quality of service policy is used as quality of service target parameter information that is related to said service and which corresponds to the second user.

[0305] FIG. 3 is a schematic flow diagram of another method for obtaining quality of service parameters according to an embodiment of this application.

[0306] 301. The policy control network element sends the first request information to the data analytics network element.

[0307] The first request information may be real-time request information or subscription request information. For a specific implementation of step 301, refer to the description of step 201 in the method shown in FIG. 2. Details are not repeated here.

[0308] 302. The data analytics network element determines at least one group of quality of service parameter information for a service based on the first request information.

[0309] For a specific implementation of step 302, refer to the description of step 202 in the method shown in FIG. 2. Details are not repeated here.

[0310] 303. The policy control network element receives at least one group of quality of service parameter information for a service that is sent by the data analysis network element.

[0311] For a specific implementation of step 303, refer to the description of step 203 in the method shown in FIG. 2. Details are not repeated here.

[0312] 304. The policy network element receives second request information sent by the service server, where the second request information is used to request service establishment for the first user.

[0313] For a specific implementation of step 304, refer to the description of step 204 in the method shown in FIG. 2. Details are not repeated here.

[0314] 305. The policy network element determines, based on the user category information of the first user itself and/or the first user's quality of service requirement and at least one group of quality of service parameter information for a service, quality of service target parameter information that relates to the mentioned service and which corresponds to the first user.

[0315] In some embodiments, the policy control network element may further receive an applicable condition that is related to each group of QoS parameter information for a service and that is sent by the analytics network element. Thus, the network policy control element can determine the appropriate QoS target parameter information based on the applied condition.

[0316] For a specific implementation of step 305, refer to the description of step 205 in the method shown in FIG. 2. Details are not repeated here.

[0317] FIG. 4 is a schematic flow diagram of another method for obtaining quality of service parameters according to an embodiment of this application.

[0318] 401. The policy network element receives third request information sent by the service server, where the third request information is used to request service establishment for the second user.

[0319] For a specific implementation of step 401, refer to the description of step 206 in the method shown in FIG. 2. Details are not repeated here.

[0320] 402. The policy network element determines the quality of service requirement and/or user category information based on the information of the third request, where the quality of service requirement is the quality of service requirement of the second user, and the user category information is the user category information of the second user itself. user.

[0321] For a specific implementation of step 402, refer to the description of step 207 in the method shown in FIG. 2. Details are not repeated here.

[0322] 403. The policy control network element sends the first request information to the data analytics network element.

[0323] The first request information may be real-time request information or subscription request information. For a specific implementation of step 403, refer to the description of step 201 in the method shown in FIG. 2. Details are not repeated here.

[0324] 404. The data analytics network element determines at least one group of quality of service parameter information for the service based on the first request information.

[0325] For a specific implementation of step 404, refer to the description of step 202 in the method shown in FIG. 2. Details are not repeated here.

[0326] 405. The policy control network element receives at least one group of quality of service parameter information for a service that is sent by the data analysis network element.

[0327] For a specific implementation of step 405, refer to the description of step 202 in the method shown in FIG. 2. Details are not repeated here.

[0328] In some embodiments, the policy control network element may further receive an applied condition that is related to each group of QoS parameter information for a service and that is sent by the analytics network element. Thus, the network policy control element can determine the appropriate QoS target parameter information based on the applied condition.

[0329] 406. The policy network element determines, based on at least one group of quality of service parameter information for a service, quality of service target parameter information that is related to said service and that corresponds to the second user.

[0330] For a specific implementation of step 405, refer to the description of step 208 in the method shown in FIG. 2. Details are not repeated here.

[0331] FIG. 5 is a schematic flow diagram of another method for obtaining quality of service parameters according to an embodiment of this application. In this embodiment, an analytics network element may be a PCF or other network element having an analytics processing function.

[0332] 501. The analytics network element determines at least one group of quality of service parameter information for a certain service, each of the at least one group of quality of service parameter information corresponding to a quality of service requirement for said service and/or category information. user.

[0333] For details on the meanings and contents of the quality of service requirement and/or user category information, refer to the meanings and contents of the quality of service requirement and/or user category information that are included in the first request message at step 201. The details are not repeated here. The data analytics network element may receive the service quality of service requirement and/or the user category information from the service server of said service.

[0334] For a specific implementation of step 501, refer to the description of step 202 in the method shown in FIG. 2, and the only difference is:

[0335] (1) In addition to AF, the historical quality of service data at the level of the service user that is received by the network element of data analysis processing may additionally come from another network device, for example, from another network element that has the function of analytical processing of the network device , such as NWDAF.

[0336] (2) The user level QoS historical data in this document may be user level QoS historical observation data, and the specific meaning of the user level QoS historical data is similar to the meaning of the user level QoS historical data at 202. Alternatively, the user level QoS historical data may be user level QoS evaluation historical data, where the user level QoS historical evaluation data may be QoS data obtained after execution by the first network device ( e.g. NWDAF) intermediate processing and which reflect the level of the user. However, regardless of the type of historical quality of service data, the method for obtaining at least one group of quality of service parameter information for a service by the analytics network element based on the historical quality of service data is similar to that in step 202. Details are not repeated here.

[0337] In particular, the method for obtaining user-level quality of service assessment data by the first network device (for example, NWDAF) is as follows:

[0338] The first network device receives historical quality of service monitoring data at the service user level from the service server. For information on the meaning of the historical quality of service monitoring data, refer to the user level historical quality of service data provided by the AF at step 202.

[0339] The first network device receives from the network the historical network data corresponding to the historical quality of service monitoring data at the user level of said service. For information about the meaning of historical network data in this document, refer to the meaning of historical network data at step 202.

[0340] The first network device obtains the user-level quality of service assessment data of said service based on said historical user-level quality monitoring data of said service and the corresponding historical network data.

[0341] For example, the first network device is trained, based on a large amount of historical user-level quality of service monitoring data and corresponding historical network data, the relationship in the model between user-level quality of service monitoring data and corresponding historical network data. This first device can further train user level QoS data based on the relationship in the model and the current network data, with the trained user level QoS data being used as user level QoS evaluation data.

[0342] 502. The data analytics network element receives the fourth request information sent by the service server, the fourth request information is used to request the establishment of a service for a third user.

[0343] For a specific implementation of step 502, refer to the description of step 204 in the method shown in FIG. 2. The only difference is: The executor of this step changes from the policy network control in step 204 to the data analytics network element, in other words, in this step the data analytics network element performs the policy network control in step 204.

[0344] 503. The analytics network element determines, based on the user category information of the third user itself and/or the third user's quality of service requirement and at least one group of quality of service parameter information for the service, quality of service target parameter information that relates to to the mentioned service and which corresponds to the third user.

[0345] The quality of service target information that is related to the service and which corresponds to the third user is included in at least one group of quality of service parameter information for said service, in other words, the quality of service target information is one of at least one group quality of service parameter information for the service. In some other embodiments, quality of service target information that is related to a service and that corresponds to a third user may alternatively be generated based on at least one group of quality of service parameter information for said service, in other words, quality of service target information may not be one of at least one group of quality of service parameter information for the service. For example, the network policy control element may modify one of the at least one group of quality of service parameter information for a service, and use the modified group of quality of service parameter information for the service as target quality of service parameter information that is related to said service and that corresponds to a third user. . Alternatively, the network policy control element may generate a quality of service policy based on one of at least one group of quality of service parameter information for a service, and this quality of service policy is used as the target quality of service parameter information that is related to said service and which corresponds to the third user.

[0346] For a specific implementation of step 503, refer to the description of step 205 in the method shown in FIG. 2. The only difference is: The execution entity of this step changes from the policy network control element in step 205 to the data analytics network element, in other words, the data analytics network element performs the policy network control operation in step 205 in this step.

[0347] In some embodiments, the analytics network element may not determine, based on the user category information of the third user itself and/or the third user's quality of service requirement, the quality of service target information that relates to said service and that corresponds to the third user. Before determining the QoS target information related to the service and corresponding to the third user, the analytics network element first obtains from the first device the current user-level QoS rating data corresponding to the third user, and then determines, based on the current user-level QoS rating data, user-level quality of service corresponding to the third user, and at least one group of quality of service parameter information for the service, quality of service target parameter information that is related to the service and that corresponds to the third user.

[0348] It should be noted that the current user level quality of service assessment data corresponding to the third user, which is sent by the first device to the data analysis network element, may be the current range of user level quality of service values corresponding to the third user, for example, the current range MOS values of the third user.

[0349] 504. The data analytics network element sends quality of service target parameter information to the core network element.

[0350] After determining the target quality of service parameter information that is related to the service and that corresponds to the third user, the network element of analytical data processing can send the quality of service parameter information to the associated network element or terminal, so that the associated network element or terminal allocates a resource or sets a parameter the quality of service for the third user's service procedure based on said quality of service parameter information, thereby ensuring that the third user's service procedure has an appropriate quality of service.

[0351] FIG. 6 is a schematic flow diagram of another method for obtaining quality of service parameters according to an embodiment of this application.

[0352] 601. The policy network element sends the first request information to the data analytics network element, where the first request information is used to obtain quality of service information. Accordingly, the data analysis network element receives the first request information sent by the policy control network element.

[0353] In some embodiments, the quality of service information may be information that reflects the extent to which the quality of service parameter information satisfies the service requirement, in other words, information about the effect of using the quality of service parameter information. For example, the quality of service information may include three levels: "high", "medium", and "low", where "high" means a very high degree in which the quality of service parameter satisfies the service requirement, "medium" means a medium degree , in which the quality of service parameter satisfies the service requirement, and "low" means a very low degree to which the quality of service parameter satisfies the service requirement. Of course, the degree to which the quality of service parameter satisfies the service requirement could alternatively be expressed in another form. In this document, this is not a limitation. As an example, this power can be some particular value in the interval [0, 1]. How the degree to which the quality of service parameter information satisfies the service requirement is calculated belongs to the internal algorithm of the analytical data processing network element. In the present application, this is not a limitation.

[0354] In some embodiments, the quality of service information may be information that reflects the service experience. For example, quality of service data evaluated in the network may reflect the service experience. The quality of service evaluated in the network includes estimated average MOS information or information about user satisfaction with the service. The average MOS information is the average value of the MOS scores obtained by the evaluation of the analytical data processing network element for all service users in the entire network or some areas of the network. User satisfaction with a service is the percentage of users who meet the quality of service requirement of an individual user of said service. For example, the percentage of users whose voice service MOS exceeds three is 95%.

[0355] In some embodiments, the quality of service information may be validity information for a service, and this validity information is information that may reflect the degree of closeness between the network's estimated quality of service and the actual quality of service for said service. For example, the validity information may be a floating point value in [0, 1]. A larger value means higher reliability, namely a higher degree of closeness between the estimated quality of service in the network and the actual quality of service for said service. For example, compared with the case in which the value of the confidence information is 0.3, the case in which the value of the confidence information is 0.8 corresponds to a higher degree of closeness between the estimated quality of service in the network and the actual quality of service for said service. For example, the analytics network element may calculate confidence based on an absolute difference between the network's estimated quality of service and the actual quality of service for said service, with a smaller difference indicating higher confidence. For example, the estimated MOS of the quality of service is 3, the actual MOS is 4, the absolute difference between the estimated MOS and the actual MOS is 1, and the confidence value corresponding to 1 is 0.8. In another example, the estimated quality of service MOS is 3.8, the actual MOS is 4, the absolute difference between the estimated MOS and the actual MOS is 0.2, and the confidence value corresponding to 0.2 is 0.98. In this application, there may be another specific algorithm for calculating this reliability. In the present application, this is not a limitation.

[0356] In this application, the quality of service information may be one type or a combination of several types of quality of service information, which is described in the above three embodiments. Of course, the quality of service information may alternatively be expressed in another form, as long as the quality of service level can be reflected.

[0357] The quality of service evaluated in the network may be determined by the analytical processing network element. The actual quality of service for the service may be obtained by the data analytics network element from another network device. For example, an analytics network element may obtain the actual quality of service for a service from a service server.

[0358] The data analytics network element generates network-estimated quality of service data, for example, a user-level MOS estimate value for a voice service, namely an individual user MOS estimate value, based on one or more of the data reported by the user performing the service , data reported by each network device associated with the service, and data reported by the service server.

[0359] In some embodiments, the data analytic network element obtains network data at the flow level or at the user level for a service, and obtains network-assessed QoS data for the service based on this network data at the flow level or at the user level.

[0360] The network data at the flow level or at the user level is network flow data corresponding to the individual service process of each user. The network flow in this document may specifically be a QoS flow in a 5G network. The network flow data may specifically include a quality of service (QoS) parameter provided by a network device, user equipment, or service server to a particular user service process, such as a Guaranteed Flow Bit Rate (GFBR) , Maximum Flow Bit Rate (MFBR), Uplink or Downlink Maximum Packet Loss Rate (UL or DL Max PLR), Packet Delay Budget (PDB) , Packet Error Rate (PER), Average Window Size, or Maximum Data Burst Volume.

[0361] In particular, this method can be divided into three execution phases:

[0362] Phase 1: The data analytics network element obtains an individual user QoS model for the service, namely a user-level QoS model. This model refers to the variant relationship between quality of service at the user level of a particular service and network data at the flow or user level.

[0363] For example, an analytics network element can obtain a quality of service model of an individual user of a certain service by using the following two steps.

[0364] A: The data analytics network element receives training data for a particular service, the training data being user-level actual QoS data and flow-level or user-level network data, respectively.

[0365] The data analytics network element first collects data separately from network elements such as a service server (e.g., AF), an access network element (e.g., RAN), a user plane function network element (e.g., UPF), a terminal device (e.g., , UE), a mobility management function network element (eg, AMF), a session management function network element (eg, SMF), a policy control function network element (eg, PCF), and then associate the network element data using information such as an ID services, a service flow identifier, a terminal identifier, a session identifier in which the service flow resides, an association identifier existing in each network element, and a time to obtain complete training data. The training data includes the following content:

[0366] (1). The actual user-level QoS data comes from the service server.

[0367] User-level QoS actual data includes at least one individual user's QoS data, and the user-level QoS may be equivalent to an individual user's QoS, namely that individual user's service experience. User-level QoS is data for evaluating the service experience of each user. For example, for a voice service, MOS is used to evaluate the quality of an individual user's voice service, and the range of this MOS is [0, 5]. A higher MOS means a better user experience with the voice service. For example, for a voice MOS=4.5 and a voice MOS=3 for some user, the voice service experience corresponding to the voice MOS=4.5 is better. For a video service, each user's experience with the video service is evaluated through the use of vMOS. The way MOS and vMOS are calculated are different. In this document, individual user quality of service assessment using MOS and vMOS is described with only two examples for voice service and video service. For another type of service, there are many other ways to evaluate the quality of service of an individual user. For example, for a data service, the QoS of an individual user in that data service can be comprehensively evaluated using parameters such as the data packet loss ratio and the average data packet transmission delay. It is not limited in this patent.

[0368] (2). Other time-varying parameter data that affects actual user-level QoS data, namely flow-level or user-level network data, includes:

i. TCP congestion window data, TCP receive window data, jitter buffer data, coding rate and media coding type data, buffer data, and data of at least one type of data that come from the AF network element;

ii. flow bit rate data, packet loss rate data, delay data, radio channel quality data, and data of at least one type of data that are received from the RAN element;

iii. flow bit rate data, packet loss rate data, delay data, and data of at least one type of data that are received from the UPF network element;

iv. stream bit rate data, packet loss rate data, delay data, at least one data type data, TCP congestion window data, TCP receive window data, jitter buffer data, code rate and media coding type data, buffer data , CPU usage, memory usage, and data of at least one type of data that is received from the UE; and

v. other data.

[0369] It should be noted that network data at the flow level or at the user level may also include normalized network data and the like. In this embodiment of the present application, this is not particularly limited.

[0370] B. For example, the data analytics network element obtains a relational model between actual user-level QoS data and flow-level or user-level network data, namely, an individual user experience model, based on the Linear Regression method. ). The details are:

(формула 1.1)

(formula 1.1)

[0371] In formula (1.1), h(x) is the actual user level QoS for some service, eg, the MOS value of an individual user for a voice service. X=(x ₁ , x ₂ , x ₃ , ..., x _D ) is an eigenvector. For example, x ₁ indicates delay, x ₂ indicates packet loss ratio, x ₃ indicates stream bitrate, ..., x _D indicates TCP congestion window, and x ₀ is constant 1. W=(w ₁ , w ₂ , w ₃ , ..., w _D ) is a parameter vector, also called a weight vector, and w _i indicates the weight value of the i-th parameter that affects the quality of service at the user level.

[0372] The above linear regression is just an example of a data analysis algorithm, and the data analytics network element may obtain an individual user experience model based on a different algorithm. In the present application, this is not particularly limited.

[0373] Phase 2: The data analytics network element obtains user level quality of service assessment data based on an existing individual user quality of service model and flow level or user level network data.

[0374] It should be noted that the difference between the network data at the flow level or at the user level in Phase 2 and the network data at the flow level or at the user level in Phase 1 is that, in terms of time, the former are generated after the latter, namely , the flow-level or user-level network data described in Phase 1 is the historical data of the flow-level or user-level network data described in Phase 2. From this, it can be concluded that the user-level QoS data corresponding to flow-level or user-level network data described in Phase 1 is also historical data of the user-level QoS data proper corresponding to the flow-level or user-level network data described in Phase 2. In addition, the difference between the actual data QoS at the user level in Phase 1 and QoS assessment data at the the user level in Phase 2 is that the former are received by the analytics network element from the service server, and the latter are the value estimated by the analytics network element with respect to quality of service.

[0375] In particular, if the analytic processing network element has learned h(x)=model by formula (1.1), the analytic processing network element may calculate based on some particular value of the independent variable X=(x ₁ , x ₂ , x ₃ , ..., x _D ) at some subsequent point in time (more precisely, network data at the flow level corresponding to this subsequent point in time), a particular value of h(x) that corresponds to this subsequent point in time. For example, when h(x) is MOS=3 for a voice service, the value of h(x) is the inferred QoS of an individual user. A large amount of individual user QoS data acquired by using the processing method multiple times generates user-level QoS evaluation data.

[0376] In the method in this phase, after obtaining a stable individual user quality of service model by using the method in Phase 1, the data analytics network element may further infer corresponding user-level quality of service data by using network data at the flow level or at the user. The inferred user-level QoS data is used as QoS evaluation data. In addition, the analytics network element can further calculate, using the received user-level QoS rating data, an average of the QoS rating data of all service users in the entire network or some areas of the network, or the degree of satisfaction of the served user.

[0377] The first request information may include service identification information, and this service identification information is used to uniquely identify the service. For details of the service identification information, refer to the description of the service identification information of FIG. 2. Details are not repeated here.

[0378] Optionally, in some embodiments, the first request information may further include time information, in other words, the first request information is used to obtain quality of service information corresponding to said time information. The specific form of time information in this embodiment of this application is not limited. For example, the time information may be an absolute time, such as from 00:00 January 1, 2017 to 24:00 January 30, 2017. Alternatively, the time information may be relative time information, such as one month ahead of the send time. the first information - request until this time of sending the first information - request. The split amount of the time information may be an hour, a minute, or a day. In this embodiment of the present application, this is not limited.

[0379] Optionally, in some embodiments, the first query information may further include location information, in other words, the first query information is used to query the quality of service information corresponding to said location information. The specific form of the place information in this embodiment of this application is not limited. The location information may be location information defined in the 3GPP communication network (hereinafter referred to as communication network location information for short), eg, serving cell A or registration area B. Alternatively, the location information may be location information defined in a non-3GPP communication network. For example, the location information is a range of a particular geographic location (e.g., latitude and longitude location information or global positioning system (GPS) location information, where the location information defined in a non-3GPP communication network is below for is referred to as geographic location information for short).

[0380] Optionally, in some embodiments, the first request information may further include service description information for a specific service, in other words, the first request information is used to find out quality information that is related to the service and that corresponds to said service description information. . For the meaning of the service description information, refer to the disclosure of the service description information in the embodiment shown in FIG. 2. Details are not repeated here.

[0381] Optionally, in some embodiments, if the service is running on a slice network, the first request information may further include a slice network identity, and the slice network identity may be NSSAI, S-NSSAI, NSI, or the like. . In other words, the first request information is used to find out the quality information which is related to the service and which corresponds to the slice network indicated by the slice network identifier.

[0382] Optionally, in some embodiments, the first request information may further include data network name (DNN) information corresponding to the service. In other words, the first request information is used to find out the quality of service information corresponding to the DNN.

[0383] Optionally, in some embodiments, the implementation of the first information - the request may further include the name of the data point (access point name, APN) corresponding to the service. In other words, the first request information is used to find out the quality information that is related to the service and that corresponds to the APN. Optionally, in some embodiments, the first request information may further include first quality of service parameter information. The first quality of service parameter information refers to quality of service parameter information that is related to a service and that corresponds to the current network. For details on the specific meaning of the quality of service parameter information, refer to the quality of service parameter information shown in FIG. 2. Details are not repeated here. The first quality of service parameter information may be used by the data analytics network element to estimate the quality of service. For example, the data analytics network element uses the first QoS parameter as all or part of the flow-level or user-level network data in Phase 2 to obtain user-level QoS score data.

[0384] Optionally, in some embodiments, the first request information may further include a quality of service requirement for the service and/or user category information, in other words, the first request information is used to find out the quality information that is related to the service. and which meets the requirement for quality of service and/or user category information. The quality of service requirement may be a plurality of quality of service requirements for a service. In this case, the first request information is used to find out the quality information that is related to the service and which meets each of the above-mentioned set of quality of service requirements. The user category information may be a plurality of pieces of user category information. In this case, the first inquiry information is used to ascertain the quality information that is related to the service and that corresponds to each of said plurality of user category information pieces.

[0385] 602. The data analysis network element sends the first response information to the policy control network element, wherein the first response information includes quality information that is related to the service and that is requested by using the first request information. Accordingly, the policy control network element receives the first response information sent by the data analysis network element.

[0386] Optionally, in some embodiments, the first response information includes service identification information.

[0387] Optionally, in some embodiments, the first response information may further include time information, in other words, the first response information includes quality of service information corresponding to said time information. The time information is used to indicate that the quality of service information is quality of service information at the time indicated by said time information.

[0388] Optionally, in some embodiments, the first response information may further include location information, in other words, the first response information includes quality of service information corresponding to said location information. The place information is used to indicate that the quality of service information is the quality of service information at the place indicated by said place information.

[0389] Optionally, in some embodiments, the first response information may further include service description information of the service itself. The service description information is used to indicate that the service quality information is quality information that is related to a service and that corresponds to the service description information.

[0390] Optionally, in some embodiments, the first response information may further include identification information of the sliced network in which the service is located. Thus, the network policy control element can determine, based on the identity information of the sliced network, the sliced network corresponding to the quality of service information.

[0391] Optionally, in some embodiments, the first response information may further include data network name information corresponding to the service. Thus, the network policy control element can determine, based on the communication network name information, the communication network corresponding to the quality of service information.

[0392] Optionally, in some embodiments, the first response information may further include an access point name corresponding to the service. Thus, the network policy control element can determine, based on the access point name, an access point corresponding to the quality of service information.

[0393] Optionally, in some embodiments, when the first request information includes first quality of service parameter information, the first response information may further include this first quality of service parameter information. The first quality of service parameter information is quality of service parameter information that is related to a service and that corresponds to the current network. The first quality of service parameter information is used to indicate that the quality of service parameter information for a service is quality information that is related to a service and that corresponds to the current network.

[0394] Optionally, in some embodiments, the first response information may further include quality of service requirement information for the service and/or user category information, in other words, the first response information includes quality information that is related to the service and that corresponds to the quality of service requirement information and/or user category information. The quality of service requirement information may be a plurality of pieces of quality of service requirement information for a service. In this case, the first response information includes quality information that is related to the service and which corresponds to each of the plurality of pieces of information of the quality of service requirement. The user category information may be a plurality of pieces of user category information. In this case, the first response information includes quality information that is related to a service and that corresponds to each of the plurality of user category information pieces.

[0395] Optionally, in some embodiments, the first response information further includes at least one group of quality of service parameter information for the service that is recommended by the data analysis network element. Refer to step 203 for the meaning and content of the quality of service parameter information for the service. Details are not repeated here.

[0396] The network policy control element can determine, depending on whether the quality of service information satisfies a predetermined condition, whether the quality of service parameter information that is related to the service and that corresponds to the current network can allow the service experience to reach the expected value. In particular, that the quality of service information is not lower than the predetermined condition may indicate that the quality of service parameter information that is related to the service and that corresponds to the current network can allow the service experience to reach the expected value; and that the quality of service information is lower than the preset condition may indicate that the quality of service parameter information that is related to the service and that corresponds to the current network cannot allow the service experience to reach the expected value.

[0397] Optionally, in some embodiments, the implementation of the method shown in FIG. 6 may further include step 603 and the method shown in FIG. 6 may further include some of the steps 604 through 611.

[0398] 603. The policy network element determines whether the quality of service information that is included in the first response information is lower than the predefined condition.

[0399] In some embodiments, the fact that the quality of service information is below the preset condition may indicate that the validity information for the service is below the preset value.

[0400] In some other embodiments, that the quality of service information is below a preset condition may indicate that the quality of service information is worse than other preset quality information, for example, that the MOS estimate value for a service is below a preset value.

[0401] That the quality of service information is not lower than the preset condition may indicate that the quality of service parameter information that is related to the service and that corresponds to the current network can allow the service experience to reach the expected value. That the quality of service information is lower than the predetermined condition may indicate that the quality of service parameter information corresponding to the current network cannot allow the service experience to reach the expected value.

[0402] Optionally, in some embodiments, if the network policy control element determines that the quality of service information that is included in the first response information is lower than the predefined condition, step 604 is executed.

[0403] 604. The policy network element regulates quality of service parameter information for a service. The quality of service parameter information for the service is adjusted so that the quality of service parameter information for the service can allow the service experience to reach the expected value.

[0404] In particular, the network policy control element can adjust the quality of service parameter information that is related to the service and that corresponds to the current network, for example, adjust one or more pieces of parameter information in the quality of service parameter information to improve the quality of service. For example, for a service, GFBR and MFBR in QoS parameters are increased, and service delay and the like are decreased.

[0405] In some embodiments, when the first response information includes time information, the network policy control element adjusts the quality of service parameter information that is related to the service and that corresponds to said time information.

[0406] In some embodiments, when the first response information includes location information, the network policy control element adjusts the quality of service parameter information that is related to the service and that corresponds to said location information.

[0407] In some embodiments, when the first response information includes the identification information of the slice network, the network policy control element adjusts the quality of service parameter information that is related to the service and that corresponds to the slice network.

[0408] In some embodiments, when the first response information includes DNN information, the network policy control element adjusts the quality of service parameter information that is related to the service and that corresponds to said DNN.

[0409] In some embodiments, when the first response information includes an APN, the network policy control element adjusts the quality of service parameter information that is related to the service and that corresponds to the APN.

[0410] In some embodiments, when the first response information includes a quality of service requirement and/or user category information, the network policy control element adjusts the quality of service parameter information that is related to the service and that corresponds to said quality requirement of the service. and/or user category information. The quality of service requirement may be a plurality of quality of service requirements for a service, and the user category information may be a plurality of pieces of user category information.

[0411] Optionally, in some embodiments, if the network policy control element determines that the quality of service information that is included in the first response information is lower than the predetermined condition, some or all of steps 605 to 610 are performed.

[0412] 605. The policy control network element requests the data analytics network element to recommend quality of service parameter information for a service.

[0413] As described above, that the quality of service information is below the preset condition may indicate that the quality of service parameter information corresponding to the current network cannot allow the service experience to reach the expected value. Thus, the policy network element may request the data analytics network element to recommend quality of service parameter information that is related to the service and that can satisfy the expected service experience.

[0414] In particular, for information about this step, refer to the method described in step 201. Details are not repeated here. That the policy network element requests quality of service parameter information for a service from the analytic processing network element by using the first request information in step 201 is equivalent to that the policy network element requests using the first request information from the analytic processing network element data recommendation information quality of service parameters for the service.

[0415] 606. The data analytics network element determines a recommended value of the quality of service parameter information for the service.

[0416] In particular, for information about this step, refer to the method described at step 202. Details are not repeated here. The at least one QoS parameter group for the service, which is determined by the data analytics network element in step 202, is equivalent herein to the recommended QoS parameter information value.

[0417] 607. The data analytics network element sends a recommended value of the quality of service parameter information for the service to the policy control network element.

[0418] In particular, for information about this step, refer to the method described in step 203. Details are not repeated here. The at least one group of service quality of service parameters that is sent by the data analysis network element in step 203 is equivalent herein to the recommended value of service quality of service parameters information to be sent.

[0419] 608. The policy network element adjusts the quality of service parameter for the service based on the recommended value of the quality of service parameter information for the service.

[0420] In particular, the policy control network element performs, based on one or more of the at least one group of service quality of service parameter information that is sent by the data analysis network element, an operation of adjusting the quality of service parameter of the service. For example, when at least one group of QoS parameter information for a service meets only one QoS requirement and/or only one piece of user category information, the network policy control element performs based on one of the at least one group of QoS parameter information for service, a QoS parameter adjustment operation for the service. When at least one group of quality of service parameter information for a service corresponds to a plurality of quality of service requirements and/or a plurality of pieces of user category information, for each quality of service requirement and/or each piece of user category information, the policy network element performs based on one a group that is included in at least one group of quality of service parameter information and that meets the requirement for quality of service and/or user category information, a service quality of service parameter adjustment operation.

[0421] In some embodiments, the policy control network element may adjust and set the quality of service parameter information for a service entirely based on the quality of service parameter information recommended by the analytical processing network element. For example, the QoS parameters for a service that initially exist in the Policy Network Element are GFBR=300 and MFBR=500, and the recommended QoS parameters are GFBR=350 and MFBR=600. In this case, the network policy control element adjusts the GFBR from 300 to 350 and adjusts the MFBR from 500 to 600.

[0422] In some other embodiments, in a case other than the above case, the policy control network element regulates and sets the quality of service parameter information for the service only with reference to the quality of service parameter information recommended by the analytical processing network element. The two pieces of QoS parameter information are not necessarily exactly the same. In addition, the two pieces of QoS parameter information may differ not only in values but also in parameter types. For example, the quality of service parameter recommended by the data analysis network element may be service encoding information, and the policy network element adjusts the maximum packet loss rate information for the data packet based on this encoding information.

[0423] 609. The policy network element receives a service establishment request message for an individual user sent by a service server, and this request message is used to request a service establishment for the user.

[0424] Refer to step 204 for details of this step. The first user in step 204 is an example of a single user in this document, and details are not provided here again.

[0425] 610. The policy network element applies the adjusted quality of service parameter information for the service to the user's service process.

[0426] Specifically, in some embodiments, the network policy control element may further determine user category information and/or user quality of service requirement, and determine, based on said user category information and/or said user quality of service requirement, an appropriate group of adjusted parameter information. quality of service for the service to be used.

[0427] The policy control network element directly or indirectly generates an appropriate QoS policy for a service for the user based on the adjusted QoS parameter information, and sends the QoS policy to the corresponding network device, the corresponding terminal, and the service server.

[0428] In some embodiments, if the network policy control element determines that the quality of service information that is included in the first response information is not lower than a predetermined condition, step 611 is executed.

[0429] 611. The network policy control element applies quality of service parameter information corresponding to the current network to the service.

[0430] That the quality of service information is not lower than the preset condition may indicate that the quality of service parameter information corresponding to the current network can allow the service experience to reach the expected value. Thus, it may not be necessary for the policy network element to request recommended quality of service parameter information for a service from the data analysis network element. The network policy control element may apply quality of service parameter information corresponding to the current network to the service. More specifically, when a user initiates or executes a service, the policy control network element directly or indirectly generates an appropriate QoS policy for the service for the user based on the QoS parameter information corresponding to the current network, and sends the QoS policy to the corresponding network device, the corresponding terminal, and service server.

[0431] In some other embodiments, if the network policy control element determines that the quality of service information that is included in the first response information is not below a predetermined condition, some or all of steps 605 to 610 are performed.

[0432] Optionally, in some embodiments, the implementation of the network policy control element may perform the procedure shown in FIG. 6, repeatedly. Thus, it can be ensured that the network policy control element continuously inquires (queries) and checks whether the quality of service parameter information that is related to the service and that is used by the network is appropriate, in other words, whether the expected quality of service information can be achieved. Optionally, in some embodiments, the network policy control element may perform the procedure shown in FIG. 6, periodically or on a schedule. Optionally, in some other embodiments, the implementation of the network policy control element may perform the procedure shown in FIG. 6 in an event-triggered manner.

[0433] FIG. 7 is a schematic representation of a process flow for obtaining a quality of service classification according to an embodiment of this application.

[0434] 701. The policy network element sends a QoS classification request message to the analytics network element, where the QoS classification request message is used to request the analytics network element to provide QoS classification information for the service. Accordingly, the analytics network element receives the QoS classification request message sent by the policy control network element. The QoS classification request message includes service identification information, and this service identification information is used to uniquely identify the service. For details of the service identification information, refer to the description of the service identification information of FIG. 2. Details are not repeated here.

[0435] Unless otherwise indicated, the quality of service in this embodiment is the quality of service at the user level. The user-level QoS may be equivalent to the individual user's QoS, namely the individual user's service experience. User-level QoS is data for evaluating the service experience of each user. For example, for a voice service, MOS is used to evaluate the quality of an individual user's voice service, and the range of this MOS is [0, 5]. A higher MOS means a better user experience with a voice service. For example, for a voice MOS=4.5 and a voice MOS=3 for some user, the service experience corresponding to the voice MOS=4.5 is better. For a video service, each user's experience with the video service is evaluated through the use of vMOS. The way MOS and vMOS are calculated are different. In this document, individual user quality of service assessment using MOS and vMOS is described with only two examples for voice service and video service. For another type of service, there are many other ways to evaluate the quality of service of an individual user. For example, for a data service, the QoS of an individual user in that data service can be comprehensively evaluated using parameters such as the data packet loss ratio and the average data packet transmission delay. It is not limited in this patent.

[0436] For a certain service, the data analytics network element has a large amount of quality of service data, such as a large amount of user level MOS data for a voice service. A large amount of QoS data in the analytics network element can be obtained from the original QoS data, namely the actual QoS data, in the service server of a specific service. Alternatively, the QoS data bulk in the analytics network element may be generated by the data analytics network element, that is, the QoS data bulk is network evaluation quality of service data. For example, the data analytics network element generates network-estimated quality of service data, such as user-level MOS estimation data for a voice service, based on one or more of user data reported by a user performing the service, network data reported by each network device, associated with the service and service data reported by the service server.

[0437] The quality of service classification information is the classification result of the quality of service data at the user level. For example, the quality of service classification information may be a division of a range of MOS values of a specific service, such as MOS [3, 4] and MOS [4, 5]. Optionally, in some embodiments, the QoS Classification Request Message includes a first Classification Value, and the first Classification Value is used to indicate to the Data Analytics Network Element the classification value recommended or expected by the QoS Policy Network Element of a specific service. For example, for a voice service, the MOS indicators recommended or expected by the policy control network element can be classified into three categories.

[0438] Optionally, in some embodiments, the QoS Classification Request message may further include time information, in other words, this QoS Classification Request message is used to request QoS classification information that corresponds to said time information. The specific form of time information in this embodiment of this application is not limited. For example, the time information may be an absolute time, such as from 00:00 January 1, 2017 to 24:00 January 30, 2017. Alternatively, the time information may be relative time information, such as one month ahead of the send time. the first information - request until this time of sending the first information - request. The split amount of the time information may be an hour, a minute, or a day. In this embodiment of the present application, this is not limited.

[0439] Optionally, in some embodiments, the QoS Classification Request message may further include location information, in other words, this QoS Classification Request message is used to request QoS classification information that corresponds to said location information. The specific form of the place information in this embodiment of this application is not limited. The location information may be location information defined in the 3GPP communication network (hereinafter referred to as communication network location information for short), eg, serving cell A or registration area B. Alternatively, the location information may be location information defined in a non-3GPP communication network. For example, the location information is a range of a particular geographic location (e.g., latitude and longitude location information or global positioning system (GPS) location information, where the location information defined in a non-3GPP communication network is below for is referred to as geographic location information for short).

[0440] Optionally, in some embodiments, the quality of service classification request message may further include service description information for the service, in other words, this quality of service classification request message is used to request classification information that is related to quality of service and that corresponds to the mentioned service description information. For the meaning of the service description information, refer to the disclosure of the service description information in the embodiment shown in FIG. 2. Details are not repeated here.

[0441] Optionally, in some embodiments, if the service is performed on a slice network, the QoS classification request message may further include a slice network identity, and the slice network identity may be NSSAI, S-NSSAI, NSI, or similar. In other words, the QoS Classification Request message is used to request QoS classification information that corresponds to the slice network indicated by the slice network ID.

[0442] Optionally, in some embodiments, the QoS classification request message may further include data network name (DNN) information corresponding to the service. In other words, the QoS Classification Request message is used to request QoS-related classification information that corresponds to the DNN.

[0443] In some embodiments, the QoS classification request message may further include APN information. In other words, the QoS Classification Request message is used to request QoS-related classification information that corresponds to the APN.

[0444] 702. The analytics network element classifies the quality of service for the service based on the quality of service classification request message to obtain a classification result.

[0445] For a certain service, the data analysis network element classifies a large amount of quality of service data by using an internal calculation method to obtain a classification result.

[0446] For example, the data analysis network element classifies a large amount of MOS data at the voice service user level by using a K-means algorithm to obtain that the MOS of the voice service can be classified into five categories: MOS=[0, 1], MOS =[1, 2], MOS=[2, 3], MOS=[3, 4] and MOS=[4, 5]. The MOS data of each individual user may belong to one of these five categories, for example, if the user's voice MOS is 3.8, MOS=3.8 may belong to the MOS=[3, 4] category.

[0447] The K-means algorithm is used above only as an example for description. In fact, in this embodiment of this application, another internal calculation method may alternatively be used, such as a classification method according to the cosine of an angle. In this document, this is not a limitation.

[0448] In some embodiments, the data analytics network element may independently determine the classification value of the quality of service data. For example, the MOS classification value of the voice service is 5. In particular, the data analytics network element may determine the optimal classification value based on the amount of data of the actual stored quality of service data and the internal algorithm. The optimal classification value may ensure that the classification degree is not excessively high or excessively low, and the analytics network element may use the optimal classification value as the classification value of the quality of service data.

[0449] In some other embodiments, the data analysis network element may determine the classification value of the quality of service data based on the first classification value provided by the policy control network element in step 701. For example, the data analysis network element directly uses the first classification value as the value classification of quality of service data. Alternatively, the data analytics network element generates a second classification value based on the first classification value and uses the second classification value as the classification value of the quality of service data.

[0450] In some embodiments, when the quality of service classification request message further includes time information, the data analytics network element may classify the quality of service for the service based on this time information. For example, only QoS data over a period of time is classified.

[0451] In some embodiments, when the quality of service classification request message further includes location information, the data analytics network element may classify the quality of service for a service based on that location information. For example, only QoS data in a certain spatial range is classified.

[0452] Optionally, in some embodiments, when the QoS classification request message further includes service description information for the service, the data analysis network element may further classify the quality of service for the service based on this service description information for the service.

[0453] Optionally, in some embodiments, when the QoS Classification Request message includes the network identity from the slice, the analytics network element may further classify the quality of service for the service based on that network identity from the slice.

[0454] Optionally, in some embodiments, when the QoS classification request message includes data network name (DNN) information corresponding to the service, the data analytic processing network element may further classify the quality of service for the service based on this DNN information.

[0455] Optionally, in some embodiments, when the QoS Classification Request message includes APN information, the data analysis network element may further classify the QoS for the service based on this APN information.

[0456] 703. The analytics network element sends a quality of service classification response message to the policy network element, wherein the quality of service classification response message includes quality of service classification information for the service. Accordingly, the policy control network element receives the QoS classification response message sent by the data analysis network element.

[0457] In particular, the data analysis network element sends, as quality of service classification information, to the policy network element one or more categories of the classification result determined in step 702. For example, the data analysis network element may send all of MOS=[ 0, 1], MOS=[1, 2], MOS=[2, 3], MOS=[3, 4] and MOS=[4, 5] to the network policy control element as quality of service classification information. In another example, the data analytics network element may only send MOS=[3, 4] and MOS=[4, 5] to the policy control network element.

[0458] In some embodiments, the analytics network element may alternatively send the actual classification value to the policy control network element. The actual classification value is the classification value of the quality of service data, which is obtained by the data analysis network element. For example, in the example of step 702, the actual classification value is 5. The actual classification data may be the same as or different from the first classification value sent by the policy network element. In the present application, this is not a limitation.

[0459] In some embodiments, the QoS classification response message may further include time information. In other words, the QoS classification response message includes classification information that is related to the quality of service for a service and that corresponds to this time information.

[0460] In some embodiments, the QoS classification response message may further include location information. In other words, the QoS classification response message includes classification information that is related to the QoS for a service and that corresponds to this location information.

[0461] In some embodiments, the QoS classification response message may further include service description information for the service. In other words, the QoS classification response message includes classification information that is related to QoS for a service and which corresponds to this service description information for the service.

[0462] In some embodiments, the QoS Classification Response message may further include sliced network identification information. In other words, the QoS classification response message includes classification information that is related to the quality of service for a service and that corresponds to this slice network identification information.

[0463] In some embodiments, the QoS classification response message may further include data network name (DNN) information corresponding to the service. In other words, the QoS classification response message includes classification information that is related to the quality of service for a service and that corresponds to this DNN information.

[0464] In some embodiments, the QoS classification response message may further include APN information. In other words, the QoS classification response message includes classification information that is related to the quality of service for a service and that corresponds to this APN information.

[0465] The above step is actually a way to properly subdivide the range of quality of service values through the use of an analytical data processing network element. Subsequently, the network policy control element separately obtains quality of service parameter information for the quality of service of various categories based on the division of the range of quality of service values.

[0466] In some embodiments, the implementation of the method shown in FIG. 7 may further include step 704 and step 705.

[0467] 704. The policy control network element sends the first request information to the data analytics network element. Accordingly, the data analysis network element receives the information of the first request.

[0468] The first request information includes a quality of service requirement. In other words, in this case, the first request information is used to request the quality of service parameter information that is related to the service and which meets the quality of service requirement.

[0469] The quality of service requirement may be quality of service classification information, or it may be generated by the policy network element based on this quality of service classification information. For information about the quality of service requirement, refer to the meaning and content of the quality of service requirement described in FIG. 2. Details are not repeated here.

[0470] In some embodiments, the network policy control element generates one quality of service requirement based on one category in the quality of service classification information. The quality of service requirement is included in the first request information in step 201, and then this first request information is sent to the analytics network element. For example, the network policy control element generates a quality of service requirement MOS=[3, 4] based on the category for MOS=[3, 4].

[0471] In some other embodiments, the network policy control element generates a set of quality of service requirements based on a plurality of categories in the quality of service classification information, and a plurality of pieces of the quality of service classification information corresponds to said set of quality of service requirements. A plurality of quality of service requirements are included in the first request information in step 201, and then this first request information is sent to the analytic processing network element. For example, the policy network element generates a quality of service requirement MOS=[3, 4] based on the category for MOS=[3, 4] and generates a quality of service requirement MOS=[4, 5] based on the category for MOS=[4 , five].

[0472] It should be noted that the above description used an example in which the requirement for quality of service was equated to the corresponding category of quality of service. In fact, there is no restriction in this application on whether the quality of service requirement is the same as the corresponding quality of service category. For example, the network policy control element may generate a quality of service requirement MOS=[3,5, 4] based on the category for MOS=[3, 4].

[0473] 705. The data analytics network element determines at least one piece of QoS parameter information for a service based on the QoS requirement.

[0474] For details on a specific implementation of step 705, refer to the embodiment shown in FIG. 2. Details are not repeated here. It can be understood that the data analytics network element and the policy control network element may further perform step 203 in the embodiment shown in FIG. 2. The analytics network element and the policy control network element may further perform some of the steps 204 to 208 in the embodiment shown in FIG. 2. For specific implementation details, refer to the embodiment shown in FIG. 2. Details are not repeated here.

[0475] Optionally, in some embodiments, the implementation of the method shown in FIG. 7 may further include step 706 and step 707.

[0476] 706. The policy network element may send a first request information to a data analytics network element, where the first request information includes a quality of service requirement. Accordingly, the data analysis network element receives the first request information.

[0477] In other words, in this case, the first request information is used to obtain quality information that is related to the service and that meets the quality of service requirement.

[0478] The quality of service requirement may be quality of service classification information, or it may be generated by the policy network element based on this quality of service classification information. For information about the quality of service requirement, refer to the meaning and content of the quality of service requirement described in FIG. 2. Details are not repeated here.

[0479] In some embodiments, the network policy control element generates one quality of service requirement based on one category in the quality of service classification information. The quality of service requirement is included in the first request information in step 201, and then this first request information is sent to the analytics network element. For example, the network policy control element generates a quality of service requirement MOS=[3, 4] based on the category for MOS=[3, 4].

[0480] In some other embodiments, the network policy control element generates a set of quality of service requirements based on a plurality of categories in the quality of service classification information, and a plurality of pieces of the quality of service classification information corresponds to said set of quality of service requirements. A plurality of quality of service requirements are included in the first request information in step 201, and then this first request information is sent to the analytic processing network element. For example, the policy network element generates a quality of service requirement MOS=[3, 4] based on the category for MOS=[3, 4] and generates a quality of service requirement MOS=[4, 5] based on the category for MOS=[4 , five].

[0481] It should be noted that the above description used an example in which the requirement for quality of service was equated to the corresponding category of quality of service. In fact, there is no restriction in this application on whether the quality of service requirement is the same as the corresponding quality of service category. For example, the network policy control element may generate a quality of service requirement MOS=[3,5, 4] based on the category for MOS=[3, 4].

[0482] A quality of service requirement may be a plurality of quality of service requirements for a service. In this case, the first request information is used to obtain quality information that is related to the service and that meets each of the above-mentioned set of quality of service requirements.

[0483] For details on a specific implementation of step 706, refer to the method shown in FIG. 6. Details are not repeated here.

[0484] 707. The data analytics network element determines the first response information based on the quality of service requirement.

[0485] For details on a specific implementation of step 707, refer to the embodiment shown in FIG. 6. Details are not repeated here. It can be understood that the data analysis network element and the policy control network element may further perform some of the steps 603 to 611 in the embodiment shown in FIG. 6. For specific implementation details, refer to the embodiment shown in FIG. 6. Details are not repeated here.

[0486] FIG. 8 is a structural block representation of a network device according to an embodiment of this application. The network device 800 shown in FIG. 8 includes a processing block 801, a sending block 802, and a receiving block 803. Network device 800 may be a policy network element in the embodiments shown in FIG. 2 - FIG. 4 FIG. 6 and FIG. 7.

[0487] For example, when the network device 800 is a network policy control element in the embodiment shown in FIG. 2, the sender may be configured to send the first request information to the analytic processing network element. The receiving unit may be configured to receive at least one group of quality of service parameter information for a service that is sent by the analytical processing network element. The receiving unit may further be configured to receive second request information sent by the service server. The processing unit may be configured to determine quality of service target parameter information that is related to the service and that corresponds to the first user. The receiving unit may further be configured to receive third request information sent by the service server. The processing unit may be further configured to determine the quality of service requirement and/or user category information. The processing unit may be further configured to determine quality of service target parameter information that is related to the service and that corresponds to the second user.

[0488] In another example, when the network device 800 is a network policy control element in the embodiment shown in FIG. 3, the sender may be configured to send the first request information to the analytic processing network element. The receiving unit may be configured to receive at least one group of quality of service parameter information for a service that is sent by the analytical processing network element. The receiving unit may further be configured to receive second request information sent by the service server. The processing unit may be configured to determine quality of service target parameter information that is related to the service and that corresponds to the first user.

[0489] In another example, when the network device 800 is a network policy control element in the embodiment shown in FIG. 4, the receiving unit may be configured to receive third request information sent by the service server. The processing unit may be further configured to determine the quality of service requirement and/or user category information. The processing unit may be further configured to determine quality of service target parameter information that is related to the service and that corresponds to the second user. The sender may be configured to send the first request information to the analytical data processing network element. The receiving unit may be configured to receive at least one group of quality of service parameter information for a service that is sent by the analytical processing network element. The receiving unit may further be configured to receive the second request information sent by the service server. The processing unit may be further configured to determine quality of service target parameter information that is related to the service and that corresponds to the second user.

[0490] In another example, when the network device 800 is a network policy control element in the embodiment shown in FIG. 6, the sender may be configured to send the first request information. The receiving unit may be configured to receive the first response information. The processing unit may be configured to determine whether the quality parameter information for the service that is included in the first response information is lower than the predetermined condition. The processing unit may be further configured to adjust the quality of service parameter for the service. The sender may be further configured to request the analytics network element to recommend quality of service parameter information for the service. The receiving unit may be further configured to receive a recommended value that relates to quality of service parameter information for a service that is sent by the analytical processing network element. The processing unit may be further configured to adjust the quality of service parameter for the service based on the recommended value of the quality of service parameter information for the service. The receiving unit may further be configured to receive a service establishment request message for an individual user sent by the service server. The processing unit may be further configured to apply the adjusted quality of service parameter information for the service to the service process for the user. The processing unit may be further configured to apply the quality of service parameter information corresponding to the current network to the service.

[0491] In another example, when the network device 800 is a network policy control element in the embodiment shown in FIG. 7, the sender may be configured to send a QoS classification request message. The receiving unit may be configured to receive a quality of service classification response message. The processing unit may be configured to determine the information of the first request. The send block may be configured to send the first request information.

[0492] In an exemplary implementation, processing block 801 may be implemented by a processor, send block 802 may be implemented by a transmitter, and receive block 803 may be implemented by a receiver. For specific functions and beneficial effects of the processing block 801, the sending block 802, and the receiving block 803, refer to the methods shown in FIG. 2 - FIG. 4 FIG. 6 and FIG. 7. Details are not repeated here.

[0493] In a possible implementation, a hardware communication unit (device) is additionally provided. The communication hardware unit may be a network device, or may be a component (eg, a chip or circuit) of a network device. The communication hardware unit may include a processor. The communication hardware unit may further include a receiver, a transmitter, and a memory. The processor may be configured to implement the corresponding function and operation of the aforementioned processing unit. The transmitter may be configured to implement the corresponding function and operation of the aforementioned sender. The receiver may be configured to implement the function and operation of the aforementioned receiving unit. The transmitter and receiver may be combined together and referred to as a transceiver. A component configured to implement a receive function in the transceiver is referred to as a receive unit, and a component configured to implement a send function is regarded as a send unit. The memory may be configured to store an executable instruction or application program code, with the processor directing execution to implement, together with a receiver and transmitter, the methods provided in the aforementioned embodiments of this application; and/or the memory may be configured to temporarily store some data, instruction information, and the like. The memory may be independent of the processor. In this case, the memory may be connected to the processor via a communication line. In another possible implementation, the memory may alternatively be integrated with the processor. In this embodiment of the present application, this is not limited.

[0494] FIG. 9 is a structural block representation of a network device according to an embodiment of this application. As shown in FIG. 9, the network device 900 includes a processor 901 and a memory 902. The processor 901 may be configured to process a communication protocol and communication data, control a network device, execute a software program, process software program data, and the like. The memory 902 is mainly configured to store the software program and data.

[0495] For ease of description, FIG. 9 shows only one memory and one processor. An actual network device product may have one or more processors and one or more memory units. The memory may also be referred to as a storage medium, a storage device, or the like. The memory may be located independently of the processor or may be integrated with the processor. In this embodiment of the present application, this is not limited.

[0496] In this embodiment, according to this application, the circuit or component with the functions of sending and receiving can be considered as the transceiver 903 of the network device, and the processor with the processing function is considered as the processing unit of the network device. A transceiver may also be referred to as a transceiver unit, a transceiver hardware unit, or the like. The processing unit may also be referred to as a processor, a processing board, a processing unit, a processing hardware unit, or the like. A component configured to implement a receive function in the transceiver 903 may be considered a receive unit, and a component configured to implement a send function in the transceiver 903 may be considered a send unit. In other words, the transceiver unit 903 includes a receive unit and a send unit. The receiving unit may sometimes also be referred to as a receiver, a receiver circuit, or the like. The sender may sometimes also be referred to as a transmitter, a transmitter circuit, or the like.

[0497] The processor 901, the memory 902, and the transceiver 903 communicate with each other via an internal communication path to transmit a control signal and/or a data signal.

[0498] The above methods disclosed in the embodiments of this application may be applied to the processor 901 or may be implemented by the processor 901. The processor may be an integrated circuit and may have signal processing capability. During implementation, the steps of the above methods may be performed using a hardware integrated logic circuit in the processor 901 or using an instruction in the form of software.

[0499] The processor described in the embodiments of this application may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array, FPGA) or other programmable logic device, discrete logic element, or transistorized logic device, or discrete hardware component, and may implement or perform the methods, steps, and logic flow diagrams that are disclosed in the embodiments of this application. A general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed with reference to the embodiments of this application may be directly executed and executed by a hardware decode processor, or may be executed and executed using a combination of hardware and a software module in a decode processor. The software module may be located on a storage medium known in the art, such as random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory, electrically erasable programmable memory, or a register. . The storage medium is located in the memory and the processor reads the instruction in the memory and executes the steps in the methods described above in combination with the processor hardware.

[0500] In some embodiments, memory 902 may store an instruction used to perform a method performed by a policy network control element in the method shown in FIG. 2. The processor 901 may execute an instruction stored in memory 902 to implement, together with other hardware (eg, transceiver 903), the steps performed by the policy network element in the manner shown in FIG. 2. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 2.

[0501] In some embodiments, memory 902 may store an instruction used to perform the method performed by the policy network control element in the method shown in FIG. 3. Processor 901 may execute an instruction stored in memory 902 to implement, together with other hardware (eg, transceiver 903), the steps performed by the policy network element in the manner shown in FIG. 3. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 3.

[0502] In some embodiments, memory 902 may store an instruction used to perform a method performed by a policy network control element in the method shown in FIG. 4. Processor 901 may execute an instruction stored in memory 902 to implement, together with other hardware (eg, transceiver 903), the steps performed by the policy network element in the manner shown in FIG. 4. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. four.

[0503] In some embodiments, memory 902 may store an instruction used to perform the method performed by the policy network control element in the method shown in FIG. 6. Processor 901 may execute an instruction stored in memory 902 to implement, together with other hardware (eg, transceiver 903), the steps performed by the policy network element in the manner shown in FIG. 6. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 6.

[0504] In some embodiments, memory 902 may store an instruction used to perform the method performed by the policy network control element in the method shown in FIG. 7. Processor 901 may execute an instruction stored in memory 902 to implement, together with other hardware (eg, transceiver 903), the steps performed by the policy network element in the manner shown in FIG. 7. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 7.

[0505] An embodiment of this application further provides a chip including a transceiver unit and a processing unit. The transceiver unit may be an I/O circuit or a communications interface. A processing unit is a processor, microprocessor, or integrated circuit that is integrated into a chip. The chip may execute the method on the network policy control element side in the above method embodiments.

[0506] An embodiment of this application further provides a computer-readable storage medium. A computer-readable storage medium stores an instruction; when this instruction is executed, the method on the network policy control element side in the above method embodiments is executed.

[0507] An embodiment of this application further provides a computer program product including an instruction. When this instruction is executed, the method on the network policy control element side in the above method embodiments is executed.

[0508] FIG. 10 is a structural block representation of a network device according to an embodiment of this application. The network device 1000 shown in FIG. 10 includes a processing block 1001, a sending block 1002, and a receiving block 1003. The network device 1000 may be an analytics network element in the embodiments shown in FIG. 2 - FIG. 7.

[0509] For example, when the network device 1000 is an analytics network element in the embodiment shown in FIG. 2, the receiving unit may be configured to receive first request information sent by the policy network control element. The processing unit may be configured to determine at least one group of quality of service parameter information for a service. The sender may be configured to send at least one group of QoS parameter information for the service to the network policy control element.

[0510] In another example, when the network device 1000 is an analytics network element in the embodiment shown in FIG. 3, the receiving unit may be configured to receive first request information sent by the policy network control element. The processing unit may be configured to determine at least one group of quality of service parameter information for a service. The sender may be configured to send at least one group of QoS parameter information for the service to the network policy control element.

[0511] In another example, when the network device 1000 is an analytics network element in the embodiment shown in FIG. 4, the receiving unit may be configured to receive first request information sent by the policy network control element. The processing unit may be configured to determine at least one group of quality of service parameter information for a service. The sender may be configured to send at least one group of QoS parameter information for the service to the network policy control element.

[0512] In another example, when the network device 1000 is an analytics network element in the embodiment shown in FIG. 5, the processing unit may be configured to determine at least one group of quality of service parameter information for a service. The receiving unit may be configured to receive the fourth request information sent by the policy network control element. The processing unit may be configured to determine quality of service target parameter information that is related to the service and that corresponds to the third user.

[0513] In another example, when the network device 1000 is an analytics network element in the embodiment shown in FIG. 6, the receiving unit may be configured to receive the first request information. The send block may be configured to send the first response information. The receiving unit may further be configured to receive first request information that is sent by the policy network element and that is used to request a recommendation of quality of service parameter information for a service. The sender may further be configured to send a recommended value of the quality of service parameter information for the service. The processing unit may be configured to determine the first response information and the recommended value of the quality of service parameter information for the service.

[0514] In another example, when the network device 1000 is an analytics network element in the embodiment shown in FIG. 7, the receiving unit may be configured to receive a quality of service classification request message. The processing unit may be configured to determine the classification result. The sender may be configured to send a QoS classification response message. The receiving unit may be configured to receive the first request information.

[0515] In an exemplary manner, processing block 1001 may be implemented by a processor, and send block 1002 may be implemented by a transmitter. For specific functions and beneficial effects of the processing block 1001 and sending block 1002, refer to the methods shown in FIG. 2 - FIG. 7. Details are not repeated here.

[0516] In a possible implementation, a hardware communication unit (device) is additionally provided. The communication hardware unit may be a network device, or may be a component (eg, a chip or circuit) of a network device. The communication hardware unit may include a processor. The communication hardware unit may further include a transmitter and a memory. The processor may be configured to implement the corresponding function and operation of the aforementioned processing unit. The transmitter may be configured to implement the corresponding function and operation of the aforementioned sender. The transmitter and receiver may be combined together and referred to as a transceiver. A component configured to implement a receive function in the transceiver is referred to as a receive unit, and a component configured to implement a send function is regarded as a send unit. The memory may be configured to store an executable instruction or application program code, with the processor directing execution to implement, together with the transmitter, the methods provided in the aforementioned embodiments of this application; and/or the memory may be configured to temporarily store some data, instruction information, and the like. The memory may be independent of the processor. In this case, the memory may be connected to the processor via a communication line. In another possible implementation, the memory may alternatively be integrated with the processor. In this embodiment of the present application, this is not limited.

[0517] FIG. 11 is a structural block representation of a network device according to an embodiment of this application. As shown in FIG. 11, the network device 1100 includes a processor 1101 and a memory 1102. The processor 1101 may be configured to process a communication protocol and communication data, control a network device, execute a software program, process software program data, and the like. The memory 1102 is mainly configured to store the software program and data.

[0518] For ease of description, FIG. 11 shows only one memory and one processor. An actual network device product may have one or more processors and one or more memory units. The memory may also be referred to as a storage medium, a storage device, or the like. The memory may be located independently of the processor or may be integrated with the processor. In this embodiment of the present application, this is not limited.

[0519] In this embodiment, according to this application, the circuit or component with the functions of sending and receiving can be considered as the transceiver 1103 of the network device, and the processor with the processing function is considered as the processing unit of the network device. A transceiver may also be referred to as a transceiver unit, a transceiver means, a transceiver hardware unit, or the like. The processing unit may also be referred to as a processor, a processing board, a processing unit, a processing hardware unit, or the like. A component configured to implement a receive function in the transceiver 1103 may be considered a receive unit, and a component configured to implement a send function in the transceiver 1103 may be considered a send unit. In other words, the transceiver 1103 includes a receiving unit and a sending unit. The receiving unit may sometimes also be referred to as a receiver, a receiver means, a receiver circuit, or the like. The sender may sometimes also be referred to as a transmitter, a transmitter means, a transmitter circuit, or the like.

[0520] The processor 1101, the memory 1102, and the transceiver 1103 communicate with each other via an internal communication path to transmit a control signal and/or a data signal.

[0521] The above methods disclosed in the embodiments of this application may be applied to the processor 1101 or may be implemented by the processor 1101. The processor 1101 may be an integrated circuit and may have signal processing capability. During implementation, the steps of the above methods may be performed using a hardware integrated logic circuit in the processor 1101 or using an instruction in the form of software.

[0522] The processor described in embodiments of this application may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array, FPGA) or other programmable logic device, discrete logic element, or transistorized logic device, or discrete hardware component, and may implement or perform the methods, steps, and logic flow diagrams that are disclosed in the embodiments of this application. A general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed with reference to the embodiments of this application may be directly executed and executed by a hardware decode processor, or may be executed and executed using a combination of hardware and a software module in a decode processor. The software module may be located on a storage medium known in the art, such as random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory, electrically erasable programmable memory, or a register. . The storage medium is located in the memory, and the processor reads an instruction in the memory and executes the steps in the methods described above in combination with the processor hardware.

[0523] In some embodiments, the memory 1102 may store an instruction used to perform the method performed by the analytical data processing network element in the method shown in FIG. 2. Processor 1101 may execute an instruction stored in memory 1102 to implement, together with other hardware (eg, transceiver 1103), the steps performed by the analytical processing network element in the manner shown in FIG. 2. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 2.

[0524] In some embodiments, the memory 1102 may store an instruction used to perform the method performed by the analytical data processing network element in the method shown in FIG. 3. Processor 1101 may execute an instruction stored in memory 1102 to implement, together with other hardware (eg, transceiver 1103), the steps performed by the analytical processing network element in the manner shown in FIG. 3. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 3.

[0525] In some embodiments, the memory 1102 may store an instruction used to perform the method performed by the analytical data processing network element in the method shown in FIG. 4. Processor 1101 may execute an instruction stored in memory 1102 to implement, together with other hardware (eg, transceiver 1103), the steps performed by the analytical processing network element in the manner shown in FIG. 4. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. four.

[0526] In some embodiments, the memory 1102 may store an instruction used to perform the method performed by the analytical data processing network element in the method shown in FIG. 5. Processor 1101 may execute an instruction stored in memory 1102 to implement, together with other hardware (eg, transceiver 1103), the steps performed by the analytical processing network element in the manner shown in FIG. 5. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. five.

[0527] In some embodiments, memory 1102 may store an instruction used to perform the method performed by the analytical data processing network element in the method shown in FIG. 6. Processor 1101 may execute an instruction stored in memory 1102 to implement, together with other hardware (eg, transceiver 1103), the steps performed by NWDAF in the method shown in FIG. 6. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 6.

[0528] In some embodiments, memory 1102 may store an instruction used to perform the method performed by the analytical data processing network element in the method shown in FIG. 7. Processor 1101 may execute an instruction stored in memory 1102 to implement, together with other hardware (eg, transceiver 1103), the steps performed by the analytical processing network element in the manner shown in FIG. 7. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 7.

[0529] An embodiment of this application further provides a chip including a transceiver unit and a processing unit. The transceiver unit may be an I/O circuit or a communications interface. A processing unit is a processor, microprocessor, or integrated circuit that is integrated into a chip. The chip may execute the method on the analytics network element side in the above method embodiments.

[0530] An embodiment of this application further provides a computer-readable storage medium. A computer-readable storage medium stores an instruction; when this instruction is executed, the analytic processing network element side method in the above method embodiments is executed.

[0531] An embodiment of this application further provides a computer program product including an instruction. When this instruction is executed, the analytic processing network element side method in the above method embodiments is executed.

[0532] FIG. 12 is a structural block representation of a server according to the embodiment of this application. Server 1200 shown in FIG. 12 includes a processing block 1201 and a sending block 1202. Server 1200 may be a service server in the embodiments shown in FIG. 2 - FIG. 6.

[0533] The sender may be configured to send information sent by the service server in any of the embodiments shown in FIG. 2 - FIG. 6. The processing unit may be configured to determine the information sent by the send unit.

[0534] For example, the sender may be configured to send second request information. The send block may be configured to send third request information. The sender may further be configured to send the fourth request information. The sender may further be configured to send a service establishment message for an individual user.

[0535] In an exemplary manner, processing block 1201 may be implemented by a processor, and send block 1202 may be implemented by a transmitter. For specific functions and beneficial effects of the processing block 1201 and the sending block 1202, refer to the methods shown in FIG. 2 - FIG. 6. Details are not repeated here.

[0536] In a possible implementation, a hardware communication unit (device) is additionally provided. The communication hardware unit may be a network device, or may be a component (eg, a chip or circuit) of a network device. The communication hardware unit may include a processor. The communication hardware unit may further include a receiver and a memory. The processor may be configured to implement the corresponding function and operation of the aforementioned processing unit. The receiver may be configured to implement the function and operation of the aforementioned receiving unit. The transmitter and receiver may be combined together and referred to as a transceiver. A component configured to implement a receive function in the transceiver is referred to as a receive unit, and a component configured to implement a send function is regarded as a send unit. The memory may be configured to store an executable instruction or application program code, with the processor directing execution to implement, together with a receiver, the methods provided in the aforementioned embodiments of this application; and/or the memory may be configured to temporarily store some data, instruction information, and the like. The memory may be independent of the processor. In this case, the memory may be connected to the processor via a communication line. In another possible implementation, the memory may alternatively be integrated with the processor. In this embodiment of the present application, this is not limited.

[0537] FIG. 13 is a structural block representation of a server according to the embodiment of this application. As shown in FIG. 13, the server 1300 includes a processor 1301 and a memory 1302. The processor 1301 may be configured to process a communication protocol and communication data, control a network device, execute a software program, process software program data, and the like. The memory 1302 is mainly configured to store the software program and data.

[0538] For ease of description, FIG. 13 shows only one memory and one processor. An actual network device product may have one or more processors and one or more memory units. The memory may also be referred to as a storage medium, a storage device, or the like. The memory may be located independently of the processor or may be integrated with the processor. In this embodiment of the present application, this is not limited.

[0539] In this embodiment, according to this application, the circuit or component with the functions of sending and receiving can be considered as the transceiver 1303 of the network device, and the processor with the processing function is considered as the processing unit of the network device. A transceiver may also be referred to as a transceiver unit, a transceiver means, a transceiver hardware unit, or the like. The processing unit may also be referred to as a processor, a processing board, a processing unit, a processing hardware unit, or the like. A component configured to implement a receive function in the transceiver 1303 may be considered a receive unit, and a component capable of implementing a send function may be considered a send unit. In other words, the transceiver 1103 includes a receiving unit and a sending unit. The receiving unit may sometimes also be referred to as a receiver, a receiver means, a receiver circuit, or the like. The sender may sometimes also be referred to as a transmitter, a transmitter means, a transmitter circuit, or the like.

[0540] The processor 1301, the memory 1302, and the transceiver 1303 communicate with each other via an internal communication path to transmit a control signal and/or a data signal.

[0541] The above methods disclosed in the embodiments of this application may be applied to the processor 1301 or may be implemented by the processor 1301. The processor 1301 may be an integrated circuit and may have signal processing capability. During implementation, the steps of the above methods may be performed using a hardware integrated logic circuit in the processor 1301 or using an instruction in the form of software.

[0542] The processor described in embodiments of this application may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array, FPGA) or other programmable logic device, discrete logic element, or transistorized logic device, or discrete hardware component, and may implement or perform the methods, steps, and logic flow diagrams that are disclosed in the embodiments of this application. A general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed with reference to the embodiments of this application may be directly executed and executed by a hardware decode processor, or may be executed and executed using a combination of hardware and a software module in a decode processor. The software module may be located on a storage medium known in the art, such as random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory, electrically erasable programmable memory, or a register. . The storage medium is located in the memory, and the processor reads an instruction in the memory and executes the steps in the methods described above in combination with the processor hardware.

[0543] In some embodiments, memory 1302 may store an instruction used to execute the method performed by the service server in the method shown in FIG. 2. Processor 1301 may execute an instruction stored in memory 1302 to implement, together with other hardware (eg, transceiver 1303), the steps performed by the service server in the method shown in FIG. 2. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 2.

[0544] In some embodiments, memory 1302 may store an instruction used to perform the method performed by the service server in the method shown in FIG. 3. Processor 1301 may execute an instruction stored in memory 1302 to implement, together with other hardware (eg, transceiver 1303), the steps performed by the service server in the method shown in FIG. 3. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 3.

[0545] In some embodiments, memory 1302 may store an instruction used to perform the method performed by the service server in the method shown in FIG. 4. Processor 1301 may execute an instruction stored in memory 1302 to implement, together with other hardware (eg, transceiver 1303), the steps performed by the service server in the method shown in FIG. 4. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. four.

[0546] In some embodiments, memory 1302 may store an instruction used to perform the method performed by the service server in the method shown in FIG. 5. Processor 1301 may execute an instruction stored in memory 1302 to implement, together with other hardware (eg, transceiver 1303), the steps performed by the service server in the method shown in FIG. 5. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. five.

[0547] In some embodiments, memory 1302 may store an instruction used to perform the method performed by the service server in the method shown in FIG. 6. Processor 1301 may execute an instruction stored in memory 1302 to implement, together with other hardware (eg, transceiver 1303), the steps performed by the service server in the method shown in FIG. 6. For specific workflow and benefits, refer to the description in the embodiment shown in FIG. 6.

[0548] An embodiment of this application further provides a chip including a transceiver unit and a processing unit. The transceiver unit may be an I/O circuit or a communications interface. A processing unit is a processor, microprocessor, or integrated circuit that is integrated into a chip. The chip may execute the service server side method in the above method embodiments.

[0549] An embodiment of this application further provides a computer-readable storage medium. A computer-readable storage medium stores an instruction; when this instruction is executed, the service server side method in the above method embodiments is executed.

[0550] An embodiment of this application further provides a computer program product including an instruction. When this instruction is executed, the service server side method in the above method embodiments is executed.

[0551] In the embodiments of this application, the network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory). The operating system may be any one or more computer operating systems, such as a Linux operating system, a UNIX operating system, an Android operating system, or a Windows operating system, which implement the processing of a service by a process. In addition, the specific structure of the execution component of the method provided in the embodiments of this application is not particularly limited in the embodiments of this application, provided that this execution component can execute a program in which the code of the method provided in the embodiments of this application is written. this application to perform communication based on the method provided in the embodiments of this application. For example, an execution component of the method provided in the embodiments of this application may be a network device or a functional module that can call and execute a program on the network device.

[0552] In the devices of FIG. 8 in FIG. 13 in this application, the components are in a communication connection. In particular, the processing unit (or processor), the storage unit (or memory), and the transceiver unit (or transceiver) communicate with each other via an internal connection path for transmitting a control signal and/or a data signal. The above embodiments of the method of this application may apply to a processor, or the processor implements the steps of the above method embodiments. The processor may be an integrated circuit and may have signal processing capability. During implementation, the steps in the above method embodiments may be performed using a hardware hardware integrated logic circuit in a processor or with an instruction in the form of software. The processor can be a central processing unit (CPU), a network processor (NP), a combination of CPU and NP, a digital signal processor (DSP), an application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete logic element or transistorized logic device, or discrete hardware component, and may implement or perform the methods, steps, and logic flow diagrams as disclosed in embodiments of this application. A general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed in this application may be directly executed and executed by a hardware decode processor, or may be executed and executed using a combination of hardware and a software module in the decode processor. The program module may be located on a storage medium known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or a register. The storage medium is located in the memory, and the processor reads an instruction in the memory and executes the steps in the methods described above in combination with the processor hardware. Although only one processor is shown in the figure, a hardware unit may include a plurality of processors, or a processor may include a plurality of processing units. In particular, the processor may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor.

[0553] The memory is configured to store a computer instruction executable by the processor. The memory may be a storage circuit or a storage medium. The memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or flash -memory. Volatile memory can be random access memory (RAM) used as an external cache. The memory may be independent of the processor or may be a storage unit within the processor. In this document, this is not a limitation. Although only one memory is shown in the figure, the hardware block may alternatively include a plurality of memory blocks, or the memory includes a plurality of memory blocks.

[0554] The transceiver is configured to communicate between the processor and another unit or network element. In particular, the transceiver may be a communication interface of a hardware unit, may be a transceiver circuit, or a communication unit. Alternatively, the transceiver may be a communication interface or a processor transceiver circuit. Optionally, the transceiver may be a transceiver chip. The transceiver may further include a send unit and/or a receive unit. In a possible implementation, the transceiver may include at least one communication interface. In another possible implementation, the transceiver may alternatively be a unit implemented in the form of software. In embodiments of this application, the processor may communicate with another unit or network element using a transceiver. For example, the processor receives or receives content from another network element using a transceiver. If the processor and the transceiver are two physically separate components, the processor can exchange content with another block of the hardware block without the use of a transceiver.

[0555] In a possible implementation, the processor, memory, and transceiver may be connected via a bus. The bus may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus can be divided into address bus, data bus, control bus and the like.

[0556] In embodiments of this application, a word such as "example" or "for example" is used to represent an example, illustration, or description. Any embodiment or design scheme described as "example" or "for example" in the embodiments of this application should not be construed as preferable or having more advantages than another embodiment or design scheme. The use of words such as "example" or "for example" is intended to represent a relative concept in a certain way.

[0557] In the embodiments of this application, for ease of understanding, many examples are used in the description. However, these examples are merely examples and do not imply that these examples are the best implementations for this application.

[0558] In the embodiments of this application, a request message, a response message, and various other message names are used for ease of description. However, these messages are only used as examples to describe the content to be migrated or the functionality to be implemented. Specific message names are not a limitation for this application. For example, the messages may be a first message, a second message, and a third message. These messages may be specific messages or may be some fields in the messages. These messages may alternatively represent various maintenance operations.

[0559] Additionally, aspects or features of this application may be implemented as a method, hardware unit, or product that uses standard programming and/or development techniques. The term "product" as used in this application encompasses a computer program that can be accessed from any computer-readable component, medium or medium. For example, computer-readable media may include, but is not limited to, a magnetic storage component (such as a hard disk drive, floppy disk, or magnetic tape), an optical disc (such as a compact disc, CD), or a digital versatile disc. disc, DVD)), a smart card, and a flash memory component (such as an erasable programmable read-only memory (EPROM), card, flash drive, or flash drive). In addition, the various storage media described herein may represent one or more devices that are configured to store information and/or other computer-readable media. The term "computer-readable medium" may include, but is not limited to, a radio channel and various other media that may store, contain, and/or carry instructions and/or data.

[0560] One skilled in the art may be aware that, in combination with the examples described in the embodiments disclosed herein, the blocks and steps of an algorithm may be implemented using electronic hardware or a combination of computer software and electronic hardware. The performance of functions by hardware or software depends on the specific applications and design constraints of the technical solutions. A person skilled in the art can use various methods to implement the described functions for each particular application, but such an implementation should not be considered to be outside the scope of this application.

[0561] A person skilled in the art can clearly understand that for the purposes of a convenient and concise description of the detailed working process of the above system, device and block, see the corresponding process in the above method embodiments. The details are not repeated here.

[0562] In some embodiments presented in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the described embodiments of the hardware unit are only examples. For example, the division into blocks is only a logical division into functions, but in actual implementation it may be different. For example, many blocks or components may be combined or integrated into another system, or certain features may be ignored or not implemented. In addition, the interconnections or direct links or communication connections shown or described may be implemented using certain interfaces. Indirect connections or communication connections between devices or units can be implemented electrically, mechanically, or take other forms.

[0563] Blocks described as separate parts may or may not be physically separate, and parts shown as blocks may or may not be physical blocks, may be located in the same location, or may be distributed over multiple network blocks. Some or all of the blocks may be selected based on actual requirements in order to achieve the objectives of the decisions in the mentioned embodiments.

[0564] In addition, the functional blocks in the embodiments of the present application may be integrated into one processing unit, or each of the units may exist physically separately, or two or more blocks may be integrated into one unit.

[0565] When functions are implemented in the form of a software functional block and sold or used as a standalone product, the functions may be stored on a computer-readable medium. Based on this understanding, the essence of the technical solutions in this application, or a certain part that contributes to the prior art, or some of the technical solutions can be implemented in the form of a software product. The computer program product is stored on a storage medium and includes several instructions for instructing a computing device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the methods described in the embodiments of this application. The above storage media includes: any media that can store program code, such as a USB flash drive, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk.

[0566] The above description is only specific implementations of this application, but is not intended to limit the scope of protection of this application. Any change or replacement readily detectable by a person skilled in the art within the technical scope disclosed in this application should/should fall within the scope of this application. Therefore, the scope of this application is protected by the claims.

Claims (41)

1. Communication method, comprising: sending, by means of the policy network element, a first request information to a data analysis network element, wherein the first request information is for obtaining quality of service information; and receiving, by the policy network element, first response information from the data analysis network element, wherein the first response information contains quality of service information that is requested by using the first request information; wherein the quality of service information is service experience information. 2. The method according to claim. 1, in which the first information - the request contains time information, and the first information - the request is for obtaining quality of service information corresponding to this time information. 3. The method of claim 1, wherein the first request information contains location information, and the first request information is for obtaining quality of service information corresponding to the location information. 4. The method according to p. 1, further comprising: adjusting, by the network policy element, the quality of service parameters information for the service based on the quality of service information. 5. The method of claim 4, wherein the policy network element adjusts the quality of service parameter information for the service based on the quality of service information, comprising: determining by the policy network element that the quality of service information is below a predetermined condition; and adjusting the quality of service information policy information policy element for the service. 6. The method according to claim 1, wherein the first request information further comprises service identification information, and this service identification information uniquely identifies the service. 7. The method according to claim 1, wherein the first request information further comprises data network name (DNN) information corresponding to the service, wherein the first request information ascertains quality of service information corresponding to the DNN. 8. The method of claim 1, wherein the first request information further comprises slice network identification information in case the service is performed on the slice network, wherein the slice network identification information comprises Single Network Slice Selection Assistance Information (S-NSSAI) . 9. The method of claim 1, wherein the service requirement comprises a requirement for a range of mean score (MOS) values for the service. 10. The method according to p. 1, further comprising: sending the data analysis network element the response information to the policy control network element. 11. Communication method, comprising: receiving, by the data analysis network element, a first request information from the policy control network element, wherein the first request information is for obtaining quality of service information; and sending, by the data analysis network element, first response information to the policy control network element, wherein the first response information contains quality of service information that is requested by using the first request information; wherein the quality of service information is service experience information. 12. The method of claim 11, wherein the first response information contains time information, and the quality of service information corresponds to this time information. 13. The method of claim 11, wherein the first response information contains location information, and the quality of service information corresponds to the location information. 14. The method of claim 11, wherein the first request information further comprises service identification information, and the service identification information uniquely identifies the service. 15. The method of claim 11, wherein the first request information further comprises data network name (DNN) information corresponding to the service, wherein the first request information ascertains quality of service information corresponding to the DNN. 16. The method of claim 11, wherein the first request information further comprises slice network identification information if the service is performed on the slice network, wherein the slice network identification information comprises Single Network Slice Selection Assistance Information (S-NSSAI) . 17. The method of claim 11, wherein the service requirement comprises a requirement for a range of mean score (MOS) values for the service. 18. The method according to p. 11, further comprising: obtaining by the analytical processing network element a service experience model for the service; and the analytics network element obtaining quality of service information based on this service experience model for the service. 19. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program; and when that computer program is executing on the processor, the policy network element containing the processor is caused to execute the method of any one of claims. 1-10. 20. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program; and when this computer program is executed on the processor, the analytical data processing network element containing this processor is caused to execute the method according to any one of claims. 11-18. 21. Hardware communication unit, containing: a memory configured to store the instruction; and a processor configured to recall this instruction from memory and execute this instruction to cause this hardware unit to execute the method according to any one of paragraphs. 1-10. 22. Hardware communication unit, containing: a memory configured to store the instruction; and a processor configured to recall this instruction from memory and execute this instruction to cause this hardware unit to execute the method according to any one of paragraphs. 11-18. 23. A communication system, comprising: a network policy control element configured to perform the method according to any one of paragraphs. 1-10; and a data analytics network element configured to send response information to the policy control network element, the response information comprising quality of service information, the quality of service information being service experience information.

Images