WO2021148012A1 - 报告信息的发送方法和通信装置以及通信系统 - Google Patents

报告信息的发送方法和通信装置以及通信系统 Download PDF

Info

Publication number
WO2021148012A1
WO2021148012A1 PCT/CN2021/073400 CN2021073400W WO2021148012A1 WO 2021148012 A1 WO2021148012 A1 WO 2021148012A1 CN 2021073400 W CN2021073400 W CN 2021073400W WO 2021148012 A1 WO2021148012 A1 WO 2021148012A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
qos
candidate
session management
policy
Prior art date
Application number
PCT/CN2021/073400
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 华为技术有限公司
Priority to EP21744326.6A priority Critical patent/EP4080828A4/en
Publication of WO2021148012A1 publication Critical patent/WO2021148012A1/zh
Priority to US17/868,224 priority patent/US20220353746A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403Architecture for metering, charging or billing
    • H04L12/1407Policy-and-charging control [PCC] architecture
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0894Policy-based network configuration management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/32Specific management aspects for broadband networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003Managing SLA; Interaction between SLA and QoS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5032Generating service level reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80Responding to QoS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66Policy and charging system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80Rating or billing plans; Tariff determination aspects
    • H04M15/8016Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82Criteria or parameters used for performing billing operations
    • H04M15/8228Session based
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information

Definitions

  • This application relates to the field of communication technology, and in particular to a method for sending report information, a communication device, and a communication system.
  • UE user equipment
  • PDU protocol data unit
  • the network interacts with the application server deployed in the DN.
  • the session management function session management function, SMF
  • UPF user plane function
  • the application server of the same application can be deployed in multiple locations.
  • SMF can select a UPF that is close to the UE and supports the UE's access to the DN according to the UE's access location, so as to reduce circuitous routes and reduce network delay.
  • these application servers can be deployed in a mobile edge computing (mobile edge computing, MEC) environment.
  • the application needs to perceive the quality of service (QoS) information of the service data stream transmission path in order to perform corresponding adjustments at the application layer.
  • QoS quality of service
  • applications can obtain QoS information in the following ways: application functions (AF) send QoS control notification (control notification) requests to network capability opening functions (network exposure function, NEF), and QoS control notification requests are used to request services.
  • the NEF sends the QoS control notification request to the policy control function (PCF).
  • PCF policy control function
  • the PCF receives the Qos control notification request, it formulates the corresponding QoS policy and sends the QoS policy to the SMF.
  • the SMF executes the QoS policy and generates the execution result.
  • the SMF sends the execution result to the radio access network (RAN) through the access and mobility management function (AMF).
  • RAN radio access network
  • AMF access and mobility management function
  • the RAN can judge the QoS flow (flow) based on the execution result to generate QoS information. For example, when the RAN judges the guaranteed flow bit rate (GFBR) of the QoS flow, when the guaranteed flow bit rate (GFBR) cannot be guaranteed, the RAN sends the following path that cannot be guaranteed by GFBR Notification: RAN->AMF->SMF->PCF->NEF->AF, and finally the AF can receive a notification that GFBR cannot guarantee. After receiving the notification, the AF can perform corresponding adjustments at the application layer.
  • GFBR guaranteed flow bit rate
  • the embodiment of the present application provides a method for sending report information, a communication device, and a communication system, which are used to shorten the transmission path of the reported information and reduce the processing delay of the application function network element.
  • an embodiment of the present application provides a method for sending report information, including: a first session management network element receives first report information from a user plane network element, where the first report information includes first indication information and An identifier of a candidate quality of service QoS document, the first indication information is used to indicate that the QoS requirements of the first quality of service flow QoS Flow cannot be guaranteed; the first session management network element sends second report information to the application function network element , Wherein the second report information includes second indication information and an identifier of the first candidate service requirement, the identifier of the first candidate service requirement corresponds to the identifier of the first candidate QoS document, and the second indication information is used for When indicating that the QoS requirements of the first service data flow cannot be guaranteed, the first QoS Flow is used to transmit the first service data flow, and the first service data flow is the service of the application corresponding to the application function network element data flow.
  • the first session management network element can receive the first report information from the user plane network element, the first report information carries the first indication information and the identifier of the first QoS document, so the first session management network The element can obtain the second indication information according to the first indication information, and can also determine the identification of the first candidate service requirement according to the identification of the first candidate QoS document. Therefore, the first session management network element can generate the second report information.
  • the second report information sent by the network element to the application function management network element indicates that the QoS requirement of the first service data stream cannot be guaranteed through the second indication information in the second report information.
  • the application function network element can determine that the QoS requirements of the first service data flow cannot be guaranteed.
  • the second report information It also carries the identifier of the first candidate service requirement, so that the application function network element can also determine the candidate service requirement, so that the application function network element determines that the QoS requirement of the first service data stream cannot be guaranteed according to the first candidate service requirement Quickly adjust at the application layer. Therefore, the path indicating that the QoS requirements of the first service data flow cannot be guaranteed is greatly shortened.
  • the second report information has high timeliness, which reduces the adjustment of application function network elements at the application layer. Time delay.
  • the second indication information is determined according to the first indication information.
  • the second indication information is generated according to the indication content carried in the first indication information
  • the first indication information indicates that the QoS requirements of the first QoS Flow cannot be guaranteed
  • the first session management network element is based on the first QoS Flow.
  • QoS requirements cannot be guaranteed. It is determined that the QoS requirements of the first service data flow transmitted by the first QoS Flow cannot be guaranteed, and the QoS requirements of the first service data flow carried in the second indication information cannot be guaranteed.
  • the method when the first session management network element is an intermediate session management network element, before the first session management network element receives the first report information from the user plane network element, the method It also includes: the first session management network element receives a first policy from a second session management network element, where the first policy includes an identifier of the first QoS Flow, first QoS notification control indication information, and at least one candidate QoS document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS Document, the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement, and the first QoS notification control indication information is used to indicate whether the QoS requirement for sending the first QoS Flow can be guaranteed Information; the first session management network element determines a second strategy according to the first strategy, and sends the second strategy to the first access network element, wherein
  • the first access network network element can communicate with the first session management network element, and the second policy is received from the first session management network element, and the first access network network element parses the second policy.
  • An access network element can obtain the identification of the first QoS Flow, the second QoS notification control indication information, and at least one candidate QoS document.
  • the second QoS notification control indication information is used to indicate that the QoS requirements for sending the first QoS Flow cannot be obtained.
  • Guaranteed instruction information for example, the second QoS notification control instruction information instructs the first access network element to send the first instruction information to the user plane network element, so that the user plane network element can generate the first report information according to the first instruction information, and Sending the first report information to the first session management network element realizes the rapid reporting of the first report information.
  • the method when the first session management network element is an intermediate session management network element, before the first session management network element receives the first report information from the user plane network element, the method It also includes: the first session management network element receives a first policy from a second session management network element, where the first policy includes an identifier of the first QoS Flow, first QoS notification control indication information, and at least one candidate The QoS document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS Document, the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement, and the first QoS notification control indication information is used to indicate whether the QoS requirement for sending the first QoS Flow can be guaranteed Information; the first session management network element determines a third strategy according to the first strategy, and sends the third strategy to the user plane network element, the
  • the user plane network element can communicate with the first session management network element, and the third policy is received from the first session management network element.
  • the user plane network element analyzes the third policy, and the user plane network element performs communication according to the third policy.
  • the instruction of the policy needs to send the indication information of whether the QoS requirements of the first QoS Flow can be guaranteed. For example, when the user plane network element determines that the QoS requirements of the first QoS Flow cannot be guaranteed, it sends the aforementioned first indication information carrying the first indication information.
  • the first report information realizes the rapid reporting of the first report information.
  • the first session management network element sending the second report information to the application function network element includes: when the first indication information includes the identifier of the first QoS Flow, the The first session management network element determines the notification endpoint of the application function network element according to the identifier of the first QoS Flow, and sends the second report to the application function network element through the notification endpoint of the application function network element information.
  • the first session management network element analyzes the first policy, and can obtain the identification of the first QoS Flow and the notification endpoint information of the application function network element.
  • the first session management network element determines the notification endpoint of the application function network element carried in the first policy according to the identifier of the first QoS Flow carried in the first indication information, and sends the second report information to the notification endpoint, so that the application function network
  • the element may receive the second report information from the first session management network element.
  • the first session management network element may send the second report information to the application function network element through the notification endpoint of the application function network element, thereby realizing the communication between the first session management network element and the application function network element , So that the application function network element can quickly receive the second report information, and adjust the application layer according to the second report information, reducing the transmission delay of the second report information.
  • the method when the first session management network element is an intermediate session management network element, before the first session management network element receives the first report information from the user plane network element, the method It also includes: the first session management network element receives a first policy from a second session management network element, where the first policy includes an identifier of the first QoS Flow, first QoS notification control indication information, and at least one candidate The QoS document, the information of the notification endpoint of the local network capability opening network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS Document, the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement, and the first QoS notification control indication information is used to indicate whether the QoS requirement for sending the first QoS Flow can be guaranteed Information; the first session management network element determines a second policy according to the first policy, and sends the second policy to the first access
  • the first access network network element can communicate with the first session management network element, and the second policy is received from the first session management network element, and the first access network network element parses the second policy.
  • An access network element can obtain the identifier of the first QoS Flow, the second QoS notification control indication information, and at least one candidate QoS document.
  • the second QoS notification control indication information is used to indicate that the QoS requirements for sending the first QoS Flow cannot be obtained.
  • Guaranteed instruction information for example, the second QoS notification control instruction information instructs the first access network element to send the first instruction information to the user plane network element, so that the user plane network element can generate the first report information according to the first instruction information, and Sending the first report information to the first session management network element realizes the rapid reporting of the first report information.
  • the method when the first session management network element is an intermediate session management network element, before the first session management network element receives the first report information from the user plane network element, the method It also includes: the first session management network element receives a first policy from a second session management network element, where the first policy includes an identifier of the first QoS Flow, first QoS notification control indication information, and at least one candidate The QoS document, the information of the notification endpoint of the local network capability opening network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS Document, the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement, and the first QoS notification control indication information is used to indicate whether the QoS requirement for sending the first QoS Flow can be guaranteed Information; the first session management network element determines a third strategy according to the first strategy, and sends the third strategy to the user plane
  • the user plane network element can communicate with the first session management network element, and the third policy is received from the first session management network element.
  • the user plane network element analyzes the third policy, and the user plane network element performs communication according to the third policy.
  • the instruction of the policy needs to send the indication information of whether the QoS requirements of the first QoS Flow can be guaranteed. For example, when the user plane network element determines that the QoS requirements of the first QoS Flow cannot be guaranteed, it sends the aforementioned first indication information carrying the first indication information.
  • the first report information realizes the rapid reporting of the first report information.
  • the first session management network element sending the second report information to the application function network element includes: when the first indication information includes the identifier of the first QoS Flow, the The first session management network element determines the notification endpoint of the local network capability opening network element according to the identifier of the first QoS Flow, and transmits the notification endpoint of the local network capability opening network element to the local network capability opening network element The second report information is sent, and the second report information is sent by the local network capability opening network element to the application function network element.
  • the first session management network element analyzes the first policy, and can obtain the identification of the first QoS Flow and the notification endpoint of the local network capability opening network element.
  • the first session management network element determines the notification endpoint of the local network capability opening network element carried in the first policy according to the identifier of the first QoS Flow carried in the first indication information, and sends second report information to the notification endpoint, Therefore, the local network capability opening network element can receive the second report information from the first session management network element, and the local network capability opening network element sends the second report information to the application function network element.
  • the first session management network element may send the second report information to the local network capability opening network element through the notification endpoint of the local network capability opening network element, and then the local network capability opening network element sends the second report information to the application function network element
  • the second report information thus realizes the communication between the first session management network element and the application function network element, so that the application function network element can quickly receive the second report information, and perform application layer analysis based on the second report information
  • the adjustment reduces the transmission delay of the second report information.
  • the first policy is generated by the second session management network element according to a fourth policy from a policy control network element, and the fourth policy includes at least one candidate QoS parameter set and the An identifier of at least one candidate service requirement corresponding to an identifier of at least one candidate QoS parameter set, the at least one candidate QoS parameter set is used by the second session management network element to determine the at least one candidate QoS document, and the at least one candidate The identifier of the at least one candidate service requirement corresponding to the identifier of the QoS parameter set is used by the second session management network element to determine the identifier of the at least one candidate service requirement corresponding to the identifier of the at least one candidate QoS document, wherein the at least one The identifier of the candidate business requirement includes the identifier of the first candidate business requirement.
  • the second session management network element receives the fourth policy from the policy control network element, and the second session management network element analyzes the fourth policy, and determines at least one candidate QoS parameter set and at least one candidate QoS parameter set. Identifies the corresponding identifier of at least one candidate service requirement, at least one candidate QoS parameter set is used to determine at least one candidate QoS document; the second session management network element generates the first policy, and the second session management network element generates the first policy including The identification of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document.
  • the second session management network element can generate the first policy through interaction with the policy control network element, so that the second session management network element can send the first policy to the first session management network element.
  • the method further includes: the first session management network element receives from the policy control network element
  • the fourth strategy includes at least one candidate QoS parameter set and at least one candidate service requirement identifier corresponding to the identifier of the at least one candidate QoS parameter set, wherein the identifier of the at least one candidate service requirement includes The identification of the first candidate service requirement; the first session management network element determines the at least one candidate QoS document according to at least one candidate QoS parameter set, and determines at least one candidate corresponding to the identification of the at least one candidate QoS document Identification of business requirements.
  • the first session management network element receives the fourth policy from the policy control network element, and the first session management network element analyzes the fourth policy, and determines at least one candidate QoS parameter set and at least one candidate QoS parameter set. Identifies the corresponding identifier of at least one candidate service requirement, at least one candidate QoS parameter set is used to determine at least one candidate QoS document; the first session management network element generates a first policy, and the first policy generated by the first session management network element includes The identification of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document.
  • the first session management network element can generate the first policy through interaction with the policy control network element.
  • the method further includes: when the terminal device switches from the first access network network element to the second access network element When accessing the network element of the network, the first session management network element receives the identification information of the QoS Flow from the second access network element, and the identification information of the QoS Flow includes the identification of the first QoS Flow; The first session management network element sends third report information to the application function network element, where the third report information includes third indication information, and the third indication information is used to indicate the first service data The QoS requirements of the flow cannot be guaranteed.
  • the second access network network element may also send QoS Flow identification information to the first session management network element, for example An N2 interface is established between the second access network network element and the AMF, and an N11 interface is established between the AMF and the first session management network element.
  • the first session management network element receives the QoS Flow from the second access network network element. Identification information.
  • the identification information of the QoS Flow includes the identification of the first QoS Flow, and the first QoS Flow is used to transmit the first service data flow.
  • the first session management network element may send third report information to the application function network element, where the third report information includes third indication information, and the third indication information is used to indicate that the QoS requirement of the first service data stream cannot be guaranteed.
  • the application function network element may also receive the third report information from the first session management network element, and adjust the application layer according to the third report information, reducing the third report information Transmission delay.
  • the method further includes: the first session management network element receives an identifier of the second candidate QoS document corresponding to the first QoS Flow from the second access network network element ; Wherein, the third report information further includes the identifier of the second candidate service requirement, and the identifier of the second candidate service requirement corresponds to the identifier of the second candidate QoS document.
  • the second access network element may also send the identification of the second candidate QoS document corresponding to the first QoS Flow to the first session management network element, and the second Candidate QoS documents are also candidate QoS documents that meet the QoS requirements of the first QoS Flow.
  • the first session management network element can also determine the second candidate QoS document that meets the QoS requirements of the first QoS Flow, and the first session management network element can determine the second candidate QoS document based on the correspondence between the candidate QoS documents and the candidate service requirements.
  • the identifier of the candidate QoS document corresponds to the identifier of the second candidate service requirement.
  • the first session management network element sends third report information to the application function network element.
  • the third report information also includes the identification of the second candidate service requirement, so that the application function network element can obtain
  • the second candidate QoS document that meets the QoS requirements of the first QoS Flow solves the report indication problem when there are multiple candidate QoS documents.
  • the second report information further includes identification information of the first service data stream.
  • the application function network element may receive the second report information from the first session management network element. If the application function network element provides description information of multiple service data streams, for example, there are first service data streams and second service data streams. When the QoS requirements of the data flow can be guaranteed, the second report information sent by the first session management network element needs to carry the identification information of the first service data flow and the identification information of the second service data flow.
  • the report information sent by the first session management network element to the application function network element carries the identification information of the service data flow, which solves the problem of indicating whether the QoS requirements of each service flow can be guaranteed when there are multiple service data flows. .
  • the third report information further includes identification information of the first service data flow.
  • the application function network element may receive the third report information from the first session management network element. If the application function network element provides description information of multiple service data streams, for example, there are first service data streams and second service data streams. When the QoS requirements of the data flow can be guaranteed, the third report information sent by the first session management network element needs to carry the identification information of the first service data flow and the identification information of the second service data flow.
  • the report information sent by the first session management network element to the application function network element carries the identification information of the service data flow, which solves the problem of indicating whether the QoS requirements of each service flow can be guaranteed when there are multiple service data flows. .
  • the first session management network element can receive the first report information from the user plane network element, the first report information carries the first indication information and the identifier of the first QoS document, so the first session management network The element can obtain the second indication information according to the first indication information, and can also determine the identification of the first candidate service requirement according to the identification of the first candidate QoS document, so the first session management network element can generate the second report information, the first session management The second report information sent by the network element to the application function management network element indicates that the QoS requirement of the first service data stream cannot be guaranteed through the second indication information in the second report information.
  • the application function network element can determine that the QoS requirements of the first service data flow cannot be guaranteed.
  • the second report information It also carries the identifier of the first candidate service requirement, so that the application function network element can also determine the candidate service requirement, so that the application function network element determines that the QoS requirement of the first service data stream cannot be guaranteed according to the first candidate service requirement Quickly adjust at the application layer. Therefore, the path indicating that the QoS requirements of the first service data flow cannot be guaranteed is greatly shortened.
  • the second report information has high timeliness, which reduces the adjustment of application function network elements at the application layer. Time delay.
  • the second indication information is determined according to the first indication information.
  • the second indication information is generated according to the indication content carried in the first indication information
  • the first indication information indicates that the QoS requirements of the first QoS Flow cannot be guaranteed
  • the first session management network element is based on the first QoS Flow.
  • QoS requirements cannot be guaranteed. It is determined that the QoS requirements of the first service data flow transmitted by the first QoS Flow cannot be guaranteed, and the QoS requirements of the first service data flow carried in the second indication information cannot be guaranteed.
  • the method when the first session management network element is an intermediate session management network element, before the first session management network element receives the first report information from the user plane network element, the method It also includes: a second session management network element sending a first policy to the first session management network element, where the first policy includes an identifier of the first QoS Flow, first QoS notification control indication information, and at least one candidate QoS Document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS document
  • the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement
  • the first QoS notification control indication information is used to indicate that the QoS requirement for sending the first QoS Flow cannot be guaranteed;
  • the first session management network element receives the first policy from the second session management network element; the first session management network element determines the second policy according to the first policy,
  • the first access network network element can communicate with the first session management network element, and the second policy is received from the first session management network element, and the first access network network element parses the second policy.
  • An access network element can obtain the identification of the first QoS Flow, the second QoS notification control indication information, and at least one candidate QoS document.
  • the second QoS notification control indication information is used to indicate that the QoS requirements for sending the first QoS Flow cannot be obtained.
  • Guaranteed instruction information for example, the second QoS notification control instruction information instructs the first access network element to send the first instruction information to the user plane network element, so that the user plane network element can generate the first report information according to the first instruction information, and Sending the first report information to the first session management network element realizes the rapid reporting of the first report information.
  • the method when the first session management network element is an intermediate session management network element, before the first session management network element receives the first report information from the user plane network element, the method It also includes: a second session management network element sending a first policy to the first session management network element, where the first policy includes an identifier of the first QoS Flow, first QoS notification control indication information, and at least one candidate QoS Document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS document
  • the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement
  • the first QoS notification control indication information is used to indicate whether the QoS requirement of the first QoS Flow can be guaranteed.
  • the first session management network element receives the first policy from the second session management network element; the first session management network element determines a third policy according to the first policy, and sends it to the user
  • the plane network element sends the third policy, where the third policy is used to instruct the user plane network element to send the indication information of whether the QoS requirements of the first QoS Flow can be guaranteed; the user plane network element receives The third strategy.
  • the user plane network element can communicate with the first session management network element, and the third policy is received from the first session management network element.
  • the user plane network element analyzes the third policy, and the user plane network element performs communication according to the third policy.
  • the instruction of the policy needs to send the indication information of whether the QoS requirements of the first QoS Flow can be guaranteed. For example, when the user plane network element determines that the QoS requirements of the first QoS Flow cannot be guaranteed, it sends the aforementioned first indication information carrying the first indication information.
  • the first report information realizes the rapid reporting of the first
  • the first session management network element sends second report information to the application function network element according to the first report information, including: when the first indication information includes the first QoS When the flow is identified, the first session management network element determines the notification endpoint of the application function network element according to the identification of the first QoS Flow, and sends the notification endpoint to the application function network through the notification endpoint of the application function network element. Yuan sends the second report information.
  • the first session management network element analyzes the first policy, and can obtain the identification of the first QoS Flow and the notification endpoint information of the application function network element.
  • the first session management network element determines the notification endpoint of the application function network element carried in the first policy according to the identifier of the first QoS Flow carried in the first indication information, and sends the second report information to the notification endpoint, so that the application function network
  • the element may receive the second report information from the first session management network element.
  • the first session management network element may send the second report information to the application function network element through the notification endpoint of the application function network element, thereby realizing the communication between the first session management network element and the application function network element , So that the application function network element can quickly receive the second report information, and adjust the application layer according to the second report information, reducing the transmission delay of the second report information.
  • the method when the first session management network element is an intermediate session management network element, before the first session management network element receives the first report information from the user plane network element, the method It also includes: a second session management network element sending a first policy to the first session management network element, where the first policy includes an identifier of the first QoS Flow, first QoS notification control indication information, and at least one candidate QoS Document, the notification endpoint information of the local network capability opening network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS document
  • the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement
  • the first QoS notification control indication information is used to indicate whether the QoS requirement of the first QoS Flow can be guaranteed.
  • the first session management network element receives the first policy from the second session management network element; the first session management network element determines the second policy according to the first policy, and sends it to the first An access network element sends the second policy, where the second policy includes the first QoS Flow identifier, second QoS notification control indication information, and the at least one candidate QoS document, and the second QoS notification control
  • the indication information is determined according to the first QoS notification control indication information; the first access network network element receives the second policy.
  • the first access network network element can communicate with the first session management network element, and the second policy is received from the first session management network element, and the first access network network element parses the second policy.
  • An access network element can obtain the identification of the first QoS Flow, the second QoS notification control indication information, and at least one candidate QoS document.
  • the second QoS notification control indication information is used to indicate that the QoS requirements for sending the first QoS Flow cannot be obtained. Guaranteed instruction information, for example, the second QoS notification control instruction information instructs the first access network element to send the first instruction information to the user plane network element, so that the user plane network element can generate the first report information according to the first instruction information, and Sending the first report information to the first session management network element realizes the rapid reporting of the first report information.
  • the method when the first session management network element is an intermediate session management network element, before the first session management network element receives the first report information from the user plane network element, the method It also includes: a second session management network element sending a first policy to the first session management network element, where the first policy includes an identifier of the first QoS Flow, first QoS notification control indication information, and at least one candidate QoS Document, the notification endpoint information of the local network capability opening network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS document
  • the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement
  • the first QoS notification control indication information is used to indicate whether the QoS requirement of the first QoS Flow can be guaranteed.
  • the first session management network element receives the first policy from the second session management network element; the first session management network element determines a third policy according to the first policy, and sends it to the user
  • the plane network element sends the third policy, where the third policy is used to instruct the user plane network element to send the indication information of whether the QoS requirements of the first QoS Flow can be guaranteed; the user plane network element receives The third strategy.
  • the user plane network element can communicate with the first session management network element, and the third policy is received from the first session management network element.
  • the user plane network element analyzes the third policy, and the user plane network element performs communication according to the third policy.
  • the instruction of the policy needs to send the indication information of whether the QoS requirements of the first QoS Flow can be guaranteed. For example, when the user plane network element determines that the QoS requirements of the first QoS Flow cannot be guaranteed, it sends the aforementioned first indication information carrying the first indication information.
  • the first report information realizes the rapid reporting of the first
  • the first session management network element sending the second report information to the application function network element includes: when the first indication information includes the identifier of the first QoS Flow, the The first session management network element determines the notification endpoint of the local network capability opening network element according to the identifier of the first QoS Flow, and transmits the notification endpoint of the local network capability opening network element to the local network capability opening network element The second report information is sent, and the second report information is sent by the local network capability opening network element to the application function network element.
  • the first session management network element analyzes the first policy, and can obtain the identification of the first QoS Flow and the notification endpoint of the local network capability opening network element.
  • the first session management network element determines the notification endpoint of the local network capability opening network element carried in the first policy according to the identifier of the first QoS Flow carried in the first indication information, and sends second report information to the notification endpoint, Therefore, the local network capability opening network element can receive the second report information from the first session management network element, and the local network capability opening network element sends the second report information to the application function network element.
  • the first session management network element may send the second report information to the local network capability opening network element through the notification endpoint of the local network capability opening network element, and then the local network capability opening network element sends the second report information to the application function network element
  • the second report information thus realizes the communication between the first session management network element and the application function network element, so that the application function network element can quickly receive the second report information, and perform application layer analysis based on the second report information
  • the adjustment reduces the transmission delay of the second report information.
  • the method further includes: the policy control network element sends a fourth policy to the second session management network element, where the fourth policy includes at least one candidate QoS parameter set and the at least one candidate QoS parameter set.
  • the identifier of the candidate QoS parameter set corresponds to the identifier of at least one candidate service requirement; the second session management network element receives the fourth policy from the policy control network element; the second session management network element is based on the fourth policy.
  • the first policy is generated, wherein the at least one candidate QoS parameter set is used to determine the at least one candidate QoS document; the identification of the at least one candidate QoS parameter set corresponds to the identification of the at least one candidate service requirement that is used to determine The identifier of the at least one candidate service requirement corresponding to the identifier of the at least one candidate QoS document, wherein the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement.
  • the second session management network element receives the fourth policy from the policy control network element, and the second session management network element analyzes the fourth policy and determines at least one candidate QoS parameter set and at least one candidate QoS parameter set. Identifies the corresponding identifier of at least one candidate service requirement, at least one candidate QoS parameter set is used to determine at least one candidate QoS document; the second session management network element generates the first policy, and the second session management network element generates the first policy including The identification of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document.
  • the second session management network element can generate the first policy through interaction with the policy control network element, so that the second session management network element can send the first policy to the first session management network element.
  • the method further includes: the policy control network element sends to the first session management network element A fourth strategy, the fourth strategy includes at least one candidate QoS parameter set and at least one candidate service requirement identifier corresponding to the identifier of the at least one candidate QoS parameter set, wherein the identifier of the at least one candidate service requirement includes all The identifier of the first candidate service requirement; the first session management network element receives the fourth policy from the policy control network element; the first session management network element generates the first policy according to the fourth policy, Wherein, the at least one candidate QoS parameter set is used to determine at least one candidate QoS document, and the identification of the at least one candidate QoS parameter set corresponding to the identification of the at least one candidate service requirement is used to determine the identification of the at least one candidate QoS document The corresponding identification of at least one candidate service requirement; the first policy includes the identification of the first QoS Flow, the first QoS
  • the first session management network element receives the fourth policy from the policy control network element, and the first session management network element analyzes the fourth policy, and determines at least one candidate QoS parameter set and at least one candidate QoS parameter set. Identifies the corresponding identifier of at least one candidate service requirement, at least one candidate QoS parameter set is used to determine at least one candidate QoS document; the first session management network element generates a first policy, and the first policy generated by the first session management network element includes The identification of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document.
  • the first session management network element can generate the first policy through interaction with the policy control network element.
  • an embodiment of the present application also provides a method for sending report information, including: a policy control network element receives a service request from an application function network element, where the service request includes first quality of service QoS notification control indication information and at least A candidate service requirement, where the first QoS notification control indication information is used to indicate whether the QoS requirement for sending the first service data stream can be guaranteed; the policy control network element generates a fourth policy according to the service request, The fourth policy includes second QoS notification control indication information, at least one candidate QoS parameter set, and an identification of the at least one candidate service requirement corresponding to the identification of the at least one candidate QoS parameter set, wherein the at least one candidate The quality of service QoS parameter set is determined according to the at least one candidate service requirement, and the second QoS notification control indication information is used to indicate whether the QoS requirement of the first service data stream can be guaranteed to be sent; the policy control network element Send the fourth policy to the first session management network element.
  • the application function network element provides candidate service requirements when sending a service request to the policy control network element, the policy control network element determines the candidate QoS parameter set according to the candidate service requirements, and the policy control network element can obtain at least one candidate QoS parameter set, and at least one candidate service requirement identification corresponding to the identification of the at least one candidate QoS parameter set is obtained, and then the policy control network element generates a fourth policy, and sends the fourth policy to the first session management network element, and the fourth policy It includes at least one candidate QoS parameter set and at least one candidate service requirement identification corresponding to the identification of the at least one candidate QoS parameter set.
  • the service request further includes identification information of the first service data flow
  • the fourth policy further includes identification information of the first service data flow.
  • the application function network element provides description information of multiple service data streams
  • the service request further includes the identification information of the first service data stream
  • the fourth policy also includes the information of the first service data stream. Identification information.
  • the application function network element sends the policy control network element
  • the sent service request carries the identification information of the service data stream, which solves the problem of indicating whether the QoS requirement of each service stream can be guaranteed when there are multiple service data streams.
  • an embodiment of the present application provides a communication device, the communication device is specifically a first session management network element, and the first session management network element is configured to execute the method described in any one of the foregoing first aspects .
  • an embodiment of the present application provides a communication device, where the communication device is specifically a policy control network element, and the policy control network element is configured to execute the method described in any one of the foregoing third aspects.
  • an embodiment of the present application provides a communication system, including: a user plane network element, a first session management network element, and an application function network element, wherein the user plane network element is used to perform the above-mentioned second aspect Any method performed by the user plane network element; the first session management network element is used to perform any method performed by the first session management network element in the second aspect; the application function network element uses Any one of the methods executed by the application function network element described in the foregoing second aspect is executed.
  • the communication system further includes at least one of the following: a second session management network element, a policy control network element, a first access network network element, a second access network network element, and local network capabilities Open network elements.
  • an embodiment of the present application provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, which when run on a computer, causes the computer to execute the first aspect or the second aspect or The method of any one of the third aspect.
  • the embodiments of the present application provide a computer program product containing instructions, which when run on a computer, cause the computer to execute the method described in any one of the first aspect, the second aspect, or the third aspect. .
  • inventions of the present application provide a communication device.
  • the communication device may include entities such as a user plane network element, a first session management network element, an application function network element, a policy control network element, or a chip, and the communication device includes : A processor, optionally, further comprising a memory; the memory is used to store instructions; the processor is used to execute the instructions in the memory, so that the communication device executes the aforementioned first aspect or second aspect Or the method of any one of the third aspect.
  • this application provides a chip system that includes a processor for supporting user plane network elements, first session management network elements, application function network elements, or policy control network elements to implement the aspects involved in the above aspects Functions, for example, sending or processing the data and/or information involved in the above methods.
  • the chip system further includes a memory for storing necessary program instructions and data for the user plane network element, the first session management network element, the application function network element, or the policy control network element .
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of the composition structure of a communication system provided by an embodiment of this application.
  • FIG. 2 is a schematic diagram of the composition structure of another communication system provided by an embodiment of this application.
  • FIG. 3 is a schematic diagram of the interaction flow of a method for sending report information according to an embodiment of the application
  • FIG. 4a is a schematic diagram of an application system architecture of a communication system provided by an embodiment of this application.
  • 4b is a schematic diagram of the application system architecture of another communication system provided by an embodiment of this application.
  • FIG. 4c is a schematic diagram of an application system architecture of another communication system provided by an embodiment of this application.
  • FIG. 5 is a schematic diagram of an interaction process between network elements in the communication system provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of an interaction flow between network elements in the communication system provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of the composition structure of a first session management network element provided by an embodiment of this application.
  • FIG. 8 is a schematic diagram of the composition structure of an application function network element provided by an embodiment of the application.
  • FIG. 9 is a schematic diagram of the composition structure of another first session management network element provided by an embodiment of this application.
  • FIG. 10 is a schematic diagram of the composition structure of another application function network element provided by an embodiment of the application.
  • the embodiment of the present application provides a method for sending report information, a communication device, and a communication system, which are used to shorten the transmission path of the reported information and reduce the processing delay of the application function network element.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • the term "system” can be used interchangeably with "network”.
  • the CDMA system can implement wireless technologies such as universal terrestrial radio access (UTRA) and CDMA2000.
  • UTRA can include wideband CDMA (wideband CDMA, WCDMA) technology and other CDMA variants.
  • CDMA2000 can cover the interim standard (IS) 2000 (IS-2000), IS-95 and IS-856 standards.
  • the TDMA system can implement wireless technologies such as the global system for mobile communication (GSM).
  • GSM global system for mobile communication
  • OFDMA system can realize such as evolved universal wireless terrestrial access (evolved UTRA, E-UTRA), ultra mobile broadband (ultra mobile broadband, UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDMA And other wireless technologies.
  • UTRA and E-UTRA are UMTS and UMTS evolved versions.
  • 3GPP is a new version of UMTS using E-UTRA in long term evolution (LTE) and various versions based on LTE evolution.
  • the fifth generation (5G”) communication system and New Radio (“NR”) are the next generation communication systems under study.
  • the communication system may also be suitable for future-oriented communication technologies, all of which are applicable to the technical solutions provided in the embodiments of the present application.
  • the system architecture and business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those of ordinary skill in the art will know that with the network With the evolution of architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.
  • FIG. 1 is a schematic diagram of the composition structure of a communication system provided by an embodiment of this application.
  • An embodiment of the present application provides a communication system 100, including:
  • the user plane network element 101 is configured to send first report information to the first session management network element 102.
  • the first report information includes the first indication information and the identifier of the first candidate quality of service (QoS) document.
  • the indication information is used to indicate that the QoS requirements of the first quality of service flow (QoS Flow) cannot be guaranteed;
  • the first session management network element 102 is configured to receive the first report information from the user plane network element 101;
  • the first session management network element 102 is configured to send second report information to the application function network element 103.
  • the second report information includes the second indication information and the identifier of the first candidate service requirement.
  • the identifier of the first candidate service requirement corresponds to the first candidate service requirement.
  • the identification of the candidate QoS document, the second indication information is used to indicate that the QoS requirements of the first service data flow cannot be guaranteed, the first QoS Flow is used to transmit the first service data flow, and the service data flow is the application corresponding to the application function network element 103 Business data flow;
  • the application function network element 103 is configured to receive the second report information sent by the first session management network element 102.
  • the user plane network element 101 can communicate with the radio access network (RAN) and the first session management network element 102 respectively, and the user plane network element 101 may specifically be a user plane function (UPF) Network element.
  • the user plane network element 101 may be in a local data center (local data center), and the user plane network element 101 may also be referred to as a local protocol data unit anchor (local PDU session anchor, local PSA).
  • the user plane network element 101 may support all or part of the following functions: interconnecting protocol data unit (PDU) sessions with data networks; packet routing and forwarding (for example, supporting upstream classification of traffic and forwarding to data Network; data packet inspection and other functions.
  • PDU interconnecting protocol data unit
  • the user plane network element 101 may communicate with the first session management network element 102. For example, an N4 interface is established between the user plane network element 101 and the first session management network element 102.
  • the first session management network element 102 is a management network element of a PDU session.
  • the first session management network element 102 is located in a local data center, and the first session management network element 102 may specifically be a session management function (SMF) .
  • the first session management network element 102 may specifically be an intermediate session management function (intermediate session management function, I-SMF), and the first session management network element 102 may communicate with the SMF in the core data center (central DC) .
  • central DC core data center
  • an N4 interface is established between the first session management network element 102 and the user plane network element 101.
  • an N33 interface is established between the first session management network element 102 and the application function network element 103, or between the first session management network element 102 and a local network exposure function (local network exposure function, local NEF)
  • An Nx interface is established, an N33 interface is established between the local network capability opening network element and the application function network element 103, and the first session management network element 102 communicates with the application function network element 103 through the local network capability opening network element.
  • the implementation manner of the first session management network element 102 can be determined according to the application scenario, which is not limited here.
  • the application function network element 103 may communicate with the first session management network element 102 to obtain QoS report information, and perform application layer function adjustments based on the report information.
  • the application function network element 103 may specifically be an application function network element (AF) in a local data center.
  • the AF is deployed on an edge application server (EAS).
  • EAS edge application server
  • An embodiment of the present application provides a communication system 100 in addition to including a user plane network element 101, a first session management network element 102, and an application function network element 103,
  • the communication system 100 may also include:
  • the policy control network element 104 is configured to receive a service request from the application function network element 103.
  • the service request includes first quality of service QoS notification control indication information and at least one candidate service requirement.
  • the first QoS notification control indication information is used to instruct to send the second An indication information of whether the QoS requirements of the service data stream can be guaranteed;
  • the policy control network element 104 is configured to generate a fourth policy according to the service request, where the fourth policy includes second QoS notification control indication information, at least one candidate QoS parameter set, and at least one candidate service requirement corresponding to the identifier of the at least one candidate QoS parameter set Where the at least one candidate QoS parameter set is determined according to the at least one candidate service requirement, and the second QoS notification control indication information is used to indicate whether the QoS requirement of the first service data stream can be guaranteed to be sent;
  • the policy control network element 104 is configured to send the fourth policy to the first session management network element 102.
  • the policy control network element 104 is a functional network element that provides a policy.
  • the policy control network element 104 may specifically be a policy control function (PCF) network element in a core data center, and the policy control network element 104 can formulate a policy
  • PCF policy control function
  • the charging control (policy and charging control, PCC) rule carries the aforementioned fourth policy through the PCC rule.
  • the policy control network element 104 can communicate with the application function network element 103.
  • the policy control network element 104 communicates with the application function network element 103 through a network capability opening network element (NEF), such as the policy control network element 104 and the application function network element 103.
  • NEF network capability opening network element
  • An N5 interface is configured between the network capability opening network elements
  • an N33 interface is configured between the network capability opening network element and the application function network element 103.
  • the policy control network element 104 communicates through the network capability open network element, the local network capability open network element, and the application function network element 103.
  • the policy control network element 104 and the network capability open network element are configured with an N5 interface, and the network capability An N33a interface is configured between the open network element and the local network capability open network element, and an N33 interface is configured between the local network capability open network element and the application function network element 103.
  • the communication system 100 in the embodiment of the present application may also include the above-mentioned local network capability opening network element and network capability opening network element, which are not illustrated schematically in FIG. 2.
  • the communication system 100 may also include network elements such as the second session management network element, the first access network network element, and the second access network network element mentioned in the subsequent embodiments, all of which are not illustrated schematically in the illustration.
  • the first access network network element may be the wireless access network where the terminal device is located before the handover
  • the second access network network element may be the wireless access network where the terminal device is located after the handover.
  • the first session management network element may receive the first report information from the user plane network element, and the first report information carries the first indication information. And the identification of the first QoS document, so the first session management network element can obtain the second indication information according to the first indication information, and can also determine the identification of the first candidate service requirement according to the identification of the first candidate QoS document, so the first session The management network element can generate second report information.
  • the second report information sent by the first session management network element to the application function management network element indicates the QoS requirements of the first service data stream through the second indication information in the second report information Cannot be guaranteed.
  • the application function network element can determine that the QoS requirements of the first service data flow cannot be guaranteed.
  • the second report information It also carries the identifier of the first candidate service requirement, so that the application function network element can also determine the candidate service requirement, so that the application function network element determines that the QoS requirement of the first service data stream cannot be guaranteed according to the first candidate service requirement Quickly adjust at the application layer. Therefore, the path indicating that the QoS requirements of the first service data flow cannot be guaranteed is greatly shortened.
  • the second report information has high timeliness, which reduces the adjustment of application function network elements at the application layer. Time delay.
  • the communication system provided by this application.
  • the communication method executed based on the communication system will be introduced.
  • the method for sending report information provided by the embodiment of this application mainly includes the following steps:
  • a user plane network element sends first report information to a first session management network element, where the first report information includes first indication information and an identifier of a first candidate quality of service QoS document, and the first indication information is used to indicate the first quality of service Flow QoS Flow's QoS requirements cannot be guaranteed.
  • the user plane network element can obtain from the RAN whether the QoS requirements of the first QoS Flow can be guaranteed.
  • the first QoS Flow is the QoS Flow that carries the first service data flow.
  • the user plane network element determines that the QoS requirements of the first QoS Flow cannot be guaranteed, the user plane network element generates the first indication information, and when it determines that the QoS requirements of the first QoS Flow cannot be guaranteed, the user plane network element may also determine the first candidate (Alternative).
  • the identification of the QoS profile (Profile) the first candidate QoS profile may be a QoS profile that can guarantee the QoS requirements of the first QoS Flow.
  • the identifier of the first candidate QoS document may be the first AltProId.
  • the first report information may specifically be a data packet carrying a QoS notification control (Notification Control) event report.
  • QoS notification control Notification Control
  • the QoS requirements of the first QoS Flow can include the maximum bandwidth (that is, the maximum transmission bit rate (max bitrate)), the guaranteed bandwidth (that is, the guaranteed bitrate), the packet delay budget, and the packet delay.
  • the first indication information is used to indicate that the guaranteed bandwidth of the first quality of service flow QoS Flow cannot be guaranteed.
  • the first session management network element receives the first report information from the user plane network element.
  • the user plane network element can communicate with the first session management network element, for example, an N4 interface is established between the user plane network element and the first session management network element.
  • the first session management network element may receive the first report information from the user plane network element.
  • the first report information includes the first indication information and the identifier of the first candidate quality of service QoS document, and the first indication information is used to indicate that the QoS requirement of the first quality of service flow QoS Flow cannot be guaranteed.
  • the first session management network element may be an intermediate session management network element.
  • the first session management network element may be an I-SMF.
  • the first session management network element is located in the local data center, and the core A second session management network element may be deployed in the data center.
  • the second session management network element may be an SMF.
  • An N16a interface may be configured between the first session management network element and the second session management network element.
  • the second session management network element sends a first policy to the first session management network element, where the first policy includes the identifier of the first QoS Flow, the first QoS notification control instruction information, at least one candidate QoS document, and the application function network element
  • the second session management network element may generate the first policy, the second session management network element may communicate with the first session management network element, and the second session management network element sends the first policy to the first session management network element.
  • the first policy generated by the second session management network element includes the identifier of the first QoS Flow, the first QoS notification control instruction information, at least one candidate QoS document, the notification endpoint information of the application function network element, and at least one candidate QoS
  • the identification of the document corresponds to the identification of at least one candidate business requirement.
  • the at least one candidate QoS document includes a first candidate QoS document
  • the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement
  • the identifier of the at least one candidate QoS document corresponding to the identifier of the at least one candidate service requirement indicates the candidate QoS Correspondence between documents and candidate business requirements.
  • the notification endpoint information of the application function network element includes the notification endpoint corresponding to the application function network element.
  • the notification endpoint corresponding to the application function network element may be Notification Endpoint 1a (Notification Endpoint 1a), and the notification endpoint 1a includes the target of receiving QoS notification control event notification.
  • the notification address 1a (Notification Target Address1a)
  • the notification endpoint 1a includes the target notification address 1a (Notification Target Address1a) and the notification correlation identifier 1a (Notification Correlation Id1a).
  • the first policy sent by the second session management network element may further include: first QoS notification control instruction information, which is used to indicate that the QoS requirements for sending the first QoS Flow cannot be guaranteed. That is, the first QoS notification control instruction information may be used to indicate that the foregoing first instruction information needs to be sent.
  • the first session management network element receives the first policy from the second session management network element.
  • the first session management network element can communicate with the second session management network element, the second session management network element sends the first policy to the first session management network element, and the first session management network element receives from the second session management network element.
  • the first strategy of the network element, the first session management network element analyzes the first strategy, and can obtain the identification of the first QoS Flow, the first QoS notification control instruction information, at least one candidate QoS document, and the notification endpoint of the application function network element And the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document.
  • the first session management network element determines the second policy according to the first policy, and sends the second policy to the first access network element, where the second policy includes the identifier of the first QoS Flow and the second QoS notification control instruction Information and at least one candidate QoS document, and the second QoS notification control indication information is determined according to the first QoS notification control indication information.
  • the first session management network element can obtain the identification of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, the notification endpoint information of the application function network element, and the identification correspondence of at least one candidate QoS document Then the first session management network element generates a second policy, the second policy includes the first QoS Flow identifier, the second QoS notification control indication information and at least one candidate QoS document, and the second QoS notification The control instruction information is determined according to the first QoS notification control instruction information.
  • the second QoS notification control indication information can be the same QoS notification control indication information as the first QoS notification control indication information, that is, the second QoS notification control indication information is used to indicate that the QoS requirements for sending the first QoS Flow cannot be guaranteed.
  • the first QoS notification control instruction information may be used to indicate that the foregoing first instruction information needs to be sent.
  • the second QoS notification control indication information is generated according to the content of the indication information carried in the first QoS notification control indication information. Specifically, the second QoS notification control indication information may be required to be in the first QoS according to the communication protocol of the transmission information.
  • the notification control indication information is obtained by adding a specific information field, or the second QoS notification control indication information may be obtained after removing unnecessary information fields from the first QoS notification control indication information according to the requirements of the communication protocol of the transmission information.
  • the first session management network element may communicate with the first access network network element, for example, the first session management network element sends a second policy to the first access network network element, where the first access network network element may be a terminal
  • the wireless access network where the device was switched before.
  • an N11 interface may be established between the first session management network element and an access and mobility management function (AMF), and an N2 interface may be established between the AMF and the first access network network element.
  • AMF access and mobility management function
  • the network element of the first access network receives the second policy.
  • the first access network network element can communicate with the first session management network element, the second policy is received from the first session management network element, the first access network network element analyzes the second policy, and the first access The network element can obtain the identity of the first QoS Flow, the second QoS notification control indication information, and at least one candidate QoS document.
  • the second QoS notification control indication information is used to indicate that the QoS requirements for sending the first QoS Flow cannot be guaranteed.
  • Information for example, the second QoS notification control instruction information instructs the first access network element to send the first instruction information to the user plane network element.
  • the first session management network element may be an intermediate session management network element.
  • the first session management network element may be an I-SMF.
  • the first session management network element is located in the local data center, and the core A second session management network element may be deployed in the data center.
  • the second session management network element may be an SMF.
  • An N16a interface may be configured between the first session management network element and the second session management network element.
  • the second session management network element sends a first policy to the first session management network element, where the first policy includes the identifier of the first QoS Flow, the first QoS notification control instruction information, at least one candidate QoS document, and the information of the application function network element.
  • the second session management network element may generate the first policy, the second session management network element may communicate with the first session management network element, and the second session management network element sends the first policy to the first session management network element.
  • the first policy generated by the second session management network element includes the identifier of the first QoS Flow, the first QoS notification control instruction information, at least one candidate QoS document, the notification endpoint information of the application function network element, and at least one candidate QoS
  • the identification of the document corresponds to the identification of at least one candidate business requirement.
  • the at least one candidate QoS document includes a first candidate QoS document
  • the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement
  • the identifier of the at least one candidate QoS document corresponding to the identifier of the at least one candidate service requirement indicates the candidate QoS Correspondence between documents and candidate business requirements.
  • the notification endpoint information of the application function network element includes the notification endpoint corresponding to the application function network element.
  • the notification endpoint corresponding to the application function network element may be Notification Endpoint 1a (Notification Endpoint 1a), and the notification endpoint 1a includes the target of receiving QoS notification control event notification.
  • the notification address 1a (Notification Target Address1a)
  • the notification endpoint 1a includes the target notification address 1a (Notification Target Address1a) and the notification correlation identifier 1a (Notification Correlation Id1a).
  • the first policy sent by the second session management network element may further include: first QoS notification control instruction information, which is used to indicate that the QoS requirements for sending the first QoS Flow cannot be guaranteed. That is, the first QoS notification control instruction information may be used to indicate that the foregoing first instruction information needs to be sent.
  • the first session management network element receives the first policy from the second session management network element.
  • the first session management network element can communicate with the second session management network element, the second session management network element sends the first policy to the first session management network element, and the first session management network element receives from the second session management network element.
  • the first strategy of the network element, the first session management network element analyzes the first strategy, and can obtain the identification of the first QoS Flow, the first QoS notification control instruction information, at least one candidate QoS document, and the notification endpoint of the application function network element And the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document.
  • the first session management network element determines the third strategy according to the first strategy, and sends the third strategy to the user plane network element.
  • the third strategy is used to indicate whether the QoS requirements of the user plane network element for sending the first QoS Flow can be guaranteed. Instructions.
  • the first session management network element can obtain the identification of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, the notification endpoint information of the application function network element, and the identification correspondence of at least one candidate QoS document Then, the first session management network element generates a third strategy, and the third strategy is used to instruct the user plane network element to send the first QoS Flow to indicate whether the QoS requirements of the first QoS Flow can be guaranteed.
  • the first session management network element can communicate with the user plane network element, and the first session management network element sends the third policy to the user plane network element.
  • the user plane network element receives the third strategy.
  • the user plane network element can communicate with the first session management network element, the third policy is received from the first session management network element, the user plane network element analyzes the third policy, and the user plane network element follows the instructions of the third policy , It is necessary to send the indication information of whether the QoS requirement of the first QoS Flow can be guaranteed, for example, when the user plane network element determines that the QoS requirement of the first QoS Flow cannot be guaranteed, it sends the aforementioned first report information carrying the first indication information .
  • the first session management network element may be an intermediate session management network element.
  • the first session management network element may be an I-SMF.
  • the first session management network element is located in the local data center, and the core A second session management network element may be deployed in the data center.
  • the second session management network element may be an SMF.
  • An N16a interface may be configured between the first session management network element and the second session management network element.
  • the second session management network element sends a first policy to the first session management network element, where the first policy includes the identifier of the first QoS Flow, the first QoS notification control instruction information, at least one candidate QoS document, and the local network capability opening network.
  • the identification of the requirement, the first QoS notification control indication information is used to indicate whether the QoS requirement of the first QoS Flow can be guaranteed.
  • step S21 is different from the information of the notification endpoint carried in the first strategy in step S01.
  • the first strategy in step S21 includes the notification endpoint information of the local network capability opening network element, and the local network capability opening network element
  • the notification endpoint information includes the notification endpoint corresponding to the local network capability opening network element.
  • the notification endpoint corresponding to the local network capability opening network element may be Notification Endpoint 1a (Notification Endpoint 1a), and the notification endpoint 1a includes the target that receives the QoS notification control event notification.
  • the notification address 1a (Notification Target Address1a), or the notification endpoint 1a includes the target notification address 1a (Notification Target Address1a) and the notification correlation identifier 1a (Notification Correlation Id1a).
  • the first session management network element receives the first policy from the second session management network element.
  • the first session management network element determines a second policy according to the first policy, and sends the second policy to the first access network element.
  • the second policy includes the first QoS Flow identifier, the second QoS notification control instruction information, and at least A candidate QoS document, and the second QoS notification control indication information is determined according to the first QoS notification control indication information;
  • the network element of the first access network receives the second policy.
  • steps S22 to S24 are similar to the implementation of steps S02 to S04 in the foregoing embodiment, and will not be repeated here.
  • the first session management network element may be an intermediate session management network element.
  • the first session management network element may be an I-SMF.
  • the first session management network element is located in the local data center, and the core A second session management network element may be deployed in the data center.
  • the second session management network element may be an SMF.
  • An N16a interface may be configured between the first session management network element and the second session management network element.
  • the second session management network element sends a first policy to the first session management network element, where the first policy includes the identifier of the first QoS Flow, the first QoS notification control instruction information, at least one candidate QoS document, and the local network capability opening network.
  • the identification of the requirement, the first QoS notification control indication information is used to indicate whether the QoS requirement of the first QoS Flow can be guaranteed.
  • step S31 is different from the information of the notification endpoint carried by the first policy in step S11.
  • the first policy in step S31 includes the notification endpoint information of the local network capability opening network element, and the local network capability opening network element
  • the notification endpoint information includes the notification endpoint corresponding to the local network capability opening network element.
  • the notification endpoint corresponding to the local network capability opening network element may be Notification Endpoint 1a (Notification Endpoint 1a), and the notification endpoint 1a includes the target that receives the QoS notification control event notification.
  • the notification address 1a (Notification Target Address1a), or the notification endpoint 1a includes the target notification address 1a (Notification Target Address1a) and the notification correlation identifier 1a (Notification Correlation Id1a).
  • the first session management network element receives the first policy from the second session management network element.
  • the first session management network element determines the third strategy according to the first strategy, and sends the third strategy to the user plane network element.
  • the third strategy is used to indicate whether the QoS requirements of the user plane network element for sending the first QoS Flow can be guaranteed. Instruction information;
  • the user plane network element receives the third strategy.
  • steps S32 to S34 are similar to the implementation of steps S12 to S14 in the foregoing embodiment, and will not be repeated here.
  • the report information provided by the embodiment of this application can also include the following steps:
  • the policy control network element sends a fourth policy to the second session management network element, where the fourth policy includes at least one candidate QoS parameter set and at least one candidate service requirement identification corresponding to the identification of the at least one candidate QoS parameter set;
  • the second session management network element receives the fourth policy from the policy control network element.
  • the network element of the second session management network generates the first policy according to the fourth policy, where at least one candidate QoS parameter set is used to determine at least one candidate QoS document; at least one candidate service requirement corresponding to the identifier of the at least one candidate QoS parameter set
  • the identifier of is used to determine the identifier of at least one candidate service requirement corresponding to the identifier of the at least one candidate QoS document, where the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement.
  • the second session management network element and the policy control network element are both in the core data center.
  • the second session management network element and the policy control network element can communicate through the N7 interface, and the application function network element is in the direction of the policy control network element.
  • the policy control network element determines a candidate QoS parameter set according to the candidate service requirements.
  • the policy control network element can obtain at least one candidate QoS parameter set and the identification of at least one candidate QoS parameter set.
  • the policy control network element generates a fourth policy, and sends the fourth policy to the second session management network element.
  • the fourth policy includes at least one candidate QoS parameter set and at least one candidate QoS parameter set. Identifies the corresponding identifier of at least one candidate business requirement.
  • the second session management network element receives the fourth policy from the policy control network element, the second session management network element parses the fourth policy, and determines at least one candidate QoS parameter set and at least one corresponding to the identifier of the at least one candidate QoS parameter set Identification of candidate service requirements, at least one candidate QoS parameter set is used to determine at least one candidate QoS document; the second session management network element generates the first policy, the second session management network element generates the first policy including the first QoS Flow The identification, the first QoS notification control indication information, at least one candidate QoS document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document.
  • the second session management network element can generate the first policy through interaction with the policy control network element, so that the second session management network element can send the first policy to the first session management network element.
  • the first session management network element may be a session management network element, for example, the first session management network element may be an SMF, and the first session management network element is located in a local data center, and a core data center.
  • a policy control network element may be deployed, for example, the policy control network element may be a PCF.
  • An N7 interface may be configured between the first session management network element and the policy control network element.
  • the policy control network element sends a fourth policy to the first session management network element, where the fourth policy includes at least one candidate QoS parameter set and at least one candidate service requirement identification corresponding to the identification of the at least one candidate QoS parameter set, where at least one candidate
  • the identification of the business requirement includes the identification of the first candidate business requirement
  • the first session management network element receives the fourth policy from the policy control network element
  • the network element of the first session management network generates the first policy according to the fourth policy, wherein at least one candidate QoS parameter set is used to determine at least one candidate QoS document, and the identification of the at least one candidate QoS parameter set corresponds to the identification of the at least one candidate service requirement Used to determine the identification of at least one candidate service requirement corresponding to the identification of at least one candidate QoS document; the first strategy includes the identification of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, and the notification of the target network element The information of the endpoint and the identifier of at least one candidate service requirement corresponding to the identifier of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS document, and the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement ,
  • the first QoS notification control instruction information is used to indicate whether the QoS requirement of the first QoS Flow can be guaranteed
  • the first session management network element is in the local data center
  • the policy control network element is in the core data center
  • the first session management network element and the policy control network element can communicate through the N7 interface
  • the application function network element is in the forward direction.
  • the policy control network element provides candidate service requirements when sending a service request.
  • the policy control network element determines a candidate QoS parameter set according to the candidate service requirements.
  • the policy control network element can obtain at least one candidate QoS parameter set and obtain at least one candidate QoS parameter set.
  • the identification of the parameter set corresponds to the identification of at least one candidate service requirement, and then the strategy control network element generates a fourth strategy, and sends the fourth strategy to the first session management network element.
  • the fourth strategy includes at least one candidate QoS parameter set and at least one candidate The identifier of the at least one candidate service requirement corresponding to the identifier of the QoS parameter set.
  • the first session management network element receives the fourth policy from the policy control network element, the first session management network element parses the fourth policy, and determines at least one candidate QoS parameter set and at least one corresponding to the identifier of the at least one candidate QoS parameter set Identification of candidate service requirements, at least one candidate QoS parameter set is used to determine at least one candidate QoS document; the first session management network element generates a first policy, and the first policy generated by the first session management network element includes the first QoS Flow The identification, the first QoS notification control indication information, at least one candidate QoS document, the notification endpoint information of the application function network element, and the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document.
  • the first session management network element can generate the first policy through interaction with the policy control network element.
  • the method for sending report information provided in the embodiments of the present application includes the following steps:
  • the policy control network element receives a service request from an application function network element.
  • the service request includes first quality of service QoS notification control indication information and at least one candidate service requirement.
  • the first QoS notification control indication information is used to instruct to send the first Information indicating whether the QoS requirements of the service data stream can be guaranteed;
  • the policy control network element generates a fourth policy according to the service request, where the fourth policy includes second QoS notification control indication information, at least one candidate QoS parameter set, and all corresponding to the identifier of the at least one candidate QoS parameter set.
  • the policy control network element sends the fourth policy to the first session management network element.
  • the application function network element provides candidate service requirements when sending a service request to the policy control network element
  • the policy control network element determines a candidate QoS parameter set according to the candidate service requirements
  • the policy control network element can obtain at least one candidate QoS parameter Set, and at least one candidate service requirement identification corresponding to the identification of the at least one candidate QoS parameter set is obtained, and then the policy control network element generates a fourth policy, and sends the fourth policy to the first session management network element.
  • the fourth policy includes at least One candidate QoS parameter set and the identification of the at least one candidate QoS parameter set correspond to the identification of at least one candidate service requirement.
  • the service request further includes identification information of the first service data flow
  • the fourth policy further includes identification information of the first service data flow
  • the service request further includes the identification information of the first service data flow
  • the fourth policy further includes the identification information of the first service data flow.
  • the application function network element sends the policy control network element
  • the sent service request carries the identification information of the service data stream, which solves the problem of indicating whether the QoS requirement of each service stream can be guaranteed when there are multiple service data streams.
  • the first session management network element sends second report information to the application function network element, the second report information includes the second indication information and the identifier of the first candidate service requirement, and the identifier of the first candidate service requirement corresponds to the first candidate QoS document
  • the second indication information is used to indicate that the QoS requirements of the first service data flow cannot be guaranteed
  • the first QoS Flow is used to transmit the first service data flow
  • the first service data flow is the service of the application corresponding to the application function network element data flow.
  • the first session management network element parses the first report information, and obtains the first indication information and the first report information through the first report information. With the identification of the candidate QoS document, the first session management network element further parses the first indication information, and the first session management network element can obtain the first QoS Flow.
  • the QoS requirements cannot be guaranteed.
  • the first session management network element can obtain the identifier of the first candidate service requirement corresponding to the identifier of the first candidate QoS document, for example, the identifier of the first candidate service requirement It can be the first Alternative Service Requirement Id (AltSerId for short).
  • the first service data flow is the service data flow of the application corresponding to the application function network element, and the first QoS Flow is used to transmit the first service data flow, so the first session management network element can generate the second indication information according to the first indication information
  • the first indication information indicates that the QoS requirements of the first QoS Flow cannot be guaranteed
  • the first session management network element determines the QoS requirements of the first service data flow transmitted by the first QoS Flow according to the QoS requirements of the first QoS Flow. If it cannot be guaranteed, the first session management network element generates the second indication information.
  • the first session management network element may generate second report information.
  • the QoS requirement of the first service data stream may include one or more of media type, maximum requested bandwidth, minimum requested bandwidth, maximum supported bandwidth, minimum expected bandwidth, maximum packet loss rate, and QoS reference identifier.
  • media type of the first service data stream it is determined according to the media type of the first service data stream that the guaranteed bandwidth of the first service data stream cannot be guaranteed, and the second indication information is used to indicate that the guaranteed bandwidth of the first service data stream cannot be guaranteed.
  • the second indication information is determined according to the first indication information.
  • the second indication information is generated according to the indication content carried in the first indication information
  • the first indication information indicates that the QoS requirements of the first QoS Flow cannot be guaranteed
  • the first session management network element cannot according to the QoS requirements of the first QoS Flow.
  • Obtaining Guarantee It is determined that the QoS requirement of the first service data flow transmitted by the first QoS Flow cannot be guaranteed, and the QoS requirement of the first service data flow carried in the second indication information cannot be guaranteed.
  • the second indication information is obtained based on the first indication information.
  • the first indication information and the second indication information may be the same indication information. This is just an example, not as a limitation to the embodiments of the present application.
  • the first session management network element can communicate with the application function network element, for example, the first session management network element sends the second report information to the application function network element.
  • the application function network element receives the second report information sent by the first session management network element.
  • the application function network element can communicate with the first session management network element.
  • the application function network element can receive the second report information from the first session management network element, and the application function network element analyzes For the second report information, the second indication information and the identification of the first candidate service requirement are obtained through the second report information, and the application function network element further analyzes the second indication information, and the application function network element can obtain the first service data
  • the QoS requirements of the flow cannot be guaranteed.
  • the application function network element also obtains the identification of the first candidate service requirement from the second report information, so that the application function network element can also determine the candidate service requirement, so that the application function network element can determine the QoS of the first service data stream.
  • the second report information has high timeliness, which reduces the adjustment of application function network elements at the application layer. Time delay.
  • the first session management network element receives the first policy from the second session management network element, and the first policy includes the notification endpoint information of the application function network element. Specifically, in step 304, the first session management network element sends the second report information to the application function network element according to the first report information, including:
  • the first session management network element determines the notification endpoint of the application function network element according to the identification of the first QoS Flow, and sends the notification endpoint of the application function network element to the application function network element Send the second report information.
  • the first session management network element analyzes the first policy, and can obtain the identification of the first QoS Flow and the notification endpoint information of the application function network element.
  • the first session The management network element determines the notification endpoint of the application function network element carried in the first policy according to the identification of the first QoS Flow carried in the first indication information, and sends the second report information to the notification endpoint, so that the application function network element can receive To the second report information from the first session management network element.
  • the first session management network element may send the second report information to the application function network element through the notification endpoint of the application function network element, thereby realizing the communication between the first session management network element and the application function network element , So that the application function network element can quickly receive the second report information, and adjust the application layer according to the second report information, reducing the transmission delay of the second report information.
  • the first session management network element receives the first policy from the second session management network element, and the first policy includes the notification endpoint information of the application function network element. Specifically, in step 304, the first session management network element sends the second report information to the application function network element according to the first report information, including:
  • the first session management network element determines the notification endpoint of the local network capability opening network element according to the identification of the first QoS Flow, and sends the notification endpoint of the local network capability opening network element to The local network capability opening network element sends the second report information, and the second report information is sent by the local network capability opening network element to the application function network element.
  • the first session management network element analyzes the first policy and can obtain the identification of the first QoS Flow and the notification endpoint information of the local network capability opening network element.
  • a session management network element determines the notification endpoint of the local network capability opening network element carried in the first policy according to the identifier of the first QoS Flow carried in the first indication information, and sends the second report information to the notification endpoint, so that the local network
  • the capability opening network element may receive the second report information from the first session management network element, and the local network capability opening network element sends the second report information to the application function network element.
  • the first session management network element may send the second report information to the local network capability opening network element through the notification endpoint of the local network capability opening network element, and then the local network capability opening network element sends the second report information to the application function network element
  • the second report information thus realizes the communication between the first session management network element and the application function network element, so that the application function network element can quickly receive the second report information, and perform application layer analysis based on the second report information
  • the adjustment reduces the transmission delay of the second report information.
  • the terminal device may also be switched.
  • the terminal device is switched from a first access network network element to a second access network network element, where the first access network network element may be a terminal device
  • the wireless access network where the terminal device is located before the handover, and the second access network network element may be the wireless access network where the terminal device is located after the handover.
  • Step 304 After the first session management network element sends the second report information to the application function network element, the method for sending report information provided in the embodiment of the present application further includes the following steps:
  • the first session management network element receives the QoS Flow identification information from the second access network network element, and the QoS Flow identification information includes The identification of the first QoS Flow;
  • the first session management network element sends third report information to the application function network element, where the third report information includes third indication information, and the third indication information is used to indicate that the QoS requirement of the first service data stream cannot be guaranteed.
  • the second access network element may also send QoS Flow identification information to the first session management network element, for example, the second access network element
  • the first session management network element receives the identification information of the QoS Flow from the second access network network element.
  • the identification information of the QoS Flow includes the identification of the first QoS Flow, and the first QoS Flow is used to transmit the first service data flow.
  • the first session management network element may send third report information to the application function network element, where the third report information includes third indication information, and the third indication information is used to indicate that the QoS requirement of the first service data stream cannot be guaranteed.
  • the application function network element may also receive the third report information from the first session management network element, and adjust the application layer according to the third report information, reducing the third report information Transmission delay.
  • the terminal device may also be switched.
  • the terminal device is switched from a first access network network element to a second access network network element, where the first access network network element may be a terminal device
  • the wireless access network where the terminal device is located before the handover, and the second access network network element may be the wireless access network where the terminal device is located after the handover.
  • the first session management network element receives the identifier of the second candidate QoS document corresponding to the first QoS Flow from the second access network network element;
  • the third report information further includes the identifier of the second candidate service requirement, and the identifier of the second candidate service requirement corresponds to the identifier of the second candidate QoS document.
  • the second access network network element may also send the identification of the second candidate QoS document corresponding to the first QoS Flow to the first session management network element, and the second candidate QoS The document is also a candidate QoS document that meets the QoS requirements of the first QoS Flow.
  • the first session management network element can also determine the second candidate QoS document that meets the QoS requirements of the first QoS Flow, and the first session management network element can determine the second candidate QoS document based on the correspondence between the candidate QoS documents and the candidate service requirements.
  • the identifier of the candidate QoS document corresponds to the identifier of the second candidate service requirement.
  • the first session management network element sends third report information to the application function network element.
  • the third report information also includes the identification of the second candidate service requirement, so that the application function network element can obtain The second candidate QoS document that meets the QoS requirements of the first QoS Flow solves the report indication problem when there are multiple candidate QoS documents.
  • the second report information further includes identification information of the first service data stream.
  • the third report information further includes identification information of the first service data stream.
  • the application function network element may receive the second report information from the first session management network element, or receive the third report information, if the application function network element provides description information of multiple service data streams, for example, there is first service data
  • the second report information and the third report information sent by the first session management network element need to carry the identification information of the first service data stream and the second service data stream.
  • the identification information of the service data flow In the embodiment of the application, the report information sent by the first session management network element to the application function network element carries the identification information of the service data flow, which solves the problem of indicating each service flow when there are multiple service data flows. The question of whether the QoS requirements can be guaranteed.
  • the first session management network element receives the first report information from the user plane network element, the first report information includes the first indication information and the identifier of the first candidate QoS document, and the first indication The information is used to indicate that the QoS requirements of the first QoS Flow cannot be guaranteed; the first session management network element sends the second report information to the application function network element, where the second report information includes the second indication information and the information of the first candidate service requirements ID, the ID of the first candidate service requirement corresponds to the ID of the first candidate QoS document, the second indication information is used to indicate that the QoS requirement of the first service data flow cannot be guaranteed, and the first QoS Flow is used to transmit the first service data flow,
  • the service data flow is the service data flow of the application corresponding to the application function network element.
  • the first session management network element can receive the first report information from the user plane network element, and the first report information carries the first indication information and the identifier of the first QoS document, the first session management network element can be based on the first report information.
  • the instruction information acquires the second instruction information, and the identification of the first candidate service requirement can also be determined according to the identification of the first candidate QoS document. Therefore, the first session management network element can generate the second report information, and the first session management network element sends the application function to the application function.
  • the second report information sent by the management network element indicates that the QoS requirement of the first service data flow cannot be guaranteed through the second indication information in the second report information.
  • the application function network element can determine that the QoS requirements of the first service data flow cannot be guaranteed.
  • the second report information It also carries the identifier of the first candidate service requirement, so that the application function network element can also determine the candidate service requirement, so that the application function network element determines that the QoS requirement of the first service data stream cannot be guaranteed according to the first candidate service requirement Quickly adjust at the application layer. Therefore, the path indicating that the QoS requirements of the first service data flow cannot be guaranteed is greatly shortened.
  • the second report information has high timeliness, which reduces the adjustment of application function network elements at the application layer. Time delay.
  • FIGS. 4a to 4c are three specific application scenarios of the communication system shown in FIG.
  • the first session management network element is I-SMF
  • the user plane network element is Local PSA
  • the application function network element is AF for illustration.
  • FIG. 4a a schematic diagram of the application scenario framework of a communication system provided by an embodiment of this application.
  • the I-SMF is deployed in a local data center.
  • the I-SMF supports the intercommunication between the N33 interface and AF, and the N4 interface and Local PSA interoperability.
  • the communication system may include: UE, RAN, Local PSA, AF, I-SMF, AMF, SMF, PCF, and NEF.
  • N1 interface is configured between AMF and UE
  • N2 interface is configured between AMF and RAN
  • N3 interface is configured between RAN and Local PSA
  • N11 interface is configured between AMF and I-SMF
  • I-SMF and Local N4 interface is configured between PSA
  • N16a interface is configured between I-SMF and SMF
  • N33 interface is configured between I-SMF and AF
  • N6 interface is configured between AF and Local PSA
  • N6 interface is configured between AF and NEF.
  • N33 interface N5 interface is configured between NEF and PCF
  • N7 interface is configured between PCF and SMF.
  • FIG. 4b a schematic diagram of the application scenario framework of a communication system provided by this embodiment of the application.
  • Local NEF and I-SMF are deployed locally.
  • Local NEF supports N33 interface and AF intercommunication, and N33a interface and NEF intercommunication or N5 Interface and PCF, Nx interface and I-SMF intercommunication.
  • the communication system may include: UE, RAN, Local PSA, AF, I-SMF, AMF, Local NEF, SMF, PCF, and NEF.
  • N1 interface is configured between AMF and UE
  • N2 interface is configured between AMF and RAN
  • N3 interface is configured between RAN and Local PSA
  • N11 interface is configured between AMF and I-SMF
  • I-SMF and Local N4 interface is configured between PSA
  • N16a interface is configured between I-SMF and SMF
  • Nx interface is configured between I-SMF and Local NEF
  • N33 interface is configured between Local NEF and AF
  • AF and Local PSA N6 interface is configured
  • N33 interface is configured between Local NEF and NEF
  • N5 interface is configured between Local NEF and PCF
  • N5 interface is configured between NEF and PCF
  • N7 interface is configured between PCF and SMF.
  • the SMF is deployed in a local data center.
  • the communication system may include: UE, RAN, Local PSA, AF, I-SMF, AMF, Local NEF, PCF, and NEF.
  • N1 interface is configured between AMF and UE
  • N2 interface is configured between AMF and RAN
  • N3 interface is configured between RAN and Local PSA
  • N11 interface is configured between AMF and I-SMF
  • I-SMF and Local N4 interface is configured between PSA
  • N7 interface is configured between I-SMF and PCF
  • Nx interface is configured between I-SMF and Local NEF
  • N33 interface is configured between Local NEF and AF
  • AF and Local PSA N6 interface is configured
  • N33 interface is configured between Local NEF and NEF
  • N5 interface is configured between Local NEF and PCF
  • N5 interface is configured between NEF and PCF.
  • FIGS. 4a to 4c are schematic diagrams of the architecture of the next-generation mobile network provided by the embodiments of the application.
  • the embodiments of the application can be used in the architecture of the next-generation mobile network.
  • the main network elements involved in the embodiments of the application are described as follows:
  • RAN is used to implement wireless-related functions
  • Access and mobility management function is responsible for user mobility management, including mobility status management, assigning user temporary identities, authenticating and authorizing users.
  • SMF is responsible for UPF network element selection, UPF network element reselection, IP address allocation, bearer establishment, modification and release, and QoS control. Specifically, SMF can be deployed in the core data center, and I-SMF can be deployed in the local data center.
  • UPF can be deployed in a local data center, for example, UPF can be Local PSA.
  • UPF supports all or part of the following functions: interconnecting PDU sessions with data networks; packet routing and forwarding; data packet inspection.
  • the policy control function includes policy control decision-making and flow-based charging control functions, including user subscription data management functions, policy control functions, charging policy control functions, QoS control, and so on.
  • An application function provides a certain application layer service to the UE.
  • the AF provides a service to the UE, it has requirements for the quality of service QoS policy (Policy) and charging policy (Charging), and needs to notify the network.
  • Policy quality of service
  • Charging charging policy
  • AF also needs application-related information fed back from the core network.
  • AF can be deployed in EAS.
  • the network capability opening function (NEF) mainly supports the network capability opening function, opening network capabilities and services to the outside world, and the 3GPP network function (Network Function, NF) publishes functions and events to other NFs through NEF.
  • the capabilities and events opened by NF can be safely opened to third-party applications.
  • NEF can be deployed in the core data center, and Local NEF can be deployed in the local data center.
  • the PCF determines to carry the notification endpoint, QoS Notification Control information, Alternative QoS parameter set (Parameter Set), AltQosId and AltSerId in the PCC rules according to the application function network element identifier (AFId), notification endpoint, or local report indication.
  • Alternative QoS parameter set includes an AltQosId and corresponding candidate parameters.
  • the QoS Notification Control information is used to indicate that the RAN is required to send a notification whether the QoS requirement can be guaranteed.
  • the SMF sends to the I-SMF the QoS Notification Control information corresponding to the notification endpoint, local report instructions, Alternative QoS Profile, and the correspondence between AltProId and AltSerId.
  • the SMF sends QoS Notification Control event detection information to the Local PSA, which is used to detect the packet information reported by the event for delay measurement.
  • the gNodeB detects the QoS Notification Control event, it sends a user plane data packet to the PSA.
  • the data packet carries the Quality of Service Flow Identifier (QFI), QoS Notification Control event, and AltProId.
  • QFI Quality of Service Flow Identifier
  • the I-SMF performs the mapping from AltProId to AltSerId.
  • the I-SMF judges that the QoS Flow that cannot guarantee the QoS requirements before is in this list based on the accepted QoS Flow list, then the I-SMF judges that the QoS requirements of this QoS Flow can be guaranteed again, and then it reports to the Local NEF or AF sends a notification that QoS requirements can be guaranteed.
  • QoS notification control Notification Control
  • the embodiment of this application is based on the communication system architecture described in FIG. 4a to FIG. 4c.
  • the AF requests event detection through the Local NEF or directly through the NEF.
  • the event may be a QoS Notificaiton control event.
  • the RAN sends the detected QoS Notification Control event report to the Local PSA through the user plane, the Local PSA then sends it to the I-SMF, and the I-SMF is directly sent to the AF or Local NEF.
  • it mainly includes the following interactive processes:
  • S501 The UE establishes a PDU session with the Local.
  • the gNodeB saves the core network tunnel information (CN Tunnel Info) of the Local PSA for accepting uplink data packets, where the CN Tunnel Info usually includes the IP address and the tunnel identifier (TEID) for receiving the uplink data.
  • CN Tunnel Info core network tunnel information
  • TEID tunnel identifier
  • the AF sends a quality of service creation request message to the NEF.
  • the quality of service creation request message may be a Nnef_AFsessionWithQoS_Create request message, and the Nnef_AFsessionWithQoS_Create request message includes the application function network element identifier (AFId) and the UE address.
  • the requested service information (for example, the service information includes service data flow description information, QoS requirements of the service), event identifier (for example, the event identifier may be the identifier of the QoS Notification Control event), and the notification endpoint (Notification Endpoint1a).
  • Notification Endpoint1a includes the target notification address Notification Target Address1a or Notification Target Address1a and Notification Correlation Id1a for receiving event notifications.
  • AF can provide description information of multiple service data streams, and use data stream identifiers to identify them.
  • the AF sends a Nnef_AFsessionWithQoS_Create request message to the Local NEF.
  • the Nnef_AFsessionWithQoS_Create request message includes the AFId, the UE address, the event identifier (for example, the event identifier may be the identifier of the QoS Notification Control event), and the notification endpoint Notification Endpoint1a.
  • Notification Endpoint1a includes the target notification address Notification Target Address1a that receives event notifications, or Notification Target Address1a and Notification Correlation Id1a.
  • Local NEF determines Notification Endpoint1b and maintains the corresponding relationship with Notification Endpoint1a.
  • NEF may also need to send a Nnef_AFsessionWithQoS_Create request message to NEF.
  • the Nnef_AFsessionWithQoS_Create request message needs to carry the information received in step S502, and the Nnef_AFsessionWithQoS_Create request needs to carry Notification Endpoint1b.
  • the service information requested by the AF may also include Alternative Service Requirements (Alternative Service Requirements), and each Alternative Service Requirement uses an Alternative Service Requirement Id (AltSerId for short).
  • Alternative Service Requirements Alternative Service Requirements
  • AltSerId Alternative Service Requirement Id
  • the policy authorization creation message can be the Npcf_PolicyAuthorization_Create message.
  • the Npcf_PolicyAuthorization_Create message includes the AF ID, UE address, requested service information, and event identifier (for example, the event identifier can be QoS Notification Control Event identification), and the information of the notification endpoint. If Local NEF is not deployed, the notification endpoint information can be Notification Endpoint1a, or if Local NEF is deployed, the notification endpoint information can be Notification Endpoint1b.
  • the service information requested by the AF may also include Alternative Service Requirements, and each Alternative Service Requirement uses an Alternative Service Requirement Id (AltSerId for short).
  • the Npcf_PolicyAuthorization_Create message also carries local report indication information, which is used to indicate that a local event report needs to be performed.
  • the PCF makes a policy decision based on the received information to generate a PCC rule.
  • PCC rules are formulated for the PDU session established in step S501.
  • the PCC rules include service information, and the service information may include service data flow templates and QoS parameters.
  • the PCF determines that Notification Endpiont1a or Notification Endpoint1b is included in the PCC rules.
  • the PCF may also carry an explicit local report indication in the PCC rules.
  • the PCC rule can also carry Notification Endpoint1a/Notification Endpoint1b and an explicit local report indication, which are used to indicate that the SMF needs to report events locally.
  • the SMF can still report events to the PCF through control.
  • the PCF can formulate different PCC rules according to the description information of multiple service data flows.
  • the PCF also carries the corresponding service data flow identifiers in the PCC rules.
  • the PCF will also include Alternative QoS Parameter Sets in the PCC rules according to Alternative Service Requirements.
  • Each Alternative QoS Parameter Set is identified by an Alternative QoS Parameter Set Id (AltQosId for short).
  • the PCC rules include the correspondence between AltQosId and AltSerId.
  • the PCF sends the PCC rule to the SMF corresponding to the PDU session.
  • the SMF executes the PCC rules, performs QoS Flow binding according to the QoS parameters carried in the PCC rules, and then decides to create or modify the QoS Flow.
  • the SMF sends a protocol data unit session update request message to the I-SMF, such as a protocol data unit session update request
  • the message may be Nsmf_PDU Session_Update Request message. If a new QoS Flow is created, the SMF can assign the QoS flow identifier to the QoS Flow and formulate a corresponding QoS profile according to the QoS parameters of the PCC rules, and send the QoS flow identifier and the corresponding QoS document to the I-SMF.
  • the SMF does not need to assign an identifier to the modified QoS Flow, but the created QoS document needs to be modified.
  • the SMF sends the QFI and the modified QoS document to the I-SMF.
  • the SMF can also send a message notifying the endpoint to the I-SMF.
  • the PCF provides multiple PCC rules
  • the SMF may bind different PCC rules to different QoS Flows, and the SMF sends the QoS Flow identifier to the I-SMF according to the binding result, and the corresponding notification endpoints and service data flow identifiers relation.
  • the protocol data unit session update request message includes QoS Notification Control indication and local report indication information, which are used to indicate the need for local event reporting or event reporting through the user plane.
  • the protocol data unit session update request message carries local report indication information, which is used to instruct the gNodeB to report the event through the user plane, and it does not exclude the gNodeB from reporting the event through the control plane.
  • the PCC rule carries Alternative QoS Parameter Sets
  • the SMF determines the Alternative QoS Profiles according to the Alternative QoS Parameter Sets, and each Alternative QoS Profile is identified by the Alternative QoS Profile Id (AltProId for short).
  • the SMF carries the correspondence between AltProId and AltSerId in the message.
  • the I-SMF sends a communication message transmission request to the AMF.
  • the communication message transmission request may be a Namf_Communication_N1N2MessageTransfer Request message, and the Namf_Communication_N1N2MessageTransfer Request message carries QFI.
  • the Namf_Communication_N1N2MessageTransfer Request message includes QoS Notification Control indication and local report indication information. If the message in step S509 carries Alternative QoS Profile, the Namf_Communication_N1N2MessageTransfer Request message also carries Alternative QoS Profile.
  • I-SMF saves the corresponding relationship between QFI and notification endpoints, or I-SMF saves the corresponding relationship between QFI, notification endpoints, and business data. Further, the I-SMF saves the correspondence between AltProId and AltSerId.
  • the AMF interacts with the gNodeB, and the AMF sends the information received in step S509 to the gNodeB.
  • the gNodeB further interacts with the UE.
  • the AMF returns a confirmation message to the I-SMF.
  • the I-SMF sends a session modification message to the Local PSA, and the session modification message carries the QFI.
  • the session modification message carries QoS Notification Control information to instruct the Local PSA to detect the data packet sent by the RAN for reporting the QoS Notification Control event, and report it to the I-SMF.
  • the Local PSA returns a confirmation message to the I-SMF.
  • the gNodeB For the QoS Notification Control event, if the gNodeB detects that the QoS requirement of the QoS Profile of the QoS Flow cannot be guaranteed, the gNodeB detects the event. At this time, if the gNodeB has previously received the Alternative QoS Profile, the gNodeB determines the Alternative QoS Profile that can be guaranteed currently. If the QoS of an Alternative QoS Profile being executed by the gNodeB cannot be guaranteed, the gNodeB detects the event. The gNodeB judges other Alternative QoS Profiles that can currently be guaranteed. If the gNodeB has previously sent a notification that the QoS requirement of QoS Flow cannot be guaranteed, and then detects that the GBR of QoS Flow can be guaranteed, the gNodeB detects the event.
  • whether the gNodeB detects whether the QoS requirements of QoS Flow can be guaranteed can include: gNodeB detects the current actual quality of service of QoS Flow, and if the current actual quality of service of QoS Flow meets the QoS requirements of QoS Flow, determine the QoS requirements of QoS Flow If it can be guaranteed, on the contrary, the QoS requirements for determining QoS Flow cannot be guaranteed.
  • gNodeB can detect the minimum transmission rate of a service data flow transmitted on QoS Flow within a period of time, and determine whether the minimum transmission rate of the service data flow meets the transmission rate of guaranteed transmission If the minimum transmission rate of the service data flow is greater than or equal to the guaranteed transmission rate, it is determined that the QoS requirements of QoS Flow can be guaranteed. On the contrary, if the minimum transmission rate of the service data flow is less than the guaranteed transmission rate, then QoS Flow is determined. The QoS requirements cannot be guaranteed.
  • the gNodeB sends a data packet to the Local PSA.
  • the data packet carries the QFI and the indication information that the QoS requirement cannot be guaranteed or the indication information that the QoS requirement can be guaranteed.
  • the gNodeB may also carry the AltProId of the Alternative QoS Profile that can be guaranteed.
  • the gNodeB can include multiple QFIs and corresponding indication information in one data packet.
  • the Local PSA receives the data packet carrying the QoS Notification Control event report, and detects the event.
  • the Local PSA sends an event report to the I-SMF.
  • the Local PSA sends QFI and indication information that cannot guarantee QoS requirements or indication information that can guarantee QoS requirements to I-SMF.
  • the AltProId is also included in the event report.
  • the I-SMF determines the Notification Endpoint1a or Notification Endpoint1b according to QFI. Determine AltSerId based on AltProId. If the I-SMF also saves the corresponding relationship between the QFI and the service data flow identifier, the I-SMF further determines the service data flow identifier.
  • the I-SMF sends an event report to the AF, and the event report carries Notification Endpoint1a.
  • the event report includes the indication information that the QoS requirement cannot be guaranteed or the indication information that the QoS requirement can be guaranteed.
  • the AltSerId is also included in the incident report. It is also possible to include the identification of the business data flow in the event report.
  • the I-SMF sends an event report to the Local NEF, and the event report carries Notification Endpoint1b.
  • the event report includes indication information that cannot guarantee QoS requirements or indication information that can guarantee QoS requirements.
  • the AltSerId is also included in the event report. It is also possible to include the identification of the business data flow in the event report.
  • Local NEF further sends an event report to the AF, and the event report carries Notification Endpoint1a.
  • the event report includes indication information that cannot guarantee QoS requirements or indication information that can guarantee QoS requirements.
  • the AltSerId is also included in the event report. It is also possible to include the identification of the business data flow in the event report.
  • the execution process under the architecture of Figure 4b is similar to the process under the architecture of Figure a, except that the Local NEF sends messages to the NEF in the core data center, and the NEF in the core data center further sends messages to the PCF.
  • the interaction between I-SMF and SMF is omitted, and the Local PSA sends a notification message to the SMF, and the SMF sends a notification message to the Local NEF/AF.
  • the I-SMF judges based on the received QoS flow list that the QoS Flow corresponding to the previously sent indication information that cannot guarantee the QoS requirement is otherwise in this QoS flow list, if there is a QoS flow list ,
  • the Local PSA sends to the Local NEF or AF indication information that can guarantee the QoS requirements. Specifically, it mainly includes the following processes:
  • the network After the UE moves, the network performs cross-gNodeB handover, for example, through Xn-based inter NG-RAN handover or Inter NG-RAN node N2 based handover to complete the handover from the source gNodeB to the target (Target) gNodeB.
  • the target gNodeB sends a QoS Flow list to the AF.
  • the target gNodeB sends a path switch request or a handover request confirmation message.
  • the path switch request can be N2 Path Switch Request
  • the handover request confirmation message can be a handover request Acknowledge message.
  • the path switching request or the switching request confirmation message includes the QoS Flow list (List) accepted by the Target gNodeB, including the accepted QFI list.
  • the QoS flow list may also include the Alternative QoS Profile Id (AltProId for short) of one or more accepted QoS flows.
  • the AMF sends a session management context request message to the SMF.
  • the session management context request message may be a Nsmf_PDUSession_UpdateSMContext Request message, and the Nsmf_PDUSession_UpdateSMContext Request message includes an accepted QoS flow list.
  • the QoS flow list may also include the Alternative QoS Profile Id (AltProId for short) of one or more accepted QoS flows.
  • S604 The SMF returns a confirmation message to the AMF.
  • the I-SMF determines the Notification Endpoint1a according to the QFI of this QoS Flow and sends the event to the AF Report.
  • the event report includes indication information and Notification Endpoint1b that can guarantee QoS requirements. If this QFI has a corresponding AltProId, the I-SMF also carries the corresponding AltSerId in the event report. If the I-SMF also saves the corresponding relationship between the QFI and the service data flow identifier, the I-SMF further determines the service data flow identifier, and includes the service data flow identifier in the event report.
  • the I-SMF determines the Notification Endpoint1b according to the QFI of the QoS Flow and sends it to the Local NEF Event report, the event report includes indication information that can guarantee QoS requirements and Notification Endpoint1b. If this QFI has a corresponding AltProId, the I-SMF also carries the corresponding AltSerId in the event report. If the I-SMF also saves the corresponding relationship between the QFI and the service data flow identifier, the I-SMF further determines the service data flow identifier, and includes the service data flow identifier in the event report.
  • the LocalNEF determines the Notification Endpoint 1a according to the Notification Endpoint 1b and sends an event report to the AF.
  • the event report includes the indication information that can guarantee the QoS requirements and the Notification Endpoint 1b.
  • the event report may also carry AltSerId.
  • the event report may also carry the identifier of the service data stream.
  • the gNodeB reports the QoS Notification Control event to the Local PSA through the user, and the Local PSA reports the QoS Notification Control event to the I-SMF.
  • the I-SMF determines the AltSerId according to the AltProId. I-SMF reports events to AF or Local AF.
  • the I-SMF judges that the GBR QoS Flow cannot be guaranteed before is in this list, and the I-SMF sends the event and AltSerId that can guarantee the GBR to the Local NEF or AF.
  • the I-SMF directly sends the detected QoS Notification Control to the local application, which reduces network delay and can also solve the problem of event reporting during handover.
  • UPF can send event reports directly to local applications, reducing circuitous routing.
  • the AMF can directly interact with the SMF, and the SMF sends a notification message to the Local NEF/AF. Reduce the network delay, but also solve the problem of event reporting during handover. UPF can send event reports directly to local applications, reducing circuitous routing.
  • a first session management network element 700 provided by an embodiment of the present application may include: a receiving module 701, a processing module 702, and a sending module 703, where:
  • the processing module 702 is configured to receive first report information from a user plane network element through the receiving module 701, where the first report information includes first indication information and an identifier of a first candidate quality of service QoS document, and the first indication information
  • the QoS requirement used to indicate the first quality of service flow QoS Flow cannot be guaranteed;
  • the processing module 702 is configured to send second report information to the application function network element through the sending module 703, where the second report information includes the second indication information and the identifier of the first candidate service requirement, and the first candidate service requirement
  • the identifier corresponds to the identifier of the first candidate QoS document
  • the second indication information is used to indicate that the QoS requirements of the first service data flow cannot be guaranteed
  • the first QoS Flow is used to transmit the first service data flow
  • the first service data flow is a service data flow of an application corresponding to the application function network element.
  • the second indication information is determined according to the first indication information.
  • the processing module 702 is configured to receive through the receiving module 701 before receiving the first report information from the user plane network element when the first session management network element is an intermediate session management network element A first policy from a second session management network element, where the first policy includes the identifier of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, and the notification endpoint of the application function network element And the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS document, and the identification of the at least one candidate service requirement includes The identifier of the first candidate service requirement, and the first QoS notification control indication information is used to indicate whether the QoS requirement for sending the first QoS Flow can be guaranteed;
  • the processing module 702 is configured to determine a second policy according to the first policy, and send the second policy to the first access network element through the sending module 703, where the second policy includes the first policy An identifier of a QoS Flow, second QoS notification control indication information, and the at least one candidate QoS document, where the second QoS notification control indication information is determined according to the first QoS notification control indication information.
  • the processing module 702 is configured to receive through the receiving module 701 before receiving the first report information from the user plane network element when the first session management network element is an intermediate session management network element A first policy from a second session management network element, where the first policy includes the identifier of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, and the notification endpoint of the application function network element And the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS document, and the identification of the at least one candidate service requirement includes The identifier of the first candidate service requirement, and the first QoS notification control indication information is used to indicate whether the QoS requirement for sending the first QoS Flow can be guaranteed;
  • the processing module 702 is configured to determine a third policy according to the first policy, and send the third policy to the user plane network element through the sending module 703, where the third policy is used to instruct the user plane network element Send the indication information of whether the QoS requirements of the first QoS Flow can be guaranteed.
  • the processing module 702 is configured to determine the status of the application function network element according to the identifier of the first QoS Flow when the first indication information includes the identifier of the first QoS Flow Notify the endpoint, and send the second report information to the application function network element through the notification endpoint of the application function network element.
  • the processing module 702 is configured to receive through the receiving module 701 before receiving the first report information from the user plane network element when the first session management network element is an intermediate session management network element
  • the first policy from the second session management network element, the first policy includes the identification of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, and the notification endpoint of the local network capability opening network element
  • the identifier of at least one candidate service requirement corresponding to the identifier of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS document, and the identifier of the at least one candidate service requirement includes The identifier of the first candidate service requirement, and the first QoS notification control indication information is used to indicate whether the QoS requirement for sending the first QoS Flow can be guaranteed;
  • the processing module 702 is configured to determine a second policy according to the first policy, and send the second policy to the first access network element through the sending module 703, where the second policy includes the first QoS Flow identifier, second QoS notification control indication information, and the at least one candidate QoS document, and the second QoS notification control indication information is determined according to the first QoS notification control indication information.
  • the processing module 702 is configured to receive through the receiving module 701 before receiving the first report information from the user plane network element when the first session management network element is an intermediate session management network element
  • the first policy from the second session management network element, the first policy includes the identifier of the first QoS Flow, the first QoS notification control indication information, at least one candidate QoS document, and the notification endpoint of the local network capability opening network element
  • the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document, wherein the at least one candidate QoS document includes the first candidate QoS document, and the identification of the at least one candidate service requirement includes The identifier of the first candidate service requirement, and the first QoS notification control indication information is used to indicate whether the QoS requirement for sending the first QoS Flow can be guaranteed;
  • the processing module 702 is configured to determine a third policy according to the first policy, and send the third policy to the user plane network element through the sending module 703, where the third policy is used to instruct the user plane network element Send the indication information of whether the QoS requirements of the first QoS Flow can be guaranteed.
  • the processing module 702 is configured to determine the local network capability opening network according to the identifier of the first QoS Flow when the first indication information includes the identifier of the first QoS Flow And send the second report information to the local network capability opening network element through the notification endpoint of the local network capability opening network element, and the second report information is sent by the local network capability opening network element Send to the application function network element.
  • the first policy is generated by the second session management network element according to a fourth policy from a policy control network element, and the fourth policy includes at least one candidate QoS parameter set and the An identifier of at least one candidate service requirement corresponding to an identifier of at least one candidate QoS parameter set, the at least one candidate QoS parameter set is used by the second session management network element to determine the at least one candidate QoS document, and the at least one candidate The identifier of the at least one candidate service requirement corresponding to the identifier of the QoS parameter set is used by the second session management network element to determine the identifier of the at least one candidate service requirement corresponding to the identifier of the at least one candidate QoS document, wherein the at least one The identifier of the candidate business requirement includes the identifier of the first candidate business requirement.
  • the processing module 702 is configured to receive a fourth policy from the policy control network element through the receiving module 701 before receiving the first report information from the user plane network element, where the fourth policy includes at least One candidate QoS parameter set and an identifier of at least one candidate service requirement corresponding to the identifier of the at least one candidate QoS parameter set, wherein the identifier of the at least one candidate service requirement includes the identifier of the first candidate service requirement;
  • the processing module 702 is configured to determine the at least one candidate QoS document according to the at least one candidate QoS parameter set, and determine the identification of at least one candidate service requirement corresponding to the identification of the at least one candidate QoS document.
  • the processing module 702 is configured to send the second report information to the application function network element, when the terminal device switches from the first access network network element to the second access network network element, pass
  • the receiving module 701 receives the identification information of the QoS Flow from the network element of the second access network, where the identification information of the QoS Flow includes the identification of the first QoS Flow; sends to the application function network element through the sending module 703
  • the third report information where the third report information includes third indication information, and the third indication information is used to indicate that the QoS requirement of the first service data stream cannot be guaranteed.
  • the processing module 702 is configured to receive the identifier of the second candidate QoS document corresponding to the first QoS Flow from the second access network network element through the receiving module 701;
  • the third report information further includes the identifier of the second candidate service requirement, and the identifier of the second candidate service requirement corresponds to the identifier of the second candidate QoS document.
  • the second report information further includes identification information of the first service data stream.
  • the third report information further includes identification information of the first service data stream.
  • a policy control network element 800 provided by an embodiment of the present application may include: a receiving module 801, a processing module 802, and a sending module 803, where:
  • the processing module 802 is configured to receive a service request from an application function network element through the receiving module 801, the service request including first quality of service QoS notification control indication information and at least one candidate service requirement, the first QoS notification control indication information Indication information used to indicate whether the QoS requirements of the first service data stream can be guaranteed;
  • the processing module 802 is configured to generate a fourth policy according to the service request, where the fourth policy includes second QoS notification control indication information, at least one candidate QoS parameter set, and all corresponding to the identifier of the at least one candidate QoS parameter set.
  • the processing module 802 is configured to send the fourth policy to the first session management network element through the sending module 803.
  • the service request further includes the identification information of the first service data flow
  • the fourth policy further includes the identification information of the first service data flow
  • An embodiment of the present application also provides a computer storage medium, wherein the computer storage medium stores a program, and the program executes some or all of the steps recorded in the above method embodiments.
  • the first session management network element 900 includes:
  • the receiver 901, the transmitter 902, the processor 903, and the memory 904 (the number of the processors 903 in the first session management network element 900 may be one or more, and one processor is taken as an example in FIG. 9).
  • the receiver 901, the transmitter 902, the processor 903, and the memory 904 may be connected by a bus or in other ways, where the bus connection is taken as an example in FIG. 9.
  • the memory 904 may include a read-only memory and a random access memory, and provides instructions and data to the processor 903. A part of the memory 904 may also include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 904 stores an operating system and operating instructions, executable modules or data structures, or a subset of them, or an extended set of them.
  • the operating instructions may include various operating instructions for implementing various operations.
  • the operating system may include various system programs for implementing various basic services and processing hardware-based tasks.
  • the processor 903 controls the operation of the first session management network element, and the processor 903 may also be referred to as a central processing unit (CPU).
  • the components of the first session management network element are coupled together through a bus system, where the bus system may include a power bus, a control bus, a status signal bus, etc., in addition to a data bus.
  • bus system may include a power bus, a control bus, a status signal bus, etc., in addition to a data bus.
  • various buses are referred to as bus systems in the figure.
  • the method disclosed in the foregoing embodiment of the present application may be applied to the processor 903 or implemented by the processor 903.
  • the processor 903 may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 903 or instructions in the form of software.
  • the aforementioned processor 903 may be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or Other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processing
  • ASIC application specific integrated circuit
  • FPGA field-programmable gate array
  • Other programmable logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory 904, and the processor 903 reads the information in the memory 904, and completes the steps of the foregoing method in combination with its hardware.
  • the receiver 901 can be used to receive input digital or character information, and to generate signal input related to the relevant settings and function control of the first session management network element.
  • the transmitter 902 can include display devices such as a display screen.
  • the transmitter 902 can be used to pass The external interface outputs digital or character information.
  • the processor 903 is configured to execute the method for sending report information executed by the aforementioned first session management network element.
  • the policy control network element 1000 includes:
  • the receiver 1001, the transmitter 1002, the processor 1003, and the memory 1004 (the number of processors 1003 in the policy control network element 1000 may be one or more, and one processor is taken as an example in FIG. 10).
  • the receiver 1001, the transmitter 1002, the processor 1003, and the memory 1004 may be connected by a bus or in other ways. In FIG. 10, a bus connection is taken as an example.
  • the memory 1004 may include a read-only memory and a random access memory, and provides instructions and data to the processor 1003. A part of the memory 1004 may also include NVRAM.
  • the memory 1004 stores an operating system and operating instructions, executable modules or data structures, or a subset of them, or an extended set of them.
  • the operating instructions may include various operating instructions for implementing various operations.
  • the operating system may include various system programs for implementing various basic services and processing hardware-based tasks.
  • the processor 1003 controls the operation of the network element by controlling the strategy, and the processor 1003 may also be referred to as a CPU.
  • the various components of the strategy control network element are coupled together through a bus system, where the bus system may include a power bus, a control bus, and a status signal bus in addition to a data bus.
  • bus system may include a power bus, a control bus, and a status signal bus in addition to a data bus.
  • various buses are referred to as bus systems in the figure.
  • the methods disclosed in the foregoing embodiments of the present application may be applied to the processor 1003 or implemented by the processor 1003.
  • the processor 1003 may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method can be completed by an integrated logic circuit of hardware in the processor 1003 or instructions in the form of software.
  • the aforementioned processor 1003 may be a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or a processor, or may be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory 1004, and the processor 1003 reads the information in the memory 1004, and completes the steps of the foregoing method in combination with its hardware.
  • the processor 1003 is configured to execute a method for sending report information executed by a policy control network element.
  • the chip when the first session management network element and the policy control network element are chips, the chip includes a processing unit and a communication unit.
  • the processing unit may be a processor, and the communication unit may, for example, be a processor. It is the input/output interface, pin or circuit, etc.
  • the processing unit can execute the computer-executable instructions stored in the storage unit, so that the chip in the terminal executes the method for sending wireless report information according to any one of the above-mentioned first aspects.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit in the terminal located outside the chip, such as a read-only memory (read-only memory). -only memory, ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), etc.
  • the processor mentioned in any one of the foregoing may be a general-purpose central processing unit, a microprocessor, an ASIC, or one or more integrated circuits used to control the execution of the programs of the foregoing methods.
  • the device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physically separate.
  • the physical unit can be located in one place or distributed across multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the connection relationship between the modules indicates that they have a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.
  • this application can be implemented by means of software plus necessary general hardware.
  • it can also be implemented by dedicated hardware including dedicated integrated circuits, dedicated CPUs, dedicated memory, Dedicated components and so on to achieve.
  • all functions completed by computer programs can be easily implemented with corresponding hardware.
  • the specific hardware structures used to achieve the same function can also be diverse, such as analog circuits, digital circuits or special-purpose circuits. Circuit etc.
  • software program implementation is a better implementation in more cases.
  • the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, such as a computer floppy disk. , U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., including several instructions to make a computer device (which can be a personal computer, server, or network device, etc.) execute the methods described in each embodiment of this application .
  • a computer device which can be a personal computer, server, or network device, etc.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • 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 instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • wired such as coaxial cable, optical fiber, digital subscriber line (DSL)
  • wireless such as infrared, wireless, microwave, etc.
  • the computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开报告信息的发送方法和通信装置以及通信系统,用于缩短上报信息的传输路径,减少应用功能网元的处理时延。一种报告信息的发送方法包括:第一会话管理网元接收来自用户面网元的第一报告信息,第一报告信息包括第一指示信息和第一候选QoS文档的标识,第一指示信息用于指示第一QoS Flow的QoS需求不能得到保障;第一会话管理网元向应用功能网元发送第二报告信息,第二报告信息包括第二指示信息和第一候选业务需求的标识,第一候选业务需求的标识对应第一候选QoS文档的标识,第二指示信息用于指示第一业务数据流的QoS需求不能得到保障,第一QoS Flow用于传输第一业务数据流,第一业务数据流是应用功能网元对应的应用的业务数据流。

Description

报告信息的发送方法和通信装置以及通信系统
本申请要求于2020年1月23日提交中国专利局、申请号为2020010077131.5、发明名称为“报告信息的发送方法和通信装置以及通信系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,尤其涉及报告信息的发送方法和通信装置以及通信系统。
背景技术
在第五代移动通信系统(5th generation wireless systems,5G)中,用户设备(user equipment,UE)接入网络后建立协议数据单元(protocol data unit,PDU)会话,并通过PDU会话访问外部的数据网络(data network,DN),与部署在DN中的应用服务器交互。根据用户访问的DN不同,会话管理功能(session management function,SMF)可以选择接入DN的用户面功能(user plane function,UPF),并通过UPF访问应用服务器。同一个应用的应用服务器可以部署在多个位置,SMF能够根据UE的接入位置选择靠近UE同时又能支持UE访问DN的UPF,以便减少路由迂回,降低网络延迟。通常,这些应用服务器可部署在移动边缘计算(mobile edge compute,MEC)环境中。应用需要感知到业务数据流传输路径的服务质量(quality of service,QoS)信息,以便在应用层执行相应的调整。
目前,应用可以通过如下方式获取QoS信息:应用功能(application function,AF)向网络能力开放功能(network exposure function,NEF)发送QoS控制通知(control notification)请求,Qos控制通知请求用于请求获取业务数据流传输的QoS信息,NEF将Qos控制通知请求发送给策略控制功能(policy control function,PCF)。PCF接收到Qos控制通知请求之后,制定相应的QoS策略并将该QoS策略发送给SMF。SMF执行QoS策略并生成执行结果,SMF通过接入和移动性管理功能(access and mobility management function,AMF)向无线接入网(radio access network,RAN)发送执行结果。RAN可以根据该执行结果对QoS流(flow)进行判断以生成QoS信息,例如RAN判断QoS流的保障流比特速率(guaranteed flow bit rate,GFBR)不能保证时,RAN通过如下路径发送GFBR无法保证的通知:RAN->AMF->SMF->PCF->NEF->AF,最终才能使得AF接收到GFBR无法保证的通知,AF接收到该通知后可以在应用层执行相应的调整。
通过对QoS信息的获取方式的说明可知,需要通过“RAN->AMF->SMF->PCF->NEF->AF”复杂路径才能完成RAN与AF的通信,该路径太长,对于时间敏感性较高的业务,QoS信息的时效性差,使得AF在应用层做出调整时存在较大时延。
发明内容
本申请实施例提供了报告信息的发送方法和通信装置以及通信系统,用于缩短上报信息的传输路径,减少应用功能网元的处理时延。
为解决上述技术问题,本申请实施例提供以下技术方案:
第一方面,本申请实施例提供一种报告信息的发送方法,包括:第一会话管理网元接收来自用户面网元的第一报告信息,所述第一报告信息包括第一指示信息和第一候选服务质量QoS文档的标识,所述第一指示信息用于指示第一服务质量流QoS Flow的QoS需求不能得到保障;所述第一会话管理网元向应用功能网元发送第二报告信息,其中,所述第二报告信息包括第二指示信息和第一候选业务需求的标识,所述第一候选业务需求的标识对应所述第一候选QoS文档的标识,所述第二指示信息用于指示第一业务数据流的QoS需求不能得到保障,所述第一QoS Flow用于传输所述第一业务数据流,所述第一业务数据流是所述应用功能网元对应的应用的业务数据流。在上述方案中,由于第一会话管理网元可以从用户面网元接收到第一报告信息,该第一报告信息中携带第一指示信息和第一QoS文档的标识,因此第一会话管理网元可以根据第一指示信息获取第二指示信息,还可以根据第一候选QoS文档的标识确定第一候选业务需求的标识,因此第一会话管理网元可以生成第二报告信息,第一会话管理网元向应用功能管理网元发送的第二报告信息,通过该第二报告信息中的第二指示信息指示第一业务数据流的QoS需求不能得到保障。本申请实施例中基于“用户面网元-第一会话管理网元-应用功能网元”路径可以使得应用功能网元确定第一业务数据流的QoS需求不能得到保障,另外第二报告信息中还携带第一候选业务需求的标识,从而使得应用功能网元还可以确定出候选业务需求,以便于应用功能网元在确定第一业务数据流的QoS需求不能得到保障时根据第一候选业务需求在应用层快速调整。因此极大地缩短了指示第一业务数据流的QoS需求不能得到保障的路径,对于时间敏感性较高的业务,第二报告信息的时效性高,降低了应用功能网元在应用层做出调整时的时延。
在一种可能的实现方式中,所述第二指示信息根据所述第一指示信息确定。在上述方案中,第二指示信息是根据第一指示信息携带的指示内容生成的,第一指示信息指示第一QoS Flow的QoS需求不能得到保障,第一会话管理网元根据第一QoS Flow的QoS需求不能得到保障确定第一QoS Flow传输的第一业务数据流的QoS需求不能得到保障,在第二指示信息中携带第一业务数据流的QoS需求不能得到保障。
在一种可能的实现方式中,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:所述第一会话管理网元接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;所述第一会话管理网元根据所述第一策略确定第二策略,并向所述第一接入网网元发送所述第二策略,其中,所述第二策略包括所述第一QoS Flow的标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知控制指示信息根据所述第一QoS通知控制指示信息确定。在上述方案中,第一接入网网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第二策略,第一接入网网元解析该第二策略,第一接入网网元可以获取到第一QoS Flow的标识、第二QoS通知控制指示信息和至少一个候选QoS文档,第二QoS通知控制指示信息 用于指示发送第一QoS Flow的QoS需求不能得到保障的指示信息,例如第二QoS通知控制指示信息指示第一接入网网元向用户面网元发送第一指示信息,使得用户面网元能够根据第一指示信息生成第一报告信息,并向第一会话管理网元发送第一报告信息,实现了第一报告信息的快速上报。
在一种可能的实现方式中,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:所述第一会话管理网元接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;所述第一会话管理网元根据所述第一策略确定第三策略,并向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息。在上述方案中,用户面网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第三策略,用户面网元解析该第三策略,用户面网元按照第三策略的指示,需要发送第一QoS Flow的QoS需求能否得到保障的指示信息,例如用户面网元在确定第一QoS Flow的QoS需求不能得到保障时,发送前述的携带第一指示信息的第一报告信息,实现了第一报告信息的快速上报。
在一种可能的实现方式中,所述第一会话管理网元向应用功能网元发送第二报告信息,包括:当所述第一指示信息包括所述第一QoS Flow的标识时,所述第一会话管理网元根据所述第一QoS Flow的标识确定所述应用功能网元的通知端点,并通过所述应用功能网元的通知端点向所述应用功能网元发送所述第二报告信息。在上述方案中,第一会话管理网元接收到第一策略之后,第一会话管理网元解析该第一策略,可以获取到第一QoS Flow的标识和应用功能网元的通知端点的信息,第一会话管理网元根据第一指示信息中携带的第一QoS Flow的标识确定第一策略中携带的应用功能网元的通知端点,并向该通知端点发送第二报告信息,从而应用功能网元可以接收到来自第一会话管理网元的第二报告信息。本申请实施例中,第一会话管理网元可以通过应用功能网元的通知端点向应用功能网元发送第二报告信息,从而实现了第一会话管理网元和应用功能网元之间的通信,使得应用功能网元可以快速的接收到第二报告信息,并根据第二报告信息进行应用层的调整,降低了第二报告信息的传输时延。
在一种可能的实现方式中,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:所述第一会话管理网元接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;所述第一会话管理网元根 据所述第一策略确定第二策略,并向所述第一接入网网元发送所述第二策略,所述第二策略包括所述第一QoS Flow标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知控制指示信息根据所述第一QoS通知控制指示信息确定。在上述方案中,第一接入网网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第二策略,第一接入网网元解析该第二策略,第一接入网网元可以获取到第一QoS Flow的标识、第二QoS通知控制指示信息和至少一个候选QoS文档,第二QoS通知控制指示信息用于指示发送第一QoS Flow的QoS需求不能得到保障的指示信息,例如第二QoS通知控制指示信息指示第一接入网网元向用户面网元发送第一指示信息,使得用户面网元能够根据第一指示信息生成第一报告信息,并向第一会话管理网元发送第一报告信息,实现了第一报告信息的快速上报。
在一种可能的实现方式中,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:所述第一会话管理网元接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;所述第一会话管理网元根据所述第一策略确定第三策略,并向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息。在上述方案中,用户面网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第三策略,用户面网元解析该第三策略,用户面网元按照第三策略的指示,需要发送第一QoS Flow的QoS需求能否得到保障的指示信息,例如用户面网元在确定第一QoS Flow的QoS需求不能得到保障时,发送前述的携带第一指示信息的第一报告信息,实现了第一报告信息的快速上报。
在一种可能的实现方式中,所述第一会话管理网元向应用功能网元发送第二报告信息,包括:当所述第一指示信息包括所述第一QoS Flow的标识时,所述第一会话管理网元根据所述第一QoS Flow的标识确定所述本地网络能力开放网元的通知端点,并通过所述本地网络能力开放网元的通知端点向所述本地网络能力开放网元发送所述第二报告信息,所述第二报告信息由所述本地网络能力开放网元向所述应用功能网元发送。在上述方案中,第一会话管理网元接收到第一策略之后,第一会话管理网元解析该第一策略,可以获取到第一QoS Flow的标识和本地网络能力开放网元的通知端点的信息,第一会话管理网元根据第一指示信息中携带的第一QoS Flow的标识确定第一策略中携带的本地网络能力开放网元的通知端点,并向该通知端点发送第二报告信息,从而本地网络能力开放网元可以接收到来自第一会话管理网元的第二报告信息,本地网络能力开放网元向应用功能网元发送该第二报告信息。本申请实施例中,第一会话管理网元可以通过本地网络能力开放网元的通知端点向本地网络能力开放网元发送第二报告信息,再由本地网络能力开放网元向应用功能网元发送该第二报告信息,从而实现了第一会话管理网元和应用功能网元之间的通信,使得应用功能网元可以快速的接收到第二报告信息,并根据第二报告信息进行应用层的调整,降 低了第二报告信息的传输时延。
在一种可能的实现方式中,所述第一策略由所述第二会话管理网元根据来自策略控制网元的第四策略生成,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,所述至少一个候选QoS参数集用于所述第二会话管理网元确定所述至少一个候选QoS文档,所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识用于所述第二会话管理网元确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识。在上述方案中,第二会话管理网元接收来自策略控制网元的第四策略,第二会话管理网元解析第四策略,并确定出至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,至少一个候选QoS参数集用于确定至少一个候选QoS文档;第二会话管理网网元生成第一策略,第二会话管理网元生成的第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。第二会话管理网元通过和策略控制网元的交互,可以生成第一策略,使得第二会话管理网元可以向第一会话管理网元发送第一策略。
在一种可能的实现方式中,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:所述第一会话管理网元接收来自策略控制网元的第四策略,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识;所述第一会话管理网元根据至少一个候选QoS参数集确定所述至少一个候选QoS文档,并确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。在上述方案中,第一会话管理网元接收来自策略控制网元的第四策略,第一会话管理网元解析第四策略,并确定出至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,至少一个候选QoS参数集用于确定至少一个候选QoS文档;第一会话管理网网元生成第一策略,第一会话管理网元生成的第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。第一会话管理网元通过和策略控制网元的交互,可以生成第一策略。
在一种可能的实现方式中,所述第一会话管理网元向应用功能网元发送第二报告信息之后,所述方法还包括:当终端设备从第一接入网网元切换至第二接入网网元时,所述第一会话管理网元接收来自所述第二接入网网元的QoS Flow的标识信息,所述QoS Flow的标识信息包括所述第一QoS Flow的标识;所述第一会话管理网元向所述应用功能网元发送第三报告信息,其中,所述第三报告信息包括第三指示信息,所述第三指示信息用于指示所述第一业务数据流的QoS需求不能得到保障。在上述方案中,终端设备从第一接入网网元切换至第二接入网网元时,第二接入网网元还可以向第一会话管理网元发送QoS Flow的标识信息,例如第二接入网网元和AMF之间建立有N2接口,AMF和第一会话管理网元之间建立有N11接口,第一会话管理网元接收来自第二接入网网元的QoS Flow的标识信息,QoS Flow的标识信息包括第一QoS Flow的标识,第一QoS Flow用于传输第一业务数据流。第一会话 管理网元可以向应用功能网元发送第三报告信息,其中,第三报告信息包括第三指示信息,第三指示信息用于指示第一业务数据流的QoS需求不能得到保障。本申请实施例中在终端设备发生切换时,应用功能网元也可以从第一会话管理网元接收到第三报告信息,并根据第三报告信息进行应用层的调整,降低了第三报告信息的传输时延。
在一种可能的实现方式中,所述方法还包括:所述第一会话管理网元接收来自所述第二接入网网元的所述第一QoS Flow对应的第二候选QoS文档的标识;其中,所述第三报告信息还包括第二候选业务需求的标识,所述第二候选业务需求的标识对应所述第二候选QoS文档的标识。在上述方案中,第一QoS Flow的QoS需求不能得到保障时,第二接入网网元还可以向第一会话管理网元发送第一QoS Flow对应的第二候选QoS文档的标识,第二候选QoS文档也是满足第一Qos Flow的QoS需求的候选QoS文档。此时,第一会话管理网元还可以确定出满足第一Qos Flow的QoS需求的第二候选QoS文档,第一会话管理网元根据候选QoS文档和候选业务需求的对应关系可以确定出第二候选QoS文档的标识对应的第二候选业务需求的标识。第一会话管理网元向应用功能网元发送第三报告信息,第三报告信息除了包括第三指示信息,第三报告信息还包括第二候选业务需求的标识,从而使得应用功能网元可以获取到满足第一Qos Flow的QoS需求的第二候选QoS文档,解决了存在多个候选QoS文档时的报告指示问题。
在一种可能的实现方式中,所述第二报告信息还包括所述第一业务数据流的标识信息。在上述方案中,应用功能网元可以从第一会话管理网元接收到第二报告信息,若应用功能网元提供多个业务数据流的描述信息,例如存在第一业务数据流和第二业务数据流的QoS需求能否得到保障的指示时,在第一会话管理网元发送的第二报告信息中需要携带第一业务数据流的标识信息和第二业务数据流的标识信息,本申请实施例中第一会话管理网元向应用功能网元发送的报告信息中携带业务数据流的标识信息,解决了存在多个业务数据流时指示每个业务流的QoS需求能否得到保障的指示问题。
在一种可能的实现方式中,所述第三报告信息还包括所述第一业务数据流的标识信息。在上述方案中,应用功能网元可以从第一会话管理网元接收到第三报告信息,若应用功能网元提供多个业务数据流的描述信息,例如存在第一业务数据流和第二业务数据流的QoS需求能否得到保障的指示时,在第一会话管理网元发送的第三报告信息中需要携带第一业务数据流的标识信息和第二业务数据流的标识信息,本申请实施例中第一会话管理网元向应用功能网元发送的报告信息中携带业务数据流的标识信息,解决了存在多个业务数据流时指示每个业务流的QoS需求能否得到保障的指示问题。
第二方面,本申请实施例还提供一种报告信息的发送方法,包括:用户面网元向第一会话管理网元发送第一报告信息,所述第一报告信息包括第一指示信息和第一候选服务质量QoS文档的标识,所述第一指示信息用于指示第一服务质量流QoS Flow的QoS需求不能得到保障;所述第一会话管理网元接收来自所述用户面网元的所述第一报告信息;所述第一会话管理网元向应用功能网元发送第二报告信息,所述第二报告信息包括第二指示信息和第一候选业务需求的标识,所述第一候选业务需求的标识对应所述第一候选QoS文档的标识,所述第二指示信息用于指示第一业务数据流的QoS需求不能得到保障,所述第一QoS Flow用于传输所述第一业务数据流,所述第一业务数据流是所述应用功能网元对应的应用 的业务数据流;所述应用功能网元接收所述第一会话管理网元发送的所述第二报告信息。在上述方案中,由于第一会话管理网元可以从用户面网元接收到第一报告信息,该第一报告信息中携带第一指示信息和第一QoS文档的标识,因此第一会话管理网元可以根据第一指示信息获取第二指示信息,还可以根据第一候选QoS文档的标识确定第一候选业务需求的标识,因此第一会话管理网元可以生成第二报告信息,第一会话管理网元向应用功能管理网元发送的第二报告信息,通过该第二报告信息中的第二指示信息指示第一业务数据流的QoS需求不能得到保障。本申请实施例中基于“用户面网元-第一会话管理网元-应用功能网元”路径可以使得应用功能网元确定第一业务数据流的QoS需求不能得到保障,另外第二报告信息中还携带第一候选业务需求的标识,从而使得应用功能网元还可以确定出候选业务需求,以便于应用功能网元在确定第一业务数据流的QoS需求不能得到保障时根据第一候选业务需求在应用层快速调整。因此极大地缩短了指示第一业务数据流的QoS需求不能得到保障的路径,对于时间敏感性较高的业务,第二报告信息的时效性高,降低了应用功能网元在应用层做出调整时的时延。
在一种可能的实现方式中,所述第二指示信息根据所述第一指示信息确定。在上述方案中,第二指示信息是根据第一指示信息携带的指示内容生成的,第一指示信息指示第一QoS Flow的QoS需求不能得到保障,第一会话管理网元根据第一QoS Flow的QoS需求不能得到保障确定第一QoS Flow传输的第一业务数据流的QoS需求不能得到保障,在第二指示信息中携带第一业务数据流的QoS需求不能得到保障。
在一种可能的实现方式中,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:第二会话管理网元向所述第一会话管理网元发送第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求不能得到保障的指示信息;所述第一会话管理网元接收来自所述第二会话管理网元的所述第一策略;所述第一会话管理网元根据所述第一策略确定第二策略,并向所述第一接入网网元发送所述第二策略,其中,所述第二策略包括所述第一QoS Flow的标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知控制指示信息根据所述第一QoS通知控制指示信息确定;所述第一接入网网元接收所述第二策略。在上述方案中,第一接入网网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第二策略,第一接入网网元解析该第二策略,第一接入网网元可以获取到第一QoS Flow的标识、第二QoS通知控制指示信息和至少一个候选QoS文档,第二QoS通知控制指示信息用于指示发送第一QoS Flow的QoS需求不能得到保障的指示信息,例如第二QoS通知控制指示信息指示第一接入网网元向用户面网元发送第一指示信息,使得用户面网元能够根据第一指示信息生成第一报告信息,并向第一会话管理网元发送第一报告信息,实现了第一报告信息的快速上报。
在一种可能的实现方式中,当所述第一会话管理网元为中间会话管理网元时,所述第 一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:第二会话管理网元向所述第一会话管理网元发送第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;所述第一会话管理网元接收来自所述第二会话管理网元的所述第一策略;所述第一会话管理网元根据所述第一策略确定第三策略,并向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;所述用户面网元接收所述第三策略。在上述方案中,用户面网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第三策略,用户面网元解析该第三策略,用户面网元按照第三策略的指示,需要发送第一QoS Flow的QoS需求能否得到保障的指示信息,例如用户面网元在确定第一QoS Flow的QoS需求不能得到保障时,发送前述的携带第一指示信息的第一报告信息,实现了第一报告信息的快速上报。
在一种可能的实现方式中,所述第一会话管理网元根据所述第一报告信息向应用功能网元发送第二报告信息,包括:当所述第一指示信息包括所述第一QoS Flow的标识时,所述第一会话管理网元根据所述第一QoS Flow的标识确定所述应用功能网元的通知端点,并通过所述应用功能网元的通知端点向所述应用功能网元发送所述第二报告信息。在上述方案中,第一会话管理网元接收到第一策略之后,第一会话管理网元解析该第一策略,可以获取到第一QoS Flow的标识和应用功能网元的通知端点的信息,第一会话管理网元根据第一指示信息中携带的第一QoS Flow的标识确定第一策略中携带的应用功能网元的通知端点,并向该通知端点发送第二报告信息,从而应用功能网元可以接收到来自第一会话管理网元的第二报告信息。本申请实施例中,第一会话管理网元可以通过应用功能网元的通知端点向应用功能网元发送第二报告信息,从而实现了第一会话管理网元和应用功能网元之间的通信,使得应用功能网元可以快速的接收到第二报告信息,并根据第二报告信息进行应用层的调整,降低了第二报告信息的传输时延。
在一种可能的实现方式中,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:第二会话管理网元向所述第一会话管理网元发送第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;所述第一会话管理网元接收来自所述第二会话管理网元的所述第一策略;所述第一会话管理网元根据所述第一策略确定第二策略,并向所述第一接入网网元发送所述第二策略,所述第二策略包括所述第一QoS Flow标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知 控制指示信息根据所述第一QoS通知控制指示信息确定;所述第一接入网网元接收所述第二策略。在上述方案中,第一接入网网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第二策略,第一接入网网元解析该第二策略,第一接入网网元可以获取到第一QoS Flow的标识、第二QoS通知控制指示信息和至少一个候选QoS文档,第二QoS通知控制指示信息用于指示发送第一QoS Flow的QoS需求不能得到保障的指示信息,例如第二QoS通知控制指示信息指示第一接入网网元向用户面网元发送第一指示信息,使得用户面网元能够根据第一指示信息生成第一报告信息,并向第一会话管理网元发送第一报告信息,实现了第一报告信息的快速上报。
在一种可能的实现方式中,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:第二会话管理网元向所述第一会话管理网元发送第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;所述第一会话管理网元接收来自所述第二会话管理网元的所述第一策略;所述第一会话管理网元根据所述第一策略确定第三策略,并向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;所述用户面网元接收所述第三策略。在上述方案中,用户面网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第三策略,用户面网元解析该第三策略,用户面网元按照第三策略的指示,需要发送第一QoS Flow的QoS需求能否得到保障的指示信息,例如用户面网元在确定第一QoS Flow的QoS需求不能得到保障时,发送前述的携带第一指示信息的第一报告信息,实现了第一报告信息的快速上报。
在一种可能的实现方式中,所述第一会话管理网元向应用功能网元发送第二报告信息,包括:当所述第一指示信息包括所述第一QoS Flow的标识时,所述第一会话管理网元根据所述第一QoS Flow的标识确定所述本地网络能力开放网元的通知端点,并通过所述本地网络能力开放网元的通知端点向所述本地网络能力开放网元发送所述第二报告信息,所述第二报告信息由所述本地网络能力开放网元向所述应用功能网元发送。在上述方案中,第一会话管理网元接收到第一策略之后,第一会话管理网元解析该第一策略,可以获取到第一QoS Flow的标识和本地网络能力开放网元的通知端点的信息,第一会话管理网元根据第一指示信息中携带的第一QoS Flow的标识确定第一策略中携带的本地网络能力开放网元的通知端点,并向该通知端点发送第二报告信息,从而本地网络能力开放网元可以接收到来自第一会话管理网元的第二报告信息,本地网络能力开放网元向应用功能网元发送该第二报告信息。本申请实施例中,第一会话管理网元可以通过本地网络能力开放网元的通知端点向本地网络能力开放网元发送第二报告信息,再由本地网络能力开放网元向应用功能网元发送该第二报告信息,从而实现了第一会话管理网元和应用功能网元之间的通信,使得应用功能网元可以快速的接收到第二报告信息,并根据第二报告信息进行应用层的调整,降 低了第二报告信息的传输时延。
在一种可能的实现方式中,所述方法还包括:策略控制网元向所述第二会话管理网元发送第四策略,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识;所述第二会话管理网元接收来自策略控制网元的第四策略;所述第二会话管理网网元根据所述第四策略生成所述第一策略,其中,所述至少一个候选QoS参数集用于确定所述至少一个候选QoS文档;所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识用于确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识。在上述方案中,第二会话管理网元接收来自策略控制网元的第四策略,第二会话管理网元解析第四策略,并确定出至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,至少一个候选QoS参数集用于确定至少一个候选QoS文档;第二会话管理网网元生成第一策略,第二会话管理网元生成的第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。第二会话管理网元通过和策略控制网元的交互,可以生成第一策略,使得第二会话管理网元可以向第一会话管理网元发送第一策略。
在一种可能的实现方式中,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:策略控制网元向所述第一会话管理网元发送第四策略,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识;所述第一会话管理网元接收来自策略控制网元的所述第四策略;所述第一会话管理网网元根据所述第四策略生成第一策略,其中,所述至少一个候选QoS参数集用于确定至少一个候选QoS文档,所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识用于确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识;所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、目标网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息,所述目标网元包括:本地网络能力开放网元或者所述应用功能网元。在上述方案中,第一会话管理网元接收来自策略控制网元的第四策略,第一会话管理网元解析第四策略,并确定出至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,至少一个候选QoS参数集用于确定至少一个候选QoS文档;第一会话管理网网元生成第一策略,第一会话管理网元生成的第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。第一会话管理网元通过和策略控制网元的交互,可以生成第一策略。
第三方面,本申请实施例还提供一种报告信息的发送方法,包括:策略控制网元接收 来自应用功能网元的业务请求,所述业务请求包括第一服务质量QoS通知控制指示信息和至少一个候选业务需求,所述第一QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;所述策略控制网元根据所述业务请求生成第四策略,所述第四策略包括第二QoS通知控制指示信息、至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的所述至少一个候选业务需求的标识,其中,所述至少一个候选服务质量QoS参数集根据所述至少一个候选业务需求确定,所述第二QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;所述策略控制网元向第一会话管理网元发送所述第四策略。在上述方案中,应用功能网元在向策略控制网元发送业务请求时提供候选的业务需求,策略控制网元根据候选的业务需求确定候选QoS参数集,策略控制网元可以获取到至少一个候选QoS参数集,以及获取到至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,然后策略控制网元生成第四策略,向第一会话管理网元发送第四策略,第四策略包括至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识。
在一种可能的实现方式中,所述业务请求还包括所述第一业务数据流的标识信息,所述第四策略还包括所述第一业务数据流的标识信息。在上述方案中,若应用功能网元提供多个业务数据流的描述信息,业务请求还包括所述第一业务数据流的标识信息,所述第四策略还包括所述第一业务数据流的标识信息。例如存在第一业务数据流和第二业务数据流,业务请求还包括第一业务数据流的标识信息和第二业务数据流的标识信息,本申请实施例中应用功能网元向策略控制网元发送的业务请求中携带业务数据流的标识信息,解决了存在多个业务数据流时指示每个业务流的QoS需求能否得到保障的指示问题。
第四方面,本申请实施例提供一种通信装置,所述通信装置具体为第一会话管理网元,所述第一会话管理网元用于执行前述第一方面中任一项所述的方法。
第五方面,本申请实施例提供一种通信装置,所述通信装置具体为策略控制网元,所述策略控制网元用于执行前述第三方面中任一项所述的方法。
第六方面,本申请实施例提供一种通信系统,包括:用户面网元、第一会话管理网元和应用功能网元,其中,所述用户面网元用于执行前述第二方面中所述用户面网元执行的任意一种方法;所述第一会话管理网元用于执行前述第二方面中所述第一会话管理网元执行的任意一种方法;所述应用功能网元用于执行前述第二方面中所述应用功能网元执行的任意一种方法。
在一种可能的实现方式中,所述通信系统还包括如下至少一个:第二会话管理网元、策略控制网元、第一接入网网元、第二接入网网元、本地网络能力开放网元。
第七方面,本申请实施例提供了一种计算机可读存储介质,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行上述第一方面或第二方面或第三方面中任一项所述的方法。
第八方面,本申请实施例提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第一方面或第二方面或第三方面中任一项所述的方法。
第九方面,本申请实施例提供一种通信装置,该通信装置可以包括用户面网元、第一会话管理网元、应用功能网元、策略控制网元或者芯片等实体,所述通信装置包括:处理 器,可选的,还包括存储器;所述存储器用于存储指令;所述处理器用于执行所述存储器中的所述指令,使得所述通信装置执行如前述第一方面或第二方面或第三方面中任一项所述的方法。
第十方面,本申请提供了一种芯片系统,该芯片系统包括处理器,用于支持用户面网元、第一会话管理网元、应用功能网元或策略控制网元实现上述方面中所涉及的功能,例如,发送或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中,所述芯片系统还包括存储器,所述存储器,用于保存用户面网元、第一会话管理网元、应用功能网元或策略控制网元必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包括芯片和其他分立器件。
附图说明
图1为本申请实施例提供的一种通信系统的组成结构示意图;
图2为本申请实施例提供的另一种通信系统的组成结构示意图;
图3为本申请实施例提供的一种报告信息的发送方法的交互流程示意图;
图4a为本申请实施例提供的一种通信系统的应用系统架构示意图;
图4b为本申请实施例提供的另一种通信系统的应用系统架构示意图;
图4c为本申请实施例提供的另一种通信系统的应用系统架构示意图;
图5为本申请实施例提供的通信系统中各网元之间的一种交互流程示意图;
图6为本申请实施例提供的通信系统中各网元之间的一种交互流程示意图;
图7为本申请实施例提供的一种第一会话管理网元的组成结构示意图;
图8为本申请实施例提供的一种应用功能网元的组成结构示意图;
图9为本申请实施例提供的另一种第一会话管理网元的组成结构示意图;
图10为本申请实施例提供的另一种应用功能网元的组成结构示意图。
具体实施方式
本申请实施例提供了报告信息的发送方法和通信装置以及通信系统,用于缩短上报信息的传输路径,减少应用功能网元的处理时延。
下面结合附图,对本申请的实施例进行描述。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。此外,术语“包括”和“具有”以及他们的任何变形,意图在于覆盖不排他的包含,以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元,而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
本申请实施例的技术方案可以应用于各种数据处理的通信系统,例如码分多址(code division multiple access,CDMA)、时分多址(time division multiple access,TDMA)、频分多址(frequency division multiple access,FDMA)、正交频分多址(orthogonal frequency-division multiple access,OFDMA)、单载波频分多址(single carrier FDMA, SC-FDMA)和其它系统等。术语“系统”可以和“网络”相互替换。CDMA系统可以实现例如通用无线陆地接入(universal terrestrial radio access,UTRA),CDMA2000等无线技术。UTRA可以包括宽带CDMA(wideband CDMA,WCDMA)技术和其它CDMA变形的技术。CDMA2000可以覆盖过渡标准(interim standard,IS)2000(IS-2000),IS-95和IS-856标准。TDMA系统可以实现如全球移动通信系统(global system for mobile communication,GSM)等无线技术。OFDMA系统可以实现诸如演进通用无线陆地接入(evolved UTRA,E-UTRA)、超级移动宽带(ultra mobile broadband,UMB)、IEEE 802.11(Wi-Fi),IEEE 802.16(WiMAX),IEEE 802.20,Flash OFDMA等无线技术。UTRA和E-UTRA是UMTS以及UMTS演进版本。3GPP在长期演进(long term evolution,LTE)和基于LTE演进的各种版本是使用E-UTRA的UMTS的新版本。第五代(5 Generation,简称:“5G”)通信系统、新空口(New Radio,简称“NR”)是正在研究当中的下一代通信系统。此外,所述通信系统还可以适用于面向未来的通信技术,都适用本申请实施例提供的技术方案。本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
请参阅图1所示,为本申请实施例提供的一种通信系统的组成结构示意图。本申请实施例提供一种通信系统100,包括:
用户面网元101,用于向第一会话管理网元102发送第一报告信息,第一报告信息包括第一指示信息和第一候选服务质量(quality of service,QoS)文档的标识,第一指示信息用于指示第一服务质量流(quality of service flow,QoS Flow)的QoS需求不能得到保障;
第一会话管理网元102,用于接收来自用户面网元101的第一报告信息;
第一会话管理网元102,用于向应用功能网元103发送第二报告信息,第二报告信息包括第二指示信息和第一候选业务需求的标识,第一候选业务需求的标识对应第一候选QoS文档的标识,第二指示信息用于指示第一业务数据流的QoS需求不能得到保障,第一QoS Flow用于传输第一业务数据流,业务数据流是应用功能网元103对应的应用的业务数据流;
应用功能网元103,用于接收第一会话管理网元102发送的第二报告信息。
其中,用户面网元101能够与无线接入网(radio access network,RAN)、第一会话管理网元102分别进行通信,用户面网元101具体可以是用户面功能(user plane function,UPF)网元。具体的,用户面网元101可以处于本地数据中心(local data center)中,该用户面网元101还可以称为本地协议数据单元锚点(local PDU session anchor,local PSA)。例如,用户面网元101可以支持以下全部或者部分功能:将协议数据单元(protocol data unit,PDU)会话与数据网络互连;分组路由和转发(例如,支持对流量进行上行分类后转发到数据网络;数据包检测等功能。
用户面网元101可以和第一会话管理网元102进行通信,例如用户面网元101和第一会话管理网元102之间建立有N4接口。
第一会话管理网元102是PDU会话的管理网元,例如该第一会话管理网元102处于本地数据中心中,第一会话管理网元102具体可以是会话管理功能(session management function, SMF)。又如,第一会话管理网元102具体可以是中间会话管理功能(intermediate session management function,I-SMF),该第一会话管理网元102可以与核心数据中心(central DC)中的SMF进行通信。例如,第一会话管理网元102和用户面网元101之间建立有N4接口。例如,该第一会话管理网元102和应用功能网元103之间建立有N33接口,或者该第一会话管理网元102和本地网络能力开放网元(local network exposure function,local NEF)之间建立有Nx接口,本地网络能力开放网元和应用功能网元103之间建立有N33接口,第一会话管理网元102通过本地网络能力开放网元和应用功能网元103进行通信。具体可以根据应用场景确定第一会话管理网元102的实现方式,此处不做限定。
应用功能网元103可以和第一会话管理网元102进行通信,以获取到QoS的报告信息,并根据该报告信息进行应用层的功能调整。例如应用功能网元103具体可以是本地数据中心中的应用功能网元(application function,AF),例如AF部署在边缘应用服务器(edge application server,EAS)。
在本申请的一些实施例中,请参阅图2所示,本申请实施例提供一种通信系统100除了包括用户面网元101、第一会话管理网元102和应用功能网元103之外,通信系统100还可以包括:
策略控制网元104,用于接收来自应用功能网元103的业务请求,业务请求包括第一服务质量QoS通知控制指示信息和至少一个候选业务需求,第一QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;
策略控制网元104,用于根据业务请求生成第四策略,第四策略包括第二QoS通知控制指示信息、至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,其中,至少一个候选服务质量QoS参数集根据至少一个候选业务需求确定,第二QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;
策略控制网元104,用于向第一会话管理网元102发送第四策略。
其中,策略控制网元104是提供策略的功能网元,例如策略控制网元104具体可以是核心数据中心中的策略控制功能(policy control function,PCF)网元,策略控制网元104可以制定策略计费控制(policy and charging control,PCC)规则,通过PCC规则携带上述的第四策略。
策略控制网元104可以和应用功能网元103进行通信,例如策略控制网元104通过网络能力开放网元(network exposure function,NEF)和应用功能网元103进行通信,例如策略控制网元104和网络能力开放网元之间配置有N5接口,网络能力开放网元和应用功能网元103之间配置有N33接口。又如,策略控制网元104通过网络能力开放网元、本地网络能力开放网元和应用功能网元103进行通信,策略控制网元104和网络能力开放网元之间配置有N5接口,网络能力开放网元和本地网络能力开放网元之间配置有N33a接口,本地网络能力开放网元和应用功能网元103之间配置有N33接口。
需要说明的是,本申请实施例中通信系统100还可以包括上述的本地网络能力开放网元和网络能力开放网元,在图2中没有示意说明。同样的,通信系统100中还可以包括后续实施例中提及的第二会话管理网元、第一接入网网元、第二接入网网元等网元,均不在 图例中示意说明。其中,第一接入网网元可以是终端设备切换之前所在的无线接入网,第二接入网网元可以是终端设备切换之后所在的无线接入网。
通过前述实施例对通信系统的组成结构的说明可知,在该通信系统中,第一会话管理网元可以从用户面网元接收到第一报告信息,该第一报告信息中携带第一指示信息和第一QoS文档的标识,因此第一会话管理网元可以根据第一指示信息获取第二指示信息,还可以根据第一候选QoS文档的标识确定第一候选业务需求的标识,因此第一会话管理网元可以生成第二报告信息,第一会话管理网元向应用功能管理网元发送的第二报告信息,通过该第二报告信息中的第二指示信息指示第一业务数据流的QoS需求不能得到保障。本申请实施例中基于“用户面网元-第一会话管理网元-应用功能网元”路径可以使得应用功能网元确定第一业务数据流的QoS需求不能得到保障,另外第二报告信息中还携带第一候选业务需求的标识,从而使得应用功能网元还可以确定出候选业务需求,以便于应用功能网元在确定第一业务数据流的QoS需求不能得到保障时根据第一候选业务需求在应用层快速调整。因此极大地缩短了指示第一业务数据流的QoS需求不能得到保障的路径,对于时间敏感性较高的业务,第二报告信息的时效性高,降低了应用功能网元在应用层做出调整时的时延。
前述实施例介绍了本申请提供给的通信系统,接下来介绍基于该通信系统执行的通信你方法,请参阅图3所示,本申请实施例提供的报告信息的发送方法主要包括如下步骤:
301、用户面网元向第一会话管理网元发送第一报告信息,第一报告信息包括第一指示信息和第一候选服务质量QoS文档的标识,第一指示信息用于指示第一服务质量流QoS Flow的QoS需求不能得到保障。
其中,用户面网元可以从RAN获取第一QoS Flow的QoS需求能否得到保障,第一QoS Flow是承载第一业务数据流的QoS Flow。例如用户面网元在确定第一QoS Flow的QoS需求不能得到保障时生成第一指示信息,在确定第一QoS Flow的QoS需求不能得到保障时用户面网元还可以确定第一候选(Alternative)QoS文档(Profile)的标识,第一候选QoS文档可以是能够保障第一QoS Flow的QoS需求的QoS文档。例如,第一候选QoS文档的标识可以是第一AltProId。
可选的,第一报告信息具体可以是携带QoS通知控制(Notification Control)事件报告的数据包。
举例说明如下,第一QoS Flow的QoS需求可以包括最大带宽(即最大传输比特率(max bitrate))、保障带宽(即保障比特率(guaranteed bitrate))、包延迟预计(packet delay budget)和包错误率(packet error rate)中的一种或多种等等。特别地,第一指示信息用于指示第一服务质量流QoS Flow的保障带宽不能得到保障。
302、第一会话管理网元接收来自用户面网元的第一报告信息。
基于图1所示的通信系统可知,用户面网元可以和第一会话管理网元进行通信,例如用户面网元和第一会话管理网元之间建立有N4接口。第一会话管理网元可以接收到来自用户面网元的第一报告信息。第一报告信息包括第一指示信息和第一候选服务质量QoS文档的标识,第一指示信息用于指示第一服务质量流QoS Flow的QoS需求不能得到保障。
在本申请的一些实施例中,第一会话管理网元可以为中间会话管理网元,例如第一会 话管理网元可以是I-SMF,该第一会话管理网元处于本地数据中心中,核心数据中心中可部署有第二会话管理网元,例如第二会话管理网元可以是SMF。第一会话管理网元和第二会话管理网元之间可以配置有N16a接口。当第一会话管理网元为中间会话管理网元时,步骤302第一会话管理网元接收来自用户面网元的第一报告信息之前,本申请实施例提供的报告信息的发送方法还包括如下步骤:
S01、第二会话管理网元向第一会话管理网元发送第一策略,第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,至少一个候选QoS文档包括第一候选QoS文档,至少一个候选业务需求的标识包括第一候选业务需求的标识,第一QoS通知控制指示信息用于指示发送第一QoS Flow的QoS需求不能得到保障的指示信息。
其中,第二会话管理网元可以生成第一策略,第二会话管理网元可以和第一会话管理管理网元进行通信,第二会话管理网元向第一会话管理网元发送第一策略。
具体的,第二会话管理网元生成的第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。其中,至少一个候选QoS文档包括第一候选QoS文档,至少一个候选业务需求的标识包括第一候选业务需求的标识,至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识指示了候选QoS文档和候选业务需求的对应关系。应用功能网元的通知端点的信息包括应用功能网元对应的通知端点,例如应用功能网元对应的通知端点可以是通知端点1a(Notification Endpoint1a),通知端点1a包括接收QoS通知控制事件通知的目标通知地址1a(Notification Target Address1a),或者,通知端点1a包括目标通知地址1a(Notification Target Address1a)和通知关联标识1a(Notification Correlation Id1a)。
第二会话管理网元发送的第一策略中还可以包括:第一QoS通知控制指示信息,用于指示发送第一QoS Flow的QoS需求不能得到保障的指示信息。即第一QoS通知控制指示信息可以用于指示需要发送前述的第一指示信息。
S02、第一会话管理网元接收来自第二会话管理网元的第一策略。
其中,第一会话管理网元可以和第二会话管理管理网元进行通信,第二会话管理网元向第一会话管理网元发送第一策略,第一会话管理网元接收来自第二会话管理网元的第一策略,第一会话管理网元解析该第一策略,可以获取到第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。
S03、第一会话管理网元根据第一策略确定第二策略,并向第一接入网网元发送第二策略,其中,第二策略包括第一QoS Flow的标识、第二QoS通知控制指示信息和至少一个候选QoS文档,第二QoS通知控制指示信息根据第一QoS通知控制指示信息确定。
其中,第一会话管理网元可以获取到第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,然后第一会话管理网元生成第二策略,第二 策略包括第一QoS Flow的标识、第二QoS通知控制指示信息和至少一个候选QoS文档,第二QoS通知控制指示信息根据第一QoS通知控制指示信息确定。例如第二QoS通知控制指示信息可以和第一QoS通知控制指示信息是相同的QoS通知控制指示信息,即第二QoS通知控制指示信息,用于指示发送第一QoS Flow的QoS需求不能得到保障的指示信息。即第一QoS通知控制指示信息可以用于指示需要发送前述的第一指示信息。又如,第二QoS通知控制指示信息是根据第一QoS通知控制指示信息携带的指示信息内容生成的,具体的,第二QoS通知控制指示信息可以是根据传输信息的通信协议要求在第一QoS通知控制指示信息中增加特定的信息字段后得到的,或者第二QoS通知控制指示信息可以是根据传输信息的通信协议要求在第一QoS通知控制指示信息中取出不必要的信息字段后得到的。
第一会话管理网元可以和第一接入网网元进行通信,例如第一会话管理网元向第一接入网网元发送第二策略,其中,第一接入网网元可以是终端设备切换之前所在的无线接入网。具体的,第一会话管理网元可以和接入和移动性管理功能(access and mobility management function,AMF)之间建立有N11接口,AMF和第一接入网网元之间建立有N2接口。
S04、第一接入网网元接收第二策略。
其中,第一接入网网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第二策略,第一接入网网元解析该第二策略,第一接入网网元可以获取到第一QoS Flow的标识、第二QoS通知控制指示信息和至少一个候选QoS文档,第二QoS通知控制指示信息用于指示发送第一QoS Flow的QoS需求不能得到保障的指示信息,例如第二QoS通知控制指示信息指示第一接入网网元向用户面网元发送第一指示信息。
在本申请的一些实施例中,第一会话管理网元可以为中间会话管理网元,例如第一会话管理网元可以是I-SMF,该第一会话管理网元处于本地数据中心中,核心数据中心中可部署有第二会话管理网元,例如第二会话管理网元可以是SMF。第一会话管理网元和第二会话管理网元之间可以配置有N16a接口。当第一会话管理网元为中间会话管理网元时,步骤302第一会话管理网元接收来自用户面网元的第一报告信息之前,本申请实施例提供的报告信息的发送方法还包括如下步骤:
S11、第二会话管理网元向第一会话管理网元发送第一策略,第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,至少一个候选QoS文档包括第一候选QoS文档,至少一个候选业务需求的标识包括第一候选业务需求的标识,第一QoS通知控制指示信息用于指示发送第一QoS Flow的QoS需求能否得到保障的指示信息。
其中,第二会话管理网元可以生成第一策略,第二会话管理网元可以和第一会话管理管理网元进行通信,第二会话管理网元向第一会话管理网元发送第一策略。
具体的,第二会话管理网元生成的第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。其中,至少一个候选QoS文档包括第一候选QoS文档,至少一个候选业务需求的标识包括第一候选业务需求的标识,至少 一个候选QoS文档的标识对应的至少一个候选业务需求的标识指示了候选QoS文档和候选业务需求的对应关系。应用功能网元的通知端点的信息包括应用功能网元对应的通知端点,例如应用功能网元对应的通知端点可以是通知端点1a(Notification Endpoint1a),通知端点1a包括接收QoS通知控制事件通知的目标通知地址1a(Notification Target Address1a),或者,通知端点1a包括目标通知地址1a(Notification Target Address1a)和通知关联标识1a(Notification Correlation Id1a)。
第二会话管理网元发送的第一策略中还可以包括:第一QoS通知控制指示信息,用于指示发送第一QoS Flow的QoS需求不能得到保障的指示信息。即第一QoS通知控制指示信息可以用于指示需要发送前述的第一指示信息。
S12、第一会话管理网元接收来自第二会话管理网元的第一策略。
其中,第一会话管理网元可以和第二会话管理管理网元进行通信,第二会话管理网元向第一会话管理网元发送第一策略,第一会话管理网元接收来自第二会话管理网元的第一策略,第一会话管理网元解析该第一策略,可以获取到第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。
S13、第一会话管理网元根据第一策略确定第三策略,并向用户面网元发送第三策略,第三策略用于指示用户面网元发送第一QoS Flow的QoS需求能否得到保障的指示信息。
其中,第一会话管理网元可以获取到第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,然后第一会话管理网元生成第三策略,第三策略用于指示用户面网元发送第一QoS Flow的QoS需求能否得到保障的指示信息。基于前述说明可知,第一会话管理网元可以和用户面网元进行通信,第一会话管理网元向用户面网元发送第三策略。
S14、用户面网元接收第三策略。
其中,用户面网元可以和第一会话管理网元进行通信,从第一会话管理网元接收到第三策略,用户面网元解析该第三策略,用户面网元按照第三策略的指示,需要发送第一QoS Flow的QoS需求能否得到保障的指示信息,例如用户面网元在确定第一QoS Flow的QoS需求不能得到保障时,发送前述的携带第一指示信息的第一报告信息。
在本申请的一些实施例中,第一会话管理网元可以为中间会话管理网元,例如第一会话管理网元可以是I-SMF,该第一会话管理网元处于本地数据中心中,核心数据中心中可部署有第二会话管理网元,例如第二会话管理网元可以是SMF。第一会话管理网元和第二会话管理网元之间可以配置有N16a接口。当第一会话管理网元为中间会话管理网元时,步骤302第一会话管理网元接收来自用户面网元的第一报告信息之前,本申请实施例提供的报告信息的发送方法还包括如下步骤:
S21、第二会话管理网元向第一会话管理网元发送第一策略,第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,至少一个候选QoS文档包括第一候选QoS文档,至少一个候选业务需求的标识包括第 一候选业务需求的标识,第一QoS通知控制指示信息用于指示发送第一QoS Flow的QoS需求能否得到保障的指示信息。
其中,步骤S21与前述步骤S01中第一策略携带的通知端点的信息是不相同的,步骤S21中第一策略包括的是本地网络能力开放网元的通知端点的信息,本地网络能力开放网元的通知端点的信息包括本地网络能力开放网元对应的通知端点,例如本地网络能力开放网元对应的通知端点可以是通知端点1a(Notification Endpoint1a),通知端点1a包括接收QoS通知控制事件通知的目标通知地址1a(Notification Target Address1a),或者,通知端点1a包括目标通知地址1a(Notification Target Address1a)和通知关联标识1a(Notification Correlation Id1a)。
S22、第一会话管理网元接收来自第二会话管理网元的第一策略。
S23、第一会话管理网元根据第一策略确定第二策略,并向第一接入网网元发送第二策略,第二策略包括第一QoS Flow标识、第二QoS通知控制指示信息和至少一个候选QoS文档,第二QoS通知控制指示信息根据第一QoS通知控制指示信息确定;
S24、第一接入网网元接收第二策略。
其中,步骤S22至步骤S24与前述实施例中的步骤S02至步骤S04的实现方式相类似,此处不再赘述。
在本申请的一些实施例中,第一会话管理网元可以为中间会话管理网元,例如第一会话管理网元可以是I-SMF,该第一会话管理网元处于本地数据中心中,核心数据中心中可部署有第二会话管理网元,例如第二会话管理网元可以是SMF。第一会话管理网元和第二会话管理网元之间可以配置有N16a接口。当第一会话管理网元为中间会话管理网元时,步骤302第一会话管理网元接收来自用户面网元的第一报告信息之前,本申请实施例提供的报告信息的发送方法还包括如下步骤:
S31、第二会话管理网元向第一会话管理网元发送第一策略,第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,至少一个候选QoS文档包括第一候选QoS文档,至少一个候选业务需求的标识包括第一候选业务需求的标识,第一QoS通知控制指示信息用于指示发送第一QoS Flow的QoS需求能否得到保障的指示信息。
其中,步骤S31与前述步骤S11中第一策略携带的通知端点的信息是不相同的,步骤S31中第一策略包括的是本地网络能力开放网元的通知端点的信息,本地网络能力开放网元的通知端点的信息包括本地网络能力开放网元对应的通知端点,例如本地网络能力开放网元对应的通知端点可以是通知端点1a(Notification Endpoint1a),通知端点1a包括接收QoS通知控制事件通知的目标通知地址1a(Notification Target Address1a),或者,通知端点1a包括目标通知地址1a(Notification Target Address1a)和通知关联标识1a(Notification Correlation Id1a)。
S32、第一会话管理网元接收来自第二会话管理网元的第一策略。
S33、第一会话管理网元根据第一策略确定第三策略,并向用户面网元发送第三策略,第三策略用于指示用户面网元发送第一QoS Flow的QoS需求能否得到保障的指示信息;
S34、用户面网元接收第三策略。
其中,步骤S32至步骤S34与前述实施例中的步骤S12至步骤S14的实现方式相类似,此处不再赘述。
在申请的一些实施例中,步骤S01、或步骤S11、或步骤S21、或步骤S31中第二会话管理网元向第一会话管理网元发送第一策略之前,本申请实施例提供的报告信息的发送方法还可以包括如下步骤:
S41、策略控制网元向第二会话管理网元发送第四策略,第四策略包括至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识;
S42、第二会话管理网元接收来自策略控制网元的第四策略;
S43、第二会话管理网网元根据第四策略生成第一策略,其中,至少一个候选QoS参数集用于确定至少一个候选QoS文档;至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识用于确定至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,至少一个候选业务需求的标识包括第一候选业务需求的标识。
其中,第二会话管理网元和策略控制网元都处于核心数据中心中,第二会话管理网元和策略控制网元之间可以通过N7接口进行通信,应用功能网元在向策略控制网元发送业务请求时提供候选的业务需求,策略控制网元根据候选的业务需求确定候选QoS参数集,策略控制网元可以获取到至少一个候选QoS参数集,以及获取到至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,然后策略控制网元生成第四策略,向第二会话管理网元发送第四策略,第四策略包括至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识。
第二会话管理网元接收来自策略控制网元的第四策略,第二会话管理网元解析第四策略,并确定出至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,至少一个候选QoS参数集用于确定至少一个候选QoS文档;第二会话管理网网元生成第一策略,第二会话管理网元生成的第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。第二会话管理网元通过和策略控制网元的交互,可以生成第一策略,使得第二会话管理网元可以向第一会话管理网元发送第一策略。
在本申请的一些实施例中,第一会话管理网元可以为会话管理网元,例如第一会话管理网元可以是SMF,该第一会话管理网元处于本地数据中心中,核心数据中心中可部署有策略控制网元,例如策略控制网元可以是PCF。第一会话管理网元和策略控制网元之间可以配置有N7接口。当第一会话管理网元为本地数据中心中的会话管理网元时,步骤302第一会话管理网元接收来自用户面网元的第一报告信息之前,本申请实施例提供的报告信息的发送方法还包括如下步骤:
策略控制网元向第一会话管理网元发送第四策略,第四策略包括至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,其中,至少一个候选业务需求的标识包括第一候选业务需求的标识;
第一会话管理网元接收来自策略控制网元的第四策略;
第一会话管理网网元根据第四策略生成第一策略,其中,至少一个候选QoS参数集用于确定至少一个候选QoS文档,至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识用于确定至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识;第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、目标网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,至少一个候选QoS文档包括第一候选QoS文档,至少一个候选业务需求的标识包括第一候选业务需求的标识,第一QoS通知控制指示信息用于指示发送第一QoS Flow的QoS需求能否得到保障的指示信息,目标网元包括:本地网络能力开放网元或者应用功能网元。
其中,第一会话管理网元处于本地数据中心中,策略控制网元处于核心数据中心中,第一会话管理网元和策略控制网元之间可以通过N7接口进行通信,应用功能网元在向策略控制网元发送业务请求时提供候选的业务需求,策略控制网元根据候选的业务需求确定候选QoS参数集,策略控制网元可以获取到至少一个候选QoS参数集,以及获取到至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,然后策略控制网元生成第四策略,向第一会话管理网元发送第四策略,第四策略包括至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识。
第一会话管理网元接收来自策略控制网元的第四策略,第一会话管理网元解析第四策略,并确定出至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,至少一个候选QoS参数集用于确定至少一个候选QoS文档;第一会话管理网网元生成第一策略,第一会话管理网元生成的第一策略包括第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、应用功能网元的通知端点的信息以及至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。第一会话管理网元通过和策略控制网元的交互,可以生成第一策略。
在本申请的一些实施例中,本申请实施例提供的报告信息的发送方法包括如下步骤:
策略控制网元接收来自应用功能网元的业务请求,所述业务请求包括第一服务质量QoS通知控制指示信息和至少一个候选业务需求,所述第一QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;
所述策略控制网元根据所述业务请求生成第四策略,所述第四策略包括第二QoS通知控制指示信息、至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的所述至少一个候选业务需求的标识,其中,所述至少一个候选服务质量QoS参数集根据所述至少一个候选业务需求确定,所述第二QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;
所述策略控制网元向第一会话管理网元发送所述第四策略。
具体的,应用功能网元在向策略控制网元发送业务请求时提供候选的业务需求,策略控制网元根据候选的业务需求确定候选QoS参数集,策略控制网元可以获取到至少一个候选QoS参数集,以及获取到至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,然后策略控制网元生成第四策略,向第一会话管理网元发送第四策略,第四策略包括至少一个候选QoS参数集以及至少一个候选QoS参数集的标识对应的至少一个候选业 务需求的标识。
在本申请的一些实施例中,所述业务请求还包括所述第一业务数据流的标识信息,所述第四策略还包括所述第一业务数据流的标识信息。
其中,若应用功能网元提供多个业务数据流的描述信息,业务请求还包括所述第一业务数据流的标识信息,所述第四策略还包括所述第一业务数据流的标识信息。例如存在第一业务数据流和第二业务数据流,业务请求还包括第一业务数据流的标识信息和第二业务数据流的标识信息,本申请实施例中应用功能网元向策略控制网元发送的业务请求中携带业务数据流的标识信息,解决了存在多个业务数据流时指示每个业务流的QoS需求能否得到保障的指示问题。
303、第一会话管理网元向应用功能网元发送第二报告信息,第二报告信息包括第二指示信息和第一候选业务需求的标识,第一候选业务需求的标识对应第一候选QoS文档的标识,第二指示信息用于指示第一业务数据流的QoS需求不能得到保障,第一QoS Flow用于传输第一业务数据流,第一业务数据流是应用功能网元对应的应用的业务数据流。
其中,第一会话管理网元接收到来自用户面网元的第一报告信息之后,第一会话管理网元解析该第一报告信息,通过该第一报告信息获取到第一指示信息和第一候选QoS文档的标识,第一会话管理网元进一步的解析第一指示信息,第一会话管理网元可以获取到第一QoS Flow的QoS需求不能得到保障。第一会话管理网元根据第一候选业务需求和第一候选QoS文档的对应关系,可以获取到第一候选QoS文档的标识对应的第一候选业务需求的标识,例如第一候选业务需求的标识可以是第一Alternative Service Requirement Id(简称AltSerId)。第一业务数据流是应用功能网元对应的应用的业务数据流,而第一QoS Flow用于传输第一业务数据流,因此第一会话管理网元可以根据第一指示信息生成第二指示信息,例如第一指示信息指示第一QoS Flow的QoS需求不能得到保障,第一会话管理网元根据第一QoS Flow的QoS需求不能得到保障确定第一QoS Flow传输的第一业务数据流的QoS需求不能得到保障,第一会话管理网元生成第二指示信息。第一会话管理网元在获取到第二指示信息和第一候选业务需求的标识之后,可以生成第二报告信息。
第一业务数据流的QoS需求可以包括媒体类型、最大请求带宽、最小请求带宽、最大支持带宽、最小期望带宽、最大丢包率和QoS参考标识中的一种或多种。特别地,根据第一业务数据流的媒体类型确定第一业务数据流的保障带宽不能得到保障,第二指示信息用于指示第一业务数据流的保障带宽不能得到保障。
在本申请的一些实施例中,第二指示信息根据第一指示信息确定。例如,第二指示信息是根据第一指示信息携带的指示内容生成的,第一指示信息指示第一QoS Flow的QoS需求不能得到保障,第一会话管理网元根据第一QoS Flow的QoS需求不能得到保障确定第一QoS Flow传输的第一业务数据流的QoS需求不能得到保障,在第二指示信息中携带第一业务数据流的QoS需求不能得到保障。可以理解的是,第二指示信息是基于第一指示信息得到,例如第一指示信息和和第二指示信息可以是相同的指示信息。此处仅作举例,不作为对本申请实施例的限定。
基于图1所示的通信系统可知,第一会话管理网元可以和应用功能网元进行通信,例如第一会话管理网元向应用功能网元发送第二报告信息。
304、应用功能网元接收第一会话管理网元发送的第二报告信息。
基于图1所示的通信系统可知,应用功能网元可以和第一会话管理网元进行通信,例如应用功能网元可以从第一会话管理网元接收到第二报告信息,应用功能网元解析该第二报告信息,通过该第二报告信息获取到第二指示信息和第一候选业务需求的标识,应用功能网元进一步的解析第二指示信息,应用功能网元可以获取到第一业务数据流的QoS需求不能得到保障。应用功能网元还从第二报告信息中获取到了第一候选业务需求的标识,从而使得应用功能网元还可以确定出候选业务需求,以便于应用功能网元在确定第一业务数据流的QoS需求不能得到保障时根据第一候选业务需求在应用层快速调整。因此极大地缩短了指示第一业务数据流的QoS需求不能得到保障的路径,对于时间敏感性较高的业务,第二报告信息的时效性高,降低了应用功能网元在应用层做出调整时的时延。
在前述的实施例中,第一会话管理网元接收来自第二会话管理网元的第一策略,该第一策略中包括有应用功能网元的通知端点的信息。具体的,步骤304第一会话管理网元根据第一报告信息向应用功能网元发送第二报告信息,包括:
当第一指示信息包括第一QoS Flow的标识时,第一会话管理网元根据第一QoS Flow的标识确定应用功能网元的通知端点,并通过应用功能网元的通知端点向应用功能网元发送第二报告信息。
其中,第一会话管理网元接收到第一策略之后,第一会话管理网元解析该第一策略,可以获取到第一QoS Flow的标识和应用功能网元的通知端点的信息,第一会话管理网元根据第一指示信息中携带的第一QoS Flow的标识确定第一策略中携带的应用功能网元的通知端点,并向该通知端点发送第二报告信息,从而应用功能网元可以接收到来自第一会话管理网元的第二报告信息。本申请实施例中,第一会话管理网元可以通过应用功能网元的通知端点向应用功能网元发送第二报告信息,从而实现了第一会话管理网元和应用功能网元之间的通信,使得应用功能网元可以快速的接收到第二报告信息,并根据第二报告信息进行应用层的调整,降低了第二报告信息的传输时延。
在前述的实施例中,第一会话管理网元接收来自第二会话管理网元的第一策略,该第一策略中包括有应用功能网元的通知端点的信息。具体的,步骤304第一会话管理网元根据第一报告信息向应用功能网元发送第二报告信息,包括:
当第一指示信息包括第一QoS Flow的标识时,第一会话管理网元根据第一QoS Flow的标识确定本地网络能力开放网元的通知端点,并通过本地网络能力开放网元的通知端点向本地网络能力开放网元发送第二报告信息,第二报告信息由本地网络能力开放网元向应用功能网元发送。
其中,第一会话管理网元接收到第一策略之后,第一会话管理网元解析该第一策略,可以获取到第一QoS Flow的标识和本地网络能力开放网元的通知端点的信息,第一会话管理网元根据第一指示信息中携带的第一QoS Flow的标识确定第一策略中携带的本地网络能力开放网元的通知端点,并向该通知端点发送第二报告信息,从而本地网络能力开放网元可以接收到来自第一会话管理网元的第二报告信息,本地网络能力开放网元向应用功能网元发送该第二报告信息。本申请实施例中,第一会话管理网元可以通过本地网络能力开放网元的通知端点向本地网络能力开放网元发送第二报告信息,再由本地网络能力开放网元 向应用功能网元发送该第二报告信息,从而实现了第一会话管理网元和应用功能网元之间的通信,使得应用功能网元可以快速的接收到第二报告信息,并根据第二报告信息进行应用层的调整,降低了第二报告信息的传输时延。
在本申请的一些实施例中,终端设备还可以进行切换,例如终端设备从第一接入网网元切换至第二接入网网元,其中,第一接入网网元可以是终端设备切换之前所在的无线接入网,第二接入网网元可以是终端设备切换之后所在的无线接入网。步骤304第一会话管理网元向应用功能网元发送第二报告信息之后,本申请实施例提供的报告信息的发送方法还包括如下步骤:
当终端设备从第一接入网网元切换至第二接入网网元时,第一会话管理网元接收来自第二接入网网元的QoS Flow的标识信息,QoS Flow的标识信息包括第一QoS Flow的标识;
第一会话管理网元向应用功能网元发送第三报告信息,其中,第三报告信息包括第三指示信息,第三指示信息用于指示第一业务数据流的QoS需求不能得到保障。
其中,终端设备从第一接入网网元切换至第二接入网网元时,第二接入网网元还可以向第一会话管理网元发送QoS Flow的标识信息,例如第二接入网网元和AMF之间建立有N2接口,AMF和第一会话管理网元之间建立有N11接口,第一会话管理网元接收来自第二接入网网元的QoS Flow的标识信息,QoS Flow的标识信息包括第一QoS Flow的标识,第一QoS Flow用于传输第一业务数据流。第一会话管理网元可以向应用功能网元发送第三报告信息,其中,第三报告信息包括第三指示信息,第三指示信息用于指示第一业务数据流的QoS需求不能得到保障。本申请实施例中在终端设备发生切换时,应用功能网元也可以从第一会话管理网元接收到第三报告信息,并根据第三报告信息进行应用层的调整,降低了第三报告信息的传输时延。
在本申请的一些实施例中,终端设备还可以进行切换,例如终端设备从第一接入网网元切换至第二接入网网元,其中,第一接入网网元可以是终端设备切换之前所在的无线接入网,第二接入网网元可以是终端设备切换之后所在的无线接入网。本申请实施例提供的报告信息的发送方法还包括如下步骤:
第一会话管理网元接收来自第二接入网网元的第一QoS Flow对应的第二候选QoS文档的标识;
其中,第三报告信息还包括第二候选业务需求的标识,第二候选业务需求的标识对应第二候选QoS文档的标识。
具体的,第一QoS Flow的QoS需求不能得到保障时,第二接入网网元还可以向第一会话管理网元发送第一QoS Flow对应的第二候选QoS文档的标识,第二候选QoS文档也是满足第一Qos Flow的QoS需求的候选QoS文档。此时,第一会话管理网元还可以确定出满足第一Qos Flow的QoS需求的第二候选QoS文档,第一会话管理网元根据候选QoS文档和候选业务需求的对应关系可以确定出第二候选QoS文档的标识对应的第二候选业务需求的标识。第一会话管理网元向应用功能网元发送第三报告信息,第三报告信息除了包括第三指示信息,第三报告信息还包括第二候选业务需求的标识,从而使得应用功能网元可以获取到满足第一Qos Flow的QoS需求的第二候选QoS文档,解决了存在多个候选QoS文档时的报告指示问题。
在本申请的一些实施例中,第二报告信息还包括第一业务数据流的标识信息。
在本申请的一些实施例中,第三报告信息还包括第一业务数据流的标识信息。
其中,应用功能网元可以从第一会话管理网元接收到第二报告信息,或者接收到第三报告信息,若应用功能网元提供多个业务数据流的描述信息,例如存在第一业务数据流和第二业务数据流的QoS需求能否得到保障的指示时,在第一会话管理网元发送的第二报告信息和第三报告信息中需要携带第一业务数据流的标识信息和第二业务数据流的标识信息,本申请实施例中第一会话管理网元向应用功能网元发送的报告信息中携带业务数据流的标识信息,解决了存在多个业务数据流时指示每个业务流的QoS需求能否得到保障的指示问题。
通过前述实施例对本申请的举例说明可知,第一会话管理网元接收来自用户面网元的第一报告信息,第一报告信息包括第一指示信息和第一候选QoS文档的标识,第一指示信息用于指示第一QoS Flow的QoS需求不能得到保障;第一会话管理网元向应用功能网元发送第二报告信息,其中,第二报告信息包括第二指示信息和第一候选业务需求的标识,第一候选业务需求的标识对应第一候选QoS文档的标识,第二指示信息用于指示第一业务数据流的QoS需求不能得到保障,第一QoS Flow用于传输第一业务数据流,业务数据流是应用功能网元对应的应用的业务数据流。由于第一会话管理网元可以从用户面网元接收到第一报告信息,该第一报告信息中携带第一指示信息和第一QoS文档的标识,因此第一会话管理网元可以根据第一指示信息获取第二指示信息,还可以根据第一候选QoS文档的标识确定第一候选业务需求的标识,因此第一会话管理网元可以生成第二报告信息,第一会话管理网元向应用功能管理网元发送的第二报告信息,通过该第二报告信息中的第二指示信息指示第一业务数据流的QoS需求不能得到保障。本申请实施例中基于“用户面网元-第一会话管理网元-应用功能网元”路径可以使得应用功能网元确定第一业务数据流的QoS需求不能得到保障,另外第二报告信息中还携带第一候选业务需求的标识,从而使得应用功能网元还可以确定出候选业务需求,以便于应用功能网元在确定第一业务数据流的QoS需求不能得到保障时根据第一候选业务需求在应用层快速调整。因此极大地缩短了指示第一业务数据流的QoS需求不能得到保障的路径,对于时间敏感性较高的业务,第二报告信息的时效性高,降低了应用功能网元在应用层做出调整时的时延。
为便于更好的理解和实施本申请实施例的上述方案,下面举例相应的应用场景来进行具体说明。
基于图1所示的通信系统,接下来对通信系统的不同应用场景进行举例说明,例如图4a至图4c为图1所示的通信系统的三种具体应用场景。后续实施例中以第一会话管理网元为I-SMF、用户面网元为Local PSA、应用功能网元为AF进行示例说明。
如图4a所示,为本申请实施例提供的一种通信系统的应用场景框架示意图,在本地数据中心(local data center)部署I-SMF,I-SMF支持N33接口与AF互通,N4接口与Local PSA互通。具体的,通信系统中可以包括:UE、RAN、Local PSA、AF、I-SMF、AMF、SMF、PCF、NEF。其中,AMF和UE之间配置有N1接口,AMF和RAN之间配置有N2接口,RAN和Local PSA之间配置有N3接口,AMF和I-SMF之间配置有N11接口,I-SMF和Local PSA之间配置有N4接口,I-SMF和SMF之间配置有N16a接口,I-SMF和AF之间配置有N33接口,AF和Local PSA之间配置有N6接口,AF和NEF之间配置有N33接口,NEF和PCF之间配置还有N5接口,PCF和SMF之间配置有N7接口。
如图4b所示,为本申请实施例提供的一种通信系统的应用场景框架示意图,在本地部署Local NEF和I-SMF,Local NEF支持N33接口与AF互通,支持N33a接口与NEF互通或N5接口与PCF,Nx接口与I-SMF互通。具体的,通信系统中可以包括:UE、RAN、Local PSA、AF、I-SMF、AMF、Local NEF、SMF、PCF、NEF。其中,AMF和UE之间配置有N1接口,AMF和RAN之间配置有N2接口,RAN和Local PSA之间配置有N3接口,AMF和I-SMF之间配置有N11接口,I-SMF和Local PSA之间配置有N4接口,I-SMF和SMF之间配置有N16a接口,I-SMF和Local NEF之间配置有Nx接口,Local NEF和AF之间配置有N33接口,AF和Local PSA之间配置有N6接口,Local NEF和NEF之间配置有N33接口,Local NEF和PCF之间配置还有N5接口,NEF和PCF之间配置还有N5接口,PCF和SMF之间配置有N7接口。
如图4c所示,为本申请实施例提供的一种通信系统的应用场景框架示意图,SMF在本地数据中心部署。具体的,通信系统中可以包括:UE、RAN、Local PSA、AF、I-SMF、AMF、Local NEF、PCF、NEF。其中,AMF和UE之间配置有N1接口,AMF和RAN之间配置有N2接口,RAN和Local PSA之间配置有N3接口,AMF和I-SMF之间配置有N11接口,I-SMF和Local PSA之间配置有N4接口,I-SMF和PCF之间配置有N7接口,I-SMF和Local NEF之间配置有Nx接口,Local NEF和AF之间配置有N33接口,AF和Local PSA之间配置有N6接口,Local NEF和NEF之间配置有N33接口,Local NEF和PCF之间配置还有N5接口,NEF和PCF之间配置还有N5接口。
图4a至图4c为本申请实施例提供的下一代移动网络的架构示意图,本申请实施例可用于下一代移动网络架构,接下来对本申请实施例涉及的主要网元进行如下说明:
RAN用于实现无线有关的功能;
接入和移动性管理功能(access and mobility management function,AMF)负责用户的移动性管理,包括移动状态管理,分配用户临时身份标识,认证和授权用户。
SMF负责UPF网元选择,UPF网元重选,IP地址分配,负责承载的建立、修改和释放,QoS控制。具体可以在核心数据中心中部署SMF,在本地数据中心中部署I-SMF。
UPF可以部署在本地数据中心,例如UPF可以是Local PSA。UPF支持以下全部或者部分功能:将PDU会话与数据网络互连;分组路由和转发;数据包检测。
策略控制功能(policy control function,PCF)包含策略控制决策和基于流计费控制的功能,包含用户签约数据管理功能,策略控制功能,计费策略控制功能,QoS控制等等。
应用服务(application function,AF)向UE提供某种应用层服务,AF在向UE提供服务时,对服务质量QoS策略(Policy)和计费策略(Charging)有要求,且需要通知网络。同时,AF也需要核心网反馈的应用相关的信息。例如AF可以部署在EAS中。
网络能力开放功能(network exposure function,NEF)主要支持网络能力开放功能,对外开放网络能力和服务,3GPP网络功能(Network Function,NF)通过NEF向其他NF发布功能和事件。NF开放的能力和事件可以安全地开放给第三方应用。具体可以在核心数据中心中部署NEF,在本地数据中心中部署Local NEF。
如下以图5和图6所示的实施例分别介绍本申请实施例提供的技术方案。本申请实施例中,PCF根据应用功能网元标识(AF Id)、通知端点或本地报告指示确定在PCC规则中 携带通知端点、QoS Notification Control信息、Alternative QoS参数集(Parameter Set)以及AltQosId和AltSerId对应关系,其中,每个Alternative QoS参数集包括一个AltQosId和对应的候选参数。QoS Notification Control信息用于指示需要RAN发送QoS需求能否保障的通知。SMF向I-SMF发送通知端点对应的QoS Notification Control信息、本地报告指示、Alternative QoS Profile以及AltProId和AltSerId对应关系。SMF向Local PSA发送QoS Notification Control事件检测信息,用于检测事件报告的数据包信息进行延迟测量。当gNodeB检测到QoS Notification Control事件,向PSA发送用户面数据包,数据包中携带服务质量流标识(QFI)和QoS Notification Control事件、AltProId。Local PSA再通知I-SMF。I-SMF执行AltProId到AltSerId的映射。在跨gNodeB切换过程中,I-SMF根据接受的QoS Flow列表,判断之前不能保障QoS需求的QoS Flow在这个列表中,则I-SMF判断这个QoS Flow的QoS需求能够再次得到保障,于是向Local NEF或AF发送QoS需求能够得到保障的通知。通过上述交互方式,能够将QoS通知控制(Notification Control)事件高效的发送给应用功能网元,降低了传输时延。
本申请实施例基于图4a至图4c所述的通信系统架构,AF通过Local NEF或直接通过NEF请求事件检测,例如事件可以是QoS Notificaiton control事件。针对QoS Notification Control事件,RAN通过用户面将检测到的QoS Notification Control事件报告发送给Local PSA,Local PSA再发送给I-SMF,而I-SMF直接发送给AF或Local NEF。如图5所示,主要包括如下交互流程:
S501、UE和Local建立PDU会话。
gNodeB保存Local PSA由于接受上行数据包的核心网隧道信息(CN Tunnel Info),其中,CN Tunnel Info通常包括接收上行数据的IP地址和隧道标识(TEID)。
S502、若本地没有部署Local NEF,则AF向NEF发送服务质量创建请求消息,例如该服务质量创建请求消息可以是Nnef_AFsessionWithQoS_Create request消息,Nnef_AFsessionWithQoS_Create request消息中包括应用功能网元标识(AF Id)、UE地址、请求的业务信息(例如业务信息包括业务数据流描述信息、业务的QoS需求)、事件标识(例如事件标识可以是QoS Notification Control事件的标识)和通知端点(Notification Endpoint1a)。Notification Endpoint1a包括接收事件通知的目标通知地址Notification Target Address1a或是Notification Target Address1a和Notification Correlation Id1a。AF可以提供多个业务数据流的描述信息,并用数据流标识进行标识。
若本地部署Local NEF,则AF向Local NEF发送Nnef_AFsessionWithQoS_Create request消息,Nnef_AFsessionWithQoS_Create request消息中包括AF Id、UE地址、事件标识(例如事件标识可以是QoS Notification Control事件的标识)和通知端点Notification Endpoint1a。Notification Endpoint1a包括接收事件通知的目标通知地址Notification Target Address1a,或是Notification Target Address1a和Notification Correlation Id1a。Local NEF确定Notification Endpoint1b,保持与Notification Endpoint1a的对应关系。Local NEF可能还需要向NEF发送Nnef_AFsessionWithQoS_Create request消息,Nnef_AFsessionWithQoS_Create request消息中要携带步骤S502中收到的信息,该Nnef_AFsessionWithQoS_Create request中需要携带Notification Endpoint1b。
对于QoS Notification Control事件,AF请求的业务信息中还可能包括候选业务请求(Alternative Service Requirements),每一个Alternative Service Requirement用一个Alternative Service Requirement Id(简称AltSerId)。
S503、Local NEF或NEF向PCF发送策略授权创建消息,例如策略授权创建消息可以是Npcf_PolicyAuthorization_Create消息,Npcf_PolicyAuthorization_Create消息中包括AF Id、UE地址、请求的业务信息、事件标识(例如事件标识可以是QoS Notification Control事件的标识),和通知端点的信息,若没有部署Local NEF,通知端点的信息可以是Notification Endpoint1a,或若部署Local NEF,通知端点的信息可以是Notification Endpoint1b。
对于QoS Notification Control事件,AF请求的业务信息中还可能包括Alternative Service Requirements,每一个Alternative Service Requirement用一个Alternative Service Requirement Id(简称AltSerId)。
Npcf_PolicyAuthorization_Create消息中还携带本地报告指示信息,用于指示需要进行本地事件报告。
S504、PCF保存接收到的策略授权创建消息之后,向Local NEF或NEF返回确认消息。
S505、Local NEF或者NEF向AF返回确认消息。
S506、PCF根据接收到的信息进行策略决策,以生成PCC规则。例如为步骤S501建立的PDU会话制定PCC规则。PCC规则中包括业务信息,该业务信息可以包括业务数据流模板和QoS参数。PCF根据AF ID、Notification Endpiont1a/Notification Endpiont1b或本地报告指示,确定在PCC规则中包括Notification Endpiont1a或Notification Endpoint1b。可选地,PCF在PCC规则中还可以携带显式的本地报告指示。在本实施例中,还可以在PCC规则携带Notification Endpiont1a/Notification Endpoint1b以及显式的本地报告指示,用于指示SMF需要本地报告事件,不限定的是,SMF仍然可以通过控制面向PCF进行事件报告。PCF可以根据多个业务数据流描述信息制定不同的PCC规则,此时PCF还在PCC规则中携带对应的业务数据流标识。
针对QoS Notification Control事件,若请求消息中携带Alternative Service Requirements,则PCF还会根据Alternative Service Requirements在PCC规则中包括Alternative QoS Parameter Sets。每个Alternative QoS Parameter Set用一个Alternative QoS Parameter Set Id(简称AltQosId)标识。同时PCC规则中包括AltQosId和AltSerId的对应关系。
S507、PCF向PDU会话对应的SMF发送PCC规则。
S508、SMF安装PCC规则后,向PCF返回确认消息。
S509、SMF执行PCC规则,根据PCC规则中携带的QoS参数执行QoS Flow绑定后,决定创建或修改QoS Flow,SMF向I-SMF发送协议数据单元会话更新请求消息,例如协议数据单元会话更新请求消息可以是Nsmf_PDU Session_Update Request消息。若创建新的QoS Flow,SMF可以为QoS Flow分配QoS flow的标识和根据PCC规则的QoS参数制定对应的QoS文档(profile),并将QoS flow的标识和对应的QoS文档发送给I-SMF。若修改已有的QoS Flow,则SMF无需为修改后的QoS Flow分配标识但要修改已经创建的QoS文档, SMF向I-SMF发送QFI和修改后的QoS文档。SMF还可以向I-SMF发送通知端点的消息。若PCF提供了多个PCC规则,则SMF可能将不同的PCC规则绑定到不同的QoS Flow,则SMF根据绑定结果向I-SMF发送QoS Flow的标识、通知端点和业务数据流标识的对应关系。
针对QoS Notification Control事件,协议数据单元会话更新请求消息中包括QoS Notification Control指示和本地报告指示信息,用于指示需要进行本地事件报告或通过用户面进行事件报告。在本实施例中,在协议数据单元会话更新请求消息中携带本地报告指示信息,用于指示gNodeB通过用户面进行事件报告,并不排除gNodeB通过控制面进行事件报告。此外若PCC规则中携带Alternative QoS Parameter Sets,则SMF根据Alternative QoS Parameter Sets确定Alternative QoS Profiles,每个Alternative QoS Profile用Alternative QoS Profile Id(简称AltProId)标识。SMF在消息中携带AltProId和AltSerId的对应关系。
S510、I-SMF向AMF发送通信消息传输请求。
例如,该通信消息传输请求可以是Namf_Communication_N1N2MessageTransfer Request消息,Namf_Communication_N1N2MessageTransfer Request消息中携带QFI。
针对QoS Notification Control事件,Namf_Communication_N1N2MessageTransfer Request消息中包括QoS Notification Control指示和本地报告指示信息。若步骤S509的消息中携带Alternative QoS Profile,在Namf_Communication_N1N2MessageTransfer Request消息中还携带Alternative QoS Profile。
I-SMF保存QFI和通知端点的对应关系,或者I-SMF保存QFI、通知端点和业务数据里的对应关系。进一步地,I-SMF保存AltProId和AltSerId的对应关系。
S511、AMF与gNodeB交互,AMF将步骤S509接收到的信息发送给gNodeB。gNodeB进一步跟UE交互。
S512、AMF向I-SMF返回确认消息。
S513、I-SMF向SMF返回确认消息。
S514、I-SMF向Local PSA发送会话修改消息,会话修改消息中携带QFI。
针对QoS Notification Control事件,会话修改消息中携带QoS Notification Control信息用于指示Local PSA检测RAN发送的用于上报QoS Notification Control事件的数据包,并向I-SMF上报。
S515、Local PSA向I-SMF返回确认消息。
S516、针对QoS Notification Control事件,若gNodeB检测到QoS Flow的QoS Profile的QoS需求不能保障时,则gNodeB检测到事件。此时若gNodeB之前接收到了Alternative QoS Profile,则gNodeB判断当前能够保障的Alternative QoS Profile。若gNodeB正在执行的一个Alternative QoS Profile的QoS不能保障,则gNodeB检测到事件。gNodeB判断当前能够保障的其他Alternative QoS Profile。若gNodeB之前发送了QoS Flow的QoS需求不能保障的通知后,又检测到了QoS Flow的GBR能够保障,则gNodeB检测到事件。
可选的,gNodeB检测QoS Flow的QoS需求能否得到保障可以包括:gNodeB检测QoS Flow当前实际的服务质量,若QoS Flow当前实际的服务质量满足QoS Flow的QoS需求,则确 定QoS Flow的QoS需求能够得到保障,反之,则确定QoS Flow的QoS需求不能得到保障。
例如,以检测QoS Flow的保障带宽是否得到保障为例,gNodeB可以检测一段时间内QoS Flow上传输的业务数据流的最小传输速率,确定该业务数据流的最小传输速率是否满足保障传输的传输速率,若该业务数据流的最小传输速率大于或等于保障传输速率,则确定QoS Flow的QoS需求能够得到保障,反之,若该业务数据流的最小传输速率小于保障传输的传输速率,则确定QoS Flow的QoS需求不能得到保障。
S517、gNodeB向Local PSA发送数据包,数据包中携带QFI和不能保障QoS需求的指示信息或能够保障QoS需求的指示信息。针对不能保障QoS需求的指示信息,gNodeB还可能携带能够保证的Alternative QoS Profile的AltProId。gNodeB可以在一个数据包里包括多个QFI和对应的指示信息。
S518、Local PSA接收到携带QoS Notification Control事件报告的数据包,检测到事件。
S519、Local PSA向I-SMF发送事件报告。
Local PSA向I-SMF发送QFI和不能保障QoS需求的指示信息或能够保障QoS需求的指示信息。针对不能保障QoS需求的指示信息,事件报告中还包括的AltProId。I-SMF根据QFI确定Notification Endpoint1a或Notification Endpoint1b。根据AltProId确定AltSerId。若I-SMF还保存了QFI和业务数据流标识的对应关系,则I-SMF进一步确定业务数据流的标识。
S520a、若没有部署Local NEF,则I-SMF向AF发送事件报告,事件报告中携带Notification Endpoint1a。
事件报告中包括不能保障QoS需求的指示信息或能够保障QoS需求的指示信息。针对不能保障GBR的指示信息,事件报告中还包括的AltSerId。还可以在事件报告中包括业务数据流的标识。
S520b、若部署Local NEF,则I-SMF向Local NEF发送事件报告,事件报告中携带Notification Endpoint1b。
针对QoS Notification Control,事件报告中包括不能保障QoS需求的指示信息或能够保障QoS需求的指示信息。针对不能保障QoS需求的指示信息,事件报告中还包括的AltSerId。还可以在事件报告中包括业务数据流的标识。
S520c、Local NEF进一步向AF发送事件报告,事件报告中携带Notification Endpoint1a。
针对QoS Notification Control,事件报告中包括不能保障QoS需求的指示信息或能够保障QoS需求的指示信息。针对不能保障QoS需求的指示信息,事件报告中还包括的AltSerId。还可以在事件报告中包括业务数据流的标识。
对于图4b架构下的执行流程与图a架构下的流程类似,不同之处在于Local NEF向核心数据中心中的NEF发送消息,而核心数据中心中的NEF进一步向PCF发送消息。
对于图4c的架构,省略I-SMF和SMF之间的交互,由Local PSA向SMF发送通知消息,而SMF向Local NEF/AF发送通知消息。
如图6所示,当发生跨gNodeB切换时,I-SMF根据接受到的QoS flow list判断之前 发送不能保障QoS需求指示信息对应的QoS Flow是否则这个QoS flow list中,若存在QoS flow list中,则Local PSA向Local NEF或AF发送能够保障QoS需求的指示信息。具体的,主要包括如下流程:
S601、UE发生移动后,网络执行跨gNodeB的切换,例如通过Xn-based inter NG-RAN handover或Inter NG-RAN node N2 based handover完成从源gNodeB到目标(Target)gNodeB的切换。
S602、在切换过程中,目标gNodeB向AF发送QoS Flow列表,例如目标gNodeB发送路径切换请求或者切换请求确认消息,例如路径切换请求可以是N2 Path Switch Request,切换请求确认消息可以是handover request Acknowledge消息,路径切换请求或者切换请求确认消息中包括Target gNodeB接受的QoS Flow列表(List),其中包括接受的QFI列表。QoS flow list还可能包括接受的一个或多个QoS flow的Alternative QoS Profile Id(简称AltProId)。
S603、AMF向SMF发送会话管理上下文请求消息,例如会话管理上下文请求消息可以是Nsmf_PDUSession_UpdateSMContext Request消息,Nsmf_PDUSession_UpdateSMContext Request消息中包括接受的QoS flow list。QoS flow list还可能包括接受的一个或多个QoS flow的Alternative QoS Profile Id(简称AltProId)。
S604、SMF向AMF返回确认消息。
S605a、若没有部署Local NEF,若I-SMF判断之前发送不能保障QoS需求指示信息对应的QoS Flow在这个QoS flow list中,则I-SMF根据这个QoS Flow的QFI确定Notification Endpoint1a并向AF发送事件报告,事件报告中包括能够保障QoS需求的指示信息和Notification Endpoint1b。若这个QFI有对应的AltProId,则I-SMF还在事件报告中携带对应的AltSerId。若I-SMF还保存了QFI和业务数据流标识的对应关系,则I-SMF进一步确定业务数据流的标识,在事件报告中包括业务数据流的标识。
S605b、若部署了Local NEF,若I-SMF判断之前发送不能保障QoS需求指示信息对应的QoS Flow在这个QoS flow list中,则I-SMF根据这个QoS Flow的QFI确定Notification Endpoint1b并向Local NEF发送事件报告,事件报告中包括能够保障QoS需求的指示信息和Notification Endpoint1b。若这个QFI有对应的AltProId,则I-SMF还在事件报告中携带对应的AltSerId。若I-SMF还保存了QFI和业务数据流标识的对应关系,则I-SMF进一步确定业务数据流的标识,在事件报告中包括业务数据流的标识。
S605c、若部署了Local NEF,LocalNEF根据Notification Endpoint1b确定Notification Endpoint1a并向AF发送事件报告,事件报告中包括能够保障QoS需求的指示信息和Notification Endpoint1b。针对能够保障GBR的指示信息,事件报告中还可能携带AltSerId。事件报告中还可能携带业务数据流的标识。
通过前述的举例说明可知,针对QoS Notification Control事件,gNodeB通过用户面向Local PSA报告QoS Notification Control事件,Local PSA向I-SMF报告QoS Notification Control事件。若之前下发的Alternative QoS Profile还携带AltProId,I-SMF根据AltProId确定AltSerId。I-SMF向AF或Local AF报告事件。在跨gNodeB切换过程中,I-SMF判断之前不能保障GBR的QoS Flow在这个列表中,则I-SMF向Local NEF 或AF发送能够保证GBR的事件和AltSerId。本申请实施例中,I-SMF直接向本地应用发送检测到的QoS Notification Control,减少了网络时延,还能解决切换时的事件报告问题。UPF可以向本地应用直接发送事件报告,减少路由迂回。
在本申请的前述实施例中,对于图4c的架构,AMF可以直接与SMF交互,而SMF向Local NEF/AF发送通知消息。减少了网络时延,还能解决切换时的事件报告问题。UPF可以向本地应用直接发送事件报告,减少路由迂回。
需要说明的是,对于前述的各方法实施例,为了简单描述,故将其都表述为一系列的动作组合,但是本领域技术人员应该知悉,本申请并不受所描述的动作顺序的限制,因为依据本申请,某些步骤可以采用其他顺序或者同时进行。其次,本领域技术人员也应该知悉,说明书中所描述的实施例均属于优选实施例,所涉及的动作和模块并不一定是本申请所必须的。
为便于更好的实施本申请实施例的上述方案,下面还提供用于实施上述方案的相关装置。
请参阅图7所示,本申请实施例提供的一种第一会话管理网元700,可以包括:接收模块701、处理模块702、发送模块703,其中,
处理模块702,用于通过接收模块701接收来自用户面网元的第一报告信息,所述第一报告信息包括第一指示信息和第一候选服务质量QoS文档的标识,所述第一指示信息用于指示第一服务质量流QoS Flow的QoS需求不能得到保障;
处理模块702,用于通过发送模块703向应用功能网元发送第二报告信息,其中,所述第二报告信息包括第二指示信息和第一候选业务需求的标识,所述第一候选业务需求的标识对应所述第一候选QoS文档的标识,所述第二指示信息用于指示第一业务数据流的QoS需求不能得到保障,所述第一QoS Flow用于传输所述第一业务数据流,所述第一业务数据流是所述应用功能网元对应的应用的业务数据流。
在本申请的一些实施例中,所述第二指示信息根据所述第一指示信息确定。
在本申请的一些实施例中,处理模块702,用于当所述第一会话管理网元为中间会话管理网元时,接收来自用户面网元的第一报告信息之前,通过接收模块701接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
处理模块702,用于根据所述第一策略确定第二策略,并通过发送模块703向所述第一接入网网元发送所述第二策略,其中,所述第二策略包括所述第一QoS Flow的标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知控制指示信息根据所述第一QoS通知控制指示信息确定。
在本申请的一些实施例中,处理模块702,用于当所述第一会话管理网元为中间会话管理网元时,接收来自用户面网元的第一报告信息之前,通过接收模块701接收来自第二会话 管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
处理模块702,用于根据所述第一策略确定第三策略,并通过发送模块703向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息。
在本申请的一些实施例中,处理模块702,用于当所述第一指示信息包括所述第一QoS Flow的标识时,根据所述第一QoS Flow的标识确定所述应用功能网元的通知端点,并通过所述应用功能网元的通知端点向所述应用功能网元发送所述第二报告信息。
在本申请的一些实施例中,处理模块702,用于当所述第一会话管理网元为中间会话管理网元时,接收来自用户面网元的第一报告信息之前,通过接收模块701接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
处理模块702,用于根据所述第一策略确定第二策略,并通过发送模块703向所述第一接入网网元发送所述第二策略,所述第二策略包括所述第一QoS Flow标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知控制指示信息根据所述第一QoS通知控制指示信息确定。
在本申请的一些实施例中,处理模块702,用于当所述第一会话管理网元为中间会话管理网元时,接收来自用户面网元的第一报告信息之前,通过接收模块701接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
处理模块702,用于根据所述第一策略确定第三策略,并通过发送模块703向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息。
在本申请的一些实施例中,处理模块702,用于当所述第一指示信息包括所述第一QoS Flow的标识时,根据所述第一QoS Flow的标识确定所述本地网络能力开放网元的通知端点,并通过所述本地网络能力开放网元的通知端点向所述本地网络能力开放网元发送所述第二 报告信息,所述第二报告信息由所述本地网络能力开放网元向所述应用功能网元发送。
在本申请的一些实施例中,所述第一策略由所述第二会话管理网元根据来自策略控制网元的第四策略生成,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,所述至少一个候选QoS参数集用于所述第二会话管理网元确定所述至少一个候选QoS文档,所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识用于所述第二会话管理网元确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识。
在本申请的一些实施例中,处理模块702,用于接收来自用户面网元的第一报告信息之前,通过接收模块701接收来自策略控制网元的第四策略,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识;
处理模块702,用于根据至少一个候选QoS参数集确定所述至少一个候选QoS文档,并确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。
在本申请的一些实施例中,处理模块702,用于向应用功能网元发送第二报告信息之后,当终端设备从第一接入网网元切换至第二接入网网元时,通过接收模块701接收来自所述第二接入网网元的QoS Flow的标识信息,所述QoS Flow的标识信息包括所述第一QoS Flow的标识;通过发送模块703向所述应用功能网元发送第三报告信息,其中,所述第三报告信息包括第三指示信息,所述第三指示信息用于指示所述第一业务数据流的QoS需求不能得到保障。
在本申请的一些实施例中,处理模块702,用于通过接收模块701接收来自所述第二接入网网元的所述第一QoS Flow对应的第二候选QoS文档的标识;
其中,所述第三报告信息还包括第二候选业务需求的标识,所述第二候选业务需求的标识对应所述第二候选QoS文档的标识。
在本申请的一些实施例中,所述第二报告信息还包括所述第一业务数据流的标识信息。
在本申请的一些实施例中,所述第三报告信息还包括所述第一业务数据流的标识信息。
请参阅图8所示,本申请实施例提供的一种策略控制网元800,可以包括:接收模块801、处理模块802、发送模块803,其中,
处理模块802,用于通过接收模块801接收来自应用功能网元的业务请求,所述业务请求包括第一服务质量QoS通知控制指示信息和至少一个候选业务需求,所述第一QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;
处理模块802,用于根据所述业务请求生成第四策略,所述第四策略包括第二QoS通知控制指示信息、至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的所述至少一个候选业务需求的标识,其中,所述至少一个候选服务质量QoS参数集根据所述至少一个候选业务需求确定,所述第二QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;
处理模块802,用于通过发送模块803向第一会话管理网元发送所述第四策略。
在本申请的一些实施例中,所述业务请求还包括所述第一业务数据流的标识信息,所 述第四策略还包括所述第一业务数据流的标识信息。
需要说明的是,上述装置各模块/单元之间的信息交互、执行过程等内容,由于与本申请方法实施例基于同一构思,其带来的技术效果与本申请方法实施例相同,具体内容可参见本申请前述所示的方法实施例中的叙述,此处不再赘述。
本申请实施例还提供一种计算机存储介质,其中,该计算机存储介质存储有程序,该程序执行包括上述方法实施例中记载的部分或全部步骤。
接下来介绍本申请实施例提供的另一种第一会话管理网元,请参阅图9所示,第一会话管理网元900包括:
接收器901、发射器902、处理器903和存储器904(其中第一会话管理网元900中的处理器903的数量可以一个或多个,图9中以一个处理器为例)。在本申请的一些实施例中,接收器901、发射器902、处理器903和存储器904可通过总线或其它方式连接,其中,图9中以通过总线连接为例。
存储器904可以包括只读存储器和随机存取存储器,并向处理器903提供指令和数据。存储器904的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory,NVRAM)。存储器904存储有操作系统和操作指令、可执行模块或者数据结构,或者它们的子集,或者它们的扩展集,其中,操作指令可包括各种操作指令,用于实现各种操作。操作系统可包括各种系统程序,用于实现各种基础业务以及处理基于硬件的任务。
处理器903控制第一会话管理网元的操作,处理器903还可以称为中央处理单元(central processing unit,CPU)。具体的应用中,第一会话管理网元的各个组件通过总线系统耦合在一起,其中总线系统除包括数据总线之外,还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见,在图中将各种总线都称为总线系统。
上述本申请实施例揭示的方法可以应用于处理器903中,或者由处理器903实现。处理器903可以是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法的各步骤可以通过处理器903中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器903可以是通用处理器、数字信号处理器(digital signal processing,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现场可编程门阵列(field-programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器904,处理器903读取存储器904中的信息,结合其硬件完成上述方法的步骤。
接收器901可用于接收输入的数字或字符信息,以及产生与第一会话管理网元的相关设置以及功能控制有关的信号输入,发射器902可包括显示屏等显示设备,发射器902可用于通过外接接口输出数字或字符信息。
本申请实施例中,处理器903,用于执行前述第一会话管理网元执行的报告信息的发 送方法。
接下来介绍本申请实施例提供的另一种策略控制网元,请参阅图10所示,策略控制网元1000包括:
接收器1001、发射器1002、处理器1003和存储器1004(其中策略控制网元1000中的处理器1003的数量可以一个或多个,图10中以一个处理器为例)。在本申请的一些实施例中,接收器1001、发射器1002、处理器1003和存储器1004可通过总线或其它方式连接,其中,图10中以通过总线连接为例。
存储器1004可以包括只读存储器和随机存取存储器,并向处理器1003提供指令和数据。存储器1004的一部分还可以包括NVRAM。存储器1004存储有操作系统和操作指令、可执行模块或者数据结构,或者它们的子集,或者它们的扩展集,其中,操作指令可包括各种操作指令,用于实现各种操作。操作系统可包括各种系统程序,用于实现各种基础业务以及处理基于硬件的任务。
处理器1003控制策略控制网元的操作,处理器1003还可以称为CPU。具体的应用中,策略控制网元的各个组件通过总线系统耦合在一起,其中总线系统除包括数据总线之外,还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见,在图中将各种总线都称为总线系统。
上述本申请实施例揭示的方法可以应用于处理器1003中,或者由处理器1003实现。处理器1003可以是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法的各步骤可以通过处理器1003中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1003可以是通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1004,处理器1003读取存储器1004中的信息,结合其硬件完成上述方法的步骤。
本申请实施例中,处理器1003,用于执行策略控制网元执行的报告信息的发送方法。
在另一种可能的设计中,当第一会话管理网元、策略控制网元为芯片时,芯片包括:处理单元和通信单元,所述处理单元例如可以是处理器,所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令,以使该终端内的芯片执行上述第一方面任意一项的无线报告信息的发送方法。可选地,所述存储单元为所述芯片内的存储单元,如寄存器、缓存等,所述存储单元还可以是所述终端内的位于所述芯片外部的存储单元,如只读存储器(read-only memory,ROM)或可存储静态信息和指令的其他类型的静态存储设备,随机存取存储器(random access memory,RAM)等。
其中,上述任一处提到的处理器,可以是一个通用中央处理器,微处理器,ASIC,或一个或多个用于控制上述方法的程序执行的集成电路。
另外需说明的是,以上所描述的装置实施例仅仅是示意性的,其中所述作为分离部件 说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外,本申请提供的装置实施例附图中,模块之间的连接关系表示它们之间具有通信连接,具体可以实现为一条或多条通信总线或信号线。
通过以上的实施方式的描述,所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现,当然也可以通过专用硬件包括专用集成电路、专用CPU、专用存储器、专用元器件等来实现。一般情况下,凡由计算机程序完成的功能都可以很容易地用相应的硬件来实现,而且,用来实现同一功能的具体硬件结构也可以是多种多样的,例如模拟电路、数字电路或专用电路等。但是,对本申请而言更多情况下软件程序实现是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在可读取的存储介质中,如计算机的软盘、U盘、移动硬盘、ROM、RAM、磁碟或者光盘等,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述的方法。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘(Solid State Disk,SSD))等。

Claims (30)

  1. 一种报告信息的发送方法,其特征在于,包括:
    第一会话管理网元接收来自用户面网元的第一报告信息,所述第一报告信息包括第一指示信息和第一候选服务质量QoS文档的标识,所述第一指示信息用于指示第一服务质量流QoS Flow的QoS需求不能得到保障;
    所述第一会话管理网元向应用功能网元发送第二报告信息,其中,所述第二报告信息包括第二指示信息和第一候选业务需求的标识,所述第一候选业务需求的标识对应所述第一候选QoS文档的标识,所述第二指示信息用于指示第一业务数据流的QoS需求不能得到保障,所述第一QoS Flow用于传输所述第一业务数据流,所述第一业务数据流是所述应用功能网元对应的应用的业务数据流。
  2. 根据权利要求1所述的方法,其特征在于,所述第二指示信息根据所述第一指示信息确定。
  3. 根据权利要求1或2所述的方法,其特征在于,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    所述第一会话管理网元接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
    所述第一会话管理网元根据所述第一策略确定第二策略,并向所述第一接入网网元发送所述第二策略,其中,所述第二策略包括所述第一QoS Flow的标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知控制指示信息根据所述第一QoS通知控制指示信息确定。
  4. 根据权利要求1或2所述的方法,其特征在于,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    所述第一会话管理网元接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
    所述第一会话管理网元根据所述第一策略确定第三策略,并向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息。
  5. 根据权利要求3或4所述的方法,其特征在于,所述第一会话管理网元向应用功能网 元发送第二报告信息,包括:
    当所述第一指示信息包括所述第一QoS Flow的标识时,所述第一会话管理网元根据所述第一QoS Flow的标识确定所述应用功能网元的通知端点,并通过所述应用功能网元的通知端点向所述应用功能网元发送所述第二报告信息。
  6. 根据权利要求1或2所述的方法,其特征在于,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    所述第一会话管理网元接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
    所述第一会话管理网元根据所述第一策略确定第二策略,并向所述第一接入网网元发送所述第二策略,所述第二策略包括所述第一QoS Flow标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知控制指示信息根据所述第一QoS通知控制指示信息确定。
  7. 根据权利要求1或2所述的方法,其特征在于,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    所述第一会话管理网元接收来自第二会话管理网元的第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
    所述第一会话管理网元根据所述第一策略确定第三策略,并向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息。
  8. 根据权利要求6或7所述的方法,其特征在于,所述第一会话管理网元向应用功能网元发送第二报告信息,包括:
    当所述第一指示信息包括所述第一QoS Flow的标识时,所述第一会话管理网元根据所述第一QoS Flow的标识确定所述本地网络能力开放网元的通知端点,并通过所述本地网络能力开放网元的通知端点向所述本地网络能力开放网元发送所述第二报告信息,所述第二报告信息由所述本地网络能力开放网元向所述应用功能网元发送。
  9. 根据权利要求3至8中任一项所述的方法,其特征在于,所述第一策略由所述第二会话管理网元根据来自策略控制网元的第四策略生成,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,所述 至少一个候选QoS参数集用于所述第二会话管理网元确定所述至少一个候选QoS文档,所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识用于所述第二会话管理网元确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识。
  10. 根据权利要求1或2所述的方法,其特征在于,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    所述第一会话管理网元接收来自策略控制网元的第四策略,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识;
    所述第一会话管理网元根据至少一个候选QoS参数集确定所述至少一个候选QoS文档,并确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识。
  11. 根据权利要求1至10中任一项所述的方法,其特征在于,所述第一会话管理网元向应用功能网元发送第二报告信息之后,所述方法还包括:
    当终端设备从第一接入网网元切换至第二接入网网元时,所述第一会话管理网元接收来自所述第二接入网网元的QoS Flow的标识信息,所述QoS Flow的标识信息包括所述第一QoS Flow的标识;
    所述第一会话管理网元向所述应用功能网元发送第三报告信息,其中,所述第三报告信息包括第三指示信息,所述第三指示信息用于指示所述第一业务数据流的QoS需求不能得到保障。
  12. 根据权利要求11所述的方法,其特征在于,所述方法还包括:
    所述第一会话管理网元接收来自所述第二接入网网元的所述第一QoS Flow对应的第二候选QoS文档的标识;
    其中,所述第三报告信息还包括第二候选业务需求的标识,所述第二候选业务需求的标识对应所述第二候选QoS文档的标识。
  13. 根据权利要求1至12中任一项所述的方法,其特征在于,所述第二报告信息还包括所述第一业务数据流的标识信息。
  14. 根据权利要求11至13中任一项所述的方法,其特征在于,所述第三报告信息还包括所述第一业务数据流的标识信息。
  15. 一种报告信息的发送方法,其特征在于,包括:
    用户面网元向第一会话管理网元发送第一报告信息,所述第一报告信息包括第一指示信息和第一候选服务质量QoS文档的标识,所述第一指示信息用于指示第一服务质量流QoS Flow的QoS需求不能得到保障;
    所述第一会话管理网元接收来自所述用户面网元的所述第一报告信息;
    所述第一会话管理网元向应用功能网元发送第二报告信息,所述第二报告信息包括第二指示信息和第一候选业务需求的标识,所述第一候选业务需求的标识对应所述第一候选QoS文档的标识,所述第二指示信息用于指示第一业务数据流的QoS需求不能得到保障,所述第一QoS Flow用于传输所述第一业务数据流,所述第一业务数据流是所述应用功能网元对应的应用的业务数据流;
    所述应用功能网元接收所述第一会话管理网元发送的所述第二报告信息。
  16. 根据权利要求15所述的方法,其特征在于,所述第二指示信息根据所述第一指示信息确定。
  17. 根据权利要求15或16所述的方法,其特征在于,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    第二会话管理网元向所述第一会话管理网元发送第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求不能得到保障的指示信息;
    所述第一会话管理网元接收来自所述第二会话管理网元的所述第一策略;
    所述第一会话管理网元根据所述第一策略确定第二策略,并向所述第一接入网网元发送所述第二策略,其中,所述第二策略包括所述第一QoS Flow的标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知控制指示信息根据所述第一QoS通知控制指示信息确定;
    所述第一接入网网元接收所述第二策略。
  18. 根据权利要求15或16所述的方法,其特征在于,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    第二会话管理网元向所述第一会话管理网元发送第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、所述应用功能网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
    所述第一会话管理网元接收来自所述第二会话管理网元的所述第一策略;
    所述第一会话管理网元根据所述第一策略确定第三策略,并向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
    所述用户面网元接收所述第三策略。
  19. 根据权利要求17或18所述的方法,其特征在于,所述第一会话管理网元根据所述第一报告信息向应用功能网元发送第二报告信息,包括:
    当所述第一指示信息包括所述第一QoS Flow的标识时,所述第一会话管理网元根据所述第一QoS Flow的标识确定所述应用功能网元的通知端点,并通过所述应用功能网元的通知端点向所述应用功能网元发送所述第二报告信息。
  20. 根据权利要求15或16所述的方法,其特征在于,当所述第一会话管理网元为中间 会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    第二会话管理网元向所述第一会话管理网元发送第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
    所述第一会话管理网元接收来自所述第二会话管理网元的所述第一策略;
    所述第一会话管理网元根据所述第一策略确定第二策略,并向所述第一接入网网元发送所述第二策略,所述第二策略包括所述第一QoS Flow标识、第二QoS通知控制指示信息和所述至少一个候选QoS文档,所述第二QoS通知控制指示信息根据所述第一QoS通知控制指示信息确定;
    所述第一接入网网元接收所述第二策略。
  21. 根据权利要求15或16所述的方法,其特征在于,当所述第一会话管理网元为中间会话管理网元时,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    第二会话管理网元向所述第一会话管理网元发送第一策略,所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、本地网络能力开放网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
    所述第一会话管理网元接收来自所述第二会话管理网元的所述第一策略;
    所述第一会话管理网元根据所述第一策略确定第三策略,并向所述用户面网元发送所述第三策略,所述第三策略用于指示所述用户面网元发送所述第一QoS Flow的QoS需求能否得到保障的指示信息;
    所述用户面网元接收所述第三策略。
  22. 根据权利要求20或21所述的方法,其特征在于,所述第一会话管理网元向应用功能网元发送第二报告信息,包括:
    当所述第一指示信息包括所述第一QoS Flow的标识时,所述第一会话管理网元根据所述第一QoS Flow的标识确定所述本地网络能力开放网元的通知端点,并通过所述本地网络能力开放网元的通知端点向所述本地网络能力开放网元发送所述第二报告信息,所述第二报告信息由所述本地网络能力开放网元向所述应用功能网元发送。
  23. 根据权利要求17至22中任一项所述的方法,其特征在于,所述方法还包括:
    策略控制网元向所述第二会话管理网元发送第四策略,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识;
    所述第二会话管理网元接收来自策略控制网元的第四策略;
    所述第二会话管理网网元根据所述第四策略生成所述第一策略,其中,所述至少一个候选QoS参数集用于确定所述至少一个候选QoS文档;所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识用于确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识。
  24. 根据权利要求15或16所述的方法,其特征在于,所述第一会话管理网元接收来自用户面网元的第一报告信息之前,所述方法还包括:
    策略控制网元向所述第一会话管理网元发送第四策略,所述第四策略包括至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识;
    所述第一会话管理网元接收来自策略控制网元的所述第四策略;
    所述第一会话管理网网元根据所述第四策略生成第一策略,其中,所述至少一个候选QoS参数集用于确定至少一个候选QoS文档,所述至少一个候选QoS参数集的标识对应的至少一个候选业务需求的标识用于确定所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识;所述第一策略包括所述第一QoS Flow的标识、第一QoS通知控制指示信息、至少一个候选QoS文档、目标网元的通知端点的信息以及所述至少一个候选QoS文档的标识对应的至少一个候选业务需求的标识,其中,所述至少一个候选QoS文档包括所述第一候选QoS文档,所述至少一个候选业务需求的标识包括所述第一候选业务需求的标识,所述第一QoS通知控制指示信息用于指示发送所述第一QoS Flow的QoS需求能否得到保障的指示信息,所述目标网元包括:本地网络能力开放网元或者所述应用功能网元。
  25. 一种报告信息的发送方法,其特征在于,所述方法包括:
    策略控制网元接收来自应用功能网元的业务请求,所述业务请求包括第一服务质量QoS通知控制指示信息和至少一个候选业务需求,所述第一QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;
    所述策略控制网元根据所述业务请求生成第四策略,所述第四策略包括第二QoS通知控制指示信息、至少一个候选QoS参数集以及所述至少一个候选QoS参数集的标识对应的所述至少一个候选业务需求的标识,其中,所述至少一个候选服务质量QoS参数集根据所述至少一个候选业务需求确定,所述第二QoS通知控制指示信息用于指示发送第一业务数据流的QoS需求能否得到保障的指示信息;
    所述策略控制网元向第一会话管理网元发送所述第四策略。
  26. 根据权利要求25所述的方法,其特征在于,所述业务请求还包括所述第一业务数据流的标识信息,所述第四策略还包括所述第一业务数据流的标识信息。
  27. 一种通信装置,其特征在于,所述通信装置具体为第一会话管理网元,所述第一会话管理网元用于执行前述权利要求1至14中任一项所述的方法。
  28. 一种通信装置,其特征在于,所述通信装置具体为策略控制网元,所述策略控制网元用于执行前述权利要求25至26中任一项所述的方法。
  29. 一种通信系统,其特征在于,包括:用户面网元、第一会话管理网元和应用功能网元,其中,
    所述用户面网元用于执行前述权利要求15至24中所述用户面网元执行的任意一种方法;
    所述第一会话管理网元用于执行前述权利要求15至24中所述第一会话管理网元执行的任意一种方法;
    所述应用功能网元用于执行前述权利要求15至24中所述应用功能网元执行的任意一种方法。
  30. 根据权利要求29所述的通信系统,其特征在于,所述通信系统还包括如下至少一个:第二会话管理网元、策略控制网元、第一接入网网元、第二接入网网元、本地网络能力开放网元。
PCT/CN2021/073400 2020-01-23 2021-01-22 报告信息的发送方法和通信装置以及通信系统 WO2021148012A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21744326.6A EP4080828A4 (en) 2020-01-23 2021-01-22 REPORT INFORMATION SENDING METHOD, COMMUNICATION DEVICE AND SYSTEM
US17/868,224 US20220353746A1 (en) 2020-01-23 2022-07-19 Report information sending method, communication apparatus, and communication system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010077131.5 2020-01-23
CN202010077131.5A CN113162788B (zh) 2020-01-23 2020-01-23 报告信息的发送方法和通信装置以及通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/868,224 Continuation US20220353746A1 (en) 2020-01-23 2022-07-19 Report information sending method, communication apparatus, and communication system

Publications (1)

Publication Number Publication Date
WO2021148012A1 true WO2021148012A1 (zh) 2021-07-29

Family

ID=76882142

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/073400 WO2021148012A1 (zh) 2020-01-23 2021-01-22 报告信息的发送方法和通信装置以及通信系统

Country Status (4)

Country Link
US (1) US20220353746A1 (zh)
EP (1) EP4080828A4 (zh)
CN (1) CN113162788B (zh)
WO (1) WO2021148012A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114423029A (zh) * 2022-02-08 2022-04-29 深圳艾灵网络有限公司 服务质量参数调整方法、设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117280657A (zh) * 2021-08-04 2023-12-22 Oppo广东移动通信有限公司 传输方法、装置、设备及存储介质
CN115767652A (zh) * 2021-09-03 2023-03-07 中兴通讯股份有限公司 站点切换方法、基站、存储介质
CN117641467A (zh) * 2022-08-11 2024-03-01 华为技术有限公司 一种通信方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108738071A (zh) * 2017-04-20 2018-11-02 华为技术有限公司 一种资源建立的方法及装置
US20190132251A1 (en) * 2017-10-31 2019-05-02 Huawei Technologies Co., Ltd. Method and system for supporting multiple qos flows for unstructured pdu sessions
CN110049517A (zh) * 2018-01-16 2019-07-23 华为技术有限公司 QoS流的控制方法和装置
CN110603842A (zh) * 2017-05-08 2019-12-20 三星电子株式会社 用于在无线通信系统中配置qos流的方法和装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109729549B (zh) * 2017-10-30 2021-05-18 华为技术有限公司 通信方法及装置
US10986528B2 (en) * 2018-02-15 2021-04-20 Huawei Technologies Co., Ltd. Tracking QoS violated events
CN110519802B (zh) * 2018-05-21 2022-05-10 华为技术有限公司 一种数据处理方法、发送方法及装置
CN110691370B (zh) * 2018-07-06 2021-02-09 华为技术有限公司 一种数据传输方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108738071A (zh) * 2017-04-20 2018-11-02 华为技术有限公司 一种资源建立的方法及装置
CN110603842A (zh) * 2017-05-08 2019-12-20 三星电子株式会社 用于在无线通信系统中配置qos流的方法和装置
US20190132251A1 (en) * 2017-10-31 2019-05-02 Huawei Technologies Co., Ltd. Method and system for supporting multiple qos flows for unstructured pdu sessions
CN110049517A (zh) * 2018-01-16 2019-07-23 华为技术有限公司 QoS流的控制方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "PDU Session Modification procedures", 3GPP DRAFT; S2-170253_PDU SESSION MODIFICATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Spokane, WA, USA; 20170116 - 20170120, 16 January 2017 (2017-01-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051216442 *
See also references of EP4080828A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114423029A (zh) * 2022-02-08 2022-04-29 深圳艾灵网络有限公司 服务质量参数调整方法、设备及存储介质
CN114423029B (zh) * 2022-02-08 2023-12-19 深圳艾灵网络有限公司 服务质量参数调整方法、设备及存储介质

Also Published As

Publication number Publication date
CN113162788B (zh) 2022-12-27
US20220353746A1 (en) 2022-11-03
EP4080828A1 (en) 2022-10-26
CN113162788A (zh) 2021-07-23
EP4080828A4 (en) 2023-05-31

Similar Documents

Publication Publication Date Title
WO2021148012A1 (zh) 报告信息的发送方法和通信装置以及通信系统
US11917498B2 (en) Communication method and communications apparatus
US11871330B2 (en) Transparent session migration between user plane functions
EP3783862A1 (en) Session management method and session management function network element
WO2021213035A1 (zh) 网络辅助信息提供方法、装置、电子设备及计算机可读存储介质
WO2019076306A1 (zh) 数据传输通道的处理方法、装置和系统
WO2020259688A1 (zh) 用户面重路由方法及装置
US20230019215A1 (en) TSC-5G QoS MAPPING WITH CONSIDERATION OF ASSISTANCE TRAFFIC INFORMATION AND PCC RULES FOR TSC TRAFFIC MAPPING AND 5G QoS FLOWS BINDING
WO2020073159A1 (en) Notification control in a communication system
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2021190488A1 (zh) 一种建立连接的方法和通信装置以及系统
WO2018233451A1 (zh) 通信方法、装置和系统
WO2022007484A1 (zh) 重定向方法、网络设备、终端设备及可读存储介质
WO2016197306A1 (zh) 一种业务链策略的制定方法及设备
CN111586600A (zh) 网络辅助信息提供方法及相关设备
JP2023534597A (ja) リロケーション時にエッジアプリケーションサーバへのシームレスなサービス継続性を調整するためのメカニズム
WO2022022471A1 (zh) 一种媒体流切换方法及装置
JP2023547904A (ja) アプリケーションプログラム制御方法および装置、デバイス、並びに記憶媒体
WO2021197112A1 (zh) 一种数据传输的方法及装置
WO2019096332A1 (zh) 报文头压缩机制确定方法、设备及系统
WO2020010637A1 (zh) 一种无线通信方法及装置
WO2023035925A1 (zh) 一种业务处理方法、装置和系统
WO2022099484A1 (zh) 标识发送方法和通信装置
US11502778B2 (en) Method and apparatus for efficient delivery of source and forward error correction streams in systems supporting mixed unicast multicast transmission
WO2021190513A1 (zh) 一种数据传输方法、装置及系统

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: 21744326

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021744326

Country of ref document: EP

Effective date: 20220722

NENP Non-entry into the national phase

Ref country code: DE