Communication method and apparatus

Abstract

The embodiments of the present application provide a communication method and apparatus. The method comprises: a session management function network element receiving first information, which is configured to perform network information monitoring on a plurality of data flows, wherein the plurality of data flows correspond to a first data session, and the first data session corresponds to a plurality of session anchors; and the session management function network element creating at least one quality-of-service flow for the first data session, wherein a first quality-of-service flow among the at least one quality-of-service flow corresponds to one or more of the plurality of data flows, the first quality-of-service flow is used for executing network information monitoring on a data flow carried in the first quality-of-service flow, and the first quality-of-service flow corresponds to one of the plurality of session anchors. The solution enables a quality-of-service flow, to which a data flow for executing network information monitoring belongs, not to be divided, thereby ensuring the reliability of network information monitoring and exposure in a scenario where a flow division point is inserted.

Description

A communication method and device CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 15, 2023, with application number 202311201837.8 and application name “A Communication Method and Device”, the entire contents of which are incorporated by reference in this application. Technical Field The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art The 3rd Generation Partnership Project (3GPP) standard allows wireless communication systems to provide the ability to monitor network information and open it to the outside. For example, when a third party (such as a service provider) needs to obtain the transmission status of user messages in the communication system, the session management function (SMF) network element can configure the access network equipment and at least one protocol data unit (PDU) session anchor to perform network information monitoring on the data stream. The PDU session anchor point can specifically be an anchor user plane function (UPF) network element, and the anchor UPF is a UPF directly connected to the DN on the data transmission channel from the user equipment (UE) to the data network (DN). For the sake of ease of description, the anchor UPF configured to perform network information monitoring is referred to as the "target anchor UPF" below. When performing network information monitoring, the access network device reports the acquired monitoring results (such as congestion information, latency information, etc.) to the target anchor point UPF through the GPRS tunnelling protocol for the user plane (GTP-U) header of the uplink data packet. Specifically, the access network device reports the monitoring results of the access network device at the granularity of the service quality flow, that is, when the access network device identifies an uplink data packet belonging to a service quality flow for performing network information monitoring, the access network device adds the monitoring results of the access network device to the GTP-U header of the uplink data packet. Among them, the service quality flow for performing network information monitoring is the service quality flow corresponding to the data flow for performing network information monitoring. The existing technology supports a PDU session to access the data network through multiple anchor UPFs at the same time. In this scenario, a service quality flow can carry data streams corresponding to different anchor UPFs at the same time. In order to realize that different data streams in a service quality flow pass through different anchor UPFs, a "diversion point" will be inserted into the transmission path of the service quality flow, which is responsible for providing the functions of forwarding uplink traffic toward different anchor UPFs and merging downlink traffic from different anchor UPFs to the UE. Therefore, the scenario in which different data streams in a service quality flow correspond to different anchor UPFs can also be called a "diversion point insertion scenario". In actual applications, the diversion point is generally implemented by an intermediate UPF (the intermediate UPF is the UPF other than the anchor UPF). When the diversion point receives an uplink data packet, it forwards the uplink data packet to the corresponding anchor UPF according to the source Internet protocol (IP) address, source / destination IP address, source / destination port number, etc. of the uplink data packet. In the diversion point insertion scenario, when performing network status information monitoring, the access network equipment reports the monitoring results at the granularity of service quality flow, and there is a problem of inaccurate reporting of network information monitoring results, which makes it impossible to complete the monitoring and disclosure of network information. Summary of the invention A communication method and device provided in an embodiment of the present application are used to improve the accuracy of reporting network information monitoring results and ensure the reliability of network information monitoring and opening in a diversion point insertion scenario. In a first aspect, a communication method is provided, which can be applied to a session management function network element or a chip in a session management function network element. Taking the application of the method to a session management function network element as an example, the method includes: the session management function network element receives first information, and the first information is used to configure network information monitoring of multiple data streams, the multiple data streams correspond to a first data session and the first data session corresponds to multiple session anchor points; the session management function network element creates at least one service quality flow for the first data session, a first service quality flow in the at least one service quality flow corresponds to one or more data flows in the multiple data flows, the first service quality flow is used to perform network information monitoring on the data flow carried in the first service quality flow, and the first service quality flow corresponds to one session anchor point in the multiple session anchor points. In the above scheme, when the data sessions corresponding to the multiple data flows for performing network information monitoring correspond to multiple session anchor points, the session management function network element creates at least one quality of service flow and performs network information monitoring on the data flow carried in the first quality of service flow based on the first quality of service flow in the at least one quality of service flow. Since the first quality of service flow corresponds to one of the multiple session anchor points, the quality of service flow (i.e., the first quality of service flow) to which the data flow for performing network information monitoring belongs can be not diverted, and the monitoring result reported by the access network device through the first quality of service flow can reach the target session anchor point (i.e., the session anchor point for performing network information monitoring). The accuracy of reporting network information monitoring results is improved, and the reliability of network information monitoring (or network information monitoring and opening) in the diversion point insertion scenario is guaranteed. In a possible implementation manner, the session management function network element creates at least one quality of service flow for the first data session, including: the session management function network element creates multiple quality of service flows (or at least two quality of service flows) for the first data session. In a possible implementation, the session management function network element further receives a network information monitoring result for the data flow carried in the first quality of service flow. In this way, the network information monitoring result can be opened to the outside through the session management function network element. Of course, in actual applications, the network information monitoring results may not be opened to the outside through the session management function network element, but may also be opened to the outside through the policy control function network element or the user plane function network element (such as the session anchor point) and other network elements, and the embodiments of the present application do not limit this. In a possible implementation, before at least one quality of service flow is created, multiple data flows correspond to a second quality of service flow in a first data session; the session management function network element may also determine that the second quality of service flow corresponds to multiple session anchor points. In this way, in a scenario where the service quality flow (i.e., the second service quality flow) to which the data flow used to perform network information monitoring originally belongs corresponds to multiple session anchor points, at least one service quality flow can be created, and network information monitoring can be performed based on the first service quality flow in the at least one service quality flow, so that the access network device reports the monitoring results through the first service quality flow, thereby ensuring that the monitoring results reach the target session anchor point (i.e., the session anchor point for performing network information monitoring). In a possible implementation manner, the session management function network element creates at least one quality of service flow for the first data session, including but not limited to the following manners: The session management function network element deletes the second quality of service flow, and creates the at least one quality of service flow, where the at least one quality of service flow is specifically, for example, a plurality of quality of service flows; or, The session management function network element modifies the second quality of service flow, creates at least one new quality of service flow, and the created at least one quality of service flow includes the modified second quality of service flow and the at least one new quality of service flow; or, The session management function network element divides the second quality of service flow into multiple new quality of service flows, and creates at least one quality of service flow as the multiple new quality of service flows; or, The session management function network element modifies the second quality of service flow into multiple new quality of service flows, and the at least one quality of service flow created is the multiple new quality of service flows. Of course, the above methods are just examples, and there may be other methods. In a possible implementation, at least one quality of service flow corresponds to the multiple session anchor points one by one. In this case, the number of the at least one quality of service flow is multiple, and the number is equal to the number of the multiple session anchor points. In this way, it can be ensured that each created quality of service flow corresponds to a session anchor point, and different created quality of service flows correspond to different session anchor points. In a possible implementation manner, the first quality of service flow carries all data flows of a session anchor point corresponding to the first quality of service flow. In one possible implementation, the data streams corresponding to the same quality of service flow in at least one quality of service flow have the same attributes, such as whether to support explicit congestion notification marking. In this way, data streams with different attributes can be guaranteed to correspond to different quality of service flows, thereby improving the reliability of the solution. In a possible implementation, the session management function network element may create different quality of service flows for data flows corresponding to different session anchor points in the second quality of service flow according to the diversion rule and / or the attribute of the data flow, wherein the diversion rule is used to indicate the traffic that should be forwarded to different session anchor points. In this way, it can be achieved that data streams corresponding to different session anchor points correspond to different quality of service streams and / or data streams corresponding to different attributes correspond to different quality of service streams. In a possible implementation manner, the session management network element creates a quality of service flow for each of the multiple data flows. In this way, it can be ensured that different data flows correspond to different service quality flows. The implementation method is simple. In a possible implementation, the session management function network element further sends second information to the policy control function network element, and the second information is used by the policy control function network element to generate multiple network information monitoring rules for multiple data flows; the session management function network element receives multiple network information monitoring rules generated for multiple data flows from the policy control function network element, and each of the multiple network information monitoring rules is used to perform network information monitoring on the corresponding one or more data flows, and the one or more data flows corresponding to each of the multiple network information monitoring rules correspond to one of the multiple session anchor points. Each of the multiple network information monitoring rules corresponds to one or more data flows, and different network information monitoring rules correspond to different data flows. This method creates a non-diverted quality of service flow (ie, the first quality of service flow) by regenerating the network information monitoring rules, thereby improving the reliability of the solution. In a possible implementation manner, the second information includes a set of data flow identifiers. In this way, it is convenient for the policy control function network element to generate multiple network information monitoring rules according to the set of data flow identifiers, thereby further improving the reliability of the solution. In a possible implementation manner, the set of data flow identifiers includes an identifier of a data flow corresponding to at least one session anchor point among multiple session anchor points. In a possible implementation, each network information monitoring rule includes identifiers of one or more data flows corresponding to a session anchor point among multiple session anchor points. In this way, it can be ensured that the quality of service flow (and the data flow carried in the quality of service flow) created according to each network information monitoring rule corresponds to one session anchor point among the multiple session anchor points. In a possible implementation manner, the first information is a PCC rule, and the multiple network information monitoring rules are multiple PCC rules. This implementation is compatible with existing PCC binding rules (ie, one PCC rule corresponds to one quality of service flow) and has high applicability. For example, the session management function network element may bind multiple PCC rules to multiple created quality of service flows in a one-to-one correspondence. In a possible implementation manner, data flows corresponding to the same PCC rule among multiple PCC rules correspond to the same session anchor point, and data flows corresponding to different PCC rules among multiple PCC rules correspond to different session anchor points. In a possible implementation, the session management function network element does not send the second information to the policy control function network element. The first information is a PCC rule; the session management function network element binds the PCC rule to the multiple created quality of service flows. In this way, the interaction process can be reduced and the efficiency of network information monitoring can be improved. In one possible implementation, the first information includes a network information monitoring rule; the session management function network element can also configure the access network device and / or the session anchor point corresponding to the first service quality flow according to the network information monitoring rule to perform network information monitoring based on the first service quality flow. In this way, the access network device and the session anchor point can perform network information monitoring based on the created first quality of service flow, thereby ensuring the reliability of the solution. According to a second aspect, a communication method is provided. The method can be applied to a policy control function network element or a chip in a policy control function network element. Taking the application of the method to a policy control function network element as an example, the method includes: the policy control function network element receives second information, and the second information is used for the policy control function network element to generate multiple network information monitoring rules; the policy control function network element sends multiple network information monitoring rules to a session management function network element, and the multiple network information monitoring rules are used to indicate the policy of the session served by the session management function network element. In one possible implementation, before the policy control function network element receives the second information, the policy control function network element may also send first information to the session management function network element, where the first information is used to configure network information monitoring for multiple data streams, where the multiple data streams correspond to a first data session and the first data session corresponds to multiple session anchors; wherein the second information is used by the policy control function network element to generate multiple network information monitoring rules for the multiple data streams; each of the multiple network information monitoring rules is used to perform network information monitoring on the corresponding one or more data streams, where the one or more data streams corresponding to each of the multiple network information monitoring rules correspond to one session anchor point among the multiple session anchor points. In a possible implementation manner, the second information includes a set of data flow identifiers; the policy control function network element may also generate a plurality of network information monitoring rules according to the set of data flow identifiers. In a possible implementation manner, the set of data flow identifiers includes an identifier of a data flow corresponding to at least one session anchor point among multiple session anchor points. In a possible implementation, each network information monitoring rule includes identifiers of one or more data flows corresponding to a session anchor point among multiple session anchor points. The beneficial effects of the above-mentioned second aspect and its various implementation methods can be referred to the relevant description of the above-mentioned first aspect and its various implementation methods, and will not be repeated here. According to a third aspect, a communication method is provided, which can be applied to a user plane network element or a chip in the user plane network element. Taking the application of the method to the user plane network element as an example, the method includes: the user plane network element receives a first data packet, the first data packet carries reporting information, the first data packet is carried on a second service quality flow, the second service quality flow corresponds to multiple session anchor points, the reporting information is used to notify the access network device of the monitoring result, and the first data packet corresponds to the first session anchor point; the user plane network element sends a second data packet to the second session anchor point, the second data packet carries reporting information, and the second data packet is carried on the second service quality flow; wherein the first session anchor point is different from the second session anchor point, and the multiple session anchor points include the first session anchor point and the second session anchor point. In the above scheme, when the service quality flow corresponding to the data flow for executing network information monitoring is diverted, the user plane network element (specifically, for example, a user plane network element serving as a diversion point or having a diversion point function) can report the reporting information reported by the access network device to the network information monitoring execution unit. The measured session anchor point (such as the second session anchor point) can ensure that the monitoring results reported by the access network device reach the target session anchor point (that is, the session anchor point that performs network information monitoring), thereby ensuring the reliability of network information monitoring (or network information monitoring and opening) in the diversion point insertion scenario. In a possible implementation manner, the user plane network element may send the second data packet to the second session anchor point according to the reporting information in the first data packet. In a possible implementation manner, the user plane network element may carry the reporting information in the first data packet in a second data packet sent to the second session anchor point. In a possible implementation, the user plane network element may obtain the fourth information from the session management function network element or the user plane network element may obtain the fourth information according to the local configuration, and the fourth information is used to indicate at least one session anchor point used to report the network information monitoring result, and the at least one session anchor point includes the second session anchor point. Accordingly, the user plane network element sends the second data packet to the second session anchor point, including: the user plane network element sends the second data packet to each session anchor point of the at least one session anchor point. In this way, the user plane network element can determine the session anchor point (such as the second session anchor point) for performing network information monitoring according to the local configuration or the instruction of other network elements, thereby improving the reliability of the solution. In a possible implementation manner, at least one session anchor point identifier is included. In a possible implementation manner, the fourth information includes indication information, where the indication information is used to indicate that the session anchor points used for reporting the network information monitoring result are all session anchor points corresponding to the second service quality flow. Of course, in practical applications, the fourth information is not limited to the above two implementation methods. In a possible implementation, the second data packet is an empty packet belonging to the second quality of service flow. In this way, when there is no data packet sent to the second session anchor point, the reporting information can be sent to the second session anchor point through the empty packet, thereby improving information transmission efficiency. In a possible implementation manner, the reporting information is carried in a GPRS tunnelling protocol for the user plane (GTP-U) header of the second data packet. In a possible implementation manner, the reported information includes the time when the third data packet leaves the second session anchor point and the time when the third data packet arrives at the access network device. In one possible implementation, the reported information also includes the time when the first data packet leaves the access network device; the method also includes: the user plane network element determines the time when the first data packet arrives at the user plane network element and the time when the second data packet leaves the user plane network element; wherein the second data packet also includes the time when the first data packet arrives at the user plane network element and the time when the second data packet leaves the user plane network element. In this way, the time influence of the reported information staying in the user-plane network element can be compensated, thereby improving the reliability of network information monitoring. In one possible implementation, the first data packet also includes the time when the first data packet leaves the access network device; the method also includes: the user plane network element determines the time when the first data packet arrives at the user plane network element and the time when the second data packet leaves the user plane network element; the user plane network element modifies the time when the first data packet leaves the access network device based on the time when the first data packet arrives at the user plane network element and the time when the second data packet leaves the user plane network element; the second data packet also includes the modified time when the first data packet leaves the access network device. In this way, the time influence of the reported information staying in the user-plane network element can be compensated, thereby improving the reliability of network information monitoring. In a fourth aspect, a communication method is provided, which can be applied to a session management function network element or a chip in a session management function network element. Taking the application of the method to a session management function network element as an example, the method includes: the session management function network element receives first information from a policy control function network element, and the first information is used by the session management function network element to perform network information monitoring on one or more data streams, and the one or more data streams correspond to a first data session and the first data session corresponds to multiple session anchor points; the session management function network element sends fourth information to the user plane network element according to the first information, and the fourth information is used to indicate at least one session anchor point for reporting network information monitoring results. In a possible implementation, one or more data flows correspond to a second quality of service flow in a first data session, and the second quality of service flow corresponds to a plurality of session anchor points. In a possible implementation manner, the fourth information includes an identifier of at least one session anchor point. In a possible implementation manner, the fourth information includes indication information, where the indication information is used to indicate that the session anchor points used for reporting the network information monitoring result are all session anchor points corresponding to the second service quality flow. In one possible implementation, a session management function network element receives network information monitoring results from at least one session anchor point; the session management function network element opens the network information monitoring results and path information to the application function network element, and the path information is used to indicate the path corresponding to the network information monitoring results, and the path information includes one or more of a data network access identifier, a session anchor point address, an edge application server address, an application function network element address, and path indication information. In this way, it can be indicated which user plane path each network information monitoring result corresponds to, thereby improving the reliability of network information disclosure. In a possible implementation, the first information includes a network information monitoring rule; the session management function network element may also monitor the network information according to the network information. The information monitoring rule configures the access network device and / or at least one session anchor point to perform network information monitoring. In this way, access network equipment, session anchor points, etc. can perform network information monitoring to ensure the reliability of the solution. In a possible implementation, when there are multiple at least one session anchor points, the session management function network element may configure different session anchor points among the at least one session anchor point to perform network information monitoring at different times. In this way, the time for each session anchor point to perform network information monitoring can be staggered to ensure that only one network information monitoring is performed at a time, thereby improving the reliability of network information monitoring. The beneficial effects of the fourth aspect and its various implementation methods mentioned above can be referred to the relevant description of the third aspect and its various implementation methods mentioned above, and will not be repeated here. In a fifth aspect, a communication method is provided, which can be applied to a session management function network element or a chip in a session management function network element. Taking the application of the method to a session management function network element as an example, the method includes: the session management function network element receives first information from a policy control function network element, and the first information is used by the session management function network element to perform network information monitoring on one or more data streams, and the one or more data streams correspond to a second service quality flow and the second service quality flow corresponds to multiple session anchor points; the session management function network element sends fifth information to the user plane network element according to the first information, and the fifth information is used to indicate that all data streams corresponding to the second service quality flow are diverted to the same session anchor point. In the above scheme, when the service quality flow (i.e., the second service quality flow) corresponding to the data flow for performing network information monitoring is diverted, the SMF notifies the user-side network element serving as the diversion point to divert all data flows in the service quality flow to the same session anchor point. In this way, it can ensure that the monitoring results reported by the access network device reach the target session anchor point (i.e., the session anchor point for performing network information monitoring), thereby ensuring the reliability of network information monitoring (or network information monitoring and opening) in the diversion point insertion scenario. In one possible implementation, the first information includes one or more of a data network access identifier, a session anchor address, an edge application server address, an application function network element address, and a path indication information, and the one or more of the information is used to indicate a path requested by the application function network element for performing network information monitoring and opening. In this way, the SMF can determine the path for performing network information monitoring and opening based on the above one or more information, which can assist the SMF in determining to which session anchor point all data flows in the service quality flow need to be diverted. In a possible implementation, the fifth information includes an identifier of a target session anchor point, and the fifth information is used to indicate that all data flows corresponding to the second quality of service flow are directed to the target session anchor point. The session management function network element may also determine the target session anchor point based on one or more items of information in the first information, as well as one or more items of edge application server deployment information, contract information of the terminal device, and internal logic of the session management function network element. In this way, SMF can determine which session anchor point to divert all data flows in the second service quality flow and notify the diversion point of the session anchor point, so that the diversion point diverts all data flows in the second service quality flow to the session anchor point, further improving the reliability of network information monitoring. In a possible implementation manner, the first information is a PCC rule. In a possible implementation, the first information includes network information monitoring rules; the session management function network element can also configure the access network device and / or at least one session anchor point among multiple session anchor points to perform network information monitoring according to the network information monitoring rules. In this way, access network equipment, session anchor points, etc. can perform network information monitoring to ensure the reliability of the solution. In a sixth aspect, a communication device is provided, the communication device comprising a module or unit or technical means for executing the method described in the first aspect or any possible implementation of the first aspect. Exemplarily, the device may include: A transceiver module, configured to receive first information from a policy control function network element, the first information being used to configure network information monitoring for a plurality of data streams, the plurality of data streams corresponding to a first data session and the first data session corresponding to a plurality of session anchor points; A processing module is used to create at least one service quality flow for a first data session, a first service quality flow in the at least one service quality flow corresponds to one or more data flows in the multiple data flows, the first service quality flow is used to perform network information monitoring on the data flow carried in the first service quality flow, and the first service quality flow corresponds to a session anchor point in the multiple session anchor points. In a seventh aspect, a communication device is provided, the communication device comprising a module or unit or technical means for executing the method described in the second aspect or any possible implementation of the second aspect. Exemplarily, the device may include: The transceiver module is used to receive the second information, the second information is used for the policy control function network element to generate multiple network information monitoring rules; send the multiple network information monitoring rules to the session management function network element, the multiple network information monitoring rules are used to indicate the policy of the session served by the session management function network element. Optionally, the device further includes a processing module, configured to generate a plurality of network information monitorings according to the second information. In an eighth aspect, a communication device is provided, the communication device including a module or unit or technical means for executing the method described in the third aspect or any possible implementation manner of the third aspect. Exemplarily, the device may include: A transceiver module is used to receive a first data packet, the first data packet carries reporting information, the first data packet is carried on a second service quality flow, the second service quality flow corresponds to multiple session anchors, the reporting information is used to notify the access network device of the monitoring result, and the first data packet corresponds to the first session anchor; send a second data packet to the second session anchor, the second data packet carries reporting information, and the second data packet is carried on the second service quality flow; wherein the first session anchor is different from the second session anchor, and the multiple session anchors include the first session anchor and the second session anchor. Optionally, the device further includes a processing module, configured to determine the second data packet according to the reporting information in the first data packet. In a ninth aspect, a communication device is provided, the communication device comprising a module or unit or technical means for executing the method described in the fourth aspect or any possible implementation of the fourth aspect. Exemplarily, the device may include: A transceiver module is used to receive first information from a policy control function network element, the first information is used by a session management function network element to perform network information monitoring on one or more data streams, the one or more data streams correspond to a first data session and the first data session corresponds to multiple session anchor points; fourth information is sent to a user plane network element according to the first information, the fourth information is used to indicate at least one session anchor point for reporting network information monitoring results. Optionally, the device further includes a processing module, configured to determine fourth information based on the first information. In a tenth aspect, a communication device is provided, the communication device comprising a module or unit or technical means for executing the method described in the fifth aspect or any possible implementation manner of the fifth aspect. Exemplarily, the device may include: A transceiver module is used to receive first information from a policy control function network element, the first information is used by a session management function network element to perform network information monitoring on one or more data streams, the one or more data streams correspond to a second quality of service stream and the second quality of service stream corresponds to multiple session anchor points; and send fifth information to a user plane network element according to the first information, the fifth information is used to indicate that all data streams corresponding to the second quality of service stream are diverted to the same session anchor point. Optionally, the device further includes a processing module, configured to determine fifth information based on the first information. In an eleventh aspect, a communication device is provided, the device comprising: Memory, for storing computer instructions; A processor, used to execute the computer instructions so that the communication device performs the method described in the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, the third aspect or any possible implementation of the third aspect, the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect. In the twelfth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer program or instruction is executed by a communication device, the method described in the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, the third aspect or any possible implementation of the third aspect, the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect is implemented. In the thirteenth aspect, a computer program product comprising instructions is provided. The computer program product stores instructions that, when executed on a computer, cause the computer to execute a method as described in the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, the third aspect or any possible implementation of the third aspect, the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect. For the technical effects that can be achieved in the above-mentioned sixth to thirteenth aspects, please refer to the description of the technical effects that can be achieved by the corresponding design schemes in the above-mentioned first to fifth aspects, and this application will not repeat them here. BRIEF DESCRIPTION OF THE DRAWINGS FIG1 is a network architecture diagram of a communication system applicable to an embodiment of the present application; FIG2 is an example diagram of a multi-session anchor point; FIG3 is a flow chart of a communication method provided in an embodiment of the present application; 4A to 4C are schematic diagrams of several possible diversion scenarios; 5A to 5D are schematic diagrams of several possible QoS flow creations; FIG6 is a flow chart of another communication method provided in an embodiment of the present application; FIG7 is a flow chart of another communication method provided in an embodiment of the present application; FIG8 is a flow chart of another communication method provided in an embodiment of the present application; FIG9 is a flow chart of another communication method provided in an embodiment of the present application; FIG10 is a flow chart of another communication method provided in an embodiment of the present application; FIG11 is a flow chart of another communication method provided in an embodiment of the present application; FIG12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application; FIG13 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It is understandable that the terms "system" and "network" in the embodiments of the present application can be used interchangeably. "At least one" means one or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items, such as at least one of a, b or c, which can represent: a, or b, or c, or a and b, or b and c, or a and c, or a and b and c. Furthermore, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority or importance of multiple objects. For example, the first priority criterion and the second priority criterion are only used to distinguish different criteria, and do not indicate the difference in the content, priority or importance of the two criteria. The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: fifth generation (5th Generation, 5G) communication systems, sixth generation (6th Generation, 6G) communication systems or other future evolution systems, or various other wireless communication systems using wireless access technologies, etc., can all adopt the technical solutions of the embodiments of the present application. Referring to FIG1 , a network architecture diagram of a communication system applicable to an embodiment of the present application is shown. The network functions and entities included in the system mainly include: terminal equipment (UE), radio access network ((radio) access network, (R) AN) network element, user plane function (UPF) network element, data network (Data Network, DN), access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, application function (AF) network element, unified data management (UDM) network element, network exposure function (NEF) network element, network storage function (NRF) network element, edge application server discovery network element (EASDF) network element, and the like. Among them, the terminal equipment (UE) can also be called user equipment, terminal, mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios, for example, device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a mechanical arm, a smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal. The network element of the radio access network ((radio) access network, (R)AN) may also be referred to as access network equipment, radio access network equipment, access network, etc. The specific implementation may be a base station (Base Station), an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation mobile communication system, a next generation base station in a sixth generation mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; it may also be a module or unit that completes part of the functions of a base station, for example, a centralized unit (CU) or a distributed unit (DU). The CU here completes the functions of the radio resource control protocol and the packet data convergence layer protocol (Packet Data Convergence Protocol, PDCP) of the base station, and can also complete the function of the service data adaptation protocol (Service Data Adaptation Protocol, SDAP); DU completes the functions of the radio link control layer and the medium access control (Medium Access Control, MAC) layer of the base station, and can also complete the functions of part of the physical layer or all of the physical layer. For the specific description of the above-mentioned various protocol layers, please refer to the relevant technical specifications of 3GPP. The wireless access network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific equipment form adopted by the wireless access network device. Data Network (DN): A data network that provides business services to users. Generally, the client is located in the terminal device and the server is located in the data network. The data network can be a private network, such as a local area network, or an external network that is not controlled by the operator, such as the Internet, or a proprietary network jointly deployed by operators, such as a network that provides Internet protocol (IP) multimedia core network subsystem (IMS) services. The following is a brief introduction to the functions of network elements in the core network: 1. SMF network element: mainly used for session management, IP address allocation and management of terminal equipment, selection of endpoints for manageable user equipment plane functions, policy control, or charging function interfaces, and downlink data notification. 2. AMF network element: mainly used for mobility management and access management, for example, it can be the mobility management entity (MME) function in the 4G communication network or the AMF network element in the 5G network. 3. PCF network element: a unified policy framework used to guide network behavior and provide policy rule information for control plane functional network elements (such as AMF, SMF, etc.). 4. UDM network element: used to process user identification, contract signing, access authentication, registration, or mobility management, etc. 5. AF network element: used for data routing affected by applications, access to network open functions, or interaction with the policy framework for policy control, etc. 6. UPF network element: used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc. 7. NEF network element: used to securely open the services and capabilities provided by 3GPP network functions to the outside world. 8. NRF network element: used to store description information of network function entities and the services they provide, and to support service discovery, network element entity discovery and other functions. 9. EASDF network element: A network element used to assist in discovering edge application servers (EAS). Its main function is to process domain name system (DNS) messages according to the instructions of SMF. It is understandable that in actual applications, the above network architecture may also include other network elements, and this application does not limit this. It should be noted that the names of the network elements in this application are only examples, and this application does not exclude the possibility that the network elements may be named differently in the future, or that the functions of the network elements may be merged. With the evolution of technology, any device or network element that can realize the functions of the above network elements is within the protection scope of this application. It should be understood that the interface name between the network elements in Figure 1 is only an example, and the name of the interface in the specific implementation may be other names, which is not specifically limited in this application. In addition, the name of the message (or signaling) transmitted between the above network elements is only an example and does not constitute any limitation on the function of the message itself. For ease of description, in the following text, each network element may be represented by its corresponding English abbreviation, for example, "AF" is used to represent an application function network element, "SMF" is used to represent a session management function network element, and so on. The above-mentioned communication system supports guaranteeing the service quality of the business with QoS flow as the granularity. Specifically, SMF maps (or associates or corresponds) the data flow to the corresponding QoS flow according to the policy and charging control (PCC) rule for the data flow, so that the data flow is carried in the QoS flow for transmission. QoS flow is the minimum granularity of QoS differentiation processing in a data session (such as a protocol data unit (PDU) session, or other forms of data sessions. The following text takes the PDU session as an example). QoS flow can be identified by a QoS flow ID (QFI). There can be multiple QoS flows in a PDU session, and multiple data flows can be carried or transmitted in a QoS flow. A PDU session refers to a session for communication between a UE and a DN. The establishment of a PDU session indicates a data transmission channel between the UE and the DN. In the application, the data flow can be a service data flow (SDF). The service data flow can be a service data flow or a packet flow defined in the 3GPP standard. The SDF can be identified by a service data flow template. The service data flow template can be identified by one or more service data flow filters or application identifiers. A service data flow filter can indicate one or more IP quintuples / triplets. Among them, the IP triplet can be a source / destination IP address, a source / destination port number, a protocol, or a source IP address, a destination IP address, and a protocol. For example, data packets that conform to the same service data flow template belong to one SDF. The Service Data Flow Filter may be a packet filter set, which includes two types: an Internet Protocol packet filter set (IP Packet Filter Set) and an Ethernet packet filter set (Ethernet Packet Filter Set). The IP Packet Filter Set is a Packet Filter Set corresponding to an IP PDU session, and the Ethernet Packet Filter Set is a Packet Filter Set corresponding to an Ethernet PDU session. (1) For an IP PDU session, the Packet Filter Set can include any one or more of the following: Source / destination IP address or IPv6 prefix. Source / destination port number; Protocol ID of the protocol above IP / Next header type; Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask; Flow Label (IPv6 only) Security parameter index; Packet Filter direction, either upstream or downstream. (2) For Ethernet PDU sessions, the Packet Filter Set can include any one or more of the following: Source / destination MAC address; Ethertype (Ethertype as defined in IEEE 802.3

[0131] ); Customer-VLAN tag (C-TAG) and / or Service-VLAN tag (S-TAG) VLAN identifier (VLAN identifier, VID field (Customer-VLAN tag (C-TAG) and / or Service-VLAN tag (S-TAG) VID fields as defined in IEEE Std802.1Q

[0098] ); Customer-VLAN tag (C-TAG) and / or Service-VLAN tag (S-TAG) priority code point (PCP) / drop eligible indicator (DEI) fields (Customer-VLAN tag (C-TAG) and / or Service-VLAN tag (S-TAG) PCP / DEI fields as defined in IEEE Std 802.1Q

[0098] ); IP Packet Filter Set, in the case that Ethertype indicates IPv4 / IPv6 payload; Packet Filter direction, either upstream or downstream. The above explanations of data flows are all based on IP as an example, but are also applicable to Ethernet types, for example, if the IP address is replaced with a MAC address, the same is also applicable. For ease of description, the data flow in this application is described with service data flow filter as the granularity, that is, the data of a data flow contains multiple data packets with the same IP quintuple. In the above communication system, SMF can control UPF to be responsible for forwarding user plane data packets. Among them, UPF is divided into intermediate UPF (intermediate UPF, I-UPF) and PDU session anchor user plane network element (PDU session anchor, PSA). PSA refers to the UPF connected to DN through the N6 interface or the UPF that terminates the N6 interface. The intermediate UPF is other UPF other than the anchor UPF. For example, the intermediate UPF can be connected to the RAN through the N3 interface and connected to the anchor UPF (ie PSA) through the N9 interface. The intermediate UPFs can be connected in series with each other, so the intermediate UPF can also be connected to other intermediate UPFs or anchor UPFs through the N9 interface. In order to support selective traffic routing to the data network or support session continuity mode, SMF can control the user plane path of the PDU session (the user plane path refers to the transmission path of the user plane data packet, that is, the data transmission path. User plane data refers to business and application data) so that a PDU session can access the DN through multiple N6 interfaces (or multiple anchor UPFs) at the same time. In other words, a PDU session can have multiple anchor UPFs at the same time. When a PDU session has multiple anchor UPFs at the same time, a node is required on the user plane path of the PDU session to provide the functions of uplink traffic forwarding to different anchor UPFs and downlink traffic merging from different anchor UPFs. This node is called a diversion point or diversion point UPF. For example, as shown in FIG2, it is an example diagram of a multi-session anchor point. SMF can insert a diversion point UPF in the data transmission path of the PDU session. The diversion point UPF can be a branching point (BP) or an uplink classifier (UL CL), that is, the diversion point UPF provides the function of BP or UL CL. The UPF inserted with the function of BP or UL CL is the diversion point UPF. The purpose of the diversion point is to forward the data packets that meet the service filtering rules to the specified path, wherein the service filtering rules include SDF templates. The diversion point UPF forwards the corresponding data packets to the specified PSA UPF (i.e., the anchor point UPF that performs network information monitoring) according to the SDF template in the service filtering rules. For example, taking the service filtering rules including IP quintuple as an example, the diversion point can divert the user plane message according to the IP quintuple of the user plane message. In addition, the 3GPP standard provides a solution for monitoring and opening of network information. Among them, network information may refer to information about the transmission status of user messages on the user plane path. Network information, for example, includes but is not limited to one or more of congestion information, packet loss rate, latency or data rate. The monitoring of network information can be performed by RAN and / or UPF. The opening of network information means that the communication system (such as 5GS) notifies the third party (such as AF network element) of the results of network information monitoring, so that the third party (such as the provider of application services) can obtain the transmission status of user messages in the communication system based on the results of network information monitoring, so as to facilitate the third party to take corresponding actions, for example, when user messages are congested in the communication system, the sending rate of user messages is adjusted. It can be understood that in this application, "monitoring" can also be referred to as "monitoring" or "detection". When a third party needs to obtain the transmission status of user messages in the communication system, the third party (such as AF) can indicate the network information monitoring and open requirements to the PCF. After the PCF receives the network information monitoring and open requirements indicated by the AF, the PCF indicates to the SMF one or more SDFs for performing network information monitoring. The SMF configures the RAN and anchor UPF corresponding to the QoS Flow carrying the one or more SDF flows to perform network information monitoring (for example, the SMF can indicate to the RAN and anchor UPF the requirements for performing network information monitoring and open). QoS flow, that is, the QoS flow corresponding to the SDF used to perform network information monitoring. The RAN and anchor UPF corresponding to the QoS Flow may be the RAN and anchor UPF configured with the QoS Flow related information, for example, the RAN configures the QoS Profile of the QoS Flow, and the anchor UPF configures the packet detection rule (PDR) and QoS enforcement rule (QER) of the QoS Flow. Among them, the anchor UPF that performs network information monitoring may be one or more anchor UPFs in the PDU session to which these SDFs belong. For the sake of ease of description, this application refers to the anchor UPF that performs network information monitoring as the target anchor UPF. The following are two ways to monitor and open network information: 1. Quality of service monitoring (QoS Monitoring): QoS Monitoring includes the measurement of QoS parameters of QoS flows. PCF can enable QoS Monitoring based on third-party instructions or local configuration. When QoS Monitoring is enabled, PCF will generate an authorized QoS Monitoring policy for one or more SDFs, and indicate the QoS Monitoring policy to SMF through Policy and Charging Control (PCC) rules. After SMF receives the QoS Monitoring policy, SMF binds the above one or more data flows to an independent QoS Flow based on the QoS Monitoring policy, and configures the target anchor UPF and RAN for the QoS Flow to perform QoS Monitoring. QoS Monitoring mainly includes monitoring of packet delay, monitoring of congestion, monitoring of data rate, etc. 1. When monitoring packet delay, SMF instructs the target anchor point UPF and RAN to perform packet delay monitoring. The target anchor UPF and RAN will perform the following actions: (1) The target anchor UPF adds the time T1 at which the target anchor UPF sends the downlink data packet in the GPRS tunnelling protocol for the user plane (GTP-U) header of the downlink data packet. (2) After receiving the downlink data packet, the RAN records the time T2 when the downlink data packet is received, and records the time T1 carried in the GTP-U header of the downlink data packet. (3) When the RAN receives an uplink data packet belonging to the QoS Flow from the UE (e.g., an uplink data packet carrying the QFI in the GTP-U header), the RAN portion of the delay monitoring result (i.e., the delay of the path between the UE and the RAN), the time T3 when the RAN sends the uplink data packet, and the times T1 and T2 previously recorded by the RAN are encapsulated in the GTP-U header of the uplink data packet; or, if the RAN does not receive an uplink data packet belonging to the QoS Flow from the UE for a period of time (a locally configured time period), the RAN generates a virtual uplink data packet (or an empty packet, i.e., a data packet without valid data), and encapsulates the time T3 when the empty packet is sent, as well as the times T1 and T2 in the GTP-U header of the empty packet. (4) After receiving the uplink data packet sent by the RAN, the target anchor point UPF records the time T4 of receiving the uplink data packet, and calculates the round-trip delay between the RAN and the target anchor point UPF (if the time of each network element is not synchronized) or the uplink and downlink packet delay (if the time of each network element is synchronized) based on the time information (i.e., T1, T2, T3) contained in the GTP-U header of the uplink data packet. 2. When monitoring congestion, SMF instructs the target anchor point UPF and RAN to perform congestion monitoring. The target anchor point UPF and RAN will perform the following actions: (1) RAN measures the uplink / downlink congestion status of the air interface data radio bearer corresponding to the QoS flow. RAN encapsulates congestion information in the GTP-U header of the uplink data packet belonging to the QoS Flow (such as the uplink data packet carrying the QFI corresponding to the QoS Flow in the GTP-U header) and sends it to the target anchor point UPF. The congestion information is used to indicate the congestion status (such as the congestion degree). (2) The target anchor UPF extracts congestion information from the GTP-U header of the uplink data packet. 3. When performing data rate monitoring, the target anchor UPF measures the uplink and / or downlink data rate of each QoS flow based on the QoS detection request for the uplink and / or downlink data rate from the SMF. After completing the monitoring of QoS flow, QoS Monitoring can open the network information monitoring results (such as uplink and downlink packet delays, congestion information or data rate, etc.) to a third party (such as AF) through the application programming interface (API). 2. Low Latency, Low Loss and Scalable Throughput (L4S): L4S is a method of opening congestion information to a third party via user plane messages, so that the third-party server can dynamically perceive the network congestion situation and make corresponding adaptive bitrate adjustments in real time to ensure the user service experience. Specifically, the RAN monitors the congestion information of the QoS flow of the current data flow carrying a certain service. The RAN or UPF adds an explicit congestion notification marking (ECN marking) to the IP header of the uplink / downlink data packet of the service in proportion to the congestion information obtained by monitoring. The UE or server (such as EAS, AF / AS) makes adaptive bitrate adjustments based on the received data packets containing the ECN marking. Specifically, the congestion information can be the congestion information of the QoS Flow or the wireless data bearer corresponding to the QoS Flow. In particular, when UPF adds ECN marking, RAN needs to encapsulate the monitored network congestion information in the GTP-U header of the uplink data packet belonging to the QoS Flow (such as the uplink data packet with the QFI in the GTP-U header). UPF The congestion information is obtained from the GTP-U header, and an ECN mark is added according to the congestion information. Based on the above, during the network information monitoring process, RAN adds the acquired monitoring results (such as time T1, T2, T3 or congestion information, etc.) to the GTP-U header of the uplink data packet of QoS Flow and sends it to the UPF side. However, in a multi-session anchor point scenario, if the data transmission path of the PDU session is inserted into the diversion point UPF, different data flows of the same QoS flow may be diverted to different anchor point UPFs. Then when the access network device sends the network monitoring results of the access network to the UPF, it cannot guarantee that the monitoring results will eventually be sent to the target anchor point UPF (such as the designated PSA UPF), which may cause the monitoring results to reach the non-target anchor point UPF while the target anchor point UPF cannot obtain the monitoring results, resulting in the above-mentioned network information monitoring and open functions cannot be completed. The following are some examples of the above technical issues combined with several specific scenarios: Example 1: In the congestion information monitoring scenario of QoS Monitoring, the congestion information needs to be reported to the target anchor point UPF for external disclosure. After the access network equipment monitors and obtains the congestion information of the QoS Flow, it will add the congestion information to the uplink data packet of the QoS Flow, regardless of whether the data packet is sent to the target anchor point UPF. If the uplink data packet is forwarded by the diversion point UPF and then sent to other anchor point UPFs, the target anchor point UPF cannot receive the corresponding congestion information, which ultimately leads to the inability to complete the monitoring and disclosure of network congestion information. Example 2: In the QoS Monitoring packet delay monitoring scenario, after the access network device receives the time T1 and other information added by the target anchor UPF in the GTP-U header of the downlink data packet, it needs to add the time T2, T3 and other information in the GTP-U header of the uplink data packet and report it to the target anchor UPF. Similarly, when the access network device recognizes that the QFI in the GTP-U header of an uplink data packet is the QFI of the QoS flow used to perform network information monitoring, it will add the time T2, T3 and other information to the data packet, but the uplink data packet may be diverted to a non-target anchor UPF, resulting in the target UPF being unable to measure the delay, and ultimately the network information monitoring and opening cannot be completed. Example 3: In the UPF L4S scenario, if the congestion information detected by the access network device is reported only to one anchor UPF, other anchor UPFs will not perform ECN marking, which will result in an incorrect proportion of ECN-marked packets arriving at the UE or server. For example, if the congestion ratio is 50%, 50% of all downlink packets need to be marked with ECN. However, there are actually two anchor UPFs, and RAN only notifies one of them of the congestion information, so only one anchor UPF marks 50% of the downlink data packets passing through it with ECN. Assuming that the traffic passing through the two anchor UPFs is 40% and 60% respectively, if the UPF with 40% of the traffic is notified, the final proportion of packets marked with ECN is 40%*50%=20%. After receiving it, the UE will determine that the congestion ratio is 20% instead of 50%, resulting in an incorrect ratio and inaccurate network information monitoring and opening results. In view of this, a technical solution of an embodiment of the present application is provided to ensure that the monitoring results reported by the access network device reach the target session anchor point (i.e., the session anchor point for performing network information monitoring and opening), and to ensure the reliability of network information monitoring and opening in the diversion point insertion scenario. Referring to FIG. 3 , a flow chart of a communication method provided in an embodiment of the present application includes: S101. PCF sends first information to SMF, and SMF receives the first information from PCF. Optionally, when the PCF receives the network information monitoring requirement (or the network information monitoring and opening requirement) from the AF, the PCF sends the first information to the SMF. The first information is used to configure network information monitoring for a target data stream, and the target data stream includes one or more data streams. For example, the target data stream is SDF1 shown in FIG. 4A , or is SDF1 and SDF2 shown in FIG. 4A . For example, the target data stream is SDF1 and SDF2 shown in FIG. 4B or FIG. 4C . When the target data stream includes multiple data streams, the target data stream corresponds to multiple session anchor points. Optionally, the target data stream corresponds to a first data session and the first data session corresponds to multiple session anchor points. When the target data stream includes one data stream, the target data stream corresponds to one session anchor point. Wherein, the definition of data stream can refer to the relevant introduction above. For ease of description, the embodiment of the present application takes a data stream corresponding to an IP quintuple as an example. In other words, a data stream is a data stream composed of data packets of the same IP quintuple (i.e., the data packets in a data stream have the same source IP address, destination IP address, source port number, destination port number, and protocol). The embodiment of the present application is equally applicable to other situations, such as a data stream corresponding to an IP triplet (i.e., the data packets in a data stream have the same source / destination IP address, source / destination port number, protocol or source IP address, destination IP address, and protocol). The session anchor point corresponding to the data flow may refer to: the data packets in the data flow are transmitted through the session anchor point, or the data flow is transmitted through a tunnel including the session anchor point, or the data flow is forwarded and routed to the session anchor point by the diversion point UPF, etc. The network information monitoring in the embodiments of the present application may be the network information monitoring part of the network information monitoring and open scheme introduced above. For example, network information monitoring includes the process in which the access network device detects network information (such as time information, congestion information, etc.) and reports the monitoring results. The introduction to the network information monitoring and open scheme can refer to the introduction to QoS Monitoring or L4S above, which will not be repeated here. Of course, with the evolution of communication systems, network information monitoring can also be implemented in other ways. For the sake of ease of description, this application uses network information monitoring as Take the network information monitoring part of the network information monitoring and open plan as an example. In a possible implementation, the first information may be a network information monitoring rule, or a PCC rule indicating a network information monitoring rule, or a PCC rule for other indications, and this application does not limit this. The PCC rule includes a data flow template, which is used to indicate the specified policy control and processing for one or more data flows corresponding to the data flow template. In this application, the data flow indicated in the PCC rule is also referred to as the data flow corresponding to the PCC rule or the data flow or target data flow included in the PCC rule. The PCC rule may include a network information monitoring rule (or a network information monitoring and open requirement), for example, the PCC rule includes a QoS monitoring policy or an indication for ECN marking for L4S, etc. Alternatively, the network information monitoring rule may also be the PCC rule itself. The network information monitoring rule may also be referred to as a network information monitoring policy or other names. Among them, the QoS Monitoring policy may include one or more of the following: QoS parameters that need to be monitored (such as uplink / downlink data packet delay, loopback data packet delay, etc.), reporting frequency (including event triggering and periodic triggering), notification target (such as NEF, AF, local NEF, etc.), direct event notification indication (used to instruct UPF to directly notify AF or local NEF of the monitoring results through its service-based interface). The indication for ECN marking for L4S is an indication information for indicating that network information monitoring or opening is performed based on L4S. When the PCC rule includes the indication for ECN marking for L4S, the PCC rule may further include another indication information for indicating that uplink ECN marking or downlink ECN marking is performed. After receiving the PCC rule, the SMF can perform network information monitoring on the target data flow according to the QoS Monitoring policy or indication for ECN marking for L4S in the PCC rule. The target data stream corresponds to the first data session, which means that the target data stream is transmitted through the first data session, or the target data stream is carried in the first data session for transmission. The first data session may specifically be a PDU session. Of course, with the evolution of the communication system, the first data session may also be other types of sessions. For ease of description, this application mainly takes the first data session as an example of a PDU session. In the following, unless otherwise specified, "data session" may be interchangeable with "PDU session". The multiple session anchor points corresponding to the first data session refer to the number of session anchor points (session anchor points can also be referred to as anchor points) for the first data session to access the data network (DN). For example, when the first data session is a PDU session, the session anchor point can specifically be a PSA, and the specific implementation of PSA can be a UPF with a session anchor function (i.e., an anchor UPF). For ease of description, this application mainly takes the example that the session anchor point is an anchor UPF. In the following, unless otherwise specified, "session anchor point" can be interchanged with "anchor UPF". In a possible implementation, the target data flow corresponds to a first data session and the first data session corresponds to multiple session anchors, including: the target data flow corresponds to a second quality of service flow in the first data session. The session management function network element also determines that the second quality of service flow corresponds to multiple session anchors. In some embodiments, the quality of service flow may be a QoS flow. With the evolution of communication systems, the quality of service flow may also have other names, which are not limited in this application. For ease of description, the following mainly takes the quality of service flow as an example of a QoS flow. Unless otherwise specified, the quality of service flow can be interchangeable with the QoS flow. For example, the second quality of service flow may be QoS flow#0 shown in Figure 4A. The first data session may have one or more quality of service flows, and the second quality of service flow is a quality of service flow in the first data session. The second quality of service flow is carried in the first data session, or the second quality of service flow is transmitted through the first data session. The target data flow for network information monitoring is carried in the second quality of service flow in the first data session. Multiple session anchor points refer to at least two session anchor points, that is, two or more session anchor points. For example, referring to FIG4A , which is an example in which the target data flow corresponds to the second quality of service flow and the second quality of service flow corresponds to multiple session anchors, the target data flow carried by the second quality of service flow QoS flow#0 in the first data session specifically includes SDF#1 and / or SDF#2, and QoS flow#0 corresponds to two session anchors PSA1 and PSA2. One or all of SDF1 and SDF2 are used for network information monitoring. In one implementation method, the second quality of service flow corresponds to multiple session anchor points, and the second quality of service flow may correspond to multiple session anchor points before the SMF receives the first information from the PCF. In this case, the SMF executes S102 after receiving the first information, and optionally, the action of the SMF receiving the first information triggers S102. In one implementation method, the second quality of service flow corresponds to multiple session anchor points, which may be that the second quality of service flow will correspond to multiple session anchor points. For example, after the SMF receives the first information, the second quality of service flow is inserted into the diversion point (such as ULCL or BP). After receiving the first information and determining that the second quality of service flow is inserted into the diversion point, the SMF executes S102. Optionally, the action of inserting the diversion point triggers S102S. Before the SMF receives the first information, the second quality of service flow is not inserted into the diversion point, and the second quality of service flow corresponds to only one session anchor point. That is, all data packets in the second quality of service flow are forwarded to the same session anchor point. Exemplarily, when the SMF receives the first information to monitor the network information of the target data flow, because the UE finds triggering factors such as edge application server, link congestion, node overload or local configuration, the SMF decides to add a diversion point to the current session and split the second quality of service flow to different session anchor points, that is, forward the data packets in the second quality of service flow to different session anchor points. S102: The SMF creates at least one quality of service flow for the first data session. Specifically, when the target data flow is a data flow, the SMF may create one or more quality of service flows. When the target data flow is a plurality of quality of service flows, the SMF creates a plurality of quality of service flows (or the SMF creates at least two quality of service flows). Among them, the first service quality flow in at least one service quality flow corresponds to one or more data flows among multiple data flows, the first service quality flow is used to perform network information monitoring on the data flow carried in the first service quality flow, and the first service quality flow corresponds to a session anchor point among multiple session anchor points. In a specific implementation, network information monitoring is performed on the data flow carried in the first quality of service flow, and specifically, network information monitoring is performed on the first quality of service flow. In other words, the network information monitoring result of the first quality of service flow can be used as the network information monitoring result of the data flow carried in the first quality of service flow. The number of the first quality of service flows may be one or more. In other words, when multiple quality of service flows are created, only one quality of service flow among the multiple quality of service flows created may be used to perform network information monitoring, or multiple quality of service flows among the multiple quality of service flows created may be used to perform network information monitoring, or all quality of service flows among the multiple quality of service flows created may be used to perform network information monitoring, which is not limited in the embodiments of the present application. In one implementation, the SMF creates quality of service flows for the data flows in the second quality of service flow that are diverted to different session anchor points respectively. Take the second quality of service flow including SDF1, SDF2 and SDF3, and the target data flow as SDF1 and SDF2 as an example: Example 1, as shown in FIG5A , SDF1 and SDF2 are shunted to PSA1, and SDF3 is shunted to PSA2, then SMF may create two quality of service flows, wherein the first quality of service flow includes SDF1 and SDF2, and the other quality of service flow includes SDF3. Example 2, as shown in FIG5B , SDF1 is shunted to PSA1, and SDF2 and SDF3 are shunted to PSA2, then SMF can create two first quality of service flows, one of which includes SDF1 and the other includes SDF2 and SDF3, and delete the second quality of service flow. Alternatively, SMF can create two first quality of service flows and modify the second quality of service flow, one of which includes SDF1 and the other includes SDF2, and the modified second quality of service flow includes SDF3. It can be understood that the first quality of service flow includes one or more of the target data flows, the first quality of service flow corresponds to only one session anchor point, and other quality of service flows created can correspond to one or more session anchor points. The first quality of service flow can only include the target data flow quality of service flow, or the first quality of service flow can include the target data flow and other data flows. In some embodiments, if the second quality of service flow has not been created before S102, when S102 is executed, the SMF may create the at least one quality of service flow and not create the second quality of service flow. In some embodiments, if the second quality of service flow already exists before S102, S102 may be implemented in a variety of ways, and several possible implementations are listed below: 1) The SMF deletes the second quality of service flow, and creates the at least one quality of service flow, where the at least one quality of service flow is, for example, a plurality of quality of service flows. 2) The SMF modifies the second quality of service flow and creates at least one new quality of service flow, wherein the created at least one quality of service flow includes the modified second quality of service flow and the at least one new quality of service flow. 3) The SMF divides the second quality of service flow into multiple new quality of service flows, and the at least one quality of service flow created is the multiple new quality of service flows. 4) The SMF modifies the second quality of service flow into multiple new quality of service flows, and creates at least one quality of service flow that is the multiple new quality of service flows. Of course, the above are just examples and are not limited to these. In some implementations, the SMF may create multiple quality of service flows for the first data session according to the diversion rule. In this case, each of the multiple quality of service flows created corresponds to a session anchor point; or, each first quality of service flow in the multiple quality of service flows created corresponds to a session anchor point, and other quality of service flows in the multiple quality of service flows may correspond to one or more session anchor points, each first quality of service includes one or more target data flows, and other quality of service flows do not include target data flows. For example, the first information is used by SMF to perform network information monitoring on SDF1 and SDF2. Before SMF receives the first information, QoS flow#0 (i.e., the second quality of service flow) SDF1, SDF2, SDF3, SDF4, of which SDF1, SDF3 are diverted to PSA1, and SDF2, SDF4 are diverted to PSA2. To PSA1. After receiving the first information, SMF can create QoS flow#1 and QoS flow#2, where SDF1 and SDF3 belong to QoS flow#2, and SDF2 and SDF4 belong to QoS flow#1, or SMF can make SDF1 belong to QoS flow#2, SDF2 belong to QoS flow#1, and SDF3 and SDF4 belong to QoS flow#0. The diversion rule is used to indicate the traffic / data / data packets forwarded to different session anchor points. Alternatively, the diversion rule is used to route / forward (UE's) data / data packets to different session anchor points. Exemplarily, the diversion rule can be at least one of traffic routing rules, traffic detection rules, (IPv6 multi-homed routing rule), traffic detection rules, traffic routing rules, packet detection, forwarding action rule, etc. For example, when the diversion point is ULCL, the diversion rule can be a traffic routing rule. The SMF determines which data flows correspond to which session anchors according to the traffic routing rules, and then creates different service quality flows for data flows corresponding to different session anchors according to the correspondence between the data flows and the session anchors. In a possible example, when creating multiple quality of service flows, the SMF may also consider the attributes of the data flows. Exemplarily, the attributes of the data flows corresponding to the same quality of service flow in the multiple quality of service flows created are the same. Among them, the attribute is, for example, whether the data flow supports ECN marking (supporting ECN marking). For example, SMF cannot correspond data flows that support ECN marking and do not support ECN marking to the same quality of service flow, even if the session anchor points corresponding to these data flows are the same. For example, for the above example as shown in Figure 4B, after receiving the first information, SMF can create QoS flow#1 and QoS flow#2 according to Figure 5A, where SDF1 and SDF2 belong to QoS flow#1, and SDF3 belongs to QoS flow#2. However, if SDF1 supports ECN marking, and SDF2 does not support ECN marking, SMF can create QoS flow#1, QoS flow#2, and QoS flow#3, so that SDF1 belongs to QoS flow#1, SDF2 belongs to QoS flow#2, and SDF3 belongs to QoS flow#3, as shown in Figure 5C. In another implementation, the SMF creates a quality of service flow for each data flow in the second quality of service flow. Exemplarily, the first information is used by the SMF to perform network information monitoring on multiple data flows, the number of multiple service quality flows created is equal to the number of data flows in the second service quality flow, and the multiple service quality flows created correspond one-to-one to the data flows in the second service quality flow. It can be understood that before SMF creates multiple service quality flows, even if SMF determines according to the diversion rules that different data flows among multiple data flows are diverted to the same session anchor point, it is necessary to create multiple service quality flows so that the different data flows diverted to the same session anchor point are divided into different service quality flows. For example, a quality of service flow is created for each of SDF1, SDF2, and SDF3 shown in FIG. 4B or FIG. 4C. If the second quality of service flow contains other data flows besides the target data flow, the quality of service flow carrying of the other data flows also needs to be considered. In this case, the other quality of service flows can be carried in the original quality of service flow (i.e., the second quality of service flow), or a quality of service flow can be created for each data flow in the other data flows. For example, as shown in FIG. 5D , a quality of service flow (ie, Qos flow#1 and Qos flow#2) is created for each of SDF1 and SDF2, while SDF3 is still carried in the second quality of service flow Qos flow#0. In one possible design, when the first information is used by the SMF to perform network information monitoring on multiple data streams (i.e., the number of data streams indicated in the first information for performing network information monitoring is multiple), the SMF can modify the first data session so that each of the multiple data streams for performing network information monitoring corresponds to one quality of service stream among the multiple quality of service streams created. For example, referring to FIG. 6 , after S101 , S103 to S104 may be further executed: S103. The SMF sends second information to the PCF according to the first information; correspondingly, the PCF receives the second information from the SMF. The second information is used to instruct the PCF to generate multiple third information. The first information and the third information may be network information monitoring rules. The first information and the third information may also be PCC rules indicating network information monitoring rules, or may be PCC rules for other indications, which are not limited in this application. For example, the network information monitoring rule may be a QoS Monitoring policy or an indication for ECN marking for L4S, etc. (see above for details). In an alternative implementation, the SMF may not send the second information to the PCF based on the first information, and the PCF may also receive the second information from other network elements such as the AMF, AF, NEF, UDR, etc., which is not limited in the embodiment of the present application. S104. PCF sends multiple third information to SMF, and correspondingly, SMF receives multiple third information. It can be understood that the steps marked with dotted lines in the drawings of the present application are optional steps. For ease of description, the following takes the example where the third information is a network information monitoring rule. Specifically, SMF receives multiple network information monitoring rules generated for multiple data streams from PCF, each of the multiple network information monitoring rules is used to perform network information monitoring on the corresponding one or more data streams, and the one or more data streams corresponding to each of the multiple network information monitoring rules correspond to a session anchor point among the multiple session anchor points. Among them, each network information monitoring rule in the multiple network monitoring rules corresponds to one or more data flows, and different network information monitoring rules correspond to different data flows. Optionally, the one or more data flows corresponding to each network information monitoring rule may be the data flows indicated in the PCC rule. It can be understood that the SMF can send the second information to the PCF before creating multiple quality of service flows (such as steps S103 to S104 are performed before step S102), and the SMF can also send the second information to the PCF after creating multiple quality of service flows (such as steps S103 to S104 are performed after step S102). The embodiment of the present application does not limit the order in which the SMF creates multiple quality of service flows and the SMF modifies the first data session. Different from the first information, the target data flow in the first information (for ease of distinction, referred to as the first target data flow hereinafter) corresponds to multiple session anchor points. For example, in S101, SMF receives PCC rule0, PCC rule0 includes SDF1 and SDF2, SDF1 corresponds to PSA1, and SDF2 corresponds to PSA2, while the data flow in the third information (for ease of distinction, referred to as the second target data flow hereinafter) corresponds to one session anchor point. For example, in S104, SMF receives PCC rule1, PCC rule1 only includes SDF1, and SDF1 corresponds to PSA1. For example, take the scenario shown in Figure 4A as an example: In S101, PCF sends PCCrule 0 (i.e., the first information) to SMF, PCCrule0 indicates to monitor the network information of SDF1 and SDF2 (for example, PCC rule 0 includes SDF1 and SDF2). Before SMF receives PCCrule 0, SDF1 and SDF2 belong to QoS flow#0, as shown in Figure 4A, where SDF1 is diverted to PSA1 and SDF2 is diverted to PSA2. After receiving PCCrule 0, SMF can send a second message to PCF, instructing PCF to send multiple PCC rules or instructing PCF to resend PCC rules. After receiving the second message, PCF sends PCCrule 1 and PCCrule 2 (i.e., two third messages) to SMF. PCC rule 1 indicates that network information monitoring is performed on SDF1, that is, PCC rule 1 corresponds to PSA1; PCC rule 2 indicates that network information monitoring is performed on SDF2, that is, PCC rule 2 corresponds to PSA2. In this way, PCC rules can be bound one-to-one to QoS flows that are not diverted (for example, PCC rule 1 is bound to QoS flow#1, and PCC rule 2 is bound to QoS flow#2), so that SDF1 belongs to QoS flow#1 and SDF2 belongs to QoS flow#2. In some embodiments, the second target data stream includes a portion of the first target data stream and other data streams except the first target data stream, the second quality of service stream includes other data streams except the first target data stream, and the second information includes an identifier of the second target data stream. For another example, in S101, PCF sends PCCrule 0 (i.e., the first information) to SMF. PCCrule 0 indicates that network information monitoring is to be performed on SDF1 and SDF2 (for example, PCC rule 0 includes SDF1 and SDF2). Before SMF receives the first information, SDF1, SDF2, and SDF3 all belong to QoS flow#0 (i.e., the second quality of service flow), in which SDF1 and SDF3 are diverted to PSA1, and SDF2 is diverted to PSA2. After receiving the first information, SMF may send a second information to PCF, instructing PCF to send multiple PCC rules or instructing PCF to resend PCC rules. After receiving the second information, PCF sends PCCrule 1 and PCCrule 2 (i.e., two third information) to SMF. PCC rule1 indicates that network information monitoring is to be performed on SDF1 and SDF3, i.e., PCC rule 1 corresponds to PSA1; PCC rule 2 indicates that network information monitoring is to be performed on SDF2, i.e., PCC rule 2 corresponds to PSA2. SMF binds PCC rule 1 to QoS flow#1 and PCC rule 2 to QoS flow#2. Alternatively, PCC rule 1 indicates that network information monitoring is performed on SDF1, that is, PCC rule 1 corresponds to PSA1; PCC rule 2 indicates that network information monitoring is performed on SDF2, that is, PCC rule 2 corresponds to PSA2. SMF binds PCC rule 1 to QoS flow#1 and PCC rule 2 to QoS flow#2. The SDF included in the second information corresponds to the SDF included in the PCC rule. Optionally, the second information includes a set of data flow identifiers. The PCF generates a plurality of network information monitoring rules according to the set of data flow identifiers. Further optionally, the set of data flow identifiers includes an identifier of a data flow corresponding to at least one session anchor point among the multiple session anchor points. For example, each network information monitoring rule includes an identifier of one or more data flows corresponding to one session anchor point among the multiple session anchor points, and different network information monitoring rules include an identifier of one or more data flows corresponding to different session anchor points. In a specific implementation, the second information may include at least one identification set, wherein each identification set may indicate one or more data streams. For example, each identification set is an identification set of data streams corresponding to a session anchor point in the multiple data streams. The specific form of the identification set, such as a range or a list, is not limited in the embodiments of the present application. For example, the set consisting of SDF1, SDF2, and SDF3 can be represented by a list (SDF1, SDF3), or by SDFrange1, where SDFrange1 corresponds to the range of SDF1 and SDF3, and the second information also includes SDF2, represented by SDFrange2. The second information is used to indicate that a PCC rule is generated for SDFrange1 (SDF1, SDF3) and SDFrange2 (SDF2), respectively. SDF can be identified by the above-mentioned service data flow template or packet filter set. Optionally, the second information may further include first indication information, where the first indication information instructs the PCF to send multiple third information. In some embodiments, all the data flows indicated in the second information are multiple data flows indicated in the first information for performing network information monitoring. In this case, the second information may include a set of identifiers of data streams corresponding to different session anchor points in the multiple data streams. The identifiers of one or more data streams included in different third information in the three information respectively correspond to the identifier sets of data streams corresponding to different session anchor points included in the second information. For example, the second information includes a list (SDF1, SDF3) and a list (SDF2). (SDF1, SDF3) corresponds to PSA1 and (SDF2) corresponds to PSA2; or, (SDF1, SDF3) corresponds to reason value 1 and (SDF2) corresponds to reason value 2, where the reason value can be an indication information used to indicate the role of the corresponding SDF / the action required of the PCF / the reason for initiating this information, etc. After receiving the second information, the PCF sends two third information, one of which includes SDF1 and SDF3, and the other includes SDF2. In some other embodiments, the data stream indicated in the second information includes not only the data stream indicated in the first information for performing network information monitoring, but also other data streams, such as other data streams carried in the second quality of service flow but requiring network information monitoring. In this case, the PCF may identify which of the data flows indicated by the second information are data flows for which network information monitoring needs to be performed, and send a plurality of third information for these data flows. For example, if the second information includes a list (SDF1, SDF3) and a list (SDF2), but the first information does not include SDF3, the PCF sends three third information, including SDF1, SDF2, and SDF3, and instructs to perform network information monitoring on SDF1 and SDF2. Alternatively, the PCF sends three third information, including (SDF1, SDF3) and SDF2, and instructs to perform network information monitoring on (SDF1, SDF3) and SDF2. After the SMF receives the multiple third information and creates the multiple quality of service flows, the SMF binds the third information and the created multiple quality of service flows. The above method realizes the remapping of data flow and service quality flow by modifying the data session (that is, each data flow in the multiple data flows used to perform network information monitoring corresponds to a service quality flow in the multiple service quality flows created), which can be compatible with the existing PCC binding rules (that is, one PCC rule is bound to one service quality flow), with few changes and high applicability. In another possible design, when the first information is used by the SMF to perform network information monitoring on one or more data flows, the SMF may not modify the first data session, but directly create one of the multiple quality of service flows corresponding to each data flow used to perform network information monitoring. Exemplarily, the first information is a PCC rule, and the SMF directly binds only the one PCC rule to the multiple created service quality flows. Specifically, for example, the SMF can bind the QoS parameters (such as guaranteed flow bit rate (Guaranteed Flow Bit Rate, GFBR), packet delay budget (Packet Delay Budget, PDB) or packet error rate (Packet Error Rate, PER)) in the PCC rule to each of the multiple created service quality flows, and each data flow for performing network information monitoring corresponds to one of the multiple created service quality flows. The above method directly corresponds the data flow used to perform network information monitoring to the created service quality flow, which can reduce information interaction and improve the efficiency of network information monitoring. In another possible design, when the PCF receives the network information monitoring (or network information monitoring) requirement indicated by the AF, the PCF may send the first information (i.e., S101) with data flow as the granularity, that is, the first information is only used for the SMF to perform network information monitoring on one data flow. In this case, after the SMF receives the first information, since there is only one data flow for performing network information monitoring, the data flow can be mapped to only one quality of service flow. For example, the PCF receives an instruction from the AF to perform network information monitoring on SDF1 and SDF2. In S101, the PCF generates two first information, including SDF1 and SDF2 respectively. In the above manner, by performing network information monitoring on only one data flow, the data session may not be modified, information interaction may be reduced, and there is no need to modify the PCC binding rule (ie, one PCC rule is bound to one service quality flow), thereby improving the efficiency of network information monitoring. It can be understood that when SMF actually creates multiple service quality flows, it needs to interact with other network elements or devices (such as access network equipment, UE, diversion points, session anchor points, etc.). The process of SMF creating service quality flows can refer to the relevant 3GPP technical specifications, which will not be introduced here. Optionally, the SMF may also configure the access network device and / or at least one of the multiple session anchor points according to the network information monitoring rules to perform network information monitoring based on at least one of the multiple quality of service flows. For example, referring to FIG. 7 , after creating multiple quality of service flows (ie, S102 ), S105 to S106 are also included: S105. The SMF sends first reporting information to at least one session anchor point, where the first reporting information is used to instruct execution of network information monitoring (or network information monitoring and opening). The first reporting information may carry an identifier of a first quality of service flow (such as QFI). For example, the SMF notifies the anchor UPF to perform network information monitoring (or network information monitoring and opening) by sending an N4 session modification request (N4 session modification request) to the anchor UPF corresponding to the first service quality flow. For example, the N4 session modification request is specifically used to configure the QoS monitoring per QoS flow control information in the session report rule (session report rule) of the anchor UPF. It can be understood that the number of first service quality flows can be one or more, so the SMF may send the first reporting information to one or more session anchor points. S106. The SMF sends second reporting information to the access network device, where the second reporting information is used to instruct the access network device to measure and report the corresponding network information monitoring result. The second reporting information may carry an identifier of the first quality of service flow (eg, QFI). For example, the SMF notifies the access network device to provide monitoring results (such as RAN part result) through the N2 message, that is, it indicates that the RAN needs to notify the target anchor point UPF of the monitoring results. The subsequent access network devices and session anchor points cooperate with each other to complete network information monitoring (or network information monitoring and opening). For details, please refer to the introduction of QoS Monitoring or L4S above, which will not be repeated here. Optionally, before S102 or before S103, the following is also performed: S107, SMF determines that the first information is used by SMF to perform network information monitoring on the target data stream, and the target data stream includes one or more data streams, and the target data stream corresponds to multiple session anchor points. For example, SMF determines based on the first information that the one or more data streams correspond to the second service quality stream in the first data session, and network information monitoring is required for the one or more data streams, and the second service quality stream corresponds to multiple session anchor points (that is, the second service quality is shunted or inserted into the shunting point). Figure 7 takes the execution of S107 before S103 as an example. For example, after the SMF receives a PCC rule (i.e., the first information described above), the PCC rule indicates the need for network information monitoring (or network information monitoring and opening). The SMF determines whether the service quality flow (i.e., the second service quality flow described above) in which the data flow used to perform network information monitoring in the PCC rule is located is diverted (i.e., whether a diversion point is inserted). If so, execute step S102 above. On the contrary, if the quality of service flow in which the data flow used to perform network information monitoring belongs (ie, the second quality of service flow mentioned above) is not split, the network information monitoring can be performed directly based on the second quality of service flow. Optionally, after S105 or S106, the following is further performed: S108, at least one session anchor point and access network device, etc. perform network information monitoring. The specific implementation of S105, S106, and S108 can refer to the introduction of QoS Monitoring or L4S above and the description in 3GPP TS23.501, TS23.502, TS23.503, etc., which will not be repeated here. In the above scheme, when the SMF receives a network information monitoring indication (such as the first information), if the data flow used to perform network information monitoring corresponds to multiple session anchor points (for example, the service quality flow corresponding to the data flow performing network information monitoring is diverted), then multiple service quality flows can be created to ensure that the service quality flow used to perform network information monitoring only corresponds to one session anchor point among the multiple session anchor points. In this way, it can be ensured that the monitoring results reported by the access network device reach the target session anchor point (that is, the session anchor point performing network information monitoring), thereby ensuring the reliability of network information monitoring (or network information monitoring and opening) in the diversion point insertion scenario. It can be understood that in addition to the network information monitoring scenario, other scenarios may also trigger the PCF to generate multiple PCC rules. For example, due to the insertion of the diversion point, the core network packet delay budget (core network packet delay buget, CNPDB) of the RAN to PSA1 and PSA2 paths in the session is different. The SMF triggers the creation of different QoS Flows for the data flows corresponding to PSA1 and PSA2, and instructs the PCF to generate multiple PCC rules for the created QoS Flows. For another example, due to the AF's policy, the AF instructs the PCF to generate different PCC rules for different data flows to correspond these data flows to different QoS Flows. For another example, after the NEF receives the AF indication, the NEF generates a second information according to the AF indication, instructing the PCF to generate different PCC rules for different data flows. Correspondingly, referring to FIG8 , an embodiment of the present application further provides a communication method, which may include: S110, the first network element sends second information to the PCF, and the PCF network element receives the second information; The first network element includes, for example, but is not limited to, AF / AMF / NEF / UDR / SMF. The specific content of the second information can be referred to above and will not be described in detail here. S120. The PCF generates a plurality of PCC rules according to the second information. The specific implementation of the PCF generating multiple PCC rules according to the second information is referred to above and will not be repeated here. S130. The PCF sends the multiple PCC rules to the SMF, and the SMF receives the multiple PCC rules. For the specific implementation method after SMF receives multiple PCC rules, reference may be made to the relevant content after SMF receives multiple third information above, and the embodiments of the present application will not be repeated here. For the above implementation methods, please refer to the relevant content above and will not be repeated here. Through the above solution, PCF can adjust the generation of PCC rules according to the instructions of other network elements (such as AF / AMF / NEF / UDR / SMF, etc.). Compared with PCF generating PCC rules according to local policies and logic, it can consider the impact of more information and improve the reliability of communication. Referring to FIG. 9 , another communication method provided in an embodiment of the present application includes: S201: An access network device sends a first data packet, and a diversion point receives the first data packet. The first data packet carries reporting information, and the reporting information is used to notify the access network device of the monitoring result. It is understandable that the reporting information can also be replaced by other names, such as notification information, etc., which is not limited in the embodiment of the present application. Optionally, the reporting information is, for example, a monitoring result. The first data packet is carried in a second quality of service flow, the second quality of service flow corresponds to a plurality of session anchor points, and the first data packet corresponds to a first session anchor point. In an embodiment of the present application, the monitoring result of the access network device may specifically be the monitoring result obtained by the access network device performing network information monitoring, such as but not limited to the access network part result (RAN part result), or congestion information (congestion information) or QoS notification event (QoS notification event), etc. It can be understood that in different network information monitoring scenarios, the monitoring results reported by the access network device may be different. For example, in the packet delay monitoring scenario of QoS Monitoring, the monitoring result may be time information (such as T1, T2, T3, etc. introduced above). In this scenario, after the time information is reported to the session anchor point, the session anchor point also needs to calculate the network information monitoring result based on the time information, such as calculating the delay from UE to UPF. For example, in the congestion information monitoring or L4S scenario of QoS Monitoring, the monitoring result may be congestion information. In this scenario, the congestion information is the network information monitoring result. The first data packet carries the reporting information specifically by: the header of the first data packet carries the reporting information. For example, the reporting information is carried in the GTP-U header of the first data packet. S202: The diversion point sends a second data packet to the second session anchor point, and the second session anchor point receives the second data packet. Among them, the second data packet carries notification information, and the second data packet is carried on the second service quality flow; the second data packet corresponds to the second session anchor point, the first session anchor point is different from the second session anchor point, and the second service quality flow corresponds to multiple session anchor points including the first session anchor point and the second session anchor point. It can be understood that the reporting information carried in the second data packet is determined according to the reporting information carried in the first data packet. Specifically, the reporting information carried in the second data packet may be the same as or different from the reporting information carried in the first data packet. The shunt point sends a second data packet to the second session anchor point, including: the shunt point sends the second data packet to the second session anchor point according to the reporting information in the first data packet. The second data packet can be a data packet of a data flow corresponding to the second session anchor point in the second quality of service flow, or it can be an empty data packet generated by the shunt point. For example, after receiving the first data packet, the shunt point stores the reporting information in the first data packet, waits for a second data packet sent to the second session anchor point, and carries the reporting information in the GTP-U header of the second data packet, or, after waiting for a period of time and still no second data packet is sent to the second session anchor point, an empty packet sent to the second session anchor point is generated, and the reporting information is carried in the GTP-U header of the empty data packet, or, after receiving the first data packet, the shunt point generates an empty packet sent to the second session anchor point, and carries the reporting information in the GTP-U header of the empty data packet. The reporting information in the first data packet can be the monitoring result of the access network device. The above is an example of the shunt point sending the second data packet to the second session anchor point, and other methods are not limited. To ensure that the reporting information is sent to the second session anchor point, the split point can send the second data packet in any of the following ways: In one possible implementation, the diversion point may only report the monitoring results of the access network device to the second session anchor point, where the target anchor point is the session anchor point that performs network information monitoring (or network information monitoring and opening), thereby ensuring that the second session anchor point can obtain the monitoring results. The fourth information is used to indicate at least one session anchor point that reports the network information monitoring results, referred to as the second session anchor point. The at least one session anchor point may be part or all of the session anchor points corresponding to the second service quality flow, depending on the configuration of the SMF for the second session anchor point. In this way, the fourth information may include the identifier of at least one session anchor point for reporting network information monitoring results. Taking the session anchor point as UPF as an example, the identifier of the session anchor point may be one or more of the identifier of the UPF, the address of the UPF, the tunnel information of the UPF, or the tunnel identifier of the UPF. The identifier of the session anchor point may also be the source or destination IP address of the data stream. For example, when ULCL is diverted, the data stream with the destination IP address 1 is diverted to the session anchor point 1. The SMF may send the IP address 1 to the diversion point. The diversion point determines that the session anchor point corresponding to the data packet is anchor point 1 based on the IP address 1 in the received data packet and the diversion rule. Optionally, the fourth information may further include indication information, used to instruct the diversion point to report the reporting information from the access network device to the second session anchor point. In another possible implementation, the diversion point can report the monitoring results of the access network device to all session anchor points corresponding to the second service quality flow. Since the second session anchor point belongs to the session anchor point corresponding to the second service quality flow, this method can also ensure that the second session anchor point can obtain the monitoring results. In this way, the fourth information may include an identifier of at least one session anchor point used to report network information monitoring results; and / or, the fourth information may include an indication information, which is used to indicate that the session anchor points used to report network information monitoring results (or for receiving reported information) are all session anchor points corresponding to the second service quality flow, or to indicate the diversion point to report the reported information from the access network device to all session anchor points. It can be understood that when the second session anchor point is all session anchor points corresponding to the second service quality flow, there is no difference between the diversion point reporting the monitoring results of the access network device only to the second session anchor point and the diversion point reporting the monitoring results of the access network device to all session anchor points corresponding to the second service quality flow. For the packet delay monitoring scenario of QoS Monitoring, the reporting information carried in the first data packet includes the time when the third data packet leaves the second session anchor point (T1), the time when the third data packet arrives at the access network device (T2), and the time when the first data packet leaves the access network device (T3). In one possible implementation, when the time difference between the diversion point receiving the first data packet and the diversion point generating (or sending) the second data packet does not exist or can be ignored, the time information carried in the first data packet and the second data packet can be the same, such as T1, T2, T3. For example, when the diversion point receives the first data packet (carrying T1, T2, and T3), it immediately generates one or more empty packets (the number of empty packets is the same as the number of at least one session anchor point used to report network information monitoring results), and adds T1, T2, and T3 to the GTP-U headers of all empty packets (for example, PSA2 sends a downlink delay QoS Monitoring packet, and this RAN reporting information is a reply to PSA2, then the diversion point generates an empty packet, adds T1, T2, and T3 to the GTP-U header of the empty packet, and sends the empty packet to PSA2), and sends empty packets to all anchor point UPFs used to report network information monitoring results. In another possible implementation, when the time difference between the diversion point receiving the first data packet and the diversion point generating (or sending) the second data packet exists or cannot be ignored, the second data packet, in addition to carrying the reporting information (T1, T2, T3) in the first data packet, also includes the time when the first data packet arrives at the diversion point (Tx) and the time when the second data packet leaves the diversion point (Ty). For example, when the diversion point receives the first data packet (carrying T1, T2, T3), it records the time Tx when the first data packet arrives at the diversion point. When waiting for an uplink packet or waiting for a certain period of time without an uplink packet, it generates an uplink empty packet for each session anchor point in at least one session anchor point used to report network information monitoring results, records the time Ty when the uplink empty packet arrives, is generated, or leaves, adds T1, T2, T3, Tx, Ty to the GTP-U header of the uplink empty packet, and sends the empty packet to the session anchor point. In another possible implementation, when the time difference between the diversion point receiving the first data packet and the diversion point generating (or sending) the second data packet exists or cannot be ignored, the reporting information carried in the second data packet may be different from the reporting information carried in the first data packet. For example, the reporting information in the first data packet includes T1, T2, and T3, and the reporting information in the second data packet includes T1, T2, and the modified time (T3') when the first data packet leaves the access network device. T3' is obtained by modifying T3 based on Tx and Ty. For example, when the diversion point receives the first data packet (carrying T1, T2, T3), it determines the delay △t of the path from the access network device to the diversion point, records the time Tx when the first data packet arrives at the diversion point, and when waiting for an uplink packet or waiting for a certain period of time without an uplink packet, generates an uplink empty packet for each session anchor point in at least one session anchor point used to report network information monitoring results, and records the time Ty when the uplink empty packet arrives, is generated, or leaves. Based on △t and Ty, the time t3' when the uplink empty packet departs from the access network device is inferred, t3'=Ty-△t. Add T1, T2, T3' to the GTP-U header of the uplink empty packet. Of course, the above are only examples and are not limited thereto. In an embodiment of the present application, when there are multiple session anchors for reporting network information monitoring results, the multiple session anchors for reporting network information monitoring results may include the first session anchor or may not include the first session anchor. When the first session anchor point is included in multiple session anchor points used to report network information monitoring results, the diversion point may send the first data packet directly to the first session anchor point without performing any processing on the first data packet; or the diversion point processes the first data packet (for example, re-encapsulates it after decapsulation) and then sends the processed first data packet to the first session anchor point; or the diversion point sends the first data packet and the third data packet to the first session anchor point, the third data packet carries the reporting information, the first data packet and the third data packet are different data packets, and so on, which is not limited to the embodiments of the present application. When the first session anchor point is not included in the multiple session anchor points used to report the network information monitoring results, the diversion point may send the first data packet directly to the first session anchor point without performing any processing on the first data packet; or the diversion point processes the first data packet (for example, re-encapsulates it after decapsulation) and then sends the processed first data packet to the first session anchor point; or the diversion point discards the first data packet, for example, the first data packet is an uplink empty packet (i.e., it does not carry valid data), etc., and the embodiments of the present application are not limited thereto. In a specific example, the diversion point may carry the reporting information in a second data packet sent to the second session anchor point according to the local configuration. For example, the diversion point is locally configured with fourth information, and the fourth information is used to indicate at least one session anchor point for reporting user plane monitoring results, and the at least one session anchor point includes the second session anchor point. Accordingly, after the diversion point receives the first data packet, the diversion point carries the reporting information in a data packet sent to each session anchor point in at least one session anchor point according to the local configuration (or is described as the diversion point sending a second data packet to each session anchor point in at least one session anchor point). In another specific example, the diversion point may send the second data packet to the second session anchor point according to the fourth information indicated by other network elements. For example, referring to FIG. 10 , before S202 (or S201 ), steps S203 to S205 are further performed: S203: The PCF receives the network information monitoring and opening requirements (or network information monitoring requirements) indicated by the AF. S204. PCF sends the first information to SMF, and correspondingly, SMF receives the first information. The first information is used by the SMF to perform network information monitoring on one or more data streams, the one or more data streams correspond to the second quality of service stream and the second quality of service stream corresponds to multiple session anchor points. The specific implementation of this step can refer to the relevant description in S101 above, which will not be repeated here. Optionally, after S204 and before S206, the following may also be performed: S205: SMF determines that the second quality of service is diverted (ie, the second quality of service flow corresponds to multiple session anchor points). S206. After receiving the first information, the SMF sends fourth information to the diversion point according to the first information, where the fourth information is used to indicate at least one session anchor point for reporting network information monitoring results. The fourth information may be carried in an N4 session modification request, or the fourth information is an N4 session modification request. In the embodiment of the present application, the network information monitoring result is determined according to the monitoring result of the access network device, so these session anchor points need to receive the reporting information reported by the access network device. Therefore, in some embodiments, at least one session anchor point for reporting the network information monitoring result can also be replaced by: a session anchor point for receiving the reporting information, and the number of session anchor points for receiving the reporting information is one or more. In specific implementation, at least one session anchor point used to report network information monitoring results can be a UPF in which SMF is configured as QoSFlow to perform QoS Monitoring and report monitoring results, or a UPF in which SMF is configured as QoSFlow to perform ECN marking. This embodiment of the present application does not limit this. The content of the fourth information and the action performed by the diversion point after receiving the fourth information may refer to the above S202. In a possible implementation, before S201, the following is further performed: S207, SMF configures the access network device to perform network information monitoring and / or at least one session anchor point (including the second session anchor point) to perform network information monitoring according to the network information monitoring rules. For example, the first information includes network information monitoring rules (such as QoS Monitoring policy or indication for ECN marking for L4S, etc.). For example, the first information is PCC rule, PCC rule indicates SDF1, 2. If SDF1, 2 are both diverted to PSA, SMF configures PSA to perform network information opening. If SDF1, 2 are respectively diverted to PSA and PSA2, SMF configures PSA and PSA2 to perform network information opening. It should be noted that if the network information monitoring rule is UPF L4S, no matter how the SDF corresponding to the PCC rule is diverted, SMF needs to notify all anchor points to perform network information monitoring. SMF configures the access network device to perform network information monitoring according to the network information monitoring rules, so that the access network device can report the reported information. SMF configures the session anchor point to perform network information monitoring according to the network information monitoring rules, so that the session anchor point can receive the reported information and determine the network information monitoring results based on the reported information. In a possible implementation, after S202, the following is further performed: S208: after any session anchor point (such as the second session anchor point) receives the second data packet, it determines whether to receive the reporting information carried in the second data packet. For example, after any session anchor receives the second data packet, it can determine whether to receive the reporting information carried in the data packet based on whether it has received a network information monitoring indication from the SMF or the address in the data packet. If the location is the address of the session anchor, the reporting information carried in the second data packet is received and processed, otherwise the reporting information carried in the second data packet is discarded. Alternatively, in the packet delay monitoring scenario of QoS Monitoring, after any session anchor corresponding to the second service quality flow receives any data packet, it can determine whether to receive the reporting information carried in the data packet based on the time information in the second data packet. For example, if T1 in the second data packet is the time when the session anchor previously sent a downlink data packet, the reporting information carried in the second data packet is received and processed, otherwise the reporting information carried in the second data packet is discarded. For example, in a packet delay monitoring scenario, the session anchor point that performs network information monitoring can carry its address in the downlink packet, indicating which session anchor point the delay measurement comes from. If this action is performed, the access network device RAN needs to carry the same content in the uplink packet. The subsequent session anchor point can determine whether to receive the reported information in the uplink packet based on whether the session anchor point address contained in the received uplink packet is its address. In another possible implementation, when there are multiple at least one session anchor points for reporting network information monitoring results, the SMF can configure different session anchor points to perform network information monitoring at different times. For example, after receiving the user plane monitoring policy, SMF divides the policy into multiple parts (for example, according to the session anchor points corresponding to the data flow). First, one part (for example, one or more data flows corresponding to a session anchor point) is executed. After the execution of this part is completed (for example, the anchor point UPF has reported the network information monitoring results), SMF executes another part (for example, one or more data flows corresponding to another session anchor point), and so on, until the execution of all policies is completed. For example, after receiving the user plane monitoring policy, the SMF divides the policy into multiple parts (for example, according to the session anchor points corresponding to the data flow). When configuring each session anchor point to perform network information monitoring, add a time indication to indicate the time when these session anchor points perform network information monitoring (for example, anchor point 1 starts immediately, and anchor point 2 starts after 5 seconds), so as to stagger the time when each session anchor point performs network information monitoring. In another possible implementation, for Latency QoS Monitoring, if multiple session anchor points simultaneously perform Latency QoS Monitoring, the diversion point records the time T1 in the third data packet when receiving the third data packet from each session anchor point UPF, and when receiving the first data packet from the access network device, it determines that T1 in the first data packet is the same as T1 in the third data packet from a certain session anchor point, and then sends the reporting information carried by the first data packet to the session anchor point via the second data packet. In a possible implementation, after each of the at least one session anchor point for reporting the network information monitoring result obtains the network information monitoring result according to the reported information, the session anchor points may open the network information monitoring result. For example, after S208, the following is further performed: S209, the second session anchor point opens the network information monitoring result. For example, these session anchors open the network information monitoring results to the outside. Alternatively, these session anchors can also send the network information monitoring results to the SMF (or PCF), and the SMF (or PCF) receives the network information monitoring results from at least one session anchor, and then opens the network information monitoring results to the outside through the SMF (or PCF). Optionally, when SMF (or PCF) opens the network information monitoring result to AF, SMF (or PCF) can also provide path information, and the path information is used to indicate the path corresponding to the network information monitoring result. The path information includes one or more of the data network access identifier (DNAI), session anchor address (such as anchor UPF address), edge application server address (EAS address), AF address, and path indication information (such as AF path indication information). For example, during QoS monitoring, when UPF (or PCF) (optionally, through some intermediate network elements) opens the network information monitoring results to the outside (such as informing AF of the results), it can carry path information to indicate the path corresponding to the network information monitoring results (such as PSA or PSA2). In the above scheme, when the service quality flow corresponding to the data flow for performing network information monitoring is diverted, the diversion point can report the reporting information reported by the access network device to the session anchor point for performing network information monitoring (i.e., the target session anchor point, such as the second session anchor point) according to the local configuration or the instructions of other network elements. In this way, it can be ensured that the monitoring results reported by the access network device reach the target session anchor point, thereby ensuring the reliability of network information monitoring (or network information monitoring and opening) in the diversion point insertion scenario. In one possible method, when SMF adds a diversion point for the current session, the diversion filtering rules used for diversion forwarding at the diversion point will forward the data packets in the second service quality flow to the same session anchor point, that is, when SMF adds a diversion point, it will consider diversion at the granularity of the service quality flow. Referring to FIG. 11 , another communication method provided in an embodiment of the present application includes S301 to S302: S301. PCF sends first information to SMF, and SMF receives the first information. The first information is used by the SMF to perform network information monitoring on one or more data flows, the one or more data flows correspond to the second quality of service flow, and the second quality of service flow corresponds to multiple session anchor points. The specific implementation of this part can refer to the corresponding design in S101 above. For example, the first information is a PCC rule. Optionally, the first information may also include one or more of a data network access identifier, a session anchor address, an edge application server address, an application function network element address, and path indication information. One or more of the information may come from a request sent by the AF, and is used to indicate a path requested (or desired) by the AF for performing network information monitoring (or network information monitoring and opening). For example, the first information includes a data network access identifier. Since the DNAIs of the DN accessed by PSA and PSA2 are different, if AF indicates the DNAI corresponding to PSA2, SMF needs to monitor and open the network information of the PSA2 path. S302. The SMF sends fifth information to the diversion point according to the first information, and the SMF receives the fifth information. The fifth information is used to indicate that all data flows corresponding to the second quality of service flow are diverted to the same session anchor point. For example, PCC rule indicates SDF1, SDF1 is in QoS flow#1, QoS flow#1 includes SDF1, 2, 3, where SDF1 is diverted to PSA, and SDF2, 3 are diverted to PSA2. Then SMF can modify the diversion rule by indicating the diversion point through the fifth information, and divert SDF1, 2, 3 to PSA or PSA2. For example, the fifth information is an N4 session modification request, or the fifth information is carried in the N4 session modification request. Optionally, the fifth information may include an identifier of a target session anchor point, and the fifth information is used to instruct to divert all data flows corresponding to the second quality of service flow to the target session anchor point. For example, the fifth information includes an anchor point identifier and an indication information, the indication information indicates that all data streams corresponding to the second quality of service flow are diverted to the same session anchor point, and an anchor point identifier indicates the same session anchor point. Alternatively, the fifth information includes an anchor point identifier, and the anchor point identifier indicates that all data streams corresponding to the second quality of service flow are diverted to the session anchor point corresponding to the anchor point identifier. In a specific implementation, the SMF can be based on one or more pieces of information in the first information, as well as the edge application server deployment information, the terminal The target session anchor point is determined by one or more of the device's contract information and the internal logic of the SMF. For example, the PCC rule includes DNAI 1, and the SMF consults EAS deployment information (EDI) to determine that the DNAI 1 corresponds to PSA2, and then determines to divert the data flow only to PSA2. Optionally, after S301 and before S302, the following is further performed: S303: SMF determines, according to the first information, that the second quality of service flow is diverted (ie, corresponds to multiple session anchor points). For example, after the SMF receives a PCC rule (i.e., the first information), the PCC rule indicates the need for network information monitoring (or network information monitoring and opening). The SMF determines whether the service quality flow (i.e., the second service quality flow described above) in which the data flow used to perform network information monitoring in the PCC rule is located is diverted (i.e., whether a diversion point is inserted). If so, execute the above step S301. Optionally, after S302, the following steps may be performed: S304, SMF configures the access network device and / or the target session anchor point to perform network information monitoring according to the network information monitoring rule. For example, the first information includes the network information monitoring rule. S305: The access network device, the diversion point, the target session anchor point, etc. perform network information monitoring. For example, when the diversion point receives a data packet belonging to the second quality of service flow (the data packet carries the reporting information reported by the access network device), the data packet is sent to the target session anchor point. In the above scheme, when SMF determines that the service quality flow corresponding to the data flow used to perform network information monitoring is diverted, SMF notifies the diversion point to divert all data flows in the service quality flow corresponding to the data flow used to perform network information monitoring to the same session anchor point. In this way, it can ensure that the monitoring results reported by the access network equipment reach the target session anchor point, thereby ensuring the reliability of network information monitoring (or network information monitoring and opening) in the diversion point insertion scenario. The method provided by the embodiment of the present application is introduced above in combination with the accompanying drawings, and the device provided by the embodiment of the present application is introduced below in combination with the accompanying drawings. Based on the same technical concept, an embodiment of the present application provides a communication device, which includes a module / unit / means for executing the method executed by any network function and entity in the above method embodiment. The module / unit / means can be implemented by software, or by hardware, or the corresponding software can be implemented by hardware. Exemplarily, referring to Fig. 12, the device may include a transceiver module 401 and may also include a processing module 402. The dotted line indicates that the processing module 402 is optional. For example, when the device is a session management function network element or is located in a session management function network element: The transceiver module 401 is used to receive first information from a policy control function network element, where the first information is used to configure network information monitoring for multiple data streams, where the multiple data streams correspond to a first data session and the first data session corresponds to multiple session anchor points; The processing module 402 is used to create at least one service quality flow for the first data session, the first service quality flow in the at least one service quality flow corresponds to one or more data flows in the multiple data flows, the first service quality flow is used to perform network information monitoring on the data flow carried in the first service quality flow, and the first service quality flow corresponds to a session anchor point in the multiple session anchor points. For example, when the device is a policy control function network element or is located in a policy control function network element: The transceiver module 401 is used to receive the second information, which is used for the policy control function network element to generate multiple network information monitoring rules; send the multiple network information monitoring rules to the session management function network element, and the multiple network information monitoring rules are used to indicate the policy of the session served by the session management function network element. Optionally, the device further includes a processing module 402, configured to generate a plurality of network information monitorings according to the second information. For example, when the device is a user plane network element serving as a branch point or is located at a user plane network element serving as a branch point: The transceiver module 401 is used to receive a first data packet, which carries reporting information and is carried on a second quality of service flow. The second quality of service flow corresponds to multiple session anchors, and the reporting information is used to notify the access network device of the monitoring result. The first data packet corresponds to the first session anchor; send a second data packet to the second session anchor, the second data packet carries reporting information and is carried on the second quality of service flow; wherein the first session anchor is different from the second session anchor, and the multiple session anchors include the first session anchor and the second session anchor. Optionally, the device further includes a processing module 402, configured to determine a second data packet according to reporting information in the first data packet. For example, when the device is a session management function network element or is located in a session management function network element: The transceiver module 401 is used to receive first information from a policy control function network element, where the first information is used by the session management function network element to perform network information monitoring on one or more data streams, where the one or more data streams correspond to a first data session and the first data session corresponds to multiple session anchor points; and send fourth information to the user plane network element based on the first information, where the fourth information is used to indicate at least one session anchor point for reporting network information monitoring results. Optionally, the device further includes a processing module 402, configured to determine fourth information according to the first information. For example, when the device is a session management function network element or is located in a session management function network element: The transceiver module 401 is used to receive first information from a policy control function network element, where the first information is used by the session management function network element to perform network information monitoring on one or more data streams, where the one or more data streams correspond to a second quality of service stream and the second quality of service stream corresponds to multiple session anchor points; and send fifth information to the user plane network element based on the first information, where the fifth information is used to instruct that all data streams corresponding to the second quality of service stream be diverted to the same session anchor point. Optionally, the device further includes a processing module 402, configured to determine fifth information according to the first information. A more detailed description of the transceiver module 401 and the processing module 402 can be directly obtained by referring to the relevant description in the above method embodiment, which will not be repeated here. Based on the same technical concept, an embodiment of the present application also provides a communication device, as shown in Figure 13, including a processor 501 and a memory 502; the memory 502 is used to store computer execution instructions; the processor 501 is used to execute the computer execution instructions stored in the memory 502, so that the communication device can implement any network function and entity function of the above method embodiment. The number of the memory 502 may be one or more. The memory 502 may include a read-only memory (ROM), a random access memory (RAM), a disk memory, etc. The memory 502 may be used to store program codes required by the processor 501 to perform tasks, and may also be used to store data, etc. The memory 502 is an optional functional module rather than a mandatory functional module. The processor 501 and the memory 502 may be connected via a bus, or may be connected to the processor via a dedicated connection line, which is not limited here. By programming the processor 501, the code corresponding to the above method is fixed into the chip, so that the chip can execute the method shown in the above embodiment when running. How to program the processor 501 is a technology known to those skilled in the art and will not be described here. It should be understood that the processor mentioned in the embodiments of the present application can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor implemented by reading software code stored in a memory. Exemplarily, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. It should be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct RAM bus random access memory (DR RAM). It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor. It should be noted that the memory described herein is intended to include, without being limited to, these and any other suitable types of memory. Based on the same technical concept, an embodiment of the present application also provides a computer-readable storage medium, which is used to store instructions. When the instructions are executed, the method executed by any network function and entity function in the above method embodiment is implemented. Based on the same technical concept, an embodiment of the present application also provides a chip, which is coupled to a memory and is used to read and execute program instructions stored in the memory to implement a method executed by any network function and entity function in the above method embodiment. Based on the same technical concept, an embodiment of the present application also provides a computer program product comprising instructions, wherein the computer program product stores instructions that, when executed on a computer, enable the computer to execute a method as performed by any network function and entity function in the above method embodiments. It should be understood by those skilled in the art that the embodiments of the present application may be provided as methods, systems, or computer program products. The application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. The present application is described with reference to the flowchart and / or block diagram of the method, device (system), and computer program product according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the process and / or box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the function specified in one process or multiple processes in the flowchart and / or one box or multiple boxes in the block diagram. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram. These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A communication method, characterized in that: include: The session management function network element receives first information, where the first information is used to configure network information monitoring for multiple data streams, where the multiple data streams correspond to a first data session and the first data session corresponds to multiple session anchor points; The session management function network element creates at least one quality of service flow for the first data session, a first quality of service flow among the at least one quality of service flow corresponds to one or more data flows among the multiple data flows, the first quality of service flow is used to perform network information monitoring on the data flow carried in the first quality of service flow, and the first quality of service flow corresponds to one session anchor point among the multiple session anchor points.

2. The method according to claim 1, characterized in that The method further comprises: The session management function network element receives a network information monitoring result for a data flow carried in the first quality of service flow.

3. The method according to claim 1 or 2, characterized in that Before the at least one quality of service flow is created, the plurality of data flows correspond to a second quality of service flow in the first data session; The method further comprises: The session management function network element determines that the second quality of service flow corresponds to the multiple session anchor points.

4. The method according to claim 3, characterized in that The session management function network element creates at least one quality of service flow for the first data session, including: The session management function network element deletes the second quality of service flow and creates the at least one quality of service flow; or The session management function network element modifies the second quality of service flow and creates at least one new quality of service flow, wherein the created at least one quality of service flow includes the modified second quality of service flow and the at least one new quality of service flow.

5. The method according to any one of claims 1 to 4, characterized in that: The at least one quality of service flow corresponds one-to-one to the multiple session anchor points.

6. The method according to claim 3 or 4, characterized in that The session management function network element creates at least one quality of service flow for the first data session, including: The session management function network element creates different quality of service flows for data flows corresponding to different session anchor points in the second quality of service flow according to the diversion rule.

7. The method according to any one of claims 1 to 4, characterized in that: The session management function network element creates at least one quality of service flow for the first data session, including: The session management network element creates a quality of service flow for each of the multiple data flows.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: The session management function network element sends second information to the policy control function network element, where the second information is used by the policy control function network element to generate multiple network information monitoring rules for the multiple data flows; The session management function network element receives multiple network information monitoring rules generated for the multiple data flows from the policy control function network element, each of the multiple network information monitoring rules is used to perform network information monitoring on the corresponding one or more data flows, and the one or more data flows corresponding to each of the multiple network information monitoring rules correspond to one of the multiple session anchor points.

9. The method according to claim 8, characterized in that The second information includes a set of data flow identifiers.

10. The method according to claim 9, characterized in that The set of data flow identifiers includes an identifier of a data flow corresponding to at least one session anchor point among the multiple session anchor points.

11. The method according to claim 10, characterized in that Each of the network information monitoring rules includes identifiers of one or more data flows corresponding to a session anchor point among the multiple session anchor points.

12. A communication method, characterized in that: include: The policy control function network element receives second information, where the second information is used by the policy control function network element to generate a plurality of network information monitoring rules; The policy control function network element sends the multiple network information monitoring rules to the session management function network element, where the multiple network information monitoring rules are used to indicate the policies of the sessions served by the session management function network element.

13. The method according to claim 12, characterized in that Before the policy control function network element receives the second information, the method further includes: The policy control function network element sends first information to the session management function network element, wherein the first information is used to configure the multiple data The plurality of data flows perform network information monitoring, the plurality of data flows correspond to a first data session and the first data session corresponds to a plurality of session anchor points; Among them, the second information is used by the policy control function network element to generate the multiple network information monitoring rules for the multiple data flows; each of the multiple network information monitoring rules is used to perform network information monitoring on the corresponding one or more data flows, and the one or more data flows corresponding to each of the multiple network information monitoring rules correspond to one session anchor point among the multiple session anchor points.

14. The method according to claim 12, characterized in that The second information includes a set of data flow identifiers; The method further includes: the policy control function network element generating the multiple network information monitoring rules according to the set of data flow identifiers.

15. The method according to claim 14, characterized in that The set of data flow identifiers includes an identifier of a data flow corresponding to at least one session anchor point among the multiple session anchor points.

16. The method according to claim 15, characterized in that Each of the network information monitoring rules includes identifiers of one or more data flows corresponding to a session anchor point among the multiple session anchor points.

17. A communication method, characterized in that: include: The user plane network element receives a first data packet, the first data packet carries reporting information, the first data packet is carried in a second quality of service flow, the second quality of service flow corresponds to multiple session anchor points, the reporting information is used to notify the access network device of the monitoring result, and the first data packet corresponds to the first session anchor point; The user plane network element sends a second data packet to the second session anchor point, where the second data packet carries the reporting information, and the second data packet is carried in the second quality of service flow; The first session anchor point is different from the second session anchor point, and the multiple session anchor points include the first session anchor point and the second session anchor point.

18. The method according to claim 17, characterized in that The user plane network element sends a second data packet to the second session anchor point, including: The user plane network element sends the second data packet to the second session anchor point according to the reporting information in the first data packet.

19. The method according to claim 17 or 18, characterized in that The user plane network element sending the second data packet to the second session anchor point includes: The user plane network element carries the reporting information in the first data packet in the second data packet sent to the second session anchor point.

20. The method according to any one of claims 17 to 19, characterized in that: The method further comprises: The user plane network element obtains fourth information from the session management function network element or the user plane network element obtains fourth information according to local configuration, where the fourth information is used to indicate at least one session anchor point for reporting the network information monitoring result, and the at least one session anchor point includes the second session anchor point; The user plane network element sends a second data packet to the second session anchor point, including: The user plane network element sends a second data packet to each session anchor point of the at least one session anchor point.

21. The method of claim 20, wherein: The fourth information includes an identifier of the at least one session anchor point; or, The fourth information includes indication information, where the indication information is used to indicate that the session anchor points used to report the network information monitoring result are all session anchor points corresponding to the second quality of service flow.

22. The method according to any one of claims 17 to 21, characterized in that: The second data packet is a null packet belonging to the second quality of service flow.

23. The method according to any one of claims 17 to 22, characterized in that: The reporting information is carried in a user plane tunneling protocol GTP-U header of the second data packet.

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

25. A communication device, characterized in that: include: Memory, for storing computer instructions; A processor, configured to execute the computer instructions so that the communication device executes the method according to any one of claims 1 to 11, or executes the method according to any one of claims 12 to 16, or executes the method according to any one of claims 17 to 23.

26. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, it implements the method as described in any one of claims 1 to 11, or implements the method as described in any one of claims 12 to 16, or implements the method as described in any one of claims 17 to 23.

27. A computer program product, characterized in that The computer program product stores instructions, and when the computer program product runs on a computer, the computer executes the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 16, or the method according to any one of claims 17 to 23.

Images