WO2022179317A1 - 应用程序的控制方法、装置、设备及存储介质 - Google Patents

应用程序的控制方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2022179317A1
WO2022179317A1 PCT/CN2022/070546 CN2022070546W WO2022179317A1 WO 2022179317 A1 WO2022179317 A1 WO 2022179317A1 CN 2022070546 W CN2022070546 W CN 2022070546W WO 2022179317 A1 WO2022179317 A1 WO 2022179317A1
Authority
WO
WIPO (PCT)
Prior art keywords
qnc
application
notification message
core network
network entity
Prior art date
Application number
PCT/CN2022/070546
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 KR1020237011660A priority Critical patent/KR20230062622A/ko
Priority to JP2023525508A priority patent/JP2023547904A/ja
Priority to EP22758683.1A priority patent/EP4199576A4/en
Publication of WO2022179317A1 publication Critical patent/WO2022179317A1/zh
Priority to US17/985,278 priority patent/US20230070295A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0257—Traffic management, e.g. flow control or congestion control per individual bearer or channel the individual bearer or channel having a maximum bit rate or a bit rate guarantee
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0273—Traffic management, e.g. flow control or congestion control adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP]

Definitions

  • the embodiments of the present application relate to the field of mobile communications, and in particular, to a method, apparatus, device, and medium for controlling an application program.
  • QoS control is performed according to a QoS flow (QoS Flow) unit.
  • GBR Guaranteed Bit Rate
  • N-Guaranteed Bit Rate Non-Guaranteed Bit Rate
  • non-GBR QoS traffic such as common audio and video calls and online conferences. Because changes in wireless network status often cause such audio and video communications to be stuck, it is necessary to optimize the QoS control of non-GBR QoS flows.
  • the present application provides an application control method, device, device and storage medium, and provides a QNC mechanism for non-GBR QoS flows, so that the application entity perceives the change of the wireless network state, and then actively controls the running of the application to prevent adapt to the change.
  • the technical solution is as follows:
  • a method for controlling an application comprising:
  • the application entity receives the notification message sent by the core network entity, and the notification message is used to indicate that the change of the parameter value of the quality of service notification control (QoS Notification Control, QNC) of the non-GBR bearer flow satisfies the reporting condition;
  • QNC quality of service notification control
  • the application entity controls the application according to the notification message.
  • a method for controlling an application program comprising:
  • the core network entity receives the notification message sent by the access network device, where the notification message is used to indicate that the change of the parameter of the quality of service notification control QNC of the non-guaranteed bit rate GBR stream satisfies the reporting condition;
  • the core network entity sends the notification message to the application entity, so that the application entity controls the flow of the application program according to the notification message.
  • an apparatus for controlling an application program includes:
  • a receiving module configured to receive a notification message sent by the core network entity, where the notification message is used to indicate that the change of the parameter value of the QNC of the non-GBR bearer stream satisfies the reporting condition;
  • a control module configured to control the application program according to the notification message.
  • an apparatus for controlling an application program includes:
  • a receiving module configured to receive a notification message sent by the access network device, where the notification message is used to indicate that the change of the parameter of the quality of service notification control QNC of the non-guaranteed bit rate GBR stream satisfies the reporting condition;
  • a sending module configured to send the notification message to an application entity, so that the application entity controls the flow of the application program according to the notification message.
  • a network element device includes: a processor and a memory, the memory stores a computer program, and the computer program is executed by the processor to make the network A meta-device to implement the control method of the application as described above.
  • a chip is provided, the chip includes a programmable logic circuit, and the programmable logic circuit is used to implement the control method for an application program as described above when running.
  • a computer-readable storage medium stores a computer program, and the computer program is loaded and executed by a processor to implement the above-described application program control method.
  • a computer program product comprising computer instructions stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the application program control method provided by the above aspects.
  • a notification message is sent to the application entity through the core network entity.
  • the flow provides a QNC mechanism, so that the application entity can know the change of the wireless network state of the non-GBR carrying flow, and then actively control the operation of the application program to adapt to the change. For example, the calculation strategy and traffic strategy of the application program are controlled, so that the application entity can adjust the application program to adapt to the network transmission under the parameter change when the parameters of the QNC become worse, or recover from the difference to the better.
  • FIG. 1 shows a structural block diagram of a mobile communication system provided by an exemplary embodiment of the present application
  • FIG. 2 shows a structural block diagram of a mobile communication system provided by another exemplary embodiment of the present application
  • FIG. 3 shows a flowchart of a method for notifying a QoS change provided by an exemplary embodiment of the present application
  • FIG. 4 shows a flowchart of a method for notifying a QoS change provided by another exemplary embodiment of the present application
  • FIG. 5 shows a flowchart of a configuration method of a QNC provided by an exemplary embodiment of the present application
  • FIG. 6 shows a flowchart of a configuration method of a QNC provided by another exemplary embodiment of the present application
  • FIG. 7 shows a flowchart of a configuration method of a QNC provided by another exemplary embodiment of the present application.
  • Fig. 8 shows the flow chart of the optimization method of QNC provided by an exemplary embodiment of the present application
  • Fig. 9 shows the flow chart of the optimization method of QNC provided by another exemplary embodiment of the present application.
  • FIG. 10 shows a schematic diagram of a UE or network-requested PDU session modification (for non-roaming and local grooming roaming) process provided by an exemplary embodiment of the present application;
  • FIG. 11 shows a schematic diagram of an SM policy association modification process provided by an exemplary embodiment of the present application.
  • FIG. 12 shows a schematic diagram of a PDU session establishment process requested by a UE provided by an exemplary embodiment of the present application
  • FIG. 13 shows a flowchart of a PDU session establishment process requested by a UE for a home routing roaming scenario provided by an exemplary embodiment of the present application
  • FIG. 14 shows a schematic diagram of the process of transferring an AF request for a single UE address to a related PCF provided by an exemplary embodiment of the present application
  • FIG. 15 shows a schematic diagram of a PDU session modification process requested by a UE or network for non-roaming and local grooming roaming provided by an exemplary embodiment of the present application
  • FIG. 16 shows a schematic diagram of a PDU session modification process requested by a UE or a network for home routing roaming provided by an exemplary embodiment of the present application
  • FIG. 17 shows a control device of an application program provided by an exemplary embodiment of the present application
  • FIG. 18 shows a control device of an application program provided by an exemplary embodiment of the present application
  • FIG. 19 shows a block diagram of a network element device provided by an exemplary embodiment of the present application.
  • FIG. 1 shows a schematic diagram of the architecture of a mobile communication system provided by an exemplary embodiment of the present application.
  • the system architecture 100 may include: a user equipment (User Equipment, UE), a radio access network (Radio Access Network, RAN), a core network (Core), and a data network (Data Network, DN).
  • UE, RAN, and Core are the main components of the architecture. Logically, they can be divided into two parts: the user plane and the control plane.
  • the control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data.
  • the NG2 reference point is located between the RAN control plane and the Core control plane
  • the NG3 reference point is located between the RAN user plane and the Core user plane
  • the NG6 reference point is located between the Core user plane and the data network.
  • the UE It is the portal for mobile users to interact with the network. It can provide basic computing capabilities and storage capabilities, display service windows to users, and accept user operation input. The UE will use the next-generation air interface technology to establish a signal connection and a data connection with the RAN, thereby transmitting control signals and service data to the mobile network.
  • RAN Similar to the base station in the traditional network, it is deployed close to the UE to provide network access functions for authorized users within the cell coverage area, and can use transmission tunnels of different quality to transmit user data according to user levels and service requirements.
  • the RAN can manage its own resources, utilize them rationally, provide access services for the UE on demand, and forward control signals and user data between the UE and the core network.
  • Core responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing functions such as session management, mobility management, policy management, and security authentication for the UE.
  • the UE When the UE is attached, it provides network access authentication for the UE; when the UE has a service request, it allocates network resources for the UE; when the UE moves, it updates the network resources for the UE; when the UE is idle, it provides a fast recovery mechanism for the UE;
  • the DN It is a data network that provides business services for users.
  • the client is located in the UE, and the server is located in the data network.
  • the data network can be a private network, such as a local area network, or an external network that is not controlled by operators, such as the Internet, or a private network jointly deployed by operators, such as in order to configure the IP Multimedia Core Network. Subsystem, IMS) service.
  • IMS IP Multimedia Core Network. Subsystem
  • Figure 2 is a detailed architecture determined on the basis of Figure 1, wherein the core network user plane includes a user plane function (User Plane Function, UPF); the core network control plane includes an authentication server function (Authentication Server Function, AUSF), access and Access and Mobility Management Function (AMF), Session Management (Session Management Function, SMF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Function Storage Function (NF Repository Function, NRF), Unified Data Management (Unified Data Management, UDM), Policy Control Function (Policy Control Function, PCF), Application Function (Application Function, AF).
  • the functions of these functional entities are as follows:
  • UPF perform user data packet forwarding according to the routing rules of SMF
  • AUSF perform security authentication of the UE
  • AMF UE access and mobility management
  • SMF UE session management
  • NSSF select network slice for UE
  • NEF Open network functions to third parties in the form of API interfaces
  • NRF Provides the storage function and selection function of network function entity information for other network elements
  • UDM user subscription context management
  • PCF User Policy Management
  • the N1 interface is the reference point between the UE and the AMF; the N2 interface is the reference point between the RAN and the AMF, used for sending NAS messages, etc.; the N3 interface is the reference point between the RAN and the UPF, It is used to transmit data on the user plane, etc.; the N4 interface is the reference point between the SMF and the UPF, and is used to transmit information such as the tunnel identification information of the N3 connection, the data buffer indication information, and the downlink data notification message; the N6 interface is the UPF and the UPF. The reference point between DNs, used to transmit data on the user plane, etc.
  • Next Generation (NG) interface The interface between the radio access network equipment and the 5G core network.
  • the name of the interface between each network element in FIG. 1 and FIG. 2 is just an example, and the name of the interface in the specific implementation may be other names, which are not specifically limited in this embodiment of the present application.
  • the names of various network elements (such as SMF, AF, UPF, etc.) included in Fig. 1 and Fig. 2 are also only an example, and do not limit the functions of the network elements themselves.
  • the above-mentioned network elements may also have other names, which are not specifically limited in this embodiment of the present application.
  • network elements may use the terminology in 5G, and may also use other names, etc., which will be uniformly described here, and will not be repeated below.
  • names of the messages (or signaling) transmitted between the above network elements are only an example, and do not constitute any limitation on the functions of the messages themselves.
  • the foregoing network element entities may be implemented as computer equipment, or virtual computer equipment running in the computer equipment.
  • a quick change QoS notification control (Quick Change QoS Notification Control, QCQNC) mechanism is defined for the non-GBR QoS flow.
  • the QCQNC mechanism is a type of QNC, which may be referred to as QNC for short.
  • the access network device sends a fast change notification to the SMF when it detects that at least one QoS parameter of the non-GBR QoS flow rapidly changes.
  • SMF sends fast change notifications to PCF, AF and UE. After receiving the notification of rapid change, AF and UE adjust their internal applications so that the application can adapt to the change, so as to prevent the occurrence of QoE (Quality of Experience) that affects the service experience such as stuck.
  • QoE Quality of Experience
  • a QoS flow is the smallest granularity of QoS differentiation in a PUD session.
  • QoS Flow ID (QFI) is used in 5G systems to distinguish QoS flows.
  • the QoS flow is controlled by the SMF, and the QoS flow can be pre-configured or established in the PDU session establishment procedure, or modified in the PDU session modification procedure.
  • 5G QoS Identifier 5G QoS Identifier, 5QI
  • Allocation and Retention Priority ARP
  • Reflective QoS Attribute RQA
  • GBR delay critical GBR or non-GBR.
  • PDB Packet Delay Budget
  • the first two parameters Resource Type and Priority Level define the features of 5QI, while the last two parameters, PDB and PER, define the performance of 5QI.
  • the Profile (characteristic) of the QoS QNC is related to the three parameters PDB, PER and the current transmission rate (Current Bit Rate, CBR) of the NGBF (Non GBR QoS Flow).
  • CBR Current Bit Rate
  • the RAN detects that the value of any one of these three parameters increases or decreases a rate of change (or, increases or decreases a change value) exceeds a specified threshold (due to the different properties of different parameters, for each parameter, Its corresponding change rate or change value is different), then send a notification message to SMF, and notify the change rate or change value of all parameter changes.
  • the SMF sends a notification message to the PCF, the PCF sends a notification message to the AF, and the application program corresponding to the AF makes corresponding adjustments.
  • the SMF sends a notification message to the UE through the NAS message, and the corresponding application program of the UE can also make corresponding adjustments, thereby realizing the interaction between the network and the application, realizing the optimization of service transmission, and solving the jam when the network is congested, or When the network conditions become better, the application still uses a very low transmission rate, which cannot make full use of network resources, but cannot improve the user experience.
  • the change rate is uniformly defined as the parameter value before and after the change (the larger value – Smaller value)/smaller value, or the rate of change is uniformly defined as the parameter value before and after the change (larger value–smaller value)/larger value, or the rate of change is uniformly defined as the parameter value before and after the change (larger value–smaller value) smaller value)/a fixed value.
  • the larger value is the parameter value before and after the change with the larger absolute value
  • the smaller value is the parameter value before and after the change with the smaller absolute value
  • a fixed value is a predetermined value that does not change. In this way, when the parameter value A first increases by 30%, and then decreases by 30%, it returns to the original parameter value A.
  • Whether a QoS flow is GBR or non-GBR is determined by its QoS configuration.
  • the QoS configuration of the QoS flow is sent to the (R)AN, containing the following QoS parameters (details of the QoS parameters are defined in subsection 5.7.2 of the communication protocol TS23.501).
  • the QoS configuration can also contain QoS parameters:
  • the QoS configuration can also contain QoS parameters:
  • GFBR Guaranteed Flow Bit Rate
  • MFBR Maximum Flow Bit Rate
  • the QoS configuration may also contain one or more QoS parameters
  • a QoS Quick Change Notification control Profile is provided.
  • the QoS fast change notification control configuration is provided for non-GBR QoS flows that have fast change notification control enabled. If the corresponding PCC rules contain relevant information (as described in the communication protocol TS 23.503), the SMF shall provide the NG-RAN with the rapid change notification control configuration in addition to the QoS profile. If the SMF provides the NG-RAN with the fast change notification control configuration (if the corresponding Policy and Charging Control Rule (PCC) rule information has changed), the NG-RAN will replace the previously stored configuration with it .
  • PCC Policy and Charging Control Rule
  • the fast change notification control configuration indicates the fast change of any QoS parameters PDB, PER and detected CBR (current bit rate), which will help the application to control the application traffic according to the changed QoS parameters.
  • the rapid change notification control configuration indicates that (PDR, PER, CBR) changes rapidly (increase or decrease) in a short time (20%, 10%, 30%), and the new value after the change can be maintained continuously, that is, this rapid Changes are not short and fast spikes caused by sudden shocks and other reasons.
  • the fast change notification control configuration can be any combination of PDB, PER, CBR, for example, the fast change notification control configuration can set the increased (or decreased) PDR to 20%; it can also be an increased (or decreased) PDR and PER set to 20%, increase (or decrease) CBR by 10%; or increase (or decrease) CBR by 30%.
  • the NG-RAN When the NG-RAN sends a quick change notification that satisfies the QCQNC configuration to the SMF, the NG-RAN should also include the current QoS parameters (PDB, PER) and CBR in the notification message.
  • the current QoS parameters PDB, PER
  • the QNC mechanism for non-GBR bearer flows includes at least the following processes:
  • FIG. 3 is a flowchart of a method for notifying a QoS change provided by an exemplary embodiment of the present application. This embodiment is illustrated by taking the method applied to the mobile communication system shown in FIG. 1 or FIG. 2 as an example. The method includes:
  • Step 320 the access network device sends a notification message to the application entity through the core network entity when the change of the parameter of the QNC of the non-GBR bearer flow satisfies the reporting condition;
  • a non-GBR bearer stream refers to a bearer stream of a non-GBR type.
  • Non-GBR bearer flows include: non-GBR QoS flows, or, non-GBR EPS bearers.
  • a non-GBR bearer flow is a non-GBR type QoS flow
  • a non-GBR bearer flow is a non-GBR type EPS bearer.
  • the parameters of the QNC include at least one of the following: PDB, PER, and CBR.
  • the reporting conditions corresponding to the at least two parameters are the same; and/or the reporting conditions corresponding to the at least two parameters are different.
  • reporting conditions include at least one of the following:
  • the change value of the parameters of the QNC in the first time period is greater than the first threshold
  • the first threshold is a decimal greater than 0 and less than 1.
  • the first thresholds are 20%, 30% and 40%.
  • the first duration is the period or duration used to calculate the change value, such as 1 second, 2 seconds.
  • the rate of change of the parameters of the QNC in the second time period is greater than the second threshold
  • the second threshold is a decimal greater than 0 and less than 1.
  • the second thresholds are 20%, 30% and 40%.
  • the second duration is the period or duration used to calculate the rate of change, such as 1 second, 2 seconds.
  • the change value of the parameters of the QNC within the first time period is greater than the first threshold value, and the third threshold value is continuously maintained;
  • the third threshold is a threshold for measuring the holding time of the changed value, such as 2 seconds.
  • the rate of change of the parameters of the QNC in the second time period is greater than the second threshold, and the fourth threshold is maintained continuously.
  • the fourth threshold is a threshold for measuring the hold time of the rate of change, such as 2 seconds.
  • the notification message also carries: the changed parameter value of the QNC. That is, the current parameter value of the QNC parameter after the QNC parameter changes rapidly.
  • the "current" is a relative concept, not the current in an absolute sense.
  • the current parameter value is the parameter value when the reporting condition is triggered, and is not necessarily equal to the real-time parameter value after the notification message is sent.
  • the parameter value of the changed QNC may be represented by a quantized value of the parameter value of the changed QNC.
  • the value range of QNC is divided into 16 non-overlapping sub-ranges. Each of the 16 sub-intervals corresponds to a unique quantized value, and the quantized value is represented by four bits.
  • the parameter value of the changed QNC belongs to the i-th sub-interval, it is represented by the quantized value corresponding to the i-th sub-interval.
  • the quantized value only needs 4 bits, which can reduce the transmission resources required for the notification message.
  • Step 340 The application entity controls the application according to the notification message.
  • the notification message (or referred to as fast change notification, fast change report, notification report) is used to indicate that the change of the parameters of the QoS notification control QNC of the non-GBR bearer flow satisfies the reporting condition.
  • the application entity controls at least one of the operation parameters, operation policies and traffic of the application program according to the notification message, so that the application program can adapt to the rapid change of the relevant parameters of the non-GBR bearer flow.
  • SDF Service Data Flow
  • SDFs with different QoS requirements are mapped to independent QoS flows. For example, an SDF with a first QoS requirement is mapped to a first QoS flow, and an SDF with a second QoS requirement is mapped to a second QoS flow.
  • SDFs with the same QoS requirements can be mapped to the same QoS flow.
  • one or more QoS flows corresponding to an application program include a non-GBR QoS flow, and the non-GBR QoS flow is used to transmit voice, video, text, message, file, control information and other services in the Data packets of at least one service.
  • the method provided by this embodiment sends a notification message to the application entity through the core network entity when the increase/decrease of the parameter of the QNC of the non-GBR bearer flow meets the reporting condition, and the application entity receives the notification message after receiving the notification message.
  • control the application program according to the notification message thereby providing a QNC mechanism for the non-GBR bearer flow, so that the application entity can learn the change of the wireless network state of the non-GBR bearer flow, and then actively control the operation of the application program to adapt to the change.
  • the calculation strategy and traffic strategy of the application program are controlled, so that the application entity can adjust the application program to adapt to the network transmission under the parameter change when the parameters of the QNC become worse, or recover from the difference to the better.
  • the steps performed by the access network device can be implemented independently as an embodiment on the access network device side; the steps performed by the application entity can be implemented independently as an embodiment on the application entity side, which will not be repeated in this application.
  • FIG. 4 is a flowchart of a method for notifying a QoS change provided by another exemplary embodiment of the present application. This embodiment is illustrated by taking the method applied to the mobile communication system shown in FIG. 1 or FIG. 2 as an example. The method includes:
  • Step 322 the access network device sends a notification message to the core network entity when the change of the parameter of the QNC of the non-GBR bearer flow satisfies the reporting condition;
  • the core network entity receives the notification message sent by the access network device.
  • the notification message is used to indicate that the change of the parameters of the QoS notification control QNC of the non-GBR bearer flow satisfies the reporting condition.
  • the notification message also carries: the changed parameter value of the QNC. That is, after the parameters of the QNC change rapidly, the current parameter values of the parameters of the QNC.
  • the "current" is a relative concept, not the current in an absolute sense.
  • the current parameter value is the parameter value when the reporting condition is triggered, and is not necessarily equal to the real-time parameter value after the notification message is sent.
  • the parameter value of the changed QNC may be represented by a quantized value of the parameter value of the changed QNC.
  • the value range of QNC is divided into 16 non-overlapping sub-ranges. Each of the 16 sub-intervals corresponds to a unique quantized value, and the quantized value is represented by four bits.
  • the parameter value of the changed QNC belongs to the i-th sub-interval, it is represented by the quantized value corresponding to the i-th sub-interval.
  • the quantized value only needs 4 bits, which can reduce the transmission resources required for the notification message.
  • Step 324 the core network entity sends a notification message to the application entity
  • the multiple core network entities transmit the notification message in sequence, and different core network entities may use different types of messages to carry the notification message.
  • the core network entities include: Mobility Management Entity (MME), Serving GateWay (SGW), PDN Gateway (PDN GateWay, PGW) and PCF, then the transmission path of the notification message includes at least RAN ⁇ MME ⁇ SGW/PGW ⁇ PCF ⁇ AF; for another example, if the core network entities include: the first core network entity AMF, the second core network entity SMF and the third core network entity PCF, the transmission path of the notification message includes at least RAN ⁇ AMF ⁇ SMF ⁇ PCF ⁇ AF.
  • the core network entity sends an event report (Event Reporting) to the application entity, where the event report carries a notification message.
  • Event Reporting an event report
  • Step 342 the application entity receives the notification message sent by the core network entity
  • the application entity receives the event report sent by the core network entity.
  • Step 344 The application entity controls the application according to the notification message.
  • the application entity controls at least one of the computing strategy and the traffic strategy of the application program according to the notification message, so that the application program adapts to the rapid change of the relevant parameters of the non-GBR bearer flow, so as to ensure the user's QoE as much as possible and avoid the phenomenon such as freezing.
  • the application corresponds to four SDFs: a voice SDF, a video SDF, a text message SDF, and a control plane SDF.
  • Four SDFs correspond to four non-GBR QoS flows, and the QNC mechanism is enabled for the four non-GBR QoS flows respectively.
  • the control application is executed according to the first calculation strategy
  • the control application is executed according to the second calculation strategy
  • the computing duration of the same computing task under the first computing strategy is shorter than the computing duration under the second computing strategy.
  • Compute policies are policies related to the running computation of an application.
  • the calculation strategy includes, but is not limited to, at least one of an encoding/decoding method selection strategy, an encoding/decoding model selection strategy, an encoding/decoding level selection strategy, a compression level selection strategy, and a neural network model selection strategy.
  • the control application uses the first codec mode to encode and decode; in response to the notification message being used to indicate the parameter value of the QNC When it becomes better, the control application uses the second codec method to encode and decode.
  • Encoding and decoding here refers to at least one of encoding and decoding.
  • the computation duration of the same encoding/decoding task under the first encoding/decoding strategy is shorter than that under the second encoding/decoding strategy.
  • the application program can compensate for the deterioration of the network delay by reducing the internal calculation time, and the overall transmission delay can still be kept unchanged or changed very little. For example, if the PDR of the non-GBR QoS flow corresponding to the video becomes poor, the encoding bit rate of the video is reduced to reduce the number and/or size of video data packets.
  • the control application is executed according to the first traffic policy
  • the control application is executed according to the second traffic policy
  • the traffic of the first traffic policy is less than the traffic of the second traffic policy.
  • the traffic of the application includes voice data packets and video data packets
  • the first flow corresponding to the voice data packet is maintained, and the second flow corresponding to the video data packet is reduced; in response to the notification message being used to indicate that the parameter value of the QNC becomes better, the voice
  • the first traffic corresponding to the data packet is added to the second traffic corresponding to the video data packet.
  • the flow of the first non-GBR QoS flow corresponding to video is reduced, and the flow of the second non-GBR QoS flow corresponding to voice is maintained, thereby occupying less wireless resources as a whole to increase voice data Packet transmission quality and reduce interference.
  • the application entity adjusts the application program according to the changed parameter value of the QNC, so that when the relevant parameters of the non-GBR bearer flow become worse, or the When the relevant parameters are recovered from bad to good, the application entity can adjust its internal application program to adapt to the parameter change, so as to optimize the operation of the application program.
  • the method provided by this embodiment also changes the calculation strategy of the application program when the relevant parameters of the non-GBR bearer flow become worse, and compensates for the deterioration of the network delay by reducing the calculation time inside the application program, and can still ensure the overall The transmission delay does not change or changes very little.
  • the traffic policy of the application program is changed when the relevant parameters of the non-GBR bearer stream become worse, such as maintaining the traffic of voice data packets and reducing the traffic of video data packets, so as to avoid the occurrence of adverse effects on users.
  • the relevant parameters of the non-GBR bearer stream become worse, such as maintaining the traffic of voice data packets and reducing the traffic of video data packets, so as to avoid the occurrence of adverse effects on users.
  • the stuttering that affects the audio so as to improve the user experience when using audio and video programs as much as possible.
  • the core network entity performs the QNC configuration process to the access network device. That is, the core network entity sends the QNC configuration to the access network device, and the QNC configuration is used to configure the parameters and reporting conditions of the QNC (or change threshold, rapid change threshold, change reporting threshold, and rapid change reporting threshold).
  • FIG. 5 is a flowchart of a QNC configuration method provided by an exemplary embodiment of the present application. This embodiment is illustrated by taking the method applied to the mobile communication system shown in FIG. 1 or FIG. 2 as an example. The method includes:
  • Step 420 the third core network entity PCF sends the QNC parameters and reporting conditions to the second core network entity SMF;
  • the third core network entity is an entity in the core network responsible for policy management.
  • the second core network entity is an entity in the core network responsible for session management.
  • the third core network entity PCF sends the QNC parameters and reporting conditions to the second core network entity SMF.
  • a (th) QoS flow will be established, and this QoS flow is called a QoS flow based on a default QoS rule (QoS Flow with Default QoS Rules).
  • this QoS flow is of non-GBR type, and the third core network entity may provide the QNC parameters and reporting conditions to the second core network entity.
  • the parameters of the QNC and the reporting conditions are determined by the third core network entity PCF; or, the parameters of the QNC and the reporting conditions are determined by the third core network entity PCF based on the service flow information sent by the application entity; or , the parameters and reporting conditions of the QNC are determined by the third core network entity PCF based on the subscription data of the UE.
  • Step 440 the second core network entity SMF receives the PCC rule sent by the third core network entity PCF;
  • Step 460 The second core network entity sends a QNC configuration (QNC Profile) to the access network device, where the QNC configuration is used to configure the QNC parameters and reporting conditions to the access network device.
  • QNC Configuration QNC Profile
  • the method provided by this embodiment can trigger the second core network entity to configure the QNC parameters and Report the conditions to complete the QNC configuration process.
  • the application entity provides service flow information to the third core network entity, and the service flow information carries the QNC parameters and reporting conditions required (or suggested) by the application entity, as shown in FIG. 6 .
  • the third core network entity determines QNC parameters and reporting conditions based on the QNC subscription data, as shown in FIG. 7 .
  • FIG. 6 is a flowchart of a QNC configuration method provided by another exemplary embodiment of the present application. This embodiment is illustrated by taking the method applied to the mobile communication system shown in FIG. 1 or FIG. 2 as an example. The method includes:
  • Step 412 the application entity AF sends the control parameters of the QNC to the third core network entity PCF;
  • the control parameters of the QNC include: whether to enable the QNC, at least one of the parameters of the QNC, and a change threshold.
  • the application entity AF sends a policy authorization creation/update message to the core network entity, and the policy authorization creation/update message carries the control parameters of the QNC.
  • the third core network entity PCF receives the policy authorization creation/update message sent by the application entity AF.
  • Step 420 the third core network entity PCF sends the PCC rule to the second core network entity SMF, where the PCC rule carries the control parameters of the QNC;
  • Step 440 the second core network entity SMF receives the PCC rule sent by the third core network entity PCF;
  • Step 460 The second core network entity sends the QNC configuration to the access network device, where the QNC configuration is used to configure the control parameters of the QNC to the access network device.
  • the active interaction between the application entity and the core network entity can be realized, and the application entity can drive the wireless access network equipment.
  • Networks (such as 5G, 4G's RAN) report rapid changes in non-GBR bearer flows, thereby opening up their network capabilities to application entities by the radio access network device network, providing a new way for Internet application innovation.
  • FIG. 7 is a flowchart of a QNC configuration method provided by another exemplary embodiment of the present application. This embodiment is illustrated by taking the method applied to the mobile communication system shown in FIG. 1 or FIG. 2 as an example. The method includes:
  • Step 414 the fourth core network entity UDM sends QNC subscription data to the third core network entity PCF, where the QNC subscription data carries the control parameters of the QNC;
  • the fourth core network entity UDM sends the QNC subscription data to the second core network entity SMF, and the second core network entity SMF sends the QNC subscription data to the third core network entity PCF.
  • Step 420 the third core network entity PCF sends a default QoS rule to the second core network entity SMF, and the default QoS rule carries the control parameters of the QNC;
  • Step 440 the second core network entity SMF receives the default PCC rule sent by the third core network entity PCF;
  • Step 460 The second core network entity sends the QNC configuration to the access network device, where the QNC configuration is used to configure the control parameters of the QNC to the access network device.
  • the third core network entity determines the control parameters of the QNC based on the subscription data of the UE, so that the subscription based on the UE can also be realized without the AF providing the control parameters of the QNC.
  • the data-driven radio access network device network reports rapid changes of non-GBR bearer flows to the UE.
  • the third core network entity PCF or the application entity AF finds that the notification messages of the QNC are too frequent, a large amount of signaling is caused to the system. At this time, the third core network entity PCF or the application entity AF should modify the reporting conditions of the QNC, such as increasing the change threshold.
  • FIG. 8 is a flowchart of a method for optimizing a QNC provided by an exemplary embodiment of the present application. This embodiment is illustrated by taking the method applied to the mobile communication system shown in FIG. 1 or FIG. 2 as an example. The method includes:
  • Step 520 the third core network entity PCF sends the updated QNC control parameters to the second core network entity SMF when the reporting frequency of the notification message is greater than or less than the frequency threshold;
  • the control parameters of the updated QNC include at least one of: whether to enable the QNC, parameters of the updated QNC, and an updated change threshold. That is, the updated control parameter of the QNC can update at least one of the QNC enabled, the QNC parameter, and the change threshold.
  • the third core network entity PCF when the reporting frequency of the notification message is greater than the frequency threshold, the third core network entity PCF sends an instruction to disable QNC to the second core network entity SMF; for another example, when the reporting frequency of the notification message by the third core network entity PCF is greater than When the frequency threshold is set, the parameters of the reduced QNC are sent to the second core network entity SMF; for another example, when the reporting frequency of the notification message is greater than the frequency threshold, the third core network entity PCF sends the increased QNC parameters to the second core network entity SMF. change threshold.
  • Step 540 The second core network entity SMF sends the QNC configuration to the access network device, where the QNC configuration carries the updated control parameters of the QNC.
  • the updated control parameters of the QNC are sent to the second core network entity SMF and the access network device, so as to avoid any The system causes a large signaling overhead, or the notification mechanism of the QNC is used reasonably.
  • FIG. 9 is a flowchart of a method for optimizing a QNC provided by another exemplary embodiment of the present application. This embodiment is illustrated by taking the method applied to the mobile communication system shown in FIG. 1 or FIG. 2 as an example. The method includes:
  • Step 510 when the reporting frequency of the notification message is greater than or less than the frequency threshold, the application entity sends the updated control parameters of the QNC to the third core network entity PCF;
  • the control parameters of the updated QNC include at least one of: whether to enable the QNC, parameters of the updated QNC, and an updated change threshold. That is, the updated control parameter of the QNC can update at least one of the QNC enabled, the QNC parameter, and the change threshold.
  • the AF when the reporting frequency of the notification message is greater than the frequency threshold, the AF sends an instruction to disable QNC to the third core network entity PCF; for another example, when the reporting frequency of the notification message is greater than the frequency threshold, the AF sends an instruction to the third core network entity to the third core network entity
  • the PCF sends the parameters of the reduced QNC; for another example, when the reporting frequency of the notification message is greater than the frequency threshold, the AF sends the increased change threshold to the third core network entity PCF.
  • Step 520 the third core network entity PCF sends the updated control parameters of the QNC to the second core network entity SMF;
  • Step 540 The second core network entity SMF sends the QNC configuration to the access network device, where the QNC configuration carries the updated control parameters of the QNC.
  • the AF when the reporting frequency of the notification message is greater than or less than the frequency threshold, the AF triggers the PCF to send the updated QNC control parameters to the second core network entity SMF and the access network device. , which can avoid causing a large signaling overhead to the system, or reasonably utilize the QNC notification mechanism.
  • the base station When the network where the UE is located changes, that is, the base station detects that the radio resources change rapidly (become better or worse). When the change reaches the change threshold defined by the QNC, the RAN will trigger the notification process of the QNC and send a notification message to the AF.
  • the notification message carries the parameter value (current parameter value) of the changed QNC parameter.
  • the base station first sends the notification message to the SMF, then the SMF sends the notification message to the PCF, and the PCF sends the notification message to the AF.
  • FIG. 10 shows a schematic diagram of a UE or network-requested PDU session modification (for non-roaming and local grooming roaming) process provided by an exemplary embodiment of the present application.
  • step 1e the RAN sends an N2 message (PDU session ID, SM information) to the AMF, and the AMF sends a Namf_PDUSession_UpdateSMContext message to the SMF.
  • N2 message PDU session ID, SM information
  • the two messages carry a notification message.
  • the notification message also carries the transformed parameter value of the QNC.
  • step 2 the SMF initiates a session management (Session Management, SM) policy association modification process, and sends a notification message to the PCF and the AF.
  • Session Management Session Management, SM
  • step 5 the SMF sends a PDU session modification command to the UE, and sends the changed parameter value of the QNC to the UE.
  • the SMF will send the The UE initiates a PDU session modification command to notify the UE of the current parameter values (PDB, PER, CBR) of the QNC of the QFI corresponding to the current QNC.
  • PDB current parameter values
  • step 9 the UE responds with a PDU session modification confirmation.
  • the PDU session modification command and the PDU session modification confirmation are transparently transmitted between the UE and the SMF through the RAN.
  • the SM policy association modification process shown in the above step 2 is defined by FIG. 11 . As shown in Figure 11:
  • step 1 the SMF sends an Npcf_SMPolicyControl_Update request to the PCF, and the request carries a notification message.
  • step 2 the PCF sends an event report Npcf_PolicyAuthorizationNotify to the AF, and the event report carries a notification message.
  • FIG. 12 shows a schematic diagram of a PDU session establishment process requested by a UE according to an exemplary embodiment of the present application.
  • the SMF sends a new SM policy association establishment request message to the PCF, and the PCF sends an SM policy association establishment response message to the SMF, which carries the control parameters of the QNC; or, the SMF sends the SM policy association modification to the PCF request message, the PCF sends the SM policy association modification response message to the SMF, and the message carries the control parameters of the QNC.
  • a QoS flow (usually the first one) will be established, this QoS flow is called a QoS flow based on the default QoS rules (no longer similar to the default bearer of 4G, 5G no longer uses the default QoS flow to name).
  • this default QoS rule is of non-GBR type
  • the PCF can include the control parameters of the QNC in the PCC rule. Then in step 7b or 9 of FIG. 12 , if the 5QI in the Default QoS Rule provided by the PCF is of NGBR type, the PCF can provide the control parameters of QCQNC to the SMF.
  • the SMF sends a Namf_Communication_N1N2 information conversion message to the AMF, and the message carries the QNC configuration according to the control parameters of the QCQNC provided by the PCF.
  • the subscription data of the UE includes the default 5QI and the default ARP. If the default 5QI is of NGBR type, QNC subscription data is added.
  • the UDM provides the message containing the QNC subscription data to the SMF, then the SMF provides the QNC subscription data to the PCF, and then the default QoS rules provided by the PCF contain the control parameters of the QNC.
  • the PDU session establishment procedure can be used for PDU session handover from N3GPP to 3GPP. If in step 7b, or 9, the PCF provides the control parameters of the QNC for any non-GBR QoS flow, the control parameters of the QNC are added in steps 11 and 12, similar to the above.
  • step 11 includes the control parameters of the QNC.
  • FIG. 13 shows a flow chart of a PDU session establishment process requested by a UE for a home routing roaming scenario provided by an exemplary embodiment of the present application.
  • a QoS flow (usually the first one) will be established, this QoS flow is called a QoS flow based on the default QoS rules (no longer similar to the default bearer of 4G, 5G no longer uses the default QoS flow to name).
  • this default QoS rule is of non-GBR type
  • the PCF can include the control parameters of the QNC in the PCC rule. Then, in the message of step 9b or 11 in FIG. 13 , if the 5QI in the default QoS rule provided by the PCF is of non-GBR type, the PCF can provide the control parameters of the QNC. Then, in the messages in steps 13, 14 and 15, the QNC configuration is added.
  • the subscription data of the UE includes the default 5QI and the default ARP. If the default 5QI is of NGBR type, QNC subscription data is added.
  • the UDM provides the subscription data containing the QNC to the SMF, and the SMF provides the subscription data of the QNC to the PCF. Then, the default QoS rules provided by the PCF contain the control parameters of the QNC.
  • FIG. 14 shows a schematic diagram of the process of transferring an AF request for a single UE address to a related PCF provided by an exemplary embodiment of the present application.
  • FIG. 15 shows a schematic diagram of a PDU session modification process requested by a UE or a network for non-roaming and local grooming roaming provided by an exemplary embodiment of the present application.
  • the AF sends a Npcf_PolicyAuthorization_Create/Update message to the PCF, and the QNC control parameter is added to the (one or more) media component (Media Component) information contained in the message.
  • the media component contains the control parameters of QNC, the media is requested to be transmitted on the NGBF; if the media component does not contain the QCQNC parameters, it indicates that the media can be transmitted on the NGBF or It is transmitted on GBF (GBR QoS Flow, GBR QoS data flow).
  • step 1b of Figure 15 the PCF sends a Npcf_SMPolicyControlUpdateNotify request message.
  • the control parameters of the QNC are added to the PCC rule of (one or more) SDFs (Service Data Flow, service data flow, one SDF corresponds to one media flow provided by the AF).
  • control parameters including the QNC are carried in the messages in steps 3b and 4 of FIG. 15 .
  • FIG. 16 shows a schematic diagram of a PDU session modification process requested by a UE or a network for home routing roaming provided by an exemplary embodiment of the present application.
  • step 1b, step 3, step 4b, and step 5 of FIG. 16 is to add one or more control parameters of the QNC (ie each possible service flow, SDF, QoS Flow).
  • Step 3 in FIG. 16 is a new step relative to the scenario described in FIG. 15 , that is, adding the control parameters of the QNC to the QoS parameters of one or more QoS flows.
  • NR-gNB When applied to 4G system, NR-gNB is replaced by eNB.
  • the interaction between PCF and AF does not make any changes.
  • the interaction between SMF and PCF is modified to the interaction between PGW and PCF.
  • 5G's QoS Flow is replaced by 4G's EPS Bearer.
  • 5QI of 5G is replaced by 4G QCI.
  • the interaction between RAN and AMF/SMF in 5G is replaced by the interaction between RAN and MME in 4G.
  • FIG. 17 shows a block diagram of an apparatus for controlling an application provided by an exemplary embodiment of the present application.
  • the device includes:
  • the receiving module 1720 is used for the application entity to receive the notification message sent by the core network entity, where the notification message is used to indicate that the change of the parameter value of the QNC of the non-GBR bearer stream satisfies the reporting condition;
  • the control module 1740 is configured to control the application according to the notification message.
  • control module 1740 is configured to control the computing strategy of the application program according to the notification message; and/or the control module 1740 is configured to control the computing strategy according to the notification message Controls the traffic policy for the application.
  • control module 1740 is configured to, in response to the notification message being used to indicate that the parameter value of the QNC becomes worse, control the application to execute according to the first calculation strategy;
  • the notification message is used to indicate that the parameter value of the QNC becomes better, and the application is controlled to be executed according to the second calculation strategy;
  • the computing duration of the same computing task under the first computing strategy is shorter than the computing duration under the second computing strategy.
  • control module 1740 is configured to, in response to the notification message being used to indicate that the parameter value of the QNC becomes worse, control the application to use the first encoding and decoding mode to encode Decoding; in response to the notification message being used to indicate that the parameter value of the QNC becomes better, controlling the application to use the second encoding and decoding mode to perform encoding and decoding;
  • the computation duration of the same encoding/decoding task under the first encoding/decoding strategy is shorter than the computation duration under the second encoding/decoding strategy.
  • control module 1740 is configured to control the application to execute according to the first traffic policy in response to the notification message being used to indicate that the parameter value of the QNC becomes worse; response When the notification message is used to indicate that the parameter value of the QNC becomes better, the application is controlled to be executed according to the second traffic policy;
  • the traffic of the first traffic policy is less than the traffic of the second traffic policy.
  • the traffic of the application includes voice data packets and video data packets
  • the control module 1740 is configured to maintain the first flow corresponding to the voice data packet and reduce the second flow corresponding to the video data packet in response to the notification message being used to indicate that the parameter value of the QNC becomes worse; In response to the notification message being used to indicate that the parameter value of the QNC becomes better, the first flow corresponding to the voice data packet is maintained, and the second flow corresponding to the video data packet is increased.
  • the notification message is sent to the core network entity by the access network device entity when it detects that the change of the parameter of the QNC of the non-GBR bearer flow satisfies the reporting condition of.
  • the notification message includes:
  • the changed parameter value of the QNC or, the quantized value of the changed parameter value of the QNC.
  • the device further includes:
  • the sending module 1760 is configured to send the control parameter of the QNC to the core network entity, where the control parameter of the QNC is used to indicate the parameter of the QNC and the reporting condition.
  • the sending module 1760 is configured to send a policy authorization creation/update message to the core network entity, where the policy authorization creation/update message carries the control parameters of the QNC.
  • the method further includes:
  • the application entity sends the changed QNC control parameters to the core network entity when the reporting frequency of the notification message is greater than or less than a frequency threshold.
  • the parameter value of the QNC includes at least one of the following:
  • the parameter values of the QNC include at least two kinds;
  • the reporting conditions corresponding to at least two kinds of the parameter values are the same; and/or the reporting conditions corresponding to at least two kinds of the parameter values are different.
  • the reporting condition includes at least one of the following:
  • the change value of the parameter value of the QNC within the first duration is greater than the first threshold
  • the rate of change of the parameter value of the QNC in the second time period is greater than the second threshold
  • the change value of the parameter value of the QNC within the first time period is greater than the first threshold value, and the third threshold value is continuously maintained;
  • the rate of change of the parameter value of the QNC within the second time period is greater than the second threshold, and the fourth threshold is continuously maintained;
  • the third threshold and the fourth threshold are thresholds used to measure the holding time.
  • the third threshold is a threshold for measuring the holding time of the change value
  • the fourth threshold is a threshold for measuring the holding time of the change rate.
  • the non-GBR bearer stream includes:
  • a non-GBR quality of service QoS flow or, a non-GBR Evolved Packet System EPS bearer.
  • the QNC is defined in the uplink; or, the QNC is defined in the downlink; or, the QNC is defined in the uplink and the downlink.
  • the target service flow is a service flow that enables the QNC and includes parameter values of the QNC.
  • Fig. 18 shows a block diagram of an apparatus for controlling an application provided by an exemplary embodiment of the present application.
  • the device includes:
  • the receiving module 1820 is used for the core network entity to receive a notification message sent by the access network device, where the notification message is used to indicate that the change of the parameter of the quality of service notification control QNC of the non-guaranteed bit rate GBR stream satisfies the reporting condition;
  • the sending module 1840 is configured to send the notification message to an application entity, so that the application entity can control the flow of the application program according to the notification message.
  • the sending module 1840 is used for the core network entity to send an event report to the application entity, where the event report carries the notification message.
  • the notification message includes:
  • the changed parameter value of the QNC or, the quantized value of the changed parameter value of the QNC.
  • the sending module 1840 is configured to send the QNC configuration to the access network device according to the control parameter of the QNC;
  • control parameter of the QNC is used to indicate the parameter of the QNC and the reporting condition.
  • the receiving module 1820 is configured to receive a policy authorization creation/update message sent by the application entity, where the policy authorization creation/update message carries the control parameters of the QNC.
  • the receiving module 1820 is configured to acquire subscription data of the QNC, where the subscription data of the QNC carries the control parameters of the QNC.
  • FIG. 19 shows a schematic structural diagram of a network element device 1900 provided by an embodiment of the present application.
  • the network element device may be used to execute the control method for the above application program.
  • the network element device 1900 is an application entity or a core network entity.
  • the network element device 1900 may include: a processor 1901 , a receiver 1902 , a transmitter 1903 , a memory 1904 and a bus 1905 .
  • the processor 1901 includes one or more processing cores, and the processor 1901 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1902 and the transmitter 1903 may be implemented as a transceiver 1906, which may be a communication chip.
  • the memory 1904 is connected to the processor 1901 through a bus 1905.
  • the memory 1904 can be used to store a computer program, and the processor 1901 is used to execute the computer program, so as to implement various steps performed by the application entity, core network element or core network entity in the above method embodiments.
  • the memory 1904 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, and the volatile or non-volatile storage device includes but is not limited to: RAM (Random-Access Memory, random access memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory, Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory, Electrically Erasable Programmable Read-Only Memory) memory), flash memory or other solid-state storage technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc, high-density digital video disc) or other optical storage, tape cassettes, magnetic tapes, magnetic disks storage or other magnetic storage devices.
  • RAM Random-Access Memory, random access memory
  • ROM Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory or other solid-
  • the present application further provides a computer-readable storage medium, where at least one instruction, at least one piece of program, code set or instruction set is stored in the storage medium, the at least one instruction, the at least one piece of program, the code set or The instruction set is loaded and executed by the processor to implement the application control method provided by the above method embodiments.
  • the present application also provides a computer program product, wherein the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the application program control method provided by the above aspects.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种应用程序的控制方法、装置、设备及存储介质，属于通信领域。该方法包括：应用实体接收核心网实体发送的通知消息(320)，通知消息用于表示非保证比特速率GBR承载流的服务质量通知控制QNC的参数值的变化满足上报条件；应用实体根据通知消息控制应用程序(340)。本申请能够使得应用实体感知到非GBR承载流的无线网络状态的变化，进而根据该变化来主动控制应用程序的运行。

Description

应用程序的控制方法、装置、设备及存储介质
本申请要求申请号202110215376.4，申请日2021年02月25日，发明名称为“应用程序的控制方法、装置、设备及存储介质”的中国申请的优先权，其全部内容引用在本申请中。
技术领域
本申请实施例涉及移动通信领域，特别涉及一种应用程序的控制方法、装置、设备及介质。
背景技术
在第五代(5th-Generation，5G)移动通信技术中，按照QoS流(QoS Flow)为单位进行QoS控制。
按照承载类型进行区分，QoS流分为保证比特速率(Guaranteed Bit Rate，GBR)和非保证比特速率(Non-Guaranteed Bit Rate，非GBR)两种。对于GBR的QoS流，在网络资源紧张的情况下，相应的比特速率也能够保证；对于非GBR的QoS流，在网络资源紧张的情况下，需要承受降低速率的要求。
目前90％以上的业务流量都是非GBR QoS流，比如常见的音视频通话以及在线会议等。因为无线网络状态的变化经常会造成这种音视频通信的卡顿出现，因此需要对非GBR QoS流的QoS控制进行优化。
发明内容
本申请提供了一种应用程序的控制方法、装置、设备及存储介质，提供一种针对非GBR QoS流的QNC机制，使得应用实体感知到无线网络状态的变化，进而主动控制应用程序的运行以适应该变化。所述技术方案如下：
根据本申请的一个方面，提供了一种应用程序的控制方法，所述方法包括：
应用实体接收核心网实体发送的通知消息，所述通知消息用于表示非GBR承载流的服务质量通知控制(QoS Notification Control，QNC)的参数值的变化满足上报条件；
所述应用实体根据所述通知消息控制所述应用程序。
根据本申请的另一方面，提供了一种应用程序的控制方法，所述方法包括：
核心网实体接收接入网设备发送的通知消息，所述通知消息用于表示非保证比特速率GBR流的服务质量通知控制QNC的参数的变化满足上报条件；
所述核心网实体向应用实体发送所述通知消息，以便所述应用实体根据所述通知消息控制应用程序的流量。
根据本申请的另一方面，提供了一种应用程序的控制装置，所述装置包括：
接收模块，用于接收核心网实体发送的通知消息，所述通知消息用于表示非GBR承载流的QNC的参数值的变化满足上报条件；
控制模块，用于根据所述通知消息控制所述应用程序。
根据本申请的另一方面，提供了一种应用程序的控制装置，所述装置包括：
接收模块，用于接收接入网设备发送的通知消息，所述通知消息用于表示非保证比特速率GBR流的服务质量通知控制QNC的参数的变化满足上报条件；
发送模块，用于向应用实体发送所述通知消息，以便所述应用实体根据所述通知消息控制应用程序的流量。
根据本申请的一个方面，提供了一种网元设备，所述网元设备包括：处理器和存储器，所述存储器存储有计算机程序，所述计算机程序由所述处理器运行以使得所述网元设备以实现如上所述的应用程序的控制方法。
根据本申请的一个方面，提供了一种芯片，所述芯片包括可编程逻辑电路，所述可编程 逻辑电路在运行时用于实现如上所述的应用程序的控制方法。
根据本申请的另一方面，提供了一种计算机可读存储介质，所述存储介质存储有计算机程序，所述计算机程序由处理器加载并执行以实现如上所述的应用程序的控制方法。
根据本申请的另一方面，提供了一种计算机程序产品，所述计算机程序产品包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行上述方面提供的应用程序的控制方法。
本申请实施例提供的技术方案带来的有益效果至少包括：
在非GBR承载流的QNC的参数的增加/减少满足上报条件时，通过核心网实体向应用实体发送通知消息，应用实体在接收到通知消息后，根据通知消息控制应用程序，从而针对非GBR承载流提供了QNC机制，使得应用实体能够获知非GBR承载流的无线网络状态的变化，进而主动地控制应用程序的运行来适应该变化。比如控制应用程序的计算策略和流量策略，使得在QNC的参数变差的情况下，或者，由差恢复为好的情况下，应用实体能够调整应用程序来适应该参数变化下的网络传输。
附图说明
图1示出了本申请一个示例性实施例提供的移动通信系统的结构框图；
图2示出了本申请另一个示例性实施例提供的移动通信系统的结构框图；
图3示出了本申请一个示例性实施例提供的QoS变化的通知方法的流程图；
图4示出了本申请另一个示例性实施例提供的QoS变化的通知方法的流程图；
图5示出了本申请一个示例性实施例提供的QNC的配置方法的流程图；
图6示出了本申请另一个示例性实施例提供的QNC的配置方法的流程图；
图7示出了本申请另一个示例性实施例提供的QNC的配置方法的流程图；
图8示出了本申请一个示例性实施例提供的QNC的优化方法的流程图；
图9示出了本申请另一个示例性实施例提供的QNC的优化方法的流程图；
图10示出了本申请的一个示例性实施例提供的UE或网络请求的PDU会话修改(用于非漫游和本地疏导漫游)流程的示意图；
图11示出了本申请一个示例性实施例提供的SM策略关联修改流程的示意图；
图12示出了本申请一个示例性实施例提供的UE请求的PDU会话建立流程的示意图；
图13示出了本申请一个示例性实施例提供的用于归属路由漫游场景的UE请求的PDU会话建立流程的流程图；
图14示出了本申请一个示例性实施例提供的针对单个UE地址的AF请求转移到相关PCF流程的示意图；
图15示出了本申请一个示例性实施例提供的用于非漫游和本地疏导漫游的UE或网络请求的PDU会话修改流程的示意图；
图16示出了本申请一个示例性实施例提供的用于归属路由漫游的UE或网络请求的PDU会话修改流程的示意图；
图17示出了本申请一个示例性实施例提供的应用程序的控制装置；
图18示出了本申请一个示例性实施例提供的应用程序的控制装置；
图19示出了本申请一个示例性实施例提供的网元设备的框图。
具体实施方式
图1示出了本申请一个示例性实施例提供的移动通信系统的架构示意图。如图1所示，该系统架构100可以包括：用户设备(User Equipment，UE)、无线接入网设备(Radio Access Network，RAN)、核心网(Core)和数据网络(Data Network，DN)构成。其中，UE、RAN、Core是构成架构的主要成分，逻辑上它们可以分为用户面和控制面两部分，控制面负责移动网络的管理，用户面负责业务数据的传输。在图1中，NG2参考点位于RAN 控制面和Core控制面之间，NG3参考点位于RAN用户面和Core用户面之间，NG6参考点位于Core用户面和数据网络之间。
UE：是移动用户与网络交互的入口，能够提供基本的计算能力、存储能力，向用户显示业务窗口，接受用户操作输入。UE会采用下一代空口技术，与RAN建立信号连接、数据连接，从而传输控制信号和业务数据到移动网络。
RAN：类似于传统网络里面的基站，部署在靠近UE的位置，为小区覆盖范围的授权用户提供入网功能，并能够根据用户的级别，业务的需求等使用不同质量的传输隧道传输用户数据。RAN能够管理自身的资源，合理利用，按需为UE提供接入服务，把控制信号和用户数据在UE和核心网之间转发。
Core：负责维护移动网络的签约数据，管理移动网络的网元，为UE提供会话管理、移动性管理、策略管理、安全认证等功能。在UE附着的时候，为UE提供入网认证；在UE有业务请求时，为UE分配网络资源；在UE移动的时候，为UE更新网络资源；在UE空闲的时候，为UE提供快恢复机制；在UE去附着的时候，为UE释放网络资源；在UE有业务数据时，为UE提供数据路由功能，如转发上行数据到DN；或者从DN接收UE下行数据，转发到RAN，从而发送给UE。
DN：是为用户提供业务服务的数据网络，一般客户端位于UE，服务端位于数据网络。数据网络可以是私有网络，如局域网，也可以是不受运营商管控的外部网络，如Internet，还可以是运营商共同部署的专有网络，如为了配置IP多媒体网络子系统(IP Multimedia Core Network Subsystem，IMS)服务。
图2是在图1的基础上确定的详细架构，其中核心网用户面包括用户面功能(User Plane Function，UPF)；核心网控制面包括认证服务器功能(Authentication Server Function，AUSF)、接入和移动管理(Access and Mobility Management Function，AMF)、会话管理(Session Management Function，SMF)、网络切片选择功能(Network Slice Selection Function，NSSF)、网络开放功能(Network Exposure Function，NEF)、网络功能仓储功能(NF Repository Function，NRF)、统一数据管理(Unified Data Management，UDM)、策略控制功能(Policy Control Function，PCF)、应用功能(Application Function，AF)。这些功能实体(简称功能或实体)的功能如下：
UPF：根据SMF的路由规则执行用户数据包转发；
AUSF：执行UE的安全认证；
AMF：UE接入和移动性管理；
SMF：UE会话管理；
NSSF：为UE选择网络切片；
NEF：以API接口的方式向第三方开放网络功能；
NRF：为其他网元提供网络功能实体信息的存储功能和选择功能；
UDM：用户签约上下文管理；
PCF：用户策略管理；
AF：用户应用管理。
在图2所示架构中，N1接口为UE与AMF之间的参考点；N2接口为RAN和AMF的参考点，用于NAS消息的发送等；N3接口为RAN和UPF之间的参考点，用于传输用户面的数据等；N4接口为SMF和UPF之间的参考点，用于传输例如N3连接的隧道标识信息、数据缓存指示信息，以及下行数据通知消息等信息；N6接口为UPF和DN之间的参考点，用于传输用户面的数据等。下一代(Next Generation，NG)接口：无线接入网设备和5G核心网之间的接口。
需要说明的是，图1和图2中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请实施例对此不作具体限定。图1和图2中包括的各个网 元(比如SMF、AF、UPF等)的名称也仅是一个示例，对网元本身的功能不构成限定。在5G以及未来其它的网络中，上述各个网元也可以是其他的名称，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称，等等，在此进行统一说明，以下不再赘述。此外，应理解，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。上述各个网元实体可以实现成为计算机设备，或运行在计算机设备中的虚拟计算机设备。
在本申请实施例中，为非GBR QoS流定义了快速变化的QoS通知控制(Quick Change QoS Notification Control，QCQNC)机制。QCQNC机制是QNC的一种，可简称为QNC。在本申请实施例提供的QCQNC机制中，接入网设备在检测到非GBR QoS流的至少一个QoS参数发生快速变化时，向SMF发送快速变化通知。SMF向PCF、AF以及UE发送快速变化通知。AF和UE在接收到快速变化通知后，对自身内部的应用程序进行调整，使得应用程序来适应该变化，以防止卡顿等影响业务体验QoE(Quality of Experience)的现象出现。
QoS流是PUD会话中最小的QoS区分粒度。5G系统中使用QoS流ID(QFI)来区分QoS流。QoS流被SMF控制，QoS流可以预配置或者在PDU会话建立流程中建立，或者在PDU会话修改流程中修改。
在本申请实施例中，为非GBR QoS流定义了如下的QoS特性：
·5G QoS标识(5G QoS Identifier，5QI)、分配和维持优先级(Allocation and Retention Priority，ARP)、反射QoS特性(Reflective QoS Attribute，RQA)。
·且对应于非GBR QoS流的5QI，只定义了如下的QoS特性：
·资源类型(Resource Type)；
分为：GBR、时延关键GBR或非GBR。
·优先级(Priority Level)；
·分组数据时延(Packet Delay Budget，PDB)；
分组数据时延(预算)，包含核心网的分组时延。
·分组误码率(Packet Error Rate，PER)；
在这4个QoS特性中，前面的两个参数Resource Type，Priority Level是定义5QI的特性，而后面的两个参数PDB和PER则是定义5QI的性能。
在本申请实施例中，提出QoS QNC的Profile(特性)是有关NGBF(Non GBR QoS Flow)的三个参数PDB，PER及当前传输速率(Current Bit Rate，CBR)。当RAN检测到这三个参数中的任何一个参数值增加或减少一个变化率(或，增加或减少一个变化值)超过了一个指定门限(由于不同的参数的性质不一样，对于每个参数，其对应的变化率或变化值都是不同的)，则向SMF发送通知消息，并且通知所有参数变化的变化率或变化值。SMF向PCF发送通知消息，PCF向AF发送通知消息，AF对应的应用程序则作相应的调整。同时SMF通过NAS消息向UE发送通知消息，UE对应的应用程序也可以有作相应的调整，从而实现了网络与应用的交互，实现了业务传输的优化，解决网络出现拥塞时的卡顿，或当网络条件变好之后，应用程序仍然使用非常低的传输速率，不能充分利用网络资源，却不能提升用户的体验。
在一个实施例中，参数变化的定义有两种：
1、变化值；
在参数值从A变化到B时，定义B-A为变化值。需要注意的是，假设参数值从A变化到B时的变化值为第一变化值，从B变回到A时的变化值为第二变化值，则第一变化值和 第二变化值的幅值相同(不考虑正负)。
2、变化率。
在一种可能的设计中，在参数值从A变化到B时，定义(B-A)/A为变化值。需要注意的是，假设参数值从A变化到B时的变化率为第一变化率(B-A)/A，从B变回到A时的变化率为第二变化率(A-B)/B，则第一变化率和第二变化率的幅值相同(不考虑正负)。
即(B-A)/A不等于(A-B)/B的幅值(假设B>A>0)。因此在上述定义中，参数值A上升30％到参数值B后，然后参数值B下降30％之后，并不是恢复到参数值A。
在另一种可能的设计中，为了让同一参数值在先上升30％再下降30％后，是表示恢复到同一参数值，则将变化率统一定义为参数值变化前后的(较大值–较小值)/较小值，或变化率统一定义为参数值变化前后的(较大值–较小值)/较大值，或变化率统一定义为参数值变化前后的(较大值–较小值)/一固定值。其中，较大值是变化前后的参数值中绝对值较大的一个，较小值是变化前后的参数值中绝对值较小的一个，一固定值是事先确定的一个数值不变的值。这样，参数值A先上升30％，再下降30％时，则恢复到原参数值A了。
在一个实施例中，提供了如下通信协议：
QoS配置
一个QoS流是GBR或非GBR受其QoS配置决定。QoS流的QoS配置被发送至(R)AN，包含以下QoS参数(QoS参数的详细信息在通信协议TS23.501的5.7.2小节定义)。
-每一个QoS流，QoS配置要包含的QoS参数；
-5QI；和，
-ARP；
-仅对每个非GBR的QoS流，QoS配置可以还包含的QoS参数：
-QCQNC；
-RQA；
-仅对每个GBR的QoS流，QoS配置可以还包含的QoS参数：
-保证的流比特率(Guaranteed Flow Bit Rate，GFBR)-上行和下行，和，
-最大流比特率(Maximum Flow Bit Rate，MFBR)-上行和下行；和，
-仅对GBR QoS流，QoS配置可以还包含一个或者更多的QoS参数；
-通知控制；
-最大丢包率-上行和下行。
在一个实施例中，提供了QoS快速变化通知控制配置(QoS Quick Change Notification control Profile)。
QoS快速变化通知控制配置是为启用快速变化通知控制的非GBR QoS流提供的。如果相应的PCC规则包含相关信息(如通信协议TS 23.503中所述)，则SMF除QoS配置文件外，还应向NG-RAN提供快速变化通知控制配置。如果SMF向NG-RAN提供了快速变化通知控制配置(如果相应的策略控制和计费(Policy and Charging Control Rule，PCC)规则信息发生了变化)，则NG-RAN将用它替换之前存储的配置。
快速变化通知控制配置表示任何QoS参数PDB，PER和检测到的CBR(当前比特率)的快速变化，这将有助于应用程序根据变化后的QoS参数来控制应用程序流量。快速变化通知控制配置表示(PDR，PER，CBR)在短时间内的(20％，10％，30％)快速变化(增加或减少)，并且变化后的新值能够持续保持，即这种快速变化不是由于突发冲击干扰等原因所造成了短而快的刺峰。
注意：快速变化通知控制配置可以是PDB，PER，CBR的任何变化组合，例如，快速变化通知控制配置可以将增加(或减少)的PDR设置为20％；也可以是增加(或减少)的 PDR和PER设置为20％，增加(或减少)的CBR为10％；或者增加(或减少)的CBR为30％。
当NG-RAN向SMF发送满足QCQNC配置的快速变化通知时，NG-RAN还应通知消息中包括当前的QoS参数(PDB，PER)和CBR。
非GBR承载流的QNC机制至少包括如下几个过程：
1.QNC的通知过程(针对AF)；
2.QNC的配置过程；
3.QNC的优化过程。
下面分别介绍上述过程。
1.QNC的通知过程(针对AF)：
图3是本申请一个示例性实施例提供的QoS变化的通知方法的流程图。本实施例以该方法应用于图1或图2所示的移动通信系统中来举例说明。该方法包括：
步骤320：接入网设备在非GBR承载流的QNC的参数的变化满足上报条件时，通过核心网实体向应用实体发送通知消息；
非GBR承载流是指非GBR类型的承载流。非GBR承载流包括：非GBR QoS流，或，非GBR EPS承载。示例性的，在5G系统中，非GBR承载流是非GBR类型的QoS流；在4G系统中，非GBR承载流是非GBR类型的EPS承载。
示例性的，QNC(或称QCQNC)的参数包括如下至少一种：PDB、PER、CBR。在QNC的参数包括至少两种的情况下，存在至少两种参数对应的上报条件相同；和/或，存在至少两种参数对应的上报条件不同。
示例性的，上报条件(或称变化门限、变化上报门限)包括如下至少一种：
·QNC的参数在第一时长内的变化值大于第一阈值；
第一阈值是大于0且小于1的小数。比如，该第一阈值是20％、30％和40％。第一时长是用于计算变化值的周期或时长，比如1秒、2秒。
·QNC的参数在第二时长内的变化率大于第二阈值；
第二阈值是大于0且小于1的小数。比如，该第二阈值是20％、30％和40％。第二时长是用于计算变化率的周期或时长，比如1秒、2秒。
·QNC的参数在第一时长内的变化值大于第一阈值，且持续保持第三阈值；
第三阈值是用于衡量变化值的保持时长的阈值，比如2秒。
·QNC的参数在第二时长内的变化率大于第二阈值，且持续保持第四阈值。
第四阈值是用于衡量变化率的保持时长的阈值，比如2秒。
示例性的，通知消息内还携带有：变化后的QNC的参数值。也即在QNC的参数发生快速变化后，QNC的参数的当前参数值。该“当前”是相对概念，并不是绝对意义上的当前。比如，当前参数值是在触发上报条件时的参数值，并不一定等于发送通知消息后的实时参数值。
示例性的，变化后的QNC的参数值可以使用变化后的QNC的参数值的量化值来表示。比如，将QNC的取值范围划分为16个不重叠的子区间。16个子区间中的每个子区间对应有唯一的量化值，该量化值采用四个比特来表示。当变化后的QNC的参数值属于第i个子区间的情况下，使用第i个子区间对应的量化值来表示，该量化值仅需4个比特即可，能够降低通知消息所需要的传输资源。
步骤340：应用实体根据通知消息控制应用程序。
该通知消息(或称快速变化通知、快速变化报告、通知报告)用于指示非GBR承载流的QoS通知控制QNC的参数的变化满足上报条件。
应用实体根据通知消息控制应用程序的运行参数、运行策略和流量中的至少一种，以使得应用程序适应非GBR承载流的相关参数的快速变化。
应用实体上运行有一个或多个应用程序，同一个应用程序对应至少一个业务数据流(Service Data Flow，SDF)。具有不同QoS需求的SDF会分别映射至独立的QoS流，比如具有第一QoS需求的SDF会映射至第一QoS流，具有第二QoS需求的SDF会映射至第二QoS流。可选地，具有相同QoS需求的SDF可以映射至相同的QoS流。
在本申请实施例中，假设一个应用程序对应的一个或多个QoS流中包括有非GBR QoS流，该非GBR QoS流用于传输语音、视频、文本、消息、文件、控制信息等业务中的至少一种业务的数据包。
综上所述，本实施例提供的方法，通过在非GBR承载流的QNC的参数的增加/减少满足上报条件时，通过核心网实体向应用实体发送通知消息，应用实体在接收到通知消息后，根据通知消息控制应用程序，从而针对非GBR承载流提供了QNC机制，使得应用实体能够获知非GBR承载流的无线网络状态的变化，进而主动地控制应用程序的运行来适应该变化。比如控制应用程序的计算策略和流量策略，使得在QNC的参数变差的情况下，或者，由差恢复为好的情况下，应用实体能够调整应用程序来适应该参数变化下的网络传输。
上述接入网设备执行的步骤，可以单独实现成为接入网设备侧的一个实施例；上述应用实体执行的步骤，可以单独实现成为应用实体侧的一个实施例，本申请不再赘述。
图4是本申请另一个示例性实施例提供的QoS变化的通知方法的流程图。本实施例以该方法应用于图1或图2所示的移动通信系统中来举例说明。该方法包括：
步骤322：接入网设备在非GBR承载流的QNC的参数的变化满足上报条件时，向核心网实体发送通知消息；
核心网实体接收接入网设备发送的通知消息。该通知消息用于指示非GBR承载流的QoS通知控制QNC的参数的变化满足上报条件。
示例性的，通知消息内还携带有：变化后的QNC的参数值。也即在QNC的参数发生快速变化后，QNC的参数的当前参数值。该“当前”是相对概念，并不是绝对意义上的当前。比如，当前参数值是在触发上报条件时的参数值，并不一定等于发送通知消息后的实时参数值。
示例性的，变化后的QNC的参数值可以使用变化后的QNC的参数值的量化值来表示。比如，将QNC的取值范围划分为16个不重叠的子区间。16个子区间中的每个子区间对应有唯一的量化值，该量化值采用四个比特来表示。当变化后的QNC的参数值属于第i个子区间的情况下，使用第i个子区间对应的量化值来表示，该量化值仅需4个比特即可，能够降低通知消息所需要的传输资源。
步骤324：核心网实体向应用实体发送通知消息；
核心网实体为一个或多个。在通知消息涉及位于RAN和AF之间的多个核心网实体时，多个核心网实体依次传输该通知消息，不同核心网实体可以采用不同类型的消息携带该通知消息。比如，核心网实体包括：移动性管理实体(Mobility Management Entity，MME)、服务网关(Serving GateWay，SGW)、PDN网关(PDN GateWay，PGW)和PCF，则通知消息的传输路径至少包括RAN→MME→SGW/PGW→PCF→AF；又比如，核心网实体包括：第一核心网实体AMF、第二核心网实体SMF和第三核心网实体PCF，则通知消息的传输路径至少包括RAN→AMF→SMF→PCF→AF。
示例性的，核心网实体向应用实体发送事件报告(Event Reporting)，该事件报告携带有通知消息。
步骤342：应用实体接收核心网实体发送的通知消息；
示例性的，应用实体接收核心网实体发送的事件报告。
步骤344：应用实体根据通知消息控制应用程序。
应用实体根据通知消息控制应用程序的计算策略和流量策略中的至少一种，以使得应用程序适应非GBR承载流的相关参数的快速变化，以尽量保证用户的QoE，避免出现卡顿等现象。
以在线会议的服务器侧的应用程序为例，该应用程序对应有4个SDF：语音SDF、视频SDF、文本消息SDF和控制面SDF。4个SDF对应4个非GBR QoS流，针对4个非GBR QoS流分别启用QNC机制。
第一种可能的实现方式：
响应于通知消息用于指示QNC的参数值变差，控制应用程序按照第一计算策略执行；
响应于通知消息用于指示QNC的参数值变优，控制应用程序按照第二计算策略执行；
其中，相同计算任务在第一计算策略下的计算时长小于在第二计算策略下的计算时长。
计算策略是与应用程序的运行计算有关的策略。计算策略包括但不限于：编解码方式的选择策略、编解码模型的选择策略、编解码等级的选择策略、压缩级别的选择策略、神经网络模型的选择策略中的至少一种。
以计算策略包括编解码方式的选择为例，响应于通知消息用于指示QNC的参数值变差，控制应用程序采用第一编解码方式进行编解码；响应于通知消息用于指示QNC的参数值变优，控制应用程序采用第二编解码方式进行编解码。此处的“编解码”是指编码和解码中的至少一种。
其中，相同编解码任务在第一编解码策略下的计算时长小于在第二编解码策略下的计算时长。
例如，在PDR变大时，虽然网络时延变大，但是应用程序通过减少内部的计算时长来弥补网络时延的恶化，仍然能够保证整体的传输时延不变或变化很小。比如，与视频对应的非GBR QoS流的PDR变差，则降低视频的编码码率，以减少视频数据包的数量和/或大小。
第二种可能的实现方式：
响应于通知消息用于指示QNC的参数值变差，控制应用程序按照第一流量策略执行；
响应于通知消息用于指示QNC的参数值变优，控制应用程序按照第二流量策略执行；
其中，所述第一流量策略的流量少于所述第二流量策略的流量。
示例性的，应用程序的流量包括语音数据包和视频数据包；
响应于通知消息用于指示QNC的参数值变差，保持语音数据包对应的第一流量，减少视频数据包对应的第二流量；响应于通知消息用于指示QNC的参数值变优，保持语音数据包对应的第一流量，增加视频数据包对应的第二流量。
例如，在PDR变大时，降低与视频对应的第一非GBR QoS流的流量，保持与语音对应的第二非GBR QoS流的流量，从而整体上占用更少的无线资源，以增加语音数据包的传输质量以及减少干扰。
这是由于在基于云的应用(视频会议，语音会议，远程教学)中，通常是需要视频和语音的双向交互。对网络传输时延有一定要求(通常要单向传输时延<150ms)，但在实际的使用过程中，由于无线网络状态的变化，在一段时间内(如一个5秒的时间内)，无线网络的传输时延突然变差，或传输的速率突然变小，造成音视频的卡顿。
而相关研究表明，用户对音频的卡顿非常敏感，而对于视频的质量变化(如分辨率的变化，清晰的变化)并不是太敏感(且在保留语音的情形下，暂时关闭一下视频都是可以接受的)。对于音频一般由于其传输数据较小，不大经常出现卡顿。但若音频出现卡顿，则用户的体验非常不好。另外，即便音频从CD的质量往下降低到非常低的传输率(如2G语音传输质量)，但只要不出现卡顿，用户仍然有非常好的使用体验。
综上所述，本实施例提供的方法，通过应用实体根据变化后的QNC的参数值来调整应 用程序，使得在非GBR承载流的相关参数变差的情况下，或者，非GBR承载流的相关参数由差恢复为好的情况下，应用实体能够调整自身内部的应用程序来适应该参数变化，从而达到对应用程序的运行进行优化。
本实施例提供的方法，还通过在非GBR承载流的相关参数变差的情况下，改变应用程序的计算策略，通过减少应用程序内部的计算时长来弥补网络时延的恶化，仍然能够保证整体的传输时延不变或变化很小。
本实施例提供的方法，还通过在非GBR承载流的相关参数变差的情况下，改变应用程序的流量策略，比如保持语音数据包的流量，减少视频数据包的流量，能够避免出现对用户体验影响较大的音频的卡顿，从而尽可能提升用户在使用音视频程序时的用户体验。
2.QNC的配置过程；
在非GBR承载流的建立过程或修改过程中，由核心网实体向接入网设备进行QNC的配置过程。也即，核心网实体向接入网设备发送QNC配置，QNC配置用于配置QNC的参数以及上报条件(或称变化门限、快速变化门限、变化上报门限、快速变化上报门限)。
图5是本申请一个示例性实施例提供的QNC的配置方法的流程图。本实施例以该方法应用于图1或图2所示的移动通信系统中来举例说明。该方法包括：
步骤420：第三核心网实体PCF向第二核心网实体SMF发送QNC的参数以及上报条件；
第三核心网实体是核心网中负责策略管理的实体。
第二核心网实体是核心网中负责会话管理的实体。
示例性的，在非GBR承载流的建立过程或修改过程中，第三核心网实体PCF向第二核心网实体SMF发送QNC的参数以及上报条件。
示例性的，在建立PDU会话的过程中，会建立(第)一个QoS流，这个QoS流称为基于默认QoS规则的QoS流(QoS Flow with Default QoS Rules)。一般而言，这个QoS流是非GBR类型的，第三核心网实体可以向第二核心网实体提供QNC的参数以及上报条件。
示例性的，该QNC的参数以及上报条件是第三核心网实体PCF自行确定的；或者，该QNC的参数以及上报条件是第三核心网实体PCF基于应用实体发送的业务流信息确定的；或者，该QNC的参数以及上报条件是第三核心网实体PCF基于UE的签约数据确定的。
步骤440：第二核心网实体SMF接收第三核心网实体PCF发送的PCC规则；
步骤460：第二核心网实体向接入网设备发送QNC配置(QNC Profile)，QNC配置用于向接入网设备配置QNC的参数以及上报条件。
综上所述，本实施例提供的方法，通过由第三核心网实体向第二核心网实体发送QNC的参数以及上报条件，能够触发第二核心网实体为非GBR承载流配置QNC的参数以及上报条件，完成QNC的配置过程。
在一种设计中，应用实体向第三核心网实体提供业务流信息，业务流信息中携带有应用实体需要(或建议)的QNC的参数以及上报条件，如图6所示。在另一种设计中，第三核心网实体基于QNC签约数据来确定QNC的参数以及上报条件，如图7所示。
图6是本申请另一个示例性实施例提供的QNC的配置方法的流程图。本实施例以该方法应用于图1或图2所示的移动通信系统中来举例说明。该方法包括：
步骤412：应用实体AF向第三核心网实体PCF发送QNC的控制参数；
QNC的控制参数包括：是否使能QNC、QNC的参数、变化门限中的至少一种。
应用实体AF向核心网实体发送策略授权创建/更新消息，策略授权创建/更新消息携带有QNC的控制参数。对应的，第三核心网实体PCF接收应用实体AF发送的策略授权创建/更新消息。
步骤420：第三核心网实体PCF向第二核心网实体SMF发送PCC规则，PCC规则携带有QNC的控制参数；
步骤440：第二核心网实体SMF接收第三核心网实体PCF发送的PCC规则；
步骤460：第二核心网实体向接入网设备发送QNC配置，QNC配置用于向接入网设备配置QNC的控制参数。
综上所述，本实施例提供的方法，通过由应用实体向第三核心网实体提供QNC的控制参数，能够实现应用实体与核心网实体的主动交互，由应用实体来驱动无线接入网设备络(如5G，4G的RAN)报告非GBR承载流的快速变化，从而由无线接入网设备络向应用实体开放了其网络能力，为互联网应用的创新提供了新的途径。
图7是本申请另一个示例性实施例提供的QNC的配置方法的流程图。本实施例以该方法应用于图1或图2所示的移动通信系统中来举例说明。该方法包括：
步骤414：第四核心网实体UDM向第三核心网实体PCF发送QNC签约数据，QNC签约数据携带有QNC的控制参数；
若默认5QI是NGBR类型，则为非GBR承载流增加QNC签约数据。第四核心网实体UDM将QNC签约数据发送给第二核心网实体SMF，第二核心网实体SMF将QNC签约数据发送给第三核心网实体PCF。
步骤420：第三核心网实体PCF向第二核心网实体SMF发送默认QoS规则，默认QoS规则携带有QNC的控制参数；
步骤440：第二核心网实体SMF接收第三核心网实体PCF发送的默认PCC规则；
步骤460：第二核心网实体向接入网设备发送QNC配置，QNC配置用于向接入网设备配置QNC的控制参数。
综上所述，本实施例提供的方法，通过第三核心网实体基于UE的签约数据来确定QNC的控制参数，使得在无AF提供QNC的控制参数的情况下，也能够实现基于UE的签约数据驱动无线接入网设备络向UE报告非GBR承载流的快速变化。
3.QNC的优化过程：
当第三核心网实体PCF或应用实体AF发现QNC的通知消息过于频繁，对系统造成较大的信令量。此时，第三核心网实体PCF或应用实体AF应当修改QNC的上报条件，比如增大变化门限。
图8是本申请一个示例性实施例提供的QNC的优化方法的流程图。本实施例以该方法应用于图1或图2所示的移动通信系统中来举例说明。该方法包括：
步骤520：第三核心网实体PCF在通知消息的上报频率大于或小于频率阈值时，向第二核心网实体SMF发送更新后的QNC的控制参数；
更新后的QNC的控制参数包括：是否使能QNC、更新后的QNC的参数、更新后的变化门限中的至少一种。也即，更新后的QNC的控制参数，可以对使能QNC、QNC的参数、变化门限三者中的至少一种进行更新。
比如，第三核心网实体PCF在通知消息的上报频率大于频率阈值时，向第二核心网实体SMF发送去使能QNC的指示；又比如，第三核心网实体PCF在通知消息的上报频率大于频率阈值时，向第二核心网实体SMF发送减少后的QNC的参数；再比如，第三核心网实体PCF在通知消息的上报频率大于频率阈值时，向第二核心网实体SMF发送增大后的变化门限。
步骤540：第二核心网实体SMF向接入网设备发送QNC配置，QNC配置携带有更新后的QNC的控制参数。
综上所述，本实施例提供的方法，通过在通知消息的上报频率大于或小于频率阈值时，向第二核心网实体SMF以及接入网设备发送更新后的QNC的控制参数，可以避免对系统造成较大的信令开销，或者，合理利用QNC的通知机制。
图9是本申请另一个示例性实施例提供的QNC的优化方法的流程图。本实施例以该方法应用于图1或图2所示的移动通信系统中来举例说明。该方法包括：
步骤510：应用实体在通知消息的上报频率大于或小于频率阈值时，向第三核心网实体PCF发送更新后的QNC的控制参数；
更新后的QNC的控制参数包括：是否使能QNC、更新后的QNC的参数、更新后的变化门限中的至少一种。也即，更新后的QNC的控制参数，可以对使能QNC、QNC的参数、变化门限三者中的至少一种进行更新。
比如，AF在通知消息的上报频率大于频率阈值时，向第三核心网实体PCF发送去使能QNC的指示；又比如，AF在通知消息的上报频率大于频率阈值时，向第三核心网实体PCF发送减少后的QNC的参数；再比如，AF在通知消息的上报频率大于频率阈值时，向第三核心网实体PCF发送增大后的变化门限。
步骤520：第三核心网实体PCF向第二核心网实体SMF发送更新后的QNC的控制参数；
步骤540：第二核心网实体SMF向接入网设备发送QNC配置，QNC配置携带有更新后的QNC的控制参数。
综上所述，本实施例提供的方法，通过在通知消息的上报频率大于或小于频率阈值时，由AF触发PCF向第二核心网实体SMF以及接入网设备发送更新后的QNC的控制参数，可以避免对系统造成较大的信令开销，或者，合理利用QNC的通知机制。
下面结合第三代合作伙伴项目(Third Generation Partnership Project，3GPP)的通信协议(TS23.502)对上述过程进行更详细的阐述。下述附图中网元名称、步骤流程和步骤介绍的详细内容，均可参考TS23.502(https://www.3gpp.org/ftp/Specs/archive/23_series/23.502)中的相关记载，本文受限于篇幅，着重介绍本申请实施例与TS23.502协议中不同的内容。
1.QNC的通知过程：
当UE所在的网络发生了变化，即基站检测到无线资源发生快速变化(变好或变差)。当这个变化达到QNC所定义的变化门限时，RAN会触发QNC的通知过程，向AF发送通知消息。可选地，该通知消息携带有变化后的QNC的参数的参数值(当前参数值)。基站先将通知消息发送给SMF，然后SMF再将通知消息发送至PCF，PCF再将通知消息发送至AF。
非漫游和本地疏导漫游场景：
图10示出了本申请的一个示例性实施例提供的UE或网络请求的PDU会话修改(用于非漫游和本地疏导漫游)流程的示意图。
在步骤1e中，RAN向AMF发送N2消息(PDU会话ID，SM信息)，AMF向SMF发送Namf_PDUSession_UpdateSMContext消息。
在非GBR承载流的QNC的参数满足上报条件时，这2个消息中携带有通知消息。可选地，通知消息还携带有变换后的QNC的参数值。
在步骤2中，SMF发起会话管理(Session Management，SM)策略关联修改流程，将通知消息发送至PCF以及AF。
在步骤5中，SMF向UE发送PDU会话修改命令，将变化后的QNC的参数值发送给UE。
示例性的，在SM收到通知消息的一段时间后，当SMF没有收到PCF新的PCC规则或收到的PCC规则，对于QNC对应的SDF的PCC规则没有对QoS方面有修改，则SMF向 UE发起PDU会话修改命令，通知UE当前QNC对应的QFI的QNC的当前参数值(PDB，PER，CBR)。
在步骤9中，UE回应PDU会话修改确认。
其中，PDU会话修改命令与PDU会话修改确认是通过RAN在UE和SMF之间进行透明地传输。
上述步骤2所示出的SM策略关联修改流程由图11定义。如图11所示：
在步骤1中，SMF向PCF发送Npcf_SMPolicyControl_Update请求，该请求中携带有通知消息。
在步骤2中，PCF向AF发送事件报告Npcf_PolicyAuthorizationNotify，该事件报告中携带有通知消息。
2.QNC的配置过程：
2.1非漫游和本地疏导漫游的PDU会话建立场景：
图12示出了本申请一个示例性实施例提供的UE请求的PDU会话建立流程的示意图。
在步骤7b和9中，SMF向PCF发送SM策略关联建立请求新消息，PCF向SMF发送SM策略关联建立响应消息，该消息中携带有QNC的控制参数；或者，SMF向PCF发送SM策略关联修改请求消息，PCF向SMF发送SM策略关联修改响应消息，该消息中携带有QNC的控制参数。
在建立PDU会话的过程中，会建立一个QoS流(通常是第一个)，这个QoS流称为基于默认QoS规则的QoS流(不再类似于4G的默认承载，5G不再使用默认QoS流来命名)。
一般而言，这个基于默认QoS规则是非GBR类型的，则PCF可以在PCC规则中包含QNC的控制参数。则可以在图12的步骤7b或9中，PCF提供Default QoS Rule中的5QI若是NGBR类型的，PCF可以向SMF提供QCQNC的控制参数。
在步骤11和12中，SMF向AMF发送Namf_Communication_N1N2信息转换消息，根据PCF提供的QCQNC的控制参数在该消息中携带有QNC配置。
可选地，UE的签约数据中包含有默认5QI与默认ARP。若默认5QI是NGBR类型的，则增加QNC签约数据。
在步骤4，7b和9中，UDM将包含QNC签约数据的消息提供给SMF，然后SMF将QNC签约数据提供给PCF，然后，PCF提供的默认QoS规则中包含QNC的控制参数。
PDU会话建立过程可用于N3GPP向3GPP的PDU会话切换。若在步骤7b,或9中，PCF为任一非GBR QoS流提供了QNC的控制参数，则类似于前面，在步骤11和12中增加QNC的控制参数。
需要注意的是，此处可能有多个非GBR QoS流的处理。
需要注意的是，步骤12的N2消息中的SM相关的参数是包含在步骤11中，因此在步骤11中包含有QNC的控制参数。
2.2归属路由漫游场景：
图13示出了本申请一个示例性实施例提供的用于归属路由漫游场景的UE请求的PDU会话建立流程的流程图。
在建立PDU会话的过程中，会建立一个QoS流(通常是第一个)，这个QoS流称为基于默认QoS规则的QoS流(不再类似于4G的默认承载，5G不再使用默认QoS流来命名)。
一般而言，这个基于默认QoS规则是非GBR类型的，则PCF可以在PCC规则中包含QNC的控制参数。则可以在图13的步骤9b或11的消息中，PCF提供默认QoS规则中的5QI若是非GBR类型的，PCF可以提供QNC的控制参数。然后，在步骤13、14和15中的消息，增加QNC配置。
可选地，UE的签约数据中包含有默认5QI与默认ARP。若默认5QI是NGBR类型的，则增加QNC签约数据。
在步骤7，9b，11中UDM将包含QNC签约数据提供给SMF，SMF将QNC签约数据提供给PCF，然后，PCF提供的默认QoS规则中包含QNC的控制参数。
2.3 AF触发的QoS流建立流程，非漫游和本地疏导漫游场景：
图14示出了本申请一个示例性实施例提供的针对单个UE地址的AF请求转移到相关PCF流程的示意图。图15示出了本申请一个示例性实施例提供的用于非漫游和本地疏导漫游的UE或网络请求的PDU会话修改流程的示意图。
在图14的步骤4，AF向PCF发送Npcf_PolicyAuthorization_Create/Update消息，该消息包含的(一个或多个)媒体组件(Media Component)信息中增加QNC的控制参数。前面所说，若这个媒体组件中包含了QNC的控制参数，则是请求这个媒体在NGBF上传输的；若这个媒体组件中不包含QCQNC参数，则表明这个媒体是可以在NGBF上传输，也可以是在GBF(GBR QoS Flow,GBR服务质量数据流)上传输。
在图15的步骤1b中，PCF发送Npcf_SMPolicyControlUpdateNotify请求消息。在请求消息中，对(一个或多个)SDF(Service Data Flow，业务数据流，一个SDF对应于AF提供的一个媒体流)的PCC规则增加QNC的控制关参数。
相应的，在图15的步骤3b和4的消息中携带包括QNC的控制参数。
2.4 AF触发的QoS流建立流程，归属路由漫游场景：
图16示出了本申请一个示例性实施例提供的用于归属路由漫游的UE或网络请求的PDU会话修改流程的示意图。
在图16的步骤1b，步骤3,步骤4b,和步骤5是增加一个或多个QNC的控制参数(即每个可能的业务流，SDF，QoS Flow)。
在图16的步骤3是相对于图15所述场景的新增步骤，即在一个或多个QoS流的QoS参数上增加QNC的控制参数。
本申请提出的技术也可以应用于4G系统。在应用至4G系统时，NR-gNB用eNB代替。PCF与AF的交互，不作任何的改变。SMF与PCF的交互，修改为PGW与PCF的交互。5G的QoS Flow被4G的EPS Bearer代替。5G的5QI被4G QCI代替。5G中RAN与AMF/SMF的交互,被4G的RAN与MME交互代替。
图17示出了本申请一个示例性实施例提供的应用程序的控制装置的框图。所述装置包括：
接收模块1720，用于应用实体接收核心网实体发送的通知消息，所述通知消息用于表示非GBR承载流的QNC的参数值的变化满足上报条件；
控制模块1740，用于根据所述通知消息控制所述应用程序。
在本申请实施例的一个可能设计中，所述控制模块1740，用于根据所述通知消息控制所述应用程序的计算策略；和/或；所述控制模块1740，用于根据所述通知消息控制所述应用程序的流量策略。
在本申请实施例的一个可能设计中，所述控制模块1740，用于响应于所述通知消息用于指示所述QNC的参数值变差，控制所述应用程序按照第一计算策略执行；响应于所述通知消息用于指示所述QNC的参数值变优，控制所述应用程序按照第二计算策略执行；
其中，相同计算任务在所述第一计算策略下的计算时长小于在所述第二计算策略下的计算时长。
在本申请实施例的一个可能设计中，所述控制模块1740，用于响应于所述通知消息用于指示所述QNC的参数值变差，控制所述应用程序采用第一编解码方式进行编解码；响应于所述通知消息用于指示所述QNC的参数值变优，控制所述应用程序采用第二编解码方式 进行编解码；
其中，相同编解码任务在所述第一编解码策略下的计算时长小于在所述第二编解码策略下的计算时长。
在本申请实施例的一个可能设计中，所述控制模块1740，用于响应于所述通知消息用于指示所述QNC的参数值变差，控制所述应用程序按照第一流量策略执行；响应于所述通知消息用于指示所述QNC的参数值变优，控制所述应用程序按照第二流量策略执行；
其中，所述第一流量策略的流量少于所述第二流量策略的流量。
在本申请实施例的一个可能设计中，所述应用程序的流量包括语音数据包和视频数据包；
所述控制模块1740，用于响应于所述通知消息用于指示所述QNC的参数值变差，保持所述语音数据包对应的第一流量，减少所述视频数据包对应的第二流量；响应于所述通知消息用于指示所述QNC的参数值变优，保持所述语音数据包对应的第一流量，增加所述视频数据包对应的第二流量。
在本申请实施例的一个可能设计中，所述通知消息是接入网设备实体在检测到所述非GBR承载流的QNC的参数的变化满足所述上报条件时，发送给所述核心网实体的。
在本申请实施例的一个可能设计中，所述通知消息包括：
变化后的所述QNC的参数值；或，变化后的所述QNC的参数值的量化值。
在本申请实施例的一个可能设计中，所述装置还包括：
发送模块1760，用于向所述核心网实体发送所述QNC的控制参数，所述QNC的控制参数用于指示所述QNC的参数以及所述上报条件。
在本申请实施例的一个可能设计中，所述发送模块1760，用于向所述核心网实体发送策略授权创建/更新消息，所述策略授权创建/更新消息携带有所述QNC的控制参数。
在本申请实施例的一个可能设计中，所述方法还包括：
所述应用实体在所述通知消息的上报频率大于或小于频率阈值时，向所述核心网实体发送所述变化后的QNC的控制参数。
在本申请实施例的一个可能设计中，所述QNC的参数值包括如下至少一种：
PDR；PER；CBR。
在本申请实施例的一个可能设计中，所述QNC的参数值包括至少两种；
存在至少两种所述参数值对应的所述上报条件相同；和/或，存在至少两种所述参数值对应的所述上报条件不同。
在本申请实施例的一个可能设计中，所述上报条件包括如下至少一种：
所述QNC的参数值在第一时长内的变化值大于第一阈值；
所述QNC的参数值在第二时长内的变化率大于第二阈值；
所述QNC的参数值在所述第一时长内的变化值大于第一阈值，且持续保持第三阈值；
所述QNC的参数值在所述第二时长内的变化率大于第二阈值，且持续保持第四阈值；
其中，所述第三阈值和所述第四阈值是用于衡量保持时长的阈值。所述第三阈值是用于衡量所述变化值的保持时长的阈值，所述第四阈值是用于衡量所述变化率的保持时长的阈值。
在本申请实施例的一个可能设计中，所述非GBR承载流包括：
非GBR的服务质量QoS流；或，非GBR的演进的分组系统EPS承载。
在本申请实施例的一个可能设计中，所述QNC定义在上行链路；或，所述QNC定义在下行链路；或，所述QNC定义在所述上行链路和所述下行链路。
在本申请实施例的一个可能设计中，所述非GBR承载流与目标业务流存在一一对应关系，所述目标业务流是使能所述QNC以及包括所述QNC的参数值的业务流。
图18示出了本申请一个示例性实施例提供的应用程序的控制装置的框图。所述装置包 括：
接收模块1820，用于核心网实体接收接入网设备发送的通知消息，所述通知消息用于表示非保证比特速率GBR流的服务质量通知控制QNC的参数的变化满足上报条件；
发送模块1840，用于向应用实体发送所述通知消息，以便所述应用实体根据所述通知消息控制应用程序的流量。
在本申请实施例的一个可能设计中，所述发送模块1840，用于所述核心网实体向所述应用实体发送事件报告，所述事件报告携带有所述通知消息。
在本申请实施例的一个可能设计中，所述通知消息包括：
变化后的所述QNC的参数值；或，变化后的所述QNC的参数值的量化值。
在本申请实施例的一个可能设计中，所述发送模块1840，用于根据所述QNC的控制参数，向所述接入网设备发送QNC配置；
其中，所述QNC的控制参数用于指示所述QNC的参数以及所述上报条件。
在本申请实施例的一个可能设计中，所述接收模块1820，用于接收所述应用实体发送的策略授权创建/更新消息，所述策略授权创建/更新消息携带有所述QNC的控制参数。
在本申请实施例的一个可能设计中，所述接收模块1820，用于获取所述QNC的签约数据，所述QNC的签约数据携带有所述QNC的控制参数。
图19示出了本申请一个实施例提供的网元设备1900的结构示意图，例如，该网元设备可以用于执行上述应用程序的控制方法。可选地，该网元设备1900是应用实体或核心网实体。具体来讲：该网元设备1900可以包括：处理器1901、接收器1902、发射器1903、存储器1904和总线1905。
处理器1901包括一个或者一个以上处理核心，处理器1901通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
接收器1902和发射器1903可以实现为一个收发器1906，该收发器1906可以是一块通信芯片。
存储器1904通过总线1905与处理器1901相连。
存储器1904可用于存储计算机程序，处理器1901用于执行该计算机程序，以实现上述方法实施例中的应用实体、核心网网元或核心网实体执行的各个步骤。
此外，存储器1904可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：RAM(Random-Access Memory，随机存储器)和ROM(Read-Only Memory，只读存储器)、EPROM(Erasable Programmable Read-Only Memory，可擦写可编程只读存储器)、EEPROM(Electrically Erasable Programmable Read-Only Memory，电可擦写可编程只读存储器)、闪存或其他固态存储其技术，CD-ROM(Compact Disc Read-Only Memory，只读光盘)、DVD(Digital Video Disc，高密度数字视频光盘)或其他光学存储、磁带盒、磁带、磁盘存储或其他磁性存储设备。
本申请还提供一种计算机可读存储介质，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现上述方法实施例提供的应用程序的控制方法。
可选地，本申请还提供了一种计算机程序产品，所述计算机程序产品包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行上述方面提供的应用程序的控制方法。

Claims (34)

  1. 一种应用程序的控制方法，其特征在于，所述方法包括：
    应用实体接收核心网实体发送的通知消息，所述通知消息用于表示非保证比特速率GBR承载流的服务质量通知控制QNC的参数值的变化满足上报条件；
    所述应用实体根据所述通知消息控制所述应用程序。
  2. 根据权利要求1所述的方法，其特征在于，所述应用实体根据所述通知消息控制应用程序，包括：
    所述应用实体根据所述通知消息控制所述应用程序的计算策略；
    和/或；
    所述应用实体根据所述通知消息控制所述应用程序的流量策略。
  3. 根据权利要求2所述的方法，其特征在于，所述应用实体根据所述通知消息控制所述应用程序的计算策略，包括：
    响应于所述通知消息用于指示所述QNC的参数值变差，控制所述应用程序按照第一计算策略执行；
    响应于所述通知消息用于指示所述QNC的参数值变优，控制所述应用程序按照第二计算策略执行；
    其中，相同计算任务在所述第一计算策略下的计算时长小于在所述第二计算策略下的计算时长。
  4. 根据权利要求3所述的方法，其特征在于，所述响应于所述通知消息用于指示所述QNC的参数值变差，控制所述应用程序按照第一计算策略执行，包括：
    响应于所述通知消息用于指示所述QNC的参数值变差，控制所述应用程序采用第一编解码方式进行编解码；
    所述响应于所述通知消息用于指示所述QNC的参数值变优，控制所述应用程序按照第二计算策略执行，包括：
    响应于所述通知消息用于指示所述QNC的参数值变优，控制所述应用程序采用第二编解码方式进行编解码；
    其中，相同编解码任务在所述第一编解码策略下的计算时长小于在所述第二编解码策略下的计算时长。
  5. 根据权利要求2所述的方法，其特征在于，所述应用实体根据所述通知消息控制应用程序的流量策略，包括：
    响应于所述通知消息用于指示所述QNC的参数值变差，控制所述应用程序按照第一流量策略执行；
    响应于所述通知消息用于指示所述QNC的参数值变优，控制所述应用程序按照第二流量策略执行；
    其中，所述第一流量策略的流量少于所述第二流量策略的流量。
  6. 根据权利要求5所述的方法，其特征在于，所述应用程序的流量包括语音数据包和视频数据包；
    所述响应于所述通知消息用于指示所述QNC的参数值变差，控制所述应用程序按照第一流量策略执行，包括：
    响应于所述通知消息用于指示所述QNC的参数值变差，保持所述语音数据包对应的第一流量，减少所述视频数据包对应的第二流量；
    所述响应于所述通知消息用于指示所述QNC的参数值变优，控制所述应用程序按照第二流量策略执行，包括：
    响应于所述通知消息用于指示所述QNC的参数值变优，保持所述语音数据包对应的第 一流量，增加所述视频数据包对应的第二流量。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述通知消息是接入网设备实体在检测到所述非GBR承载流的QNC的参数的变化满足所述上报条件时，发送给所述核心网实体的。
  8. 根据权利要求1至6任一所述的方法，其特征在于，所述通知消息包括：
    变化后的所述QNC的参数值；
    或，
    变化后的所述QNC的参数值的量化值。
  9. 根据权利要求1至6任一所述的方法，其特征在于，所述方法还包括：
    所述应用实体向所述核心网实体发送所述QNC的控制参数，所述QNC的控制参数用于指示所述QNC的参数以及所述上报条件。
  10. 根据权利要求9所述的方法，其特征在于，所述应用实体向所述核心网实体发送所述QNC的控制参数，包括：
    所述应用实体向所述核心网实体发送策略授权创建/更新消息，所述策略授权创建/更新消息携带有所述QNC的控制参数。
  11. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述应用实体在所述通知消息的上报频率大于或小于频率阈值时，向所述核心网实体发送所述变化后的QNC的控制参数。
  12. 根据权利要求1至6任一所述的方法，其特征在于，所述QNC的参数值包括如下至少一种：
    分组数据时延PDR；
    分组误码率PER；
    当前比特速率CBR。
  13. 根据权利要求12所述的方法，其特征在于，所述QNC的参数值包括至少两种；
    存在至少两种所述参数值对应的所述上报条件相同；
    和/或，
    存在至少两种所述参数值对应的所述上报条件不同。
  14. 根据权利要求1至6任一所述的方法，其特征在于，所述上报条件包括如下至少一种：
    所述QNC的参数值在第一时长内的变化值大于第一阈值；
    所述QNC的参数值在第二时长内的变化率大于第二阈值；
    所述QNC的参数值在所述第一时长内的变化值大于第一阈值，且持续保持第三阈值；
    所述QNC的参数值在所述第二时长内的变化率大于第二阈值，且持续保持第四阈值；
    其中，所述第三阈值和所述第四阈值是用于衡量保持时长的阈值。
  15. 根据权利要求1至6任一所述的方法，其特征在于，所述非GBR承载流包括：
    非GBR的服务质量QoS流；
    或，非GBR的演进的分组系统EPS承载。
  16. 根据权利要求1至6任一所述的方法，其特征在于，
    所述QNC定义在上行链路；
    或，所述QNC定义在下行链路；
    或，所述QNC定义在所述上行链路和所述下行链路。
  17. 根据权利要求1至6任一所述的方法，其特征在于，
    所述非GBR承载流与目标业务流存在一一对应关系，所述目标业务流是使能所述QNC以及包括所述QNC的参数值的业务流。
  18. 一种应用程序的控制方法，其特征在于，所述方法包括：
    核心网实体接收接入网设备发送的通知消息，所述通知消息用于表示非保证比特速率GBR流的服务质量通知控制QNC的参数的变化满足上报条件；
    所述核心网实体向应用实体发送所述通知消息，以便所述应用实体根据所述通知消息控制应用程序的流量。
  19. 根据权利要求18所述的方法，其特征在于，所述核心网实体向应用实体发送所述通知消息，包括：
    所述核心网实体向所述应用实体发送事件报告，所述事件报告携带有所述通知消息。
  20. 根据权利要求18所述的方法，其特征在于，所述通知消息包括：
    变化后的所述QNC的参数值；
    或，变化后的所述QNC的参数值的量化值。
  21. 根据权利要求18至20任一所述的方法，其特征在于，所述方法还包括：
    所述核心网实体根据所述QNC的控制参数，向所述接入网设备发送QNC配置；
    其中，所述QNC的控制参数用于指示所述QNC的参数以及所述上报条件。
  22. 根据权利要求21所述的方法，其特征在于，所述核心网实体包括：第二核心网实体和第三核心网实体；所述方法还包括：
    所述第三核心网实体向所述第二核心网实体发送策略与计费控制PCC规则，所述PCC规则携带有所述QNC的控制参数；
    所述核心网实体根据所述QNC的控制参数，向所述接入网设备发送QNC配置，包括：
    所述第二核心网实体向所述接入网设备发送QNC配置，所述QNC配置携带有所述QNC的控制参数。
  23. 根据权利要求22所述的方法，其特征在于，所述第三核心网实体向所述第二核心网实体发送PCC规则，包括：
    所述第三核心网实体向所述第二核心网实体发送会话策略关联建立或基于发起的策略关联修改消息，所述会话策略关联建立或基于发起的策略关联修改消息携带有所述PCC规则。
  24. 根据权利要求22所述的方法，其特征在于，所述第二核心网实体向所述接入网设备发送QNC配置，包括：
    所述第二核心网实体通过第一核心网实体AMF向所述接入网设备发送NAS消息，所述NAS消息携带有所述QNC配置。
  25. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    所述核心网实体接收所述应用实体发送的所述QNC的控制参数。
  26. 根据权利要求25所述的方法，其特征在于，所述核心网实体包括：第二核心网实体和第三核心网实体；
    所述核心网实体接收所述应用实体发送的所述QNC的控制参数，包括：
    所述第三核心网实体接收所述应用实体发送的策略授权创建/更新消息，所述策略授权创建/更新消息携带有所述QNC的控制参数。
  27. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    所述核心网实体获取所述QNC的签约数据，所述QNC的签约数据携带有所述QNC的控制参数。
  28. 一种应用程序的控制装置，其特征在于，所述装置包括：
    接收模块，用于接收核心网实体发送的通知消息，所述通知消息用于表示非保证比特速率GBR承载流的服务质量通知控制QNC的参数值的变化满足上报条件；
    控制模块，用于根据所述通知消息控制所述应用程序。
  29. 一种应用程序的控制装置，其特征在于，所述装置包括：
    接收模块，用于接收接入网设备发送的通知消息，所述通知消息用于表示非保证比特速 率GBR流的服务质量通知控制QNC的参数的变化满足上报条件；
    发送模块，用于向应用实体发送所述通知消息，以便所述应用实体根据所述通知消息控制应用程序的流量。
  30. 一种网元设备，其特征在于，所述网元设备包括：处理器和存储器，所述存储器存储有计算机程序，所述计算机程序由所述处理器运行以使得所述网元设备以实现如权利要求1至17任一所述的应用程序的控制方法。
  31. 一种网元设备，其特征在于，所述网元设备包括：处理器和存储器，所述存储器存储有计算机程序，所述计算机程序由所述处理器运行以使得所述网元设备以实现如权利要求18至27任一所述的应用程序的控制方法。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，所述计算机程序由处理器加载并执行以实现如权利要求1至27任一所述的应用程序的控制方法。
  33. 一种芯片，其特征在于，所述芯片包括可编程逻辑电路，所述可编程逻辑电路在运行时用于实现如权利要求1至27任一所述的应用程序的控制方法。
  34. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机指令，所述计算机指令存储在计算机可读存储介质中，计算机设备的处理器从所述计算机可读存储介质读取所述计算机指令，所述处理器执行所述计算机指令，使得所述计算机设备执行如权利要求1至27任一所述的应用程序的控制方法。
PCT/CN2022/070546 2021-02-25 2022-01-06 应用程序的控制方法、装置、设备及存储介质 WO2022179317A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020237011660A KR20230062622A (ko) 2021-02-25 2022-01-06 애플리케이션 프로그램 제어 방법 및 장치, 디바이스 및 저장 매체
JP2023525508A JP2023547904A (ja) 2021-02-25 2022-01-06 アプリケーションプログラム制御方法および装置、デバイス、並びに記憶媒体
EP22758683.1A EP4199576A4 (en) 2021-02-25 2022-01-06 APPLICATION PROGRAM CONTROL METHOD AND APPARATUS, DEVICE AND STORAGE MEDIUM
US17/985,278 US20230070295A1 (en) 2021-02-25 2022-11-11 Application program control method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110215376.4 2021-02-25
CN202110215376.4A CN113038527A (zh) 2021-02-25 2021-02-25 应用程序的控制方法、装置、设备及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/985,278 Continuation US20230070295A1 (en) 2021-02-25 2022-11-11 Application program control method and apparatus

Publications (1)

Publication Number Publication Date
WO2022179317A1 true WO2022179317A1 (zh) 2022-09-01

Family

ID=76462222

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/070546 WO2022179317A1 (zh) 2021-02-25 2022-01-06 应用程序的控制方法、装置、设备及存储介质

Country Status (6)

Country Link
US (1) US20230070295A1 (zh)
EP (1) EP4199576A4 (zh)
JP (1) JP2023547904A (zh)
KR (1) KR20230062622A (zh)
CN (1) CN113038527A (zh)
WO (1) WO2022179317A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113037543B (zh) * 2021-02-25 2023-11-07 腾讯科技（深圳）有限公司 QoS变化的通知方法、装置、设备及介质
CN118042505A (zh) * 2021-07-21 2024-05-14 安科讯(福建)科技有限公司 一种5g通信基于专用qos流的qos流动态调整方法与系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102769873A (zh) * 2011-05-03 2012-11-07 中兴通讯股份有限公司 一种资源接纳控制方法及系统
CN110120878A (zh) * 2018-02-05 2019-08-13 华为技术有限公司 获取链路质量的方法和装置
US20190261211A1 (en) * 2017-05-09 2019-08-22 Huawei Technologies Co., Ltd. QOS Control Method and Device
CN110995773A (zh) * 2016-05-24 2020-04-10 华为技术有限公司 QoS控制方法及设备
WO2020074108A1 (en) * 2018-10-08 2020-04-16 Telefonaktiebolaget Lm Ericsson (Publ) Notification control in a communication system
US20200280889A1 (en) * 2017-11-20 2020-09-03 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Service configuration method and related product

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018084844A1 (en) * 2016-11-03 2018-05-11 Nokia Technologies Oy Quality of service management
US11678252B2 (en) * 2018-10-05 2023-06-13 Huawei Technologies Co., Ltd. Quality of service information notification to user equipment, users, and application server
CN111756555B (zh) * 2019-03-28 2022-04-05 华为技术有限公司 计费规则绑定的方法、设备及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102769873A (zh) * 2011-05-03 2012-11-07 中兴通讯股份有限公司 一种资源接纳控制方法及系统
CN110995773A (zh) * 2016-05-24 2020-04-10 华为技术有限公司 QoS控制方法及设备
US20190261211A1 (en) * 2017-05-09 2019-08-22 Huawei Technologies Co., Ltd. QOS Control Method and Device
US20200280889A1 (en) * 2017-11-20 2020-09-03 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Service configuration method and related product
CN110120878A (zh) * 2018-02-05 2019-08-13 华为技术有限公司 获取链路质量的方法和装置
WO2020074108A1 (en) * 2018-10-08 2020-04-16 Telefonaktiebolaget Lm Ericsson (Publ) Notification control in a communication system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "TS23.501: Clarification for the default QoS flow, notification control and 5QI", 3GPP DRAFT; S2-175610 TS23 501 CLARIFICATION FOR THE DEFAULT QOS FLOW NOTIFICATION CONTROL AND 5QI_V2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sophia Antipolis, France; 20170821 - 20170825, 15 August 2017 (2017-08-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051335085 *
See also references of EP4199576A4 *

Also Published As

Publication number Publication date
KR20230062622A (ko) 2023-05-09
JP2023547904A (ja) 2023-11-14
EP4199576A1 (en) 2023-06-21
EP4199576A4 (en) 2024-05-01
US20230070295A1 (en) 2023-03-09
CN113038527A (zh) 2021-06-25

Similar Documents

Publication Publication Date Title
WO2022179334A1 (zh) 应用程序的控制方法、装置、设备及存储介质
US10880221B2 (en) System and method for adapting an application source rate to a load condition
US7688724B2 (en) Call admission control for mobility-capable telecommunications terminals
US9549345B2 (en) Solution to improve RAN bandwidth efficiency during VoLTE call scenarios
US20140233390A1 (en) Method and system for congestion avoidance in mobile communication networks
WO2022179317A1 (zh) 应用程序的控制方法、装置、设备及存储介质
WO2019228214A1 (zh) 一种无线承载建立、业务流的监测方法及装置
US20180103389A1 (en) Service rate adjustment method and apparatus
WO2022179322A1 (zh) 基于切换过程的消息发送方法、装置、设备及介质
WO2014036704A1 (zh) 控制网络传输时延的方法、服务质量控制实体和通信设备
WO2023035894A1 (zh) 一种数据处理方法、设备、可读存储介质和程序产品
WO2022179316A1 (zh) QoS变化的通知方法、装置、设备及介质
US20190394763A1 (en) Method and apparatus for controlling downlink or uplink transmission
WO2019185800A1 (en) Dedicated bearer management
US9246817B1 (en) System and method of managing traffic flow in a communication network
WO2017177356A1 (zh) 数据传输的方法、基站和用户设备
WO2016197295A1 (zh) 多媒体业务的方法、处理装置及通信设备
US9042317B2 (en) Non-guaranteed bit rate bearer control in a mobile communication network
WO2023151042A1 (zh) 一种无线通信方法及装置、通信设备
WO2024109393A1 (zh) 服务质量参数调整方法、装置及存储介质
WO2024027383A1 (zh) 数据处理方法及装置
WO2021163855A1 (zh) 信息发送方法、接收方法、装置、设备及存储介质
WO2021163853A1 (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: 22758683

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022758683

Country of ref document: EP

Effective date: 20230313

ENP Entry into the national phase

Ref document number: 20237011660

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2023525508

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE