Method and device for controlling an application program, device and storage medium

Abstract

The present application discloses a method and apparatus for controlling an application program related to the field of communications, a device, and a storage medium. The method comprises the step (320) of an application entity receiving a notification message transmitted by a core entity—the notification message is used to indicate that a change in a parameter value of a Quality of Service Notification Control (QNC) of a non-guaranteed bit rate (GBR) bearer flow satisfies a reporting condition—; and the step (340) of the application entity controlling an application program according to the notification message. According to the present application, the application entity can detect a change in the wireless network state of a non-GBR bearer flow and more actively control the execution of the application program according to the change.

Description

Technology Field

[0001] This application claims priority to Chinese Patent Application No. 202110215376.4 ('Method and apparatus for controlling an application program, device and storage medium'), filed on February 25, 2021, the entirety of which is incorporated herein by reference.

[0002] The embodiments of the present application relate to the field of mobile communication, specifically to an application program control method and apparatus, device and medium. Background Technology

[0003] In 5th-generation (5G) mobile communication technology, QoS control is performed at the QoS flow level.

[0004] Depending on the bearer type, QoS flows are divided into two types: guaranteed bit rate (GBR) and non-guaranteed bit rate (non-GBR). In the case of GBR QoS flows, the corresponding bit rate can be guaranteed even when network resources are scarce. In the case of non-GBR QoS flows, bit rate reduction requirements must be met when network resources are scarce.

[0005] Currently, more than 90% of service flows are non-GBR QoS flows, such as general audio and video calls and online conferences. Since audio and video communication is often delayed due to changes in wireless network conditions, it is desirable to optimize QoS control for non-GBR QoS flows.

[0006] The present application provides a method and apparatus for controlling an application program, a device, and a storage medium. A QNC mechanism is provided for a non-GBR QoS flow, enabling an application entity to actively control the execution of an application program to adapt to the change after detecting a change in the wireless network state. The technical solution is as follows:

[0007] According to an aspect of the present application, an application program control method is,

[0008] A step of receiving a notification message transmitted by a core entity by an application entity — said notification message is used to indicate that a change in a parameter value of the quality of service notification control (QNC) of a guaranteed bit rate (GBR) bearer flow satisfies a reporting condition —; and

[0009] The method includes the step of controlling an application program according to the notification message by the application entity.

[0010] According to another aspect of the present application, an application program control method is provided, and

[0011] A step of receiving a notification message transmitted by an access network device by a core entity — said notification message is used to indicate that a change in a parameter of a Quality of Service Notification Control (QNC) of a non-guaranteed bit rate (GBR) flow satisfies a reporting condition —; and

[0012] The method includes the step of transmitting the notification message to the application entity by the core entity so that the application entity controls the traffic of the application program according to the notification message.

[0013] According to another aspect of the present application, an application program control device is provided, and

[0014] A receiving module configured to receive a notification message transmitted by a core entity — said notification message is used to indicate that a change in a parameter value of the Quality of Service Notification Control (QNC) of a non-guaranteed bit rate (GBR) bearer flow satisfies a reporting condition —; and

[0015] It includes a control module configured to control an application program according to the above notification message.

[0016] According to another aspect of the present application, an application program control device is provided, and

[0017] A receiving module configured to receive a notification message transmitted by an access network device — said notification message is used to indicate that a change in a parameter of the Quality of Service Notification Control (QNC) of a non-guaranteed bit rate (GBR) flow satisfies a reporting condition —; and

[0018] It includes a transmission module configured to transmit the notification message to the application entity so that the application entity controls the traffic of the application program according to the notification message.

[0019] According to an aspect of the present application, a network element device is provided, comprising a processor and a memory, wherein the memory stores a computer program executed by the processor to enable the network element device to implement an application program control method as described above.

[0020] According to an aspect of the present application, a chip is provided and includes a programmable logic circuit configured to implement an application program control method as described above when executed.

[0021] According to another aspect of the present application, a computer-readable storage medium is provided, which stores a computer program, and said computer program is loaded and executed by a processor to implement the aforementioned application program control method.

[0022] According to another aspect of the present application, a computer program product is provided, said computer program product includes computer instructions, said computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads said computer instructions from said computer-readable storage medium and executes said computer instructions to cause said computer device to perform an application program control method according to the aforementioned aspect.

[0023] The technical solution provided in the embodiments of the present application includes at least the following beneficial effects:

[0024] If an increase or decrease in the QNC parameters of a non-GBR bearer flow satisfies the reporting conditions, the core entity sends a notification message to the application entity, and upon receiving the notification message, the application entity controls the application program according to the notification message. In this way, a QNC mechanism is provided for non-GBR bearer flows, allowing the application entity to detect changes in the wireless network state of the non-GBR bearer flow and then actively control the execution of the application program to adapt to the changes. For example, the computing policy and traffic policy of the application program are controlled so that when the QNC parameters deteriorate or are restored, the application entity can adjust the application program to adapt to network transmission under these parameter changes. Brief explanation of the drawing

[0025] FIG. 1 is a structural block diagram of a mobile communication system according to an exemplary embodiment of the present application. FIG. 2 is a structural block diagram of a mobile communication system according to another exemplary embodiment of the present application. FIG. 3 is a flowchart of a QoS change notification method according to an exemplary embodiment of the present application. FIG. 4 is a flowchart of a QoS change notification method according to another exemplary embodiment of the present application. FIG. 5 is a flowchart of a QNC configuration method according to an exemplary embodiment of the present application. FIG. 6 is a flowchart of a QNC configuration method according to another exemplary embodiment of the present application. FIG. 7 is a flowchart of a QNC configuration method according to another exemplary embodiment of the present application. FIG. 8 is a flowchart of a QNC optimization method according to an exemplary embodiment of the present application. FIG. 9 is a flowchart of a QNC optimization method according to another exemplary embodiment of the present application. FIG. 10 is a schematic diagram of a PDU session modification process (for non-roaming and local breakout roaming) requested by a UE or network according to an exemplary embodiment of the present application. FIG. 11 is a schematic diagram of an SM policy association modification process according to an exemplary embodiment of the present application. FIG. 12 is a schematic diagram of a PDU session setup process requested by a UE according to an exemplary embodiment of the present application. FIG. 13 is a flowchart of the PDU session setup process requested by the UE in a home routing roaming scenario according to an exemplary embodiment of the present application. FIG. 14 is a schematic diagram of a process of transmitting to an associated PCF in response to a request from an AF for a single UE address according to an exemplary embodiment of the present application. FIG. 15 is a schematic diagram of a PDU session modification process requested by a UE or network for non-roaming and local breakout roaming according to an exemplary embodiment of the present application. FIG. 16 is a schematic diagram of a PDU session modification process requested by a UE or network for home routing roaming according to an exemplary embodiment of the present application. FIG. 17 is a drawing illustrating an application program control device according to an exemplary embodiment of the present application. FIG. 18 is a drawing illustrating an application program control device according to an exemplary embodiment of the present application. FIG. 19 is a block diagram of a network element device according to an exemplary embodiment of the present application. Specific details for implementing the invention

[0026] FIG. 1 is a schematic architectural diagram of a mobile communication system according to an exemplary embodiment of the present application. As illustrated in FIG. 1, the system architecture (100) may include user equipment (UE), a radio access network (RAN), a core, and a data network (DN). The UE, RAN, and core are the main components of the architecture, and each may be logically separated into two parts: a user plane and a control plane, where the control plane is responsible for managing the mobile network and the user plane is responsible for transmitting service data. In FIG. 1, reference point NG2 is located between the RAN control plane and the core control plane, reference point NG3 is located between the RAN user plane and the core user plane, and reference point NG6 is located between the core user plane and the data network.

[0027] UE: As a portal that allows mobile users to interact with the network, it provides basic computing power and storage capacity, displays service windows to users, and can accept user operation input. The UE can establish signaling and data connections with the RAN using next-generation wireless interface technology to transmit control signals and service data to the mobile network.

[0028] RAN: Similar to base stations in existing networks, it is deployed close to UEs to provide network access capabilities to authorized users within cell coverage, and can transmit user data using transmission tunnels of different qualities depending on the user level, service requirements, etc. The RAN manages and efficiently utilizes its own resources, provides access services to UEs as needed, and can transmit control signals and user data between the UE and the core.

[0029] Core: It is responsible for maintaining subscription data of the mobile network, managing network elements of the mobile network, and providing functions for the UE such as session management, mobility management, policy management, and security authentication. The Core provides network access authentication for the UE when the UE connects, allocates network resources for the UE when there is a service request from the UE, updates network resources for the UE when the UE moves, provides a fast recovery mechanism for the UE when the UE is idle, releases network resources for the UE when the UE disconnects, provides data routing functions for the UE when the UE holds service data such as uplink data delivery to the DN, and receives the UE's downlink data from the DN and delivers it to the RAN for transmission to the UE.

[0030] DN: A data network for providing business services to users. Generally, clients are located in the UE, and servers are located in the data network. The data network can be a private network such as a local area network, an external network not controlled by an operator such as the Internet, or a dedicated network jointly deployed by an operator, such as an IP multimedia network subsystem (IMS) service configuration.

[0031] Figure 2 is a detailed architecture determined based on Figure 1. The core user plane includes user plane functions (UPF). The core control plane includes authentication server functions (AUSF), access and mobility management functions (AMF), session management functions (SMF), network slice selection functions (NSSF), network exposure functions (NEF), NF repository functions (NRF), unified data management (UDM), policy control functions (PCF), and application functions (AF). The functions of these function entities (referred to as functions or entities for short) are as follows:

[0032] UPF: Performs user data packet forwarding according to SMF routing rules;

[0033] AUSF: Performs security authentication for the UE;

[0034] AMF: UE Access and Mobility Management;

[0035] SMF: UE session management;

[0036] NSSF: Select UE network slice;

[0037] NEF: Exposing network functions to third parties via API;

[0038] NRF: Provides the ability to store and select network function entity information for other network elements;

[0039] UDM: User Subscription Context Management;

[0040] PCF: User Policy Management; and

[0041] AF: User Application Management.

[0042] In the architecture illustrated in FIG. 2, the N1 interface is a reference point between the UE and the AMF. The N2 interface is a reference point between the RAN and the AMF for transmitting NAS messages, etc. The N3 interface is a reference point between the RAN and the UPF for transmitting user plane data, etc. The N4 interface is a reference point between the SMF and the UPF for transmitting tunnel identification information, data cache instructions, downlink data notification messages, and other information for the N3 connection. The N6 interface is a reference point between the UPF and the DN for transmitting user plane data, etc. The next-generation (NG) interface is an interface between the wireless access network device and the 5G core.

[0043] The interface names between the various network elements in FIGS. 1 and 2 are merely illustrative and may be different in specific implementations. There are no specific limitations thereon in the embodiments of this application. The names of the various network elements (e.g., SMF, AF, and UPF) in FIGS. 1 and 2 are also merely illustrative and do not form limitations on the functions of the network elements. In 5G and other future networks, each of the aforementioned network elements may also have different names, and there are no specific limitations thereon in the embodiments of this application. For example, in a 6G network, some or all of the various network elements may be referred to by terms used in 5G or other names, etc., which are described collectively in this specification and will not be described in detail below. Furthermore, it should be understood that the names of the messages (or signaling) transmitted between the various network elements are also merely illustrative and do not form any limitations on the functions of the messages. Various network element entities may be implemented as computer devices or virtual computer devices running on computer devices.

[0044] In the embodiments of the present application, a quick change QoS notification control (QCQNC) mechanism is defined for non-GBR QoS flows. The QCQNC mechanism is a type of QNC referred to simply as QNC. In the QCQNC mechanism provided by the embodiments of the present application, the access network device transmits a quick change notification to the SMF when it detects a quick change in at least one QoS parameter of a non-GBR QoS flow. The SMF transmits the quick change notification to the PCF, AF, and UE. Upon receiving the quick change notification, the AF and UE can adjust their internal application programs to match the change to prevent latency and other phenomena affecting quality of experience (QoE).

[0045] A QoS flow is the smallest QoS distinguishing granularity in a PDU session. In 5G systems, a QoS Flow ID (QFI) is used to distinguish QoS flows. QoS flows are controlled by SMFs. QoS flows can be pre-configured or created during the PDU session setup process, or modified during the PDU session modification process.

[0046] In an embodiment of the present application, the following QoS characteristics are defined for a non-GBR QoS flow:

[0047] 5G QoS identifier (5QI), allocation and retention priority (ARP), reflective QoS attribute (RQA).

[0048] Corresponding to 5QI for non-GBR QoS flows, only the following QoS characteristics are defined:

[0049] Resource types including GBR, delayed critical GBR, or non-GBR;

[0050] Priority level;

[0051] Packet delay budget (PDB) — Packet data delay (budget) includes the core's packet delay —; and

[0052] Packet error rate (PER).

[0053] Among the four QoS characteristics, the first two parameters, resource type and priority level, define the characteristics of 5QI, and the last two parameters, PDB and PER, define the performance of 5QI.

[0054] In an embodiment of the present application, it is proposed that the QNC profile includes three parameters for a non-GBR QoS flow (NGBF): PDB, PER, and current bit rate (CBR). When the RAN detects that the rate of change (or value of change) of any one of the three parameters increases or decreases exceeds a specified threshold (since the parameters have different characteristics, the parameters may correspond to different rates of change or values ​​of change), the RAN sends a notification message to the SMF and notifies the rate of change or values ​​of change of all parameters. The SMF sends the notification message to the PCF, the PCF sends the notification message to the AF, and the application program corresponding to the AF is adjusted accordingly. Meanwhile, the SMF sends the notification message to the UE via a NAS message, and the application program corresponding to the UE may also be adjusted accordingly. In this way, the interaction between the network and the application program is implemented, optimizing service transmission and resolving issues such as delays during network congestion or the problem where the user experience may not be improved because network resources are not sufficiently utilized due to the application program still using a very low transmission rate even when network conditions improve.

[0055] In the examples, two types of parameter changes are defined.

[0056] 1: Change value

[0057] When a parameter value changes from A to B, BA is defined as the change value. If the change value of the parameter value from A to B is the first change value and the change value from B to A is the second change value, then the magnitudes of the first change value and the second change value are the same (plus or minus signs are ignored).

[0058] 2: Change rate

[0059] In a possible design, (BA) / A is defined as the rate of change when a parameter value changes from A to B. If the rate of change of the parameter value from A to B is the first rate of change (BA) / A, while the rate of change from B to A is the second rate of change (AB) / B, then the magnitudes of the first and second rates of change are the same (ignoring the plus or minus sign).

[0060] That is, the size of (BA) / A is not equal to the size of (AB) / B (assuming B > A > 0). Therefore, in the definition above, parameter value A is not restored by increasing parameter value B by 30% and then decreasing parameter value B by 30%.

[0061] In another possible design, to restore the same parameter value by first increasing it by 30% and then decreasing it by 30%, the rate of change is uniformly defined as the ratio of the smaller value to the larger value minus the smaller value before and after the change, or as the ratio of the larger value to the smaller value before and after the change, or as the ratio of the fixed value to the larger value minus the smaller value before and after the change. The larger value is the value with the larger absolute value among the parameter values ​​before and after the change, the smaller value is the value with the smaller absolute value among the parameter values ​​before and after the change, and the fixed value is a predetermined value that does not change. Therefore, when parameter value A is first increased by 30% and then decreased by 30%, the original parameter value A is restored.

[0062] In an embodiment, the following communication protocol is provided.

[0063] QoS profile

[0064] Whether a QoS flow is a GBR flow or a non-GBR flow is determined by the corresponding QoS profile. The QoS profile of a QoS flow is transmitted to the (R)AN including the following QoS parameters (detailed information on QoS parameters is defined in Section 5.7.2 of the communication protocol TS23.501).

[0065] - For each QoS flow, the QoS profile must include the following QoS parameters:

[0066] -5QI; and

[0067] -ARP.

[0068] - For each non-GBR QoS flow only, the QoS profile may additionally include the following QoS parameters:

[0069] -QCQNC; and

[0070] -RQA.

[0071] - For each GBR QoS flow only, the QoS profile may additionally include the following QoS parameters:

[0072] - Guaranteed Flow Bit Rate (GFBR) - Uplink and Downlink, and

[0073] - Maximum flow bit rate (MFBR) - uplink and downlink; and

[0074] - For GBR QoS flows only, the QoS profile may include one or more additional QoS parameters:

[0075] -Notification control; and

[0076] -Max Packet Loss Rate-Uplink and Downlink.

[0077] In an embodiment, a QoS quick change notification control profile is provided.

[0078] A QoS fast change notification control profile is provided for non-GBR QoS flows that enable fast change notification control. If the corresponding PCC rule contains relevant information (as described in the communication protocol TS 23.503), the SMF must also provide a fast change notification control profile for the NG-RAN in addition to the QoS profile. If the SMF provides a fast change notification control profile for the NG-RAN (where the information of the corresponding policy and charging control (PCC) rule changes), the NG-RAN may replace the previously stored profile with that profile.

[0079] The Quick Change Notification Control Profile directs rapid changes to any QoS parameters, such as PDB, PER, and Detected Current Bit Rate (CBR), to help application programs control their traffic based on the changed QoS parameters. The Quick Change Notification Control Profile directs rapid changes (increases or decreases) to PDB, PER, and CBR within a short timeframe (20%, 10%, 30%), and the new values ​​may be maintained after the change. In other words, the rapid change is not a short, fast spike caused by rapid shock interference, etc.

[0080] Note: A quick change notification control profile can be any combination of changes to PDB, PER, and CBR. For example, a quick change notification control profile can be set to increase (or decrease) PDB by 20%, or increase (or decrease) PDB and PER by 20% and increase (or decrease) CBR by 10%, or increase (or decrease) CBR by 30%.

[0081] When NG-RAN sends a quick change notification to SMF that meets the QCQNC profile, NG-RAN must also include current QoS parameters (PDB, PER) and CBR in the notification message.

[0082] The QNC mechanism for non-GBR bearer flow is at least the following process:

[0083] 1: QNC notification process (for AF);

[0084] 2: QNC configuration process; and

[0085] 3: QNC's Optimization Process

[0086] Includes

[0087] The above process is explained separately below.

[0088] 1. QNC Notification Process (for AF)

[0089] FIG. 3 is a flowchart of a method for notifying a change in QoS according to an exemplary embodiment of the present application. This embodiment is described using an example in which the method is applied to a mobile communication system illustrated in FIG. 1 or FIG. 2. The method comprises the following steps:

[0090] Step 320 The access network device sends a notification message to the application entity via the core entity when a change in the QNC parameter of a non-GBR bearer flow satisfies the reporting condition.

[0091] Non-GBR bearer flow refers to a non-GBR type bearer flow. Non-GBR bearer flow includes non-GBR QoS flow or non-GBR EPS bearers. For example, in a 5G system, a non-GBR bearer flow is a non-GBR type QoS flow, and in a 4G system, a non-GBR bearer flow is a non-GBR type EPS bearer.

[0092] For example, the parameters of QNC (or QCQNC) include at least one of PDB, PER, and CBR. If there are at least two parameters of QNC, at least two parameters correspond to the same reporting condition, or at least two parameters correspond to different reporting conditions.

[0093] For example, the reporting condition (or change threshold or change reporting threshold) includes at least one of the following:

[0094] Condition in which the change value of a QNC parameter within the first time is greater than the first threshold — the first threshold is a fraction greater than 0 and less than 1, for example, the first threshold is 20%, 30%, and 40%, and the first time is a period or time for counting the change value, such as 1 second and 2 seconds —;

[0095] Condition in which the rate of change of a QNC parameter is greater than the second threshold within the second time — the second threshold is a fraction greater than 0 and less than 1, for example, the second threshold is 20%, 30%, or 40%, and the second time is a period or time for computing the rate of change, such as 1 second and 2 seconds —;

[0096] A condition in which the change value of a QNC parameter within a first time is greater than the first threshold and continues to be maintained for the third threshold — the third threshold is a threshold for measuring the duration of the change value, such as 2 seconds —; and

[0097] A condition in which the rate of change of a QNC parameter within the second time is greater than the second threshold and continues to be maintained for the fourth threshold — the fourth threshold is a threshold for measuring the duration of the rate of change, such as 2 seconds —.

[0098] For example, the notification message additionally includes the changed parameter value of QNC, that is, the current parameter value of QNC after a rapid change of QNC parameters. "Current" is a relative value, not an absolute one. For instance, the current parameter value is the parameter value at the time the reporting condition was triggered, and it is not necessarily the same as the real-time parameter value after the notification message is sent.

[0099] For example, the changed parameter value of QNC can be represented by the quantized value of the changed parameter value of QNC. For example, the value range of QNC is separated into 16 non-overlapping sub-intervals. Each of the 16 sub-intervals corresponds to a unique quantized value represented by 4 bits. If it falls within the i-th sub-interval, the changed parameter value of QNC is represented by the quantized value corresponding to the i-th sub-interval, which requires only 4 bits. Thus, the transmission resources required for the notification message can be reduced.

[0100] Step 340 The application entity controls the application program according to the notification message.

[0101] Notification messages (or quick change notifications, quick change reports, or notification reports) are used to indicate that a change in QoS Notification Control (QNC) parameters of a non-GBR bearer flow satisfies reporting conditions.

[0102] The application entity can adapt the application program to rapid changes in relevant parameters of a non-GBR bearer flow by controlling at least one of the application program's execution parameters, execution policy, and traffic according to a notification message.

[0103] An application entity executes one or more application programs, and the same application program corresponds to at least one service data flow (SDF). SDFs with different QoS requirements are each mapped to an independent QoS flow. 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. Optionally, SDFs with the same QoS requirement may be mapped to the same QoS flow.

[0104] In the present embodiment of the application, it is assumed that one or more QoS flows corresponding to an application program include a non-GBR QoS flow for transmitting data packets of at least one service, such as voice, video, text, message, file, control information, etc.

[0105] In summary, according to the method provided in this embodiment, when an increase or decrease in the QNC parameter of a non-GBR bearer flow satisfies a reporting condition, the core entity transmits a notification message to the application entity, and upon receiving the notification message, the application entity controls the application program in accordance with the notification message. In this way, a QNC mechanism is provided for the non-GBR bearer flow so that the application entity can detect a change in the wireless network state of the non-GBR bearer flow and then actively control the execution of the application program to adapt to the change. For example, the computing policy and traffic policy of the application program are controlled so that when the QNC parameter deteriorates or recovers, the application entity can adjust the application program to adapt to network transmission according to such parameter changes.

[0106] Steps performed by the access network device may be separately implemented as embodiments on the access network device side. Steps performed by the application entity may be separately implemented as embodiments on the application entity side. Detailed description is omitted in this application.

[0107] FIG. 4 is a flowchart of a QoS change notification method according to another exemplary embodiment of the present application. This embodiment is described using an example in which the method is applied to a mobile communication system illustrated in FIG. 1 or FIG. 2. The method comprises the following steps:

[0108] Step 322: If a change in QNC parameters of a non-GBR bearer flow satisfies the reporting condition, the access network device sends a notification message to the core entity.

[0109] The core entity receives a notification message transmitted by the access network device. The notification message is used to indicate that a change in the QoS Notification Control (QNC) parameter of a non-GBR bearer flow satisfies the reporting condition.

[0110] For example, the notification message additionally includes the changed parameter value of QNC, that is, the current parameter value of QNC after a rapid change of QNC parameters. "Current" is a relative value, not an absolute one. For instance, the current parameter value is the parameter value when the reporting condition is triggered, and it is not necessarily the same as the real-time parameter value after the notification message is sent.

[0111] For example, the changed parameter value of QNC can be represented by the quantized value of the changed parameter value of QNC. For example, the value range of QNC is separated into 16 non-overlapping sub-intervals. Each of the 16 sub-intervals corresponds to a unique quantized value represented by 4 bits. If it falls within the i-th sub-interval, the changed parameter value of QNC is represented by the quantized value corresponding to the i-th sub-interval, which requires only 4 bits. Thus, the transmission resources required for the notification message can be reduced.

[0112] Step 324: The core entity sends a notification message to the application entity.

[0113] There is one or more core entities. If a notification message involves multiple core entities located between the RAN and the AF, the multiple core entities transmit the notification message sequentially. Different core entities may include the notification message in different types of messages. For example, the core entities include a mobility management entity (MME), a service gateway (SGW), a PDN gateway (PGW), and a PCF. In this case, the transmission path of the notification message is at least RAN→MME→SGW / PGW → It includes PCF→AF. As another example, the core entity includes a first core entity AMF, a second core entity SMF, and a third core entity PCF. In this case, the transmission path of the notification message includes at least RAN→AMF→SMF→PCF→AF.

[0114] For example, the core entity sends an event report containing a notification message to the application entity.

[0115] Step 342 The application entity receives a notification message sent by the core entity.

[0116] For example, the application entity receives event reports sent by the core entity.

[0117] Step 344 The application entity controls the application program according to the notification message.

[0118] The application entity controls at least one of the application program's computing policy and traffic policy according to a notification message to adapt the application program to rapid changes in relevant parameters of non-GBR bearer flow, thereby maximizing the user's QoE and preventing delays and other phenomena.

[0119] Taking a server-side application program for an online conference as an example, the application program corresponds to four SDFs: voice SDF, video SDF, text message SDF, and control plane SDF. The four SDFs correspond to four non-GBR QoS flows. For each of the four non-GBR QoS flows, the QNC mechanism is enabled.

[0120] 1. Possible Implementation:

[0121] The application program is controlled to execute according to the first computing policy in response to a notification message used to indicate the deterioration of the parameter value of QNC, and

[0122] The application program is controlled to execute according to a second computing policy in response to a notification message used to instruct the optimization of QNC parameter values, and

[0123] The computing time for the same computing task under the first computing policy is shorter than the computing time under the second computing policy.

[0124] A computing policy is a policy regarding the computing execution of an application program. A computing policy includes, but is not limited to, at least one of an encoding and decoding mode selection policy, an encoding and decoding model selection policy, an encoding and decoding level selection policy, a compression level selection policy, and a neural network model selection policy.

[0125] For example, where the computing policy is an encoding and decoding mode selection policy, the application program is controlled to perform encoding and decoding in a first encoding and decoding mode in response to a notification message used to instruct the deterioration of the parameter values ​​of QNC, and the application program is controlled to perform encoding and decoding in a second encoding and decoding mode in response to a notification message used to instruct the optimization of the parameter values ​​of QNC. Here, "encoding and decoding" refers to at least one of encoding and decoding.

[0126] The computing time for the same computing task in the first encoding and decoding mode is shorter than in the second encoding and decoding mode.

[0127] For example, if the PDB increases, even if network delay increases, the application program can compensate for the worsening of network delay by reducing internal computing time so that the overall transmission delay remains unchanged or changes only slightly. For example, if the PDB of a non-GBR QoS flow corresponding to video degrades, the encoding rate of the video can be reduced to decrease the quantity and / or size of video data packets.

[0128] 2. Possible Implementation:

[0129] The application program is controlled to execute according to the first traffic policy in response to a notification message used to indicate the deterioration of the QNC parameter value, and

[0130] The application program is controlled to execute according to a second traffic policy in response to a notification message used to instruct the optimization of QNC parameter values, and

[0131] The traffic of the first traffic policy is less than the traffic of the second traffic policy.

[0132] For example, the traffic of an application program includes voice data packets and video data packets.

[0133] In response to a notification message used to indicate the deterioration of the QNC parameter value, the first traffic corresponding to voice data packets is maintained, and the second traffic corresponding to video data packets is reduced. In response to a notification message used to indicate the optimization of the QNC parameter value, the first traffic corresponding to voice data packets is maintained, and the second traffic corresponding to video data packets is increased.

[0134] For example, when the PDB increases, the traffic of the first non-GBR QoS flow corresponding to video is reduced, while the traffic of the second non-GBR QoS flow corresponding to voice is maintained. Consequently, the overall wireless resource occupancy is reduced, which can improve the transmission quality of voice data packets and reduce interference.

[0135] This is because cloud-based applications (video conferencing, voice conferencing, remote learning) generally require two-way interaction between video and audio. There are specific requirements regarding network transmission delay (typically, one-way transmission delay is less than 150ms). However, in actual use, audio and video delays may occur due to changes in wireless network conditions, which can cause wireless network transmission delays to suddenly worsen or transmission speeds to suddenly decrease within a certain period of time (e.g., 5 seconds).

[0136] According to relevant research, users are highly sensitive to audio latency but not so sensitive to changes in video quality (such as changes in resolution and clarity) (it is acceptable to temporarily turn off the video while keeping the audio on). In the case of audio, latency does not occur frequently because the transmitted data is generally small. However, if audio is delayed, the user experience becomes very poor. Furthermore, even if the audio is degraded from CD quality to a very low transmission rate (e.g., 2G voice transmission quality), users still have a very good user experience as long as no latency occurs.

[0137] In summary, according to the method provided in this embodiment, the application entity adjusts the application program according to the changed parameter values ​​of the QNC, so that when the relevant parameters of the non-GBR bearer flow deteriorate or the relevant parameters of the non-GBR bearer flow are restored, the application entity can adjust the internal application program to adapt to these parameter changes in order to optimize the execution of the application program.

[0138] According to the method provided in this embodiment, if the relevant parameters of a non-GBR bearer flow deteriorate, the computing policy of the application program is further changed to reduce the computing time of the application program to compensate for the deterioration of network delay, thereby ensuring that the overall transmission delay remains unchanged or changes only slightly.

[0139] According to the embodiment provided in this embodiment, if the relevant parameters of a non-GBR bearer flow deteriorate, the traffic policy of the application program is further changed. For example, while the traffic of voice data packets is maintained, the traffic of video data packets is reduced. Accordingly, audio delays that have a greater impact on the user experience are prevented, and furthermore, the user experience is maximized when using audio and video programs.

[0140] 2. QNC Configuration Process

[0141] In the creation or modification process of a non-GBR bearer flow, the core entity performs the configuration process of the QNC for the access network device. That is, the core entity transmits a QNC profile to the access network device, and the QNC profile is used to configure the QNC parameters and reporting conditions (or change threshold, quick change threshold, change reporting threshold, or quick change reporting threshold).

[0142] FIG. 5 is a flowchart of a method for configuring a QNC according to an exemplary embodiment of the present application. This embodiment is described using an example in which this method is applied to a mobile communication system illustrated in FIG. 1 or FIG. 2. This method comprises the following steps:

[0143] Step 420 : The third core entity PCF transmits the parameters and reporting conditions of the QNC to the second core entity SMF.

[0144] The third core entity is the entity responsible for policy management in the core.

[0145] The second core entity is the entity responsible for session management in the core.

[0146] For example, in the process of creating or modifying a non-GBR bearer flow, the third core entity PCF transmits the parameters and reporting conditions of the QNC to the second core entity SMF.

[0147] For example, in the PDU session setup process, a (first) QoS flow is created, referred to as a QoS flow with default QoS rules. Typically, the QoS flow is of a non-GBR type. The third core entity can provide parameters and reporting conditions for the QNC for the second core entity.

[0148] For example, QNC parameters and reporting conditions are determined independently by the third core entity PCF. Alternatively, QNC parameters and reporting conditions are determined by the third core entity PCF based on service flow information transmitted by the application entity. Alternatively, QNC parameters and reporting conditions are determined by the third core entity PCF based on the UE's subscription data.

[0149] Step 440 : The second core entity SMF receives the PCC rule transmitted by the third core entity PCF.

[0150] Step 460 The second core entity transmits a QNC profile to the access network device, and this QNC profile is used to configure the parameters and reporting conditions of the QNC for the access network device.

[0151] In summary, according to the method provided in this embodiment, the third core entity transmits the parameters and reporting conditions of the QNC to the second core entity, thereby triggering the second core entity to configure the parameters and reporting conditions of the QNC for a non-GBR bearer flow, so as to complete the configuration process of the QNC.

[0152] In one design, the application entity provides service flow information to a third core entity, which is service flow information including parameters and reporting conditions of QNC requested (or proposed) by the application entity, as illustrated in FIG. 6. In another design, the third core entity determines the parameters and reporting conditions of QNC based on subscription data of QNC, as illustrated in FIG. 7.

[0153] FIG. 6 is a flowchart of a method for configuring a QNC according to another exemplary embodiment of the present application. This embodiment is described using an example in which the method is applied to a mobile communication system illustrated in FIG. 1 or FIG. 2. The method comprises the following steps:

[0154] Step 412 : The application entity AF transmits the control parameters of QNC to the third core entity PCF.

[0155] The control parameters of QNC include at least one of whether QNC is enabled, the parameters of QNC, and the change threshold.

[0156] The application entity AF sends a policy authorization create / update message to the core entity, and the policy authorization create / update message includes control parameters of the QNC. Correspondingly, the third core entity PCF receives the policy authorization create / update message sent by the application entity AF.

[0157] Step 420: The third core entity PCF transmits a PCC rule to the second core entity SMF, and the PCC rule includes control parameters of the QNC.

[0158] Step 440 : The second core entity SMF receives the PCC rule transmitted by the third core entity PCF.

[0159] Step 460 The second core entity transmits a QNC profile to the access network device, and this QNC profile is used to configure the control parameters of the QNC for the access network device.

[0160] In summary, according to the method provided in this embodiment, the application entity provides control parameters of the QNC to the third core entity, thereby enabling active interaction between the application entity and the core entity. By driving a wireless access network device (e.g., a 5G or 4G RAN) to report rapid changes in non-GBR bearer flows, the wireless access network device can expose network capabilities to the application entity, thereby providing a new method for innovation in Internet applications.

[0161] FIG. 7 is a flowchart of a method for configuring a QNC according to another exemplary embodiment of the present application. This embodiment is described using an example in which the method is applied to a mobile communication system illustrated in FIG. 1 or FIG. 2. The method comprises the following steps:

[0162] Step 414 : The fourth core entity UDM transmits QNC's subscription data to the third core entity PCF, and QNC's subscription data includes QNC's control parameters.

[0163] If the base 5QI is of the non-GBR type, QNC's subscription data is added to the non-GBR bearer flow. The 4th core entity UDM transmits QNC's subscription data to the 2nd core entity SMF, and the 2nd core entity SMF transmits QNC's subscription data to the 3rd core entity PCF.

[0164] Step 420 : The third core entity PCF transmits a default QoS rule to the second core entity SMF, and the default QoS rule includes the control parameters of the QNC.

[0165] Step 440 : The second core entity SMF receives the basic PCC rule transmitted by the third core entity PCF.

[0166] Step 460 The second core entity transmits a QNC profile to the access network device, and this QNC profile is used to configure the control parameters of the QNC for the access network device.

[0167] In summary, according to the method provided in this embodiment, a third core entity determines the control parameters of the QNC based on the UE's subscription data so that a wireless access network device is driven based on the UE's subscription data and can report rapid changes in non-GBR bearer flow to the UE when there is no AF providing the control parameters of the QNC.

[0168] 3. QNC's Optimization Process

[0169] If the third core entity PCF or application entity AF detects notification messages from QNC too frequently, a large amount of signaling occurs in the system. In such cases, the third core entity PCF or application entity AF must modify the reporting conditions of QNC, such as by increasing the change threshold.

[0170] FIG. 8 is a flowchart of a method for optimizing QNC according to an exemplary embodiment of the present application. This embodiment is described using an example in which the method is applied to a mobile communication system illustrated in FIG. 1 or FIG. 2. The method comprises the following steps:

[0171] Step 520 : If the reporting frequency of notification messages by the third core entity PCF is greater or less than the frequency threshold, it transmits the updated control parameters of the QNC to the second core entity SMF.

[0172] The updated control parameter of QNC includes at least one of whether QNC is enabled, the updated parameter of QNC, and the updated change threshold. That is, the updated control parameter of QNC can update at least one of QNC enable, the parameter of QNC, and the change threshold.

[0173] For example, the third core entity PCF sends a command to the second core entity SMF to disable QNC if the reporting frequency of notification messages exceeds a frequency threshold. As another example, the third core entity PCF sends reduced parameters of QNC to the second core entity SMF if the reporting frequency of notification messages exceeds a frequency threshold. As yet another example, the third core entity PCF sends an increased change threshold to the second core entity SMF if the reporting frequency of notification messages exceeds a frequency threshold.

[0174] Step 540 : The second core entity SMF transmits a QNC profile to the access network device, and this profile includes updated control parameters of the QNC.

[0175] In summary, according to the method provided in this embodiment, when the reporting frequency of a notification message is greater than or less than a frequency threshold, the updated control parameters of the QNC are transmitted to the second core entity SMF and the access network device. Thus, the system can avoid relatively high signaling overhead, or the QNC mechanism can be used reasonably.

[0176] FIG. 9 is a flowchart of a method for optimizing QNC according to another exemplary embodiment of the present application. This embodiment is described using an example in which the method is applied to a mobile communication system illustrated in FIG. 1 or FIG. 2. The method comprises the following steps:

[0177] Step 510 The application entity transmits the updated control parameters of the QNC to the third core entity PCF if the reporting frequency of the notification message is greater or less than the frequency threshold.

[0178] The updated control parameter of QNC includes at least one of whether QNC is enabled, the updated parameter of QNC, and the updated change threshold. That is, the updated control parameter of QNC can update at least one of QNC enable, the parameter of QNC, and the change threshold.

[0179] For example, AF sends a command to disable QNC to the third core entity PCF if the reporting frequency of notification messages exceeds the frequency threshold. As another example, AF sends reduced parameters of QNC to the third core entity PCF if the reporting frequency of notification messages exceeds the frequency threshold. As yet another example, AF sends an increased change threshold to the third core entity PCF if the reporting frequency of notification messages exceeds the frequency threshold.

[0180] Step 520 : The third core entity PCF transmits the updated control parameters of QNC to the second core entity SMF.

[0181] Step 540 : The second core entity SMF transmits a QNC profile to the access network device, and this QNC profile includes updated control parameters of the QNC.

[0182] In summary, according to the method provided in this embodiment, when the reporting frequency of a notification message is greater than or less than a frequency threshold, the AF triggers the PCF to transmit the updated control parameters of the QNC to the second core entity SMF and the access network device. Thus, the system can avoid relatively high signaling overhead, or the QNC mechanism can be used reasonably.

[0183] The transmitted process is described in more detail below in relation to the third generation partnership project (3GPP) communication protocol (TS23.502). For details regarding the names of network elements, step flows, and steps in the following figure, refer to the relevant records in TS23.502 (https: / / www.3gpp.org / ftp / Specs / archive / 23_series / 23.502). Due to space limitations, this document focuses on the differences between the embodiments of this application and the TS23.502 protocol.

[0184] 1. QNC's Notification Process

[0185] When the network where the UE is located changes, that is, when the base station detects a rapid change (improvement or deterioration) in the radio resources, and when this change reaches a change threshold defined by the QNC, the RAN triggers the notification process of the QNC and transmits a notification message to the AF. Optionally, the notification message includes the parameter value of the changed parameter of the QNC (current parameter value). The base station first transmits a notification message to the SMF, then the SMF transmits a notification message to the PCF, and then the PCF transmits a notification message to the AF.

[0186] Non-roaming and local breakout roaming scenarios

[0187] FIG. 10 is a schematic diagram of a PDU session modification process (for non-roaming and local breakout roaming) requested by a UE or network according to an exemplary embodiment of the present application.

[0188] In step 1e, RAN sends the N2 message (PDU session ID, SM information) to AMF, and AMF sends the Namf_PDUSession_UpdateSMContext message to SMF.

[0189] These two messages include a notification message when the QNC parameters of a non-GBR bearer flow meet reporting conditions. Optionally, the notification message additionally includes the changed parameter values ​​of the QNC.

[0190] In Step 2, the SMF initiates the session management (SM) policy association modification process and sends a notification message to the PCF and AF.

[0191] In step 5, SMF sends a PDU session modification command to the UE to send the changed parameter values ​​of QNC to the UE.

[0192] For example, after a certain period of time following SM's receipt of a notification message, if SMF does not receive any new PCC rule from PCF or if there is no modification to the QoS of the PCC rule for the SDF corresponding to the QNC of the received PCC rule, SMF may initiate a PDU session modification command for UE to notify UE of the current parameter values ​​(PDB, PER, CBR) of the QNC of the QFI corresponding to the current QNC.

[0193] In step 9, the UE responds with a PDU session modification acknowledgment.

[0194] PDU session modification commands and PDU session modification confirmations are transparently transmitted between the UE and SMF via the RAN.

[0195] The SM policy association modification process shown in Step 2 is defined by Fig. 11. As illustrated in Fig. 11:

[0196] In Step 1, SMF sends an Npcf_SMPolicyControl_Update request to PCF, which includes a notification message.

[0197] In step 2, PCF sends the event report Npcf_PolicyAuthorizationNotify to AF, and this event report includes a notification message.

[0198] 2. QNC Configuration Process

[0199] 2.1 PDU Session Setup Scenarios for Non-Roaming and Local Breakout Roaming

[0200] FIG. 12 is a schematic diagram of a PDU session setup process requested by a UE according to an exemplary embodiment of the present application.

[0201] In steps 7b and 9, the SMF sends a new SM policy association setup request message to the PCF, and the PCF sends an SM policy association setup response message to the SMF, which is a message containing the control parameters of the QNC. Alternatively, the SMF sends an SM policy association modification request message to the PCF, and the PCF sends an SM policy association modification response message to the SMF, which is a message containing the control parameters of the QNC.

[0202] In the PDU session setup process, a QoS flow (typically the first) is created, referred to as the QoS flow with default QoS rules (unlike the default bearer in 4G, it is no longer referred to as the default QoS flow in 5G).

[0203] Generally, these QoS flows with basic QoS rules are of the non-GBR type, and the PCF may include control parameters of QNC in the PCC rules. In this case, in step 7b or 9 of FIG. 12, if the 5QI of the basic QoS rule provided by the PCF is of the non-GBR type, the PCF may provide control parameters of QCQNC to the SMF.

[0204] In steps 11 and 12, SMF sends a Namf_Communication_N1N2 information conversion message to AMF, which includes a QNC profile according to the control parameters of QCQNC provided by PCF.

[0205] Optionally, the UE's subscription data includes a default 5QI and a default ARP. If the default 5QI is of a non-GBR type, the QNC's subscription data is added.

[0206] In steps 4, 7b, and 9, the UDM provides a message containing QNC's subscription data to the SMF, then the SMF provides QNC's subscription data to the PCF, and then the PCF provides a basic QoS rule containing QNC's control parameters.

[0207] The PDU session setup process can be used for PDU session handover from N3GPP to 3GPP. If the PCF provides control parameters for the QNC for any non-GBR QoS flow in step 7b or 9, the control parameters for the QNC are added in steps 11 and 12 as previously described.

[0208] There may be multiple non-GBR QoS flows being processed.

[0209] Since the SM-related parameters of the N2 message in step 12 are included in step 11, the control parameters of QNC can be included in step 11.

[0210] 2.2 Home Routing Roaming Scenarios

[0211] FIG. 13 is a flowchart of the PDU session setup process requested by the UE in a home routing roaming scenario according to an exemplary embodiment of the present application.

[0212] In the PDU session setup process, a QoS flow (typically the first) is created, referred to as the QoS flow with default QoS rules (unlike the default bearer in 4G, it is no longer referred to as the default QoS flow in 5G).

[0213] Generally, these QoS flows with a basic QoS rule are of the non-GBR type, and the PCF may include control parameters of the QNC in the PCC rule. In this case, if the 5QI of the basic QoS rule provided by the PCF in the message of step 9b or 11 of Fig. 13 is of the non-GBR type, the PCF may provide control parameters of the QNC. Then, the QNC profile is added to the message of steps 13, 14, and 15.

[0214] Optionally, the UE's subscription data includes a default 5QI and a default ARP. If the default 5QI is of a non-GBR type, the QNC's subscription data is added.

[0215] In steps 7, 9b, and 11, the UDM provides QNC's subscription data to the SMF, the SMF provides QNC's subscription data to the PCF, and then the PCF provides a basic QoS rule containing QNC's control parameters.

[0216] 2.3 QoS Flow Generation Process Triggered by AF for Non-Roaming and Local Breakout Roaming Scenarios

[0217] FIG. 14 is a schematic diagram of a process of transmitting to an associated PCF in response to a request from an AF for a single UE address according to an exemplary embodiment of the present application. FIG. 15 is a schematic diagram of a PDU session modification process requested by a UE or network for non-roaming and local breakout roaming according to an exemplary embodiment of the present application.

[0218] In step 4 of FIG. 14, AF sends an Npcf_PolicyAuthorization_Create / Update message to PCF, and the control parameters of QNC are added as information for (one or more) media components of this message. As previously mentioned, if a media component includes the control parameters of QNC, the media component is requested to be transmitted via NGBF. If a media component does not include the parameters of QCQNC, this indicates that the media component may be transmitted via NGBF or GBR QoS flow (GBF).

[0219] In step 1b of Fig. 15, the PCF sends an Npcf_SMPolicyControlUpdateNotify request message. In this request message, the control parameters of the QNC are added to the PCC rules for (one or more) service data flows / flows (SDF / SDFs) (one SDF corresponds to one media flow provided by the AF).

[0220] Accordingly, the messages of steps 3b and 4 of FIG. 15 include the control parameters of QNC.

[0221] 2.4. QoS Flow Generation Process Triggered by AF for Home Routing Roaming Scenarios

[0222] FIG. 16 is a schematic diagram of a PDU session modification process requested by a UE or network for home routing roaming according to an exemplary embodiment of the present application.

[0223] In steps 1b, 3, 4b, and 5 of Fig. 16, control parameters of one or more QNCs (i.e., each possible service flow, SDF, and QoS flow) are added.

[0224] Step 3 of Fig. 16 is a new step related to the scenario described in Fig. 15. That is, the control parameter of QNC is added to the QoS parameter of one or more QoS flows.

[0225] The technology disclosed in this application may also be applied to 4G systems. When applied to 4G systems, the NR-gNB is replaced by an eNB. The interaction between the PCF and the AF is not changed. The interaction between the SMF and the PCF is modified to the interaction between the PGW and the PCF. The QoS flow of 5G is replaced by the EPS bearer in 4G. The 5QI of 5G is replaced by the QCI of 4G. The interaction between the RAN and the AMF / SMF in 5G is replaced by the interaction between the RAN and the MME in 4G.

[0226] FIG. 17 is a block diagram of an application program control device according to an exemplary embodiment of the present application. This device comprises:

[0227] A receiving module (1720) configured to receive a notification message transmitted by the core entity by the application entity ― the notification message is used to indicate that a change in the parameter value of the QNC of the non-GBR bearer flow satisfies a reporting condition ―; and

[0228] It includes a control module (1740) configured to control the application program according to a notification message.

[0229] In a possible design of the present embodiment of the application, the control module (1740) is configured to control the computing policy of the application program according to a notification message, and / or, the control module (1740) is configured to control the traffic policy of the application program according to a notification message.

[0230] In a possible design of the present embodiment of the present application, the control module (1740) is configured to control an application program to be executed according to a first computing policy in response to a notification message used to indicate deterioration of the parameter value of QNC, and to control an application program to be executed according to a second computing policy in response to a notification message used to indicate optimization of the parameter value of QNC.

[0231] The computing time for the same computing task under the first computing policy is shorter than the computing time under the second computing policy.

[0232] In a possible design of the present embodiment of the present application, the control module (1740) is configured to control an application program to perform encoding and decoding in a first encoding and decoding mode in response to a notification message used to indicate deterioration of the parameter value of QNC, and to control an application program to perform encoding and decoding in a second encoding and decoding mode in response to a notification message used to indicate optimization of the parameter value of QNC.

[0233] The computing time under the first encoding and decoding mode of the same computing task is shorter than the computing time under the second encoding and decoding mode.

[0234] In a possible design of the present embodiment of the present application, the control module (1740) is configured to control an application program to be executed according to a first traffic policy in response to a notification message used to indicate deterioration of the parameter value of QNC, and to control an application program to be executed according to a second traffic policy in response to a notification message used to indicate optimization of the parameter value of QNC.

[0235] The traffic of the first traffic policy is less than the traffic of the second traffic policy.

[0236] In a possible design of the present embodiment of the present application, the traffic of the application program includes voice data packets and video data packets, and

[0237] The control module (1740) is configured to maintain a first traffic corresponding to a voice data packet and reduce a second traffic corresponding to a video data packet in response to a notification message used to instruct the deterioration of the parameter value of the QNC, and to maintain a first traffic corresponding to a voice data packet and increase a second traffic corresponding to a video data packet in response to a notification message used to instruct the optimization of the parameter value of the QNC.

[0238] In a possible design of this embodiment of the present application, a notification message is transmitted to a core entity by an access network device entity in response to detecting that a change in the QNC parameter of a non-GBR bearer flow satisfies a reporting condition.

[0239] In a possible design of the present embodiment of the present application, the notification message is,

[0240] It includes the changed parameter value of QNC, or the quantized value of the changed parameter value of QNC.

[0241] In a possible design of the present embodiment of the application, the device is,

[0242] It further includes a transmission module (1760) configured to transmit control parameters of the QNC to a core entity, wherein the parameters of the QNC are used to indicate parameters and reporting conditions of the QNC.

[0243] In a possible design of this embodiment of the present application, the transmission module (1760) is configured to transmit a policy authorization create / update message to a core entity, and the policy authorization create / update message includes control parameters of the QNC.

[0244] In a possible design of the present embodiment of the present application, the method is,

[0245] It further includes the application entity sending the modified control parameters of the QNC to the core entity when the reporting frequency of notification messages is greater or less than the frequency threshold.

[0246] In a possible design of the present embodiment of the present application, the parameter value of QNC is,

[0247] It includes at least one of PDB, PER, and CBR.

[0248] In a possible design of the present embodiment of the present application, at least two QNC parameter values ​​exist, and

[0249] At least two parameter values ​​correspond to the same reporting condition, and / or at least two types of parameter values ​​correspond to different reporting conditions.

[0250] In a possible design of the present embodiment of the present application, the reporting condition is,

[0251] Condition in which the change value of the QNC parameter value within the first time is greater than the first threshold value;

[0252] Condition that the rate of change of QNC parameter values ​​within the second time is greater than the second threshold;

[0253] A condition in which the change value of the QNC parameter value within the first time is greater than the first threshold value and is maintained for the third threshold value; and

[0254] Condition in which the rate of change of the QNC parameter value within the second time is greater than the second threshold and continues to be maintained during the fourth threshold.

[0255] Includes at least one of the following,

[0256] The third threshold and the fourth threshold are thresholds for measuring retention time, the third threshold is a threshold for measuring retention time of the change value, and the fourth threshold is a threshold for measuring remaining time of the change rate.

[0257] In a possible design of the present embodiment of the present application, the non-GBR bearer flow is,

[0258] It includes non-GBR Quality of Service (QoS) flows, or non-GBR evolved packet system (EPS) bearers.

[0259] In a possible design of this embodiment of the application, the QNC is defined on the uplink, or the QNC is defined on the downlink, or the QNC is defined on both the uplink and the downlink.

[0260] In a possible design of the present embodiment of the application, the non-GBR bearer flow has a one-to-one correspondence with the target service flow, and the target service flow is a service flow that activates the QNC and includes the parameter values ​​of the QNC.

[0261] FIG. 18 is a block diagram of an application program control device according to an exemplary embodiment of the present application. This device comprises,

[0262] A receiving module (1820) configured to receive a notification message transmitted by an access network device by a core entity ― the notification message is used to indicate that a change in a Quality of Service Notification Control (QNC) parameter of a non-guaranteed bit rate (GBR) flow satisfies a reporting condition ―; and

[0263] It includes a transmission module (1840) configured to send a notification message to an application entity so that the application entity controls the traffic of the application program according to the notification message.

[0264] In a possible design of this embodiment of the present application, the transmission module (1840) is configured to transmit an event report containing a notification message to an application entity by the core entity.

[0265] In a possible design of the present embodiment of the present application, the notification message is,

[0266] It includes the changed parameter value of QNC, or the quantized value of the changed parameter value of QNC.

[0267] In a possible design of this embodiment of the present application, the transmission module (1840) is configured to transmit a QNC profile to an access network device according to the control parameters of the QNC, and

[0268] QNC control parameters are used to specify QNC parameters and reporting conditions.

[0269] In a possible design of this embodiment of the present application, the receiving module (1820) is configured to receive a policy authorization create / update message transmitted by an application entity, and the policy authorization create / update message includes control parameters of the QNC.

[0270] In a possible design of the present embodiment of the present application, the receiving module (1820) is configured to acquire subscription data of QNC, and the subscription data of QNC includes control parameters of QNC.

[0271] FIG. 19 is a schematic structural diagram of a network element device (1900) according to an embodiment of the present application. For example, the network element device may be configured to perform an application program control method. Optionally, the network element device (1900) may be an application entity or a core entity. Specifically, the network element device (1900) may include a processor (1901), a receiver (1902), a transmitter (1903), a memory (1904), and a bus (1905).

[0272] The processor (1901) includes one or more processing cores, and the processor (1901) executes software programs and modules to perform various functional applications and information processing.

[0273] The receiver (1902) and the transmitter (1903) can be implemented as a transceiver (1906). The transceiver (1906) can be a communication chip.

[0274] The memory (1904) is connected to the processor (1901) via the bus (1905).

[0275] Memory (1904) may be configured to store a computer program, and a processor (1901) may be configured to execute a computer program to implement each step executed by an application entity, a core network element, or a core entity of the above-described method embodiment.

[0276] Additionally, memory (1904) may be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include, but are not limited to, RAM, ROM, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory or other solid-state memory technology, CD-ROM, digital versatile disc (DVD) or other optical memory, tape cartridge, magnetic cassette, magnetic disk memory or other magnetic storage device.

[0277] The present application further provides a computer-readable storage medium, wherein the storage medium stores at least one instruction, at least one program, a code set, or an instruction set, and at least one instruction, at least one program, a code set, or an instruction set is loaded and executed by a processor to implement an application program control method according to the method embodiment described above.

[0278] Optionally, the present application further provides a computer program product, the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads computer instructions from a computer-readable storage medium and executes computer instructions to enable the computer device to perform an application program control method according to the aforementioned aspects.

Claims

Claim 1 A method for controlling an application program, comprising: receiving a notification message transmitted by a core entity by an application entity — said notification message is used to indicate that a change in a parameter value of a quality of service notification control (QNC) of a guaranteed bit rate (GBR) bearer flow satisfies a reporting condition —; and controlling the application program by said application entity according to the notification message, wherein the step of controlling the application program by said application entity according to the notification message comprises: controlling a computing policy of said application program by said application entity according to the notification message; and / or controlling a traffic policy of said application program by said application entity according to the notification message. Claim 2 A method for controlling an application program according to claim 1, wherein the step of controlling the computing policy of the application program according to the notification message by the application entity comprises: the step of controlling the application program to be executed according to the first computing policy in response to a notification message used to indicate the deterioration of the parameter value of the QNC; and the step of controlling the application program to be executed according to the second computing policy in response to a notification message used to indicate the optimization of the parameter value of the QNC, wherein the computing time under the first computing policy of the same computing operation is shorter than the computing time under the second computing policy. Claim 3 In paragraph 2, the step of controlling an application program to be executed according to a first computing policy in response to a notification message used to indicate deterioration of the parameter value of the QNC includes the step of controlling the application program to perform encoding and decoding in a first encoding and decoding mode in response to a notification message used to indicate deterioration of the parameter value of the QNC, and the step of controlling an application program to be executed according to a second computing policy in response to a notification message used to indicate optimization of the parameter value of the QNC includes the step of controlling the application program to perform encoding and decoding in a second encoding and decoding mode in response to a notification message used to indicate optimization of the parameter value of the QNC, wherein the computing time under the first encoding and decoding mode of the same computing operation is shorter than the computing time under the second encoding and decoding mode. Claim 4 In claim 1, the step of controlling the traffic policy of the application program according to the notification message by the application entity comprises: the step of controlling the application program to be executed according to the first traffic policy in response to a notification message used to indicate the deterioration of the parameter value of the QNC; and the step of controlling the application program to be executed according to the second traffic policy in response to a notification message used to indicate the optimization of the parameter value of the QNC, wherein the traffic of the first traffic policy is less than the traffic of the second traffic policy. Claim 5 In claim 4, the traffic of the application program includes voice data packets and video data packets, and the step of controlling the application program to be executed according to a first traffic policy in response to a notification message used to indicate the deterioration of the parameter value of the QNC includes the step of maintaining the first traffic corresponding to the voice data packet and reducing the second traffic corresponding to the video data packet in response to a notification message used to indicate the deterioration of the parameter value of the QNC, and the step of controlling the application program to be executed according to a second traffic policy in response to a notification message used to indicate the optimization of the parameter value of the QNC includes the step of maintaining the first traffic corresponding to the voice data packet and increasing the second traffic corresponding to the video data packet in response to a notification message used to indicate the optimization of the parameter value of the QNC. Claim 6 An application program control method according to any one of claims 1 to 5, wherein the notification message is transmitted to the core entity by the access network device entity in response to detecting that a change in the QNC parameter of the non-GBR bearer flow satisfies the reporting condition. Claim 7 An application program control method according to any one of claims 1 to 5, wherein the notification message comprises: a changed parameter value of the QNC; or a quantized value of the changed parameter value of the QNC. Claim 8 An application program control method according to any one of claims 1 to 5, further comprising the step of transmitting to the core entity by the application entity the parameters of the QNC and control parameters of the QNC used to instruct the reporting conditions, wherein the step of transmitting to the core entity by the application entity the control parameters of the QNC comprises the step of transmitting to the core entity by the application entity a policy authorization creation / update message including the control parameters of the QNC. Claim 9 An application program control method according to any one of claims 1 to 5, wherein the reporting condition comprises at least one of: a condition in which the change value of the parameter value of the QNC within a first time is greater than a first threshold value; a condition in which the rate of change of the parameter value of the QNC within a second time is greater than a second threshold value; a condition in which the change value of the parameter value of the QNC within the first time is greater than the first threshold value and is maintained for a third threshold value; and a condition in which the rate of change of the parameter value of the QNC within the second time is greater than the second threshold value and is maintained for a fourth threshold value, wherein the third threshold value and the fourth threshold value are threshold values ​​for measuring the maintenance time. Claim 10 A method for controlling an application program, comprising: receiving a notification message transmitted by an access network device by a core entity — said notification message is used to indicate that a change in a parameter of a Quality of Service Notification Control (QNC) of a non-guaranteed bit rate (GBR) flow satisfies a reporting condition —; and transmitting said notification message to an application entity by the core entity so that the application entity controls the traffic of the application program in accordance with said notification message, wherein controlling the application program includes controlling the computing policy of the application program in accordance with said notification message and / or controlling the traffic policy of the application program in accordance with said notification message. Claim 11 In claim 10, the application program control method further comprises the step of transmitting a QNC profile to an access network device according to the control parameters of the QNC by the core entity, wherein the control parameters of the QNC are used to indicate the parameters of the QNC and the reporting conditions. Claim 12 In claim 11, the core entity comprises a second core entity and a third core entity, and the application program control method further comprises the step of transmitting a policy and charging control (PCC) rule to the second core entity by the third core entity — the PCC rule includes control parameters of the QNC — and the step of transmitting a QNC profile to the access network device by the core entity according to the control parameters of the QNC — the step of transmitting the QNC profile to the access network device by the second core entity — the QNC profile includes control parameters of the QNC — application program control method. Claim 13 A network element device comprising a processor and a memory, wherein the memory stores a computer program executed by the processor in order to enable the network element device to implement an application program control method according to any one of claims 1 to 5, or an application program control method according to any one of claims 10 to 12. Claim 14 A computer-readable storage medium, wherein the computer program is configured to be loaded and executed by a processor to implement an application program control method according to any one of claims 1 to 5 or an application program control method according to any one of claims 10 to 12. Claim 15 delete Claim 16 delete Claim 17 delete Claim 18 delete Claim 19 delete Claim 20 delete Claim 21 delete Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete Claim 27 delete Claim 28 delete Claim 29 delete Claim 30 delete Claim 31 delete Claim 32 delete Claim 33 delete Claim 34 delete

Images