WO2023174100A1 - 通信方法及通信装置 - Google Patents

通信方法及通信装置 Download PDF

Info

Publication number
WO2023174100A1
WO2023174100A1 PCT/CN2023/080080 CN2023080080W WO2023174100A1 WO 2023174100 A1 WO2023174100 A1 WO 2023174100A1 CN 2023080080 W CN2023080080 W CN 2023080080W WO 2023174100 A1 WO2023174100 A1 WO 2023174100A1
Authority
WO
WIPO (PCT)
Prior art keywords
service flow
monitored
target service
network element
uplink
Prior art date
Application number
PCT/CN2023/080080
Other languages
English (en)
French (fr)
Inventor
潘奇
倪慧
黄正磊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023174100A1 publication Critical patent/WO2023174100A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the embodiments of the present application relate to the field of communication, and more specifically, to a communication method and a communication device.
  • third-party applications can sense the network status in real time, the third-party applications can make corresponding adjustments according to the network status, thereby ensuring the user's business experience and maximizing network utilization efficiency. Therefore, how to quickly expose more network status information, such as available bandwidth and congestion conditions, to third-party applications is a key issue.
  • network status information can be exposed to the application layer in the form of a control plane or a user plane.
  • network status information can be exposed to third-party applications through the user plane function (UPF) service interface or the network exposure function (NEF).
  • UPF can add network status information to the data packet and send it to the application server side.
  • UPF cannot monitor the network status between the radio access network (RAN) on the air interface side and the terminal equipment, if UPF needs to open the connection between the air interface side RAN and the terminal equipment to third-party applications network status information, the UPF can only receive network status information on the air interface side from the RAN. In this case, how the RAN sends the network status information on the air interface side to the UPF will become an urgent problem to be solved.
  • RAN radio access network
  • Embodiments of the present application provide a communication method, in order to enable the access network device to send the network status information obtained by monitoring the network status to the user plane network element.
  • a communication method includes: an access network device receiving monitoring configuration information of a target service flow to be monitored and an identifier of an uplink service flow.
  • the monitoring configuration information is used to monitor the target service flow to be monitored.
  • Network status the uplink service flow is used to transmit the network status information of the target service flow to be monitored;
  • the access network device performs network status monitoring based on the monitoring configuration information of the target service flow to be monitored to obtain the network status of the target service flow to be monitored Status information;
  • the access network device sends an uplink data packet to the user plane network element, and the uplink data packet includes the network status information of the target service flow to be monitored and the identifier of the uplink service flow.
  • the access network device receives the monitoring configuration information and the uplink service flow identifier of the target service flow to be monitored, which can also be understood as the access network device actively obtains the monitoring configuration information and uplink service of the target service flow to be monitored from other network elements or entities.
  • the identifier of the stream can also be understood as the access network device actively obtains the monitoring configuration information and uplink service of the target service flow to be monitored from other network elements or entities.
  • the access network device after the access network device receives the identifier of the uplink service flow used to transmit the network status information of the target service flow to be monitored, it can send the target to be monitored to the user plane network element through the uplink data packet in the uplink service flow. Measure the network status information of the service flow, so that the access network equipment can send the network status information obtained by monitoring the network status to the user plane network element. Furthermore, the user plane network element can open the received network status information to third-party applications, so that the third-party application can adjust the transmission parameters of the target service flow to be monitored based on the network status information to ensure the user's business experience. For example, third-party applications The code rate of the target service stream to be monitored can be reduced based on network status information.
  • the access network equipment sends the network status information at the service flow granularity to the user plane network element, and then the user plane network element can open the network status information at the service flow granularity to the third-party application server, so that the third-party application server can Third-party application servers can adjust the transmission parameters of the business flow based on the network status information at the granularity of the business flow to meet the user's experience and needs for different business flows.
  • the target service flow to be monitored is a first quality of service (QoS) flow
  • the uplink service flow is an uplink service flow in the second QoS flow.
  • QoS quality of service
  • the access network device when the target service flow to be monitored is the first QoS flow, that is, there are no other service flows in the first QoS flow, the access network device can also realize that the network status information of the target service flow to be monitored is Sent to the user plane network element.
  • the target service flow to be monitored is a downlink service flow, that is, there is no uplink data packet in the first QoS flow
  • the access network device does not receive the uplink service used to transmit the network status information of the target service flow to be monitored.
  • the access network device does not know which service flow should be used to transmit the network status information of the target service flow to be monitored to the user plane network element, and the access network device cannot transmit the network status of the target service flow to be monitored to the user plane network element. information.
  • the target service flow to be monitored is a downlink service flow in the first QoS flow
  • the uplink service flow is an uplink service flow in the second QoS flow.
  • the first QoS flow and the second QoS flow are the same QoS flow, or the first QoS flow and the second QoS flow are different QoS flows.
  • the access network device when the target service flow to be monitored is the downlink service flow in the first QoS flow, the access network device can be implemented to send network status information at the service flow granularity to the user plane network element. For example, if the network not only performs network status monitoring on the target service flow to be monitored, but also performs network status monitoring on the uplink service flow in the first QoS flow, if the access network device does not receive the network status for transmitting the target service flow to be monitored. The identification of the uplink service flow of the status information, then the access network device can only transmit the network status information of the target service flow to be monitored and the uplink service flow in the first QoS flow to the user plane network element through the uplink service flow in the first QoS flow.
  • the network status information makes it difficult for user plane network elements to distinguish the relationship between network status information and service flows.
  • the target service flow to be monitored is an uplink service flow in the first QoS flow
  • the uplink service flow is an uplink service flow in the second QoS flow.
  • the first QoS flow and the second QoS flow are the same QoS flow, or the first QoS flow and the second QoS flow are different QoS flows.
  • the access network device when the target service flow to be monitored is the uplink service flow in the first QoS flow, the access network device can be implemented to send network status information at the service flow granularity to the user plane network element. For example, if the network not only performs network status monitoring on the target service flow to be monitored, but also performs network status monitoring on the uplink service flow in the first QoS flow, if the access network device does not receive the network status for transmitting the target service flow to be monitored. The identification of the uplink service flow of the status information, then the access network device can only transmit the network status information of the target service flow to be monitored and the uplink service flow in the first QoS flow to the user plane network element through the uplink service flow in the first QoS flow.
  • the network status information makes it difficult for user plane network elements to distinguish the relationship between network status information and service flows.
  • the uplink service flow used to transmit the network status information of the target service flow to be monitored may also be the second QoS flow, that is, there is no other downlink service flow in the second QoS flow.
  • the method further includes: the access network device receives the The indication information of the uplink service flow of the network status of the target service flow to be monitored is transmitted.
  • the access network device when the access network device receives the identifier of the uplink service flow and the indication information, it can determine based on the indication information that the uplink service flow is used to transmit the network status information of the target service flow to be monitored, thereby accessing After the network device obtains the network status information of the target service flow to be monitored, it can send the network status information of the target service flow to be monitored to the user plane network element through the uplink service flow, thereby achieving rapid transmission of the network status information of the target service flow to be monitored. Real-time transmission.
  • the access network device receives the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow, including: the access network device receives the target to be monitored.
  • the identifier of the target service flow to be monitored and the identifier of the upstream service flow have a binding relationship, thereby indicating that the upstream service flow is used to transmit network status information of the target service flow to be monitored.
  • the uplink data packet further includes an identifier of the target service flow to be monitored.
  • the uplink data packet sent by the access network device to the user plane network element not only includes the identification of the uplink service flow , also includes the identification of the target business flow to be monitored.
  • the user plane network element can determine that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identification of the uplink service flow and the identification of the target service flow to be monitored, thereby realizing the target service flow to be monitored. Fast real-time transmission of network status information, and enabling access network equipment to send service flow granular network status information to user plane network elements.
  • a communication method includes: a user plane network element obtains an identifier of an uplink service flow, and the uplink service flow is used to transmit network status information of a target service flow to be monitored; and the user plane network element receives uplink data.
  • the uplink data packet includes the identifier of the uplink service flow and network status information; the user plane network element determines that the network status information included in the uplink data packet is the network status of the target service flow to be monitored based on the identifier of the uplink service flow. information.
  • the user plane network element obtains the identifier of the uplink service flow, which can be understood as receiving the uplink service flow identifier in the uplink data packet.
  • the access network device can send the target to be monitored to the user plane network element through the uplink data packet in the uplink service flow.
  • the user plane network element can determine that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identification of the uplink service flow, thereby realizing rapid real-time transmission of services from the access network equipment to the user plane network element. Flow granular network state information.
  • the access network device sends network status information at the service flow granularity to the user plane network element
  • the third-party application server can The transmission parameters of the service flow are adjusted based on the network status information at the granularity of the service flow to meet the user's experience and needs for different service flows.
  • the target service flow to be monitored is the first QoS flow
  • the uplink service flow is the uplink service flow in the second QoS flow.
  • the access network device can also realize that the network status information of the target service flow to be monitored is Send to Household network element.
  • the target service flow to be monitored is a downlink service flow, that is, there is no uplink data packet in the first QoS flow
  • the access network device does not receive the uplink service used to transmit the network status information of the target service flow to be monitored.
  • the access network device does not know which service flow should be used to transmit the network status information of the target service flow to be monitored to the user plane network element, and the access network device cannot transmit the network status of the target service flow to be monitored to the user plane network element. information.
  • the target service flow to be monitored is an uplink service flow in the first QoS flow
  • the uplink service flow is an uplink service flow in the second QoS flow.
  • the first QoS flow and the second QoS flow are the same QoS flow, or the first QoS flow and the second QoS flow are different QoS flows.
  • the access network device when the target service flow to be monitored is the downlink service flow in the first QoS flow, the access network device can be implemented to send network status information at the service flow granularity to the user plane network element. For example, if the network not only performs network status monitoring on the target service flow to be monitored, but also performs network status monitoring on the uplink service flow in the first QoS flow, if the access network device does not receive the network status for transmitting the target service flow to be monitored. The identification of the uplink service flow of the status information, then the access network device can only transmit the network status information of the target service flow to be monitored and the uplink service flow in the first QoS flow to the user plane network element through the uplink service flow in the first QoS flow.
  • the network status information makes it difficult for user plane network elements to distinguish the relationship between network status information and service flows.
  • the target service flow to be monitored is an uplink service flow in the first QoS flow
  • the uplink service flow is an uplink service flow in the second QoS flow.
  • the first QoS flow and the second QoS flow are the same QoS flow, or the first QoS flow and the second QoS flow are different QoS flows.
  • the access network device when the target service flow to be monitored is the uplink service flow in the first QoS flow, the access network device can be implemented to send network status information at the service flow granularity to the user plane network element. For example, if the network not only performs network status monitoring on the target service flow to be monitored, but also performs network status monitoring on the uplink service flow in the first QoS flow, if the access network device does not receive the network status for transmitting the target service flow to be monitored. The identification of the uplink service flow of the status information, then the access network device can only transmit the network status information of the target service flow to be monitored and the uplink service flow in the first QoS flow to the user plane network element through the uplink service flow in the first QoS flow.
  • the network status information makes it difficult for user plane network elements to distinguish the relationship between network status information and service flows.
  • the uplink service flow used to transmit the network status information of the target service flow to be monitored may also be the second QoS flow, that is, there is no other downlink service flow in the second QoS flow.
  • the uplink service flow is used to transmit network status information of each of multiple to-be-monitored service flows, and the multiple to-be-monitored service flows include the target to-be-monitored service flow. Monitor the service flow.
  • the uplink data packet also includes the identification of the target service flow to be monitored.
  • the user plane network element determines that the network status information included in the uplink data packet is the network of the target service flow to be monitored based on the identification of the uplink service flow.
  • the status information includes: the user plane network element determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identification of the target service flow to be monitored and the identification of the uplink service flow.
  • the user plane network element can determine based on the identification of the uplink service flow and the identification of the target service flow to be monitored.
  • the network status information included in the uplink data packet is the network status information of the target service flow to be monitored, thereby achieving rapid real-time transmission of the network status information of the target service flow to be monitored, and enabling the access network equipment to send service flow granularity to user plane network elements. Network status information.
  • the user plane network element obtains the identifier of the uplink service flow, including: the user plane network element receives the identifier of the uplink service flow from the session management network element.
  • the method further includes: the user plane network element receiving the uplink service for transmitting the network status information of the target service flow to be monitored from the session management network element. Streaming instructions.
  • the user plane network element when the user plane network element receives the identifier of the uplink service flow and the indication information, it can determine based on the indication information that the uplink service flow is used to transmit the network status information of the target service flow to be monitored, so that the user plane The network element can receive the network status information of the target service flow to be monitored from the access network device through the uplink service flow, thereby realizing rapid and real-time transmission of the network status information of the target service flow to be monitored.
  • the user plane network element receives the identifier of the uplink service flow from the session management network element, including: the user plane network element receives the uplink service flow from the session management network element.
  • the identifier of the target service flow to be monitored has a binding relationship with the identifier of the upstream service flow to indicate that the upstream service flow is used to transmit network status information of the target service flow to be monitored.
  • the method further includes: the user plane network element receiving instruction information for obtaining the network status information of the target service flow to be monitored from the application function network element; the user plane network element The network element sends the instruction information for network status monitoring of the target service flow to be monitored to the session management network element.
  • the user plane network element clearly needs to perform network status monitoring on the target service flow to be monitored based on the instruction information for obtaining the network status information of the target service flow to be monitored.
  • the user plane network element sends instruction information for monitoring the network status of the target service flow to be monitored to the session management network element, so that the session management network element can determine the transmission method for the target service flow to be monitored based on the instruction information.
  • the user plane network element obtains the identifier of the uplink service flow, including: the user plane network element receives and obtains the network of the target service flow to be monitored from the application function network element. Instruction information of the status information; the user plane network element determines the identity of the uplink service flow based on the instruction information for obtaining the network status information of the target service flow to be monitored; the method also includes: the user plane network element sends a request to the access network The device sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow. The monitoring configuration information is used to monitor the network status of the target service flow to be monitored.
  • the user plane network element determines the identifier of the uplink service flow based on the instruction information for obtaining the network status information of the target service flow to be monitored, and sends the identifier of the uplink service flow to the access network device, so that the access network device can According to the identification of the uplink service flow, the network status information of the target service flow to be monitored is determined to be sent to the user plane network element through the uplink service flow, thereby achieving rapid real-time transmission of the network status information of the target service flow to be monitored.
  • the method further includes: the user plane network element sending the uplink service for transmitting network status information of the target service flow to be monitored to the access network device. Streaming instructions.
  • the access network device when the access network device receives the identifier of the uplink service flow and the indication information, it can determine based on the above indication information that the uplink service flow is used to transmit the network status information of the target service flow to be monitored.
  • the user plane network element obtains the identifier of the uplink service flow, including: the user plane network element receives the identifier of the uplink service flow from the access network device.
  • One possibility for the user plane network element to receive the identifier of the uplink service flow is to receive a data packet in the uplink service flow, and the data packet contains the identifier of the uplink service flow.
  • the method further includes: the user plane network element sends the Network status information of the target service flow to be monitored.
  • the user plane network element can send the network status information of the target service flow to be monitored to the third-party application server, so that the third-party application server can adjust the target service flow to be monitored based on the network status information of the target service flow to be monitored.
  • transmission parameters to avoid the impact of network congestion and changes on user service experience.
  • the network status information of the target service flow to be monitored includes the congestion status of the target service flow to be monitored, and the user plane network element sends the network status information of the target service flow to be monitored, including: the user plane network element sends At least one uplink data packet in the target uplink service flow.
  • the ratio of the number of data packets carrying an explicit congestion notification (ECN) identifier in the at least one uplink data packet to the number of the at least one uplink data packet is used to determine
  • ECN explicit congestion notification
  • a communication method includes: receiving instruction information for network status monitoring of a target service flow to be monitored; and determining an identifier of an uplink service flow based on the instruction information for network status monitoring of a target service flow to be monitored.
  • the uplink service flow is used to transmit the network status information of the target service flow to be monitored; and sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow.
  • the identification of the upstream service flow is determined according to the above instruction information, and the monitoring configuration information of the target service flow to be monitored and the identification of the upstream service flow are sent, which is conducive to realizing the integration of the monitoring configuration information and the upstream service of the target service flow to be monitored.
  • the flow identification is sent to the access network equipment and the user plane network element, so that the access network equipment can send the network status information of the target service flow to be monitored to the user plane network element according to the monitoring configuration information and the identification of the uplink service flow, as well as the user plane
  • the network element can receive the network status information of the target service flow to be monitored through the uplink service flow, thereby enabling the access network equipment to quickly transmit service flow granular network status information to the user plane network element in real time.
  • sending the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow includes: sending the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow to the session management network element. .
  • sending the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow includes: sending the monitoring configuration information and the identification of the target service flow to be monitored to the access network equipment and the user plane network element. The identifier of this upstream service flow.
  • the identifier of the uplink service flow can be sent to the access network equipment and the user plane network element together with the monitoring configuration information of the target service flow to be monitored, or the identifier of the uplink service flow can be included in the target service to be monitored.
  • the flow monitoring configuration information is sent to the access network equipment and user plane network elements, and is not limited here.
  • the target service flow to be monitored is the first QoS flow
  • the uplink service flow is the uplink service flow in the second QoS flow.
  • the target service flow to be monitored is an uplink service flow in the first QoS flow
  • the uplink service flow is an uplink service flow in the second QoS flow.
  • the first QoS flow and the second QoS flow are the same QoS flow, or the first QoS flow and the second QoS flow are different QoS flows.
  • the target service flow to be monitored is an uplink service flow in the first QoS flow
  • the uplink service flow is an uplink service flow in the second QoS flow.
  • the first QoS flow and the second QoS flow are the same QoS flow, or the first QoS flow and the second QoS flow are different QoS flows.
  • the uplink service flow used to transmit the network status information of the target service flow to be monitored may also be the second QoS flow, that is, there is no other downlink service flow in the second QoS flow.
  • the method further includes: sending for transmitting the target Indication information of the uplink service flow of the network status information of the service flow to be monitored.
  • the access network equipment and the user plane network element can receive the identifier of the uplink service flow and the indication information according to the The above indication information determines that the uplink service flow is used to transmit network status information of the target service flow to be monitored.
  • sending the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow includes: sending the monitoring configuration information of the target service flow to be monitored, the uplink service The identifier of the flow and the identifier of the target service flow to be monitored.
  • the identifier of the target service flow to be monitored has a binding relationship with the identifier of the upstream service flow to indicate that the upstream service flow is used to transmit network status information of the target service flow to be monitored.
  • a communication method includes: an access network device receiving monitoring configuration information of a target service flow to be monitored, and the monitoring configuration information is used to monitor the network status of the target service flow to be monitored; the access network device The network device determines the identifier of the uplink service flow based on the monitoring configuration information, and the uplink service flow is used to transmit the network status information of the target service flow to be monitored; the access network device sends the identifier of the uplink service flow to the user plane network element; the The access network device performs network status monitoring based on the monitoring configuration information of the target service flow to be monitored to obtain the network status information of the target service flow to be monitored; the access network device sends an uplink data packet to the user plane network element.
  • the data packet includes network status information of the target service flow to be monitored and the identifier of the upstream service flow.
  • the access network device determines the identifier of the uplink service flow and sends the identifier of the uplink service flow to the user plane network element, so that the access network device can send the uplink data packet to the user plane network element through the uplink data packet in the uplink service flow.
  • the user plane network element can determine that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identification of the uplink service flow, thereby realizing rapid real-time transmission of services from the access network equipment to the user plane network element.
  • Flow granular network state information is granular network state information.
  • the uplink data packet further includes an identifier of the target service flow to be monitored.
  • the uplink data packet sent by the access network device to the user plane network element not only includes the identification of the uplink service flow , also includes the identification of the target business flow to be monitored.
  • the user plane network element can determine that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identification of the uplink service flow and the identification of the target service flow to be monitored, thereby realizing the target service flow to be monitored. Fast real-time transmission of network status information.
  • a communication method includes: an access network device receiving monitoring configuration information of a target service flow to be monitored, and the monitoring configuration information is used to monitor the network status of the target service flow to be monitored; the access network device The network device determines the identity of the uplink service flow based on the monitoring configuration information.
  • the uplink service flow is used to transmit the network status information of the target service flow to be monitored; the access network device determines the network status based on the monitoring configuration information of the target service flow to be monitored.
  • the access network device sends an uplink data packet to the user plane network element, and the uplink data packet includes the network status information of the target service flow to be monitored, the uplink service flow The identifier and the identifier of the target business flow to be monitored.
  • the access network device determines the identity of the uplink service flow, so that the access network device can send the network status information of the target service flow to be monitored to the user plane network element through the uplink data packet in the uplink service flow.
  • the user plane network element can determine that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identification of the target service flow to be monitored included in the uplink data packet, thereby realizing the access network device to the user Face net Rapidly transmit service flow granular network status information in real time.
  • the method further includes: the access network device sending the identifier of the uplink service flow to the user plane network element.
  • a communication method includes: a user plane network element receives an uplink data packet, the uplink data packet includes an identifier of the uplink service flow, an identifier of the target service flow to be monitored, and network status information; the user The network element determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identification of the target service flow to be monitored.
  • the user plane network element can determine that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identification of the target service flow to be monitored, thereby realizing the transmission of data from the access network equipment to the user plane network element. Fast and real-time transmission of service flow granular network status information.
  • a communication device in a seventh aspect, includes a transceiver unit and a processing unit.
  • the transceiver unit is used to receive the monitoring configuration information of the target service flow to be monitored and the identification of the uplink service flow.
  • the monitoring configuration information is used for monitoring.
  • the network status of the target service flow to be monitored, the uplink service flow is used to transmit the network status information of the target service flow to be monitored;
  • the processing unit is used to perform network status monitoring based on the monitoring configuration information of the target service flow to be monitored to obtain the The network status information of the target service flow to be monitored;
  • the transceiver unit is also used to send an uplink data packet to the user plane network element.
  • the uplink data packet includes the network status information of the target service flow to be monitored and the identifier of the uplink service flow.
  • the transceiver unit is further configured to receive indication information of the uplink service flow used to transmit network status information of the target service flow to be monitored.
  • the transceiver unit is specifically configured to receive monitoring configuration information of the target service flow to be monitored, an identifier of the target service flow to be monitored, and an identifier of the uplink service flow.
  • the uplink data packet further includes an identifier of the target service flow to be monitored.
  • the target service flow to be monitored is the first QoS flow, and the uplink service flow is the uplink service flow in the second QoS flow; or, the target service flow to be monitored is The flow is a downlink service flow in the first QoS flow, and the uplink service flow is an uplink service flow in the second QoS flow; or, the target service flow to be monitored is an uplink service flow in the first QoS flow, and the uplink service flow It is the upstream service flow in the second QoS flow.
  • a communication device in an eighth aspect, includes an acquisition unit, a transceiver unit and a processing unit.
  • the acquisition unit is used to acquire an identifier of an uplink service flow.
  • the uplink service flow is used to transmit the network status of the target service flow to be monitored. information;
  • the transceiver unit is used to receive an uplink data packet, the uplink data packet includes the identifier of the uplink service flow and network status information;
  • the processing unit is used to determine the network status information included in the uplink data packet based on the identifier of the uplink service flow It is the network status information of the target service flow to be monitored.
  • the uplink service flow is used to transmit network status information of each of a plurality of to-be-monitored service flows, and the plurality of to-be-monitored service flows include the target to-be-monitored service flow. Monitor the service flow.
  • the uplink data packet also includes an identifier of the target service flow to be monitored.
  • the processing unit is specifically configured to determine the network included in the uplink data packet based on the identifier of the target service flow to be monitored and the identifier of the uplink service flow.
  • the status information is the network status information of the target service flow to be monitored.
  • the acquisition unit is the transceiver unit, and the transceiver unit is specifically configured to receive the identifier of the uplink service flow from the session management network element.
  • the transceiver unit is also used to manage the network element from the session Receive indication information of the uplink service flow used to transmit network status information of the target service flow to be monitored.
  • the transceiver unit is specifically configured to receive an identifier of the uplink service flow and an identifier of the target service flow to be monitored from the session management network element.
  • the transceiver unit is also configured to receive indication information from the application function network element to obtain the network status information of the target service flow to be monitored; the transceiver unit is also configured to provide The session management network element sends the instruction information for network status monitoring of the target service flow to be monitored.
  • the acquisition unit is the transceiver unit and the processing unit.
  • the transceiver unit is specifically configured to receive and acquire the network status of the target service flow to be monitored from the application function network element. Instruction information of the information; the processing unit is specifically configured to determine the identity of the uplink service flow based on the instruction information for obtaining the network status information of the target service flow to be monitored; the transceiver unit is also used to send the target to the access network device Monitoring configuration information of the service flow to be monitored and the identifier of the uplink service flow. The monitoring configuration information is used to monitor the network status of the target service flow to be monitored.
  • the transceiver unit is further configured to send, to the access network device, indication information of the uplink service flow for transmitting network status information of the target service flow to be monitored.
  • the acquisition unit is the transceiver unit, and the transceiver unit is specifically configured to receive the identifier of the uplink service flow from the access network device.
  • the target service flow to be monitored is the first QoS flow, and the uplink service flow is the uplink service flow in the second QoS flow; or, the target service flow to be monitored is The flow is a downlink service flow in the first QoS flow, and the uplink service flow is an uplink service flow in the second QoS flow; or, the target service flow to be monitored is an uplink service flow in the first QoS flow, and the uplink service flow It is the uplink service flow in the second QoS flow.
  • the transceiver unit is also configured to send network status information of the target service flow to be monitored.
  • the network status information of the target service flow to be monitored includes the congestion status of the target service flow to be monitored, and the transceiver unit is specifically configured to send the target uplink service flow.
  • At least one uplink data packet The ratio of the number of data packets carrying the ECN identifier in the at least one uplink data packet to the number of the at least one uplink data packet is used to determine the congestion status of the target service flow to be monitored.
  • the target uplink service flow The same business corresponds to the target business flow to be monitored.
  • a communication device in a ninth aspect, includes a transceiver unit and a processing unit.
  • the transceiver unit is configured to receive instruction information for network status monitoring of a target service flow to be monitored; the processing unit is configured to monitor the network status according to the The instruction information for network status monitoring of the target service flow to be monitored determines the identity of the uplink service flow.
  • the uplink service flow is used to transmit the network status information of the target service flow to be monitored; the transceiver unit is also used to send the network status information of the target service flow to be monitored. Monitor the configuration information and the identifier of the upstream service flow.
  • the transceiver unit is specifically configured to send the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow to the session management network element.
  • the transceiver unit is specifically configured to: send the monitoring configuration information of the target service flow to be monitored and the uplink service flow to the access network equipment and the user plane network element. logo.
  • the transceiver unit is further configured to send indication information of the uplink service flow used to transmit network status information of the target service flow to be monitored.
  • the transceiver unit is specifically configured to send the target to be monitored.
  • the target service flow to be monitored is the first QoS flow, and the uplink service flow is the uplink service flow in the second QoS flow; or, the target service flow to be monitored is The flow is a downlink service flow in the first QoS flow, and the uplink service flow is an uplink service flow in the second QoS flow; or, the target service flow to be monitored is an uplink service flow in the first QoS flow, and the uplink service flow It is the upstream service flow in the second QoS flow.
  • a communication device in a tenth aspect, includes a transceiver unit and a processing unit.
  • the transceiver unit is used to receive monitoring configuration information of a target business flow to be monitored.
  • the monitoring configuration information is used to monitor the target business flow to be monitored.
  • the processing unit is also used to perform network status monitoring based on the monitoring configuration information of the target service flow to be monitored to obtain the network status information of the target service flow to be monitored;
  • the transceiver unit is also used to send uplink data to the user plane network element
  • the uplink data packet includes the network status information of the target service flow to be monitored and the identifier of the uplink service flow.
  • the uplink data packet further includes an identifier of the target service flow to be monitored.
  • a communication device in an eleventh aspect, includes a transceiver unit and a processing unit.
  • the transceiver unit is used to receive monitoring configuration information of a target service flow to be monitored.
  • the monitoring configuration information is used to monitor the target service to be monitored.
  • the processing unit is used to determine the identity of the uplink service flow, and the uplink service flow is used to transmit the network status information of the target service flow to be monitored; the processing unit is also used to monitor the configuration of the target service flow to be monitored.
  • the transceiver unit is also used to send an uplink data packet to the user plane network element, and the uplink data packet includes the network status information of the target service flow to be monitored. , the identifier of the upstream service flow and the identifier of the target service flow to be monitored.
  • the transceiver unit is further configured to send the identifier of the uplink service flow to the user plane network element.
  • a communication device in a twelfth aspect, includes a transceiver unit and a processing unit.
  • the transceiver unit is used to receive an uplink data packet.
  • the uplink data packet includes an identifier of the uplink service flow and a target service flow of the target to be monitored. Identity and network status information; the processing unit is configured to determine, according to the identification of the target service flow to be monitored, that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored.
  • a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in the above first aspect and any possible implementation manner of the first aspect. Either by implementing the method in any one of the above fourth aspect and the possible implementation manner of the fourth aspect, or by implementing the method in any one of the above mentioned fifth aspect and the possible implementation manner of the fifth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication device is an access network device.
  • the communication interface may be a transceiver or an input/output interface.
  • the communication device is a chip configured in access network equipment.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a communication device including a processor.
  • the processor is coupled to memory and can be used to perform Instructions in the row memory are used to implement the method in any one of the above-mentioned second aspect and the possible implementation manner of the second aspect, or to implement the method in any one of the above-mentioned sixth aspect and the possible implementation manner of the sixth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication device is a user plane network element.
  • the communication interface may be a transceiver or an input/output interface.
  • the communication device is a chip configured in a user plane network element.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in the above third aspect and any possible implementation manner of the third aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication device is a policy control network element or a session management network element.
  • the communication interface may be a transceiver or an input/output interface.
  • the communication device is a chip configured in a policy control network element or a session management network element.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a processor including: an input circuit, an output circuit and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any one of the possible implementations of the first to sixth aspects.
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop and various logic circuits, etc.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, the receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by the transmitter, and the input circuit and the output A circuit may be the same circuit that functions as an input circuit and an output circuit at different times.
  • the embodiments of this application do not limit the specific implementation methods of the processor and various circuits.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in any possible implementation manner of the first to sixth aspects.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated on the same chip as the processor, or can be set in different On the chip, the embodiment of the present application does not limit the type of memory and the arrangement of the memory and the processor.
  • ROM read only memory
  • relevant data interaction processes such as sending indication information, may be a process of outputting indication information from the processor, and receiving uplink data packets may be a process of the processor receiving uplink data packets.
  • the data output by the processor can be output to the transmitter, and the input data received by the processor can be from the receiver.
  • the transmitter and receiver can be collectively called a transceiver.
  • the processing device in the above-mentioned seventeenth aspect may be one or more chips.
  • the processor in the processing device can be implemented by hardware or software.
  • the processor can be a logic circuit, an integrated circuit, etc.;
  • the processor can be a general processor, which is implemented by reading software codes stored in a memory, and the memory can Integrated in the processor, it can be located outside the processor and exist independently.
  • a computer program product includes: a computer program (which may also be called a code, or an instruction).
  • a computer program which may also be called a code, or an instruction.
  • the computer program When the computer program is run, it causes the computer to execute the above-mentioned first aspect to A method in any possible implementation manner of the sixth aspect.
  • a computer-readable storage medium stores a computer program (which may also be called a code, or an instruction) that when run on a computer enables the above-mentioned first aspect to The method in any possible implementation manner in the sixth aspect is executed.
  • a computer program which may also be called a code, or an instruction
  • a communication system including the aforementioned access network equipment and user plane network elements.
  • the communication system also includes the aforementioned policy control network element and/or session management network element.
  • Figure 1 is a schematic diagram of a communication system suitable for the method provided by the embodiment of the present application.
  • Figure 2 is a schematic flow chart of the communication method provided by the embodiment of the present application.
  • Figure 3 is a schematic flow chart of the communication method provided by the embodiment of the present application.
  • FIG. 4 is a schematic diagram of the Internet protocol (IP) header format of the data packet
  • Figure 5 is a schematic flow chart of the communication method provided by the embodiment of the present application.
  • Figure 6 is a schematic flow chart of the communication method provided by the embodiment of the present application.
  • Figure 7 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • Figure 8 is a schematic block diagram of a communication device provided by another embodiment of the present application.
  • Figure 9 is a schematic diagram of a chip system provided by an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as long term evolution (LTE) systems, frequency division duplex (FDD) systems, time division duplex (TDD) systems ) system, universal mobile telecommunication system (UMTS), global interoperability for microwave access (WiMAX) communication system, fifth generation (5th generation, 5G) system or new radio, NR), sixth generation (6G) system or future communication system, etc.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX global interoperability for microwave access
  • 5G mobile communication system described in this application includes a non-standalone (NSA) 5G mobile communication system or a standalone (SA) 5G mobile communication system.
  • the communication system can also be a public land mobile network (PLMN), a device to device (D2D) communication system, or a machine to machine (M2M) Communication system, Internet of things (IoT) communication system, vehicle to everything (V2X) communication system, unmanned aerial vehicle (UAV) communication system or other communication systems.
  • PLMN public land mobile network
  • D2D device to device
  • M2M machine to machine
  • IoT Internet of things
  • V2X vehicle to everything
  • UAV unmanned aerial vehicle
  • At least one of the following or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.
  • words such as “first” and “second” are used to distinguish identical or similar items with basically the same functions and effects.
  • words such as “first” and “second” do not limit the number and execution order, and words such as “first” and “second” do not limit the number and execution order.
  • words such as “exemplarily” or “for example” are used to represent examples, illustrations or explanations. Any embodiment or design described as “exemplary” or “such as” in the embodiments of the present application is not to be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplarily” or “for example” is intended to present related concepts in a concrete manner to facilitate understanding.
  • FIG. 1 An application scenario of the embodiment of the present application is first described in detail with reference to FIG. 1 .
  • User equipment can be called terminal equipment, terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment , user agent or user device.
  • the terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless Handheld devices with communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, drones, wearable devices, terminal devices in 5G networks or terminal devices in evolved PLMN, etc., the embodiments of this application are suitable for This is not limiting.
  • Access network Provides network access functions for authorized users in a specific area, and can use transmission tunnels of different qualities according to user levels, business needs, etc.
  • the access network may be an access network using different access technologies.
  • Current access network technologies include: wireless access network technology used in third generation (3G) systems, wireless access network technology used in fourth generation (4G) systems, or next-generation wireless Access network (next generation radio access network, NG-RAN) technology (such as the wireless access technology used in 5G systems, etc.).
  • An access network that implements access network functions based on wireless communication technology can be called a radio access network (RAN).
  • the wireless access network can manage wireless resources, provide access services to terminals, and complete the forwarding of control signals and user data between the terminals and the core network.
  • the radio access network equipment may be, for example, a base station (NodeB), an evolved base station (evolved NodeB, eNB or eNodeB), the next generation Node Base station (gNB) in the 5G mobile communication system, the base station in the future mobile communication system or the access point (AP) in the wifi wireless hotspot system, etc., can also It is a wireless controller in a cloud radio access network (CRAN) scenario, or the wireless access network device can be a relay station, access point, vehicle-mounted device, drone, wearable device, or in a 5G network network equipment or network equipment in evolved PLMN, etc.
  • CRAN cloud radio access network
  • the embodiments of this application do not limit the specific technology and specific equipment form used by the wireless access network equipment.
  • Access management network element Mainly used for mobility management and access management, responsible for transmitting user policies between user equipment and policy control function (PCF) network elements, etc., and can be used to implement mobility management entities (mobile management entity, MME) functions other than session management. For example, access authorization (authentication) function.
  • PCF policy control function
  • the access management network element can be an access and mobility management function (AMF) network element.
  • AMF access and mobility management function
  • the access management network element can still be an AMF network element, or it can have other names, which are not limited in this application.
  • Session management network element Mainly used for session management, allocation and management of Internet protocol (IP) addresses of user equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink Data communications, etc.
  • IP Internet protocol
  • the session management network element may be a session management function (SMF) network element.
  • SMF session management function
  • the session management network element can still be an SMF network element, or it can also have other names, which is not limited in this application.
  • User plane network element used for packet routing and forwarding, quality of services (QoS) processing of user plane data, completing user plane data forwarding, session/flow level-based billing statistics, bandwidth limitation functions, etc.
  • QoS quality of services
  • the user plane network element can be a user plane function (UPF) network element.
  • UPF user plane function
  • user plane network elements can still be UPF network elements, or they can have other names, which are not limited in this application.
  • Data network element used to provide a network for transmitting data.
  • the data network element may be a data network (DN) network element.
  • DN data network
  • data network elements can still be DN network elements, or they can have other names, which are not limited in this application.
  • Policy control 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 network elements, etc.).
  • the policy control network element may be a policy and charging rules function (PCRF) network element.
  • the policy control network element may be a policy control function (PCF) network element.
  • PCF policy control function
  • future communication systems the policy control network element can still be a PCF network element, or it can also have other names, which are not limited in this application.
  • Data management network element used to handle user equipment identification, access authentication, registration, and mobility management.
  • the data management network element may be a unified data management (UDM) network element; in the 4G communication system, the data management network element may be a home subscriber server (HSS) network element. Yuan. In future communication systems, the data management network element can still be a UDM network element, or it can also have other names, which is not limited in this application.
  • UDM unified data management
  • HSS home subscriber server
  • Network exposure function (NEF) network element used to safely open to the outside the services and capabilities provided by the 3rd generation partnership project (3rd generation partnership project, 3GPP) network functions.
  • Application function (AF) network element Provides certain application layer services to UE. When AF provides services to UE, it has requirements for QoS policies and charging policies, and needs to notify the network. At the same time, AF also needs to obtain information related to core network feedback applications.
  • the AF can have all the functions of the AF defined in the technical specification (TS) 23.501R-15 version, as well as related functions for application services. That is to say, in the user plane architecture, the application server and the UE communicate on the user plane through the UE-RAN-UPF-AF path. AF can also communicate with other network functions (NF) in the 5G core network (5G core network, 5GC) through NEF in the control plane architecture. For example, communicating with PCF through NEF. If the AF is deployed by the operator of 5GC, the AF can also be in the control plane architecture, that is, the AF is in the trusted domain and does not directly communicate with other NFs in the 5GC through NEF, such as directly communicating with the PCF.
  • NF network functions
  • NWDAF Network data analysis function
  • OAM operation administration and maintenance
  • the solution analyzes the data and provides feedback to network elements, AF, etc. for network or service configuration optimization, thereby providing better network quality and service experience.
  • Network repository function (NRF) network element It can be used to provide network element discovery functions and provide network element information corresponding to the network element type based on the requests of other network elements. NRF network elements also provide network element management services, such as network element registration, update, de-registration, network element status subscription and push, etc.
  • AUSF Authentication server function
  • Service communication proxy (SCP) network element It can be used for indirect communication between NFs. The service requests of NF can be proxied by the SCP network element.
  • N1, N2, N3, N4, N6, N9, Nnwdaf, Nnef, Nnrf, Npcf, Nudm, Naf, Nausf, Namf and Nsmf are interface serial numbers. The meaning of these interface serial numbers can be found in the meaning defined in 3GPP technical standards (TS) 23.501.
  • the AMF, SMF, UPF, NEF, PCF, UDM, NWDAF, NRF, AUSF, SCP, etc. shown in Figure 1 can be understood as network elements used to implement different functions in the core network. For example, they can be combined as needed. Network slicing. These core network elements can be independent devices, or can be integrated into the same device to implement different functions. This application does not limit the specific forms of the above network elements.
  • the third-party application can sense the network status in real time, the third-party application can make corresponding adjustments according to the network status, thereby ensuring the user's business experience and maximizing network utilization efficiency. Therefore, how to quickly expose more network status information, such as available bandwidth and congestion conditions, to third-party applications is a key issue.
  • the RAN can monitor the congestion status of the network and release the congestion status of the network by marking the ECN in the IP version 4 (IPv4) header of the downlink data packet. For example, the RAN adds an ECN identifier to the packet data convergence protocol (PDCP) header (i.e., PDCP service data unit (SDU)) of the downlink data packet and sends the downlink data packet to the UE. The UE then sends the downlink data packet to the application server side through the application layer, so that the third-party application can obtain the congestion status of the network.
  • PDCP packet data convergence protocol
  • SDU packet data convergence protocol
  • the UE sends the downlink data packet to the application server side through the application layer, so that the third-party application can obtain the congestion status of the network.
  • the transmission link is long and the timeliness is poor due to network congestion.
  • the above method requires the RAN to parse the IP header of the downlink data packet, which poses security risks.
  • network status information can be exposed to the application layer in the form of a control plane or a user plane.
  • network status information can be exposed to third-party applications through the UPF service interface or NEF.
  • UPF can add network status information to the data packet and send it to the application server side.
  • UPF since UPF cannot monitor the network status between the air interface side RAN and UE, if the RAN needs to obtain the network status information between the air interface side RAN and UE from a third party application, UPF can only obtain the network status information between the air interface side RAN and UE from the RAN. Receive network status information on the air interface side. In this case, how the RAN sends the network status information on the air interface side to the UPF will become an urgent problem to be solved.
  • embodiments of the present application provide a communication method that enables the RAN to send the network status information obtained by monitoring the network status to the UPF.
  • the service flow from the terminal device or the access network device and whose destination address is the third-party application server is called an uplink service flow.
  • the service flow from the third-party application server with the destination address being the terminal device is called the downstream service flow.
  • the third-party application server provides the terminal device with application services corresponding to the uplink service flow and/or the downlink service flow.
  • the user plane network element mentioned in the embodiment of this application may be UPF
  • the session management network element may be SMF
  • the policy control network element may be PCF
  • the access network device may be RAN.
  • FIG. 2 shows a schematic flow chart of the communication method provided by the embodiment of the present application. Various steps included in the method 200 are described in detail below.
  • the user plane network element obtains the identifier of the uplink service flow.
  • the upstream service flow is used to transmit network status information of the target service flow to be monitored.
  • the upstream service flow used to transmit the target service flow to be monitored is recorded as upstream service flow #1 in the following.
  • the identifier of upstream service flow #1 is used to identify upstream service flow #1.
  • the identification of upstream service flow #1 includes one or more of the following: data connection session identification (such as: protocol data unit (PDU) session identification #1, or IP-CAN session identification, or other The identifier of the session (for the convenience of description, the subsequent examples will take the PDU session as an example), business flow description information #1, application identifier #1, second OoS flow identifier (QoS flow identifier, QFI), service type identifier #1 and Application Type Identification #1.
  • data connection session identification such as: protocol data unit (PDU) session identification #1, or IP-CAN session identification, or other
  • PDU protocol data unit
  • IP-CAN session identification IP-CAN session identification
  • the PDU session identifier #1 is the session identifier information of the PDU session #1 carrying the uplink service flow #1. For example, if PDU session #1 only carries uplink service flow #1, the identifier of uplink service flow #1 may be PDU session identifier #1.
  • Service flow description information #1 is used to determine uplink service flow #1.
  • the service flow description information #1 may be at least one of the IP five-tuple description information, IP triplet information, domain name, uplink and downlink IP data packet filtering sets of the uplink service flow #1.
  • the IP five-tuple description information of upstream service flow #1 can be: source IP address (source IP address) #1, destination IP Address (destination IP address) #1, source port number (source port number) #1, destination port number (destination port number) #1 and protocol type #1.
  • the IP triplet information of upstream service flow #1 may be: destination IP address #1, destination port number #1, and protocol type #1.
  • the service flow description information #1 can be at least one of the Ethernet (ethernet) header information, for example, source media access control (MAC) address #1 and destination MAC address #1, virtual local area (virtual local area) network, VLAN) identification #1, etc.
  • the service flow description information #1 may also include application identification #1.
  • the service flow description information #1 may also be called service data flow (service data flow, SDF) description information #1.
  • SDF description information please refer to the IP packet filter set.
  • the description of the IP packet filter set please refer to the description in 3GPP TS 23.501.
  • Application identifier #1 is used to identify application #1 corresponding to upstream service flow #1. For example, if application #1 only has uplink service flow #1 but no downlink service flow, the identifier of uplink service flow #1 may be application identifier #1.
  • the second QFI is used to identify the second QoS flow, and the uplink service flow #1 is transmitted in the second QoS flow.
  • the identifier of the uplink service flow #1 can be the second QFI, or it can be said that the uplink service flow #1 Flow #1 is the second QoS flow.
  • the service type identifier #1 may be an identifier of the type of the uplink service flow #1.
  • the type of the uplink service flow #1 may be a video service, a voice service, a game service, or a web browsing service.
  • the application type identifier #1 may be an identifier of the type of application #1 corresponding to the uplink service flow #1.
  • the target service flow to be monitored may be an uplink service flow or a downlink service flow, which is not limited in this embodiment of the present application.
  • the target service flow to be monitored is a downstream service flow
  • the target service flow to be monitored and the uplink service flow #1 correspond to the same service
  • the target service to be monitored and the uplink service flow #1 correspond to different services.
  • the target service flow to be monitored is an uplink service flow
  • the target service flow to be monitored and the uplink service flow #1 are the same service flow, or the target service flow to be monitored and the uplink service flow #1 are different services. flow.
  • the method 200 further includes: the user plane network element obtains the identifier of the target service flow to be monitored, and the identifier of the target service flow to be monitored is used to identify the target service flow to be monitored.
  • the identification of the target service flow to be monitored may include one or more of the following: data connection identification (for example: PDU session identification #2), business flow description information #2, application identification #2, first QFI, service type identification #2 and application type identification #2.
  • the user plane network element can determine that the network will monitor the network status of the target service flow to be monitored.
  • the user plane network element can determine that the upstream service flow #1 is used to transmit network status information of the target service flow to be monitored.
  • the PDU session identifier #2 is the session identifier information of the PDU session #2 carrying the target service flow to be monitored. For example, if PDU session #2 only carries the target service flow to be monitored, the identifier of the target service flow to be monitored may be PDU session identifier #2.
  • Service flow description information #2 is used to determine the target service flow to be monitored.
  • Service flow description information #2 may refer to the description of service flow description information #1.
  • Application identifier #2 is used to identify application #2 corresponding to the target service flow to be monitored. For example, if application #2 only has a target service flow to be monitored and no other service flows, the identifier of the target service flow to be monitored may be application identifier #2.
  • the first QFI is used to identify the first QoS flow, and the target service flow to be monitored is transmitted in the first QoS flow. If the first QoS flow only corresponds to the target to-be-monitored service flow aggregation, that is, only the target to-be-monitored service flow is transmitted in the first QoS flow, then the identifier of the target to-be-monitored service flow can be the first QFI, which can also be said to be the target to-be-monitored service. The flow is the first QoS flow.
  • Service type identifier #2 may be an identifier of the type of the target service flow to be monitored, for example, the target service flow to be monitored
  • the types can be video services, voice services, game services or web browsing services, etc.
  • the application type identifier #2 may be an identifier of the type of application #2 corresponding to the target service flow to be monitored.
  • the target service flow to be monitored is a downstream service flow
  • the target service flow to be monitored corresponds to the same service as the upstream service flow #1
  • the second QoS flow corresponding to the upstream service flow #1 is the same as the target service to be monitored.
  • the first QoS flow corresponding to the flow may be the same QoS flow, or the second QoS flow and the first QoS flow may be different QoS flows.
  • the target service flow to be monitored is an upstream service flow
  • the target service flow to be monitored is the same service flow as the upstream service flow #1
  • the second QoS flow corresponding to the upstream service flow #1 and the third QoS flow corresponding to the target service flow to be monitored are A QoS flow can be the same QoS flow.
  • the target service flow to be monitored is an upstream service flow
  • the target service flow to be monitored is a different service flow from the upstream service flow #1
  • the second QoS flow corresponding to the upstream service flow #1 corresponds to the target service flow to be monitored.
  • the first QoS flow is a different QoS flow.
  • the embodiment of this application does not limit the way in which the user plane network element obtains the identifier of the uplink service flow #1.
  • the user plane network element obtains the identifier of the uplink service flow #1, including: the user plane network element receives the identifier of the uplink service flow #1 from the session management network element.
  • the session management network element sends the identifier of the uplink service flow #1 to the user plane network element.
  • S340 For more description about the identifier of the uplink service flow #1 sent by the session management network element to the user plane network element, please refer to S340 in the method 300 below. For the sake of brevity, it will not be described in detail here.
  • the method 200 further includes: the session management network element determines the identifier of the uplink service flow #1.
  • the session management network element determines the identity of the upstream service flow #1.
  • the method 200 further includes: the session management network element receives the monitoring configuration information of the target service flow to be monitored from the policy control network element and Identification of upstream traffic flow #1.
  • the policy control network element determines the identifier of the upstream service flow #1, and sends the monitoring configuration information of the target service flow to be monitored and the identifier of the upstream service flow #1 to the session management network element.
  • the process of the policy control network element determining the identifier of the upstream service flow #1 please refer to the method 500 below. For the sake of simplicity, the details will not be described here.
  • the user plane network element obtains the identity of the uplink service flow #1, including: the user plane network element receives instruction information from the application function network element to obtain the network status information of the target service flow to be monitored; The surface network element determines the identity of the upstream service flow #1 based on the indication information for obtaining the network status information of the target service flow to be monitored.
  • the process of the user plane network element determining the identity of the uplink service flow #1 please refer to the method 600 below. For the sake of simplicity, the details will not be described here.
  • the user plane network element obtains the identity of the uplink service flow #1, including: the user plane network element receives the identity of the uplink service flow #1 from the access network device.
  • the access network device sends the identifier of the uplink service flow #1 to the user plane network element.
  • the user plane network element receives the identifier of the uplink service flow #1 from the access network device, including: the user plane network element receives the identifier of the uplink service flow #1 from the access network device and the target service flow to be monitored. logo.
  • the method 200 further includes: the user plane network element receiving indication information from the access network device for transmitting the uplink service flow #1 of the target service flow to be monitored.
  • the indication information for transmitting the uplink service flow #1 of the target service flow to be monitored will be recorded as indication information #1 in the following.
  • the indication information #1 may be 1-bit information.
  • the indication information #1 is the monitoring configuration information of the target service flow to be monitored or an event identifier. The event identifier is used to indicate the network status information of the target service flow to be monitored, and/or is used to Indicates the network status information of the open target service flow to be monitored.
  • the event identification and "subscription target industry to be monitored” Corresponds to the event “Network status information of the service flow” or the event “Network status information of the open target service flow to be monitored”.
  • the event identifier may include monitoring parameters and the reported information of the target network element or entity. Monitoring parameters may include the following One or more: transmission delay, packet loss rate, congestion level, length of send data queue and available bandwidth
  • the user plane network element obtains the identifier of the uplink service flow #1 from the uplink data packet.
  • the access network device adds the identifier of the uplink service flow #1 in the uplink data packet sent to the user plane network element. That is, S210 can be executed between S240 and S250.
  • the access network device can carry the identification information of the uplink service flow #1 and the indication information #1 in the same message and send it to the user plane network element, or the access network device can send the identification information of the uplink service flow #1 to the user plane network element.
  • the identification and indication information #1 are carried in different messages and sent to the user plane network element.
  • the method 200 further includes: the access network device determines the identifier of the uplink service flow #1.
  • the access network device determines the identity of the uplink service flow #1.
  • the embodiment of the present application does not limit the uplink service flow #1 to only be used to transmit network status information of the target service flow to be monitored.
  • the uplink service flow #1 may be used to transmit network status information of each service flow to be monitored among multiple service flows to be monitored, and the plurality of service flows to be monitored include the target service flow to be monitored.
  • the multiple service flows to be monitored also include uplink service flow #1.
  • this step is optional. For example, if the identifier of uplink service flow #1 is determined by the access network device, the access network device may not send the identifier of uplink service flow #1 to the user plane network element.
  • the method 200 further includes: the session management network element sending the monitoring configuration information of the target service flow to be monitored to the user plane network element.
  • the monitoring configuration information of the target service flow to be monitored is used to monitor the network status of the target service flow to be monitored.
  • the monitoring configuration information of the target service flow to be monitored includes monitoring parameters and the identification of the target service flow to be monitored or the user plane general packet wireless network (general packet radio network). packet radio system, GPRS) tunneling protocol (GPRS tunneling protocol user plane, GTP-U) tunnel identification.
  • the monitoring parameters may include one or more of the following: transmission delay, packet loss rate, congestion level, length of the sending data queue, and available bandwidth.
  • the monitoring configuration information of the target service flow to be monitored may also include a reporting period of network status information of the target service flow to be monitored.
  • the monitoring configuration information of the target service flow to be monitored may also include triggering conditions for reporting network status information of the target service flow to be monitored. For example, if the monitoring configuration information of the target service flow to be monitored includes a transmission delay threshold, then when the transmission delay of the target service flow to be monitored exceeds the transmission delay threshold, reporting of the network status information of the target service flow to be monitored is triggered.
  • the monitoring configuration information of the target service flow to be monitored may also include an event identifier used to indicate subscribing to the network status information of the target service flow to be monitored.
  • the monitoring configuration information of the target service flow to be monitored may also include a method of reporting the network status information of the target service flow to be monitored.
  • the method of reporting the network status information of the target service flow to be monitored is: by the user plane network element or The access network device reports to the session management network element; or the access network device reports to the user plane network element; or the user plane network element directly opens it to the outside world.
  • the monitoring configuration information of the target service flow to be monitored also includes reporting target network element or entity information.
  • the reporting target network element or entity information is used to indicate the target network element or target entity that reports the network status information of the target service flow to be monitored, or the reporting target network element or entity information is used to indicate the network used to receive the target service flow to be monitored.
  • the target network element or target entity of the status information is used to indicate the target network element or target entity that reports the network status information of the target service flow to be monitored.
  • the GTP-U tunnel identifier is used to identify the GTP-U tunnel that carries the target service flow to be monitored between the access network device and the user plane network element. For example, if the GTP-U tunnel only carries the target business flow to be monitored, then the target business flow to be monitored is The monitoring configuration information of the service flow may include the identifier of the GTP-U tunnel. Alternatively, if the target service flow to be monitored is the set of all service flows on the GTP-U tunnel, then the monitoring configuration information may include the identifier of the GTP-U tunnel.
  • the access network device obtains the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow.
  • the access network device receives the identifier of the uplink service flow, which is the identifier of the uplink service flow #1 described above.
  • the identifier of upstream service flow #1 may be included in the monitoring configuration information, or may be outside the monitoring configuration information, which is not limited here.
  • the access network device obtains the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1, including: the access network device receives the monitoring of the target service flow to be monitored from the session management network element. Configuration information and identification of upstream service flow #1.
  • the session management network element sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the access network device.
  • S330 for more description about the session management network element sending the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the access network device, please refer to S330 in method 300 below. For the sake of brevity, it is not detailed here. narrate.
  • the method 200 further includes: the session management network element determines the uplink service flow #1 Monitoring configuration information that identifies and targets the business flow to be monitored.
  • the process for the session management network element to determine the identity of the upstream service flow #1 and the monitoring configuration information of the target service flow to be monitored can be referred to the method 300 below. For the sake of simplicity, it will not be described in detail here.
  • the method 200 further includes: the session management network element receives a message from the policy control network element.
  • the access network device obtains the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1, including: the access network device receives the target service flow to be monitored from the user plane network element. Monitor configuration information and identification of upstream service flow #1.
  • the user plane network element sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the access network device.
  • S630 for more description about the user plane network element sending the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the access network device, please refer to S630 in method 600 below. For the sake of brevity, it is not detailed here. narrate.
  • the method 200 further includes: the user plane network element determines the identity of the uplink service flow #1 and Obtain the monitoring configuration information of the target business flow to be monitored.
  • the user plane network element determines the identity of the uplink service flow #1 and Obtain the monitoring configuration information of the target business flow to be monitored.
  • the method for the user plane network element to obtain the monitoring configuration information of the target service flow to be monitored includes: the user plane network element receives the monitoring configuration information of the target service flow to be monitored from the session management network element.
  • the access network device obtains the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1, including: the access network device receives the target service flow to be monitored from the session management network element monitoring configuration information; the access network equipment receives the identification of uplink service flow #1 from the user plane network element.
  • the access network device receives the identifier of the uplink service flow #1 from the user plane network element, including: the access network device receives the identifier of the uplink service flow #1 from the user plane network element and the target service flow to be monitored. logo.
  • the method 200 further includes: the access network device receiving indication information #1 from the user plane network element.
  • the access network device obtains the monitoring configuration information and uplink configuration information of the target service flow to be monitored.
  • the identification of service flow #1 includes: the access network device receives the monitoring configuration information of the target service flow to be monitored from the session management network element or the user plane network element; the access network device determines the uplink service flow #1 based on the monitoring configuration information. logo.
  • the access network device determines to perform network status monitoring on the target service flow to be monitored according to the monitoring configuration information of the target service flow to be monitored. Further, the access network device selects an uplink service flow #1 from the established uplink service flows for transmitting the network status information of the target service flow to be monitored.
  • the upstream service flow #1 and the target service flow to be monitored belong to the same GTP-U tunnel.
  • the access network device performs network status monitoring based on the monitoring configuration information of the target service flow to be monitored to obtain network status information of the target service flow to be monitored.
  • the access network device determines to perform network status monitoring for the target service flow to be monitored based on the identifier of the target service flow to be monitored or the GTP-U tunnel identifier included in the monitoring configuration information. Further, the access network device performs network status monitoring based on the monitoring parameters included in the monitoring configuration information. For example, the access network device may perform network monitoring on the radio bearer where the target service flow to be monitored is located. For example, if the monitoring parameter includes transmission delay, the access network device monitors the transmission delay of data packets in the target service flow to be monitored between the access network device and the user plane network element. If the monitoring parameter includes the packet loss rate, the access network device monitors the packet loss rate of the data packets in the target service flow to be monitored.
  • the access network device monitors the sending queue length of the data packets in the target service flow to be monitored. It should be noted that the sending queue length can be the PDCP layer or MAC on the access network device side. The sending queues in different layers such as layers are not limited here. If the monitoring parameter includes available bandwidth, the access network device monitors the available bandwidth of the target service flow to be monitored. If the monitoring parameter includes the congestion level, the access network device monitors the congestion level of the target service flow to be monitored.
  • the congestion level of the target service flow to be monitored can be obtained by monitoring the transmission delay, packet loss rate, sending data queue length or available bandwidth.
  • the access network device determines whether the target service flow to be monitored is congested by comparing the transmission delay of the data packets in the target service flow to be monitored with the transmission delay threshold, or determines the congestion situation of the target service flow to be monitored, or determines Network status information of the target service flow to be monitored. For example, if the data packet transmission delay in the target service flow to be monitored exceeds the transmission delay threshold, the access network device determines that congestion occurs in the target service flow to be monitored.
  • the access network device can calculate the transmission delay based on the transmission delay of the data packet in the target service flow to be monitored and the transmission delay threshold. , determine the congestion degree of the target service flow to be monitored. For example, if the ratio of the transmission delay of the data packets in the target service flow to be monitored to the transmission delay threshold is 60%, the access network device determines that the congestion level of the target service flow to be monitored is 60%.
  • the access network device can determine whether the target service flow to be monitored is congested or determine the congestion situation of the target service flow to be monitored by comparing the packet loss rate of the data packets in the target service flow to be monitored with the packet loss rate threshold. Or determine the network status information of the target service flow to be monitored. Alternatively, the access network device determines the congestion level of the target service flow to be monitored based on the ratio of the packet loss rate of the data packets in the target service flow to be monitored and the packet loss rate threshold.
  • the access network device can also determine whether the target service flow to be monitored is congested, or determine the congestion situation of the target service flow to be monitored, or determine the target service to be monitored by comparing the send queue length of the target service flow to be monitored with the send queue length threshold. Network status information for the flow. Alternatively, the access network device determines the congestion level of the target service flow to be monitored based on the ratio of the sending queue length of the target service flow to be monitored and the sending queue length threshold.
  • the access network device can also determine whether the target service flow to be monitored is congested by comparing the available bandwidth of the target service flow to be monitored with the available bandwidth threshold, or determine the congestion situation of the target service flow to be monitored, or determine the flow of the target service flow to be monitored. Network status information.
  • the access network equipment may configure the access network device according to the available bandwidth of the target service flow to be monitored and the available bandwidth. The ratio of the wide threshold determines the congestion level of the target service flow to be monitored.
  • the transmission delay threshold, packet loss rate threshold, sending queue length threshold or available bandwidth threshold may be included in the monitoring configuration information of the target service flow to be monitored, or may be predefined by the protocol, which is not limited in the embodiments of this application.
  • the network status information of the target service flow to be monitored obtained by the access network device through network status monitoring is related to the monitoring parameters. For example, if the monitoring parameters include transmission delay, then the network status information of the target service flow to be monitored includes the transmission delay of the data packets in the target service flow to be monitored. For another example, if the monitoring parameter includes the degree of congestion, then the network status information of the target service flow to be monitored includes the congestion information of the target service flow to be monitored. The congestion information is used to determine whether the target service flow to be monitored is congested and/or the target service flow to be monitored is. degree of congestion.
  • S240 The access network device sends the uplink data packet to the user plane network element.
  • the user plane network element receives the uplink data packet from the access network device.
  • the uplink data packet includes the identification of the uplink service flow #1 and the network status information of the target service flow to be monitored. That is to say, the uplink data packet is the data packet in the uplink service flow #1.
  • the uplink data packet may be a data packet received by the access network device from the terminal device, or the uplink data packet may be an empty data packet generated by the access network device.
  • the identifier of the uplink service flow #1 included in the uplink data packet may be the second QFI.
  • the second QFI is carried in the GTP-U layer header of the uplink data packet.
  • the network status information of the target service flow to be monitored is included in the GTP-U layer header of the uplink data packet.
  • the access network device once the access network device obtains the network status information of the target service flow to be monitored, it sends the network status of the target service flow to be monitored to the user plane network element through the uplink data packet in uplink service flow #1. information.
  • the access network device periodically sends uplink data packets in the uplink service flow #1 to the user plane according to the reporting period.
  • the network element sends the network status information of the target service flow to be monitored.
  • the access network device sends the network status information of the target service flow to be monitored to the user plane network element through the uplink data packet in uplink service flow #1 every 10 seconds.
  • the monitoring configuration information of the target service flow to be monitored includes a trigger condition for reporting the network status information of the target service flow to be monitored
  • the access network device passes The uplink data packet in the uplink service flow #1 sends the network status information of the target service flow to be monitored to the user plane network element.
  • the trigger condition is that the transmission delay exceeds the transmission delay threshold or the sending queue length exceeds the sending queue length threshold, etc., then the transmission delay of the data packets in the target service flow to be monitored exceeds the transmission delay threshold or the sending queue length exceeds
  • the access network device sends the network status information of the target service flow to be monitored to the user plane network element through the uplink data packet of uplink service flow #1.
  • the uplink data packet also includes the identification of the target service flow to be monitored.
  • the access network device can add the identifier of the target service flow to be monitored in the uplink data packet.
  • the access network device will Add the identifier of the target service flow to be monitored, so that the user plane network element determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored.
  • the access network device adds the identifier of the target service flow to be monitored in the uplink data packet, and the uplink data packet will carry the identifier of the uplink service flow #1.
  • the monitoring configuration information of the target service flow to be monitored includes a method of reporting network status information of the target service flow to be monitored, and the method is reported by the access network device to the user plane network element, then in S240, continue Network access equipment
  • the user plane network element sends an uplink data packet including network status information of the target service flow to be monitored.
  • the user plane network element determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identifier of the uplink service flow and/or the identifier of the target service flow to be monitored.
  • uplink service flow #1 is used to transmit the network status information of the target service flow to be monitored. Therefore, after the user plane network element receives the uplink data packet from the access network device, it can The identifier #1 determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored.
  • the GTP-U layer header of the uplink data packet includes the identifier and target of upstream service flow #1
  • the user plane network element determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored based on the identification of the upstream service flow #1 and the identification of the target service flow to be monitored.
  • the user plane network element determines whether the network status information included in the uplink data packet is the network status information of the target service flow to be monitored.
  • the method 200 further includes: the user plane network element sending network status information of the target service flow to be monitored.
  • the process of the user plane network element sending the network status information of the target service flow to be monitored please refer to the method 300 below. For the sake of simplicity, it will not be described in detail here.
  • both the access network device and the user plane network element can obtain the identifier of the uplink service flow used to transmit the network status information of the target service flow to be monitored, and then the access network device can use the uplink service flow#
  • the uplink data packet in 1 sends the network status information of the target service flow to be monitored to the user plane network element, and the user plane network element can use the identification of the uplink service flow #1 included in the uplink data packet and/or the identity of the target service flow to be monitored.
  • the identification determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored.
  • This method realizes that the access network equipment sends the network status information of the target service flow to be monitored to the user plane network element, so that the user plane network element can open the received network status information to third-party applications, so that the third-party application can
  • the status information adjusts the transmission parameters of the target business flow to be monitored to ensure the user's business experience. For example, if the target service flow to be monitored is a downstream service flow, even if there is no uplink data flow in the target service flow to be monitored, the access network device can still send the network status information of the target service flow to be monitored to the user plane network element.
  • media services media services are carried on two different service flows at the same time.
  • the upstream service flow of the media service transmits some control information of the service session or gesture information such as the user's perspective and actions, while the downstream service flow of the media service is only responsible for the delivery of downlink media data, that is, a single service flow only contains a single directional business flow. If the access network equipment monitors congestion information for the downlink service flow of the media service, the access network equipment cannot quickly send the network status information of the downlink service flow of the media service because there is no uplink data flow in the downlink service flow of the media service. to user plane network elements.
  • the access network device can transfer the downlink service flow of the media service to The network status information of the service flow is quickly sent to the user plane network element.
  • the access network device sends network status information at the service flow granularity to the user plane network element. If the user plane network element opens the network status information at the service flow granularity to a third-party application server, Then the third-party application server can adjust the parameters of the business flow according to the network status information of the business flow, thereby adapting to changes in the network status and meeting the user's experience requirements for different business flows.
  • Figure 3 shows a schematic flow chart of the communication method provided by the embodiment of the present application. Specifically, Figure 3 shows the method flow of the embodiment in which the session management network element determines the identity of the upstream service flow #1 mentioned in the method 200, and Figure 3 shows The method process of the user plane network element sending the network status information of the target service flow to be monitored mentioned in the method 200 is described. Each step included in the method 300 is described in detail below.
  • the session management network element receives instruction information for network status monitoring of the target service flow to be monitored.
  • S310 includes S311 and S312.
  • the application function network element sends instruction information #2 to the policy control network element.
  • the policy control network element receives indication information #2 from the application function network element.
  • Instruction information #2 is used to instruct network status monitoring of the target service flow to be monitored, and/or to indicate the identification of the uplink service flow #1 used to transmit the target service flow to be monitored.
  • the embodiment of the present application does not limit the form of the indication information #2, and it may be one or more of the following examples.
  • the indication information #2 is the service flow description information #2
  • the service flow description information #2 is used to determine the target service flow to be monitored.
  • business flow description information #2 please refer to S210 above.
  • the indication information #2 is 1-bit information.
  • indication information #2 is an event identification.
  • the description of the event identifier may refer to S210 above.
  • the indication information #2 is an event reporting triggering condition
  • the event reporting triggering condition is used to indicate a triggering condition for opening network status information of the target service flow to be monitored to the outside world. Such as opening to the outside world at fixed intervals, event triggering, etc.
  • the embodiment of this application does not limit the manner in which the application function network element sends the instruction information #2 to the policy control network element.
  • the application function network element may send instruction information #2 to the policy control network element through an application function request (AF request) message. That is, the application function network element sends an AF request message to the policy control network element, and the AF request message includes indication information #2.
  • AF request application function request
  • the application function network element directly sends the instruction information #2 to the policy control network element, or the application function network element first sends the instruction information #2 to the network exposure function (NEF), and the network exposure function network The network element then forwards the instruction information #2 to the policy control network element.
  • NEF network exposure function
  • the application function network element sends service flow description information #2 to the policy control network element.
  • the network element sends service flow description information #2 and instruction information #2.
  • the application function network element sends an AF request message to the policy control network element.
  • the AF request message includes service flow description information #2 and indication information #2.
  • the policy control network element sends instruction information #3 to the session management network element.
  • the session management network element receives the instruction information #3 from the policy control network element.
  • the instruction information #3 is used to instruct the network status monitoring of the target service flow to be monitored, or the instruction information #3 is used to instruct the session management network element to generate monitoring configuration information of the target service flow to be monitored, regarding the target service flow to be monitored.
  • the monitoring configuration information please refer to S210 above.
  • the indication information #3 may also be used to indicate the identification of the uplink service flow #1 that is determined to be used to transmit the target service flow to be monitored.
  • the form of instruction information #3 please refer to the description of the form of instruction information #2.
  • the indication information #3 may be generated by the policy control function network element according to the indication information #2, or the indication information #3 is equal to the indication information #2, which is not limited in this embodiment of the present application.
  • the policy control network element if the policy control network element has not previously sent the monitoring configuration policy of the target service flow to be monitored to the session management network element, then in S312, the policy control network element also sends the monitoring configuration policy of the target service flow to be monitored to the session management network element.
  • Monitor configuration strategies For more description about the monitoring configuration policy of the target service flow to be monitored, please refer to S320 below.
  • the indication information #3 may be included in the monitoring configuration policy.
  • the policy control network element may not send the target service flow to be monitored to the session management network element. Monitoring configuration policy, but after S312, if the policy control network element receives a policy request message from the session management network element, the policy request message is used to request the monitoring configuration policy of the target service flow to be monitored. Then, the policy control network element responds to the policy request message and sends the monitoring configuration policy of the target service flow to be monitored to the session management network element.
  • the policy control network element sends the instruction information #3 to the session management network element side during the session management policy association establishment or modification process.
  • S310 includes S313 and S314.
  • the application function network element sends instruction information #4 to the user plane network element.
  • the user plane network element receives indication information #4 from the application function network element.
  • the instruction information #4 is used to instruct to obtain the network status information of the target service flow to be monitored, and/or the instruction information #4 can be used to instruct to monitor the network status of the target service flow to be monitored.
  • indication information #4 please refer to the description of the form of indication information #2.
  • the application function network element may call the UPF service interface-subscription (Nupf_subscribe) service interface to send the instruction information #4 to the user plane network element.
  • UPF service interface-subscription Nupf_subscribe
  • the application function network element first sends the instruction information #4 to the network opening function network element, and the network opening function network element then forwards the instruction information #4 to the user plane network element.
  • the application function network element sends the service flow description information #4 to the user plane network element.
  • the network element sends service flow description information #2 and instruction information #4.
  • the user plane network element sends instruction information #5 to the session management network element.
  • the session management network element receives indication information #5 from the user plane network element.
  • the instruction information #5 is used to instruct network status monitoring of the target service flow to be monitored. Or the instruction information #5 is used to instruct the session management network element to generate monitoring configuration information of the target service flow to be monitored.
  • the form of instruction information #5 please refer to the description of the form of instruction information #2.
  • the user plane network element sends the instruction information #5 to the session management network element through the N4 message. That is, the user plane network element sends an N4 message to the session management network element, and the N4 message includes indication information #5.
  • the user plane network element may send the service flow description information #2 and the indication information #5 to the session management network element.
  • S320 The session management network element determines the identifier of upstream service flow #1.
  • the session management network element determines the identity of the uplink service flow #1 based on the instruction information for network status monitoring of the target service flow to be monitored (ie, the above instruction information #3 or instruction information #5).
  • the session management network element determines the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored in response to the instruction information #3 or the instruction information #5. , and determine the identity of upstream service flow #1.
  • the session management network element responds to the indication information #3 or the indication information #5 and determines the uplink service flow #1 according to the service flow description information #2. That is to say, the session management network element first determines the target service flow to be monitored based on the service flow description information #2, and then determines the uplink service flow #1 for the target service flow to be monitored.
  • the session management network element may determine the upstream service flow of the same service corresponding to the target service flow to be monitored as the network status information used to transmit the target service flow to be monitored.
  • Upstream traffic flow #1 the uplink service flow of the same service corresponding to the target service flow to be monitored may be the service flow corresponding to the service flow description information #2, or it may be the service flow corresponding to part of the description information in the service flow description information #2. business flow.
  • the session management network element may also determine the uplink service flow corresponding to different services from the target service flow to be monitored as the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored.
  • the session management network element may determine the target service flow to be monitored as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the session management network element may also determine the uplink service flow corresponding to different services from the target service flow to be monitored as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the session management network element may determine the uplink service flow not used to transmit any network status information as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the session management network element may determine the uplink service flow with a higher transmission frequency as the uplink service flow used to transmit the network status information of the target service flow to be monitored.# 1.
  • the access network device can quickly send the network status information of the target service flow to be monitored to the user plane network element.
  • the session management network element may determine the uplink service flow corresponding to the same QoS flow as the target service flow to be monitored as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the session management network element determines the identity of the upstream service flow #1 based on the determined upstream service flow #1.
  • the session management network element determines the monitoring configuration information of the target service flow to be monitored.
  • the method for the session management network element to determine the monitoring configuration information of the target service flow to be monitored includes: the session management network element receives the monitoring configuration policy of the target service flow to be monitored from the policy control network element; the session management network element determines the target service flow to be monitored according to the monitoring configuration policy.
  • Monitoring configuration information for monitoring business flows includes the identification and monitoring parameters of the target service flow to be monitored.
  • the monitoring configuration policy of the target service flow to be monitored also includes a trigger condition for reporting network status information of the target service flow to be monitored.
  • the monitoring configuration information of the target service flow to be monitored may also include an event identifier used to indicate subscribing to the network status information of the target service flow to be monitored.
  • the monitoring configuration information of the target service flow to be monitored also includes a method for reporting network status information of the target service flow to be monitored. That is to say, the session management network element can extract the monitoring configuration information of the target service flow to be monitored from the monitoring configuration policy of the target service flow to be monitored. In other words, the monitoring configuration information of the target service flow to be monitored is sent by the policy control network element to the session management network element.
  • method 300 executes S312, and in S312, the policy control network element sends the monitoring configuration policy of the target service flow to be monitored to the session management network element, then in S320, the session management network element configures the target service flow according to the target to be monitored.
  • the monitoring configuration policy of the business flow determines the monitoring configuration information of the target business flow to be monitored.
  • the session management network element determines the monitoring configuration information of the target service flow to be monitored according to the monitoring configuration policy of the target service flow to be monitored. For more description about the monitoring configuration information of the target service flow to be monitored, please refer to S220 above.
  • the session management network element sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the access network device.
  • the access network device receives the monitoring configuration information of the target service flow to be monitored and the identification of the uplink service flow #1 from the session management network element.
  • the access network device After receiving the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1, the access network device can determine that the upstream service flow #1 is used to transmit network status information of the target service flow to be monitored.
  • the session management network element sends the identifier of the uplink service flow #1 and the monitoring configuration information of the target service flow to be monitored to the access network device through an N2 session management message (N2session management message, N2SM message).
  • N2SM message can specifically correspond to any N2 message between the access network device and the access and mobility management function network element, such as the downstream non-access stratum (NAS) transport message (DL NAS Transport), in This is not limited to this.
  • NAS non-access stratum
  • the N2SM message is sent by the session management network element to the access and mobility management function network element, and is sent by the access and mobility management function network element to the access network device side through the N2 message.
  • the session management network element sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the access network device, including: the session management network element sends the monitoring configuration information of the target service flow to be monitored to the access network device. Monitoring configuration information, the identification of upstream service flow #1 and the identification of the target service flow to be monitored.
  • method 300 further includes: the session management network element sending instruction information #1 to the access network device.
  • the access network device determines according to the instruction information #1 that the uplink service flow #1 is used to transmit the network status information of the target service flow to be monitored, that is, the access network device uses the instruction information #1 to transmit the network status information of the target service flow to be monitored.
  • the information is placed in upstream service flow #1 for transmission.
  • indication information #1 please refer to the description in S210.
  • the session management network element sends the identifier of the uplink service flow #1 to the user plane network element.
  • the user plane network element receives the identification of the uplink service flow #1 from the session management network element.
  • the network only monitors the network status of the target service flow to be monitored, then after the user plane network element receives the identification of the uplink service flow #1, it can determine that the uplink service flow #1 is used to transmit the target service flow to be monitored. network status information. For example, the user plane network element receives the identifier of the target service flow to be monitored and the identifier of the uplink service flow #1 from the session management network element, thereby clarifying that the upstream service flow #1 is used to transmit network status information of the target service flow to be monitored.
  • the session management network element sends the identifier of the upstream service flow #1 to the user plane network element through an N4 session modification (N4 session modification) message.
  • N4 session modification N4 session modification
  • the session management network element sends the identifier of the uplink service flow #1 to the user plane network element, including: the session management network element sends the identifier of the uplink service flow #1 and/or the target service flow to be monitored to the user plane network element. logo. Further, if the user plane network element knows that the network will monitor the network status of the target service flow to be monitored, after the user plane network element receives the identification of the uplink service flow #1 and/or the identification of the target service flow to be monitored, it can It is determined that upstream service flow #1 is used to transmit network status information of the target service flow to be monitored.
  • the method 300 further includes: the session management network element sending the indication information of the uplink service flow #1 for transmitting the network status information of the target service flow to be monitored to the user plane network element.
  • the session management network element can carry the identification information of the upstream service flow #1 and the indication information #1 in the same message and send it to the user plane network element, or the session management network element can send the identification information of the upstream service flow #1
  • the identification and indication information #1 are carried in different messages and sent to the user plane network element.
  • the user plane network element determines that the upstream service flow #1 is used to transmit the network status information of the target service flow to be monitored based on the instruction information #1, which is equivalent to the user plane network element using the instruction information #1 to determine the uplink service flow #1.
  • the network status information transmitted on 1 is determined as the network status information of the target service flow to be monitored.
  • the session management network element can also send monitoring configuration information of the target service flow to be monitored to the user plane network element.
  • the access network device obtains the network status information of the target service flow to be monitored.
  • the access network device sends the uplink data packet to the user plane network element.
  • the user plane network element receives the uplink data packet from the access network device.
  • the uplink data packet is a data packet in the uplink service flow #1 used to transmit network status information of the target service flow to be monitored, that is, the uplink data packet includes an identifier of the uplink service flow #1.
  • the user plane network element determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored.
  • method 300 also includes S380: the user plane network element sends network status information of the target service flow to be monitored.
  • S380 includes S381 and S382.
  • the application function network element sends a subscription request message to the user plane network element.
  • the user plane network element receives the subscription request message from the application function network element.
  • the subscription request message is used to request the network status information of the target service flow to be monitored, and/or to instruct the acquisition of the network status information of the target service flow to be monitored.
  • the subscription request message includes business flow description information #2 or the identification of the target business flow to be monitored, and/or the subscription request message includes an event identifier.
  • the event identifier refer to S210 above.
  • the application function network element may call the UPF service interface-subscription (Nupf_subscribe) service interface to send a subscription request message to the user plane network element.
  • UPF service interface-subscription Nupf_subscribe
  • the application function network element sends the subscription request message to the network opening function network element, and then the network opening function network element forwards the subscription request message to the user plane network element.
  • S381 is an optional step. If method 300 does not execute S313 and S314, then method 300 executes S381. Otherwise, method 300 does not need to execute S381, that is, S381 and S313 may be the same step.
  • the user plane network element sends the network status information of the target service flow to be monitored to the application function network element.
  • the application function network element receives the network status information of the target service flow to be monitored.
  • the user plane network element responds to the subscription request message, or the user plane network element sends the network status information of the target service flow to be monitored to the application function network element after determining that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored. Network status information.
  • the user plane network element can call the UPF service interface-notification (Nupf_notify) service interface to send the network status information of the target service flow to be monitored to the application function network element.
  • UPF service interface-notification Nupf_notify
  • the user plane network element can send the network status information of the target service flow to be monitored to the network opening function network element, and the network opening function network element then forwards the network status information of the target service flow to be monitored to the application function network element.
  • S380 only includes S382. That is to say, after receiving the network status information of the target service flow to be monitored, the user plane network element sends the network status information of the target service flow to be monitored to the application function network element.
  • S380 includes S383 and S385.
  • the user plane network element adds an explicit congestion notification (ECN) identifier to at least one uplink data packet according to the congestion information.
  • ECN explicit congestion notification
  • the user plane network element can Add an ECN identifier to at least one upstream data packet.
  • the user plane network element adds an ECN identifier to the IP header (for example, IP version 4 (IPv4) header or IP version 6 (IPv6) header) of at least one uplink data packet.
  • IPv4 IP version 4
  • IPv6 IP version 6
  • Figure 4 shows the IPv4 header format of at least one upstream data packet.
  • the IPv4 header of at least one uplink data packet includes the following content: version (version), Internet header length (IHL), differentiated service code point (DSCP), ECN , total length of data packet, packet identification, flags, fragment offset, time to live, protocol, header checksum ), source IP address, destination IP address and optional (options) field (if IHL>5).
  • the at least one uplink data packet is a data packet in the target uplink service flow, and the target uplink service flow and the target service flow to be monitored correspond to the same service. It can be understood that if the target service flow to be monitored is an uplink service flow, then the target upstream service flow is the target service flow to be monitored. It should also be noted that the at least one uplink data packet includes an uplink data packet sent within a unit duration. For example, the unit duration is 1 second, 1 minute, or 1 hour, etc., which is not limited here. Alternatively, the at least one uplink data packet includes a preset number of uplink data packets, for example, the preset number is 20, 50, or 100, etc., which is not limited here.
  • the user plane network element can probabilistically add an ECN identifier to at least one uplink data packet based on the congestion information. That is, the probability of the user plane network element adding an ECN identifier to at least one uplink data packet is determined based on the congestion information. For example, if the user plane network element determines that the target service flow to be monitored is not congested based on the congestion information, the user plane network element does not add an ECN identifier to each data packet in at least one uplink data packet. For another example, if the user plane network element determines that the target service flow to be monitored is congested based on the congestion information, the user plane network element can add an ECN identifier to each uplink data packet in at least one uplink data packet.
  • the user plane network element determines that the congestion level of the target service flow to be monitored is 60% based on the congestion information, the user plane network element randomly adds ECN to 60% of the uplink data packets in the data packets of the target uplink service flow. logo.
  • the user plane network element can also add an ECN identifier to at least one uplink data packet based on the transmission delay, transmission queue length, available bandwidth or packet loss rate of the target service flow to be monitored.
  • the user plane network element can Add an ECN identifier to each uplink data packet in at least one uplink data packet.
  • the user plane network element determines the number of uplink data packets to which the ECN identifier is added based on the ratio of the transmission queue length of the target service flow to be monitored and the transmission queue length threshold. For example, if the ratio of the send queue length of the target service flow to be monitored to the send queue length threshold is 50%, the user plane network element adds an ECN identifier to 50% of the uplink data packets in at least one uplink data packet.
  • the user plane network element sends at least one uplink data packet to the application server.
  • the application server receives at least one uplink data packet from the user plane network element.
  • the application server After the application server (AS) receives at least one uplink data packet, it can determine the target service to be monitored based on the ratio of the number of uplink data packets including the ECN identifier in the at least one uplink data packet to the number of at least one uplink data packet. The degree of congestion of the flow. Wherein, at least one uplink data packet includes uplink data packets received by the AS within a unit duration, or at least one uplink data packet includes a preset number of uplink data packets.
  • the application server determines the target service to be monitored. The stream is congested. For another example, if each uplink data packet received by the AS within one minute does not include an ECN identifier, the application server determines that the target service flow to be monitored is not congested. For another example, if 60% of the uplink data packets received by the AS within one minute include the ECN identifier, the application server determines that the congestion level of the target service flow to be monitored is 60%.
  • the application server will negotiate with the terminal device or the network side in advance to determine that the user plane network element will probabilistically add an ECN identifier. Feedback network status information in the form of identification.
  • the application server can also determine the transmission delay, packet loss rate, and packet loss rate of the target service flow to be monitored based on the ratio of the number of uplink data packets including the ECN identifier in the at least one uplink data packet to the number of at least one uplink data packet. Available bandwidth or send queue length.
  • the application server determines the sending queue length of the target service flow to be monitored based on the ratio of the number of uplink data packets including the ECN identifier in at least one uplink data packet to the number of at least one uplink data packet, if the application server determines that at least one uplink data packet If each uplink data packet in the data packet includes an ECN identifier, the application server determines that the sending queue length of the target service flow to be monitored exceeds the sending queue length threshold. For another example, if the application server determines that 60% of the uplink data packets in at least one uplink data packet include the ECN identifier, the application server determines that the sending queue length of the target service to be monitored is 60% of the sending queue length threshold.
  • S380 includes S384 and S385.
  • the user plane network element adds the target service flow to be monitored in the IP layer or transmission control protocol (TCP) layer or user data protocol (UDP) layer or other layers of at least one uplink data packet.
  • TCP transmission control protocol
  • UDP user data protocol
  • the user plane network element can carry the network status information of the target service flow to be monitored through the optional field in the IP header.
  • the user plane network element sends at least one uplink data packet to the application server.
  • the application server obtains the network status information of the target service flow to be monitored by parsing the IP of at least one uplink data packet into the TCP layer or UDP layer or other layers.
  • the session management network element determines the identity of the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored based on the instruction information for network status monitoring of the target service flow to be monitored, and sends the uplink
  • the identification of service flow #1 is sent to the access network equipment and the user plane network element respectively, so that the access network equipment can determine according to the identification of uplink service flow #1 to send the target to-be-monitored service to the user plane network element through uplink service flow #1.
  • the network status information of the flow, and the user plane network element can determine based on the identification of the uplink service flow #1 that the uplink data packet received through the uplink service flow #1 includes the network status information of the target service flow to be monitored.
  • Figure 5 shows a schematic flow chart of the communication method provided by the embodiment of the present application. Specifically, compared with the method in Figure 3, Figure 5 shows the implementation of method 200 in which the policy control network element determines the identity of the upstream service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the method flow of the example, each step included in the method 500 is described in detail below.
  • the policy control network element receives instruction information for instructing to monitor the network status of the target service flow to be monitored.
  • S510 includes S511.
  • the application function network element sends instruction information #2 to the policy control network element.
  • the policy control network element receives indication information #2 from the application function network element.
  • S510 includes S512 to S514.
  • the application function network element sends instruction information #4 to the user plane network element.
  • the user plane network element receives indication information #4 from the application function network element.
  • the user plane network element sends instruction information #5 to the session management network element.
  • the session management network element receives indication information #5 from the user plane network element.
  • the session management network element sends instruction information #6 to the policy control network element.
  • the policy control network element receives indication information #6 from the session management network element.
  • the instruction information #6 is used to instruct network status monitoring of the target service flow to be monitored.
  • the indication information #6 may also be used to indicate the identification of the uplink service flow #1 that is determined to be used to transmit the target service flow to be monitored.
  • the form of the instruction information #6 may refer to the form of the instruction information #2 described in S311 above.
  • the session management network element reports to the policy control network element Send instruction information #6 and service flow description information #2.
  • S520 The policy control network element determines the identifier of upstream service flow #1.
  • the policy control network element determines the identity of the upstream service flow #1 based on the instruction information for network status monitoring of the target service flow to be monitored (ie, the above instruction information #2 or instruction information #6). When receiving the instruction information #2 or the instruction information #6, the policy control network element determines the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored in response to the instruction information #2 or the instruction information #6. .
  • the policy control network element responds to the indication information #2 or the indication information #6 and determines the uplink service flow #1 according to the service flow description information #2. That is to say, the policy control network element first determines the target service to be monitored based on the service flow description information #2, and then determines the uplink service flow #1 for the target service flow to be monitored.
  • the policy control network element may determine the uplink service flow of the same service corresponding to the target service to be monitored as the network status information used to transmit the target service flow to be monitored.
  • Upstream traffic flow #1 For a description of the uplink service flow of the same service corresponding to the target service flow to be monitored, please refer to S320 above.
  • the policy control network element may also determine the uplink service flow corresponding to different services from the target service flow to be monitored as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the policy control network element may determine the target service flow to be monitored as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the policy control network element may also determine the uplink service flow corresponding to different services from the target service flow to be monitored as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the policy control network element may determine the uplink service flow not used to transmit any network status information as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the policy control network element may determine the uplink service flow with a higher transmission frequency as the uplink service flow used to transmit the network status information of the target service flow to be monitored.# 1.
  • the access network device can quickly send the network status information of the target service flow to be monitored to the user plane network element.
  • the policy control network element may determine the uplink service flow corresponding to the same QoS flow as the target service flow to be monitored as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the policy control network element determines the identity of the upstream service flow #1 based on the upstream service flow #1.
  • the policy control network element sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the session management network element.
  • the session management network element receives the monitoring configuration information of the target service flow to be monitored and the identification of the uplink service flow #1 from the policy control network element.
  • the policy control network element sends the monitoring configuration information of the target service flow to be monitored to the session management network element in the form of a monitoring configuration policy of the target service flow to be monitored. That is to say, the policy control network element sends the monitoring configuration policy of the target service flow to be monitored to the session management network element, and the monitoring configuration policy of the target service flow to be monitored includes parameters used to form the monitoring configuration information of the target service flow to be monitored. Among them, the policy control network element can generate the monitoring configuration policy of the target service flow to be monitored based on the instruction information #2 or the instruction information #6. For more descriptions of the monitoring configuration information and monitoring configuration strategy of the target service flow to be monitored, please refer to the above. Text S220.
  • the session management network element sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the access network device.
  • the access network device receives the monitoring configuration information of the target service flow to be monitored and the identification of the uplink service flow #1 from the session management network element.
  • the session management network element sends the identifier of the uplink service flow #1 to the user plane network element.
  • the user plane network element receives the identification of the uplink service flow #1 from the session management network element.
  • the access network device obtains the network status information of the target service flow to be monitored.
  • S570 The access network device sends the uplink data packet to the user plane network element.
  • the user plane network element receives the uplink data packet from the access network device.
  • the uplink data packet is a data packet in the uplink service flow #1 used to transmit network status information of the target service flow to be monitored, that is, the uplink data packet includes an identifier of the uplink service flow #1.
  • the user plane network element determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored.
  • method 500 also includes S590: the user plane network element sends network status information of the target service flow to be monitored.
  • S590 please refer to S380 above.
  • S380 For the sake of brevity, details will not be described here.
  • the policy control network element determines the identity of the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored based on the instruction information for network status monitoring of the target service flow to be monitored, and sends the uplink
  • the identifier of service flow #1 is sent to the session management network element, so that the session management network element can send the identifier of uplink service flow #1 to the access network device and the user plane network element, so that the access network device can according to the uplink service flow #
  • the identification of 1 determines that the network status information of the target service to be monitored is sent to the user plane network element through the uplink service flow #1, and the user plane network element can determine the uplink data received through the uplink service flow #1 according to the identification of the uplink service flow #1
  • the package includes network status information of the target service flow to be monitored.
  • Figure 6 shows a schematic flow chart of the communication method provided by the embodiment of the present application. Specifically, with Figure 3 and Figure 5 Compared with the method, Figure 6 shows the method flow of the embodiment in which the user plane network element determines the identity of the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored mentioned in the method 200. The details are as follows. Various steps included in method 600 are described.
  • the application function network element sends instruction information #4 to the user plane network element.
  • the user plane network element receives indication information #4 from the application function network element.
  • S620 The user plane network element determines the identity of uplink service flow #1.
  • the user plane network element determines the identity of the uplink service flow #1 according to the instruction information #4. That is to say, when the user plane network element receives the instruction information #4, it determines the transmission target to be monitored in response to the instruction information #4.
  • Upstream service flow #1 of the network status information of the service flow and determine the identity of upstream service flow #1.
  • the user plane network element responds to the indication information #4 and determines the uplink service flow #1 based on the service flow description information #2. That is to say, the user plane network element first determines the target service flow to be monitored based on the service flow description information #2, and then determines the uplink service flow #1 for the target service flow to be monitored.
  • the user plane network element may determine the uplink service flow of the same service corresponding to the target service flow to be monitored as the network status information used to transmit the target service flow to be monitored.
  • Upstream traffic flow #1 For a description of the uplink service flow of the same service corresponding to the target service flow to be monitored, please refer to S320 above.
  • the user plane network element may also determine the uplink service flow corresponding to different services from the target service flow to be monitored as the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored.
  • the user plane network element may determine the target service flow to be monitored as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored.
  • the user plane network element may also determine the uplink service flow corresponding to different services from the target service flow to be monitored as the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored.
  • the user plane network element may determine the uplink service flow that is not used to transmit any network status information as the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored.
  • the user plane network element can determine the uplink service flow with a higher transmission frequency as the uplink service flow used to transmit the network status information of the target service flow to be monitored.# 1.
  • the access network device can quickly send the network status information of the target service flow to be monitored to the user plane network element.
  • the user plane network element may determine the uplink service flow corresponding to the same QoS flow as the target service flow to be monitored as the uplink service flow #1 used to transmit network status information of the target service flow to be monitored. It should be noted that the user plane network element can determine the first QoS flow corresponding to the target service flow to be monitored based on the packet detection rule (PDR) previously received from the session management network element.
  • PDR packet detection rule
  • the user plane network element determines the identity of the uplink service flow #1 based on the determined uplink service flow #1.
  • the user plane network element sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the access network device.
  • the access network device receives the monitoring configuration information of the target service flow to be monitored and the identification of the uplink service flow #1 from the user plane network element.
  • the user plane network element carries the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 in the GTP-U layer of the downlink data packet, and sends them to the access network device.
  • the downlink data packet is a data packet in the target service flow to be monitored.
  • the user plane network element sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the session management network element, and the session management network element then sends the monitoring configuration information of the target service flow to be monitored and the identifier of the upstream service flow #1.
  • the identifier of upstream service flow #1 is forwarded to the access network device.
  • the user plane network element sends the monitoring configuration information of the target service flow to be monitored and the identifier of the uplink service flow #1 to the access network device, including: the user plane network element sends the monitoring configuration information of the target service flow to be monitored to the access network device. Monitoring configuration information, the identification of upstream service flow #1 and the identification of the target service flow to be monitored.
  • the method 600 also includes: the user plane network element sends the instruction information #1 to the access network device.
  • the access network device determines according to the indication information #1 that the uplink service flow #1 is used to transmit the network status information of the target service flow to be monitored.
  • indication information #1 please refer to S210 above.
  • S640 The access network device obtains the network status information of the target service flow to be monitored.
  • the access network device sends the uplink data packet to the user plane network element.
  • the user plane network element receives the uplink data packet from the access network device.
  • the uplink data packet is a data packet in the uplink service flow #1 used to transmit network status information of the target service flow to be monitored, that is, the uplink data packet includes an identifier of the uplink service flow #1.
  • the user plane network element determines that the network status information included in the uplink data packet is the network status information of the target service flow to be monitored.
  • method 600 also includes S670: the user plane network element sends network status information of the target service flow to be monitored.
  • S670 please refer to S380 above.
  • S380 For the sake of brevity, it will not be described in detail here.
  • the user plane network element determines the identifier of the uplink service flow #1 used to transmit the network status information of the target service flow to be monitored based on the instruction information #4, and sends the identifier of the uplink service flow #1 to the receiving party.
  • the network access device enables the access network device to determine, according to the identifier of the uplink service flow #1, to send the network status information of the target service flow to be monitored to the user plane network element through the uplink service flow #1.
  • FIG. 7 is a schematic block diagram of a communication device 1000 provided by an embodiment of the present application.
  • the communication device 1000 may include: a transceiver unit 1010 and a processing unit 1020 .
  • the communication device 1000 may be the access network device in the above method embodiment, or may be a chip used to implement the functions of the access network device in the above method embodiment.
  • the communication device 1000 may correspond to the access network equipment in the method 200, the method 300, the method 500 or the method 600 in the embodiment of the present application, and the communication device 1000 may include a method for executing the method 200 in Figure 2, Figure 3
  • each unit in the communication device 1000 and the above-mentioned other operations and/or functions are respectively intended to implement the method 200 in Figure 2, the method 300 in Figure 3, the method 500 in Figure 5, or the method 600 in Figure 6. process. It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiments, and will not be described again for the sake of brevity.
  • the communication device 1000 may be the user plane network element in the above method embodiment, or may be a chip used to implement the functions of the user plane network element in the above method embodiment.
  • the communication device 1000 may correspond to the method 200, the method 300, the method 500 or the method of the embodiment of the present application.
  • the communication device 1000 may include a user plane network element for executing the method 200 in FIG. 2, the method 300 in FIG. 3, the method 500 in FIG. 5, or the method 600 in FIG. 6.
  • the unit of execution of the method Moreover, each unit in the communication device 1000 and the above-mentioned other operations and/or functions are respectively intended to implement the method 200 in Figure 2, the method 300 in Figure 3, the method 500 in Figure 5, or the method 600 in Figure 6. process. It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiments, and will not be described again for the sake of brevity.
  • the communication device 1000 may be the session management network element in the above method embodiment, or may be a chip used to implement the functions of the session management network element in the above method embodiment.
  • the communication device 1000 may correspond to the session management network element in the method 200, the method 300, the method 500 or the method 600 in the embodiment of the present application, and the communication device 1000 may include a method for executing the method 200 in Figure 2, Figure 3 A unit of the method executed by the session management network element in method 300 in FIG. 5 , method 500 in FIG. 5 , or method 600 in FIG. 6 .
  • each unit in the communication device 1000 and the above-mentioned other operations and/or functions are respectively intended to implement the method 200 in Figure 2, the method 300 in Figure 3, the method 500 in Figure 5, or the method 600 in Figure 6. process. It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiments, and will not be described again for the sake of brevity.
  • the communication device 1000 may be the policy control network element in the above method embodiment, or may be a chip used to implement the functions of the policy control network element in the above method embodiment.
  • the communication device 1000 may correspond to the policy control network element in the method 200, the method 300, the method 500 or the method 600 in the embodiment of the present application, and the communication device 1000 may include a method for executing the method 200 in Figure 2, Figure 3
  • each unit in the communication device 1000 and the above-mentioned other operations and/or functions are respectively intended to implement the method 200 in Figure 2, the method 300 in Figure 3, the method 500 in Figure 5, or the method 600 in Figure 6. process. It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiments, and will not be described again for the sake of brevity.
  • transceiver unit 1010 in the communication device 1000 may correspond to the transceiver 2020 in the communication device 2000 shown in FIG. 8
  • processing unit 1020 in the communication device 1000 may correspond to the communication device shown in FIG. 8 Processors in 2000 and 2010.
  • the chip when the communication device 1000 is a chip, the chip includes a transceiver unit.
  • the chip may also include a processing unit.
  • the transceiver unit may be an input-output circuit or a communication interface; the processing unit may be a processor or microprocessor or integrated circuit integrated on the chip.
  • the transceiver unit 1010 is used to implement the signal transceiver operation of the communication device 1000
  • the processing unit 1020 is used to implement the signal processing operation of the communication device 1000 .
  • the communication device further includes a storage unit 1030, which is used to store instructions.
  • Figure 8 is a schematic block diagram of a communication device 2000 provided by an embodiment of the present application.
  • the communication device 2000 includes: at least one processor 2010 and a transceiver 2020 .
  • the processor 2010 is coupled to the memory and is used to execute instructions stored in the memory to control the transceiver 2020 to send signals and/or receive signals.
  • the communication device 2000 further includes a memory 2030 for storing instructions.
  • processor 2010 and the memory 2030 can be combined into one processing device, and the processor 2010 is used to execute the program code stored in the memory 2030 to implement the above functions.
  • the memory 2030 may also Integrated in the processor 2010, or independent of the processor 2010.
  • the transceiver 2020 may include a receiver and a transmitter.
  • the transceiver 2020 may further include an antenna, and the number of antennas may be one or more.
  • the transceiver 2020 can be an antenna interface or an interface circuit.
  • the chip When the communication device 2000 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip.
  • Figure 9 is a schematic diagram of a chip system according to an embodiment of the present application.
  • the chip system here may also be a system composed of circuits.
  • the chip system 3000 shown in Figure 9 includes: a logic circuit 3010 and an input/output interface (input/output interface) 3020.
  • the logic circuit is used to couple with the input interface and transmit data through the input/output interface to execute the figure. 2.
  • An embodiment of the present application also provides a processing device, including a processor and an interface.
  • the processor may be used to execute the method in the above method embodiment.
  • the above processing device may be a chip.
  • the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC), or It can be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller unit , MCU), it can also be a programmable logic device (PLD) or other integrated chip.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processing unit
  • NP network processor
  • DSP digital signal processing circuit
  • MCU microcontroller unit
  • PLD programmable logic device
  • each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.
  • the software module can be located in a random register, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, register, or other mature storage media in this field.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, the details will not be described here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • non-volatile storage can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • the present application also provides a computer program product.
  • the computer program product includes: computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to execute the figure. 2.
  • the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium stores program code.
  • the program code When the program code is run on a computer, it causes the computer to execute FIG. 2 and FIG. 3. The method of any one of the embodiments shown in Figures 5 and 6.
  • this application also provides a system, which includes the aforementioned access network equipment and user plane network elements.
  • the system also includes the aforementioned session management network element.
  • the system also includes the aforementioned policy control network element.
  • the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented using software, they may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the usable media may be magnetic media (e.g., floppy disks, hard disks, tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, which may be in electrical, mechanical or other forms.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供了一种通信方法及通信装置。根据本申请的方法，接入网设备和用户面网元都可以获取到用于传输目标待监测业务流的网络状态信息的上行业务流的标识，进而接入网设备可以通过该上行业务流中的上行数据包向用户面网元发送目标待监测业务流的网络状态信息，以及用户面网元可以根据上行数据包包括的上行业务流的标识确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息，从而实现了接入网设备向用户面网元发送业务流粒度的网络状态信息。

Description

通信方法及通信装置
本申请要求于2022年03月15日提交中国国家知识产权局、申请号为202210252155.9、申请名称为“通信方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种通信方法及通信装置。
背景技术
如果第三方应用能实时感知网络状态，那么第三方应用可以根据网络状态进行相应调整，从而保证用户的业务体验，以及最大化网络利用效率。因此如何将更多的网络状态信息，诸如可用带宽、拥塞状况等快速开放给第三方应用是一个关键问题。
一种实现方式中，网络状态信息可以通过控制面或用户面的形式开放给应用层。例如，网络状态信息可以通过用户面功能网元(user plane function，UPF)服务化接口或网络开放功能(network exposure function，NEF)开放给第三方应用。又例如，UPF可以将网络状态信息添加到数据包发送给应用服务器侧。然而在上述方式中，由于UPF无法对空口侧无线接入网(radio access network，RAN)与终端设备之间的网络状态进行监测，如果UPF需要向第三方应用开放空口侧RAN与终端设备之间的网络状态信息，则UPF只能从RAN接收空口侧的网络状态信息。在此情况下，RAN如何将空口侧的网络状态信息发送给UPF将成为一个亟待解决的问题。
发明内容
本申请实施例提供一种通信方法，以期实现接入网设备将进行网络状态监测得到的网络状态信息发送给用户面网元。
第一方面，提供了一种通信方法，该方法包括：接入网设备接收目标待监测业务流的监测配置信息和上行业务流的标识，该监测配置信息用于监测该目标待监测业务流的网络状态，该上行业务流用于传输该目标待监测业务流的网络状态信息；该接入网设备根据该目标待监测业务流的监测配置信息进行网络状态监测以得到该目标待监测业务流的网络状态信息；该接入网设备向用户面网元发送上行数据包，该上行数据包包括该目标待监测业务流的网络状态信息和该上行业务流的标识。
其中，接入网设备接收目标待监测业务流的监测配置信息和上行业务流标识，也可理解为接入网设备主动从其他网元或实体获取目标待监测业务流的监测配置信息和上行业务流的标识。
基于上述技术方案，接入网设备接收到用于传输目标待监测业务流的网络状态信息的上行业务流的标识之后，可以通过上行业务流中的上行数据包向用户面网元发送目标待监 测业务流的网络状态信息，从而实现接入网设备将进行网络状态监测得到的网络状态信息发送给用户面网元。进而，用户面网元可以将接收到的网络状态信息开放给第三方应用，从而第三方应用可以根据网络状态信息调整目标待监测业务流的传输参数，保障用户的业务体验，例如，第三方应用可以根据网络状态信息降低目标待监测业务流的码率。
此外，基于上述技术方案，接入网设备向用户面网元发送的是业务流粒度的网络状态信息，进而用户面网元可以将业务流粒度的网络状态信息开放给第三方应用服务器，从而第三方应用服务器可以针对业务流粒度的网络状态信息对业务流的传输参数进行调整，以满足用户对不同业务流的体验和需求。
示例性地，该目标待监测业务流是第一服务质量(quality of service，QoS)流，该上行业务流为第二QoS流中的上行业务流。
基于上述技术方案，当该目标待监测业务流是第一QoS流时，即该第一QoS流内不存在其他的业务流，也可以实现接入网设备将目标待监测业务流的网络状态信息发送给用户面网元。例如，若该目标待监测业务流是下行业务流，即该第一QoS流内不存在上行数据包，如果接入网设备没有接收到用于传输目标待监测业务流的网络状态信息的上行业务流的标识，则接入网设备不知道该通过哪个业务流向用户面网元传输目标待监测业务流的网络状态信息，接入网设备无法向用户面网元传输目标待监测业务流的网络状态信息。
又示例性地，该目标待监测业务流是第一QoS流中的下行业务流，该上行业务流是第二QoS流中的上行业务流。第一QoS流与第二QoS流是同一个QoS流，或者，第一QoS流与第二QoS流是不同的QoS流。
基于上述技术方案，当该目标待监测业务流是第一QoS流中的下行业务流时，可以实现接入网设备向用户面网元发送业务流粒度的网络状态信息。例如，若网络既对目标待监测业务流进行网络状态监测，也对第一QoS流中的上行业务流进行网络状态监测，如果接入网设备没有接收到用于传输目标待监测业务流的网络状态信息的上行业务流的标识，则接入网设备只能通过第一QoS流中的上行业务流向用户面网元传输目标待监测业务流的网络状态信息和第一QoS流中的上行业务流的网络状态信息，使得用户面网元难以区分网络状态信息与业务流之间的关系。
再示例性地，该目标待监测业务流是第一QoS流中的上行业务流，该上行业务流是第二QoS流中的上行业务流。第一QoS流与第二QoS流是同一个QoS流，或者，第一QoS流与第二QoS流是不同的QoS流。
基于上述技术方案，当该目标待监测业务流是第一QoS流中的上行业务流时，可以实现接入网设备向用户面网元发送业务流粒度的网络状态信息。例如，若网络既对目标待监测业务流进行网络状态监测，也对第一QoS流中的上行业务流进行网络状态监测，如果接入网设备没有接收到用于传输目标待监测业务流的网络状态信息的上行业务流的标识，则接入网设备只能通过第一QoS流中的上行业务流向用户面网元传输目标待监测业务流的网络状态信息和第一QoS流中的上行业务流的网络状态信息，使得用户面网元难以区分网络状态信息与业务流之间的关系。
上述示例中，用于传输目标待监测业务流的网络状态信息的上行业务流也可以是第二QoS流，即第二QoS流中没有其他下行业务流。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：接入网设备接收用于 传输该目标待监测业务流的网络状态的该上行业务流的指示信息。
基于上述技术方案，接入网设备在接收到上行业务流的标识和该指示信息的情况下，可以根据该指示信息确定该上行业务流用于传输目标待监测业务流的网络状态信息，从而接入网设备在获取到目标待监测业务流的网络状态信息之后，可以通过该上行业务流向用户面网元发送目标待监测业务流的网络状态信息，从而实现目标待监测业务流的网络状态信息的快速实时传输。
结合第一方面，在第一方面的某些实现方式中，该接入网设备接收目标待监测业务流的监测配置信息和上行业务流的标识，包括：该接入网设备接收该目标待监测业务流的监测配置信息、该目标待监测业务流的标识和上行业务流的标识。
其中，目标待监测业务流的标识和上行业务流的标识具有绑定关系，从而指示上行业务流用于传输目标待监测业务流的网络状态信息。
结合第一方面，在第一方面的某些实现方式中，该上行数据包还包括该目标待监测业务流的标识。
基于上述技术方案，若上行业务流用于传输多个待监测业务流中各待监测业务流的网络状态信息，则接入网设备向用户面网元发送的上行数据包不只包括上行业务流的标识，还包括目标待监测业务流的标识。相应地，用户面网元可以根据上行业务流的标识和目标待监测业务流的标识，确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息，从而实现目标待监测业务流网络状态信息的快速实时传输，以及实现接入网设备向用户面网元发送业务流粒度的网络状态信息。
第二方面，提供了一种通信方法，该方法包括：用户面网元获取上行业务流的标识，该上行业务流用于传输目标待监测业务流的网络状态信息；该用户面网元接收上行数据包，该上行数据包包括该上行业务流的标识和网络状态信息；该用户面网元根据该上行业务流的标识确定该上行数据包包括的网络状态信息是该目标待监测业务流的网络状态信息。
一种可能的实现方式中，用户面网元获取上行业务流的标识，可以理解为接收上行数据包中的上行业务流标识。
基于上述技术方案，用户面网元获取到用于传输目标待监测业务流的上行业务流的标识之后，接入网设备可以通过上行业务流中的上行数据包向用户面网元发送目标待监测业务流的网络状态信息。相应地，用户面网元可以根据上行业务流的标识确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息，从而实现了接入网设备向用户面网元快速实时传输业务流粒度网络状态信息。
此外，在接入网设备向用户面网元发送业务流粒度的网络状态信息的情况下，若用户面网元将业务流粒度的网络状态信息开放给第三方应用服务器，则第三方应用服务器可以针对业务流粒度的网络状态信息对业务流的传输参数进行调整，从而满足用户对不同业务流的体验和需求。
示例性地，该目标待监测业务流是第一QoS流，该上行业务流为第二QoS流中的上行业务流。
基于上述技术方案，当该目标待监测业务流是第一QoS流时，即该第一QoS流内不存在其他的业务流，也可以实现接入网设备将目标待监测业务流的网络状态信息发送给用 户面网元。例如，若该目标待监测业务流是下行业务流，即该第一QoS流内不存在上行数据包，如果接入网设备没有接收到用于传输目标待监测业务流的网络状态信息的上行业务流的标识，则接入网设备不知道该通过哪个业务流向用户面网元传输目标待监测业务流的网络状态信息，接入网设备无法向用户面网元传输目标待监测业务流的网络状态信息。
又示例性地，该目标待监测业务流是第一QoS流中的上行业务流，该上行业务流是第二QoS流中的上行业务流。第一QoS流与第二QoS流是同一个QoS流，或者，第一QoS流与第二QoS流是不同的QoS流。
基于上述技术方案，当该目标待监测业务流是第一QoS流中的下行业务流时，可以实现接入网设备向用户面网元发送业务流粒度的网络状态信息。例如，若网络既对目标待监测业务流进行网络状态监测，也对第一QoS流中的上行业务流进行网络状态监测，如果接入网设备没有接收到用于传输目标待监测业务流的网络状态信息的上行业务流的标识，则接入网设备只能通过第一QoS流中的上行业务流向用户面网元传输目标待监测业务流的网络状态信息和第一QoS流中的上行业务流的网络状态信息，使得用户面网元难以区分网络状态信息与业务流之间的关系。
再示例性地，该目标待监测业务流是第一QoS流中的上行业务流，该上行业务流是第二QoS流中的上行业务流。第一QoS流与第二QoS流是同一个QoS流，或者，第一QoS流与第二QoS流是不同的QoS流。
基于上述技术方案，当该目标待监测业务流是第一QoS流中的上行业务流时，可以实现接入网设备向用户面网元发送业务流粒度的网络状态信息。例如，若网络既对目标待监测业务流进行网络状态监测，也对第一QoS流中的上行业务流进行网络状态监测，如果接入网设备没有接收到用于传输目标待监测业务流的网络状态信息的上行业务流的标识，则接入网设备只能通过第一QoS流中的上行业务流向用户面网元传输目标待监测业务流的网络状态信息和第一QoS流中的上行业务流的网络状态信息，使得用户面网元难以区分网络状态信息与业务流之间的关系。
上述示例中，用于传输目标待监测业务流的网络状态信息的上行业务流也可以是第二QoS流，即该第二QoS流中没有其他下行业务流。
结合第二方面，在第二方面的某些实现方式中，该上行业务流用于传输多个待监测业务流中各待监测业务流的网络状态信息，该多个待监测业务流包括该目标待监测业务流，该上行数据包还包括该目标待监测业务流的标识，该用户面网元根据该上行业务流的标识确定该上行数据包包括的网络状态信息是该目标待监测业务流的网络状态信息，包括：该用户面网元根据该目标待监测业务流的标识和该上行业务流的标识，确定该上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。
基于上述技术方案，若上行业务流用于传输多个待监测业务流中各待监测业务流的网络状态信息，则用户面网元可以根据上行业务流的标识和目标待监测业务流的标识，确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息，从而实现目标待监测业务流网络状态信息的快速实时传输，以及实现接入网设备向用户面网元发送业务流粒度的网络状态信息。
结合第二方面，在第二方面的某些实现方式中，该用户面网元获取上行业务流的标识，包括：该用户面网元从会话管理网元接收该上行业务流的标识。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该用户面网元从该会话管理网元接收用于传输该目标待监测业务流的网络状态信息的该上行业务流的指示信息。
基于上述技术方案，用户面网元在接收到上行业务流的标识和该指示信息的情况下，可以根据该指示信息确定该上行业务流用于传输目标待监测业务流的网络状态信息，从而用户面网元可以通过该上行业务流从接入网设备接收该目标待监测业务流的网络状态信息，实现目标待监测业务流网络状态信息的快速实时传输。
结合第二方面，在第二方面的某些实现方式中，该用户面网元从会话管理网元接收该上行业务流的标识，包括：该用户面网元从该会话管理网元接收该上行业务流的标识和该目标待监测业务流的标识。
其中，目标待监测业务流的标识与上行业务流的标识具有绑定关系，以指示该上行业务流用于传输目标待监测业务流的网络状态信息。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该用户面网元从应用功能网元接收获取该目标待监测业务流的网络状态信息的指示信息；该用户面网元向该会话管理网元发送对该目标待监测业务流进行网络状态监测的指示信息。
其中，用户面网元根据获取目标待监测业务流的网络状态信息的指示信息明确需要对该目标待监测业务流进行网络状态监测。
基于上述技术方案，用户面网元向会话管理网元发送对目标待监测业务流的网络状态进行监测的指示信息，从而会话管理网元可以根据该指示信息为目标待监测业务流确定用于传输目标待监测业务流的网络状态信息的上行业务流。
结合第二方面，在第二方面的某些实现方式中，该用户面网元获取上行业务流的标识，包括：该用户面网元从应用功能网元接收获取该目标待监测业务流的网络状态信息的指示信息；该用户面网元根据该获取该目标待监测业务流的网络状态信息的指示信息确定该上行业务流的标识；该方法还包括：该用户面网元向该接入网设备发送该目标待监测业务流的监测配置信息和该上行业务流的标识，该监测配置信息用于监测该目标待监测业务流的网络状态。
基于上述技术方案，用户面网元根据获取目标待监测业务流的网络状态信息的指示信息确定上行业务流的标识，并将上行业务流的标识发送给接入网设备，使得接入网设备可以根据上行业务流的标识确定通过上行业务流向用户面网元发送目标待监测业务流的网络状态信息，从而实现目标待监测业务流的网络状态信息的快速实时传输。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该用户面网元向该接入网设备发送用于传输该目标待监测业务流的网络状态信息的该上行业务流的指示信息。
基于上述技术方案，接入网设备在接收到上行业务流的标识和该指示信息的情况下，可以根据上述指示信息确定上行业务流用于传输目标待监测业务流的网络状态信息。
结合第二方面，在第二方面的某些实现方式中，该用户面网元获取上行业务流的标识，包括：该用户面网元从接入网设备接收该上行业务流的标识。
其中，用户面网元接收该上行业务流的标识的一种可能是接收上行业务流中的数据包，该数据包中包含上行业务流的标识。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该用户面网元发送该 目标待监测业务流的网络状态信息。
基于上述技术方案，用户面网元可以将目标待监测业务流的网络状态信息发送给第三方应用服务器，从而使得第三方应用服务器可以根据目标待监测业务流的网络状态信息调整目标待监测业务流的传输参数，从而避免网络拥塞与变化对于用户业务体验的影响。
示例性地，该目标待监测业务流的网络状态信息包括该目标待监测业务流的拥塞状况，该用户面网元发送该目标待监测业务流的网络状态信息，包括：该用户面网元发送目标上行业务流中的至少一个上行数据包，该至少一个上行数据包中携带显示拥塞通知(explicit congestion notification，ECN)标识的数据包的数量与该至少一个上行数据包的数量的比值用于确定该目标待监测业务流的拥塞状况，该目标上行业务流与该目标待监测业务流对应相同的业务。
第三方面，提供一种通信方法，该方法包括：接收对目标待监测业务流进行网络状态监测的指示信息；根据该对目标待监测业务流进行网络状态监测的指示信息确定上行业务流的标识，该上行业务流用于传输该目标待监测业务流的网络状态信息；发送该目标待监测业务流的监测配置信息和该上行业务流的标识。
基于上述技术方案，根据上述指示信息确定上行业务流的标识，并发送目标待监测业务流的监测配置信息和上行业务流的标识，有利于实现将目标待监测业务流的监测配置信息和上行业务流的标识发送给接入网设备与用户面网元，从而接入网设备可以根据监测配置信息和上行业务流的标识向用户面网元发送目标待监测业务流的网络状态信息，以及用户面网元可以通过上行业务流接收目标待监测业务流的网络状态信息，从而实现接入网设备向用户面网元快速实时传输业务流粒度网络状态信息。
一种实现方式中，发送该目标待监测业务流的监测配置信息和该上行业务流的标识，包括：向会话管理网元发送该目标待监测业务流的监测配置信息和该上行业务流的标识。
另一种实现方式中，发送该目标待监测业务流的监测配置信息和该上行业务流的标识，包括：向接入网设备与用户面网元发送该目标待监测业务流的监测配置信息和该上行业务流的标识。
其中，该上行业务流的标识可以与该目标待监测业务流的监测配置信息一起并列发往接入网设备与用户面网元，也可以是该上行业务流的标识包含在该目标待监测业务流的监测配置信息中发送给接入网设备与用户面网元，在此不做限定。
示例性地，该目标待监测业务流是第一QoS流，该上行业务流为第二QoS流中的上行业务流。
又示例性地，该目标待监测业务流是第一QoS流中的上行业务流，该上行业务流是第二QoS流中的上行业务流。第一QoS流与第二QoS流是同一个QoS流，或者，第一QoS流与第二QoS流是不同的QoS流。
再示例性地，该目标待监测业务流是第一QoS流中的上行业务流，该上行业务流是第二QoS流中的上行业务流。第一QoS流与第二QoS流是同一个QoS流，或者，第一QoS流与第二QoS流是不同的QoS流。
上述示例中，用于传输目标待监测业务流的网络状态信息的上行业务流也可以是第二QoS流，即第二QoS流中没有其他下行业务流。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：发送用于传输该目标 待监测业务流的网络状态信息的该上行业务流的指示信息。
基于上述技术方案，若将上述指示信息发送给接入网设备和用户面网元，则接入网设备和用户面网元可以在接收到上行业务流的标识和该指示信息的情况下，根据上述指示信息确定上行业务流用于传输目标待监测业务流的网络状态信息。
结合第三方面，在第三方面的某些实现方式中，发送该目标待监测业务流的监测配置信息和上行业务流的标识，包括：发送该目标待监测业务流的监测配置信息、上行业务流的标识和该目标待监测业务流的标识。
其中，目标待监测业务流的标识与上行业务流的标识具有绑定关系，以指示该上行业务流用于传输目标待监测业务流的网络状态信息。
第四方面，提供了一种通信方法，该方法包括：接入网设备接收目标待监测业务流的监测配置信息，该监测配置信息用于监测该目标待监测业务流的网络状态；该接入网设备根据该监测配置信息确定上行业务流的标识，该上行业务流用于传输该目标待监测业务流的网络状态信息；该接入网设备向用户面网元发送该上行业务流的标识；该接入网设备根据该目标待监测业务流的监测配置信息进行网络状态监测以得到该目标待监测业务流的网络状态信息；该接入网设备向该用户面网元发送上行数据包，该上行数据包包括该目标待监测业务流的网络状态信息和该上行业务流的标识。
基于上述技术方案，接入网设备确定上行业务流的标识，并将上行业务流的标识发送给用户面网元，从而接入网设备可以通过上行业务流中的上行数据包向用户面网元发送目标待监测业务流的网络状态信息。相应地，用户面网元可以根据上行业务流的标识确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息，从而实现了接入网设备向用户面网元快速实时传输业务流粒度网络状态信息。
结合第四方面，在第四方面的某些实现方式中，该上行数据包还包括该目标待监测业务流的标识。
基于上述技术方案，若上行业务流用于传输多个待监测业务流中各待监测业务流的网络状态信息，则接入网设备向用户面网元发送的上行数据包不只包括上行业务流的标识，还包括目标待监测业务流的标识。相应地，用户面网元可以根据上行业务流的标识和目标待监测业务流的标识，确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息，从而实现目标待监测业务流网络状态信息的快速实时传输。
第五方面，提供了一种通信方法，该方法包括：接入网设备接收目标待监测业务流的监测配置信息，该监测配置信息用于监测该目标待监测业务流的网络状态；该接入网设备根据该监测配置信息确定上行业务流的标识，该上行业务流用于传输该目标待监测业务流的网络状态信息；该接入网设备根据该目标待监测业务流的监测配置信息进行网络状态监测以得到该目标待监测业务流的网络状态信息；该接入网设备向该用户面网元发送上行数据包，该上行数据包包括该目标待监测业务流的网络状态信息、该上行业务流的标识和目标待监测业务流的标识。
基于上述技术方案，接入网设备确定上行业务流的标识，从而接入网设备可以通过上行业务流中的上行数据包向用户面网元发送目标待监测业务流的网络状态信息。相应地，用户面网元可以根据上行数据包包括的目标待监测业务流的标识确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息，从而实现了接入网设备向用户面网 元快速实时传输业务流粒度网络状态信息。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：接入网设备向用户面网元发送该上行业务流的标识。
第六方面，提供了一种通信方法，该方法包括：用户面网元接收上行数据包，该上行数据包包括该上行业务流的标识、目标待监测业务流的标识和网络状态信息；该用户面网元根据该目标待监测业务流的标识确定该上行数据包包括的网络状态信息是该目标待监测业务流的网络状态信息。
基于上述技术方案，用户面网元可以根据目标待监测业务流的标识确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息，从而实现了接入网设备向用户面网元快速实时传输业务流粒度网络状态信息。
第七方面，提供了一种通信装置，该通信装置包括收发单元和处理单元，该收发单元用于接收目标待监测业务流的监测配置信息和上行业务流的标识，该监测配置信息用于监测该目标待监测业务流的网络状态，该上行业务流用于传输该目标待监测业务流的网络状态信息；该处理单元用于根据该目标待监测业务流的监测配置信息进行网络状态监测以得到该目标待监测业务流的网络状态信息；该收发单元还用于向用户面网元发送上行数据包，该上行数据包包括目标待监测业务流的网络状态信息和该上行业务流的标识。
结合第七方面，在第七方面的某些实现方式中，该收发单元还用于接收用于传输该目标待监测业务流的网络状态信息的该上行业务流的指示信息。
结合第七方面，在第七方面的某些实现方式中，该收发单元具体用于接收该目标待监测业务流的监测配置信息、该目标待监测业务流的标识和该上行业务流的标识。
结合第七方面，在第七方面的某些实现方式中，该上行数据包还包括该目标待监测业务流的标识。
结合第七方面，在第七方面的某些实现方式中，该目标待监测业务流为第一QoS流，该上行业务流为第二QoS流中的上行业务流；或者，该目标待监测业务流为第一QoS流中的下行业务流，该上行业务流为第二QoS流中的上行业务流；或者，该目标待监测业务流为第一QoS流中的上行业务流，该上行业务流为第二QoS流中的上行业务流。
第八方面，提供了一种通信装置，该通信装置包括获取单元、收发单元和处理单元，该获取单元用于获取上行业务流的标识，该上行业务流用于传输目标待监测业务流的网络状态信息；该收发单元用于接收上行数据包，该上行数据包包括该上行业务流的标识和网络状态信息；该处理单元用于根据该上行业务流的标识确定该上行数据包包括的网络状态信息是该目标待监测业务流的网络状态信息。
结合第八方面，在第八方面的某些实现方式中，该上行业务流用于传输多个待监测业务流中各待监测业务流的网络状态信息，该多个待监测业务流包括该目标待监测业务流，该上行数据包还包括该目标待监测业务流的标识，该处理单元具体用于根据该目标待监测业务流的标识和该上行业务流的标识，确定该上行数据包包括的网络状态信息是该目标待监测业务流的网络状态信息。
结合第八方面，在第八方面的某些实现方式中，该获取单元是该收发单元，该收发单元具体用于从会话管理网元接收该上行业务流的标识。
结合第八方面，在第八方面的某些实现方式中，该收发单元还用于从该会话管理网元 接收用于传输该目标待监测业务流的网络状态信息的该上行业务流的指示信息。
结合第八方面，在第八方面的某些实现方式中，该收发单元具体用于从该会话管理网元接收该上行业务流的标识和该目标待监测业务流的标识。
结合第八方面，在第八方面的某些实现方式中，该收发单元还用于从应用功能网元接收获取该目标待监测业务流的网络状态信息的指示信息；该收发单元还用于向该会话管理网元发送该对该目标待监测业务流进行网络状态监测的指示信息。
结合第八方面，在第八方面的某些实现方式中，该获取单元是该收发单元和该处理单元，该收发单元具体用于从应用功能网元接收获取该目标待监测业务流的网络状态信息的指示信息；该处理单元具体用于根据该获取该目标待监测业务流的网络状态信息的指示信息确定该上行业务流的标识；该收发单元还用于向该接入网设备发送该目标待监测业务流的监测配置信息和该上行业务流的标识，该监测配置信息用于监测该目标待监测业务流的网络状态。
结合第八方面，在第八方面的某些实现方式中，该收发单元还用于向该接入网设备发送用于传输该目标待监测业务流的网络状态信息的该上行业务流的指示信息。
结合第八方面，在第八方面的某些实现方式中，该获取单元是该收发单元，该收发单元具体用于从接入网设备接收该上行业务流的标识。
结合第八方面，在第八方面的某些实现方式中，该目标待监测业务流为第一QoS流，该上行业务流为第二QoS流中的上行业务流；或者，该目标待监测业务流为第一QoS流中的下行业务流，该上行业务流为第二QoS流中的上行业务流；或者，该目标待监测业务流为第一QoS流中的上行业务流，该上行业务流为该第二QoS流中的上行业务流。
结合第八方面，在第八方面的某些实现方式中，该收发单元还用于发送该目标待监测业务流的网络状态信息。
结合第八方面，在第八方面的某些实现方式中，该目标待监测业务流的网络状态信息包括该目标待监测业务流的拥塞状况，该收发单元具体用于发送目标上行业务流中的至少一个上行数据包，该至少一个上行数据包中携带ECN标识的数据包的数量与该至少一个上行数据包的数量的比值用于确定该目标待监测业务流的拥塞状态，该目标上行业务流与该目标待监测业务流对应相同的业务。
第九方面，提供了一种通信装置，该通信装置包括收发单元和处理单元，该收发单元用于接收对目标待监测业务流进行网络状态监测的指示信息；该处理单元用于根据该对该目标待监测业务流进行网络状态监测的指示信息确定上行业务流的标识，该上行业务流用于传输该目标待监测业务流的网络状态信息；该收发单元还用于发送该目标待监测业务流的监测配置信息和该上行业务流的标识。
结合第九方面，在第九方面的某些实现方式中，该收发单元具体用于向会话管理网元发送该目标待监测业务流的监测配置信息和该上行业务流的标识。
结合第九方面，在第九方面的某些实现方式中，该收发单元具体用于：向接入网设备和用户面网元发送该目标待监测业务流的监测配置信息和该上行业务流的标识。
结合第九方面，在第九方面的某些实现方式中，该收发单元还用于发送用于传输该目标待监测业务流的网络状态信息的该上行业务流的指示信息。
结合第九方面，在第九方面的某些实现方式中，该收发单元具体用于发送该目标待监 测业务流的监测配置信息、该上行业务流的标识和该目标待监测业务流的标识。
结合第九方面，在第九方面的某些实现方式中，该目标待监测业务流为第一QoS流，该上行业务流为第二QoS流中的上行业务流；或者，该目标待监测业务流为第一QoS流中的下行业务流，该上行业务流为第二QoS流中的上行业务流；或者，该目标待监测业务流为第一QoS流中的上行业务流，该上行业务流为第二QoS流中的上行业务流。
第十方面，提供了一种通信装置，该通信装置包括收发单元和处理单元，该收发单元用于接收目标待监测业务流的监测配置信息，该监测配置信息用于监测该目标待监测业务流的网络状态；该处理单元用于确定上行业务流的标识，该上行业务流用于传输该目标待监测业务流的网络状态信息；该收发单元还用于向用户面网元发送该上行业务流的标识；该处理单元还用于根据该目标待监测业务流的监测配置信息进行网络状态监测以得到该目标待监测业务流的网络状态信息；该收发单元还用于该用户面网元发送上行数据包，该上行数据包包括该目标待监测业务流的网络状态信息和该上行业务流的标识。
结合第十方面，在第十方面的某些实现方式中，该上行数据包还包括该目标待监测业务流的标识。
第十一方面，提供了一种通信装置，该通信装置包括收发单元和处理单元，该收发单元用于接收目标待监测业务流的监测配置信息，该监测配置信息用于监测该目标待监测业务流的网络状态；该处理单元用于确定上行业务流的标识，该上行业务流用于传输该目标待监测业务流的网络状态信息；该处理单元还用于根据该目标待监测业务流的监测配置信息进行网络状态监测以得到该目标待监测业务流的网络状态信息；该收发单元还用于向该用户面网元发送上行数据包，该上行数据包包括该目标待监测业务流的网络状态信息、该上行业务流的标识和目标待监测业务流的标识。
结合第十一方面，在第十一方面的某些实现方式中，该收发单元还用于向用户面网元发送该上行业务流的标识。
第十二方面，提供了一种通信装置，该通信装置包括收发单元和处理单元，该收发单元用于接收上行数据包，该上行数据包包括该上行业务流的标识、目标待监测业务流的标识和网络状态信息；该处理单元用于根据该目标待监测业务流的标识确定该上行数据包包括的网络状态信息是该目标待监测业务流的网络状态信息。
第十三方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面及第一方面中任一种可能实现方式中的方法。或者以实现上述第四方面及第四方面中任一种可能实现方式中的方法，或者以实现上述第五方面及第五方面中任一种可能实现方式中的方法。示例性地，该通信装置还包括存储器。示例性地，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为接入网设备。当该通信装置为接入网设备时，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于接入网设备中的芯片。当该通信装置为配置于接入网设备中的芯片时，该通信接口可以是输入/输出接口。
示例性地，该收发器可以为收发电路。示例性地，该输入/输出接口可以为输入/输出电路。
第十四方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执 行存储器中的指令，以实现上述第二方面及第二方面中任一种可能实现方式中的方法，或者以实现上述第六方面及第六方面中任一种可能实现方式中的方法。示例性地，该通信装置还包括存储器。示例性地，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为用户面网元。当该通信装置为用户面网元时，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于用户面网元中的芯片。当该通信装置为配置于用户面网元中的芯片时，该通信接口可以是输入/输出接口。
示例性地，该收发器可以为收发电路。示例性地，该输入/输出接口可以为输入/输出电路。
第十五方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第三方面及第三方面中任一种可能实现方式中的方法。示例性地，该通信装置还包括存储器。示例性地，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为策略控制网元或会话管理网元。当该通信装置为策略控制网元或会话管理网元时，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于策略控制网元或会话管理网元中的芯片。当该通信装置为配置于策略控制网元或会话管理网元中的芯片时，该通信接口可以是输入/输出接口。
示例性地，该收发器可以为收发电路。示例性地，该输入/输出接口可以为输入/输出电路。
第十六方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面至第六方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十七方面，提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第六方面中任一种可能实现方式中的方法。
示例性地，所述处理器为一个或多个，所述存储器为一个或多个。
示例性地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收上行数据包可以为处理器接收上行数据包的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第十七方面中的处理装置可以是一个或多个芯片。该处理装置中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十八方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第六方面中任一种可能实现方式中的方法。
第十九方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得上述第一方面至第六方面中任一种可能实现方式中的方法被执行。
第二十方面，提供了一种通信***，包括前述的接入网设备和用户面网元。
可选地，该通信***还包括前述的策略控制网元和/或会话管理网元。
附图说明
图1是适用于本申请实施例提供的方法的通信***的示意图；
图2是本申请实施例提供的通信方法的示意性流程图；
图3是本申请实施例提供的通信方法的示意性流程图；
图4是数据包的网络互连协议(Internet protocol，IP)头部格式示意图；
图5是本申请实施例提供的通信方法的示意性流程图；
图6是本申请实施例提供的通信方法的示意性流程图；
图7是本申请实施例提供的通信装置的示意性框图；
图8是本申请另一实施例提供的通信设备的示意性框图；
图9是本申请实施例提供的芯片***的示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信***，例如，长期演进(long term evolution，LTE)***、频分双工(frequency division duplex，FDD)***、时分双工(time division duplex，TDD)***、通用移动通信***(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信***、第五代(5th generation，5G)***或新无线(new radio，NR)、第六代(6th generation，6G)***或未来的通信***等。本申请中所述的5G移动通信***包括非独立组网(non-standalone，NSA)的5G移动通信***或独立组网(standalone，SA)的5G移动通信***。通信***还可以是公共陆地移动网络(public land mobile network，PLMN)、设备到设备(device to device，D2D)通信***、机器到机器(machine to machine，M2M) 通信***、物联网(Internet of things，IoT)通信***、车联万物(vehicle to everything，V2X)通信***、无人机(uncrewed aerial vehicle，UAV)通信***或者其他通信***。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a和b，a和c，b和c，或a和b和c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性地”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性地”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性地”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
为便于理解本申请实施例，首先结合图1详细说明本申请实施例的一个应用场景。
1、用户设备(user equipment，UE)：可以称为终端设备、终端、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理器(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其他处理设备、车载设备、无人机、可穿戴设备、5G网络中的终端设备或演进的PLMN中的终端设备等，本申请实施例对此并不限定。
2、接入网(access network，AN)：为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等使用不同质量的传输隧道。接入网络可以为采用不同接入技术的接入网络。目前的接入网络技术包括：第三代(3rd generation，3G)***中采用的无线接入网技术、***(4th generation，4G)***中采用的无线接入网技术、或下一代无线接入网(next generation radio access network，NG-RAN)技术(如5G***中采用的无线接入技术等)。
基于无线通信技术实现接入网络功能的接入网可以称为无线接入网络(radio access network，RAN)。无线接入网能够管理无线资源，为终端提供接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
无线接入网设备例如可以是基站(NodeB)、演进型基站(evolved NodeB，eNB或 eNodeB)、5G移动通信***中的下一代基站节点(next generation Node Base station，gNB)、未来移动通信***中的基站或wifi无线热点***中的接入点(access point，AP)等，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该无线接入网设备可以为中继站、接入点、车载设备、无人机、可穿戴设备以及5G网络中的网络设备或者演进PLMN中的网络设备等。本申请实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。
3、接入管理网元：主要用于移动性管理和接入管理、负责在用户设备与策略控制功能(policy control function，PCF)网元间传递用户策略等，可以用于实现移动性管理实体(mobile management entity，MME)功能中除会话管理之外的其他功能。例如，接入授权(鉴权)的功能。
在5G通信***中，接入管理网元可以是接入和移动性管理功能(access and mobility management function，AMF)网元。在未来通信***中，接入管理网元仍可以是AMF网元，或者，还可以有其他的名称，本申请不做限定。
4、会话管理网元：主要用于会话管理、用户设备的网络互连协议(Internet protocol，IP)地址的分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通信等。
在5G通信***中，会话管理网元可以是会话管理功能(session management function，SMF)网元。在未来通信***中，会话管理网元仍可以是SMF网元，或者，还可以有其他的名称，本申请不做限定。
5、用户面网元：用于分组路由和转发、用户面数据的服务质量(quality of services，QoS)处理、完成用户面数据转发、基于会话/流级的计费统计，带宽限制功能等。
在5G通信***中，用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信***中，用户面网元仍可以是UPF网元，或者，还可以有其他名称，本申请不做限定。
6、数据网络网元：用于提供传输数据的网络。
在5G通信***中，数据网络网元可以是数据网络(data network，DN)网元。在未来通信***中，数据网络网元仍可以是DN网元，或者，还可以有其他名称，本申请不做限定。
7、策略控制网元：用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
在4G通信***中，该策略控制网元可以是策略和计费规则功能(policy and charging rules function，PCRF)网元。在5G通信***中，该策略控制网元可以是策略控制功能(policy control function，PCF)网元。在未来通信***中，该策略控制网元仍可以是PCF网元，或者，还可以有其他名称，本申请不做限定。
8、数据管理网元：用于处理用户设备标识、接入鉴权、注册以及移动性管理等。
在5G通信***中，该数据管理网元可以是统一数据管理(unified data management，UDM)网元；在4G通信***中，该数据管理网元可以是归属用户服务器(home subscriber serve，HSS)网元。在未来通信***中，数据管理网元仍可以是UDM网元，或者，还可以有其他的名称，本申请不做限定。
9、网络开放功能(network exposure function，NEF)网元：用于安全地向外部开放由第三代合作伙伴项目(3rd generation partnership project，3GPP)网络功能提供的业务和能力等。
10、应用功能(application function，AF)网元：向UE提供某种应用层服务，AF在向UE提供服务时，对QoS策略和计费(charging)策略有要求，且需要通知网络。同时，AF也需要获取核心网反馈应用相关的信息。AF可以具有技术规范(technological specification，TS)23.501R-15版本中定义的AF的所有功能，以及具有用于应用业务的相关功能。也就是说，在用户面架构中，应用服务器与UE是通过UE-RAN-UPF-AF的路径进行用户面通信。AF还可以在控制面架构中，通过NEF与5G核心网(5G core network，5GC)中的其他网络功能(network function，NF)进行通信。比如通过NEF与PCF通信。如果AF由5GC的运营商布置，则AF还可在控制面架构中，即AF处于可信域内，不通过NEF与5GC中的其他NF进行直接通信，比如直接与PCF通信。
11、网络数据分析功能(network data analysis function，NWDAF)网元：可用于收集来自网元、AF以及运维管理***(operation administration and maintenance，OAM)侧的数据，并通过机器学习、人工智能等方案对数据进行分析，并反馈于网元、AF等进行网络或业务配置优化，从而提供更好的网络质量与业务体验。
12、网络存储功能(network repository function，NRF)网元：可用于提供网元发现功能，基于其他网元的请求，提供网元类型对应的网元信息。NRF网元还提供网元管理服务，如网元注册、更新、去注册以及网元状态订阅和推送等。
13、鉴权服务器功能(authentication server function，AUSF)网元：主要负责对用户进行鉴权，以确定是否允许用户或设备接入网络。
14、服务通信代理(service communication proxy，SCP)网元：可以用于NF之间的间接通信，NF的服务请求可以由SCP网元代理。
图1中N1、N2、N3、N4、N6、N9、Nnwdaf、Nnef、Nnrf、Npcf、Nudm、Naf、Nausf、Namf以及Nsmf为接口序列号。这些接口序列号的含义可参见3GPP技术标准(technical standards，TS)23.501定义的含义。
应理解，上述应用于本申请实施例的网络架构仅是举例说明，适用于本申请实施例的网络架构并不局限于此，任何能够实现上述各网元的功能的网络架构都适用于本申请实施例。
还应理解，图1所示的AMF、SMF、UPF、NEF、PCF、UDM、NWDAF、NRF、AUSF、SCP等可以理解为核心网中用于实现不同功能的网元，例如可以按需组合成网络切片。这些核心网网元可以是各自独立的设备，也可以集成于同一设备中实现不同的功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在5G网络以及未来其他的网络中采用其他命名的可能。例如，在6G网络中，上述各个网络中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
如果第三方应用能实时地感知网络状态，那么第三方应用可以根据网络状态进行相应调整，从而保证用户的业务体验，以及最大化网络利用效率。因此如何将更多的网络状态信息，诸如可用带宽、拥塞状况等快速开放给第三方应用是一个关键问题。
一种实现方式中，RAN可以监测网络的拥塞状况，并通过在下行数据包的IP版本4(IP version 4，IPv4)头部标识ECN的方式将网络的拥塞状况开放出去。比如，RAN在下行数据包的分组数据汇聚协议(packet data convergence protocol，PDCP)头部(即PDCP服务数据单元(service data unit，SDU)中)添加ECN标识，并将下行数据包发送给UE。随后再由UE通过应用层将该下行数据包发送给应用服务器侧，从而使得第三方应用可以获得到网络的拥塞状况。然而上述方式中，网络的拥塞状况传输链路长，时效性差。此外，上述方式需要RAN解析下行数据包的IP头，从而存在安全隐患。
另一种实现方式中，网络状态信息可以通过控制面或用户面的形式开放给应用层。例如，网络状态信息可以通过UPF服务化接口或NEF开放给第三方应用。又例如，UPF可以将网络状态信息添加到数据包发送给应用服务器侧。然而在上述方式中，由于UPF无法对空口侧RAN与UE之间的网络状态进行监测，如果RAN需要向第三方应用开的空口侧RAN与UE之间的网络状态信息，则UPF只能从RAN接收空口侧的网络状态信息。在此情况下，RAN如何将空口侧的网络状态信息发送给UPF将成为一个亟待解决的问题。
有鉴于此，本申请实施例提供一种通信方法，可以实现RAN将进行网络状态监测得到的网络状态信息发送给UPF。
需要说明的是，本申请实施例中将来自终端设备或接入网设备，目的地址为第三方应用服务器的业务流称为上行业务流。将来自第三方应用服务器，目的地址为终端设备的业务流称为下行业务流。第三方应用服务器为终端设备提供上行业务流和/或下行业务流对应的应用业务。
还需要说明的是，本申请实施例中提及的用户面网元可以是UPF，会话管理网元可以是SMF，策略控制网元可以是PCF，以及接入网设备可以是RAN。
图2示出了本申请实施例提供的通信方法的示意性流程图。下面详细描述方法200包括的各个步骤。
S210，用户面网元获取上行业务流的标识。
上行业务流用于传输目标待监测业务流的网络状态信息。为了便于描述，下文中将用于传输目标待监测业务流的上行业务流记为上行业务流#1。上行业务流#1的标识用于标识上行业务流#1。示例性地，上行业务流#1的标识包括以下一项或多项：数据连接会话标识(比如：协议数据单元(protocal data unit，PDU)会话标识#1，或IP-CAN会话标识，或其它会话的标识，为便于描述，后续实例以PDU会话为例进行说明)、业务流描述信息#1、应用标识#1、第二OoS流标识(QoS flow identifier，QFI)、业务类型标识#1和应用类型标识#1。
其中，PDU会话标识#1为承载上行业务流#1的PDU会话#1的会话标识信息。例如，若PDU会话#1只承载了上行业务流#1，则上行业务流#1的标识可以是PDU会话标识#1。
业务流描述信息#1用于确定上行业务流#1。业务流描述信息#1可以为上行业务流#1的IP五元组描述信息、IP三元组信息、域名、上下行等IP数据包过滤集中的至少一个。上行业务流#1的IP五元组描述信息可以为：源IP地址(source IP address)#1、目的IP 地址(destination IP address)#1、源端口号(source port number)#1、目的端口号(destination port number)#1和协议类型#1。上行业务流#1的IP三元组信息可以为：目的IP地址#1、目的端口号#1与协议类型#1。或者业务流描述信息#1可以为以太网(ethernet)包头信息中的至少一个，例如，源媒体访问控制(media access control，MAC)地址#1和目的MAC地址#1、虚拟局域网(virtual local area network，VLAN)标识#1等。业务流描述信息#1还可以包括应用标识#1。示例性地，业务流描述信息#1也可以称为业务数据流(service data flow，SDF)描述信息#1。SDF描述信息可以参考IP数据包过滤集，关于IP数据包过滤集的描述可以参考3GPP TS 23.501中的描述。
应用标识#1用于标识上行业务流#1对应的应用#1。例如，若应用#1只有上行业务流#1，而没有下行业务流，则上行业务流#1的标识可以是应用标识#1。
第二QFI用于标识第二QoS流，上行业务流#1在第二QoS流中传输。例如，若第二QoS流仅对应上行业务流#1，即仅上行业务流#1在第二QoS流中传输，则上行业务流#1的标识可以是第二QFI，也可以说该上行业务流#1是第二QoS流。
业务类型标识#1可以为上行业务流#1的类型的标识，例如，上行业务流#1的类型可以是视频类业务、语音类业务、游戏类业务或网页浏览类业务等。
应用类型标识#1可以为上行业务流#1对应的应用#1的类型的标识。
目标待监测业务流可以是上行业务流，也可以是下行业务流，本申请实施例对此不做限定。示例性地，目标待监测业务流是下行业务流，则目标待监测业务流与上行业务流#1对应相同的业务，或者目标待监测业务与上行业务流#1对应不同的业务。又示例性地，目标待监测业务流是上行业务流，则目标待监测业务流与上行业务流#1是相同的业务流，或者，目标待监测业务流与上行业务流#1是不同的业务流。
可选地，方法200还包括：用户面网元获取目标待监测业务流的标识，目标待监测业务流的标识用于标识目标待监测业务流。目标待监测业务流的标识可以包括以下一项或多项：数据连接标识(比如：PDU会话标识#2)、业务流描述信息#2、应用标识#2、第一QFI、业务类型标识#2和应用类型标识#2。当用户面网元获取到目标待监测业务流的标识之后，用户面网元可以确定网络将对目标待监测业务流进行网络状态监测。进而当用户面网元获取到上行业务流#1的标识之后，用户面网元可以确定上行业务流#1用于传输目标待监测业务流的网络状态信息。
其中，PDU会话标识#2为承载目标待监测业务流的PDU会话#2的会话标识信息。例如，若PDU会话#2只承载了目标待监测业务流，则目标待监测业务流的标识可以是PDU会话标识#2。
业务流描述信息#2用于确定目标待监测业务流。业务流描述信息#2可参考业务流描述信息#1的描述。
应用标识#2用于标识目标待监测业务流对应的应用#2。例如，若应用#2只有目标待监测业务流，而没有其他业务流，则目标待监测业务流的标识可以是应用标识#2。
第一QFI用于标识第一QoS流，目标待监测业务流在第一QoS流中传输。若第一QoS流仅对应目标待监测业务流汇聚，即仅目标待监测业务流在第一QoS流中传输，则目标待监测业务流的标识可以是第一QFI，也可以说目标待监测业务流是第一QoS流。
业务类型标识#2可以为目标待监测业务流的类型的标识，例如，目标待监测业务流 的类型可以是视频类业务、语音类业务、游戏类业务或网页浏览类业务等。
应用类型标识#2可以为目标待监测业务流对应的应用#2的类型的标识。
需要说明的是，若目标待监测业务流是下行业务流，且目标待监测业务流与上行业务流#1对应相同的业务，则上行业务流#1对应的第二QoS流与目标待监测业务流对应的第一QoS流可以是同一个QoS流，或者，第二QoS流与第一QoS流可以是不同的QoS流。
若目标待监测业务流是上行业务流，且目标待监测业务流与上行业务流#1是相同的业务流，则上行业务流#1对应的第二QoS流与目标待监测业务流对应的第一QoS流可以是同一个QoS流。或者，若目标待监测业务流是上行业务流，且目标待监测业务流与上行业务流#1是不同的业务流，则上行业务流#1对应的第二QoS流与目标待监测业务流对应的第一QoS流是不同的QoS流。
本申请实施例对用户面网元获取上行业务流#1的标识的方式不做限定。
一种可能的实现方式中，用户面网元获取上行业务流#1的标识，包括：用户面网元接收来自会话管理网元的上行业务流#1的标识。相应地，会话管理网元向用户面网元发送上行业务流#1的标识。更多关于会话管理网元向用户面网元发送上行业务流#1的标识的描述，可以参考下文方法300中的S340，为了简洁，此处暂不详述。
示例性地，在会话管理网元向用户面网元发送上行业务流#1的标识之前，方法200还包括：会话管理网元确定上行业务流#1的标识。会话管理网元确定上行业务流#1的标识的流程，可以参考下文方法300，为了简洁，此处暂不详述。
又示例性地，在会话管理网元向用户面网元发送上行业务流#1的标识之前，方法200还包括：会话管理网元从策略控制网元接收目标待监测业务流的监测配置信息和上行业务流#1的标识。相应地，策略控制网元确定上行业务流#1的标识，并向会话管理网元发送目标待监测业务流的监测配置信息和上行业务流#1的标识。策略控制网元确定上行业务流#1的标识的流程，可以参考下文方法500，为了简洁，此处暂不详述。
另一种可能的实现方式中，用户面网元获取上行业务流#1的标识，包括：用户面网元接收来自应用功能网元的获取目标待监测业务流的网络状态信息的指示信息；用户面网元根据获取目标待监测业务流的网络状态信息的指示信息确定上行业务流#1的标识。用户面网元确定上行业务流#1的标识的流程，可以参考下文方法600，为了简洁，此处暂不详述。
再一种可能的实现方式中，用户面网元获取上行业务流#1的标识，包括：用户面网元接收来自接入网设备的上行业务流#1的标识。相应地，接入网设备向用户面网元发送上行业务流#1的标识。
可选地，用户面网元接收来自接入网设备的上行业务流#1的标识，包括：用户面网元接收来自接入网设备的上行业务流#1的标识和目标待监测业务流的标识。
可选地，方法200还包括：用户面网元接收来自接入网设备的用于传输目标待监测业务流的上行业务流#1的指示信息。为了便于描述，下文中将用于传输目标待监测业务流的上行业务流#1的指示信息记为指示信息#1。示例性地，指示信息#1可以是一个1比特的信息。又示例性地，指示信息#1是目标待监测业务流的监测配置信息或者是事件标识(event identifier)，事件标识用于指示订阅目标待监测业务流的网络状态信息，和/或，用于指示开放目标待监测业务流的网络状态信息。或者说事件标识与“订阅目标待监测业 务流的网络状态信息”这一事件或“开放目标待监测业务流的网络状态信息”这一事件对应。事件标识可以包括监测参数以及上报的目标网元或实体的信息。监测参数可以包括以下一项或多项：传输时延、丢包率、拥塞程度、发送数据队列的长度和可用带宽
可选地，用户面网元从上行数据包中获取上行业务流#1的标识，相应地，接入网设备在向用户面网元发送的上行数据包中添加上行业务流#1的标识。即S210可以在S240与S250之间执行。
需要说明的是，接入网设备可以将上行业务流#1的标识和指示信息#1携带在同一条消息中发送给用户面网元，或者，接入网设备可以将上行业务流#1的标识和指示信息#1携带在不同的消息中发送给用户面网元。
示例性地，在接入网设备向用户面网元发送上行业务流#1的标识之前，方法200还包括：接入网设备确定上行业务流#1的标识。接入网设备确定上行业务流#1的标识的方式，可以参考下文S220，此处暂不详述。
需要说明的是，本申请实施例不限定上行业务流#1仅用于传输目标待监测业务流的网络状态信息。例如，上行业务流#1可以用于传输多个待监测业务流中各个待监测业务流的网络状态信息，多个待监测业务流包括目标待监测业务流。示例性地，多个待监测业务流还包括上行业务流#1。
需要说明的是，该步骤为可选的。例如，若上行业务流#1的标识是由接入网设备确定的，接入网设备可以不向用户面网元发送上行业务流#1的标识。
可选地，方法200还包括：会话管理网元向用户面网元发送目标待监测业务流的监测配置信息。目标待监测业务流的监测配置信息用于监测目标待监测业务流的网络状态，目标待监测业务流的监测配置信息包括监测参数以及目标待监测业务流的标识或用户面通用分组无线网(general packet radio system，GPRS)隧道协议(GPRS tunneling protocol user plane，GTP-U)隧道标识。
其中，监测参数可以包括以下一项或多项：传输时延、丢包率、拥塞程度、发送数据队列的长度和可用带宽。可选地，目标待监测业务流的监测配置信息还可以包括目标待监测业务流的网络状态信息的上报周期。可选地，目标待监测业务流的监测配置信息还可以包括上报目标待监测业务流的网络状态信息的触发条件。例如，目标待监测业务流的监测配置信息包括传输时延门限，则当目标待监测业务的传输时延超过传输时延门限时，触发上报目标待监测业务流的网络状态信息。可选地，目标待监测业务流的监测配置信息还可以包括用于指示订阅目标待监测业务流的网络状态信息的事件标识。可选地，目标待监测业务流的监测配置信息还可以包括上报目标待监测业务流的网络状态信息的方式，例如上报目标待监测业务流的网络状态信息的方式为：由用户面网元或接入网设备上报给会话管理网元；或，由接入网设备上报给用户面网元；或，由用户面网元直接对外进行开放。可选地，目标待监测业务流的监测配置信息还包括上报目标网元或实体信息。上报目标网元或实体信息用于指示上报目标待监测业务流的网络状态信息的目标网元或目标实体，或者说上报目标网元或实体信息用于指示用于接收目标待监测业务流的网络状态信息的目标网元或目标实体。
GTP-U隧道标识用于标识在接入网设备和用户面网元之间承载目标待监测业务流的GTP-U隧道。示例性地，若该GTP-U隧道只承载了目标待监测业务流，则目标待监测业 务流的监测配置信息可以包括GTP-U隧道的标识。或者，若目标待监测业务流为GTP-U隧道上的所有业务流的集合，那么监测配置信息可以包括GTP-U隧道的标识。
S220，接入网设备获取目标待监测业务流的监测配置信息和上行业务流的标识。
需要说明的是，接入网设备接收到上行业务流的标识即上文所描述的上行业务流#1的标识。上行业务流#1的标识可以包含于监测配置信息中，也可以在监测配置信息之外，在此不做限定。
一种可能的实现方式中，接入网设备获取目标待监测业务流的监测配置信息和上行业务流#1的标识，包括：接入网设备从会话管理网元接收目标待监测业务流的监测配置信息和上行业务流#1的标识。相应地，会话管理网元向接入网设备发送目标待监测业务流的监测配置信息和上行业务流#1的标识。更多关于会话管理网元向接入网设备发送目标待监测业务流的监测配置信息和上行业务流#1的标识的描述，可以参考下文方法300中的S330，为了简洁，此处暂不详述。
示例性地，在会话管理网元向接入网设备发送上行业务流#1的标识和目标待监测业务流的监测配置信息之前，方法200还包括：会话管理网元确定上行业务流#1的标识和目标待监测业务流的监测配置信息。会话管理网元确定上行业务流#1的标识和目标待监测业务流的监测配置信息的流程，可以参考下文方法300，为了简洁，此处暂不详述。又示例性地，在会话管理网元向接入网设备发送上行业务流#1的标识和目标待监测业务流的监测配置信息之前，方法200还包括：会话管理网元接收来自策略控制网元的上行业务流#1的标识和目标待监测业务流的监测配置策略；会话管理网元根据目标待监测业务流的监测配置策略确定目标待监测业务流的监测配置信息。
另一种可能的实现方式中，接入网设备获取目标待监测业务流的监测配置信息和上行业务流#1的标识，包括：接入网设备从用户面网元接收目标待监测业务流的监测配置信息和上行业务流#1的标识。相应地，用户面网元向接入网设备发送目标待监测业务流的监测配置信息和上行业务流#1的标识。更多关于用户面网元向接入网设备发送目标待监测业务流的监测配置信息和上行业务流#1的标识的描述，可以参考下文方法600中的S630，为了简洁，此处暂不详述。
示例性地，在用户面网元向接入网设备发送上行业务流#1和目标待监测业务流的监测配置信息之前，方法200还包括：用户面网元确定上行业务流#1的标识以及获取目标待监测业务流的监测配置信息。用户面网元确定上行业务流#1的标识的流程，可以参考下文方法600，为了简洁，此处不再详述。用户面网元获取目标待监测业务流的监测配置信息的方法包括：用户面网元接收来自会话管理网元的目标待监测业务流的监测配置信息。
再一种可能的实现方式中，接入网设备获取目标待监测业务流的监测配置信息和上行业务流#1的标识，包括：接入网设备接收来自会话管理网元的目标待监测业务流的监测配置信息；接入网设备接收来自用户面网元的上行业务流#1的标识。
可选地，接入网设备接收来自用户面网元的上行业务流#1的标识，包括：接入网设备接收来自用户面网元的上行业务流#1的标识和目标待监测业务流的标识。
可选地，方法200还包括：接入网设备接收来自用户面网元的指示信息#1。
再一种可能的实现方式中，接入网设备获取目标待监测业务流的监测配置信息和上行 业务流#1的标识，包括：接入网设备从会话管理网元或用户面网元接收目标待监测业务流的监测配置信息；接入网设备根据该监测配置信息确定上行业务流#1的标识。
示例性地，接入网设备接收到目标待监测业务流的监测配置信息后，根据目标待监测业务流的监测配置信息确定对目标待监测业务流进行网络状态监测。进一步地，接入网设备从已建立的上行业务流中选择一个上行业务流#1用于传输目标待监测业务流的网络状态信息。可选地，上行业务流#1与目标待监测业务流属于同一个GTP-U隧道。
S230，接入网设备根据目标待监测业务流的监测配置信息进行网络状态监测得到目标待监测业务流的网络状态信息。
示例性地，接入网设备根据监测配置信息包括的目标待监测业务流的标识或GTP-U隧道标识确定针对目标待监测业务流进行网络状态监测。进一步地，接入网设备针对监测配置信息包括的监测参数进行网络状态监测。示例性地，接入网设备可以针对目标待监测业务流监测的所在的无线承载进行网络监测。例如，若监测参数包括传输时延，则接入网设备监测目标待监测业务流中的数据包在接入网设备与用户面网元之间的传输时延。若监测参数包括丢包率，则接入网设备监测目标待监测业务流中的数据包的丢包率。若监测参数包括发送数据队列长度，则接入网设备监测目标待监测业务流中的数据包的发送队列长度，需要说明的是，该发送队列长度可以是接入网设备侧的PDCP层、MAC层等不同层中的发送队列，在此不做限定。若监测参数包括可用带宽，则接入网设备监测目标待监测业务流的可用带宽。若监测参数包括拥塞程度，则接入网设备监测目标待监测业务流的拥塞程度。
其中，目标待监测业务流的拥塞程度可以通过监测传输时延、丢包率、发送数据队列长度或可用带宽获得。例如，接入网设备通过比较目标待监测业务流中的数据包的传输时延与传输时延阈值，确定目标待监测业务流是否发生拥塞，或者确定目标待监测业务流的拥塞情况，或者确定目标待监测业务流的网络状态信息。例如，若目标待监测业务流中的数据包传输时延超过传输时延阈值，则接入网设备确定目标待监测业务流发生了拥塞。又例如，在目标待监测业务流中的数据包的传输时延小于传输时延阈值的情况下，接入网设备可以根据目标待监测业务流中的数据包的传输时延与传输时延阈值，确定目标待监测业务流的拥塞程度。例如，若目标待监测业务流中的数据包的传输时延与传输时延阈值的比值是60％，则接入网设备确定目标待监测业务流的拥塞程度是60％。
类似地，接入网设备可以通过比较目标待监测业务流中的数据包的丢包率与丢包率阈值，确定目标待监测业务流是否发生拥塞，或者确定目标待监测业务流的拥塞情况，或者确定目标待监测业务流的网络状态信息。或者，接入网设备根据目标待监测业务流中的数据包的丢包率和丢包率阈值的比值，确定目标待监测业务流的拥塞程度。
接入网设备也可以通过比较目标待监测业务流的发送队列长度与发送队列长度阈值，确定目标待监测业务流是否发送拥塞，或者确定目标待监测业务流的拥塞情况，或者确定目标待监测业务流的网络状态信息。或者，接入网设备根据目标待监测业务流的发送队列长度与发送队列长度阈值的比值，确定目标待监测业务流的拥塞程度。
接入网设备也可以通过比较目标待监测业务流的可用带宽与可用带宽阈值，确定目标待监测业务流是否发送拥塞，或者确定目标待监测业务流的拥塞情况，或者确定目标待监测业务流的网络状态信息。或者，接入网设备根据目标待监测业务流的可用带宽与可用带 宽阈值的比值，确定目标待监测业务流的拥塞程度。
传输时延阈值、丢包率阈值、发送队列长度阈值或可用带宽阈值可以包括在目标待监测业务流的监测配置信息中，也可以是协议预定义的，本申请实施例对此不做限定。
可以理解，接入网设备通过网络状态监测得到的目标待监测业务流的网络状态信息与监测参数有关。例如，监测参数包括传输时延，则目标待监测业务流的网络状态信息包括目标待监测业务流中的数据包的传输时延。又例如，监测参数包括拥塞程度，则目标待监测业务流的网络状态信息包括目标待监测业务流的拥塞信息，拥塞信息用于确定目标待监测业务流是否发生拥塞和/或目标待监测业务流的拥塞程度。
S240，接入网设备向用户面网元发送上行数据包。相应地，用户面网元接收来自接入网设备的上行数据包。
上行数据包包括上行业务流#1的标识和目标待监测业务流的网络状态信息，也就是说，上行数据包是上行业务流#1中的数据包。该上行数据包可以是接入网设备从终端设备接收的数据包，或者，该上行数据包可以是接入网设备生成的空数据包。其中，上行数据包包括的上行业务流#1的标识可以是第二QFI。例如，该第二QFI携带于上行数据包的GTP-U层头部。
示例性地，目标待监测业务流的网络状态信息包括在上行数据包的GTP-U层头部。
一种可能的实现方式中，接入网设备一旦得到目标待监测业务流的网络状态信息，就通过上行业务流#1中的上行数据包向用户面网元发送目标待监测业务流的网络状态信息。
另一种可能的实现方式中，若目标待监测业务流的监测配置信息包括上报周期，则接入网设备根据该上报周期，周期性地通过上行业务流#1中的上行数据包向用户面网元发送目标待监测业务流的网络状态信息。
例如，若上报周期是10秒，则接入网设备每间隔10秒，就通过上行业务流#1中的上行数据包向用户面网元发送目标待监测业务流的网络状态信息。
再一种可能的实现方式中，若目标待监测业务流的监测配置信息包括上报目标待监测业务流的网络状态信息的触发条件，则在该触发条件被满足的情况下，接入网设备通过上行业务流#1中的上行数据包向用户面网元发送目标待监测业务流的网络状态信息。
例如，该触发条件是传输时延超过传输时延阈值或发送队列长度超过发送队列长度阈值等，则在目标待监测业务流中的数据包的传输时延超过传输时延阈值或发送队列长度超过发送队列长度阈值等情况下，接入网设备通过上行业务流#1的上行数据包向用户面网元发送目标待监测业务流的网络状态信息。
可选地，该上行数据包还包括目标待监测业务流的标识。例如，若上行业务流#1用于传输多个待监测业务流中各个待监测业务流的网络状态信息，则接入网设备可以在上行数据包中添加目标待监测业务流的标识。又例如，若上行业务流#1的标识是由接入网设备确定的，且接入网设备未向用户面网元发送上行业务流#1的标识，则接入网设备在上行数据包中添加目标待监测业务流的标识，从而使用户面网元确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。或者，可以理解为接入网设备在上行数据包中添加目标待监测业务流的标识，该上行数据包中会带有该上行业务流#1的标识。
可选地，若目标待监测业务流的监测配置信息包括上报目标待监测业务流的网络状态信息的方式，且该方式为由接入网设备上报给用户面网元，则在S240中，接入网设备向 用户面网元发送包括目标待监测业务流的网络状态信息的上行数据包。
S250，用户面网元根据上行业务流的标识和/或目标待监测业务流的标识确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。
如上文所述，上行业务流#1用于传输目标待监测业务流的网络状态信息，因此用户面网元从接入网设备接收到上行数据包之后，可以根据上行数据包包括的上行业务流#1的标识确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。
可选地，若上行业务流#1用于传输多个待监测业务流中各个待监测业务流的网络状态信息，上行数据包的GTP-U层头部包括上行业务流#1的标识和目标待监测业务流的标识，则用户面网元根据上行业务流#1的标识和目标待监测业务流的标识，确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。
可选地，若用户面网元未获取到上行业务流#1的标识，则在S250中，若用户面网元接收到的上行数据包包括目标待监测业务流的标识，则用户面网元根据目标待监测业务流的标识确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。
可选地，方法200还包括：用户面网元发送目标待监测业务流的网络状态信息。关于用户面网元发送目标待监测业务流的网络状态信息的流程，可以参考下文方法300，为了简洁，此处暂不详述。
在本申请实施例中，接入网设备和用户面网元都可以获取到用于传输目标待监测业务流的网络状态信息的上行业务流的标识，进而接入网设备可以使用上行业务流#1中的上行数据包向用户面网元发送目标待监测业务流的网络状态信息，以及用户面网元可以根据上行数据包包括的上行业务流#1的标识和/或目标待监测业务流的标识确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。该方法实现了接入网设备向用户面网元发送目标待监测业务流的网络状态信息，从而户面网元可以将接收到的网络状态信息开放给第三方应用，使得第三方应用可以根据网络状态信息调整目标待监测业务流的传输参数，保障用户的业务体验。例如若目标待监测业务流是下行业务流，即使目标待监测业务流内不存在上行数据流，也可以实现接入网设备将目标待监测业务流的网络状态信息发送给用户面网元。以媒体业务为例，媒体业务同时承载于两个不同的业务流上。媒体业务的上行业务流中传输的是业务会话的一些控制信息或用户的视角、动作等姿态信息，而媒体业务的下行业务流仅负责下行媒体数据的下发，即单个业务流内仅仅包含单向的业务流。若接入网设备针对媒体业务的下行业务流进行拥塞信息监测时，由于媒体业务的下行业务流内不存在上行数据流，接入网设备无法将媒体业务的下行业务流的网络状态信息快速发送给用户面网元。然而根据本申请实施例，若用户面网元和接入网设备获取到用于传输媒体业务的下行业务流的网络状态信息的上行业务流的标识，则接入网设备可以将媒体业务的下行业务流的网络状态信息快速发送给用户面网元。
此外，根据本申请实施例的方法，接入网设备向用户面网元发送的是业务流粒度的网络状态信息，若用户面网元将业务流粒度的网络状态信息开放给第三方应用服务器，则第三方应用服务器可以针对业务流的网络状态信息对业务流的参数进行调整，从而适应于网络状态的变化，满足用户对不同业务流的体验需求。
图3示出了本申请实施例提供的通信方法的示意性流程图。具体地，图3示出了方法200提及的由会话管理网元确定上行业务流#1的标识的实施例的方法流程，以及图3示出 了方法200提及的用户面网元发送目标待监测业务流的网络状态信息的方法流程。下面详细描述方法300包括的各个步骤。
S310，会话管理网元接收对目标待监测业务流进行网络状态监测的指示信息。
一种可能的实现方式中，S310包括S311和S312。
S311，应用功能网元向策略控制网元发送指示信息#2。相应地，策略控制网元接收来自应用功能网元的指示信息#2。
指示信息#2用于指示对目标待监测业务流进行网络状态监测，和/或用于指示确定用于传输目标待监测业务流的上行业务流#1的标识。
本申请实施例对指示信息#2的形式不做限定，可以是以下示例中的一个或多个。
示例性地，指示信息#2是业务流描述信息#2，业务流描述信息#2用于确定目标待监测业务流。更多关于业务流描述信息#2的描述可以参考上文S210。
又示例性地，指示信息#2是1比特的信息。
再示例性地，指示信息#2是事件标识。事件标识的描述可以参考上文S210。
再示例性地，指示信息#2是事件上报触发条件，事件上报触发条件用于指示对外开放目标待监测业务流的网络状态信息的触发条件。如固定周期进行对外开放、事件触发等。
本申请实施例对应用功能网元向策略控制网元发送指示信息#2的方式不做限定。例如，应用功能网元可以通过应用功能请求(AF request)消息向策略控制网元发送指示信息#2。即应用功能网元向策略控制网元发送AF请求消息，AF请求消息包括指示信息#2。
示例性地，应用功能网元直接向策略控制网元发送指示信息#2，或者，应用功能网元先向网络开放功能网元(network exposure function，NEF)发送指示信息#2，网络开放功能网元再将指示信息#2转发给策略控制网元。
可选地，若应用功能网元在先没有向策略控制网元发送业务流描述信息#2，且指示信息#2不是业务流描述信息#2，则在S311中，应用功能网元向策略控制网元发送业务流描述信息#2和指示信息#2。例如，应用功能网元向策略控制网元发送AF请求消息，AF请求消息包括业务流描述信息#2和指示信息#2。
S312，策略控制网元向会话管理网元发送指示信息#3。相应地，会话管理网元接收来自策略控制网元的指示信息#3。
该指示信息#3用于指示对目标待监测业务流进行网络状态监测，或者，该指示信息#3用于指示会话管理网元生成目标待监测业务流的监测配置信息，关于目标待监测业务流的监测配置信息的描述可以参考上文S210。或者，指示信息#3也可以用于指示确定用于传输目标待监测业务流的上行业务流#1的标识。指示信息#3的形式可以参考指示信息#2的形式的描述。
指示信息#3可以是策略控制功能网元根据指示信息#2生成的，或者，指示信息#3等同于指示信息#2，本申请实施例对此不做限定。
可选地，若策略控制网元在先没有向会话管理网元发送目标待监测业务流的监测配置策略，则在S312中，策略控制网元还向会话管理网元发送目标待监测业务流的监测配置策略。关于目标待监测业务流的监测配置策略的更多描述可以参考下文S320，该指示信息#3可以包含在监测配置策略中。
可选地，在S312中，策略控制网元可以不向会话管理网元发送目标待监测业务流的 监测配置策略，而是在S312之后，若策略控制网元从会话管理网元接收策略请求消息，策略请求消息用于请求目标待监测业务流的监测配置策略。则策略控制网元响应于策略请求消息，向会话管理网元发送目标待监测业务流的监测配置策略。
示例性地，策略控制网元在会话管理策略关联建立或修改流程中将指示信息#3发往会话管理网元侧。
另一种可能的实现方式中，S310包括S313和S314。
S313，应用功能网元向用户面网元发送指示信息#4。相应地，用户面网元接收来自应用功能网元的指示信息#4。
指示信息#4用于指示获取目标待监测业务流的网络状态信息，和/或，指示信息#4可以用于指示对目标待监测业务流的网络状态进行监测。指示信息#4的形式可以参考指示信息#2的形式的描述。
示例性地，应用功能网元可以调用UPF服务化接口-订阅(Nupf_subscribe)服务接口向用户面网元发送指示信息#4。
又示例性地，应用功能网元先向网络开放功能网元发送指示信息#4，网络开放功能网元再将指示信息#4转发给用户面网元。
可选地，若应用功能网元在先没有向用户面网元发送业务流描述信息#4，且指示信息#4不是业务流描述信息#2，则在S313中，应用功能网元向用户面网元发送业务流描述信息#2和指示信息#4。
S314，用户面网元向会话管理网元发送指示信息#5。相应地，会话管理网元接收来自用户面网元的指示信息#5。
该指示信息#5用于指示对目标待监测业务流进行网络状态监测。或者该指示信息#5用于指示会话管理网元生成目标待监测业务流的监测配置信息。指示信息#5的形式可以参考指示信息#2的形式的描述。
示例性地，用户面网元通过N4消息向会话管理网元发送指示信息#5。即用户面网元向会话管理网元发送N4消息，N4消息包括指示信息#5。
可选地，若指示信息#5不是业务流描述信息#2，则在S314中，用户面网元可以向会话管理网元发送业务流描述信息#2和指示信息#5。
S320，会话管理网元确定上行业务流#1的标识。
会话管理网元根据对目标待监测业务流进行网络状态监测的指示信息(即上述指示信息#3或指示信息#5)确定上行业务流#1的标识。会话管理网元在接收到指示信息#3或指示信息#5的情况下，响应于指示信息#3或指示信息#5确定用于传输目标待监测业务流的网络状态信息的上行业务流#1，并确定上行业务流#1的标识。
示例性地，会话管理网元响应于指示信息#3或指示信息#5，根据业务流描述信息#2确定上行业务流#1。也就是说，会话管理网元先根据业务流描述信息#2确定目标待监测业务流，再为目标待监测业务流确定上行业务流#1。
示例性地，若目标待监测业务流是下行业务流，会话管理网元可以将与目标待监测业务流对应的同一个业务的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。其中，该与目标待监测业务流对应的同一个业务的上行业务流可以是业务流描述信息#2对应的业务流，也可以是满足业务流描述信息#2中部分描述信息对应的 业务流。例如，若业务流描述信息#2是目标待监测业务流的IP五元组，则与目标待监测业务流对应同一个业务的上行业务流满足该IP五元组，或者，满足该IP五元组中的三元组。当然，会话管理网元也可以将与目标待监测业务流对应不同业务的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
又示例性地，若目标待监测业务流是上行业务流，会话管理网元可以将目标待监测业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。或者，会话管理网元也可将与目标待监测业务流对应不同业务的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
再示例性地，会话管理网元可以将不用于传输任何网络状态信息的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
再示例性地，若目标待监测业务流的优先级较高，会话管理网元可以将发送频率较高的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。相应地，当通过该发送频率高的上行业务流#1发送目标待监测业务流的网络状态信息时，接入网设备可以快速将目标待监测业务流的网络状态信息发送给用户面网元。
再示例性地，会话管理网元可以将与目标待监测业务流对应同一个QoS流的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
会话管理网元根据确定的上行业务流#1确定上行业务流#1的标识。
可选地，若会话管理网元没有确定目标待监测业务流的监测配置信息，则在S320中，会话管理网元还确定目标待监测业务流的监测配置信息。会话管理网元确定目标待监测业务流的监测配置信息的方法包括：会话管理网元接收来自策略控制网元的目标待监测业务流的监测配置策略；会话管理网元根据监测配置策略确定目标待监测业务流的监测配置信息。其中，目标待监测业务流的监测配置策略包括目标待监测业务流的标识和监测参数。可选地，目标待监测业务流的监测配置策略还包括上报目标待监测业务流的网络状态信息的触发条件。可选地，目标待监测业务流的监测配置信息还可以包括用于指示订阅目标待监测业务流的网络状态信息的事件标识。可选地，目标待监测业务流的监测配置信息还包括上报目标待监测业务流的网络状态信息的方式。也就是说，会话管理网元可以从目标待监测业务流的监测配置策略中提取出目标待监测业务流的监测配置信息。或者可以说，目标待监测业务流的监测配置信息是由策略控制网元发送给会话管理网元的。
示例性地，若方法300执行了S312，且在S312中，策略控制网元向会话管理网元发送了目标待监测业务流的监测配置策略，则在S320中，会话管理网元根据目标待监测业务流的监测配置策略确定目标待监测业务流的监测配置信息。示例性地，若会话管理网元没有获取到目标待监测业务流的监测配置策略，则会话管理网元向策略控制网元发送策略请求消息，以请求目标待监测业务流的监测配置策略；会话管理网元从策略控制网元接收到目标待监测业务流的监测配置策略之后，则根据目标待监测业务流的监测配置策略确定目标待监测业务流的监测配置信息。更多关于目标待监测业务流的监测配置信息的描述可以参考上文S220。
S330，会话管理网元向接入网设备发送目标待监测业务流的监测配置信息和上行业务流#1的标识。相应地，接入网设备接收来自会话管理网元的目标待监测业务流的监测配置信息和上行业务流#1的标识。
接入网设备接收到目标待监测业务流的监测配置信息和上行业务流#1的标识之后，可以确定上行业务流#1用于传输目标待监测业务流的网络状态信息。
示例性地，会话管理网元通过N2会话管理消息(N2session management message，N2SM message)向接入网设备发送上行业务流#1的标识和目标待监测业务流的监测配置信息。其中N2SM消息可以具体对应接入网设备与接入和移动性管理功能网元之间的任何N2消息，如下行非接入层(non-access stratum，NAS)传输消息(DL NAS Transport)，在此不做限定，该N2SM消息由会话管理网元发往接入和移动性管理功能网元，并由接入和移动性管理功能网元通过N2消息发往接入网设备侧。
可选地，会话管理网元向接入网设备发送目标待监测业务流的监测配置信息和上行业务流#1的标识，包括：会话管理网元向接入网设备发送目标待监测业务流的监测配置信息、上行业务流#1的标识和目标待监测业务流的标识。
可选地，方法300还包括：会话管理网元向接入网设备发送指示信息#1。相应地，接入网设备根据指示信息#1确定上行业务流#1用于传输目标待监测业务流的网络状态信息，即接入网设备根据指示信息#1将目标待监测业务流的网络状态信息放到上行业务流#1中进行传输。关于指示信息#1的描述可以参考S210中的描述。
S340，会话管理网元向用户面网元发送上行业务流#1的标识。相应地，用户面网元接收来自会话管理网元的上行业务流#1的标识。
示例性地，若网络仅对目标待监测业务流的网络状态进行监测，则用户面网元接收到上行业务流#1的标识之后，可以确定上行业务流#1用于传输目标待监测业务流的网络状态信息。例如，用户面网元从会话管理网元接收到目标待监测业务流的标识与上行业务流#1的标识，从而明确该上行业务流#1用于传输目标待监测业务流的网络状态信息。
示例性地，会话管理网元通过N4会话修改(N4 session modification)消息向用户面网元发送上行业务流#1的标识。
可选地，会话管理网元向用户面网元发送上行业务流#1的标识，包括：会话管理网元向用户面网元发送上行业务流#1的标识和/或目标待监测业务流的标识。进一步地，若用户面网元已知网络将对目标待监测业务流的网络状态进行监测，用户面网元接收到上行业务流#1的标识和/或目标待监测业务流的标识之后，可以确定上行业务流#1用于传输目标待监测业务流的网络状态信息。
可选地，方法300还包括：会话管理网元向用户面网元发送用于传输目标待监测业务流的网络状态信息的上行业务流#1的指示信息。
需要说明的是，会话管理网元可以将上行业务流#1的标识和指示信息#1携带在同一条消息中发送给用户面网元，或者，会话管理网元可以将上行业务流#1的标识和指示信息#1携带在不同的消息中发送给用户面网元。还需要说明的是，用户面网元根据指示信息#1确定上行业务流#1用于传输目标待监测业务流的网络状态信息，相当于用户面网元根据指示信息#1将上行业务流#1上传输的网络状态信息确定为目标待监测业务流的网络状态信息。
进一步的，会话管理网元还可以向用户面网元发送目标待监测业务流的监测配置信息。
S350，接入网设备得到目标待监测业务流的网络状态信息。
更多关于S350的描述可以参考上文S230，为了简洁，此处不再详述。
S360，接入网设备向用户面网元发送上行数据包。相应地，用户面网元接收来自接入网设备的上行数据包。
其中，上行数据包是用于传输目标待监测业务流的网络状态信息的上行业务流#1中的数据包，即上行数据包包括上行业务流#1的标识。
更多关于S360的描述可以参考上文S240，为了简洁，此处不再详述。
S370，用户面网元确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。
更多关于S370的描述可以参考上文S250，为了简洁，此处不再详述。
可选地，方法300还包括S380，用户面网元发送目标待监测业务流的网络状态信息。
一种可能的实现方式中，S380包括S381和S382。
S381，应用功能网元向用户面网元发送订阅请求消息。相应地，用户面网元接收来自应用功能网元的订阅请求消息。
订阅请求消息用于请求目标待监测业务流的网络状态信息，和/或，用于指示获取目标待监测业务流的网络状态信息。示例性地，订阅请求消息包括业务流描述信息#2或者目标待监测业务流的标识、和/或订阅请求消息包括事件标识，事件标识的描述可以参考上文S210。
示例性地，应用功能网元可以调用UPF服务化接口-订阅(Nupf_subscribe)服务接口向用户面网元发送订阅请求消息。
又示例性地，应用功能网元将订阅请求消息发送给网络开放功能网元，再由网络开放功能网元将订阅请求消息转发给用户面网元。
需要说明的是，S381为可选步骤，若方法300没有执行S313与S314，那么方法300执行S381，否则方法300可以不执行S381，即S381与S313可以是同一个步骤。
S382，用户面网元向应用功能网元发送目标待监测业务流的网络状态信息。相应地，应用功能网元接收目标待监测业务流的网络状态信息。
用户面网元响应于订阅请求消息，或者，用户面网元在确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息之后，向应用功能网元发送目标待监测业务流的网络状态信息。
示例性地，用户面网元可以调用UPF服务化接口-通知(Nupf_notify)服务接口向应用功能网元发送目标待监测业务流的网络状态信息。
又示例性地，用户面网元可以将目标待监测业务流的网络状态信息发送给网络开放功能网元，网络开放功能网元再将目标待监测业务流的网络状态信息转发给应用功能网元。
另一种可能的实现方式中，S380仅包括S382。也就是说，用户面网元在接收到目标待监测业务流的网络状态信息之后，将目标待监测业务流的网络状态信息发送给应用功能网元。
再一种可能的实现方式中，S380包括S383和S385。
S383，用户面网元根据拥塞信息在至少一个上行数据包中添加显示拥塞通知(explicit congestion notification，ECN)标识。
若目标待监测业务流的网络状态信息包括拥塞信息，则用户面网元可以根据拥塞信息 在至少一个上行数据包中添加ECN标识。示例性地，用户面网元在至少一个上行数据包的IP头部(例如IP版本4(IP version 4，IPv4)头部或IP版本6(IP version 6，IPv6)头部)添加ECN标识。
图4示出了至少一个上行数据包的IPv4头部格式。如图4所示，至少一个上行数据包的IPv4头部包括如下内容：版本(version)、网际头部长度(Internet header length，IHL)、差分服务代码点(differentiated service code point，DSCP)、ECN、数据包总长度(total length)、数据包标识(identification)、标志(flags)、片位移(fragment offset)、生存时间(time to live)、协议(protocol)、头部校验和(header checksum)、源IP地址、目的IP地址和可选(options)字段(如果IHL＞5)。
需要说明的是，该至少一个上行数据包是目标上行业务流中的数据包，目标上行业务流与目标待监测业务流对应相同的业务。可以理解，若目标待监测业务流是上行业务流，则目标上行业务流是目标待监测业务流。还需要说明的是，该至少一个上行数据包包括单位时长内发送的上行数据包，例如，该单位时长是1秒、1分钟或1小时等，在此不做限定。或者，该至少一个上行数据包包括预设数量的上行数据包，例如，该预设数量是20、50或100等，在此不做限定。
示例性地，用户面网元可以根据拥塞信息在至少一个上行数据包中概率性添加ECN标识，即用户面网元在至少一个上行数据包中添加ECN标识的概率是根据拥塞信息确定的。例如，若用户面网元根据拥塞信息确定目标待监测业务流没有发生拥塞，则用户面网元在至少一个上行数据包中每个数据包都不添加ECN标识。又例如，若用户面网元根据拥塞信息确定目标待监测业务流发生拥塞，则用户面网元可以在至少一个上行数据包中的每一个上行数据包中添加ECN标识。再例如，若用户面网元根据拥塞信息确定目标待监测业务流的拥塞程度是60％，则用户面网元随机地在目标上行业务流的数据包中的60％个上行数据包中添加ECN标识。
可选地，用户面网元也可以根据目标待监测业务流的传输时延、发送队列长度、可用带宽或丢包率，在至少一个上行数据包中添加ECN标识。
以用户面网元根据发送队列长度在至少一个上行数据包中添加ECN标识为例，若用户面网元确定目标待监测业务流的发送队列长度超过发送队列长度阈值，则用户面网元可以在至少一个上行数据包中的每一个上行数据包中添加ECN标识。或者，用户面网元根据目标待监测业务流的发送队列长度与发送队列长度阈值的比值，确定添加ECN标识的上行数据包的数量。例如，若目标待监测业务流的发送队列长度与发送队列长度阈值的比值是50％，则用户面网元在至少一个上行数据包中的50％个上行数据包中添加ECN标识。
S385，用户面网元向应用服务器发送至少一个上行数据包。相应地，应用服务器接收来自用户面网元的至少一个上行数据包。
应用服务器(application server，AS)接收到至少一个上行数据包之后，可以根据至少一个上行数据包中包括ECN标识的上行数据包的数量与至少一个上行数据包的数量的比值，确定目标待监测业务流的拥塞程度。其中，至少一个上行数据包包括AS在单位时长内接收到的上行数据包，或者，至少一个上行数据包包括预设数量的上行数据包。
例如，以至少一个上行数据包是AS在一分钟内接收到的上行数据包为例，若AS在一分钟内接收到的每个上行数据包都包括ECN标识，则应用服务器确定目标待监测业务 流发生了拥塞。又例如，若AS在一分钟内接收到的每个上行数据包都不包括ECN标识，则应用服务器确定目标待监测业务流没有发生拥塞。再例如，若AS在一分钟内接收到的上行数据包中60％的上行数据包包括ECN标识，则应用服务器确定目标待监测业务流的拥塞程度是60％。需要说明的是，若用户面网元通过概率性添加ECN标识的方式进行网络状态信息反馈，则应用服务器会提前与终端设备或网络侧进行协商，从而确定用户面网元将通过概率性添加ECN标识的方式反馈网络状态信息。
可选地，应用服务器也可以根据至少一个上行数据包中包括ECN标识的上行数据包的数量与至少一个上行数据包的数量的比值，确定目标待监测业务流的传输时延、丢包率、可用带宽或发送队列长度。
以应用服务器根据至少一个上行数据包中包括ECN标识的上行数据包的数量与至少一个上行数据包的数量的比值，确定目标待监测业务流的发送队列长度为例，若应用服务器确定至少一个上行数据包中每一个上行数据包都包括ECN标识，则应用服务器确定目标待监测业务流的发送队列长度超过发送队列长度阈值。又例如，若应用服务器确定至少一个上行数据包中60％的上行数据包包括ECN标识，则应用服务器确定目标待监测业务的发送队列长度是发送队列长度阈值的60％。
再一种可能的实现方式中，S380包括S384和S385。
S384，用户面网元在至少一个上行数据包的IP层或传输控制协议(transmission control protocol，TCP)层或用户数据协议(user datagram protocol，UDP)层或其他层等添加目标待监测业务流的网络状态信息。
以用户面网元在至少一个上行数据包的IP层添加目标待监测业务流的网络状态信息为例，用户面网元可以通过IP头部的可选字段携带目标待监测业务流的网络状态信息。
S385，用户面网元向应用服务器发送至少一个上行数据包。
相应地，应用服务器通过解析至少一个上行数据包的IP成或TCP层或UDP层或其他层，获得目标待监测业务流的网络状态信息。
在本申请实施例中，会话管理网元根据对目标待监测业务流进行网络状态监测的指示信息确定用于传输目标待监测业务流的网络状态信息的上行业务流#1的标识，并将上行业务流#1的标识分别发送给接入网设备和用户面网元，从而接入网设备可以根据上行业务流#1的标识确定通过上行业务流#1向用户面网元发送目标待监测业务流的网络状态信息，以及用户面网元可以根据上行业务流#1的标识确定通过上行业务流#1接收的上行数据包包括目标待监测业务流的网络状态信息。
图5示出了本申请实施例提供的通信方法的示意性流程图。具体地，与图3中的方法相比，图5示出了方法200提及的由策略控制网元确定用于传输目标待监测业务流的网络状态信息的上行业务流#1的标识的实施例的方法流程，下面详细描述方法500包括的各个步骤。
S510，策略控制网元接收用于指示对目标待监测业务流进行网络状态监测的指示信息。
一种可能的实现方式中，S510包括S511。
S511，应用功能网元向策略控制网元发送指示信息#2。相应地，策略控制网元接收来自应用功能网元的指示信息#2。
更多关于S511的描述可以参考上文S311，为了简洁，此处不再详述。
另一种可能的实现方式中，S510包括S512至S514。
S512，应用功能网元向用户面网元发送指示信息#4。相应地，用户面网元接收来自应用功能网元的指示信息#4。
更多关于S512的描述可以参考上文S313，为了简洁，此处不再详述。
S513，用户面网元向会话管理网元发送指示信息#5。相应地，会话管理网元接收来自用户面网元的指示信息#5。
更多关于S513的描述可以参考上文S314，为了简洁，此处不再详述。
S514，会话管理网元向策略控制网元发送指示信息#6。相应地，策略控制网元接收来自会话管理网元的指示信息#6。
该指示信息#6用于指示对目标待监测业务流进行网络状态监测。或者，指示信息#6也可以用于指示确定用于传输目标待监测业务流的上行业务流#1的标识。指示信息#6的形式可以参考上文S311中描述的指示信息#2的形式。
可选地，若指示信息#6不是业务流描述信息#2，且会话管理网元从用户面网元接收到业务流描述信息#2，则在S514中，会话管理网元向策略控制网元发送指示信息#6和业务流描述信息#2。
S520，策略控制网元确定上行业务流#1的标识。
策略控制网元根据对目标待监测业务流进行网络状态监测的指示信息(即上文的指示信息#2或指示信息#6)确定上行业务流#1的标识。策略控制网元在接收到指示信息#2或指示信息#6的情况下，响应于指示信息#2或指示信息#6确定用于传输目标待监测业务流的网络状态信息的上行业务流#1。
示例性地，策略控制网元响应于指示信息#2或指示信息#6，根据业务流描述信息#2确定上行业务流#1。也就是说，策略控制网元先根据业务流描述信息#2确定目标待监测业务，再为目标待监测业务流确定上行业务流#1。
示例性地，若目标待监测业务流是下行业务流，策略控制网元可以将与目标待监测业务对应的同一个业务的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。与目标待监测业务流对应的同一个业务的上行业务流的描述可以参考上文S320。当然，策略控制网元也可以将与目标待监测业务流对应不同业务的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
又示例性地，若目标待监测业务流是上行业务流，策略控制网元可以将目标待监测业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。或者，策略控制网元也可将与目标待监测业务流对应不同业务的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
再示例性地，策略控制网元可以将不用于传输任何网络状态信息的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
再示例性地，若目标待监测业务流的优先级较高，策略控制网元可以将发送频率较高的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。相应地，当通过该发送频率高的上行业务流#1发送目标待监测业务流的网络状态信息时，接入网设备可以快速将目标待监测业务流的网络状态信息发送给用户面网元。
再示例性地，策略控制网元可以将与目标待监测业务流对应同一个QoS流的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
策略控制网元根据上行业务流#1确定上行业务流#1的标识。
S530，策略控制网元向会话管理网元发送目标待监测业务流的监测配置信息和上行业务流#1的标识。相应地，会话管理网元接收来自策略控制网元的目标待监测业务流的监测配置信息和上行业务流#1的标识。
需要说明是，策略控制网元以目标待监测业务流的监测配置策略的形式向会话管理网元发送目标待监测业务流的监测配置信息。也就是说，策略控制网元向会话管理网元发送目标待监测业务流的监测配置策略，目标待监测业务流的监测配置策略包括用于组成目标待监测业务流的监测配置信息的参数。其中，策略控制网元可以根据指示信息#2或指示信息#6生成目标待监测业务流的监测配置策略，更多关于目标待监测业务流的监测配置信息和监测配置策略的描述，可以参考上文S220。
S540，会话管理网元向接入网设备发送目标待监测业务流的监测配置信息和上行业务流#1的标识。相应地，接入网设备接收来自会话管理网元的目标待监测业务流的监测配置信息和上行业务流#1的标识。
更多关于S540的描述可以参考上文S330，为了简洁，此处不再详述。
S550，会话管理网元向用户面网元发送上行业务流#1的标识。相应地，用户面网元接收来自会话管理网元的上行业务流#1的标识。
更多关于S550的描述可以参考上文S340，为了简洁，此处不再详述。
S560，接入网设备得到目标待监测业务流的网络状态信息。
更多关于S560的描述可以参考上文S230，为了简洁，此处不再详述。
S570，接入网设备向用户面网元发送上行数据包。相应地，用户面网元接收来自接入网设备的上行数据包。
其中，上行数据包是用于传输目标待监测业务流的网络状态信息的上行业务流#1中的数据包，即上行数据包包括上行业务流#1的标识。
更多关于S570的描述可以参考上文S240，为了简洁，此处不再详述。
S580，用户面网元确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。
更多关于S580的描述可以参考上文S250，为了简洁，此处不再详述。
可选地，方法500还包括S590，用户面网元发送目标待监测业务流的网络状态信息。更多关于S590的描述可以参考上文S380，为了简洁，此处不再详述。
在本申请实施例中，策略控制网元根据对目标待监测业务流进行网络状态监测的指示信息确定用于传输目标待监测业务流的网络状态信息的上行业务流#1的标识，并将上行业务流#1的标识发送给会话管理网元，使得会话管理网元可以将上行业务流#1的标识发送给接入网设备和用户面网元，从而接入网设备可以根据上行业务流#1的标识确定通过上行业务流#1向用户面网元发送目标待监测业务的网络状态信息，以及用户面网元可以根据上行业务流#1的标识确定通过上行业务流#1接收的上行数据包包括目标待监测业务流的网络状态信息。
图6示出了本申请实施例提供的通信方法的示意性流程图。具体地，与图3和图5中 的方法相比，图6示出了方法200提及的由用户面网元确定用于传输目标待监测业务流的网络状态信息的上行业务流#1的标识的实施例的方法流程，下面详细描述方法600包括的各个步骤。
S610，应用功能网元向用户面网元发送指示信息#4。相应地，用户面网元接收来自应用功能网元的指示信息#4。
更多关于S610的描述可以参考上文S313，为了简洁，此处不再详述。
S620，用户面网元确定上行业务流#1的标识。
用户面网元根据指示信息#4确定上行业务流#1的标识，也就是说，用户面网元在接收到指示信息#4的情况下，响应于指示信息#4确定用于传输目标待监测业务流的网络状态信息的上行业务流#1，并确定上行业务流#1的标识。
示例性地，用户面网元响应于指示信息#4，根据业务流描述信息#2确定上行业务流#1。也就是说，用户面网元先根据业务流描述信息#2确定目标待监测业务流，再为目标待监测业务流确定上行业务流#1。
示例性地，若目标待监测业务流是下行业务流，用户面网元可以将与目标待监测业务流对应的同一个业务的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。与目标待监测业务流对应的同一个业务的上行业务流的描述可以参考上文S320。当然，用户面网元也可以将与目标待监测业务流对应不同业务的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
又示例性地，若目标待监测业务流是上行业务流，用户面网元可以将目标待监测业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。或者，用户面网元也可将与目标待监测业务流对应不同业务的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
再示例性地，用户面网元可以将不用于传输任何网络状态信息的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。
再示例性地，若目标待监测业务流的优先级较高，用户面网元可以将发送频率较高的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。相应地，当通过该发送频率高的上行业务流#1发送目标待监测业务流的网络状态信息时，接入网设备可以快速将目标待监测业务流的网络状态信息发送给用户面网元。
再示例性地，用户面网元可以将与目标待监测业务流对应同一个QoS流的上行业务流确定为用于传输目标待监测业务流的网络状态信息的上行业务流#1。需要说明的是，用户面网元可以根据在先从会话管理网元接收的包检测规则(packet detection rule，PDR)确定目标待监测业务流所对应的第一QoS流。
用户面网元根据确定的上行业务流#1确定上行业务流#1的标识。
S630，用户面网元向接入网设备发送目标待监测业务流的监测配置信息和上行业务流#1的标识。相应地，接入网设备接收来自用户面网元的目标待监测业务流的监测配置信息和上行业务流#1的标识。
示例性地，用户面网元将目标待监测业务流的监测配置信息和上行业务流#1的标识携带在下行数据包的GTP-U层，发送给接入网设备。示例性地，下行数据包是目标待监测业务流中的数据包。
再示例性地，用户面网元将目标待监测业务流的监测配置信息和上行业务流#1的标识发送给会话管理网元，会话管理网元再将目标待监测业务流的监测配置信息和上行业务流#1的标识转发给接入网设备。
可选地，用户面网元向接入网设备发送目标待监测业务流的监测配置信息和上行业务流#1的标识，包括：用户面网元向接入网设备发送目标待监测业务流的监测配置信息、上行业务流#1的标识和目标待监测业务流的标识。
可选地，方法600还包括：用户面网元向接入网设备发送指示信息#1。相应地，接入网设备根据指示信息#1确定上行业务流#1用于传输目标待监测业务流的网络状态信息。关于指示信息#1的描述可以参考上文S210。
S640，接入网设备得到目标待监测业务流的网络状态信息。
更多关于S640的描述可以参考上文S230，为了简洁，此处不再详述。
S650，接入网设备向用户面网元发送上行数据包。相应地，用户面网元接收来自接入网设备的上行数据包。
其中，上行数据包是用于传输目标待监测业务流的网络状态信息的上行业务流#1中的数据包，即上行数据包包括上行业务流#1的标识。
更多关于S650的描述可以参考上文S240，为了简洁，此处不再详述。
S660，用户面网元确定上行数据包包括的网络状态信息是目标待监测业务流的网络状态信息。
更多关于S660的描述可以参考上文S250，为了简洁，此处不再详述。
可选地，方法600还包括S670，用户面网元发送目标待监测业务流的网络状态信息。更多关于S670的描述可以参考上文S380，为了简洁，此处不再详述。
在本申请实施例中，用户面网元根据指示信息#4确定用于传输目标待监测业务流的网络状态信息的上行业务流#1的标识，并将上行业务流#1的标识发送给接入网设备，使得接入网设备可以根据上行业务流#1的标识确定通过上行业务流#1向用户面网元发送目标待监测业务流的网络状态信息。
图7是本申请实施例提供的通信装置1000的示意性框图。如图7所示，该通信装置1000可以包括：收发单元1010和处理单元1020。
在一种可能的设计中，该通信装置1000可以是上文方法实施例中的接入网设备，也可以是用于实现上文方法实施例中接入网设备的功能的芯片。
应理解，该通信装置1000可对应于本申请实施例方法200、方法300、方法500或方法600中的接入网设备，该通信装置1000可以包括用于执行图2中的方法200、图3中的方法300、图5中的方法500或图6中的方法600中的接入网设备执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图2中的方法200、图3中的方法300、图5中的方法500或图6中的方法600的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该通信装置1000可以是上文方法实施例中的用户面网元，也可以是用于实现上文方法实施例中用户面网元的功能的芯片。
应理解，该通信装置1000可对应于本申请实施例方法200、方法300、方法500或方 法600中的用户面网元，该通信装置1000可以包括用于执行图2中的方法200、图3中的方法300、图5中的方法500或图6中的方法600中的用户面网元执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图2中的方法200、图3中的方法300、图5中的方法500或图6中的方法600的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该通信装置1000可以是上述方法实施例中的会话管理网元，也可以是用于实现上文方法实施例中会话管理网元的功能的芯片。
应理解，该通信装置1000可对应于本申请实施例方法200、方法300、方法500或方法600中的会话管理网元，该通信装置1000可以包括用于执行图2中的方法200、图3中的方法300、图5中的方法500或图6中的方法600中的会话管理网元执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图2中的方法200、图3中的方法300、图5中的方法500或图6中的方法600的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该通信装置1000可以是上述方法实施例中的策略控制网元，也可以是用于实现上文方法实施例中策略控制网元的功能的芯片。
应理解，该通信装置1000可对应于本申请实施例方法200、方法300、方法500或方法600中的策略控制网元，该通信装置1000可以包括用于执行图2中的方法200、图3中的方法300、图5中的方法500或图6中的方法600中的策略控制网元执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图2中的方法200、图3中的方法300、图5中的方法500或图6中的方法600的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信装置1000中的收发单元1010可对应图8中示出的通信设备2000中的收发器2020，该通信装置1000中的处理单元1020可对应于图8中示出的通信设备2000中的处理器2010。
还应理解，当该通信装置1000为芯片时，该芯片包括收发单元。可选地，该芯片还可以包括处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或微处理器或者集成电路。
收发单元1010用于实现通信装置1000的信号的收发操作，处理单元1020用于实现通信装置1000的信号的处理操作。
可选地，该通信装置还包括存储单元1030，该存储单元1030用于存储指令。
图8是本申请实施例提供的通信设备2000的示意性框图。如图8所示，该通信设备2000包括：至少一个处理器2010和收发器2020。该处理器2010与存储器耦合，用于执行存储器中存储的指令，以控制收发器2020发送信号和/或接收信号。可选地，该通信设备2000还包括存储器2030，用于存储指令。
应理解，上述处理器2010和存储器2030可以合成一个处理装置，处理器2010用于执行存储器2030中存储的程序代码来实现上述功能。具体实现时，该存储器2030也可以 集成在处理器2010中，或者独立于处理器2010中。
还应理解，收发器2020可以包括接收器(或者称，接收机)和发射器(或者称，发射机)。收发器2020还可以进一步包括天线，天线的数量可以为一个或多个。收发器2020又可以是天线接口或者接口电路。
当该通信设备2000为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或者微处理器或者集成电路。
图9是本申请实施例的一种芯片***的示意图。这里的芯片***也可为电路组成的***。图9所示的芯片***3000包括：逻辑电路3010以及输入/输出接口(input/output interface)3020，所述逻辑电路用于与输入接口耦合，通过所述输入/输出接口传输数据，以执行图2、图3、图5或图6所述的方法。
本申请实施例还提供了一种处理装置，包括处理器和接口。所述处理器可用于执行上述方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是***芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以执行体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机寄存器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤，为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行图 2、图3、图5和图6所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读存储介质，该计算机可读存储介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图2、图3、图5和图6所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种***，其包括前述的接入网设备和用户面网元。可选地，该***还包括前述的会话管理网元。可选地，该***还包括前述的策略控制网元。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现，当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
在本申请所提及的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其他的形式。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种通信方法，其特征在于，包括：
    接入网设备接收目标待监测业务流的监测配置信息和上行业务流的标识，所述监测配置信息用于监测所述目标待监测业务流的网络状态，所述上行业务流用于传输所述目标待监测业务流的网络状态信息；
    所述接入网络设备根据所述目标待监测业务流的监测配置信息进行网络状态监测以得到所述目标待监测业务流的网络状态信息；
    所述接入网设备向用户面网元发送上行数据包，所述上行数据包包括所述目标待监测业务流的网络状态信息和所述上行业务流的标识。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收用于传输所述目标待监测业务流的网络状态信息的所述上行业务流的指示信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述接入网设备接收目标待监测业务流的监测配置信息和上行业务流的标识，包括：
    所述接入网设备接收所述目标待监测业务流的监测配置信息、所述目标待监测业务流的标识和所述上行业务流的标识。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述上行数据包还包括所述目标待监测业务流的标识。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，
    所述目标待监测业务流为第一服务质量QoS流，所述上行业务流为第二QoS流中的上行业务流；或者，
    所述目标待监测业务流为第一QoS流中的下行业务流，所述上行业务流为第二QoS流中的上行业务流；或者，
    所述目标待监测业务流为第一QoS流中的上行业务流，所述上行业务流为第二QoS流中的上行业务流。
  6. 一种通信方法，其特征在于，包括：
    用户面网元获取上行业务流的标识，所述上行业务流用于传输目标待监测业务流的网络状态信息；
    所述用户面网元接收上行数据包，所述上行数据包包括所述上行业务流的标识和网络状态信息；
    所述用户面网元根据所述上行业务流的标识确定所述上行数据包包括的网络状态信息是所述目标待监测业务流的网络状态信息。
  7. 根据权利要求6所述的方法，其特征在于，所述上行业务流用于传输多个待监测业务流中各待监测业务流的网络状态信息，所述多个待监测业务流包括所述目标待监测业务流，所述上行数据包还包括所述目标待监测业务流的标识，所述用户面网元根据所述上行业务流的标识确定所述上行数据包包括的网络状态信息是所述目标待监测业务流的网络状态信息，包括：
    所述用户面网元根据所述上行数据包中的所述目标待监测业务流的标识和所述上行业务流的标识，确定所述上行数据包包括的网络状态信息是所述目标待监测业务流的网络状态信息。
  8. 根据权利要求6或7所述的方法，其特征在于，所述用户面网元获取上行业务流的标识，包括：
    所述用户面网元从会话管理网元接收所述上行业务流的标识。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述用户面网元从所述会话管理网元接收用于传输所述目标待监测业务流的网络状态信息的所述上行业务流的指示信息。
  10. 根据权利要求8或9所述的方法，其特征在于，所述用户面网元从会话管理网元接收所述上行业务流的标识，包括：
    所述用户面网元从所述会话管理网元接收所述上行业务流的标识和所述目标待监测业务流的标识。
  11. 根据权利要求8至10中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元从应用功能网元接收获取所述目标待监测业务流的网络状态信息的指示信息；
    所述用户面网元向所述会话管理网元发送对所述目标待监测业务流进行网络状态监测的指示信息。
  12. 根据权利要求6或7所述的方法，其特征在于，所述用户面网元获取上行业务流的标识，包括：
    所述用户面网元从应用功能网元接收获取所述目标待监测业务流的网络状态信息的指示信息；
    所述用户面网元根据所述获取所述目标待监测业务流的网络状态信息的指示信息确定所述上行业务流的标识；
    所述方法还包括：
    所述用户面网元向所述接入网设备发送所述目标待监测业务流的监测配置信息和所述上行业务流的标识，所述监测配置信息用于监测所述目标待监测业务流的网络状态。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述用户面网元向所述接入网设备发送用于传输所述目标待监测业务流的网络状态信息的所述上行业务流的指示信息。
  14. 根据权利要求6至13中任一项所述的方法，其特征在于，
    所述目标待监测业务流为第一服务质量QoS流，所述上行业务流为第二QoS流中的上行业务流，或者；
    所述目标待监测业务流为第一QoS流中的下行业务流，所述上行业务流为第二QoS流中的上行业务流，或者；
    所述目标待监测业务流为第一QoS流中的上行业务流，所述上行业务流为第二QoS流中的上行业务流。
  15. 根据权利要求6至14中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元发送所述目标待监测业务流的网络状态信息。
  16. 根据权利要求15所述的方法，其特征在于，所述目标待监测业务流的网络状态信息包括所述目标待监测业务流的拥塞状况，所述用户面网元发送所述目标待监测业务流的网络状态信息，包括：
    所述用户面网元发送目标上行业务流中的至少一个上行数据包，所述至少一个上行数据包中携带显示拥塞通知ECN标识的数据包的数量与所述至少一个上行数据包的数量的比值用于确定所述目标待监测业务流的拥塞状况，所述目标上行业务流与所述目标待监测业务流对应相同的业务。
  17. 一种通信方法，其特征在于，包括：
    接收对目标待监测业务流进行网络状态监测的指示信息；
    根据所述对所述目标待监测业务流进行网络状态监测的指示信息确定上行业务流的标识，所述上行业务流用于传输所述目标待监测业务流的网络状态信息；
    发送所述目标待监测业务流的监测配置信息和所述上行业务流的标识。
  18. 根据权利要求17所述的方法，其特征在于，所述发送所述目标待监测业务流的监测配置信息和所述上行业务流的标识，包括：
    向会话管理网元发送所述目标待监测业务流的监测配置信息和所述上行业务流的标识。
  19. 根据权利要求17所述的方法，其特征在于，所述发送所述目标待监测业务流的监测配置信息和所述上行业务流的标识，包括：
    向接入网设备和用户面网元发送所述目标待监测业务流的监测配置信息和所述上行业务流的标识。
  20. 根据权利要求17至19中任一项所述的方法，其特征在于，所述方法还包括：
    发送用于传输所述目标待监测业务流的网络状态信息的所述上行业务流的指示信息。
  21. 根据权利要求17至20中任一项所述的方法，其特征在于，所述发送所述目标待监测业务流的监测配置信息和所述上行业务流的标识，包括：
    发送所述目标待监测业务流的监测配置信息、所述上行业务流的标识和所述目标待监测业务流的标识。
  22. 根据权利要求17至21中任一项所述的方法，其特征在于，
    所述目标待监测业务流为第一服务QoS流，所述上行业务流为第二QoS流中的上行业务流，或者；
    所述目标待监测业务流为第一QoS流中的下行业务流，所述上行业务流为第二QoS流中的上行业务流，或者；
    所述目标待监测业务流为第一QoS流中的上行业务流，所述上行业务流为第二QoS流中的上行业务流。
  23. 一种通信装置，其特征在于，用于实现如权利要求1至22中任意一项所述的方法。
  24. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合，所述至少一个处理器用于执行所述至少一个存储器中存储的计算机程序或指令，以使所述通信装置执行如权利要求1至22中任一项所述的方法。
  25. 一种芯片，其特征在于，包括处理器和通信接口，所述通信接口用于接收数据和 /或信息，并将接收到的数据和/或信息传输至所述处理器，所述处理器处理所述数据和/或信息，以使得执行如权利要求1至22中任一项所述的方法。
  26. 一种计算机可读存储介质，其特征在于，其上存储有计算机程序，所述计算机程序被执行时，以使得计算机执行如权利要求1至22中任一项所述的方法。
  27. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行如权利要求1至22中任一项所述的方法。
  28. 一种通信方法，其特征在于，包括：
    接入网设备接收目标待监测业务流的监测配置信息和上行业务流的标识，所述监测配置信息用于监测所述目标待监测业务流的网络状态，所述上行业务流用于传输所述目标待监测业务流的网络状态信息；
    所述接入网络设备根据所述目标待监测业务流的监测配置信息进行网络状态监测以得到所述目标待监测业务流的网络状态信息；
    用户面网元接收所述接入网设备发送的上行数据包，所述上行数据包包括所述目标待监测业务流的网络状态信息和所述上行业务流的标识。
  29. 根据权利要求28所述的方法，其特征在于，该方法还包括：
    所述用户面网元获取上行业务流的标识，所述上行业务流用于传输目标待监测业务流的网络状态信息。
  30. 根据权利要求28或29所述的方法，其特征在于，该方法还包括：
    会话管理网元向所述用户面网元发送用于传输所述目标待监测业务流的网络状态信息的上行业务流的指示信息。
PCT/CN2023/080080 2022-03-15 2023-03-07 通信方法及通信装置 WO2023174100A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210252155.9A CN116801297A (zh) 2022-03-15 2022-03-15 通信方法及通信装置
CN202210252155.9 2022-03-15

Publications (1)

Publication Number Publication Date
WO2023174100A1 true WO2023174100A1 (zh) 2023-09-21

Family

ID=88022367

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/080080 WO2023174100A1 (zh) 2022-03-15 2023-03-07 通信方法及通信装置

Country Status (2)

Country Link
CN (1) CN116801297A (zh)
WO (1) WO2023174100A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2991295A1 (en) * 2014-08-27 2016-03-02 Alcatel Lucent System and method for handling data flows in an access network
CN110831033A (zh) * 2018-08-13 2020-02-21 华为技术有限公司 服务质量监测方法、设备及***
CN112188533A (zh) * 2019-07-03 2021-01-05 华为技术有限公司 一种网络性能的上报方法及装置
CN115734179A (zh) * 2021-08-30 2023-03-03 华为技术有限公司 测量网络状态的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2991295A1 (en) * 2014-08-27 2016-03-02 Alcatel Lucent System and method for handling data flows in an access network
CN110831033A (zh) * 2018-08-13 2020-02-21 华为技术有限公司 服务质量监测方法、设备及***
CN112188533A (zh) * 2019-07-03 2021-01-05 华为技术有限公司 一种网络性能的上报方法及装置
CN115734179A (zh) * 2021-08-30 2023-03-03 华为技术有限公司 测量网络状态的方法和装置

Also Published As

Publication number Publication date
CN116801297A (zh) 2023-09-22

Similar Documents

Publication Publication Date Title
TWI754244B (zh) Pdu會話的管理方法和使用者設備
US11968565B2 (en) User plane information reporting method and apparatus
JP7477661B2 (ja) データ伝送方法および装置
WO2020169039A1 (zh) 一种策略管理的方法及装置
WO2019101054A1 (zh) 聚合速率控制方法、设备以及***
JP7494327B2 (ja) 通信方法、装置、およびシステム
US20220182872A1 (en) Temporary priority elevation for non-high priority access users
US20240214864A1 (en) Communication method, apparatus, and system
US12010202B2 (en) Data unit in wireless system
WO2023207970A1 (zh) 通信方法及通信装置
WO2023071770A1 (zh) 获取数据分析结果的方法及通信装置
US20220256395A1 (en) Communication method, apparatus, and system
EP4325929A1 (en) Wireless communication method, communication apparatus and communication system
WO2023174100A1 (zh) 通信方法及通信装置
CN116436862A (zh) 一种通信方法及通信装置
WO2023083138A1 (zh) 用于通信***的电子设备、方法和存储介质
US20240056871A1 (en) Resource allocation status subscription for application related function
WO2024114192A1 (zh) 业务质量管理方法及装置
WO2024032211A1 (zh) 一种拥塞控制方法以及装置
WO2024022158A1 (zh) 通信方法及装置
US20240089795A1 (en) Data Unit Processing
WO2023083153A1 (zh) 获取安全分级结果的方法及通信装置
WO2023016243A1 (zh) 一种用于传输业务的方法和装置
CN116800685A (zh) 通信方法及通信装置
KR20240063563A (ko) 무선 통신 시스템에서 트래픽 특성 변화에 기반하여 정보를 전달하는 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23769606

Country of ref document: EP

Kind code of ref document: A1